Request message processing method and device, equipment and readable storage medium

Abstract

The embodiment of the invention provides a request message processing method, device and equipment and a readable storage medium, and is applied to the field of data processing. An aggregation platform caches a target query result message and a corresponding message identifier, receives a target confirmation request message sent by a client, and sends the target confirmation request message to the client; the target confirmation request message is used for the client to request a target airline system to verify whether the target flight meets the query condition; and if the target confirmation request message comprises the to-be-checked message identifier, based on a query result message corresponding to the to-be-checked message identifier, verifying whether the target flight meets a query condition, and obtaining a local confirmation result. Visibly, when the first query interface is the interface type corresponding to the query service, the aggregation platform caches the target query result message and the corresponding message identifier, so that after the target confirmation request message is received, the confirmation service can be executed based on the cached data to obtain the local confirmation result, and therefore, the user experience is improved. And the aggregation platform realizes flight data confirmation of the airline through the cache data.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a method, device, equipment and readable storage medium for processing a request message. Background Art

[0002] The aggregation platform deployed on the message aggregation platform provides message parsing, message conversion, and message aggregation for the message interaction between the client and the airline, so that the business process can be executed smoothly. For example, in the flight change process, the client requests the airline system to change the flight through the message aggregation platform. Due to the different interface configurations between different airlines and the message aggregation platform, the number of interface calls is different when the client initiates the same business processing request, resulting in the problem of inconsistent business processing processes. Summary of the invention

[0003] The present application provides a method, apparatus, device and readable storage medium for processing a request message, as follows:

[0004] A method for processing a request message is applied to an aggregation platform, and the method for processing the request message includes:

[0005] Sending a target query request message to a target airline system through a first query interface, wherein the target query request message includes query conditions and the type of query service, and the target query request message is used by the client to request the target airline system to query flight information that meets the query conditions;

[0006] Receiving a target query result message returned by the target airline system through the first query interface;

[0007] If the first query interface belongs to a target interface type, sending the target query result message and the corresponding message identifier to the client, and caching the target query result message and the corresponding message identifier, the target interface type is the interface type corresponding to the query service;

[0008] receiving a target confirmation request message sent by the client, wherein the target confirmation request message includes at least the type of confirmation service and the flight information of the target flight, and the target confirmation request message is used by the client to request the target airline system to verify whether the target flight meets the query condition;

[0009] If the target confirmation request message includes a message identifier to be checked, based on the query result message corresponding to the message identifier to be checked, verify whether the target flight meets the query condition to obtain a local confirmation result.

[0010] Optionally, after receiving the target query result message returned by the target airline system through the first query interface, the method for processing the request message further includes:

[0011] If the first query interface does not belong to the target interface type, sending the target query result message to the client;

[0012] After receiving the target confirmation request message sent by the client, the method for processing the request message further includes:

[0013] If the target confirmation request message does not include a message identifier to be checked, the target confirmation request message is sent to the target airline system through a second query interface, and the target airline system verifies whether the target flight meets the query conditions and obtains an airline confirmation result, and the second query interface belongs to the interface type corresponding to the confirmation service.

[0014] Optionally, before sending the target query request message to the target airline system through the first query interface, the method further includes:

[0015] Receiving a first query request message sent by the client through a preset unified interface, wherein the first query request message includes the type of the query service, the query condition, and the identifier of the target airline system;

[0016] Based on the type of the query service and the identifier of the target airline system, confirm whether the target airline system provides an interface type corresponding to the type of the query service;

[0017] If the target airline system provides an interface type corresponding to the type of the query service, obtaining a query interface of the interface type corresponding to the type of the query service provided by the target airline system as the first query interface;

[0018] If the target airline system does not provide an interface type corresponding to the type of the query service, obtain a query interface of an interface type corresponding to other query service types provided by the target airline system as the first query interface.

[0019] Optionally, sending a target query request message to a target airline system through a first query interface includes:

[0020] If the message type of the first query request message is the same as the interface message type of the first query interface, sending the first query request message as a target query request message to the target airline system;

[0021] If the message type of the first query request message is different from the interface message type of the first query interface, the target query request message obtained by converting the message type of the first query request message is sent to the target airline system through the first query interface, and the message type of the target query request message is the interface message type of the first query interface.

[0022] Optionally, receiving a target confirmation request message sent by the client includes:

[0023] Receiving a target confirmation request message sent by the client through the unified interface;

[0024] The sending of the target confirmation request message to the target airline system through the second query interface includes:

[0025] If the message type of the target confirmation request message is the same as the interface message type of the second query interface, the target confirmation request message is sent to the target airline system through the second query interface;

[0026] If the message type of the target confirmation request message is different from the interface message type of the second query interface, the message type of the target confirmation request message is converted into the interface message type of the second query interface, and the conversion result message is sent to the target airline system through the second query interface.

[0027] Optionally, sending the target query result message to the client includes:

[0028] If the target query result message is different from the message type of the unified interface, convert the message type of the target query result message into the message type of the unified interface, and then send the conversion result message to the client through the unified interface;

[0029] If the target query result message is of the same type as the message type of the unified interface, the target query result message is sent to the client through the unified interface.

[0030] A request message processing device, applied to an aggregation platform, comprising:

[0031] A first query unit, configured to send a target query request message to a target airline system through a first query interface, wherein the target query request message includes a query condition and a type of query service, and the target query request message is used by a client to request the target airline system to query flight information that meets the query condition;

[0032] A query result interface unit, used for receiving a target query result message returned by the target airline system through the first query interface;

[0033] a first query result processing unit, configured to send the target query result message and the corresponding message identifier to the client and cache the target query result message and the corresponding message identifier if the first query interface belongs to a target interface type, and the target interface type is an interface type corresponding to the query service;

[0034] A confirmation request receiving unit, configured to receive a target confirmation request message sent by the client, wherein the target confirmation request message includes at least the type of confirmation service and the flight information of the target flight, and the target confirmation request message is used by the client to request the target airline system to verify whether the target flight meets the query condition;

[0035] The first confirmation request processing unit is used to verify whether the target flight meets the query condition based on the query result message corresponding to the message identifier to be checked if the target confirmation request message includes the message identifier to be checked, and obtain a local confirmation result.

