Check-in processing method and device, computer program product and electronic equipment

Abstract

The invention discloses a check-in processing method and device, a computer program product and electronic equipment. Relates to the field of civil aviation passenger check-in, and the method comprises the steps: receiving a check-in request of a linked passenger, determining the total voyage of the linked passenger through the check-in request, and detecting whether a target voyage road section with check-in failure exists in the processing process of the check-in request; under the condition that a target voyage road section exists in the processing process of the check-in request, determining the target voyage road section in the total voyage and a road section after the target voyage road section as a check-in failure route section; generating a re-check-in task based on the voyage information of the check-in failure leg, and storing the re-check-in task in a task cache database; and re-initiating the check-in request of the check-in failure leg based on the re-check-in task every preset duration. According to the invention, the problem of low success rate of connected passenger check-in in the prior art is solved.

Description

Technical Field

[0001] The present application relates to the field of civil aviation passenger check-in, and more specifically, to a check-in processing method, device, computer program product, and electronic equipment. Background Art

[0002] In the departure system, the check-in operation corresponds to the check-in related services of the background system, including verifying the passenger's electronic ticket, checking in the baggage for the passenger, assigning seats for the passenger, processing frequent flyer business, printing passenger boarding passes, etc. The connecting check-in will complete the above service operations for multiple segments at the same time. The multiple segments of the passenger's itinerary may belong to the same airline or different airlines; the flight information may be stored in the local system or other external systems.

[0003] Since connecting check-in generally provides baggage direct check-in service, that is, the service of directly checking in passengers' baggage from the departure station to the terminal, if the transfer time between flight segments is too long, it will be inconvenient for passengers to transfer, because if the transfer time is too long, accommodation may be required, which requires luggage and cannot be checked in. If the equipment at the transfer airport cannot support direct baggage transfer, but requires passengers to take out their baggage midway and then re-check in their baggage (which is also equivalent to handling part of the check-in procedures), then it is not suitable for connecting flights. Whether different airlines can connect, there may be corresponding protocol requirements. The systems to which the flights belong need to support the corresponding communication protocols for connecting. Whether flights from different airlines and different systems can achieve connecting check-in depends on the above factors. The above factors determine the multi-segment itinerary of passengers, which may lead to a low success rate for connecting check-in. In addition to normal and reasonable business factors that cause connecting check-in failure, abnormal system problems can also cause connecting check-in failure, such as system vulnerabilities, insufficient system resources, network communication problems, system interaction failures, temporary network jitter interruptions, etc.

[0004] In the related art, the failed check-in request for connecting flight check-in is manually resolved by manual retry or other methods. Due to the failed connecting flight check-in, the boarding pass / baggage tag for the subsequent flight segment cannot be printed out immediately, which brings inconvenience to passengers. The efficiency of manual re-check-in is low, and the success rate of connecting passengers' check-in is also low.

[0005] With regard to the problem of low check-in success rate for connecting passengers in related technologies, no effective solution has been proposed so far. Summary of the invention

[0006] The main purpose of the present application is to provide a check-in processing method, device, computer program product and electronic device to solve the problem of low check-in success rate for connecting passengers in the related art.

[0007] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a check-in processing method is provided. The method includes: receiving a check-in request from a connecting passenger, determining the total flight of the connecting passenger through the check-in request, and detecting whether there is a target flight segment for which check-in fails during the processing of the check-in request, wherein the connecting passenger is a passenger whose air journey includes multiple flight segments, the total flight includes multiple flight segments, and each flight segment includes at least one transit airport; if there is a target flight segment during the processing of the check-in request, the target flight segment in the total flight and the segment after the target flight segment are determined as the check-in failed segment; generating a re-check-in task based on the flight information of the check-in failed segment, and storing the re-check-in task in the task cache database; re-initiating the check-in request for the check-in failed segment based on the re-check-in task at a preset time interval.

[0008] Optionally, after determining the target flight segment and the segment after the target flight segment in the total flight as the failed check-in segment, the method further includes: determining whether the failed check-in segment includes the starting segment, wherein the starting segment is the segment between the starting airport and the transfer airport; if the failed check-in segment does not include the starting segment, executing the step of generating a re-check-in task based on the flight information of the failed check-in segment; if the failed check-in segment includes the starting segment, issuing a first prompt message, wherein the first prompt message is used to prompt connecting passengers to re-check-in.

[0009] Optionally, before storing the re-check-in task in the task cache database, the method also includes: determining whether there is a historical check-in task corresponding to the flight information in the task cache database; if there is no historical check-in task in the task cache database, executing the step of storing the re-check-in task in the task cache database; if there is a historical check-in task in the task cache database, determining the execution status of the historical check-in task, and determining whether the re-check-in task needs to be stored in the task cache database based on the execution status of the historical check-in task; if the re-check-in task does not need to be stored in the task cache database, discarding the re-check-in task; if the re-check-in task needs to be stored in the task cache database, executing the step of storing the re-check-in task in the task cache database.

[0010] Optionally, judging whether the re-check-in task needs to be stored in the task cache database based on the execution status of the historical check-in task includes: judging whether the historical check-in task is in an executing state; if the historical check-in task is in an executing state, determining that the re-check-in task does not need to be stored in the task cache database; if the historical check-in task is in a completed state, judging whether the time from the moment when the historical check-in task is completed to the current moment is greater than or equal to a time threshold; if the time from the moment when the historical check-in task is completed to the current moment is greater than or equal to the time threshold, determining that the re-check-in task needs to be stored in the task cache database; if the time from the moment when the historical check-in task is completed to the current moment is less than the time threshold, determining that the re-check-in task does not need to be stored in the task cache database.

[0011] Optionally, judging whether the re-check-in task needs to be stored in the task cache database based on the execution status of historical check-in tasks includes: determining the number of executions of the historical check-in task, and judging whether the number of executions is greater than or equal to an execution number threshold; when the number of executions is greater than or equal to the execution number threshold, determining that the re-check-in task does not need to be stored in the task cache database; when the number of executions is less than the execution number threshold, determining that the re-check-in task needs to be stored in the task cache database.

