A flight cache updating method and device, a storage medium and an equipment

Abstract

The application provides a flight cache updating method and device, a storage medium and equipment, and relates to the field of civil aviation. After a user request is acquired, the TTL validity period is used to determine whether the flight cabin status cache data is reliable. When the TTL validity period determines that the flight cabin status cache data is reliable, the timestamp of the flight AVS message data is used to determine whether the flight cabin status cache data is reliable. When the timestamp of the flight AVS message data determines that the flight cabin status cache data is reliable again, it is determined that the flight cabin status cache data can be used to respond to the user request, thereby ensuring the reliability of the response result of the user request.

Description

Technical Field

[0001] This invention relates to the field of civil aviation technology, specifically to a method, apparatus, storage medium, and device for updating flight cache. Background Technology

[0002] The fare search process requires the analysis and calculation of massive amounts of flight data, coupled with fare rules and logic, to solve the problem of finding the optimal solution in a massive data space in the shortest possible time, resulting in high business complexity. Currently, there are nearly 700 airlines worldwide, operating more than 200,000 direct flights daily. Each flight is divided into nearly 20 cabin classes, with a number of seats allocated for sale in each class. The number of available seats in each cabin class changes constantly with sales. If the system were to query the cabin status in real time from the airline's PSS system for every business request, the response time would be considerable, and the system interaction cost would be very high. Therefore, most fare search systems choose to use caching technology to process cabin status data.

[0003] Most current fare search systems use a fixed or segmented TTL (Time To Live) model for caching flight cabin availability. In this model, the TTL is relatively fixed. When a request enters the fare search stage, the cache is still within the TTL range, and the system directly uses the cached data. However, if the flight cabin availability changes within this TTL range, the currently used cached data may not be the most accurate, potentially leading to an unoptimal result set returned to the user. This is especially problematic when only one seat remains in a particular cabin class. If someone books and then cancels, and another user books again, the fare search cache may not be updated in a timely manner, resulting in incorrect response results for the user. Summary of the Invention

[0004] In view of this, embodiments of the present invention provide a flight cache update method, apparatus, storage medium, and device to achieve accurate response to user requests.

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

[0006] A method for updating flight cache includes:

[0007] Get user request;

[0008] Parse the user request to obtain the target flight;

[0009] Determine whether the flight cabin status cache data corresponding to the target flight is within the TTL validity period;

[0010] When the TTL is within the validity period, read the flight AVS message data corresponding to the target flight and the timestamp of the flight AVS message data;

[0011] Determine whether the timestamp of the flight AVS message data is later than the timestamp of the flight cabin status cache data;

[0012] When the timestamp of the flight AVS message data is not later than the timestamp of the flight cabin status cache data, the user request is responded to based on the flight cabin status cache data.

[0013] Optionally, in the above flight cache update method, when the timestamp of the flight AVS message data is later than the timestamp of the flight cabin status cache data, the method further includes:

[0014] Based on the flight AVS message data, determine whether all cabins of the target flight are closed;

[0015] When all are closed, the range is used to characterize the response information when all cabins are closed.

[0016] Optionally, in the above flight cache update method, when not all cabins of the target flight are closed, the method further includes:

[0017] The user request is sent to the corresponding airline's PSS system, and a real-time request is initiated to update the flight cabin status cache data.

[0018] Optionally, in the above flight cache update method, when the flight cabin status cache data corresponding to the target flight is not within the TTL validity period, the method further includes:

[0019] The user request is sent to the corresponding airline's PSS system, and a real-time request is initiated to update the flight cabin status cache data.

[0020] Optionally, the above flight cache update method further includes, before obtaining the user request:

[0021] The PSS system of each target airline receives and stores the flight AVS message data corresponding to each flight, as well as the timestamp of the flight AVS message data.

[0022] Optionally, in the above flight cache update method, determining whether the flight cabin status cache data corresponding to the target flight is within the TTL validity period further includes:

[0023] The TTL validity period is configured based on the number of passengers traveling within a preset time period, wherein the larger the number of passengers traveling within the preset time period, the shorter the configured TTL validity period.

[0024] Optionally, in the above flight cache update method, determining whether the flight cabin status cache data corresponding to the target flight is within the TTL validity period further includes:

[0025] Get the current time;

[0026] Determine if the current time falls within the preset peak travel season period;

[0027] When the current time falls within a preset peak travel season, the duration of the TTL validity period is configured as a first duration.

[0028] When the current time is not within a preset peak travel season, the duration of the TTL validity period is configured as the second duration.

[0029] A flight cache update device, comprising:

[0030] The request acquisition unit is used to acquire user requests, parse the user requests, and acquire the target flight.

[0031] The validity period determination unit is used to determine whether the flight cabin status cache data corresponding to the target flight is within the TTL validity period;

[0032] The cached data reliability determination unit is used to read the flight AVS message data corresponding to the target flight and the timestamp of the flight AVS message data when it is within the TTL validity period; and determine whether the timestamp of the flight AVS message data is later than the timestamp of the flight cabin status cached data.

[0033] The request-response unit is used to respond to the user request based on the flight cabin status cache data when the timestamp of the flight AVS message data is not later than the timestamp of the flight cabin status cache data.

[0034] A storage medium storing a computer program thereon, characterized in that, when the computer program is executed by a processor, it implements each step of the flight cache update method described in any one of the preceding claims.

[0035] A flight cache update device, comprising:

[0036] Memory and processor;

[0037] The memory stores a program suitable for execution by the processor, the program being used for:

[0038] Get user request;

[0039] Parse the user request to obtain the target flight;

[0040] Determine whether the flight cabin status cache data corresponding to the target flight is within the TTL validity period;

[0041] When the TTL is within the validity period, read the flight AVS message data corresponding to the target flight and the timestamp of the flight AVS message data;

[0042] Determine whether the timestamp of the flight AVS message data is later than the timestamp of the flight cabin status cache data;

[0043] When the timestamp of the flight AVS message data is not later than the timestamp of the flight cabin status cache data, the user request is responded to based on the flight cabin status cache data.

[0044] Based on the above technical solution, after receiving a user request, the reliability of the flight cabin status cache data is first determined by the TTL validity period. When the flight cabin status cache data is determined to be reliable by the TTL validity period, the reliability of the flight cabin status cache data is determined by the timestamp of the flight AVS message data. When the flight cabin status cache data is determined to be reliable again by the timestamp of the flight AVS message data, it is determined that the flight cabin status cache data can be used to respond to the user request, thus ensuring the reliability of the response result of the user request. Attached Figure Description

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

[0046] Figure 1 This is a flowchart illustrating a flight cache update method disclosed in an embodiment of this application;

[0047] Figure 2 This is a flowchart illustrating a flight cache update method disclosed in another embodiment of this application;

[0048] Figure 3 This is a flowchart illustrating a flight cache update method disclosed in another embodiment of this application;

[0049] Figure 4 This is a flowchart illustrating a flight cache update method disclosed in another embodiment of this application;

[0050] Figure 5 This is a schematic diagram of the structure of a flight cache update device disclosed in an embodiment of this application;

[0051] Figure 6 This is a schematic diagram of the structure of a flight cache update device disclosed in an embodiment of this application. Detailed Implementation

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

[0053] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

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

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

[0056] First, the technical terms used in this application are explained in Table 1:

[0057] TTL Cache lifecycle AVS Flight cabin availability status message POS Point of sale (or sales location) is generally understood to refer to the seller's identity information. POC Point of commencement (origin of the trip)

[0058] Table 1

[0059] In this solution, AVS message data is a cabin status change message sent by the airline to the associated system when the cabin status of a flight changes. Since AVS message data is neutral and unrelated to POS and POC, it cannot be directly used as cabin status in most fare search requests.

