A request message processing method, device, equipment and readable storage medium

Abstract

Embodiments of the present application provide a request message processing method and device, equipment and readable storage medium, applied to the field of data processing, the aggregation platform caches target query result messages and corresponding message identifiers, receives a target confirmation request message sent by a client, the target confirmation request message is used for 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 to-be-searched message identifier, based on the query result message corresponding to the to-be-searched message identifier, whether the target flight meets the query condition is verified, and a local confirmation result is obtained. It can be seen that the aggregation platform caches target query result messages and corresponding message identifiers when the first query interface is an interface type corresponding to a query service, so that after receiving the target confirmation request message, the confirmation service can be executed 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 by caching data.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a method, apparatus, device, and readable storage medium for processing request messages. Background Technology

[0002] The message aggregation platform, deployed within the message aggregation platform, provides message parsing, conversion, and aggregation functions for message interaction between clients and airlines, ensuring smooth execution of business processes. For example, in a flight rescheduling process, the client requests a rescheduling from the airline's system through the message aggregation platform. Because different airlines have different interface configurations with the message aggregation platform, the number of interface calls varies when a client initiates the same business processing request, leading to inconsistencies in the business processing flow. Summary of the Invention

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

[0004] A method for processing request messages is applied to an aggregation platform. The method for processing request messages includes:

[0005] Through the first query interface, a target query request message is sent to the target airline system. The target query request message includes query conditions and the type of query service. 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] Receive the target query result message returned by the target airline system through the first query interface;

[0007] If the first query interface belongs to the target interface type, the target query result message and the corresponding message identifier are sent to the client, and the target query result message and the corresponding message identifier are cached. The target interface type is the interface type corresponding to the query service.

[0008] The client receives a target confirmation request message, which 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.

[0009] If the target confirmation request message includes a message identifier to be queried, the target flight is verified to meet the query conditions based on the query result message corresponding to the message identifier to be queried, and a local confirmation result is obtained.

[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, the target query result message is sent to the client.

[0012] After receiving the target acknowledgment 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 the message identifier to be queried, the target confirmation request message is sent to the target airline system through the second query interface, and the airline confirmation result obtained by the target airline system in verifying whether the target flight meets the query conditions is received. 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] Receive a first query request message sent by the client through a preset unified interface, wherein the first query request message includes the type of query service, the query conditions, 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 the 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 query service, obtain the query interface corresponding to the type of query service provided by the target airline system, and use it as the first query interface;

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

[0019] Optionally, a target query request message is sent to the target airline's system through the first query interface, including:

[0020] 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 will be sent to the target airline system as the target query request message;