[0012] Optionally, after re-initiating the check-in request for the failed check-in segment based on the re-check-in task at preset intervals, the method also includes: determining the execution time of the re-check-in task, and judging whether the execution time is greater than or equal to an execution time threshold; if the execution time is greater than or equal to the execution time threshold, terminating the re-check-in task, and judging whether the number of executions of the check-in task corresponding to the flight information of the failed check-in segment is greater than or equal to an execution number threshold; if the number of executions is greater than or equal to the execution number threshold, issuing a second prompt message, wherein the second prompt message is used to prompt the operation and maintenance personnel to process the check-in request for the failed check-in segment; if the number of executions is less than the execution number threshold, generating an updated re-check-in task, and storing the updated re-check-in task in the task cache database.

[0013] Optionally, before determining the execution time of the re-check-in task, the method also includes: detecting whether the check-in request for the failed check-in segment is successful within the execution time threshold; when it is detected that the check-in request for the failed check-in segment is successfully requested, issuing a third prompt message, wherein the third prompt message is used to prompt the connecting passenger that the failed check-in segment has been re-checked in successfully; when it is detected that the check-in request for the failed check-in segment is not successfully requested, executing the step of determining the execution time of the re-check-in task.

[0014] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a check-in processing device is provided. The device includes: a receiving unit, which is used to receive a check-in request from a connecting passenger, determine the total flight of the connecting passenger through the check-in request, and detect whether there is a target flight segment for which check-in fails during the processing of the check-in request, wherein the connecting passenger is a passenger whose air journey includes multiple flight segments, the total flight includes multiple flight segments, and each flight segment includes at least one transit airport; a determining unit, which is used to determine the target flight segment in the total flight and the segment after the target flight segment as a check-in failed segment if there is a target flight segment during the processing of the check-in request; a generating unit, which is used to generate a re-check-in task based on the flight information of the check-in failed segment, and store the re-check-in task in a task cache database; and an initiating unit, which is used to re-initiate the check-in request for the check-in failed segment based on the re-check-in task at a preset time interval.

[0015] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the steps of the check-in processing method described in each embodiment of the present application are implemented.

[0016] Through this application, the following steps are adopted: receiving a check-in request of a connecting passenger, determining the total flight of the connecting passenger through the check-in request, and detecting whether there is a target flight segment for which check-in fails during the processing of the check-in request, wherein the connecting passenger is a passenger whose air journey includes multiple flight segments, the total flight includes multiple flight segments, and each flight segment includes at least one transit airport; in the case where there is a target flight segment during the processing of the check-in request, the target flight segment in the total flight and the segment after the target flight segment are determined as the failed check-in segment; generating a re-check-in task based on the flight information of the failed check-in segment, and storing the re-check-in task in the task cache database; re-initiating the check-in request for the failed check-in segment based on the re-check-in task at a preset time interval, thereby solving the problem of low check-in success rate of connecting passengers in the related art. By extracting the failed check-in segment from the failed check-in request, generating a re-check-in task according to the flight information of the failed check-in segment, and initiating the check-in request for the failed check-in segment at a preset time interval, the effect of improving the check-in success rate of connecting passengers is achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings constituting a part of the present application are used to provide a further understanding of the present application. The illustrative embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0018] Figure 1 is a flow chart of a check-in processing method provided according to an embodiment of the present application;

[0019] Figure 2 is a schematic diagram of the check-in process for connecting passengers provided according to an embodiment of the present application;

[0020] Figure 3 is a schematic diagram of a check-in failure process for connecting passengers provided according to an embodiment of the present application;

[0021] Figure 4 It is a schematic diagram of a process for re-initiating a check-in request for a failed check-in segment according to an embodiment of the present application;

[0022] Figure 5 It is a schematic diagram of sending a message of a failed check-in segment according to an embodiment of the present application;

[0023] Figure 6 is a schematic diagram of a check-in processing system provided according to an embodiment of the present application;

[0024] Figure 7 It is a schematic diagram of the processing flow of the check-in task provided according to an embodiment of the present application;

[0025] Figure 8 is a schematic diagram of a check-in processing device provided according to an embodiment of the present application;

[0026] Fig. 9 is a schematic diagram of an electronic device provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0027] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0028] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0029] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0030] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for display, data for analysis, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties.

[0031] It should be noted that the information collected is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data comply with the relevant laws, regulations and standards of the relevant regions, take necessary confidentiality measures, do not violate public order and good customs, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0032] For the convenience of description, some nouns or terms involved in the embodiments of the present application are explained below:

[0033] DCS: Departure Control System, departure system, is a computer real-time network system that performs functions such as check-in for flight passengers, aircraft loading calculations, flight control, and automatic telegram processing.

[0034] Interline Checkin: Interline check-in, also known as "through check-in", includes "through baggage check-in", which means that passengers can complete the check-in procedures for multiple segments of the connecting flight and check-in luggage at the departure airport at one time, without having to pick up the luggage at the transfer airport and re-check in the luggage. After arriving at the transfer station, passengers go to the transfer counter according to the airport signs to complete the transfer procedures.

[0035] Connecting tickets: generally refer to flights from place A to place B, which are divided into several segments. The flights and even the airlines operating the flights may be different for each segment, so a "transfer" is required in the middle. Generally speaking, transfer is very convenient. At the end of the previous segment, the connecting ticket has clear regulations that if you give up the flight of the first segment, you cannot take the flight of the second segment. When checking in for the second segment flight, you need to show the boarding pass of the first segment.

[0036] Global Distribution System: The Global Distribution System is a large-scale computer information service system used in civil aviation transportation and the entire tourism industry.

[0037] The present invention is described below in conjunction with preferred implementation steps. Figure 1 is a flow chart of a check-in processing method provided according to an embodiment of the present application, such as Figure 1 As shown, the method comprises the following steps:

[0038] Step S101, receiving a check-in request of a connecting passenger, determining the total flight of the connecting passenger through the check-in request, and detecting whether there is a target flight segment for which check-in fails during the processing of the check-in request, wherein the connecting passenger is a passenger whose air journey includes multiple flight segments, the total flight includes multiple flight segments, and each flight segment includes at least one transit airport.

[0039] Specifically, a connecting passenger may be a passenger who purchases a connecting ticket. A connecting ticket is a ticket that includes multiple flight segments in the total air journey and needs to be transferred through a transfer airport. For example, if there is no direct flight from place A to place B, a transfer ticket needs to be purchased. If a passenger wants to transfer at place M, then a connecting ticket means that the passenger purchases a ticket for "place A-place M-place B" at the same time, rather than separately purchasing tickets for "place A-place M" and "place M-place B". Non-connecting tickets are purchased in segments of the total journey. Multiple segments of a connecting ticket (i.e., multiple flight segments) are displayed on one ticket number. After the ticket is issued, the passenger will get a string of ticket numbers with preset digits, and one ticket number indicates that the entire total journey is displayed on one ticket. Passengers can check in with only one ticket. For a normal single-segment passenger check-in request, the check-in process may include: check-in status check, electronic ticket status verification, frequent flyer status verification, seat allocation, passenger status data update, flight passenger data update, etc.

[0040] For connecting passengers, after receiving the check-in request from the departure system, the total flight distance of the connecting passenger's trip and the flight segments included in the total flight distance must be determined first. Then the departure system processes the check-in request and checks whether there is a target flight segment where check-in failed during the processing. The target flight segment refers to a flight segment in the total flight distance where check-in failed.

[0041] Check-in request for connecting passengers requires that passengers with multiple segments of the journey be checked in at the same time. Figure 2 is a schematic diagram of the check-in process for connecting passengers provided according to an embodiment of the present application, such as Figure 2 As shown, only after all the flight segments from the origin segment-connecting segment A-connecting segment B-connecting segment C have been successfully checked in, can it be determined that the connecting passenger has successfully checked in this time.

[0042] A failed through check-in request may include a variety of situations. Figure 3 is a schematic diagram of a check-in failure process for connecting passengers provided in an embodiment of the present application, such as Figure 3 As shown, in the first case, since the check-in of the originating segment fails, it needs to be handled immediately, which is not within the technical scope of this embodiment. In the latter three cases, although the check-in of the connecting segment fails, the passenger will be notified, but since it does not affect the passenger's travel of the originating segment, it is allowed by the business, and the boarding pass and baggage tag of the successful check-in segment will be printed normally. After the passenger travels to the originating airport where the first connecting segment fails, he / she will go through the subsequent check-in procedures again.

[0043] It should be noted that when the departure system is processing connecting check-in, if it encounters a flight segment where the first check-in fails, it will no longer continue to process the check-in operation for the subsequent connecting segments, that is, it will not "jump" the flight segment to process the connecting check-in. For normal single-segment and ordinary check-in, if the check-in fails, it will be directly fed back to the operating user for on-the-spot processing, and no additional compensation operations are required in the background. For connecting check-in, as long as the check-in for the starting flight is successful, the failure of check-in for the subsequent flight segments meets the current business requirements. This embodiment is to solve the connecting check-in request for failed check-in for other flight segments except the originating flight segment.

[0044] It should be noted that the itinerary before and after the connecting flight ticket can be the same airline, or it can be an alliance airline such as Star Alliance, Oneworld, SkyTeam. It can also be an airline that has signed a BIA (Baggage Interline Agreement). Passengers who have purchased connecting flights can check in their luggage directly. Taking place A-place M-place B as an example, checking in directly means that you do not need to pick up your luggage when transferring at place M, but pick it up at the destination place B. Connecting flights do not require a transit visa. Because you stay in the transit area, it does not involve entry.

[0045] Although it is a connecting flight, the prerequisite for checking luggage directly is that you do not cross the border for more than 24 hours. Even if there is a luggage check-in agreement between airlines, luggage may not be checked directly. It depends on the specific work instructions of the check-in staff on the day. If it is a non-connecting flight, then you need to make various preparations in advance, such as how to handle the luggage; whether a visa is required during the transfer; the transfer time; whether they will assist in re-checking the luggage, etc.

[0046] Step S102: when there is a target flight segment in the process of processing the check-in request, the target flight segment and the segment after the target flight segment in the total flight are determined as the check-in failed segment.

[0047] Specifically, for a connecting passenger's check-in request, the check-in process for the next flight segment in the total flight can only be initiated after the previous flight segment has been successfully checked in. Therefore, when there is a target flight segment in the process of determining the check-in request, the flight segment after the target flight segment in the total flight will also fail to check in. Therefore, the target flight segment in the total flight and the segment after the target flight segment are determined as the check-in failed segment.

[0048] Step S103: generating a re-check-in task based on the flight information of the failed check-in segment, and storing the re-check-in task in a task cache database.

[0049] Specifically, after the failed check-in segment is determined, it is necessary to save the failed check-in segment information, and re-initiate the check-in request for the failed check-in segment according to the failed check-in segment information. Figure 4 is a schematic diagram of a process for re-initiating a check-in request for a failed check-in segment according to an embodiment of the present application, such as Figure 4 As shown, the failed check-in segments are connecting segment A and connecting segment B. When connecting check-in fails, the failed connecting segment information will be saved in the "failed task cache". The "failed task cache" can be a database table in the task cache database, which is directly stored by the check-in server, or it can be an independent server that exchanges data with the check-in server through an interface.

[0050] Step S104: re-initiating a check-in request for the failed check-in segment based on the re-check-in task at a preset time interval.

[0051] Specifically, the preset duration can be set to one minute. When the re-check-in task in the task cache database is initiated, the connecting check-in interface is called and the result is waited for synchronously. If the execution is successful, the re-check-in task in the task table of the task cache database is updated as successful.