[0060] To ensure timely and reliable updates of flight information, this application discloses a flight cache update method. After receiving a user request, the method uses the timestamp of the flight AVS message data and the TTL validity period to jointly determine whether the flight cabin status cache data is reliable. If it is reliable, the flight cabin status cache data responds to the user request; otherwise, the airline's PSS system processes the user request.

[0061] See Figure 1 The flight cache update method disclosed in this application may include:

[0062] Step S101: Obtain user request.

[0063] The user request refers to requests such as flight search requests, ticket booking requests, and fare search requests sent by the user through the user terminal.

[0064] Step S102: Parse the user request and obtain the target flight.

[0065] After obtaining the user request, the user request is parsed to determine the target flight that the user needs to query. Once the target flight is determined, relevant data matching the target flight can be retrieved.

[0066] Step S103: Determine whether the flight cabin status cache data corresponding to the target flight is within the TTL validity period.

[0067] The flight berth status cache data refers to the flight berth cache of most current fare search systems, as mentioned in the background art. Before implementing this solution, a Time-To-Live (TTL) validity period is pre-configured. The validity of the flight berth status cache data can be initially determined by the TTL validity period. When the timestamp of the flight berth status cache data is within the TTL validity period, it indicates that the reliability of the flight berth status cache data is high, and the flight berth status cache data is likely to be in an unchanged state. When the timestamp of the flight berth status cache data is not within the TTL validity period, it indicates that the reliability of the flight berth status cache data is low, and the flight berth status cache data is likely to have changed. Therefore, by determining whether the flight berth status cache data corresponding to the target flight is within the TTL validity period, the reliability of the flight berth status cache data can be initially determined.

[0068] Step S104: When the TTL is within the validity period, read the timestamp of the flight AVS message data corresponding to the target flight.

[0069] In this embodiment, to ensure the reliability of the flight cabin status cache data, it is also necessary to obtain the timestamp of the flight AVS message data and the flight AVS message data from the PSS system of each target airline being served. The timestamp of the flight AVS message data can ensure the most recent update time of the flight data. When the reliability of the flight cabin status cache data is initially determined based on the TTL validity period, the timestamp of the AVS message data needs to be used to further determine the reliability of the flight cabin status cache data. Therefore, it is necessary to obtain the timestamp of the flight AVS message data of the target flight corresponding to the user request.

[0070] In this solution, the AVS message data of each flight to be monitored, along with the timestamps of the flight AVS message data, are sent to the system applying this method in real time. Upon receiving the user request, the system can find the corresponding target flight's flight AVS message data and timestamps locally, without needing to determine the target flight and then interact with the airline's PSS system to obtain the target flight's flight AVS message data and timestamps.

[0071] Step S105: Determine whether the timestamp of the flight AVS message data is later than the timestamp of the flight cabin status cache data.

[0072] After obtaining the timestamp of the target flight's AVS message data, the timestamp of the flight AVS message data is compared with the timestamp of the flight cabin status cache data to determine whether the timestamp of the flight AVS message data is later than the timestamp of the flight cabin status cache data. If the timestamp of the flight AVS message data is later than the timestamp of the flight cabin status cache data, it indicates that the flight data has been updated after the flight cabin status cache data was stored. Therefore, the timestamp of the flight AVS message data is later than the timestamp of the flight cabin status cache data. In this case, although the timestamp of the flight cabin status cache data is within the TTL validity period, the timestamp of the flight cabin status cache data is still invalid and cannot be used to respond to user requests.

[0073] Step S106: When the timestamp of the flight AVS message data is not later than the timestamp of the flight cabin status cache data, respond to the user request based on the flight cabin status cache data.

[0074] If the timestamp of the flight AVS message data is not later than the timestamp of the flight cabin status cache data (e.g., they are the same), it indicates that the flight data has not been updated after the flight cabin status cache data was stored, and the flight cabin status cache data is reliable and can be used to respond to the user request.