[0036] Optionally, the request message processing device further includes:

[0037] A second query result processing unit, configured to, after receiving the target query result message returned by the target airline system through the first query interface, send the target query result message to the client if the first query interface does not belong to the target interface type;

[0038] The second confirmation request processing unit is used to send the target confirmation request message to the target airline system through a second query interface after receiving the target confirmation request message sent by the client, if the target confirmation request message does not include a message identifier to be checked, and receive the airline confirmation result obtained by the target airline system to verify whether the target flight meets the query conditions. The second query interface belongs to the interface type corresponding to the confirmation service.

[0039] A request message processing device, comprising: a memory and a processor;

[0040] The memory is used to store programs;

[0041] The processor is used to execute the program to implement each step of the method for processing the request message as described above.

[0042] A readable storage medium stores a computer program, which, when executed by a processor, implements the various steps of the method for processing a request message as described above.

[0043] It can be seen from the above technical scheme that the request message processing method, device, equipment and readable storage medium provided in the embodiment of the present application, the aggregation platform sends a target query request message to the target airline system through the first query interface, the target query request message includes the query conditions and the type of query service, and the target query request message is used by the client to request the target airline system to query the flight information that meets the query conditions; receive the target query result message returned by the target airline system through the first query interface; if the first query interface belongs to the target interface type, send the target query result message and the corresponding message identifier to the client, and cache the target query result message and the corresponding message identifier, and the target interface type is the interface type corresponding to the query service; receive the target confirmation request message sent by the client, the target confirmation request message at least includes the type of confirmation service and the flight information of the target flight, and the target confirmation request message is used by the client to request the target airline system to verify whether the target flight meets the query conditions; if the target confirmation request message includes a message identifier to be checked, based on the query result message corresponding to the message identifier to be checked, verify whether the target flight meets the query conditions to obtain a local confirmation result. It can be seen that when the first query interface is the interface type corresponding to the query service, the aggregation platform caches the target query result message and the corresponding message identifier. Therefore, after receiving the target confirmation request message, it can execute the confirmation service based on the cached data to obtain the local confirmation result. It can be seen that the aggregation platform realizes the flight data confirmation of the airline by caching data. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

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

[0046] Figure 1 Schematic diagram of the SQ Airlines flight rebooking process in TrueReshop mode provided for the implementation of this application;

[0047] Figure 2 Schematic diagram of AA airline flight change process in SpecialReshop mode provided for the implementation of this application

[0048] Figure 3A schematic diagram of the structure of a ticket change system provided in an embodiment of the present application;

[0049] Figure 4 A flowchart of a specific implementation method of a request message processing method provided in an embodiment of the present application;

[0050] Figure 5 A schematic diagram of an integrated flight change process provided in an embodiment of the present application;

[0051] Figure 6 A flowchart of a method for converting a request message provided in an embodiment of the present application;

[0052] Figure 7 A flowchart of a method for processing a request message provided in an embodiment of the present application;

[0053] Figure 8 A schematic diagram of the structure of a request message processing device provided in an embodiment of the present application;

[0054] Fig. 9 A schematic diagram of the structure of a request message processing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0055] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be interpreted as being limited to the embodiments set forth herein, but rather these embodiments are provided for a more thorough and complete understanding of the present disclosure.

[0056] It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure. The term "including" and its variations used herein are open inclusions, i.e., "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 other embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the description below. The modifications of "one" and "multiple" mentioned in the present disclosure are illustrative and non-restrictive. Those skilled in the art should understand that unless the context clearly indicates otherwise, it should be understood as "one or more".

[0057] NDC (New Distribution Capability) is a new distribution industry standard that the International Air Transport Association (IATA) has been promoting in recent years. The new distribution capability mainly develops a unified data transmission standard based on XML format messages, through which airlines and their partners can exchange data.

[0058] OOMS (Offer and Order Management System) is an airline sales system built based on the NDC standard. OOMS interacts with downstream channel clients through interfaces and NDC standard messages. OOMS is the carrier for airlines to implement NDC.