[0052] After storing the re-check-in task in the task cache database, such as Figure 4 As shown, the timer service (or system) starts regularly, obtains the check-in failure segment information saved in the "failed task cache", calls the check-in related services, and re-initiates the check-in request for the failed check-in segment every preset time. If the check-in is successful again, a new check-in success message is sent to the designated "user terminal", and the task data of the successful check-in in the "failed task cache" is deleted at the same time; if the check-in fails again, no changes are made, the current failed task is skipped, and the execution of the next timer service is started. In addition, the time interval for the scheduled start and the number of times the same task is allowed to be repeated can be controlled by configuration; for failed tasks that exceed the number of repeated executions, you can also choose to delete the task or alarm and transfer it to manual processing by the operation and maintenance personnel.

[0053] The first stage is a synchronous request initiated by the user, so the returned data can be directly returned to the user terminal. The second stage is an asynchronous request initiated by the background service, so the returned data must be pre-configured with the destination terminal, system or communication link. The destination terminal can also be a background service. After receiving the new check-in success information, this service will feedback to the final passenger through passenger-related information, for example: configure a text message receiving service to send a successful text message to the passenger.

[0054] The check-in processing method provided in the embodiment of the present application receives a check-in request from a connecting passenger, determines the total flight of the connecting passenger through the check-in request, and detects whether there is a target flight segment for which check-in fails during the processing of the check-in request, wherein the connecting passenger is a passenger whose air journey includes multiple flight segments, the total flight includes multiple flight segments, and each flight segment includes at least one transit airport; if there is a target flight segment during the processing of the check-in request, the target flight segment in the total flight and the segment after the target flight segment are determined as the check-in failed segment; a re-check-in task is generated based on the flight information of the check-in failed segment, and the re-check-in task is stored in a task cache database; and a check-in request for the check-in failed segment is re-initiated based on the re-check-in task at a preset time interval, thereby solving the problem of low check-in success rate of connecting passengers in the related art. By extracting the failed check-in segments from the failed check-in requests, generating re-check-in tasks based on the flight information of the failed check-in segments, and initiating check-in requests for the failed check-in segments at preset intervals, the check-in success rate of connecting passengers is improved.

[0055] For a check-in request for a failed check-in for the starting flight segment, no re-check-in task is generated, but connecting passengers are prompted to re-check-in. Optionally, in the check-in processing method provided in the embodiment of the present application, after determining the target flight segment and the segment after the target flight segment in the total flight as the failed check-in segment, the method further includes: determining whether the failed check-in segment includes the starting flight segment, wherein the starting flight segment is the segment between the starting airport and the transfer airport; if the failed check-in segment does not include the starting flight segment, executing the step of generating a re-check-in task based on the flight information of the failed check-in segment; if the failed check-in segment includes the starting flight segment, issuing a first prompt message, wherein the first prompt message is used to prompt the connecting passenger to re-check-in.

[0056] Specifically, the check-in request that can initiate a re-check-in task in this embodiment refers to a request in which the failed check-in segment does not include the starting segment. Therefore, after determining the failed check-in segment, it is first necessary to determine whether the failed check-in segment includes the starting segment. If the starting segment is included, the connecting passenger is directly prompted to re-initiate the check-in request through the first prompt information. If the failed check-in segment does not include the starting segment, the process of generating a re-check-in task based on the flight information of the failed check-in segment can be executed.

[0057] Among them, during the check-in process of connecting passengers, if the check-in of other connecting segments other than the originating segment fails and it is caused by system reasons, a message is asynchronously sent to the message center, which receives the message and tries to process it again. If the message fails to be sent, it will try to resend it. If it still fails after reaching the maximum number of times, it will be transferred to manual processing. The message includes the previous segment of the flight information of the failed check-in. For example, if the originating segment is successful and the connecting segment A fails, the originating segment + check-in request information is sent; if the connecting segment A is successful and the connecting segment B fails, the connecting segment A + check-in request information is sent; if the connecting segment B is successful and the connecting segment C fails, the connecting segment B + check-in request information is sent, and so on. The sending of messages is determined by the parameters of the check-in interface. When performing compensation tasks, the principle of not changing the original interface should be followed.

[0058] For example, Figure 5 is a schematic diagram of sending a message for a failed check-in segment according to an embodiment of the present application, such as Figure 5 As shown, the front end receives a connecting check-in request initiated by a connecting passenger. After the check-in service receives the request, the check-in request for the first segment is successfully executed, and the check-in for the second segment or the subsequent O segment fails. A message indicating that the first segment is successful and the O segment fails is returned to the front end, and a message indicating that the check-in failed segment is sent to the message center. The message center receives the re-check-in task and stores the task in the task center (i.e., the task cache database). The task center stores or discards the re-check-in task according to the preset task cache logic.

[0059] In this embodiment, the first prompt message is used to prompt the connecting passenger to re-initiate the check-in request for the failed check-in request for the originating flight segment, thereby ensuring a quick response of the connecting passenger to the failed check-in for the originating flight segment, and then enabling the passenger to quickly initiate the check-in request, thereby improving the check-in success rate.

[0060] In order to avoid data conflicts, it is necessary to determine whether there is a historical check-in task corresponding to the voyage information in the task cache database. Optionally, in the check-in processing method provided in the embodiment of the present application, before storing the re-check-in task in the task cache database, the method also includes: determining whether there is a historical check-in task corresponding to the voyage information in the task cache database; if there is no historical check-in task in the task cache database, executing the step of storing the re-check-in task in the task cache database; if there is a historical check-in task in the task cache database, determining the execution status of the historical check-in task, and determining whether the re-check-in task needs to be stored in the task cache database based on the execution status of the historical check-in task; if the re-check-in task does not need to be stored in the task cache database, discarding the re-check-in task; if the re-check-in task needs to be stored in the task cache database, executing the step of storing the re-check-in task in the task cache database.

