A method and apparatus for storing order data
By introducing a version baseline for orders, dynamically calculating incremental data and storing it in the database, the problem of deep coupling between the order data update process and the business process is solved, and order data updates that are easy to maintain are realized.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- TRAVELSKY TECHNOLOGY LIMITED
- Filing Date
- 2023-04-04
- Publication Date
- 2026-05-12
AI Technical Summary
In existing technologies, the order data update process is deeply coupled with the business process, making it difficult to maintain.
By introducing an order version baseline, incremental data is dynamically calculated and stored in the database based on changes in the order version baseline and the response message information returned by the order business interface, reducing the reliance on caching.
This makes the order data update process easier to maintain and reduces the deep coupling between the order data update process and the business process.
Smart Images
Figure CN116340333B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of databases, and in particular to a method and apparatus for storing order data. Background Technology
[0002] In recent years, airlines have used a unified data transmission standard based on XML format messages through new distribution capability (NDC) to achieve data interaction on a unified standard. In systems built on NDC, the various transaction data stored is referred to as order data.
[0003] In existing technologies, when an order data update operation is triggered, if the information in the order business interface response message is insufficient, information is obtained from past order business interface responses to supplement the information required for the order data update, thereby realizing the acquisition and assembly of inbound data. However, when implementing order data updates using existing technologies, there is a drawback: the order data update process is difficult to maintain. Summary of the Invention
[0004] In view of this, this application provides a method and apparatus for storing order data, thereby making the order data update process easier to maintain.
[0005] The order data storage method provided in this application is implemented as follows:
[0006] Receive the first response message from the first order business interface for the first order;
[0007] Based on the first version baseline of the first order and the first response message, obtain the incremental data of the first order;
[0008] The incremental data of the first order is stored in the database.
[0009] Optionally, before receiving the first response message returned from the first order business interface, the method further includes:
[0010] Receive the second response message from the second order business interface in response to the first order;
[0011] Based on the second response message, generate the first version baseline of the first order.
[0012] Optionally, based on the second response message, generating the first version baseline of the first order includes:
[0013] The second response message is converted into a 182 version message to obtain a 182 version second response message;
[0014] Based on the second response message of version 182, generate the first version baseline of the first order.
[0015] Optionally, based on the second response message, generating the first version baseline of the first order includes:
[0016] The order processing type identifier corresponding to the second response message indicates that the second order business interface is an order creation interface, and the first version baseline of the first order is generated based on the second response message.
[0017] Optionally, after obtaining the incremental data of the first order based on the first version baseline of the first order and the first response message, the method further includes:
[0018] Add incremental data for the first order to the first version baseline to obtain the second version baseline for the first order.
[0019] Optionally, based on the second response message, a first version baseline of the first order is generated, including:
[0020] Based on the order information, air unit information, flight segment information, passenger information, and passenger flight segment information in the second response message, generate the first version baseline of the first order.
[0021] Optionally, based on the first version baseline of the first order and the first response message, the incremental data for the first order includes:
[0022] The order processing type identifier corresponding to the first response message indicates that the first order business interface is a non-order creation interface. Based on the first version baseline of the first order and the first response message, the incremental data of the first order is obtained.
[0023] Optionally, the first order business interface is an additional service purchase interface, the first response message is a response message to the additional service purchase request, and the incremental data of the first order includes at least one of the following: additional services, seat information, order number information, and payment information.
[0024] Optionally, the first order business interface is a payment and ticketing interface, the first response message is a response message to the payment and ticketing request, and the incremental data of the first order includes at least one of the following: order number information, ticket information, and price details.
[0025] This application also provides an order data storage device, including: a receiving unit, an acquiring unit, and a storage unit;
[0026] The receiving unit is used to receive the first response message from the first order business interface for the first order;
[0027] The acquisition unit is used to obtain incremental data of the first order based on the first version baseline of the first order and the first response message;
[0028] The storage unit is used to store incremental data of the first order into the database.
[0029] This application also provides a computer device, including: a processor coupled to a memory, the memory storing at least one computer program instruction, the at least one computer program instruction being loaded and executed by the processor to enable the computer device to implement a method for storing order data.
[0030] Therefore, the beneficial effects of this application are: it provides a method and apparatus for storing order data, which adopts a method of receiving a first response message from a first order business interface for a first order, obtaining incremental data of the first order based on the first version baseline of the first order and the first response message, and storing the incremental data of the first order in a database. By comparing the changes in information in the first version baseline of the first order and the first response message returned by the first order business interface, the information required for updating the order data is dynamically calculated, thereby storing the incremental data of the first order in the database to realize the update of the order data. Since the update of the order data is based on data extraction from the response message of the order business interface, the dependence on caching is reduced, and by maintaining the version baseline of the order, the deep coupling between the order data update process and the business process can be weakened, making the order data update process easier to maintain. Attached Figure Description
[0031] 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 embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.
[0032] Figure 1 This is a flowchart of the first embodiment of this application;
[0033] Figure 2 This is a flowchart of the second embodiment of this application;
[0034] Figure 3 This is a flowchart of the third embodiment of this application;
[0035] Figure 4 This is a flowchart of the fourth embodiment of this application;
[0036] Figure 5 This is a schematic diagram of an apparatus according to this application;
[0037] Figure 6 This is a schematic diagram of a computer device according to this application. Detailed Implementation
[0038] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.
[0039] The inventors discovered that when updating order data using existing technologies, each order business interface needs to know what data to store in the cache when it is called for order data updates. Conversely, the interface triggering the order update also needs to know what data to retrieve from the cache. This results in deep coupling between the order data update process and the business process, making order data updates difficult to maintain. This application addresses this by introducing an order version baseline. Based on the order version baseline and changes in the response messages returned by the order business interfaces, incremental order data is obtained, thus enabling dynamic calculation of the information required for order data updates.
[0040] In this embodiment of the application, the device for storing order data may include, but is not limited to, a computer device, which may be provided as an order business platform, such as the Tianyi interface platform.
[0041] A computer device may include: a processor coupled to a memory, the memory storing at least one computer program instruction, the at least one computer program instruction being loaded and executed by the processor to enable the computer device to implement a method for storing order data.
[0042] Please see Figure 1 The specific steps of the first embodiment of this application are as follows:
[0043] S101: The computer receives the first response message for the first order from the first order business interface.
[0044] The order service interface refers to the interface used to invoke order services. The order service interface can be an NDC interface. The primary order service interface can be a payment and ticketing interface, an add-on service purchase interface, a ticket change interface, a ticket refund interface, or an order separation interface. The primary order service interface can also be other order service interfaces defined according to actual needs.
[0045] The response message is a response message to the order business interface call request. It can be an NDC message. The first response message can be a response message to the payment and ticketing interface call request, or a response message to the additional service purchase interface call request. The first response message can also be other response messages set according to actual needs.
[0046] In some implementations, the computer receives a second response message from the second order business interface for the first order in advance, and generates a first version baseline of the first order based on the second response message.
[0047] S102: The computer obtains the incremental data of the first order based on the first version baseline of the first order and the first response message.
[0048] In some implementations, the computer responds to the order processing type identifier corresponding to the first response message, indicating that the first order business interface is a non-order creation interface, and obtains the incremental data of the first order based on the first version baseline of the first order and the first response message.
[0049] In some other implementations, the computer obtains the incremental data of the first order based on the first version baseline of the first order and the first response message, and then adds the incremental data of the first order to the first version baseline to obtain the second version baseline of the first order.
[0050] S103: The computer stores the incremental data of the first order into the database.
[0051] In the first embodiment of this application, by comparing the changes in information in the first version baseline of the first order and the first response message returned by the first order business interface, the information required for order data update is dynamically calculated, thereby decoupling the deep coupling between the order data update process and the business process and making the order data update process easier to maintain.
[0052] The second embodiment further illustrates the implementation of this application in conjunction with the generation of the first version baseline of the first order.
[0053] Please see Figure 2 The specific steps of the second embodiment of this application are as follows:
[0054] S201: The computer receives a second response message from the second order service interface in response to the first order.
[0055] The second order business interface can be an order creation interface, an additional service purchase interface, or other order business interfaces set according to actual needs.
[0056] S202: The computer generates the first version baseline of the first order based on the second response message.
[0057] In some implementations, the second order business interface is an order creation interface. In this case, the computer responds to the order processing type identifier corresponding to the second response message, indicating that the interface for generating the second response message is the order creation interface. Based on the second response message, the computer generates the first version baseline of the first order.
[0058] The order processing type identifier can be either previousOrderInfo (previous order returned information) or currentOrderInfo (current order returned information).
[0059] In some other implementations, the computer generates a first version baseline of the first order based on the order information, air unit information, segment information, passenger information, and passenger segment information in the second response message.
[0060] In other implementations, the computer converts the second response message into a version 182 message, resulting in a version 182 second response message. Based on this version 182 second response message, a first version baseline for the first order is generated. Since different order business interfaces may use different versions of NDC messages, converting the different versions of response messages from different order business interfaces into a unified standard message facilitates the computer's acquisition of information from the different versions of response messages.
[0061] In some implementations, the computer also generates the first order based on the second response message.
[0062] S203: The computer receives the first response message for the first order from the first order business interface.
[0063] S204: The computer obtains the incremental data of the first order based on the first version baseline of the first order and the first response message.
[0064] In some implementations, the first order business interface is an additional service purchase interface, the first response message is a response message to the additional service purchase request, and the incremental data of the first order includes at least one of the following: additional services, seat information, order number information, and payment information.
[0065] In some other implementations, the first order business interface is a payment and ticketing interface, the first response message is a response message to the payment and ticketing request, and the incremental data of the first order includes at least one of the following: order number information, ticket information, and price details.
[0066] S205: The computer adds incremental data of the first order to the first version baseline to obtain the second version baseline of the first order.
[0067] S206: The computer stores the incremental data of the first order into the database.
[0068] S205 can be executed first, followed by S206, or S206 can be executed first, followed by S205. This application does not restrict the execution order of S205 and S206.
[0069] In the second embodiment of this application, the original information of the order is provided by generating the first version baseline from the second response message, so that when the order is updated, the first version baseline and the first response message can be compared to obtain the incremental data of the first order.
[0070] The third embodiment uses the second order business interface as the order creation interface and the first order business interface as the additional service purchase interface as an example to describe the specific implementation of this application.
[0071] Please see Figure 3 The specific steps of the third embodiment of this application are as follows:
[0072] S301: The computer receives a second response message from the order creation interface for the first order.
[0073] In some implementations, the order business platform component receives a second response message (OrderViewRS) from the order creation interface (OrderCreate) for the first order.
[0074] S302: The computer converts the second response message into a version 182 message, resulting in a version 182 second response message.
[0075] In some implementations, the order business platform component converts the second response message into a 182 version message, resulting in a 182 version second response message.
[0076] In some implementations, the processor in the order business platform component generates the current order information from the second response message of version 182.
[0077] S303: The computer responds to the order processing type identifier corresponding to the second response message, indicating that the interface that generated the second response message is the order creation interface, and generates the first version baseline of the first order based on the second response message of version 182.
[0078] In some implementations, the order processing type identifier corresponding to the second response message indicates that the interface that generates the second response message is the order creation interface. The computer generates the first version baseline of the first order based on the order information, air item information, segment information, passenger information, and passenger segment information (PsgAndSeg) in the second response message of version 182.
[0079] In some implementations, the order inbound operation analyzer (OperationAnalysis) in the order component determines the type of operation for the current order inbound based on the preceding and current order return information. Since the second order business interface is the order creation interface, the preceding order return information is empty, indicating that the current inbound operation is an order creation operation. The order inbound operation analyzer generates a list of operation objects and sends it to the order data parser (IOrderRepositoryDataExtract). The order data parser parses the obtained operation objects and determines that the current inbound operation is an order creation operation. The order data parser then parses the second response message in the current order return information, extracts the order information, air unit, flight segment, passenger, and passenger-flight segment from the message to generate a created order model (OrderCreateDTO), and calls the save order method of the order persistence interface (IOrderPersistData).
[0080] The order persistence interface receives the created order model, converts the order information (order) in the created order model into an order domain object (AggOrderEO), and then calls the order repository class (IOrderRepositoryData) to save the order.
[0081] The order storage class primarily provides database operation methods, storing order domain objects in the corresponding tables in the database, and saving the information in the second response message as a version baseline for the current order.
[0082] S304: The computer receives a first response message from the Additional Services Purchase Interface for the first order.
[0083] In some implementations, the order processing platform component receives the first response message from the add-on service purchase interface (ServiceList) for the first order.
[0084] S305: The computer converts the first response message into a version 182 message, resulting in a version 182 first response message.
[0085] In some implementations, the order business platform component converts the first response message into a 182 version message to obtain the 182 version first response message.
[0086] In some other implementations, the processor in the order business platform component generates the current order information (currentOrderInfo) from the first response message of version 182, retrieves the first version baseline (previousOrderInfo) of the first order from the database, and then sends it to the order component.
[0087] S306: The computer obtains the incremental data of the first order based on the first version baseline of the first order and the first response message of version 182.
[0088] In this embodiment, the incremental data of the first order includes at least one of the following: additional service or seat information (ServiceListAndSeat), order number information (orderId), and payment information (Payment).
[0089] In some implementations, the order component receives a request from the processor. The order entry operation analyzer in the order component, based on the previous returned order information (which is the first version baseline) and the current returned order information, compares the first version baseline with the first response message. It can be seen that the ServiceDefinitionList node (a list of service definition data nodes) in the DataLists node (the root node of all data in the response entity of the first response message) in the first response message will have a description of the additional service added. If a seat is purchased, the DataLists node will have a SeatProfileList node (a list of seat configuration data definition). The Order node (a list of order information generated in the order management system and the price of the order business) will have an OrderItem node (detailed items of the order) with the relevant additional service added. The TicketDocInfo node (information corresponding to one to four single-segment and single-passenger tickets) will have ticketing information for the relevant additional service added. Thus, it can be determined that the current entry operation is to purchase an additional service.
[0090] The order entry operation analyzer in the order component generates a list of operation objects and sends it to the order data parser. The order data parser parses the first response message in the current order information, extracts the order number, additional service or seat information, and payment information from the message to generate a purchase additional service model (OrderServiceDTO), and calls the purchase additional service method of the order persistence interface.
[0091] The order persistence interface receives the purchase additional service model, transforms the order information in the purchase additional service model into an order domain object, and then calls the order warehouse class to update the order.
[0092] S307: The computer adds incremental data of the first order to the first version baseline to obtain the second version baseline of the first order.
[0093] In some implementations, the order storage class adds incremental data of the first order to the first version baseline to obtain the second version baseline of the first order.
[0094] S308: The computer stores the incremental data of the first order into the database.
[0095] In some implementations, the order storage class stores the incremental data of the first order in the database.
[0096] In the third embodiment of this application, the version baseline is updated by adding the incremental data of the first order to the original version baseline, so that it can be compared with the updated version baseline when performing subsequent order operations.
[0097] The fourth embodiment uses the first order business interface as a payment and ticketing interface as an example to describe the specific implementation of this application.
[0098] Please see Figure 4 The specific steps of the fourth embodiment of this application are as follows:
[0099] S401: The computer receives the first response message from the payment and ticketing interface for the first order.
[0100] In some implementations, the order business platform component receives the first response message for the first order from the payment ticketing interface (OrderChange).
[0101] S402: The computer converts the first response message into a version 182 message, resulting in a version 182 first response message.
[0102] In some implementations, the order business platform component converts the first response message into a 182 version message to obtain the 182 version first response message.
[0103] In some other implementations, the processor in the order business platform component generates the current returned order information from the first response message of version 182, retrieves the first version baseline of the first order from the database (the first version baseline is generated based on the response message of the previous interface of the payment and ticketing interface), and then sends it to the order component.
[0104] S403: The computer obtains the incremental data of the first order based on the first version baseline of the first order and the first response message of version 182.
[0105] In this embodiment, the incremental data of the first order includes at least one of the following: order number information (orderId), ticket information (Ticket), and price details (PriceDetail).
[0106] In some implementations, the order component receives requests from the processor in the order business platform component. The order inbound operation analyzer in the order component, based on the preceding returned order information (generated from the response message of the previous interface of the payment / ticketing interface) and the currently returned order information, compares the first version baseline and the first response message. It can be determined that a new TicketDocInfo node has been added to the first response message, thus identifying the current inbound operation as payment / ticketing. The order inbound operation analyzer in the order component generates a list of operation objects and sends it to the order data parser. The order data parser parses the first response message in the currently returned order information, extracts the order number, ticket information, and price details to generate the order payment model (OrderPayDTO), and calls the payment method of the order persistence interface.
[0107] The order persistence interface receives the order payment model, converts the order information in the order payment model into an order domain object, and then calls the order storage class to update the order.
[0108] In some implementations, if the first order service interface is a rebooking interface, by comparing the response message of the previous interface, it can be seen that the flight segment in the PaxSegmentList node (the flight segment data list definition) of the Datalists node in the first response message will change, and the flight segment ID and price associated with the OrderItem in the Order node will change. If a new TicketDocTypeCode node (ticket type) with a TicketDocInfo node of T is added to the first response message, it indicates a ticket change; if no new TicketDocTypeCode node with a TicketDocInfo node of T is added to the first response message, it indicates a rebooking of the same ticket.
[0109] In some other implementations, if the first order business interface is a ticket refund interface, the computer extracts the refunded order number from the first response message (OrderCancelRS) and updates the order in the database.
[0110] In some other implementations, if the first order business interface is an order separation interface, the computer parses the response message of the payment and ticketing interface and updates the order in the database.
[0111] S404: The computer adds incremental data of the first order to the first version baseline to obtain the second version baseline of the first order.
[0112] S405: The computer stores the incremental data of the first order into the database.
[0113] In the fourth embodiment of this application, by dividing the order entry operation into multiple atomic operations (such as the payment and ticketing operation in this embodiment and the operation performed by the previous interface of the payment and ticketing interface), multiple atomic operations can form a variety of different scenarios, making the storage of order data more flexible and convenient.
[0114] Please see Figure 5 This application provides an order data storage device 500, including: a receiving unit 501, an acquiring unit 502 and a storage unit 503.
[0115] Receiving unit 501: Used to receive the first response message for the first order from the first order business interface.
[0116] Optionally, receiving unit 501 is further configured to receive a second response message from the second order service interface for the first order.
[0117] Acquisition unit 502: used to obtain incremental data of the first order based on the first version baseline of the first order and the first response message.
[0118] Optionally, the acquisition unit 502 is further configured to, in response to the order processing type identifier corresponding to the first response message indicating that the first order business interface is a non-order creation interface, obtain the incremental data of the first order based on the first version baseline of the first order and the first response message.
[0119] Storage unit 503: Used to store incremental data of the first order into the database.
[0120] Optionally, an order data storage device 500 further includes: a generation unit 504, a conversion unit 505, and an addition unit 506.
[0121] Generation unit 504: Used to generate the first version baseline of the first order based on the second response message.
[0122] Optionally, generation unit 504 is further configured to generate a first version baseline of the first order based on the second response message of version 182.
[0123] Optionally, generation unit 504 is further configured to respond to the order processing type identifier corresponding to the second response message indicating that the second order business interface is an order creation interface, and generate the first version baseline of the first order according to the second response message.
[0124] Optionally, generation unit 504 is further configured to generate a first version baseline of the first order based on the order information, air unit information, flight segment information, passenger information and passenger flight segment information in the second response message.
[0125] Conversion unit 505: Used to convert the second response message into a 182 version message to obtain a 182 version second response message.
[0126] Add Unit 506: Used to add incremental data of the first order to the first version baseline to obtain the second version baseline of the first order.
[0127] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.
[0128] It should be noted that the order data storage device provided in the above embodiments is only illustrated by the division of the above functional modules when implementing the order data storage function. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of an order data storage device can be divided into different functional modules to complete all or part of the functions described above. In addition, the order data storage device and the order data storage method embodiment provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiment, which will not be repeated here.
[0129] Figure 6 This is a schematic diagram of the structure of a computer device 600 provided in an embodiment of this application.
[0130] Computer device 600 includes at least one processor 601, memory 602 and at least one network interface 603.
[0131] Processor 601 may be, for example, a general-purpose central processing unit (CPU), a network processor (NP), a graphics processing unit (GPU), a neural-network processing unit (NPU), a data processing unit (DPU), a microprocessor, or one or more integrated circuits for implementing the embodiments of this application. For example, processor 601 may include an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. A PLD may be, for example, a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.
[0132] Memory 602 may be, for example, read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions; random access memory (RAM) or other types of dynamic storage devices capable of storing information and instructions; electrically erasable programmable read-only memory (EEPROM); compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed discs, laser discs, optical discs, digital universal discs, Blu-ray discs, etc.); magnetic disk storage media or other magnetic storage devices; or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. Optionally, memory 602 exists independently and is connected to processor 601 via internal connection 604. Alternatively, memory 602 and processor 601 may be integrated together.
[0133] Network interface 603 uses any transceiver-like device for communicating with other devices or communication networks. Network interface 603 includes, for example, at least one of a wired network interface or a wireless network interface. The wired network interface is, for example, an Ethernet interface. The Ethernet interface is, for example, an optical interface, an electrical interface, or a combination thereof. The wireless network interface is, for example, a wireless local area network (WLAN) interface, a cellular network interface, or a combination thereof.
[0134] In some embodiments, processor 601 includes one or more CPUs, such as Figure 6 CPU0 and CPU1 are shown in the diagram.
[0135] In some embodiments, the computer device 600 may optionally include a plurality of processors, such as Figure 6 The processors 601 and 605 are shown. Each of these processors is, for example, a single-core processor (CPU) or a multi-core processor (CPU). A processor here may optionally refer to one or more devices, circuits, and / or processing cores used to process data (such as computer program instructions).
[0136] In some embodiments, the computer device 600 further includes an internal connection 604. The processor 601, memory 602, and at least one network interface 603 are connected via the internal connection 604. The internal connection 604 includes pathways for transmitting information between the aforementioned components. Optionally, the internal connection 604 is a single board or a bus. Optionally, the internal connection 604 may be divided into an address bus, a data bus, a control bus, etc.
[0137] In some embodiments, the computer device 600 further includes an input / output interface 606. The input / output interface 606 is connected to an internal connection 604.
[0138] In some embodiments, the input / output interface 606 is used to connect to an input device to receive commands or data input by a user through the input device, as described in the above embodiments. Input devices include, but are not limited to, keyboards, touchscreens, microphones, mice, or sensing devices, etc.
[0139] In some embodiments, the input / output interface 606 is also used to connect to an output device. The input / output interface 606 outputs intermediate and / or final results generated by the processor 601 executing the above method embodiments through the output device. The output device includes, but is not limited to, a display, printer, projector, etc.
[0140] Optionally, the processor 601 implements the method in the above embodiments by reading program code stored in the memory 602, or the processor 601 implements the method in the above embodiments by internally stored program code. When the processor 601 implements the method in the above embodiments by reading program code stored in the memory 602, the memory 602 stores program code 610 that implements the method provided in the embodiments of this application.
[0141] For more details on how processor 601 implements the above functions, please refer to the descriptions in the previous method embodiments, which will not be repeated here.
[0142] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only 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.
[0143] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A method for storing order data, characterized in that, The method includes: Receive the first response message from the first order business interface for the first order; Before receiving the first response message returned from the first order service interface, the method further includes: receiving a second response message from the second order service interface for the first order; responding to the order processing type identifier corresponding to the second response message indicating that the second order service interface is an order creation interface, generating a first version baseline of the first order based on the second response message; wherein the order processing type identifier is the pre-returned order information and the currently returned order information; In response to the order processing type identifier corresponding to the first response message indicating that the first order business interface is a non-order creation interface, the incremental data of the first order is obtained based on the first version baseline of the first order and the first response message. The incremental data of the first order is stored in the database.
2. The method according to claim 1, characterized in that, The step of generating the first version baseline of the first order based on the second response message includes: The second response message is converted into a 182 version message to obtain a 182 version second response message; Based on the second response message of version 182, the first version baseline of the first order is generated.
3. The method according to claim 1, characterized in that, After obtaining the incremental data of the first order based on the first version baseline of the first order and the first response message, the method further includes: Add the incremental data of the first order to the first version baseline to obtain the second version baseline of the first order.
4. The method according to claim 1, characterized in that, The step of generating the first version baseline of the first order based on the second response message includes: Based on the order information, air unit information, flight segment information, passenger information, and passenger flight segment information in the second response message, a first version baseline of the first order is generated.
5. The method according to claim 1, characterized in that, The first order business interface is an additional service purchase interface, the first response message is a response message to the additional service purchase request, and the incremental data of the first order includes at least one of the following: additional services, seat information, order number information, and payment information.
6. The method according to claim 1, characterized in that, The first order business interface is a payment and ticketing interface, the first response message is a response message to the payment and ticketing request, and the incremental data of the first order includes at least one of the following: order number information, ticket information, and price details.
7. A storage device for order data, characterized in that, The device includes: a receiving unit, an acquiring unit, and a storage unit; The receiving unit is used to receive a first response message from the first order service interface for the first order; The acquisition unit is used to obtain incremental data of the first order based on the first version baseline of the first order and the first response message; The storage unit is used to store the incremental data of the first order into the database; The receiving unit is further configured to receive a second response message from the second order service interface for the first order; The generation unit is configured to, in response to the order processing type identifier corresponding to the second response message indicating that the second order business interface is an order creation interface, generate a first version baseline of the first order based on the second response message; the order processing type identifier is the information after the previous order was returned and the information after the current order was returned; The acquisition unit is specifically used to obtain incremental data of the first order in response to the order processing type identifier corresponding to the first response message indicating that the first order business interface is a non-order creation interface, based on the first version baseline of the first order and the first response message.
8. A computer device, characterized in that, The computer device includes: a processor coupled to a memory, the memory storing at least one computer program instruction, the at least one computer program instruction being loaded and executed by the processor to enable the computer device to implement the method of any one of claims 1-6.