[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 the target acknowledgment request message sent by the client includes:

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

[0024] Sending 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 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.

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

[0028] If the target query result message is not the same as 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 then the conversion result message is sent to the client through the unified interface.

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

[0030] A request message processing apparatus, applied to an aggregation platform, includes:

[0031] The first query unit is used to send a target query request message to the target airline system through the first query interface. The target query request message includes query conditions and the type of query service. 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.

[0032] The query result interface unit is used to receive the target query result message returned by the target airline system through the first query interface;

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

[0034] A confirmation request receiving unit is configured to receive a target confirmation request message sent by the client. 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.

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

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

[0037] The second query result processing unit is 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 configured to, after receiving the target confirmation request message sent by the client, if the target confirmation request message does not include the message identifier to be queried, send the target confirmation request message to the target airline system through the second query interface, 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 device for processing request messages, 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 the various steps of the request message processing method described above.

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

[0043] As can be seen from the above technical solutions, the request message processing method, apparatus, device, and readable storage medium provided in this application embodiment involve the aggregation platform sending 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. 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. The platform receives 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, the platform sends a target query result message and the corresponding message identifier to the client and caches the target query result message and the corresponding message identifier. The target interface type is the interface type corresponding to the query service. The platform receives a target confirmation request message sent by the client. 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. If the target confirmation request message includes a message identifier to be queried, the platform verifies whether the target flight meets the query conditions based on the query result message corresponding to the message identifier to be queried, and obtains a local confirmation result. As can be seen, when the first query interface is the interface type corresponding to the query business, the aggregation platform caches the target query result message and the corresponding message identifier. Therefore, after receiving the target confirmation request message, it can perform the confirmation business based on the cached data to obtain the local confirmation result. It can be seen that the aggregation platform realizes the confirmation of airline flight data by caching data. Attached Figure Description

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

[0045] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote 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 A schematic diagram of the SQ Airlines flight rebooking process under the TrueReshop model provided for the implementation of this application;

[0047] Figure 2 A schematic diagram of the AA airline flight rebooking process under the SpecialReshop model provided for the implementation of this application.

[0048] Figure 3This is a schematic diagram of the structure of a rescheduling system provided in an embodiment of this application;

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

[0050] Figure 5 A schematic diagram illustrating an integrated flight rescheduling process provided as an embodiment of this application;

[0051] Figure 6 A flowchart illustrating a method for converting a request message according to an embodiment of this application;

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

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

[0054] Figure 9 This is a schematic diagram of the structure of a request message processing device provided in an embodiment of this application. Detailed Implementation

[0055] Embodiments of the present disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may 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 the present disclosure.

[0056] 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. The term "comprising" and its variations as used herein are open-ended, 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". The relevant definitions of other terms will be given in the description below. The modifications of "a" and "a plurality" mentioned in this disclosure are illustrative and not restrictive, and those skilled in the art should understand that unless explicitly indicated otherwise in the context, they 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. NDC primarily establishes a unified data transmission standard based on XML format messages, allowing airlines and their partners to exchange data using this unified standard.

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

[0059] Because different airlines have different versions of OOMS NDC, different business understandings, and different application methods, the NDC interfaces provided by airline OOMS are different. For example, NDC interfaces include: AirShopping (Offer query, providing users with the function of querying the products they need), OrderCreate (Order generation, providing users with the function of placing orders with the airline's OOMS), OrderRetrieve (Order retrieval, providing users with the function of requesting the airline to view the status of booked orders), and OrderReshop (Order rescheduling query, providing users with the function of requesting the airline to query the data of rescheduled flights).

[0060] Due to the diversity of business processes and scenarios in airline sales, OOMS must provide various interfaces to meet the interaction needs throughout the entire business process. Each type of interface uses a corresponding NDC message type. Therefore, it is evident that connecting downstream channel clients to the airline's OOMS NDC interface is costly and challenging.

[0061] For the reasons mentioned above, existing technologies use an aggregation platform configured with an aggregator to connect to the NDC interfaces of various airlines. This platform aggregates, parses, transforms, and merges the NDC standard messages from different airlines to generate aggregated messages. Then, it provides a unified interface to downstream channel users according to the NDC standard. Downstream channel clients only need to connect to this unified interface to quickly connect with multiple airlines.

[0062] Because different airlines and aggregation platforms have different interface configurations, the number of interface calls varies when a client initiates the same business processing request, resulting in inconsistent business processing flows. Specifically, the flight rescheduling process includes a rescheduling data query step. In this step, the OrderReshop interface is used to request rescheduling data from each airline's OOMS. By inputting the origin, destination, travel time, and original order number through the OrderReshop interface, information such as available flight class, brand fare, services, and rules corresponding to the query conditions can be obtained.

[0063] However, because some airlines do not provide an OrderReshop interface for querying rebooking data, that is, the airlines' OOMS does not provide an OrderReshop interface to query rebooking data, the aggregation platform cannot query rebooking data through the OrderReshop interface.

[0064] For the reasons mentioned above, the aggregation platform employs two modes when executing the rescheduling process: TrueReshop mode for the first type of OOMS (Object-Ordered Management Systems) and SpecialReshop mode for the second type of OOMS. The first type of OOMS refers to OOMS that provides an OrderReshop interface for querying rescheduling data. The second type of OOMS refers to OOMS that does not provide an OrderReshop interface for querying rescheduling data.

[0065] Taking SQ Airlines' OOMS as an example of the first type of OOMS, Figure 1 The SQ Airlines flight rebooking process under the TrueReshop model provided for the implementation of this application. For example... Figure 1 As shown, in TrueReshop mode, the aggregation platform receives query request messages (OrderReshopRQ messages) of the OrderReshop message type sent by the client through a unified interface. It then calls the OrderReshop interface to send this same query request message (OrderReshopRQ message) to SQ Airlines' OOMS to query flight rebooking data. The platform also receives query result messages (OrderReshopRS messages) of the same OrderReshop message type returned by SQ Airlines' OOMS through the OrderReshop interface. These query result messages include the rebooked flight data. The platform then sends these query result messages back to the client, prompting the client to send a confirmation request for the rebooked flight. Upon receiving the rebooking payment request, the aggregation platform directly initiates the rebooking payment request and enters the rebooking payment process.

[0066] Taking AA Airlines' OOMS as a second-category OOMS as an example, Figure 2The AA airline flight rebooking process under the SpecialReshop model provided for the implementation of this application. In SpecialReshop mode, the aggregation platform receives query request messages (AirShoppingRQ messages) of the AirShopping type from the client through a unified interface. After querying flight data, it sends AirShoppingRQ messages to AA Airlines' OOMS via the AirShopping interface and returns the query result messages (AirShoppingRS messages) of the AirShopping type from AA Airlines' OOMS to the client. Since the AiRShopping interface itself is not used for flight rescheduling query function, but is actually used for flight booking and ticketing query, the real-time timeliness of the returned flight data is low. Therefore, the client sends a flight rescheduling confirmation request (OrderReshopRQ message) of the OrderReshop type to the aggregation platform. After receiving the confirmation request, the aggregation platform sends an OrderReshop confirmation request of the OrderReshop type to AA Airlines' OOMS through the OrderReshop interface to request verification of the authenticity of the rescheduling flight. After receiving the confirmation information (OrderReshopRS message) of the OrderReshop type returned by AA Airlines' OOMS, and confirming that the verification is successful, it initiates a rescheduling payment request and enters the rescheduling payment process.

[0067] It is evident that the SpecialReshop mode requires two requests to the OOMS interface of the second type of airline, while the TrueReshop mode only requires one request to the OOMS interface of the second type of airline. Since the message types are different for each interface type, after connecting the airline, the client and the aggregation platform need to execute different processes for the rebooking process of different airlines. The processes are not uniform. In addition, the client also needs to use different message types for message interaction according to different airlines, which is inefficient.

[0068] To address this, this application provides a method for processing request messages on an aggregation platform, aiming to integrate different processing flows for the same business, specifically applicable to the integration of processing flows for rescheduling services. The request message processing method provided in this application is applicable to, but not limited to, processes such as... Figure 3The rebooking system shown includes a client, an aggregation platform, and multiple airline quoting and order management systems (OOMS) (including the first OOMS to the sixth OOMS). The aggregation platform can be an aggregation system within an aggregation platform, such as the Tianyi system on 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. The interface configurations of the OOMS are stored in interface configuration files. It should be noted that all message interfaces are NDC message interfaces.

[0069] Figure 4 The specific implementation flow of a request message processing method provided in the embodiments of this application is as follows: Figure 4 As shown, this method is applied to an aggregation platform, including:

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

[0071] In this embodiment, the unified interface is the 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 resigning 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. The type of query service indicates the type of data being queried in the current business process initiated by the client. In this step, the type of query service indicates that the client is currently querying rebooking data in the rebooking business process. The query conditions include rebooking query data items such as origin, destination, travel time, and original order number.

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

[0074] In this embodiment, when each airline's OOMS accesses the aggregation platform, it configures the interface corresponding to each service. The interface types corresponding to each service may be different. The aggregation platform stores the target airline's identifier, service identifier, and interface configuration relationship in the configuration file.

[0075] In this embodiment, the aggregation platform, based on the target airline's identifier and rebooking service identifier, queries the configuration file to obtain the type of rebooking query interface for the target airline's OOMS. The rebooking query interface refers to the interface that provides rebooking data query functionality. The rebooking query interface includes one of the AirShopping interface and the OrderReshop interface.

[0076] It's important to note that the interface providing rebooking data query functionality isn't necessarily the same interface that can directly return the rebooking data. For the second type of airline's OOMS, the interface providing rebooking data query functionality is the AirShopping interface. Although the AirShopping interface cannot return the actual rebooking data, it is configured to respond to rebooking data requests. For the first type of airline's OOMS, the interface providing rebooking data query functionality is the OrderReshop interface, which can return the actual rebooking data.

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

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

[0079] In this embodiment, the rebooking query interface of the target airline's OOMS is the OrderReshop interface (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's OOMS through the rebooking query interface, cache the first query result message and 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 service identifier, airline identifier, and query condition identifier. For specific identifier formats and generation methods, please refer to the prior art.

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

[0083] In this embodiment, the target confirmation request message is a rebooking data confirmation request message of the OrderReshop interface message type, i.e., the second OrderReshopRQ message. The rebooking data confirmation request message includes the type of confirmation service, the message identifier to be queried, and the flight information of the target flight. Since the target flight OOMS is a first-type flight OOMS, the target flight includes the flight selected by the user from the first rebooking data query results through the client. The type of confirmation service indicates the type of verification data in the client's current initiation of the service process. In this step, the type of confirmation service indicates the verification of rebookable data in the client's current initiation of the rebooking service process.

[0084] S407. Based on the confirmation request message, search the reschedule database for the first query result message corresponding to the message identifier to be searched.

[0085] S408. Based on the first query result message, confirm whether the flight information of the target flight can be rescheduled. If so, proceed to the rescheduled payment process.

[0086] In this embodiment, the method for confirming whether the flight information of the target flight can be rescheduled 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 reschedulable flight in the first query result message; if they are consistent, then confirming that the flight information of the target flight can be rescheduled.

[0087] It should be noted that the method for entering the rescheduling payment process can be found in existing technologies.

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

[0089] In this embodiment, the message type of the rebooking query interface of the target airline's OOMS is different from the message type of the unified interface. The rebooking query interface of the target airline's OOMS is the AirShopping interface, and the second query request message is the rebooking data query request message of the message type of the rebooking 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. The first message converter is then used to convert a first OrderReshopRQ message into a first AirShoppingRQ message.

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

[0092] In this embodiment, the target airline's OOMS rebooking query interface is the AirShopping interface (which is different from the unified interface type), 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. 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's OOMS through the rebooking query interface. Based on the target airline's identifier, the type of the rebooking query interface, and the message type of the unified interface, obtain the second message converter 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 the unified interface message type, that is, the second OrderReshopRS message.

[0095] In this embodiment, a second message converter pre-configured by the target airline for converting AirShopping messages into OrderReshop messages is obtained. The second message converter is then used to convert the first AirShoppingRQ message into a second OrderReshopRQ message.

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

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

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

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

[0100] In this embodiment, the rebooking confirmation interface is the NDC interface provided by the airline for the verification function of confirming the target flight, namely, 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] As can be seen from the above technical solution, the request message processing method provided in this application integrates the flight rescheduling processes of different airlines into a unified flight rescheduling process. The aggregation platform caches the first query result message and its corresponding message identifier. Upon receiving a target confirmation request message that includes a message identifier to be queried, the platform can perform a confirmation process based on the cached data to obtain a local confirmation result. Therefore, the aggregation platform achieves airline flight data confirmation through data caching. If the target confirmation request message does not include a message identifier to be queried, the aggregation platform sends the target confirmation request message to the target airline's OOMS through the rescheduling data confirmation interface and receives the airline confirmation result from the target airline's OOMS verifying whether the target flight meets the query conditions. Thus, the aggregation platform achieves confirmation of flight data for different airlines through either data caching or interface calls, thereby unifying the rescheduling process.

[0103] Furthermore, a message converter enables the conversion of different types of messages, allowing the client and the aggregation platform to interact with messages based on a unified interface.

[0104] Taking AA as a Category 2 airline and SQ as a Category 1 airline as an example, Figure 5 A diagram illustrating the integrated flight rescheduling process, such as Figure 5 As shown, the integrated flight rescheduling process includes:

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

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

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

[0108] S503 and SQ airlines sent the first OrderReshopRS message to the aggregation platform via OOMS, while AA airline sent the first AirShoppingRS message to the aggregation platform via OOMS.

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

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

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

[0112] S507, AA Airlines' OOMS confirms whether the target flight can be rebooked 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 to confirm whether the target flight can be rescheduled.

[0114] S509. When the aggregation platform confirms that the target flight is available for rebooking in S506 or S508, it initiates the rebooking payment process.

[0115] As can be seen from the above technical solution, the integrated rebooking process based on the request message processing method provided in this application embodiment allows the client and the aggregation platform to interact via a unified interface. The client does not need to construct 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 its corresponding message identifier. Upon receiving a target confirmation request message that includes the message identifier to be queried, the platform can perform confirmation operations based on the cached data to obtain a local confirmation result. Therefore, the aggregation platform confirms airline flight data through cached data. If the target confirmation request message does not include the message identifier to be queried, the aggregation platform sends the target confirmation request message to AA Airlines' OOMS via the OrderReshop interface and receives the airline confirmation result from AA Airlines' OOMS verifying whether the target flight meets the query conditions. Thus, the aggregation platform implements confirmation operations for flight data from both AA Airlines' OOMS and SQ Airlines' OOMS through either cached data or interface calls, achieving a unified business process.

[0116] It should be noted that the above embodiments are only one optional specific embodiment of a request message processing method provided by this application, and this application can also be implemented by other optional specific embodiments.

[0117] For example, when the aggregation platform uses a converter to transform the message type of a request message, the transformation method can include various approaches. Specifically, the aggregation platform pre-configures request message converters for each interface (airline interface) of each airline's OOMS based on the downstream interface type of the aggregation platform and the airline interface type. The request message converter is used to implement the conversion between different types of messages from the downstream interface of the aggregation platform and the airline interface. Taking the conversion of a first interface message into a second interface message as an example... Figure 6 This example illustrates a flowchart of a request message transformation method, such as... Figure 6 As shown, the message conversion methods include:

[0118] S601, Get the first node set and the 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, then the first target node is classified as a first type of node, and the second target node is used as a transformation node for the first type of node.

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

[0123] Specifically, according to the NDC standard message, the AirShopping interface message contains two important nodes: DataLists and OffersGroup, while the OrderReshop interface message contains nodes such as DataLists, ReshopResults, and ChangeFees. Through consistency analysis of the nodes, the DataLists node in both the AirShopping and OrderReshop interface messages meets the consistency requirements. These requirements include the same sub-nodes exceeding a preset proportion or number. For example, the sub-nodes of the DataLists node in both the AirShopping and OrderReshop interface messages, including BaggageAllowanceList (baggage allowance data list definition), BaggageDisclosureList (baggage disclosure data list definition), FareList (fare list definition), MediaList (unmentioned data list), OriginDestList (OD list), PaxJourneyList (trip list), PaxSegmentList (flight segment list), PriceClassList (brand fare list), ServiceDefinitionList (service definition list), and PaxList (passenger list), are all consistent.

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

[0125] S604. For the second type of node, the conversion logic of each fragment in the second type of node is implemented through the preset conversion code to obtain the conversion result of the second type of node.

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

[0127] It should be noted that this application proposes a targeted XSLT fragmentation processing method. For the first type of nodes in the message to be converted, the nodes are directly converted using an 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 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 this application adopts fragmented and segmented message conversion processing, supports mutual conversion between the two types of messages, and thus achieves the effect of integration.

[0128] In summary, the method for processing a request message provided in the embodiments of this application can be summarized as follows: Figure 7 Example flowchart, such as Figure 7 As shown, this method is applied to an aggregation platform and specifically includes:

[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 query conditions and the type of query service. 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. Here, the target airline system refers to the target airline's pricing and order management system, i.e., the target airline's OOMS.

[0131] In this embodiment, the aggregation platform determines the first query interface based on the type of query service in the target query request message. One possible method for determining the first query interface includes:

[0132] After receiving the first query request message sent by the client through a preset unified interface, the aggregation platform determines whether the target airline system provides the interface type corresponding to the query service type based on the query service type and the identifier of the target airline system included in the target query request message. For example, if the query service type is a rebooking query service, then it determines 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 rebooking flight data.

[0133] If the target airline's system provides an interface type corresponding to the type of query service, obtain the query interface corresponding to that type of query service provided by the target airline's system, and use it as the first query interface. If the target airline's system does not provide an interface type corresponding to the type of query service, obtain the query interface corresponding to another type of query service provided by the target airline's system, and use it as the first query interface.

[0134] For example, if SQ Airlines' OOMS provides an OrderReshop interface for querying rebooked flight data, then the OrderReshop interface will be used as the first query interface. If AA Airlines' OOMS does not provide an OrderReshop interface for querying rebooked flight data, then the AirShopping interface provided by AA Airlines' 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 based on the message type of the first query request message and the interface message type of the first query interface. One possible method for 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 first query request message has the message type of the OrderReshop interface and the first query interface is the OrderReshop interface. The first query request message is sent to the target airline's system as the target query request message through the OrderReshop interface. Alternatively, the first query request message has the message type of the OrderReshop interface and the first query interface is the AirShopping interface. After converting the message type of the first query request message to the AirShopping interface message type, the converted message (i.e., the second query request message) is sent to the target airline's system through the AirShopping interface.

[0138] S702, Receive 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 a query based on the query conditions.

[0140] For example, the target query result message returned by SQ Airlines' OOMS through the OrderReshop interface is the first query result message, which includes flight data for at least one rebookable flight. The target query result message returned by AA Airlines' OOMS through the AirShopping interface is the second query result message, which includes flight data for 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 reschedule 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, such as a rescheduling database.

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

[0145] Optionally, the methods by which S704 sends the target query result message to the client include:

[0146] If the target query result message type is different from the unified interface message type, the target query result message type is converted to the unified interface message type before being sent to the client through the unified interface. If the target query result message type is the same as the unified interface message type, 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 OrderReshop interface message type of the unified interface. The message type of the second query result message is converted to the OrderReshop interface message type to obtain the third query result message, which is then sent to the client through the unified interface. The first query result message has the same message type as the unified interface message, both being OrderReshop interface message types, and is sent to the client through the unified interface.

[0148] S705, Receive the 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 target confirmation request messages sent by clients through a unified interface.

[0151] S706. If the target confirmation request message includes a message identifier to be searched, the target flight is verified to meet the search conditions based on the query result message corresponding to the message identifier to be searched, and a local confirmation result is obtained.

[0152] S707. If the target confirmation request message does not include the message identifier to be queried, the target confirmation request message is sent to the target airline system through the second query interface, and the airline confirmation result obtained by the target airline system after verifying whether the target flight meets the query conditions is received.

[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 rebooking confirmation service.

[0154] Optionally, the aggregation platform may send a target confirmation request message to the target airline's system via the second query interface in the following ways:

[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 then the converted message is sent to the target airline system through the second query interface.

[0156] For example, if the target confirmation request message is of the OrderReshop interface message type, it is sent to the target airline's system, i.e., AA Airlines' OOMS. The system then receives the airline's confirmation result from AA Airlines' OOMS, verifying whether the target flight meets the query criteria; that is, the verification result message.

[0157] As can be seen from the above technical solution, the method for processing request messages provided in this application embodiment involves an aggregation platform sending a target query request message to a target airline system through a first query interface. The target query request message includes query conditions and the type of query service. 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. The platform receives a target query result message returned by the target airline system through the first query interface. If the first query interface is a target interface type, the platform sends a target query result message and the corresponding message identifier to the client and caches the target query result message and the corresponding message identifier. The target interface type is the interface type corresponding to the query service. The platform receives a target confirmation request message sent by the client. 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. If the target confirmation request message includes a message identifier to be queried, the platform verifies whether the target flight meets the query conditions based on the query result message corresponding to the message identifier to be queried, and obtains a local confirmation result. As can be seen, when the first query interface is the interface type corresponding to the query business, the aggregation platform caches the target query result message and the corresponding message identifier. Therefore, after receiving the target confirmation request message, it can perform the confirmation business based on the cached data to obtain the local confirmation result. It can be seen that the aggregation platform realizes the confirmation of airline flight data by caching data.

[0158] Since the aggregation platform does not include the identifier of the flight to be queried 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 from the target airline system to verify whether the target flight meets the query conditions. It is evident that the aggregation platform implements the confirmation service for flight data of different types of airlines by caching data or calling interfaces, thus achieving a unified business process.

[0159] Figure 8 This illustration shows a schematic diagram of the structure of a request message processing apparatus provided in an embodiment of this application, as shown below. Figure 8 As shown, the processing device for the request message may include:

[0160] The first query unit is used to send a target query request message to the target airline system through the first query interface. The target query request message includes query conditions and the type of query service. 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.

[0161] The query result interface unit is used to receive the target query result message returned by the target airline system through the first query interface;

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

[0163] A confirmation request receiving unit is configured to receive a target confirmation request message sent by the client. 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.

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

[0165] Figure 9 The diagram shows a schematic of the structure of a request message processing device according to an embodiment of this application. 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 this embodiment of the application, the number of processor 901, communication interface 902, memory 903 and communication bus 904 is at least one, and processor 901, communication interface 902 and memory 903 communicate with each other through communication bus 904;

[0167] The processor 901 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.

[0168] The memory 903 may include high-speed RAM, or it may also include non-volatile memory, such as at least one disk storage device;

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

[0170] A method for processing request messages is applied to an aggregation platform. The method for processing request messages includes:

[0171] Through the first query interface, a target query request message is sent to the target airline system. The target query request message includes query conditions and the type of query service. 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] Receive the target query result message returned by the target airline system through the first query interface;

[0173] If the first query interface belongs to the target interface type, the target query result message and the corresponding message identifier are sent to the client, and the target query result message and the corresponding message identifier are cached. The target interface type is the interface type corresponding to the query service.

[0174] The client receives a target confirmation request message, which 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.

[0175] If the target confirmation request message includes a message identifier to be queried, the target flight is verified to meet the query conditions based on the query result message corresponding to the message identifier to be queried, and a local confirmation result is obtained.

[0176] It should be noted that the specific execution methods of each step in the above request message processing method can be found in the above embodiments, and will not be repeated in this embodiment.

[0177] This application embodiment also provides a readable storage medium that can store a computer program suitable for execution by a processor. When the computer program is executed by the processor, it implements the various steps of a request message processing method provided in this application embodiment, as follows:

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

[0179] Through the first query interface, a target query request message is sent to the target airline system. The target query request message includes query conditions and the type of query service. 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] Receive the target query result message returned by the target airline system through the first query interface;

[0181] If the first query interface belongs to the target interface type, the target query result message and the corresponding message identifier are sent to the client, and the target query result message and the corresponding message identifier are cached. The target interface type is the interface type corresponding to the query service.

[0182] The client receives a target confirmation request message, which 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.

[0183] If the target confirmation request message includes a message identifier to be queried, the target flight is verified to meet the query conditions based on the query result message corresponding to the message identifier to be queried, and a local confirmation result is obtained.

[0184] It should be noted that the specific execution methods of each step in the above request message processing method can be found in the above embodiments, and will not be repeated in this embodiment.

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

[0186] Finally, it should be noted that, in the context of this disclosure, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

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

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

[0189] 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 processing a request message, characterized in that, Applied to an aggregation platform, the method for processing the request message includes: Through the first query interface, a target query request message is sent to the target airline system. The target query request message includes query conditions and the type of query service. 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, the target query result message and the corresponding message identifier are sent to the client, and the target query result message and the corresponding message identifier are cached. The target interface type is the interface type corresponding to the query service. If the first query interface does not belong to the target interface type, the target query result message is sent to the client. The client receives a target confirmation request message, which 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. If the target confirmation request message includes a message identifier to be queried, the target flight is verified to meet the query conditions based on the query result message corresponding to the message identifier to be queried, and a local confirmation result is obtained. If the target confirmation request message does not include the message identifier to be queried, the target confirmation request message is sent to the target airline system through the second query interface, and the airline confirmation result obtained by the target airline system in verifying whether the target flight meets the query conditions is received. The second query interface belongs to the interface type corresponding to the confirmation service.

2. The method for processing request messages according to claim 1, characterized in that, Before sending the target query request message to the target airline system through the first query interface, the processing method of the request message further includes: Receive a first query request message sent by the client through a preset unified interface, wherein the first query request message includes the type of query service, the query conditions, 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 the interface type corresponding to the type of the query service. If the target airline system provides an interface type corresponding to the type of query service, obtain the query interface corresponding to the type of query service provided by the target airline system, and use it as the first query interface; If the target airline system does not provide an interface type corresponding to the type of query service, obtain the query interface corresponding to the type of other query service provided by the target airline system, and use it as the first query interface.

3. The method for processing request messages according to claim 2, characterized in that, The step of sending a 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, the first query request message will be 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, and the message type of the target query request message is the interface message type of the first query interface.

4. The method for processing request messages according to claim 2, characterized in that, The receiving of the target confirmation request message sent by the client includes: Receive the target confirmation request message sent by the client through the unified interface; Sending 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 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.

5. The method for processing request messages according to claim 2, characterized in that, Sending the target query result message to the client includes: If the target query result message is not the same as 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 then the conversion result message is sent to the client through the unified interface. If the target query result message has the same message type as the unified interface, the target query result message is sent to the client through the unified interface.

6. A processing apparatus for request messages, characterized in that, Applied to an aggregation platform, the device for processing the request message includes: The first query unit is used to send a target query request message to the target airline system through the first query interface. The target query request message includes query conditions and the type of query service. 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. The query result interface unit is used to receive the target query result message returned by the target airline system through the first query interface; The first query result processing unit is configured to send the target query result message and the corresponding message identifier to the client if the first query interface belongs to the target interface type, and to cache the target query result message and the corresponding message identifier, wherein the target interface type is the interface type corresponding to the query service; The second query result processing unit is used to send the target query result message to the client if the first query interface does not belong to the target interface type. A confirmation request receiving unit is configured to receive a target confirmation request message sent by the client. 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. The first confirmation request processing unit is configured to, if the target confirmation request message includes a message identifier to be queried, verify whether the target flight meets the query conditions based on the query result message corresponding to the message identifier to be queried, and obtain a local confirmation result; The second confirmation request processing unit is used to send the target confirmation request message to the target airline system through the second query interface if the target confirmation request message does not include the message identifier to be queried, and to 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.

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

8. A readable 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 method for processing request messages as described in any one of claims 1 to 5.

Images