[0061] Specifically, the historical check-in task may be the last stored re-check-in task corresponding to the flight information, that is, for the flight information of the connecting passenger's failed check-in segment, since the re-check-in task may still fail to check-in, the re-check-in task will be initiated multiple times. However, in order to avoid data conflicts, before storing the re-check-in task in the task cache database, it is necessary to determine whether there is a historical check-in task corresponding to the flight information in the task cache database. If there is no historical check-in task, it means that the current re-check-in task is initiated for the first time, and the re-check-in task is directly stored in the task cache database. If there is a historical check-in task, it is necessary to determine whether the re-check-in task needs to be stored in the task cache database based on the execution status of the historical check-in task. If the re-check-in task does not need to be stored in the task cache database, the re-check-in task will be discarded.

[0062] This embodiment determines whether there is a historical check-in task in the task cache database, and then determines whether it is necessary to store the re-check-in task in the task cache database, thereby avoiding data conflicts in initiating the re-check-in task.

[0063] Optionally, in the check-in processing method provided in the embodiment of the present application, judging whether the re-check-in task needs to be stored in the task cache database based on the execution status of the historical check-in task includes: judging whether the historical check-in task is in an executing state; if the historical check-in task is in an executing state, determining that the re-check-in task does not need to be stored in the task cache database; if the historical check-in task is in an executed state, judging whether the duration from the moment when the historical check-in task is completed to the current moment is greater than or equal to a duration threshold; if the duration from the moment when the historical check-in task is completed to the current moment is greater than or equal to the duration threshold, determining that the re-check-in task needs to be stored in the task cache database; if the duration from the moment when the historical check-in task is completed to the current moment is less than the duration threshold, determining that the re-check-in task does not need to be stored in the task cache database.

[0064] Specifically, if there is a historical check-in task in the task cache database, the execution status of the historical check-in task is determined. In order to avoid task conflicts, if the historical check-in task is being executed, the currently newly initiated re-check-in task does not need to be stored in the task cache database, and the task is directly discarded. If the historical check-in task has been completed, in order to avoid repeated initiation of tasks in a short period of time and the system failure may not have been recovered, resulting in the re-check-in task still failing to check in, a time threshold is set according to expert experience, for example 60 seconds. Within 60 seconds after the completion of the historical check-in task, the re-check-in task will no longer be stored in the task cache database. After more than 60 seconds, the re-check-in task will be stored in the task cache database.

[0065] Among them, the task update mechanism in the task cache database can be to receive messages through the task cache database and persist the task data in the database. The task data has a unique business primary key, such as airline, flight number, flight suffix, airport, and airport departure date as the unique business primary key to prevent concurrent operations. During the storage process, there will be some conditions for discarding tasks. If a task already exists and has just been processed in a short time, such as within 60 seconds, the task request will be discarded. If a task already exists and the task is still in progress, the task will be discarded. If a task already exists and the upper limit of the number of failed retries has not been reached, the re-check-in task will be stored in the task cache database. If there is an insertion conflict caused by concurrent insertion, the task will be discarded. If the task exists and is not in the above-described situation, the status of the existing task is updated to initialization, the number of retries is 0, the request data is updated according to the latest data, and the update time is refreshed.

[0066] This embodiment avoids task conflicts by setting a storage mechanism for storing re-check-in tasks in the task cache database, ensures efficient initiation of re-check-in tasks in the task cache database, and improves the check-in success rate for connecting passengers.

[0067] By setting an execution count threshold, the re-check-in task can be prevented from falling into an infinite loop. Optionally, in the check-in processing method provided in the embodiment of the present application, judging whether the re-check-in task needs to be stored in the task cache database based on the execution status of the historical check-in task includes: determining the execution count of the historical check-in task, and judging whether the execution count is greater than or equal to the execution count threshold; when the execution count is greater than or equal to the execution count threshold, determining that the re-check-in task does not need to be stored in the task cache database; when the execution count is less than the execution count threshold, determining that the re-check-in task needs to be stored in the task cache database.

[0068] Specifically, the execution number threshold may be a number manually set based on expert experience. For example, 10 times is set as the execution number threshold. If the re-check-in task fails for 10 consecutive executions, the re-check-in task will no longer be stored in the task cache database, and the operation and maintenance personnel will be prompted to manually process the check-in request of the connecting passenger.

[0069] This embodiment sets an execution times threshold to avoid continuously initiating the re-check-in task, which would cause the system to fall into an infinite loop, thereby ensuring system security.

[0070] After the re-check-in task is initiated, the execution time is counted, and the re-check-in task is terminated in time after the execution time exceeds the execution time threshold. Optionally, in the check-in processing method provided in the embodiment of the present application, after re-initiating the check-in request for the failed check-in segment based on the re-check-in task at preset time intervals, the method also includes: determining the execution time of the re-check-in task, and judging whether the execution time is greater than or equal to the execution time threshold; if the execution time is greater than or equal to the execution time threshold, terminating the re-check-in task, and judging whether the execution times of the check-in task corresponding to the flight information of the failed check-in segment is greater than or equal to the execution times threshold; if the execution times are greater than or equal to the execution times threshold, issuing a second prompt message, wherein the second prompt message is used to prompt the operation and maintenance personnel to process the check-in request for the failed check-in segment; if the execution times are less than the execution times threshold, generating an updated re-check-in task, and storing the updated re-check-in task in the task cache database.

[0071] Specifically, the execution time threshold can be a threshold manually set according to expert experience, which can be adjusted at any time. For example, if the execution time threshold is set to 5 minutes, if a re-check-in task is still in the execution state for more than 5 minutes after it is initiated, it means that the re-check-in task may be down and needs to be terminated. After termination, it is determined whether the execution times of the re-check-in task exceed the execution times threshold. If not, the updated re-check-in task is continuously generated and stored in the task cache database. If it exceeds the execution times threshold, the operation and maintenance personnel are prompted to process the check-in request for the failed check-in segment through the second prompt information.

[0072] This embodiment avoids downtime of the re-check-in task by setting an execution time threshold, and can timely initiate or notify the operation and maintenance personnel to handle it, thereby improving the processing efficiency of the re-check-in task and further improving the check-in success rate.