[0059] Since each airline's OOMS has a different NDC version, different business understanding, and different application methods, the NDC interfaces provided by the airline's OOMS are different. For example, the NDC interfaces include: AirShopping (Offer query, providing users with the function of querying the required products) interface, OrderCreate (Order generation, providing users with the function of placing orders with the airline's OOMS) interface, OrderRetrieve (Order retrieval, providing users with the function of requesting the airline to view the status of the booked order) interface, etc., OrderReshop (Order change query, providing users with the function of requesting the airline to query the data of the flight that can be changed) interface.

[0060] Due to the diversity of business links and process scenarios in the airline sales process, OOMS must provide a variety of different interfaces to meet the needs of interaction in the entire business process. Each type of interface uses the corresponding NDC message type. It can be seen that the cost and difficulty of connecting the downstream channel client to the NDC interface of the airline OOMS are very high.

[0061] Based on the above reasons, the existing technology configures the aggregation platform of the aggregator to connect to the NDC interfaces of various airlines, summarizes, parses, converts, and fuses the NDC standard messages of different airlines to generate aggregated messages, and then provides a unified interface to downstream channel users in accordance with the NDC standard. The downstream channel clients only need to connect to the unified interface to quickly achieve docking with multiple airlines.

[0062] Due to the different interface configurations between different airlines and aggregation platforms, the number of interface calls when the client initiates the same business processing request is different, resulting in inconsistent business processing procedures. Specifically, the flight change process includes a change data query step. In the flight data query step, it is necessary to request the change data from the OOMS of each airline through the OrderReshop interface. Through the OrderReshop interface, by entering the origin, destination, travel time, original order number, etc., you can obtain the cabin space, brand fare, services and rules information of the changeable flights corresponding to the query conditions.

[0063] However, since the airline does not provide an OrderReshop interface for the rebooking data query step, that is, the airline's OOMS does not provide the OrderReshop interface to query the rebooking data function, the aggregation platform cannot query the rebooking data through the OrderReshop interface.

[0064] Based on the above reasons, there are two modes when the aggregation platform executes the ticket change business process: the real query TrueReshop mode for the first type of OOMS and the special query SpecialReshop mode for the second type of OOMS. Among them, the first type of OOMS refers to the OOMS that provides the OrderReshop interface to query the ticket change data function. The second type of OOMS refers to the OOMS that does not provide the OrderReshop interface to query the ticket change data function.

[0065] Take SQ Airlines OOMS as the first type of OOMS as an example. Figure 1 The SQ Airlines flight change process in TrueReshop mode provided for this application implementation. Figure 1 As shown, in TrueReshop mode, the aggregation platform receives a query request message (OrderReshopRQ message) of the OrderReshop message type sent by the client through a unified interface, calls the OrderReshop interface to send a query request message (OrderReshopRQ message) of the OrderReshop message type to the SQ airline OOMS to query the flight change data, receives a query result message (OrderReshopRS message) of the OrderReshop message type returned by the SQ airline OOMS through the OrderReshop interface, the query result message includes the flight change data, and feeds back the query result message of the OrderReshop message type to the client, so that the client sends a confirmation request for the flight change. After receiving the change payment request, the aggregation platform directly initiates the change payment request and enters the change payment process.

[0066] Take AA Airlines OOMS as the second type of OOMS as an example. Figure 2The AA airline flight change process under the SpecialReshop mode provided for the implementation of this application. In SpecialReshop mode, the aggregation platform receives the query request message (AirShoppingRQ message) of the AirShopping message type sent by the client through the unified interface, sends the AirShoppingRQ message to the AA airline OOMS through the AirShopping interface, and after querying the flight data, returns the query result message (AirShoppingRS message) of the AirShopping message type fed back by the AirShopping interface of the AA airline OOMS to the client. Since the AiRShopping interface itself is not used as a flight change query function, it is actually used as a flight reservation and ticketing query, and the real-time nature of the returned flight data is low, therefore, the client sends a confirmation request (OrderReshopRQ message) of the flight change of the OrderReshop message type to the aggregation platform. After receiving the confirmation request, the aggregation platform sends a confirmation request of the OrderReshop message type to the AA airline OOMS through the OrderReshop interface to request verification of the authenticity of the flight change, and after receiving the confirmation information (OrderReshopRS message) of the OrderReshop message type returned by the AA airline OOMS, after verification, initiates a change payment request and enters the change payment process.

[0067] It can be seen that in SpecialReshop mode, the OOMS interface of the second-category airlines needs to be requested twice, while in TrueReshop mode, the OOMS interface of the second-category airlines only needs to be requested once. Since the message types of each interface are different, after connecting to the airlines, the client and the aggregation platform need to execute different processes for the rebooking processes of different airlines. The processes are not unified. In addition, the client also needs to use different message types for message interaction according to different airlines, which is inefficient.

[0068] In this regard, the embodiment of the present application provides a method for processing request messages applied to an aggregation platform, the purpose of which is to integrate different processing flows of the same service, and specifically can be applied to the integration of processing flows of rebooking services. The method for processing request messages provided in the embodiment of the present application is applied to but not limited to the following: Figure 3The rebooking system shown in the figure includes a client, an aggregation platform, and multiple airlines' quotation and order management systems OOMS (including the first OOMS to the NOOMS). Among them, the aggregation platform can be an aggregation system arranged in the aggregation platform, for example, the Tianyi system of the Tianyi platform. The aggregation platform and the client pre-build a unified message interface, and the aggregation platform and each OOMS are pre-configured with multiple different types of message interfaces, and the interface configuration of the OOMS is stored in the interface configuration file. It should be noted that the message interfaces are all NDC message interfaces.

[0069] Figure 4 A specific implementation process of a method for processing a request message provided in an embodiment of the present application is as follows: Figure 4 As shown, the method is applied to a aggregation platform, including:

[0070] S401: Receive a first query request message sent by a client through a preset unified interface.

[0071] In this embodiment, the unified interface is a pre-configured NDC standard interface between the client and the aggregation platform. In this embodiment, the unified interface is the OrderReshop interface, and the first query request message is a change data query request message of the OrderReshop interface message type, that is, the first OrderReshopRQ message.

[0072] In this embodiment, the rebooking data query request message includes the type of query service, the identifier of the target airline and the query conditions, wherein the type of query service indicates the type of query data in the business process currently initiated by the client. In this step, the type of query service indicates the query of the rebooking data in the rebooking business process currently initiated by the client, and the query conditions include the rebooking query data items such as the starting place, destination, travel time and original order number.

[0073] S402. Based on the target airline's ID and the rebooking service ID, determine the message type of the rebooking query interface of the target airline's OOMS.

[0074] In this embodiment, when each airline OOMS is connected to the aggregation platform, the interface corresponding to each business is configured. The interface type corresponding to each business may be different. The aggregation platform stores the target airline's identifier, business identifier, and interface configuration relationship in the configuration file.

[0075] In this embodiment, the aggregation platform queries the configuration file based on the target airline's ID and the rebooking business ID to obtain the type of the rebooking query interface of the target airline's OOMS, where the rebooking query interface refers to an interface that provides a rebooking data query function. The rebooking query interface includes one of the AirShopping interface and the OrderReshop interface.

[0076] It should be noted that the interface that provides the function of querying rebooking data is not necessarily the interface that can be directly called to return the rebooking data. For the second category of airline OOMS, the interface that provides the function of querying rebooking data is the AirShopping interface. Although the AirShopping interface cannot return the real rebooking data, the AirShopping interface is configured as an interface that responds to rebooking data requests. For the first category of airline OOMS, the interface that provides the function of querying rebooking data is the OrderReshop interface, and the OrderReshop interface can return the real rebooking data.

[0077] S403. Determine whether the message type of the rebooking query interface of the target airline OOMS is the same as the message type of the unified interface. If the message type of the rebooking query interface of the target airline OOMS is the same as the message type of the unified interface, execute S404~S408. If the message type of the rebooking query interface of the target airline OOMS is different from the message type of the unified interface, execute S409~S414.

[0078] S404. Call the rebooking query interface of the target airline OOMS and send the first OrderReshopRQ message to the target airline OOMS, so that the target airline OOMS returns the first query result message based on the query conditions.

[0079] In this embodiment, the rebooking query interface of the target airline OOMS is the OrderReshop interface (of the same type as the unified interface), and the first query result message is a rebooking data query result message of the OrderReshop interface message type, that is, the first OrderReshopRS message, wherein the first query result includes flight data of at least one rebookable flight.

[0080] S405. Receive the first query result message sent by the target airline OOMS through the rebooking query interface, cache the first query result message and the message identifier in the rebooking database, and call the unified interface to send the first query result message and the corresponding message identifier to the client.

[0081] In this embodiment, the message identifier uniquely indicates the first query result message. The message identifier can be determined based on the business identifier, the airline identifier, and the query condition identifier. The specific identifier format and generation method can refer to the prior art.

[0082] S406: Receive a target confirmation request message sent by the client through the unified interface.

[0083] In this embodiment, the target confirmation request message is a change data confirmation request message of the OrderReshop interface message type, that is, the second OrderReshopRQ message. The change data confirmation request message includes the type of confirmation service, the message identifier to be checked, and the flight information of the target flight. Among them, since the target flight OOMS is the first category flight OOMS, the target flight includes the flight selected by the user from the first change data query result through the client. The type of confirmation service indicates the type of verification data in the business process currently initiated by the client. In this step, the type of confirmation service indicates the verification of the changeable data in the change business process currently initiated by the client.

[0084] S407. Based on the confirmation request message, search the ticket change database for a first query result message corresponding to the message identifier to be queried.

[0085] S408. Confirm whether the flight information of the target flight can be changed based on the first query result message. If so, enter the change payment process.

[0086] In this embodiment, the method for confirming whether the flight information of the target flight can be changed based on the first query result message includes: confirming whether the flight information of the target flight is consistent with the flight information of the changeable flight in the first query result message; if they are consistent, confirming that the flight information of the target flight can be changed.

[0087] It should be noted that the method of entering the ticket change payment process can be referred to the existing technology.

[0088] S409. Based on the identifier of the target airline, the type of the rebooking query interface, and the message type of the unified interface, a first message converter is obtained, and the first message converter is used to convert the first query request message into a second query request message.

[0089] In this embodiment, the message type of the change query interface of the target airline OOMS is different from the message type of the unified interface. The change query interface of the target airline OOMS is the AirShopping interface, and the second query request message is a change data query request message of the message type of the change query interface, that is, the AirShoppingRQ message.

[0090] In this embodiment, a first message converter pre-configured by the target airline for converting OrderReshop messages into AirShopping messages is obtained, and the first OrderReshopRQ message is converted into the first AirShoppingRQ message using the first message converter.

[0091] S410. Call the rebooking query interface of the target airline OOMS and send the first AirShoppingRQ message to the target airline OOMS, so that the target airline OOMS returns the second query result message based on the query conditions.

[0092] In this embodiment, the rebooking query interface of the target airline OOMS is the AirShopping interface (different from the type of the unified interface), and the second query result message is a rebooking data query result message of the AirShopping interface message type, that is, the first AirShoppingRS message, wherein the second query result message includes flight data of at least one flight.

[0093] S411. Receive the second query result message sent by the target airline OOMS through the rebooking query interface, obtain the second message converter based on the target airline identifier, the type of the rebooking query interface and the message type of the unified interface, and use the second message converter to convert the second query result message into a third query result message.

[0094] In this embodiment, the third query result message is a query result message of a unified interface message type, that is, a second OrderReshopRS message.

[0095] In this embodiment, a second message converter pre-configured by the target airline for converting the AirShopping message into the OrderReshop message is obtained, and the first AirShoppingRQ message is converted into the second OrderReshopRQ message using the second message converter.

[0096] S412: Call the unified interface to send the third query result message to the client.

[0097] S413: Receive a target confirmation request message sent by the client through the unified interface.

[0098] In this embodiment, the target confirmation request message is a change data confirmation request message of the OrderReshop interface message type, that is, the second OrderReshopRQ message. The change data confirmation request message includes the flight information of the target flight. Specifically, since the target flight OOMS is a second-class flight OOMS, the target flight includes the flight selected by the user from the second change data query result through the client.

[0099] S414. Call the rebooking data confirmation interface and send the target confirmation request message to the target airline OOMS, so that the target airline OOMS verifies whether the flight information of the target flight can be rebooked based on the flight information of the target flight, and sends the verification result message to the aggregation platform.

[0100] In this embodiment, the rebooking confirmation interface is an NDC interface provided by the airline to confirm the target flight verification function, that is, the OrderReshop interface. It can be understood that the OrderReshop interface can directly access the rebooking data and verify whether the flight information of the target flight is rebookable through the rebooking data.

[0101] In this embodiment, the verification result message is of the OrderReshop interface message type, that is, the third OrderReshopRS message.

[0102] It can be seen from the above technical solution that a method for processing request messages provided in an embodiment of the present application integrates the flight rebooking processes of different airlines into a unified flight rebooking process. The aggregation platform caches the first query result message and the corresponding message identifier. After receiving the target confirmation request message and the target confirmation request message includes the message identifier to be checked, it can perform confirmation services based on the cached data to obtain local confirmation results. It can be seen that the aggregation platform realizes the confirmation of airline flight data by caching data. When the target confirmation request message does not include the message identifier to be checked, the aggregation platform sends the target confirmation request message to the target airline OOMS through the rebooking data confirmation interface, and receives the airline confirmation result obtained by the target airline OOMS to verify whether the target flight meets the query conditions. It can be seen that the aggregation platform realizes the confirmation business for flight data of different airlines by caching data or calling interfaces, and realizes the unification of the rebooking business process.

[0103] Furthermore, different types of message conversions are implemented through message converters, so that the client and the aggregation platform can perform message interaction based on a unified interface.

[0104] For example, AA Airlines is a second-class airline and SQ Airlines is a first-class airline. Figure 5 A schematic diagram of the integrated flight change process, such as Figure 5 As shown, the integrated flight change process includes:

[0105] S501. The client sends a first OrderReshopRQ message to the aggregation platform.

[0106] In this embodiment, the airline identifier in the first OrderReshopRQ message includes the airline identifier of the SQ airline or the airline identifier of the AA airline, and the type of the query service type is the query change service.

[0107] S502. The aggregation platform sends the first OrderReshopRQ message to the SQ airline OOMS based on the airline identifier and the business type carried in the first OrderReshopRQ message, or sends the first AirShoppingRQ message obtained by converting the first OrderReshopRQ message by the first message converter to the AA airline OOMS.

[0108] S503, SQ airline OOMS feeds back the first OrderReshopRS message to the aggregation platform, and AA airline OOMS feeds back the first AirShoppingRS message to the aggregation platform.

[0109] S504: The aggregation platform feeds back the first OrderReshopRS message to the client and caches the first OrderReshopRS message and the corresponding message identifier, or feeds back to the client a second OrderReshopRS message obtained by converting the first AirShoppingRS message by the second message converter.

[0110] S505: The client sends a second OrderReshopRQ message to the aggregation platform.

[0111] S506. When the second OrderReshopRQ message carries the message identifier, the aggregation platform confirms whether the target flight can be rescheduled based on the rebooking database. When the second OrderReshopRQ message does not carry the message identifier, the aggregation platform sends the second OrderReshopRQ message to AA airline OOMS.

[0112] S507. AA Airlines OOMS confirms whether the target flight can be rescheduled based on the second OrderReshopRQ message, and sends the third OrderReshopRS message to the aggregation platform.

[0113] S508. The aggregation platform receives the third OrderReshopRS message and confirms whether the target flight can be rescheduled.

[0114] S509. When the aggregation platform confirms in S506 or S508 that the target flight can be rescheduled, the aggregation platform initiates the rescheduled payment process.

[0115] It can be seen from the above technical solution that based on the integrated rebooking process of the request message processing method provided in the embodiment of the present application, the client and the aggregation platform realize message interaction through a unified interface, and the client does not need to build different types of messages based on different types of interfaces provided by the target airline. The aggregation platform caches the first query result message and the corresponding message identifier. After receiving the target confirmation request message and the target confirmation request message includes the message identifier to be checked, it can perform the confirmation service based on the cached data to obtain a local confirmation result. It can be seen that the aggregation platform realizes the flight data confirmation of the airline through cached data. When the target confirmation request message does not include the message identifier to be checked, the aggregation platform sends the target confirmation request message to the AA airline OOMS through the OrderReshop interface, and receives the airline confirmation result obtained by the AA airline OOMS to verify whether the target flight meets the query conditions. It can be seen that the aggregation platform realizes the confirmation service of flight data for the AA airline OOMS and the SQ airline OOMS by caching data or calling interfaces respectively. The unification of business processes is realized.

[0116] It should be noted that the above embodiment is only an optional specific embodiment of a method for processing a request message provided by the present application, and the present application can also be implemented through other optional specific embodiments.

[0117] For example, when the aggregation platform uses a converter to convert the message type of the request message, the conversion method of the request message may include multiple methods. Specifically, the aggregation platform pre-configures a request message converter for each interface (airline interface) of each airline OOMS based on the aggregation platform downstream interface type and the airline interface type. The request message converter is used to realize the conversion of different types of aggregation platform downstream interface messages and airline interface messages. Taking the conversion of the first interface message into the second interface message as an example, Figure 6 The following is an example of a method for converting a request message: Figure 6 As shown, the message conversion method includes:

[0118] S601: Obtain a first node set and a second node set.

[0119] In this embodiment, the first node set includes all nodes of the first interface message, and the second node set includes all nodes of the second interface message.

[0120] S602: Perform node consistency analysis on the first node set and the second node set, and divide the nodes in the first node set into first-type nodes and second-type nodes.

[0121] In this embodiment, the consistency analysis method is to analyze whether each node in the second node set is consistent with each node in the first node set. If there is a second target node in the second node set that is consistent with the first target node in the first node set, the first target node is classified as a first type of node, and the second target node is used as a conversion node of the first type of node.

[0122] For example, when the OrderReshop interface message is converted into the AirShopping interface message, the difference or consistency between the nodes of the OrderReshop interface message and the AirShopping interface message is first analyzed to determine the first type of nodes and the second type of nodes in the nodes of the OrderReshop interface message.

[0123] Specifically, according to the NDC standard message, there are two important nodes, DataLists and OffersGroup, in the AirShopping interface message, and there are nodes such as DataLists, ReshopResults, and ChangeFees in the OrderReshop interface message. Through consistency analysis of the nodes, the DataLists nodes in the AirShopping interface message and the OrderReshop interface message meet the consistency requirements, which include that the same sub-nodes exceed the preset ratio or number. For example, the sub-nodes of the DataLists nodes in the AirShopping interface message and the OrderReshop interface message, such as BaggageAllowanceList (baggage allowance data list definition), BaggageDisclosureList (baggage disclosure data list definition), FareList (fare list definition), MediaList (no mention data list), OriginDestList (OD list), PaxJourneyList (trip list), PaxSegmentList (segment list), PriceClassList (brand fare list), ServiceDefinitionList (service definition list), PaxList (passenger list), etc., are consistent.

[0124] S603: For the first type of nodes, obtain target path node data based on a preset xslt template, extract the target path node data to a conversion node, and obtain a conversion result of the first type of nodes.

[0125] S604: For the second type of nodes, the conversion logic of each shard in the second type of nodes is implemented by a preset conversion code to obtain a conversion result of the second type of nodes.

[0126] S605: Assemble the conversion results of the first type of nodes and the conversion results of the second type of nodes to obtain a second interface message.

[0127] It should be noted that the present application proposes a targeted xslt fragmentation processing method. For the first type of nodes in the message to be converted, the node conversion is directly performed through the xslt template to obtain the conversion result of the first type of nodes. For the second type of nodes in the message to be converted, the nodes are fragmented, and the node data conversion is implemented through the preset java code to obtain the conversion result of the second type of nodes. The conversion results of the first type of nodes and the conversion results of the second type of nodes are aggregated into xslt to obtain a complete xml message. It can be seen that the present application adopts fragmented and segmented message conversion processing, supports the mutual conversion of the two messages, and thus achieves the effect of integration.

[0128] In summary, a method for processing a request message provided in an embodiment of the present application is summarized as follows: Figure 7 The example flowchart is as follows: Figure 7 As shown, the method is applied to the aggregation platform, specifically including:

[0129] S701. Send a target query request message to the target airline system through the first query interface.

[0130] In this embodiment, the target query request message includes the query conditions and the type of query service, and the target query request message is used by the client to request the target airline system to query the flight information that meets the query conditions. The target airline system refers to the target airline's quotation and order management system, that is, the target airline OOMS.

[0131] In this embodiment, the aggregation platform determines the first query interface by the type of query service in the target query request message. An optional method for determining the first query interface includes:

[0132] After the aggregation platform receives the first query request message sent by the client through the preset unified interface, it confirms whether the target airline system provides the interface type corresponding to the query service type based on the type of query service included in the target query request message and the identifier of the target airline system. For example, if the query service type is the rebooking query service, then it is determined whether the target airline system provides the interface type corresponding to the rebooking query service, that is, whether it provides the OrderReshop interface for querying rebooked flight data.

[0133] If the target airline system provides an interface type corresponding to the type of query service, obtain a query interface of the interface type corresponding to the type of query service provided by the target airline system as the first query interface. If the target airline system does not provide an interface type corresponding to the type of query service, obtain a query interface of an interface type corresponding to other types of query services provided by the target airline system as the first query interface.

[0134] For example, if SQ airline OOMS provides an OrderReshop interface for querying rescheduled flight data, the OrderReshop interface will be used as the first query interface. If AA airline OOMS does not provide an OrderReshop interface for querying rescheduled flight data, the AirShopping interface provided by AA airline OOMS for querying real-time flight data will be used as the first query interface.

[0135] In this embodiment, the aggregation platform sends a target query request message to the target airline system through the message type of the first query request message and the interface message type of the first query interface. An optional method of sending a target query request message to the target airline system includes:

[0136] If the message type of the first query request message is the same as the interface message type of the first query interface, the first query request message is sent to the target airline system as the target query request message. If the message type of the first query request message is different from the interface message type of the first query interface, the target query request message obtained by converting the message type of the first query request message is sent to the target airline system through the first query interface, wherein the message type of the target query request message is the interface message type of the first query interface.

[0137] For example, the message type of the first query request message is the OrderReshop interface message type, and the first query interface is the OrderReshop interface. The first query request message is sent to the target airline system as the target query request message through the OrderReshop interface. The message type of the first query request message is the OrderReshop interface message type, and the first query interface is the AirShopping interface. After the message type of the first query request message is converted to the AirShopping interface message type, the conversion result message (i.e., the second query request message) is sent to the target airline system through the AirShopping interface.

[0138] S702, receiving the target query result message returned by the target airline system through the first query interface.

[0139] In this embodiment, the target query result message is the query result data obtained by the target airline system performing the query service based on the query conditions.

[0140] For example, the target query result message returned by SQ airline OOMS through the OrderReshop interface is the first query result message, and the first query result message includes flight data of at least one flight that can be rescheduled. The target query result message returned by AA airline OOMS through the AirShopping interface is the second query result message, and the second query result message includes flight data of at least one flight.

[0141] S703: If the first query interface belongs to the target interface type, send the target query result message and the corresponding message identifier to the client, and cache the target query result message and the corresponding message identifier.

[0142] In this embodiment, the target interface type is the interface type corresponding to the query service, that is, the target interface type is the type of interface used to implement the query service. For example, the OrderReshop interface is the type of interface used to implement the ticket change query service.

[0143] In this embodiment, the method for caching the target query result message and the corresponding message identifier includes storing the target query result message and the corresponding message identifier in a preset result database, for example, a ticket change database.

[0144] S704: If the first query interface does not belong to the target interface type, send a target query result message to the client.

[0145] Optionally, the method of S704 and S704 sending the target query result message to the client includes:

[0146] If the target query result message is different from the message type of the unified interface, the message type of the target query result message is converted to the message type of the unified interface, and the converted result message is sent to the client through the unified interface. If the target query result message is the same as the message type of the unified interface, the target query result message is sent to the client through the unified interface.

[0147] For example, the message type of the second query result message is the AirShopping interface message type, which is different from the message type of the unified interface, the OrderReshop interface message type. The message type of the second query result message is converted to the OrderReshop interface message type to obtain the third query result message, and the third query result message is sent to the client through the unified interface. The first query result message has the same message type as the unified interface, both of which are the OrderReshop interface message type, and the first query result message is sent to the client through the unified interface.

[0148] S705: Receive a target confirmation request message sent by the client.

[0149] In this embodiment, the target confirmation request message includes at least the type of confirmation service and the flight information of the target flight. The target confirmation request message is used by the client to request the target airline system to verify whether the target flight meets the query conditions.

[0150] Optionally, the aggregation platform receives a target confirmation request message sent by the client through a unified interface.

[0151] S706: If the target confirmation request message includes a message identifier to be checked, based on the query result message corresponding to the message identifier to be checked, verify whether the target flight meets the query condition and obtain a local confirmation result.

[0152] S707. If the target confirmation request message does not include a message identifier to be checked, the target confirmation request message is sent to the target airline system through the second query interface, and the target airline system verifies whether the target flight meets the query conditions and obtains the airline confirmation result.

[0153] In this embodiment, the second query interface belongs to the interface type corresponding to the confirmation service. For example, for AA Airlines OOMS, the second query interface is the OrderReshop interface that provides the change confirmation service.

[0154] Optionally, the method in which the aggregation platform sends the target confirmation request message to the target airline system through the second query interface includes:

[0155] If the message type of the target confirmation request message is the same as the interface message type of the second query interface, the target confirmation request message is sent to the target airline system through the second query interface. If the message type of the target confirmation request message is different from the interface message type of the second query interface, the message type of the target confirmation request message is converted to the interface message type of the second query interface, and the conversion result message is sent to the target airline system through the second query interface.

[0156] For example, the message type of the target confirmation request message is the OrderReshop interface message type, and the target confirmation request message is sent to the target airline system, that is, AA airline OOMS. The airline confirmation result obtained by AA airline OOMS verifying whether the target flight meets the query conditions, that is, the verification result message, is received.

[0157] It can be seen from the above technical scheme that an embodiment of the present application provides a method for processing a request message, wherein the aggregation platform sends a target query request message to the target airline system through a first query interface, the target query request message includes query conditions and the type of query service, and the target query request message is used by the client to request the target airline system to query flight information that meets the query conditions; receive the target query result message returned by the target airline system through the first query interface; if the first query interface belongs to the target interface type, send the target query result message and the corresponding message identifier to the client, and cache the target query result message and the corresponding message identifier, and the target interface type is the interface type corresponding to the query service; receive the target confirmation request message sent by the client, the target confirmation request message at least includes the type of confirmation service and the flight information of the target flight, and the target confirmation request message is used by the client to request the target airline system to verify whether the target flight meets the query conditions; if the target confirmation request message includes a message identifier to be queried, based on the query result message corresponding to the message identifier to be queried, verify whether the target flight meets the query conditions to obtain a local confirmation result. It can be seen that when the first query interface is the interface type corresponding to the query service, the aggregation platform caches the target query result message and the corresponding message identifier. Therefore, after receiving the target confirmation request message, it can execute the confirmation service based on the cached data to obtain the local confirmation result. It can be seen that the aggregation platform realizes the flight data confirmation of the airline by caching data.

[0158] Since the aggregation platform does not include the message identifier to be checked in the target confirmation request message, it sends the target confirmation request message to the target airline system through the second query interface, and receives the airline confirmation result obtained by the target airline system to verify whether the target flight meets the query conditions. It can be seen that the aggregation platform realizes the confirmation business of flight data for different types of airlines by caching data or calling interfaces, realizing the unification of business processes.

[0159] Figure 8 A schematic diagram of the structure of a request message processing device provided in an embodiment of the present application is shown. Figure 8 As shown, the request message processing device may include:

[0160] A first query unit, configured to send a target query request message to a target airline system through a first query interface, wherein the target query request message includes a query condition and a type of query service, and the target query request message is used by a client to request the target airline system to query flight information that meets the query condition;

[0161] A query result interface unit, used for receiving a target query result message returned by the target airline system through the first query interface;

[0162] a first query result processing unit, configured to send the target query result message and the corresponding message identifier to the client and cache the target query result message and the corresponding message identifier if the first query interface belongs to a target interface type, and the target interface type is an interface type corresponding to the query service;

[0163] A confirmation request receiving unit, configured to receive a target confirmation request message sent by the client, wherein the target confirmation request message includes at least the type of confirmation service and the flight information of the target flight, and the target confirmation request message is used by the client to request the target airline system to verify whether the target flight meets the query condition;

[0164] The first confirmation request processing unit is used to verify whether the target flight meets the query condition based on the query result message corresponding to the message identifier to be checked if the target confirmation request message includes the message identifier to be checked, and obtain a local confirmation result.

[0165] Fig. 9 A schematic diagram of the structure of a request message processing device provided in an embodiment of the present application is shown, and the request message processing device may include: at least one processor 901, at least one communication interface 902, at least one memory 903 and at least one communication bus 904;

[0166] In the embodiment of the present application, the number of the processor 901, the communication interface 902, the memory 903, and the communication bus 904 is at least one, and the processor 901, the communication interface 902, and the memory 903 communicate with each other through the communication bus 904;

[0167] The processor 901 may be a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention;

[0168] The memory 903 may include a high-speed RAM memory, and may also include a non-volatile memory, such as at least one disk memory;

[0169] The memory stores a program, and the processor can execute the program stored in the memory to implement various steps of a method for processing a request message provided in an embodiment of the present application, as follows:

[0170] A method for processing a request message is applied to an aggregation platform, and the method for processing the request message includes:

[0171] Sending a target query request message to a target airline system through a first query interface, wherein the target query request message includes query conditions and the type of query service, and the target query request message is used by the client to request the target airline system to query flight information that meets the query conditions;

[0172] Receiving a target query result message returned by the target airline system through the first query interface;

[0173] If the first query interface belongs to a target interface type, sending the target query result message and the corresponding message identifier to the client, and caching the target query result message and the corresponding message identifier, the target interface type is the interface type corresponding to the query service;

[0174] receiving a target confirmation request message sent by the client, wherein the target confirmation request message includes at least the type of confirmation service and the flight information of the target flight, and the target confirmation request message is used by the client to request the target airline system to verify whether the target flight meets the query condition;

[0175] If the target confirmation request message includes a message identifier to be checked, based on the query result message corresponding to the message identifier to be checked, verify whether the target flight meets the query condition to obtain a local confirmation result.

[0176] It should be noted that the specific execution method of each step of the above-mentioned request message processing method can refer to the above-mentioned embodiment, and this embodiment will not be repeated.

[0177] The embodiment of the present application further provides a readable storage medium, which may store a computer program suitable for execution by a processor. When the computer program is executed by the processor, the steps of a method for processing a request message provided in the embodiment of the present application are implemented as follows:

[0178] A method for processing a request message, applied to an aggregation platform, the method for processing the request message comprising:

[0179] Sending a target query request message to a target airline system through a first query interface, wherein the target query request message includes query conditions and the type of query service, and the target query request message is used by the client to request the target airline system to query flight information that meets the query conditions;

[0180] Receiving a target query result message returned by the target airline system through the first query interface;

[0181] If the first query interface belongs to a target interface type, sending the target query result message and the corresponding message identifier to the client, and caching the target query result message and the corresponding message identifier, the target interface type is the interface type corresponding to the query service;

[0182] receiving a target confirmation request message sent by the client, wherein the target confirmation request message includes at least the type of confirmation service and the flight information of the target flight, and the target confirmation request message is used by the client to request the target airline system to verify whether the target flight meets the query condition;

[0183] If the target confirmation request message includes a message identifier to be checked, based on the query result message corresponding to the message identifier to be checked, verify whether the target flight meets the query condition to obtain a local confirmation result.

[0184] It should be noted that the specific execution method of each step of the above-mentioned request message processing method can refer to the above-mentioned embodiment, and this embodiment will not be repeated.

[0185] It should be noted that in the context of the present disclosure, a readable storage medium may be a tangible medium that may contain or store a program for use by an instruction execution system, device or equipment or used in combination with an instruction execution system, device or equipment. The readable storage medium may be a machine-readable signal medium or a machine-readable storage medium. The readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the above. More specific examples of readable storage media may include electrical connections based on one or more lines, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above.

[0186] Finally, it should be noted that, in the context of the present disclosure, relational terms such as first and second, etc., are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or equipment including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or equipment. In the absence of more restrictions, the elements limited by the statement "comprise one..." do not exclude the existence of other identical elements in the process, method, article or equipment including the elements.

[0187] Although the subject matter has been described in language specific to structural features and / or methodological logical actions, 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. On the contrary, the specific features and actions described above are merely example forms of implementing the claims.

[0188] Although several specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Certain features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0189] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present disclosure (but not limited to) by each other to form a technical solution.