[0075] As can be seen from the above scheme, the flight cache update method disclosed in this application, after obtaining a user request, first uses the TTL validity period to determine whether the flight cabin status cache data is reliable. When the flight cabin status cache data is determined to be reliable by the TTL validity period, it is then determined to be reliable based on the timestamp of the flight AVS message data. When the flight cabin status cache data is again determined to be reliable by the timestamp of the flight AVS message data, it is determined that the flight cabin status cache data can be used to respond to the user request, thus ensuring the reliability of the response result of the user request.

[0076] In this embodiment, when obtaining the timestamp of the flight AVS message data, the flight AVS message data is also obtained. This flight AVS message data contains information indicating whether all cabins of the target flight are closed. To improve the processing efficiency of user requests, see [link to documentation]. Figure 2 If the flight cabin status cache data is determined to be unreliable based on the timestamp of the flight AVS message data, the system can first determine whether all cabins of the target flight corresponding to the user request are closed based on the flight AVS message data. If the flight AVS message data indicates that all cabins of the target flight corresponding to the user request are closed, the system can directly respond to the user request and send a response signal to the user indicating that all cabins of the target flight are closed. If the flight AVS message data indicates that not all cabins of the target flight corresponding to the user request are closed, the airline's PSS system needs to respond to the user request. Therefore, the user request needs to be sent to the corresponding airline's PSS system, and a real-time request needs to be initiated to update the flight cabin status cache data stored in the system using this method.

[0077] The technical solution disclosed in this embodiment takes into account that air passenger traffic has peak and off-peak seasons. During the off-peak season, flight data changes less frequently compared to the peak season. Therefore, when determining the validity of the flight cabin status cache data based on the TTL validity period during the off-peak season, the TTL validity period can be set to be longer. Conversely, during the peak season, the TTL validity period can be set to be shorter. Therefore, see... Figure 3In the technical solution disclosed in this embodiment, determining whether the flight cabin status cache data corresponding to the target flight is within the TTL validity period further includes: configuring the TTL validity period based on the number of passengers traveling within a preset time period, wherein the larger the number of passengers traveling within the preset time period, the shorter the configured TTL validity period. The number of passengers traveling within the preset time period can refer to the number of air passengers traveling within a certain period as statistically analyzed by a data statistics department. For example, during domestic holidays such as Spring Festival, May Day, and National Day, the number of air passengers is higher than on regular working days. Therefore, the TTL validity period configured during holidays such as Spring Festival, May Day, and National Day can be shorter, while the TTL validity period configured on regular working days can be longer.

[0078] In this embodiment, since the number of air passengers changes in a regular pattern, to reduce the system's data processing load, certain time periods can be designated as peak travel seasons. These peak seasons have shorter TTL validity periods, while other time periods have longer TTL validity periods. For details, see [link to documentation]. Figure 4 In the above method, determining whether the flight cabin status cache data corresponding to the target flight is within the TTL validity period further includes:

[0079] Step S401: Get the current time.

[0080] Current time refers to the current world time, which can be expressed in days as the smallest unit of time.

[0081] Step S402: Determine whether the current time is within the preset peak travel season period.

[0082] The peak travel season period is a pre-configured time period, which may include various peak travel periods, such as peak travel periods during holidays.

[0083] Step S403: When the current time is within a preset peak travel season, configure the TTL validity period to a first duration.

[0084] Step S404: When the current time is not within a preset peak travel season, configure the TTL validity period to a second duration.

[0085] The first duration is less than the second preset duration.

[0086] This embodiment also discloses a flight cache update device. For the specific working content of each unit in the device, please refer to the above method embodiment.

[0087] The flight cache update device provided in the embodiments of the present invention is described below. The flight cache update device described below and the flight cache update method described above can be referred to in correspondence.

[0088] See Figure 5 The flight cache update device disclosed in this embodiment may include:

[0089] The request acquisition unit 10 is used to acquire user requests, parse the user requests, and acquire the target flight.