[0073] Optionally, in the check-in processing method provided in the embodiment of the present application, before determining the execution time of the re-check-in task, the method also includes: detecting whether the check-in request for the failed check-in segment is successful within the execution time threshold; when it is detected that the check-in request for the failed check-in segment is successfully requested, issuing a third prompt message, wherein the third prompt message is used to prompt the connecting passenger that the failed check-in segment has been successfully re-checked in; when it is detected that the check-in request for the failed check-in segment is not successfully requested, executing the step of determining the execution time of the re-check-in task.

[0074] Specifically, for each re-check-in task, it is detected within the execution time threshold whether the check-in request for the failed check-in segment is successful. If the request is successful, it means that the check-in of the connecting passenger is completed, and the third prompt information is used to prompt the connecting passenger that the failed check-in segment has been successfully re-checked in. If the request is not successful, it is necessary to continue to monitor the execution time, so as to terminate the task in time when the task execution times out.

[0075] This embodiment promptly notifies the connecting passenger that the check-in for the failed flight segment has been successfully rechecked in, thereby ensuring that the passenger receives the check-in information in a timely manner and avoiding the passenger from repeating the check-in operation.

[0076] According to another embodiment of the present application, a check-in processing system is also provided. Figure 6 Schematic diagram of a check-in processing system provided according to an embodiment of the present application. Figure 6 As shown, the check-in processing system includes: a user terminal, a departure system, a failed task cache and a timer.

[0077] Specifically, a user terminal is a system used to initiate a check-in or interline check-in request. The user terminal can be a passenger's mobile phone, computer, a third-party ticket seller, or an airline website system. It also includes airport check-in counter terminals, self-service check-in terminals, etc. Any device that can check in passengers through any channel after the passenger purchases a ticket can be considered a user terminal.

[0078] After receiving the passenger's check-in request, the departure system is the backend service system that actually handles the check-in procedures for the passenger. The departure system stores civil aviation passenger data and the corresponding travel flight data. After the check-in procedures are completed, the internal data of the system will be modified and updated according to the business process.

[0079] The user terminal may not be one device, but a series of devices that work together through different networks to ultimately generate a check-in request and send it to the departure system. The departure system is not necessarily a single system, but may be composed of several servers or several microservices to form a complete system that can ultimately complete the check-in function.

[0080] The failed task cache is used to save the request information of failed check-in. It is an additional system added to the original normal and complete departure system. It can save data and provide functions such as adding, deleting, modifying and checking the corresponding data. This part can be a newly added module of the original departure system, one or more tables of data added to the original system database, or a completely independent system, including its own independent database storage and external interface services.

[0081] The timer can be configured on demand and according to different conditions to automatically initiate new check-in requests regularly, periodically, and automatically. The check-in information comes from the failed task cache, and the check-in request is sent to the departure system.

[0082] The check-in processing system of this embodiment saves the information of the connecting segment that failed to check in, and then performs automatic "secondary" (or multiple) check-in operations for the failed connecting segment at a fixed time, so as to compensate for the "first" check-in request that failed due to system reasons, thereby improving the overall connecting check-in success rate. By introducing a timer service, the check-in service is automatically performed again for the failed connecting segment, reducing labor costs; it supports pushing new connecting flight boarding passes and baggage tags for passengers after successful check-in, improving passenger satisfaction.

[0083] According to another embodiment of the present application, a processing flow of a check-in task is also provided. Figure 7 Schematic diagram of the processing flow of the check-in task provided according to the embodiment of the present application. Figure 7As shown, find the task list of check-in tasks that have been initialized + failed to execute (the number of executions is less than the execution number threshold) + are in process (the execution timeout, the number of executions is less than the execution number threshold), first update the task to be in process, and update the execution time. Call the connecting check-in interface, and wait for the result synchronously. If the execution is successful, update the status of the corresponding check-in task in the task table to success. In the case of multiple connecting segments, but the first segment of the connecting segment other than this segment succeeds, and the others fail, it is also considered successful. If the execution fails, the other failed segments will be processed by the new task.

[0084] Through the above check-in task processing flow, this embodiment can repeatedly initiate the failed check-in task to compensate for the "first" check-in request that failed due to system reasons, thereby improving the overall connecting check-in success rate.

[0085] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0086] The embodiment of the present application also provides a check-in processing device. It should be noted that the check-in processing device of the embodiment of the present application can be used to execute the check-in processing method provided by the embodiment of the present application. The check-in processing device provided by the embodiment of the present application is introduced below.

[0087] Figure 8 Schematic diagram of a check-in processing device provided according to an embodiment of the present application. Figure 8 As shown, the device comprises:

[0088] The receiving unit 801 is configured to receive a check-in request of a connecting passenger, determine the total flight of the connecting passenger through the check-in request, and detect whether there is a target flight segment for which check-in fails during the processing of the check-in request, wherein the connecting passenger is a passenger whose air journey includes multiple flight segments, the total flight includes multiple flight segments, and each flight segment includes at least one transit airport;

[0089] The determining unit 802 is used to determine the target flight segment and the segment after the target flight segment in the total flight as the failed check-in segment if there is a target flight segment in the process of processing the check-in request;

[0090] A generating unit 803, configured to generate a re-check-in task based on the flight information of the failed check-in segment, and store the re-check-in task in a task cache database;

[0091] The initiating unit 804 is configured to re-initiate a check-in request for the failed check-in flight segment based on the re-check-in task at a preset time interval.

[0092] The check-in processing device provided in the embodiment of the present application receives a check-in request of a connecting passenger through a receiving unit 801, determines the total flight of the connecting passenger through the check-in request, and detects whether there is a target flight segment for which check-in fails during the processing of the check-in request, wherein the connecting passenger is a passenger whose air journey includes multiple flight segments, the total flight includes multiple flight segments, and each flight segment includes at least one transit airport; the determining unit 802 determines the target flight segment in the total flight and the segment after the target flight segment as the check-in segment if there is a target flight segment during the processing of the check-in request. Failed segment; a generating unit 803, generating a re-check-in task based on the flight information of the failed check-in segment, and storing the re-check-in task in a task cache database; an initiating unit 804, re-initiating a check-in request for the failed check-in segment based on the re-check-in task at a preset time interval, thereby solving the problem of low check-in success rate for connecting passengers in the related art, extracting the failed check-in segment from the failed check-in request, generating a re-check-in task according to the flight information of the failed check-in segment, and initiating a check-in request for the failed check-in segment at a preset time interval, thereby achieving the effect of improving the check-in success rate for connecting passengers.