Claims

1. A method for processing a request message, characterized in that: Applied to the aggregation platform, the method for processing the request message includes: Sending a target query request message to a target airline system through a first query interface, wherein the target query request message includes query conditions and the type of query service, and the target query request message is used by the client to request the target airline system to query flight information that meets the query conditions; Receiving a target query result message returned by the target airline system through the first query interface; If the first query interface belongs to a target interface type, sending the target query result message and the corresponding message identifier to the client, and caching the target query result message and the corresponding message identifier, the target interface type is the interface type corresponding to the query service; receiving a target confirmation request message sent by the client, wherein the target confirmation request message includes at least the type of confirmation service and the flight information of the target flight, and the target confirmation request message is used by the client to request the target airline system to verify whether the target flight meets the query condition; If the target confirmation request message includes a message identifier to be checked, based on the query result message corresponding to the message identifier to be checked, verify whether the target flight meets the query condition to obtain a local confirmation result.

2. The method for processing a request message according to claim 1, characterized in that: After receiving the target query result message returned by the target airline system through the first query interface, the method for processing the request message further includes: If the first query interface does not belong to the target interface type, sending the target query result message to the client; After receiving the target confirmation request message sent by the client, the method for processing the request message further includes: If the target confirmation request message does not include a message identifier to be checked, the target confirmation request message is sent to the target airline system through a second query interface, and the target airline system verifies whether the target flight meets the query conditions and obtains an airline confirmation result, and the second query interface belongs to the interface type corresponding to the confirmation service.

