CN111324612A - Storage method, system, device, equipment and storage medium of order information - Google Patents
Storage method, system, device, equipment and storage medium of order information Download PDFInfo
- Publication number
- CN111324612A CN111324612A CN202010131425.1A CN202010131425A CN111324612A CN 111324612 A CN111324612 A CN 111324612A CN 202010131425 A CN202010131425 A CN 202010131425A CN 111324612 A CN111324612 A CN 111324612A
- Authority
- CN
- China
- Prior art keywords
- order
- information
- request message
- interface
- response message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
- G06Q30/0635—Processing of requisition or of purchase orders
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
- G06Q50/14—Travel agencies
Abstract
The application discloses a storage method, a storage system, a storage device, storage equipment and a storage medium of order information, and belongs to the field of computers. The method comprises the following steps: sending an order request message to the background system through an order interface, wherein the order request message is used for acquiring order information of a full order of a specified merchant in a specified time period, the order interface is suitable for information interaction between the uniform reservation equipment and at least two different background systems, and the order interface is an interface provided by the background systems; receiving an order response message sent by a background system, wherein the order response message comprises order information; and storing the order information in the order response message into a database. The method and the system have the advantages that the order information conforming to the order interface format can be deposited into the database from the background system of the system provider no matter how many system providers exist or whether the system providers are replaced or not, the order information is analyzed and used by the scenic spot workers, and the data utilization rate and the anti-risk performance of the data center of the scenic spot are improved.
Description
Technical Field
The present application relates to the field of computers, and in particular, to a method, a system, an apparatus, a device, and a storage medium for storing order information.
Background
Scenic spots are regional locations where travel and related activities are the primary function or one of the primary functions. A ticket selling system and a ticket checking system based on a computer are arranged in the scenic spot, and the ticket selling and checking system is called the ticket selling and checking system for short.
In the related art, ticket vending systems used in scenic spots are provided by system providers. The system manufacturer produces and manufactures a selling and checking system, a ticketing system is arranged at a ticket selling point of a scenic spot, the ticket checking system is arranged at an entrance and an exit of the scenic spot, and a data center is arranged for the scenic spot. The data center stores the order information for ticketing.
Because the data storage capacities provided by different system providers are not consistent, if the scenic spot switches the old system provider a to the new system provider B, the order information generated by the old system provider a cannot be used any more.
Disclosure of Invention
The embodiment of the application provides a method, a system, a device, equipment and a storage medium for storing order information, which can store the order information received by adopting a unified interface into a database, and can ensure normal use of the order information by a scenic spot worker no matter whether a system merchant is replaced or not. The technical scheme is as follows:
according to one aspect of the application, a method for storing order information is provided, and the method is applied to a unified booking device, wherein the unified booking device is a device located between a ticket sale and check system and a background system, and the method comprises the following steps:
sending an order request message to the background system through an order interface, wherein the order request message is used for acquiring order information of a full order of a specified merchant in a specified time period, the order interface is suitable for information interaction between the unified reservation equipment and at least two different background systems, and the order interface is an interface provided by the background systems;
receiving an order response message sent by the background system, wherein the order response message comprises the order information;
and storing the order information in the order response message into a database.
According to another aspect of the present application, there is provided a method for storing order information, the method being applied to a backend system, the method including:
receiving an order request message sent by a unified booking device through an order interface, wherein the order request message is used for acquiring order information of a full order of a designated merchant in a designated time period, the order interface is suitable for information interaction between the unified booking device and at least two different background systems, the order interface is an interface provided by the background systems, and the unified booking device is a device positioned between a ticket selling and checking system and the background systems;
generating an order response message according to the order request message, wherein the order response message comprises the order information;
and sending the order response message to the unified booking equipment.
According to another aspect of the present application, there is provided a storage system of order information, the system including: the system comprises a uniform booking device and a database, wherein the uniform booking device is a device positioned between a ticket selling and checking system and a background system;
the unified booking device is used for executing the order information storage method executed by the unified booking device so as to store the order information of the full-scale order in the database;
and the database is used for storing the order information of the full order.
According to another aspect of the present application, there is provided an apparatus for storing order information, the apparatus being located between a ticket sales and inspection system and a back office system, the apparatus comprising:
the order interface is suitable for information interaction between the unified booking device and at least two different background systems, and the order interface is an interface provided by the background systems;
the first receiving module is used for receiving an order response message sent by the background system, wherein the order response message comprises the order information;
and the storage module is used for storing the order information in the order response message into a database.
According to another aspect of the present application, there is provided an order information storage apparatus, the apparatus including:
the second receiving module is used for receiving an order request message sent by the unified booking device through an order interface, wherein the order request message is used for acquiring order information of a full order of a specified merchant in a specified time period, the order interface is suitable for information interaction between the unified booking device and at least two different background systems, the order interface is provided by the background systems, and the unified booking device is a device located between the ticket selling and checking system and the background systems;
a second generating module, configured to generate an order response message according to the order request message, where the order response message includes the order information;
and the second sending module is used for sending the order response message to the unified booking device.
According to another aspect of the present application, there is provided a computer device comprising: a processor and a memory storing a computer program that is loaded and executed by the processor to implement the method of storing order information performed by a unified reservation apparatus as described above.
According to another aspect of the present application, there is provided a computer-readable storage medium having stored therein a computer program, which is loaded and executed by a processor to implement the method of storing order information performed by a unified reservation apparatus as described above.
According to another aspect of the present application, there is provided a computer device comprising: a processor and a memory, the memory storing a computer program that is loaded and executed by the processor to implement the method of storing order information performed by a backend system as described above.
According to another aspect of the present application, there is provided a computer-readable storage medium having stored therein a computer program, which is loaded and executed by a processor to implement the method for storing order information performed by a backend system as described above.
The beneficial effects brought by the technical scheme provided by the embodiment of the application at least comprise:
the unified reservation equipment sends the order request message to the background system through the order interface and receives the order response message returned by the background system, the order response message comprises order information, the unified reservation equipment stores the order information into the database, the background system of the system business can send the order information to the unified reservation equipment through the order interface to be stored no matter how many system businesses exist or whether the system businesses are replaced, the order information conforming to the format of the order interface is deposited in the database to be analyzed and used by workers in a scenic spot, and the data utilization rate and the wind risk resistance of a data center of the scenic spot are improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 illustrates a block diagram of a computer system provided in an exemplary embodiment of the present application;
FIG. 2 illustrates a flow chart of a method for storing order information provided by an exemplary embodiment of the present application;
FIG. 3 illustrates a flow chart of a method for storing order information provided by another exemplary embodiment of the present application;
FIG. 4 illustrates a flow chart of a method for storing order information provided by another exemplary embodiment of the present application;
FIG. 5 is a schematic diagram of a storage system for order information provided by another exemplary embodiment of the present application;
FIG. 6 is a schematic illustration of a storage device for order information provided by another exemplary embodiment of the present application;
FIG. 7 is a schematic illustration of a storage device for order information provided by another exemplary embodiment of the present application;
fig. 8 is a schematic structural diagram of a computer device according to an exemplary embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
Reference will first be made to several terms referred to in this application:
scenic spot: is a regional location with travel and related activities as the primary function or one of the primary functions.
And (4) channel: is a sale channel for selling tickets in scenic spots. The channels are divided according to types and comprise: at least one of a cash window channel, an official website channel, an official mobile internet portal channel (such as WeChat), a travel agency channel, a special team channel, an OTA (Online travel agency), an online store, or other channel. The same scenic spot can have a plurality of channels, and the same merchant can also have a plurality of channels.
And (4) system quotient: and the service provider is used for providing background services for the ticket selling and checking system in the scenic spot. Alternatively, the front end and hardware devices in the ticket system may be provided to the scenic spot by the system vendor.
Ticket data: data generated in the process of ticket selling and ticket checking of the entrance tickets in the scenic spot. The ticket data includes: at least one of user data, order information, product data, and channel data.
User data: among the ticket data, data relating to registration, login, and management of a user account.
Order information; in the ticket data, data related to placing, verifying, and changing of an order for a ticket is recorded.
Product data: in the ticket data, data related to the shelving, and stocking of ticket products are stored.
Channel data: in the ticket data, data related to a selling channel of the entrance ticket.
The unified reservation equipment: is a new added device between the ticket sale and check system and the background system in the application. The method and the device are used for realizing message forwarding between the ticket selling and checking system and the background system and unifying message formats. And the uniform booking device is also used for additionally backing up the ticket business data in the background system for the scenic spot in the database.
FIG. 1 illustrates a block diagram of a computer system 100 provided in an exemplary embodiment of the present application. The computer system 100 includes: a ticketing system 120, a unified reservation device 140, a back office system 160, and a database 180.
The ticketing system 120 is a software system that can be deployed in each scene and in various channels. Taking scenic spot 1 as an example, after the ticket vending and checking system 120 is deployed, one or more channels of ticket vending services are provided. Illustratively, the channel includes: at least one of a cash window, an official website, an official wechat post number (a mobile internet portal), a travel agency, a special team, OTA (online travel agency), or other channel. The special team comprises: student team, elderly team, teacher team, etc.
The unified booking device 140 is used to provide a unified form of standardized interface, referred to as a unified interface, to the ticketing system 120 and the backend system 160. The unified interface is used for receiving and sending messages with the ticket selling and checking system 120, and/or the unified interface is used for receiving and sending messages with the background system 160. Illustratively, the unified interface includes: a product change interface, an order correlation interface, a scenic spot channel setting interface, a scenic spot self-operation user interface and the like.
Optionally, the unified reservation device 140 is further configured for routing forwarding messages between the scenic spot and the backend system 160, and routing forwarding messages between the channel and the backend system. Illustratively, the unified routing rule includes: routing rules between scenic spots and background systems, and routing rules between scenic spots and selling channels.
The back office system 160 refers to a computer system provided by the system vendor of the ticketing system. The back office system 160 provides ticketing services to the scenic spot via the ticketing system 120. There may be more than one backend system 160. Each scenic spot is bound to at least one backend system 160.
The database 180 is used to store ticketing data for the scenic spot 120. Wherein the ticket data includes: at least one of user data, order information, product data, and channel data. The database 180 is a database that the unified reservation device 140 sets for the scenic spot 120. Optionally, each scenic spot 120 corresponds to a respective database.
Illustratively, the scenic spot corresponds to a first organizational structure (e.g., government), the unified subscription device 140 corresponds to a second organizational structure (e.g., OTA platform vendor), and the backend system 160 corresponds to a third organizational structure (e.g., system vendor). Wherein the ticketing system 120 and the uniform reservation device 140 are provided by a second organizational structure.
In one possible design, the ticketing system 120 sends the first message, which is forwarded by the unified reservation device 140 to the backend system 160. After the background system 160 feeds back the response message of the first message, the unified booking device 140 forwards the response message to the fare collection system 120. The first message or the ticket data in the response message is stored by the unified subscription device 140 in the database 180.
In another possible design, the second message is pushed to the unified reservation device 140 by the backend system 160, and the unified reservation device 140 stores the ticket data in the second message in the database 180.
In the present system, the ticketing system 120 comprises the front end of the ticketing system. The front end of the ticket sale and check system can be the front end provided by the first group of weaving mechanisms, the front end provided by the second group of weaving mechanisms and the front end provided by the third group of weaving mechanisms.
In another embodiment, the ticketing system 120 can be designed as a cloud service running in the background system 160, and various scenic spots or channels can access the ticketing system 120 through a browser (or a built-in browser of an application).
In the present system, the unified reservation device 140 and the back office system 160 form the back end of the ticketing system 120.
It should be noted that the scenic spots may be multiple, and each scenic spot corresponds to its own ticket selling and checking system. Each scenic spot also corresponds to a system quotient. For the same scenic spot, the facilitator of the scenic spot may also switch from the facilitator 1 to the facilitator 2. At this time, the background system of the ticket sale and check system is also switched from the background system 1 to the background system 2.
Another point to be noted is that the unified booking device 140 has a route forwarding function due to the presence of the ticketing system 120 of multiple scenic spots and/or the backend systems 160 of multiple system merchants. However, in some embodiments, such as when there is only one ticketing system 120 and one back-office system 160, the unified routing device 144 may not be provided.
It should be noted that the background system 160 stores a copy of the original ticketing data, and the database shown in fig. 1 is used for storing backup ticketing data for use in the scenic spot. Since the backup ticket data is a backup of the original ticket data, ideally, the backup ticket data is identical to the original ticket data, or the contents are identical and only the data format is different.
Illustratively, in the order information storage method, a system dealer establishes a ticket sale and check system for each scenic spot, and the system is deployed on a scenic spot server. For example, the scenic spot 1 is deployed on a server of the scenic spot 1 through a ticket sale and check system established by the system provider 1, the scenic spot 2 is deployed on a server of the scenic spot 2 through a ticket sale and check system established by the system provider 1, and the scenic spot 3 is deployed on a server of the scenic spot 3 through a ticket sale and check system established by the system provider 2. In another storage method of order information, a ticket selling and checking system established by a system dealer for each scenic spot is deployed on a cloud server. For example, the scenic spot 1 is deployed on the cloud server 1 through a ticket sale and check system established by the system provider 1, the scenic spot 2 is also deployed on the cloud server 1 through a ticket sale and check system established by the system provider 1, and the scenic spot 3 is deployed on the cloud server 2 through a ticket sale and check system established by the system provider 2.
According to the two storage methods of the order information, if the scenic spot wants to replace the system merchant, different system merchants have different schemes for designing the ticket selling and checking system and different data storage formats, so that the data migration cost is very high, and the historical order data is very easy to lose.
Fig. 2 is a flowchart illustrating a method for storing order information according to an exemplary embodiment of the present application. The present embodiment is illustrated with the method applied to the unified reservation apparatus 140 and the backend system 160 shown in fig. 1. The method comprises the following steps:
204, the unified booking device sends an order request message to a background system through an order interface, wherein the order request message is used for acquiring order information of a full order of a specified merchant in a specified time period, the order interface is suitable for information interaction between the unified booking device and at least two different background systems, and the order interface is an interface provided by the background systems;
the unified booking device is a device located between the ticketing system and the back office system.
The order interface is a program interface between the unified reservation device and the backend system. The order interface is a program interface provided by the unified booking device to the backend system, and/or the order interface is a program interface provided by the backend system to the unified booking device.
Illustratively, the order interface has a uniform message format requirement, and the order request message is a message meeting the message format requirement of the order interface. Illustratively, the unified booking device generates an order request message according to the message format requirement of the order interface, wherein the order request message includes the requested content.
Illustratively, the order interface is provided by the unified reservation device for use by at least two backend systems. That is, the message format requirements, the message templates, and the like of the order interface are set by the unified booking device, and the background system receives, identifies, and processes the message sent by the unified booking device through the request interface by using the set order interface, or sends the message to the unified booking device according to the set order interface.
Illustratively, the order information includes at least one of order basic information, order consumer information, order coupon code information, reimbursement running information, and re-signing running information. Illustratively, each type of order information corresponds to a plurality of parameter fields in the order response message, and the specific parameter fields are described in detail in the following description of the order interface.
A full order refers to all orders by the merchant over a period of time. By way of example, a merchant may refer to a scenic spot, a company, a storefront, and the like. Or, a merchant refers to a virtual shop of a certain merchant on a certain selling channel, for example, a virtual shop a established by the merchant a on a third party selling platform.
Illustratively, the order request message includes the following information to be requested: the merchant identification, the designated time period, the order quantity, the order type, the order processing state, the order verification state and the order generation channel. For example, the request message is used to request that merchant a generates order information of an order that has been checked and sold from 7/22 th to 7/28 th through a first channel.
Illustratively, the order request message is actively sent to the background system when the unified reservation device needs to request order information. For example, the order request message may be sent by the unified reservation device to the backend system periodically, or may be sent by the unified reservation device to the backend system when the sending condition is satisfied. The sending condition may be any, for example, when the unified booking device detects that order information of a certain merchant on a certain day is missing, the unified booking device sends an order request message to the background system, or when the unified booking device receives a newly generated order, the unified booking device sends an order request message to the background system, or when the unified booking device receives an instruction that the background system needs to be replaced in a scenic spot, the unified booking device sends an order request message to the background system.
Step 205, the background system receives an order request message sent by the unified booking device through an order interface, wherein the order request message is used for acquiring order information of a full order of a specified merchant in a specified time period, the order interface is suitable for information interaction between the unified booking device and at least two different background systems, and the order interface is an interface provided by the background systems;
and step 206, the background system generates an order response message according to the order request message, wherein the order response message comprises order information.
Illustratively, the background system generates a corresponding order response message according to the specific request content in the order request message, where the order response message includes order information requested by the unified booking device.
Illustratively, the order response message is generated by the background system according to the message format requirement of the order interface.
Step 207, the background system sends an order response message to the uniform booking device.
And step 208, the unified booking device receives an order response message sent by the background system, wherein the order response message comprises order information.
Step 209, store the order information in the order response message in the database.
Illustratively, the unified reservation equipment stores the order information in the order response message into the database according to a unified format.
In summary, in the method provided in this embodiment, the unified reservation device sends the order request message to the background system through the order interface, and receives the order response message returned by the background system, where the order response message includes the order information, and the unified reservation device stores the order information in the database, so that no matter how many system providers are, and no matter whether the system providers are replaced, the background system of the system provider can send the order information to the unified reservation device through the order interface for storage, and further deposit the order information conforming to the format of the order interface in the database for analysis and use by the scenic spot workers, thereby improving the data utilization rate and the wind risk resistance of the data center of the scenic spot itself.
Fig. 3 is a flowchart illustrating a method for storing order information according to an exemplary embodiment of the present application. The present embodiment is illustrated with the method applied to the unified reservation apparatus 140 and the backend system 160 shown in fig. 1. On the basis of the exemplary embodiment shown in fig. 2, step 204 further includes step 201 to step 203, step 204 includes step 2041, step 206 includes step 2061 to step 2064, and step 209 includes step 2091 to step 2092.
Step 201, the unified booking device obtains a request message template of an order request message, and a template type field of the request message template is an order information request field.
Illustratively, the order request message sent through the order interface has a uniform request message template, and when the uniform reservation equipment needs to send the order request message to the background system, the request message template is obtained. Illustratively, the request message template includes a plurality of parameter fields, wherein the template type field is an order information request field. Illustratively, the order information request field is named "orderinrequest". For example, other parameter fields in the request message template are described in detail in the following detailed description of the order interface.
Step 202, the unified reservation equipment obtains at least one parameter content required by the request message template.
Illustratively, the unified booking device fills in the request message template according to the content required by the request to generate the order request message. Illustratively, the request message template has parameter contents to be filled in, and the parameter contents include: and acquiring at least one of a merchant Identifier (ID), an order channel, the number of each page, the number of pages, a start date and an end date required by the request message template. For example, the unified booking device obtains a merchant identification ID "001" of an order to be queried, an order channel "first channel", the number of pages per "10", the number of pages "5", a start date "2019-10-01", and an end date "2019-11-01". That is, 10 pieces of order information from 10/1/2019 to 11/1/2019 by the 001 dealer through the first channel are acquired.
Step 203, the unified booking device generates an order request message according to the request message template and at least one parameter content.
Illustratively, the unified booking device fills the specific parameter content into the request message template to generate the order request message. For example, the list request message is described in detail below with respect to the order interface.
Step 2041, the unified booking device sends an order request message to the background system through the order interface in a POST mode.
Illustratively, when the backend system includes a first backend system and a second backend system, the first backend system corresponds to a first URL (Uniform Resource Locator), and the second backend system corresponds to a second URL;
in response to the order request message sent to the first background system, the unified booking device calls an order interface to send the POST type order request message to the first background system indicated by the first URL;
and in response to sending the order request message to the second background system, the unified booking device calls an order interface to send the POST type order request message to the second background system indicated by the second URL.
In step 2061, the background system identifies the template type field of the order request message.
Illustratively, the order request message is sent by the uniform reservation equipment to a background system indicated by the uniform resource locator URL by calling an order interface in a POST manner.
Step 2062, the background system responds to the template type field as the order information request field, obtains a response message template of the order response message corresponding to the order request message, and the template type field of the response message template is the order information response field.
Illustratively, when the template type field is the order information request field "orderinformatest", the corresponding response message template is obtained. Illustratively, the response message template includes a plurality of parameter fields, wherein the template type field is an order information response field. Illustratively, the order information response field is named "orderinforesponse". For example, other parameter fields in the response message template are described in detail in the following detailed description of the order interface.
Step 2063, the background system obtains at least one order information required by the order request message.
Illustratively, the background system acquires parameter content in the order request message, wherein the parameter content comprises at least one of merchant Identification (ID), order channel, number of pages, start date and end date; and acquiring at least one order information according to the parameter content, wherein the order information comprises at least one of order basic information, order consumer information, order coupon code information, verification and marketing flow information, refund flow information and re-signing flow information.
For example, the parameter contents in the order acquisition request are a merchant identification ID "001", an order channel "first channel", the number per page "10", the number of pages "5", a start date "2019-10-01", and an end date "2019-11-01". The background system acquires 50 orders from the 10 th month 1 st year in 2019 to the 11 th month 1 st year in 2019 from the 001 merchant through a first channel, and acquires at least one of order basic information, order consumer information, order coupon code information, reimbursement running information and re-signing running information of the 50 orders.
Step 2064, the background system generates an order response message according to the response message template and the order information.
Step 2091, the unified subscription device identifies the template type field of the order response message.
Step 2092, when the unified reservation device responds that the template type field is the order information response field, storing the order information in the order response message in the database.
Illustratively, when the template type field of the order response message is the order information response field "orderinforesponse", the unified booking device determines that the message is the order response message, extracts the order information in the message according to the processing mode of the order response message, and stores the order information in the database.
In summary, the method provided in this embodiment generates the order response message and the order request message according to the response message template and the request message template, so that information interaction between the unified reservation device and the background system conforms to the unified rule of the order interface, and further stores the order information of the background system in the database. The background system of the system provider can send the order information to the unified booking equipment through the order interface to be stored no matter how many system providers exist or whether the system providers are replaced or not, and further deposit the order information conforming to the order interface format in the database for the analysis and use of the scenic spot workers, so that the data utilization rate and the anti-risk performance of the data center of the scenic spot are improved.
Fig. 4 is a flowchart illustrating a method for storing order information according to an exemplary embodiment of the present application. The present embodiment is illustrated with the method applied to the unified reservation apparatus 140 and the backend system 160 shown in fig. 1. The method comprises the following steps:
step 1, the unified booking device acquires a merchant and constructs request parameters.
For example, the unified booking device acquires order data stored by various merchants on different background systems in batches. Illustratively, the unified reservation device obtains an identifier of a merchant, constructs an order request message of the merchant, and sends the order request message to a background system corresponding to the merchant.
And 2, the unified booking equipment pulls order data in batches according to the single merchant.
For example, after the unified booking device selects a merchant, the order data stored by the merchant in the background system is acquired in batches. For example, the unified reservation apparatus acquires order data in batches by year. For example, the unified booking device sends three order request messages to the background system, which are respectively used for requesting order data of the merchant in this year, last year and previous year. Or the unified booking device sends an order request message to the background system, and the background system is requested to return order data of the merchant in batches in the current year, the last year and the previous year.
And 3, the background system processes the request and constructs return data.
And after receiving the order request message, the background system processes the order request message and constructs an order response message. And returning the order information of the merchant to the unified booking device.
And 4, the background system returns the order data of the merchant in batches.
And 5, acquiring each batch of data by the database until the data acquisition of the merchant is completed, acquiring the data of the next merchant, and pulling the data in batches.
And after receiving the order response message, the unified booking device acquires the order information in the order response message and stores the order information into the database. And when the pulling of the order information of one merchant is finished, continuously pulling the order information of the next merchant.
In summary, in the method provided in this embodiment, the unified reservation device pulls the order information of one merchant from the background system in batch, stores the order data of the merchant into the database, and continues to pull the order information of the next merchant after the order information of one merchant is successfully pulled. The order information of each merchant is stored in the unified database, and when the merchant needs to replace the background system, the order data person is stored in the database. The background system of the system provider can send the order information to the unified booking equipment through the order interface to be stored no matter how many system providers exist or whether the system providers are replaced or not, and further deposit the order information conforming to the order interface format in the database for the analysis and use of the scenic spot workers, so that the data utilization rate and the anti-risk performance of the data center of the scenic spot are improved.
The following is an exemplary description of the order interface (full-scale synchronized order data interface):
1. interface description:
1.1 usage scenarios:
the unified booking device actively calls an order interface of a system provider to acquire information of a full order in a specified scenic spot and a specified time period, and the unified booking device comprises the following components: the system comprises basic information of orders, information of order players, information of order ticket codes, information of check and sales flow, information of refund flow and information of change and signing flow.
1.2 request method: POST (positive position transducer)
1.3 request Address (URL): system provider provisioning
2. The request parameters (the parameter contents in the request message template) are shown in table one:
watch 1
3. The response parameters (the parameter content/order information in the response message template) are shown in table two:
watch two
Code (error Code) description see table three:
watch III
| Error code | Error description | Solution scheme |
| 200 | Return success | |
| 101 | Parameter error | Checking validity of parameters |
| 102 | System exception | Caller retry |
| 199 | Others | According to the information processing in the descriptor, or contacting the operator |
5. Code example:
5.1 example order request message:
5.2 order response message example:
fig. 5 illustrates a storage system for order information provided by an exemplary embodiment of the present application. The system comprises: a unified booking device 601 and a database 602, wherein the unified booking device 601 is a device located between a ticket sale and check system and a background system.
The unified booking device 601 is configured to execute the storage method for order information provided in any of the above embodiments to store the order information of the full-volume order in the database;
a database 602 for storing order information for full orders.
Fig. 6 is a block diagram illustrating an apparatus for storing order information according to an exemplary embodiment of the present application. The device is a device between a ticket selling and checking system and a background system, and comprises:
a first sending module 701, configured to send an order request message to a background system through an order interface, where the order request message is used to obtain order information of a full order of a specified merchant in a specified time period, the order interface is suitable for information interaction between the unified reservation device and at least two different background systems, and the order interface is an interface provided by the background systems;
a first receiving module 703, configured to receive an order response message sent by the background system, where the order response message includes the order information;
the storage module 705 is configured to store the order information in the order response message in a database.
In one illustrative example, the apparatus further comprises:
a first obtaining module 704, configured to obtain a request packet template of the order request packet, where a template type field of the request packet template is an order information request field;
the first obtaining module 704 is further configured to obtain at least one parameter content required by the request packet template;
a first generating module 702, configured to generate the order request packet according to the request packet template and the content of the at least one parameter.
In an exemplary example, the first obtaining module 704 is further configured to obtain content of at least one parameter of a merchant identifier ID, an order channel, a quantity per page, a number of pages, a start date, and an end date, which are required by the request message template.
In one illustrative example, the order information includes: at least one of order basic information, order consumer information, order coupon code information, verification and marketing flow information, refund flow information and re-signing flow information.
In an exemplary example, the first sending module 701 is further configured to send an order request message to a background system through an order interface in a POST mode.
In one illustrative example, the backend system includes a first backend system and a second backend system, the first backend system corresponding to a first uniform resource locator, URL, the second backend system corresponding to a second URL;
the first sending module 701, further in response to sending the order request message to a first background system, calls the order interface to send the order request message of the POST type to the first background system indicated by a first URL;
the first sending module 701 further calls the order interface to send the order request message of the POST type to the second background system indicated by the second URL in response to sending the order request message to the second background system.
In one illustrative example, the apparatus further comprises:
a first identification module 706, configured to identify a template type field of the order response packet;
the storage module 705, further in response to that the template type field is an order information response field, stores the order information in the order response message into a database.
Fig. 7 is a block diagram illustrating an apparatus for storing order information provided by an exemplary embodiment of the present application.
The device includes:
a second receiving module 708, configured to receive an order request message sent by a unified booking device through an order interface, where the order request message is used to obtain order information of a full order of a specified merchant in a specified time period, the order interface is applicable to information interaction between the unified booking device and at least two different background systems, the order interface is an interface provided by the background systems, and the unified booking device is a device located between a ticket selling and checking system and the background systems;
a second generating module 709, configured to generate an order response message according to the order request message, where the order response message includes the order information;
a second sending module 707, configured to send the order response message to the unified booking device.
In one illustrative example, the apparatus further comprises:
a second identification module 710, configured to identify a template type field of the order request packet;
the second obtaining module 711, in response to the template type field being an order information request field, obtains a response message template of an order response message corresponding to the order request message, where the template type field of the response message template is an order information response field;
the second obtaining module 711 is further configured to obtain at least one piece of order information required by the order request message;
a second generating module 709, configured to generate the order response message according to the response message template and the order information.
In an exemplary example, the second obtaining module 711 is further configured to obtain parameter content in the order request message, where the parameter content includes at least one of a merchant identifier ID, an order channel, a number per page, a number of pages, a start date, and an end date;
the second obtaining module 711 is further configured to obtain at least one piece of order information according to the parameter content, where the order information includes at least one of order basic information, order consumer information, order coupon code information, reimbursement running information, and re-signing running information.
In an exemplary example, the order request message is sent by the unified reservation equipment calling the order interface to the background system indicated by a uniform resource locator URL in a POST manner.
Fig. 8 shows a schematic structural diagram of a computer device provided in an exemplary embodiment of the present application. The computer device may be a unified subscribing device or a unified routing device in the above system. Specifically, the method comprises the following steps:
the computer apparatus 800 includes a Central Processing Unit (CPU) 801, a system Memory 804 including a Random Access Memory (RAM) 802 and a Read Only Memory (ROM) 803, and a system bus 805 connecting the system Memory 804 and the Central Processing Unit 801. The computer device 800 also includes a basic Input/Output System (I/O) 806 for facilitating information transfer between devices within the computer, and a mass storage device 807 for storing an operating System 813, application programs 814, and other program modules 815.
The basic input/output system 806 includes a display 807 for displaying information and an input device 809 such as a mouse, keyboard, or the like for inputting information by a user. Wherein a display 807 and an input device 809 are connected to the central processing unit 801 through an input output controller 810 connected to the system bus 805. The basic input/output system 806 may also include an input/output controller 810 for receiving and processing input from a number of other devices, such as a keyboard, mouse, or electronic stylus. Similarly, input-output controller 810 also provides output to a display screen, a printer, or other type of output device.
The mass storage device 807 is connected to the central processing unit 801 through a mass storage controller (not shown) connected to the system bus 805. The mass storage device 807 and its associated computer-readable media provide non-volatile storage for the computer device 800. That is, the mass storage device 807 may include a computer-readable medium (not shown) such as a hard disk or Compact disk Read Only Memory (CD-ROM) drive.
Computer-readable media may include computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes RAM, ROM, Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), flash Memory or other Solid State Memory technology, CD-ROM, Digital Versatile Disks (DVD), or Solid State Drives (SSD), other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage, or other magnetic storage devices. The Random Access Memory may include a resistive Random Access Memory (ReRAM) and a Dynamic Random Access Memory (DRAM). Of course, those skilled in the art will appreciate that computer storage media is not limited to the foregoing. The system memory 804 and mass storage 807 described above may be collectively referred to as memory.
According to various embodiments of the present application, the computer device 800 may also operate as a remote computer connected to a network via a network, such as the Internet. That is, the computer device 800 may be connected to the network 812 through the network interface unit 811 coupled to the system bus 805, or may be connected to other types of networks or remote computer systems (not shown) using the network interface unit 811.
The memory further includes one or more programs, and the one or more programs are stored in the memory and configured to be executed by the CPU.
In an alternative embodiment, a computer device is provided, the computer device comprising a processor and a memory, the memory having stored therein at least one instruction, at least one program, set of codes, or set of instructions, the at least one instruction, the at least one program, set of codes, or set of instructions being loaded and executed by the processor to implement the method of controlling a virtual object as described above.
In an alternative embodiment, a computer readable storage medium is provided having stored therein at least one instruction, at least one program, set of codes, or set of instructions that is loaded and executed by a processor to implement the method of controlling a virtual object as described above.
Optionally, the computer-readable storage medium may include: a Read Only Memory (ROM), a Random Access Memory (RAM), a Solid State Drive (SSD), or an optical disc. The Random Access Memory may include a resistive Random Access Memory (ReRAM) and a Dynamic Random Access Memory (DRAM). The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The present application further provides a computer-readable storage medium, in which at least one instruction, at least one program, a code set, or a set of instructions is stored, and the at least one instruction, the at least one program, the code set, or the set of instructions is loaded and executed by a processor to implement the storage method of the order information provided by the above-mentioned method embodiments.
It should be understood that reference to "a plurality" herein means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above description is only exemplary of the present application and should not be taken as limiting, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.
Claims (18)
1. A method for storing order information is applied to a unified booking device, wherein the unified booking device is a device located between a ticket selling and checking system and a background system, and the method comprises the following steps:
sending an order request message to the background system through an order interface, wherein the order request message is used for acquiring order information of a full order of a specified merchant in a specified time period, the order interface is suitable for information interaction between the unified reservation equipment and at least two different background systems, and the order interface is an interface provided by the background systems;
receiving an order response message sent by the background system, wherein the order response message comprises the order information;
and storing the order information in the order response message into a database.
2. The method according to claim 1, wherein before sending the order request message to the background system through the order interface, the method further comprises:
acquiring a request message template of the order request message, wherein a template type field of the request message template is an order information request field;
acquiring at least one parameter content required by the request message template;
and generating the order request message according to the request message template and the at least one parameter content.
3. The method according to claim 2, wherein the obtaining at least one parameter content required by the request message template comprises:
and acquiring at least one parameter content of a merchant identifier ID, an order channel, the quantity of each page, the number of pages, a start date and an end date required by the request message template.
4. The method of claim 1, wherein the order information comprises: at least one of order basic information, order consumer information, order coupon code information, verification and marketing flow information, refund flow information and re-signing flow information.
5. The method according to claim 1, wherein sending the order request message to the back-end system through the order interface comprises:
and sending an order request message to a background system through an order interface in a POST mode.
6. The method of claim 5, wherein the backend system comprises a first backend system and a second backend system, wherein the first backend system corresponds to a first uniform resource locator, URL, and wherein the second backend system corresponds to a second URL;
the sending of the order request message to the background system by the order interface in a POST mode comprises the following steps:
in response to the order request message sent to a first background system, calling the order interface to send the order request message of the POST type to the first background system indicated by a first URL;
and in response to the order request message sent to a second background system, calling the order interface to send the POST type order request message to the second background system indicated by a second URL.
7. The method of claim 1, wherein storing the order information in the order response message in a database comprises:
identifying a template type field of the order response message;
and when the template type field is an order information response field, storing the order information in the order response message into a database.
8. The method for storing the order information is applied to a background system, and comprises the following steps:
receiving an order request message sent by a unified booking device through an order interface, wherein the order request message is used for acquiring order information of a full order of a designated merchant in a designated time period, the order interface is suitable for information interaction between the unified booking device and at least two different background systems, the order interface is an interface provided by the background systems, and the unified booking device is a device positioned between a ticket selling and checking system and the background systems;
generating an order response message according to the order request message, wherein the order response message comprises the order information;
and sending the order response message to the unified booking equipment.
9. The method according to claim 8, wherein generating an order response message according to the order request message comprises:
identifying a template type field of the order request message;
responding to the template type field as an order information request field, and acquiring a response message template of an order response message corresponding to the order request message, wherein the template type field of the response message template is the order information response field;
acquiring at least one order information required by the order request message;
and generating the order response message according to the response message template and the order information.
10. The method according to claim 9, wherein the obtaining at least one order information required by the order request message comprises:
acquiring parameter content in the order request message, wherein the parameter content comprises at least one of merchant Identification (ID), an order channel, the quantity of each page, the number of pages, a starting date and an ending date;
and acquiring at least one order information according to the parameter content, wherein the order information comprises at least one of order basic information, order consumer information, order coupon code information, verification and marketing flow information, refund flow information and re-signing flow information.
11. The method according to claim 8, wherein the order request message is sent by the unified reservation device to the backend system indicated by a uniform resource locator URL by calling the order interface in a POST manner.
12. A system for storing order information, the system comprising: the system comprises a uniform booking device and a database, wherein the uniform booking device is a device positioned between a ticket selling and checking system and a background system;
the unified booking device, configured to execute the order information storage method according to any one of claims 1 to 7, so as to store the order information of the full-volume order in the database;
and the database is used for storing the order information of the full order.
13. An apparatus for storing order information, the apparatus being located between a ticket vending and checking system and a back office system, the apparatus comprising:
the order interface is suitable for information interaction between the unified booking device and at least two different background systems, and the order interface is an interface provided by the background systems;
the first receiving module is used for receiving an order response message sent by the background system, wherein the order response message comprises the order information;
and the storage module is used for storing the order information in the order response message into a database.
14. An apparatus for storing order information, the apparatus comprising:
a second receiving module, configured to receive, through an order interface, an order request message sent by a unified booking device, where the order request message is used to obtain order information of a full order of a specified merchant in a specified time period, the order interface is applicable to information interaction between the unified booking device and at least two different background systems, the order interface is an interface provided by the background systems, and the unified booking device is a device located between a ticket selling and checking system and the apparatus;
a second generating module, configured to generate an order response message according to the order request message, where the order response message includes the order information;
and the second sending module is used for sending the order response message to the unified booking device.
15. A computer device, characterized in that the computer device comprises: a processor and a memory, the memory storing a computer program that is loaded and executed by the processor to implement the method of storing order information according to any one of claims 1 to 7.
16. A computer-readable storage medium, in which a computer program is stored, the computer program being loaded and executed by a processor to implement the storage method of order information according to any one of claims 1 to 7.
17. A computer device, characterized in that the computer device comprises: a processor and a memory, the memory storing a computer program that is loaded and executed by the processor to implement the method of storing order information according to any one of claims 8 to 11.
18. A computer-readable storage medium, in which a computer program is stored, the computer program being loaded and executed by a processor to implement the storage method of order information according to any one of claims 8 to 11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010131425.1A CN111324612A (en) | 2020-02-28 | 2020-02-28 | Storage method, system, device, equipment and storage medium of order information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010131425.1A CN111324612A (en) | 2020-02-28 | 2020-02-28 | Storage method, system, device, equipment and storage medium of order information |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111324612A true CN111324612A (en) | 2020-06-23 |
Family
ID=71172929
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010131425.1A Withdrawn CN111324612A (en) | 2020-02-28 | 2020-02-28 | Storage method, system, device, equipment and storage medium of order information |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111324612A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107358503A (en) * | 2017-07-11 | 2017-11-17 | 郑州云海信息技术有限公司 | A kind of electronic order interface system and electronic order interface realizing method |
| CN109947994A (en) * | 2018-08-10 | 2019-06-28 | 北京京东金融科技控股有限公司 | Processing method, device, medium and the electronic equipment of payment process |
| CN110300190A (en) * | 2019-07-25 | 2019-10-01 | 中国工商银行股份有限公司 | A kind of ticket selling and checking system based on MQTT message-oriented middleware |
| CN110619555A (en) * | 2019-08-15 | 2019-12-27 | 中国平安财产保险股份有限公司 | Unified management method and device for order information, terminal equipment and medium |
-
2020
- 2020-02-28 CN CN202010131425.1A patent/CN111324612A/en not_active Withdrawn
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107358503A (en) * | 2017-07-11 | 2017-11-17 | 郑州云海信息技术有限公司 | A kind of electronic order interface system and electronic order interface realizing method |
| CN109947994A (en) * | 2018-08-10 | 2019-06-28 | 北京京东金融科技控股有限公司 | Processing method, device, medium and the electronic equipment of payment process |
| CN110300190A (en) * | 2019-07-25 | 2019-10-01 | 中国工商银行股份有限公司 | A kind of ticket selling and checking system based on MQTT message-oriented middleware |
| CN110619555A (en) * | 2019-08-15 | 2019-12-27 | 中国平安财产保险股份有限公司 | Unified management method and device for order information, terminal equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5161267B2 (en) | Screen customization support system, screen customization support method, and screen customization support program | |
| CN110458562B (en) | Bill reimbursement method, device and equipment and computer storage medium | |
| WO2015096616A1 (en) | Message sending and forwarding method, apparatus, and system | |
| CN110796458B (en) | Information management system | |
| US20020035516A1 (en) | Server computer system for selling digital contents by using network, player terminal for replaying digital contents by using network, system for selling digital contents by using network, method for selling digital contents by using network, and machine-readable storage medium | |
| CN111327514B (en) | WeChat image-text message group sending method, system, server and storage medium | |
| CN107993106B (en) | Electronic invoice generation method and device | |
| CN111260399B (en) | Advertisement data processing method and device based on block chain network and electronic equipment | |
| CN112948521B (en) | Object handling method and device | |
| CN110852719A (en) | Electronic contract signing method and device, electronic equipment and storage medium | |
| KR101947483B1 (en) | The system for interaction advertisement combined on-line and off-line and that of method for advertisement | |
| US7587339B2 (en) | Systems, methods, and computer readable medium for providing a site for selling a product in response to a request from a terminal | |
| CN110738784B (en) | Invoice management method, device, server and system | |
| CN113362085A (en) | Primary and secondary account management method and system | |
| CN111324780A (en) | Storage method, transmission method, device and storage medium of product data | |
| CN111324612A (en) | Storage method, system, device, equipment and storage medium of order information | |
| CN111199427B (en) | Grouping management method and device for network users, electronic equipment and storage medium | |
| RU2372656C2 (en) | System and method of forming and distributing information on goods | |
| KR102049507B1 (en) | System for providing consulting service for communication products and method thereof | |
| CN110956512B (en) | Billing data processing method and device, computer equipment and storage medium | |
| CN113268287A (en) | Small program starting method and device based on graphic code | |
| WO2021090311A1 (en) | System and method for improving efficiency of communication sessions at a call center | |
| GB2521345A (en) | Method and system for generating a quote | |
| CN111367977A (en) | Ticket data storage system, method, device, equipment and storage medium | |
| CN110705734B (en) | Reservation service system, method and equipment for online lodging products |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20200623 |
|
| WW01 | Invention patent application withdrawn after publication |