[0093] Optionally, in the check-in processing device provided in the embodiment of the present application, the device also includes: a first judgment unit, used to judge whether the failed check-in segment includes the starting segment, wherein the starting segment is the segment between the starting airport and the transit airport; a first execution unit, used to execute the step of generating a re-check-in task based on the flight information of the failed check-in segment when the failed check-in segment does not include the starting segment; a first prompt unit, used to issue a first prompt message when the failed check-in segment includes the starting segment, wherein the first prompt message is used to prompt connecting passengers to re-check-in.

[0094] Optionally, in the check-in processing device provided in the embodiment of the present application, the device also includes: a second judgment unit, used to judge whether there is a historical check-in task corresponding to the flight information in the task cache database; a second execution unit, used to execute the step of storing the re-check-in task in the task cache database when there is no historical check-in task in the task cache database; a third judgment unit, used to determine the execution status of the historical check-in task when there is a historical check-in task in the task cache database, and judge whether the re-check-in task needs to be stored in the task cache database based on the execution status of the historical check-in task; a discarding unit, used to discard the re-check-in task when the re-check-in task does not need to be stored in the task cache database; and a third execution unit, used to execute the step of storing the re-check-in task in the task cache database when the re-check-in task needs to be stored in the task cache database.

[0095] Optionally, in the check-in processing device provided in the embodiment of the present application, the third judgment unit includes: a first judgment module, used to judge whether the historical check-in task is in an execution state; a first determination module, used to determine that the re-check-in task does not need to be stored in the task cache database when the historical check-in task is in an execution state; a second judgment module, used to judge whether the time from the moment when the historical check-in task is completed to the current moment is greater than or equal to a time threshold when the historical check-in task is in a completed state; a second determination module, used to determine that the re-check-in task needs to be stored in the task cache database when the time from the moment when the historical check-in task is completed to the current moment is greater than or equal to the time threshold; a third determination module, used to determine that the re-check-in task does not need to be stored in the task cache database when the time from the moment when the historical check-in task is completed to the current moment is less than the time threshold.

[0096] Optionally, in the check-in processing device provided in the embodiment of the present application, the third judgment unit includes: a fourth determination module, used to determine the number of executions of the historical check-in task, and determine whether the number of executions is greater than or equal to the number of executions threshold; a fifth determination module, used to determine that the re-check-in task does not need to be stored in the task cache database when the number of executions is greater than or equal to the number of executions threshold; a sixth determination module, used to determine that the re-check-in task needs to be stored in the task cache database when the number of executions is less than the number of executions threshold.

[0097] Optionally, in the check-in processing device provided in the embodiment of the present application, the device also includes: a fourth judgment unit, used to determine the execution time of the re-check-in task, and judge whether the execution time is greater than or equal to the execution time threshold; a termination unit, used to terminate the re-check-in task when the execution time is greater than or equal to the execution time threshold, and judge whether the number of executions of the check-in task corresponding to the flight information of the failed check-in segment is greater than or equal to the execution number threshold; a second prompt unit, used to issue a second prompt message when the number of executions is greater than or equal to the execution number threshold, wherein the second prompt message is used to prompt the operation and maintenance personnel to process the check-in request for the failed check-in segment; a storage unit, used to generate an updated re-check-in task when the number of executions is less than the execution number threshold, and store the updated re-check-in task in the task cache database.

[0098] Optionally, in the check-in processing device provided in the embodiment of the present application, the device also includes: a detection unit, used to detect whether the check-in request for the failed check-in segment is successfully requested within the execution time threshold; a third prompt unit, used to issue a third prompt message when it is detected that the check-in request for the failed check-in segment has been successfully requested, wherein the third prompt message is used to prompt the connecting passenger that the failed check-in segment has been successfully re-checked in; and a fourth execution unit, used to execute the step of determining the execution time of the re-check-in task when it is detected that the check-in request for the failed check-in segment has not been successfully requested.

[0099] The check-in processing device includes a processor and a memory. The above-mentioned receiving unit 801, determining unit 802, generating unit 803 and initiating unit 804 are all stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to realize corresponding functions.

[0100] The processor includes a kernel, which calls the corresponding program unit from the memory. One or more kernels can be set, and the check-in success rate of connecting passengers can be improved by adjusting kernel parameters.

[0101] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0102] An embodiment of the present invention provides a computer-readable storage medium on which a program is stored. When the program is executed by a processor, a check-in processing method is implemented.

[0103] An embodiment of the present invention provides a processor, which is used for running a flight program, wherein a check-in processing method is executed when the program is running.

[0104] Fig. 9 is a schematic diagram of an electronic device provided according to an embodiment of the present application. Fig. 9As shown, the electronic device 901 includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, the following steps are implemented: receiving a check-in request of a connecting passenger, determining the total flight of the connecting passenger through the check-in request, and detecting whether there is a target flight segment for which check-in fails during the processing of the check-in request, wherein the connecting passenger is a passenger whose air journey includes multiple flight segments, the total flight includes multiple flight segments, and each flight segment includes at least one transit airport; if there is a target flight segment during the processing of the check-in request, the target flight segment in the total flight and the segment after the target flight segment are determined as the check-in failed segment; generating a re-check-in task based on the flight information of the check-in failed segment, and storing the re-check-in task in the task cache database; re-initiating a check-in request for the check-in failed segment based on the re-check-in task at a preset time interval. The device in this article can be a server, a PC, a PAD, a mobile phone, etc.