3. The method for processing a request message according to claim 2, characterized in that: Before sending the target query request message to the target airline system through the first query interface, the method for processing the request message further includes: Receiving a first query request message sent by the client through a preset unified interface, wherein the first query request message includes the type of the query service, the query condition, and the identifier of the target airline system; Based on the type of the query service and the identifier of the target airline system, confirm whether the target airline system provides an interface type corresponding to the type of the query service; If the target airline system provides an interface type corresponding to the type of the query service, obtaining a query interface of the interface type corresponding to the type of the query service provided by the target airline system as the first query interface; If the target airline system does not provide an interface type corresponding to the type of the query service, obtain a query interface of an interface type corresponding to other query service types provided by the target airline system as the first query interface.

4. The method for processing a request message according to claim 3, characterized in that: The step of sending the target query request message to the target airline system through the first query interface includes: If the message type of the first query request message is the same as the interface message type of the first query interface, sending the first query request message as a target query request message to the target airline system; If the message type of the first query request message is different from the interface message type of the first query interface, the target query request message obtained by converting the message type of the first query request message is sent to the target airline system through the first query interface, and the message type of the target query request message is the interface message type of the first query interface.

5. The method for processing a request message according to claim 3, characterized in that: The receiving the target confirmation request message sent by the client includes: Receiving a target confirmation request message sent by the client through the unified interface; The sending of the target confirmation request message to the target airline system through the second query interface includes: If the message type of the target confirmation request message is the same as the interface message type of the second query interface, the target confirmation request message is sent to the target airline system through the second query interface; If the message type of the target confirmation request message is different from the interface message type of the second query interface, the message type of the target confirmation request message is converted into the interface message type of the second query interface, and the conversion result message is sent to the target airline system through the second query interface.