[0090] The validity period determination unit 20 is used to determine whether the flight cabin status cache data corresponding to the target flight is within the TTL validity period;

[0091] The cached data reliability judgment unit 30 is used to read the flight AVS message data corresponding to the target flight and the timestamp of the flight AVS message data when it is within the TTL validity period; and to determine whether the timestamp of the flight AVS message data is later than the timestamp of the flight cabin status cached data.

[0092] The request response unit 40 is used to respond to the user request based on the flight cabin status cache data when the timestamp of the flight AVS message data is not later than the timestamp of the flight cabin status cache data.

[0093] The flight cache update device also includes a TTL validity period configuration module, which is used for:

[0094] The TTL validity period is configured based on the number of passengers traveling within a preset time period, wherein the larger the number of passengers traveling within the preset time period, the shorter the configured TTL validity period.

[0095] Alternatively, obtain the current time; determine whether the current time falls within a preset peak travel season; when the current time falls within a preset peak travel season, configure the TTL validity period to a first duration; when the current time does not fall within a preset peak travel season, configure the TTL validity period to a second duration.

[0096] This application also discloses a storage medium storing a computer program thereon, which, when executed by a processor, implements the various steps of the flight cache update method described in any of the above claims.

[0097] Figure 6 The hardware structure diagram of the flight cache update device provided in this embodiment of the invention is shown below. Figure 6 As shown, it may include: at least one processor 100, at least one communication interface 200, at least one memory 300 and at least one communication bus 400;

[0098] In this embodiment of the invention, the number of processor 100, communication interface 200, memory 300, and communication bus 400 is at least one, and the processor 100, communication interface 200, and memory 300 communicate with each other through communication bus 400; obviously, Figure 6 The communication connections shown for the processor 100, communication interface 200, memory 300, and communication bus 400 are optional.

[0099] Optionally, the communication interface 200 can be an interface of a communication module, such as the interface of a GSM module;

[0100] Processor 100 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention.

[0101] The memory 300 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device, which stores a preset program corresponding to the above method embodiments.

[0102] Specifically, processor 100 is used for:

[0103] Get user request;

[0104] Parse the user request to obtain the target flight;

[0105] Determine whether the flight cabin status cache data corresponding to the target flight is within the TTL validity period;

[0106] When the TTL is within the validity period, read the flight AVS message data corresponding to the target flight and the timestamp of the flight AVS message data;

[0107] Determine whether the timestamp of the flight AVS message data is later than the timestamp of the flight cabin status cache data;

[0108] When the timestamp of the flight AVS message data is not later than the timestamp of the flight cabin status cache data, the user request is responded to based on the flight cabin status cache data.

[0109] The processor 100 is also used in various steps of the flight cache update method disclosed in the other embodiments above, which will not be repeated here.

[0110] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0111] In a typical configuration, the device includes one or more processors (CPUs), memory, and a bus. The device may also include input / output interfaces, network interfaces, etc.

[0112] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, like read-only memory (ROM) or flash RAM, and memory includes at least one memory chip. Memory is an example of computer-readable media.

[0113] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0114] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

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

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

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

Claims

1. A method for updating flight cache, characterized in that, include: Get user request; Parse the user request to obtain the target flight; Determine whether the flight cabin status cache data corresponding to the target flight is within the TTL validity period; When the TTL is within the validity period, read the flight AVS message data corresponding to the target flight and the timestamp of the flight AVS message data; wherein, the AVS message data is a cabin status change message sent by the airline in real time, and the AVS message data is independent of the POS of the place of sale and the POC of the place of origin of the trip; Determine whether the timestamp of the flight AVS message data is later than the timestamp of the flight cabin status cache data; When the timestamp of the flight AVS message data is not later than the timestamp of the flight cabin status cache data, the user request is responded to based on the flight cabin status cache data. When the timestamp of the flight AVS message data is later than the timestamp of the flight cabin status cache data... Based on the flight AVS message data, determine whether all cabins of the target flight are closed; When all are closed, feedback is provided to indicate that all cabins are closed; When the cabins of the target flight are not all closed, The user request is sent to the corresponding airline's PSS system, and a real-time request is initiated to update the flight cabin status cache data.