[0105] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program that is initialized with the following method steps: receiving a check-in request from a connecting passenger, determining the total flight of the connecting passenger through the check-in request, and detecting whether there is a target flight segment for which check-in fails during the processing of the check-in request, wherein the connecting passenger is a passenger whose air journey includes multiple flight segments, the total flight includes multiple flight segments, and each flight segment includes at least one transit airport; if there is a target flight segment during the processing of the check-in request, determining the target flight segment in the total flight and the segment after the target flight segment as the check-in failed segment; generating a re-check-in task based on the flight information of the check-in failed segment, and storing the re-check-in task in a task cache database; and re-initiating a check-in request for the check-in failed segment based on the re-check-in task at a preset time interval.

[0106] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0107] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0108] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0109] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0110] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0111] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0112] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0113] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0114] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0115] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A check-in processing method, It is characterized in that include: receiving a check-in request from a connecting passenger, determining the total flight of the connecting passenger through the check-in request, and detecting whether there is a target flight segment for which check-in fails during the processing of the check-in request, wherein the connecting passenger is a passenger whose air journey includes multiple flight segments, the total flight includes multiple flight segments, and each flight segment includes at least one transit airport; In the case where the target flight segment exists during the processing of the check-in request, determining the target flight segment and the segment after the target flight segment in the total flight as the check-in failed segment; Generate a re-check-in task based on the flight information of the failed check-in segment, and store the re-check-in task in a task cache database; Re-initiating a check-in request for the failed check-in flight segment based on the re-check-in task at a preset time interval.

2. The method according to claim 1, It is characterized in that After determining the target flight segment and the segment after the target flight segment in the total flight as the failed check-in segment, the method further includes: Determine whether the failed check-in segment includes a starting segment, wherein the starting segment is a segment between a starting airport and a transfer airport; In the case that the failed check-in segment does not include the starting segment, executing the step of generating a re-check-in task based on the flight information of the failed check-in segment; In the case that the failed check-in segment includes the starting segment, a first prompt message is issued, wherein the first prompt message is used to prompt the connecting passenger to check in again.

3. The method according to claim 1, It is characterized in that Before storing the re-check-in task in the task cache database, the method further includes: Determine whether there is a historical check-in task corresponding to the flight information in the task cache database; If the historical check-in task does not exist in the task cache database, executing the step of storing the re-check-in task in the task cache database; In the case where the historical check-in task exists in the task cache database, determining the execution status of the historical check-in task, and judging whether the re-check-in task needs to be stored in the task cache database based on the execution status of the historical check-in task; If the re-check-in task does not need to be stored in the task cache database, discarding the re-check-in task; In the case where the re-check-in task needs to be stored in the task cache database, a step of storing the re-check-in task in the task cache database is performed.

4. The method according to claim 3, It is characterized in that Judging whether the re-check-in task needs to be stored in the task cache database based on the execution status of the historical check-in task includes: Determine whether the historical check-in task is in an executing state; When the historical check-in task is in an executing state, determining that the re-check-in task does not need to be stored in the task cache database; When the historical check-in task is in a completed state, determining whether the duration from the time when the historical check-in task is completed to the current time is greater than or equal to a duration threshold; In the case where the duration from the time when the historical check-in task is completed to the current time is greater than or equal to the duration threshold, determining that the re-check-in task needs to be stored in the task cache database; When the duration from the time when the historical check-in task is completed to the current time is less than the duration threshold, it is determined that the re-check-in task does not need to be stored in the task cache database.

5. The method according to claim 3, It is characterized in that Judging whether the re-check-in task needs to be stored in the task cache database based on the execution status of the historical check-in task includes: Determine the execution times of the historical check-in task, and judge whether the execution times is greater than or equal to the execution times threshold; When the execution number is greater than or equal to the execution number threshold, determining that the re-check-in task does not need to be stored in the task cache database; When the execution times are less than the execution times threshold, it is determined that the re-check-in task needs to be stored in the task cache database.

6. The method according to claim 1, It is characterized in that After re-initiating the check-in request for the failed check-in flight segment based on the re-check-in task at a preset time interval, the method further includes: Determine the execution time of the re-check-in task, and determine whether the execution time is greater than or equal to an execution time threshold; In the case where the execution time is greater than or equal to the execution time threshold, the re-check-in task is terminated, and it is determined whether the execution times of the check-in task corresponding to the flight information of the failed check-in segment is greater than or equal to the execution times threshold; When the execution number is greater than or equal to the execution number threshold, issuing a second prompt message, wherein the second prompt message is used to prompt the operation and maintenance personnel to process the check-in request for the failed check-in segment; In a case where the number of executions is less than the execution number threshold, an updated re-check-in task is generated, and the updated re-check-in task is stored in the task cache database.

7. The method according to claim 6, It is characterized in that Before determining the execution time of the re-check-in task, the method further includes: Detecting whether the check-in request for the failed check-in segment is successful within the execution time threshold; In the case of detecting that the check-in request for the failed check-in segment has been successfully requested, issuing a third prompt message, wherein the third prompt message is used to prompt the connecting passenger that the failed check-in segment has been successfully re-checked in; In the case where it is detected that the check-in request for the failed check-in flight segment is not successfully requested, a step of determining the execution time of the re-check-in task is performed.

8. A check-in processing device, It is characterized in that include: a receiving unit, configured to receive a check-in request of a connecting passenger, determine a total flight of the connecting passenger through the check-in request, and detect whether there is a target flight segment for which check-in fails during the processing of the check-in request, wherein the connecting passenger is a passenger whose air journey includes multiple flight segments, the total flight includes multiple flight segments, and each flight segment includes at least one transit airport; a determining unit, configured to determine, when the target flight segment exists during the processing of the check-in request, the target flight segment and a segment after the target flight segment in the total flight as a failed check-in segment; A generating unit, configured to generate a re-check-in task based on the flight information of the failed check-in segment, and store the re-check-in task in a task cache database; The initiating unit is configured to re-initiate the check-in request for the failed check-in flight segment based on the re-check-in task at a preset time interval.

9. A computer program product comprising a computer program, It is characterized in that When the computer program is executed by a processor, the check-in processing method according to any one of claims 1 to 7 is implemented.

10. An electronic device, It is characterized in that It includes one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the check-in processing method described in any one of claims 1 to 7.

Images