6. The method for processing a request message according to claim 3, characterized in that: Sending the target query result message to the client includes: If the target query result message is different from the message type of the unified interface, convert the message type of the target query result message into the message type of the unified interface, and then send the conversion result message to the client through the unified interface; If the target query result message is of the same type as the message type of the unified interface, the target query result message is sent to the client through the unified interface.

7. A request message processing device, characterized in that: Applied to the aggregation platform, the request message processing device includes: A first query unit, configured to send a target query request message to a target airline system through a first query interface, wherein the target query request message includes a query condition and a type of query service, and the target query request message is used by a client to request the target airline system to query flight information that meets the query condition; A query result interface unit, used for receiving a target query result message returned by the target airline system through the first query interface; a first query result processing unit, configured to send the target query result message and the corresponding message identifier to the client and cache the target query result message and the corresponding message identifier if the first query interface belongs to a target interface type, and the target interface type is an interface type corresponding to the query service; A confirmation request receiving unit, configured to receive a target confirmation request message sent by the client, wherein the target confirmation request message includes at least the type of confirmation service and the flight information of the target flight, and the target confirmation request message is used by the client to request the target airline system to verify whether the target flight meets the query condition; The first confirmation request processing unit is used to verify whether the target flight meets the query condition based on the query result message corresponding to the message identifier to be checked if the target confirmation request message includes the message identifier to be checked, and obtain a local confirmation result.

8. The request message processing device according to claim 7, characterized in that: The request message processing device also includes: A second query result processing unit, configured to, after receiving the target query result message returned by the target airline system through the first query interface, send the target query result message to the client if the first query interface does not belong to the target interface type; The second confirmation request processing unit is used to send the target confirmation request message to the target airline system through a second query interface after receiving the target confirmation request message sent by the client, if the target confirmation request message does not include a message identifier to be checked, and receive the airline confirmation result obtained by the target airline system to verify whether the target flight meets the query conditions. The second query interface belongs to the interface type corresponding to the confirmation service.

9. A request message processing device, characterized in that: include: Memory and processor; The memory is used to store programs; The processor is used to execute the program to implement each step of the method for processing a request message as described in any one of claims 1 to 6.

10. A readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, each step of the method for processing a request message according to any one of claims 1 to 6 is implemented.

Images