2. The flight cache update method according to claim 1, characterized in that, When the flight cabin status cache data corresponding to the target flight is not within the TTL validity period, the method further includes: The user request is sent to the corresponding airline's PSS system, and a real-time request is initiated to update the flight cabin status cache data.

3. The flight cache update method according to claim 1, characterized in that, Before obtaining the user request, it also includes: The PSS system of each target airline receives and stores the flight AVS message data corresponding to each flight, as well as the timestamp of the flight AVS message data.

4. The flight cache update method according to claim 1, characterized in that, Determining whether the flight cabin status cache data corresponding to the target flight is within the TTL validity period also includes: The TTL validity period is configured based on the number of passengers traveling within a preset time period, wherein the larger the number of passengers traveling within the preset time period, the shorter the configured TTL validity period.

5. The flight cache update method according to claim 4, characterized in that, Determining whether the flight cabin status cache data corresponding to the target flight is within the TTL validity period also includes: Get the current time; Determine if the current time falls within the preset peak travel season period; When the current time falls within a preset peak travel season, the duration of the TTL validity period is configured as a first duration. When the current time is not within a preset peak travel season, the duration of the TTL validity period is configured as the second duration.

6. A flight cache update device, characterized in that, include: The request acquisition unit is used to acquire user requests, parse the user requests, and acquire the target flight. The validity period determination unit is used to determine whether the flight cabin status cache data corresponding to the target flight is within the TTL validity period; The cached data reliability judgment unit is used to read the flight AVS message data corresponding to the target flight and the timestamp of the flight AVS message data when it is within the TTL validity period; wherein, the AVS message data is a cabin status change message sent by the airline in real time, and the AVS message data is independent of the point of sale (POS) and the point of origin (POC); and to determine whether the timestamp of the flight AVS message data is later than the timestamp of the flight cabin status cached data; The request-response unit is configured to respond to the user request based on the flight berth status cache data when the timestamp of the flight AVS message data is not later than the timestamp of the flight berth status cache data; when the timestamp of the flight AVS message data is later than the timestamp of the flight berth status cache data, it determines whether all berths of the target flight are closed based on the flight AVS message data; when all berths are closed, it provides feedback with response information indicating that all berths are closed; when the berths of the target flight are not all closed, it sends the user request to the corresponding airline's PSS system and initiates a real-time request to update the flight berth status cache data.

7. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements each step of the flight cache update method as described in any one of claims 1 to 5.

8. A flight cache update device, characterized in that, include: Memory and processor; The memory stores a program suitable for execution by the processor, the program being used for: Get user request; Parse the user request to obtain the target flight; Determine whether the flight cabin status cache data corresponding to the target flight is within the TTL validity period; When the TTL is within the validity period, read the flight AVS message data corresponding to the target flight and the timestamp of the flight AVS message data; wherein, the AVS message data is a cabin status change message sent by the airline in real time, and the AVS message data is independent of the POS of the place of sale and the POC of the place of origin of the trip; Determine whether the timestamp of the flight AVS message data is later than the timestamp of the flight cabin status cache data; When the timestamp of the flight AVS message data is not later than the timestamp of the flight cabin status cache data, the user request is responded to based on the flight cabin status cache data. When the timestamp of the flight AVS message data is later than the timestamp of the flight cabin status cache data, it is determined whether all cabins of the target flight are closed based on the flight AVS message data. When all are closed, feedback is provided to indicate that all cabins are closed; When the cabin of the target flight is not fully closed, the user request is sent to the corresponding airline's PSS system, and a real-time request is initiated to update the flight cabin status cache data.

Images