CN107679843B - Method, device, server and storage medium for improving ticket drawing rate - Google Patents
Method, device, server and storage medium for improving ticket drawing rate Download PDFInfo
- Publication number
- CN107679843B CN107679843B CN201710915696.4A CN201710915696A CN107679843B CN 107679843 B CN107679843 B CN 107679843B CN 201710915696 A CN201710915696 A CN 201710915696A CN 107679843 B CN107679843 B CN 107679843B
- Authority
- CN
- China
- Prior art keywords
- ticket
- asynchronous
- locking
- result
- user
- 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.)
- Active
Links
Images
Classifications
-
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/102—Bill distribution or payments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- 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
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/547—Messaging middleware
Abstract
The embodiment of the invention discloses a method, a device, a server and a storage medium for improving a ticket drawing rate. The method for improving the ticket drawing rate comprises the following steps: carrying out synchronous ticket locking according to ticket booking information of a user; generating a current order according to a synchronous ticket locking result for a user to pay for the current order, wherein the synchronous ticket locking result comprises the overtime or success of ticket locking; and after the current order is generated, carrying out asynchronous ticket locking or asynchronous ticket drawing according to the result of the synchronous ticket locking and the result of user payment. According to the embodiment of the invention, the method of asynchronous ticket locking and asynchronous ticket drawing is adopted in the ticket booking process, so that the ticket drawing rate of a user when the user purchases tickets through a third-party application can be improved, the user experience is improved, and the economic loss caused by inconsistent ticket drawing states is avoided.
Description
Technical Field
The embodiment of the invention relates to the internet technology, in particular to a method, a device, a server and a storage medium for improving the ticket drawing rate.
Background
With the development and popularization of the internet technology, more and more users buy tickets, air tickets or ship tickets through third-party application, and great convenience is brought to the travel of the users.
In the prior art, a user inputs travel information through a ticket buying APP to place an order, then a server side of the ticket buying APP receives the order information and informs a ticket service provider of ticket locking and ticket drawing within a certain time in a synchronous mode, and then a client side feeds back a message according to the states of the ticket locking and the ticket drawing.
However, due to incomplete infrastructure of the provider and no remedial measure when the operation is overtime in the ticket locking and ticket drawing process, the ticket drawing rate is low, so that the trip of the client is influenced, and the user experience is poor; and the ticket issuing state of the client and the supplier is inconsistent, thereby causing economic loss.
Disclosure of Invention
The embodiment of the invention provides a method, a device, a server and a storage medium for improving a ticket drawing rate, and aims to solve the problems of low ticket drawing rate, poor user experience and economic loss in the prior art.
In a first aspect, an embodiment of the present invention provides a method for increasing a ticket output rate, where the method includes:
carrying out synchronous ticket locking according to ticket booking information of a user;
generating a current order according to a synchronous ticket locking result for a user to pay for the current order, wherein the synchronous ticket locking result comprises the overtime or success of ticket locking;
and after the current order is generated, carrying out asynchronous ticket locking or asynchronous ticket drawing according to the result of the synchronous ticket locking and the result of user payment.
In a second aspect, an embodiment of the present invention further provides a device for increasing a ticket output rate, where the device includes:
the synchronous ticket locking module is used for carrying out synchronous ticket locking according to ticket booking information of a user;
the order generation module is used for generating a current order according to a synchronous ticket locking result so that a user can pay for the current order, wherein the synchronous ticket locking result comprises the overtime or success of the ticket locking;
and the asynchronous module is used for carrying out asynchronous ticket locking or asynchronous ticket drawing according to the result of the synchronous ticket locking and the result of user payment after the current order is generated.
In a third aspect, an embodiment of the present invention further provides a server, including:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method for increasing a ticket rate of any embodiment of the present invention.
In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method for increasing a ticket output rate in any embodiment of the present invention.
According to the embodiment of the invention, the synchronous ticket locking is carried out according to the ticket booking information of the user, the current order is generated according to the result of the synchronous ticket locking so as to be paid by the user, and then the asynchronous ticket locking or asynchronous ticket drawing is carried out according to the result of the synchronous ticket locking and the result of the payment of the user after the current order is generated.
Drawings
FIG. 1 is a flowchart of a method for increasing a ticket output rate according to a first embodiment of the present invention;
FIG. 2 is a flowchart of a method for increasing the ticket output rate according to a second embodiment of the present invention;
FIG. 3 is a schematic structural diagram of a device for increasing a ticket output rate according to a third embodiment of the present invention;
fig. 4 is a schematic structural diagram of a server in the fourth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1 is a flowchart of a method for increasing a ticket-out rate according to an embodiment of the present invention, which is applicable to a situation that a user purchases a ticket from a ticket provider through a client, where the ticket includes a train ticket or a bus ticket. The method can be executed by a device for increasing the ticket output rate, the device can be realized in a software and/or hardware mode, and the device can be configured in a server. As shown in fig. 1, the method specifically includes:
and S110, carrying out synchronous ticket locking according to the ticket booking information of the user.
When a user has a ticket-booking requirement, the ticket-booking client is usually opened at a terminal such as a computer or a mobile phone, and corresponding ticket-booking information is filled according to a content prompt displayed on a page of the ticket-booking client, wherein the ticket-booking information includes a name, an identity card number, a travel date, a departure place, a destination, a train number, a seat category and the like of the user. The user can place the order after confirming that the information is correct, and the server performs synchronous ticket locking after receiving the order information. The ticket locking process is carried out by synchronizing the ticket locking, namely, the interaction between the server and the ticket service provider.
And S120, generating a current order according to the result of the synchronous ticket locking so that the user can pay for the current order, wherein the result of the synchronous ticket locking comprises the timeout or success of the ticket locking.
Specifically, the supplier locks the ticket for the user according to the order information submitted by the user and the remaining ticket information (including the number of the remaining tickets and the corresponding seat number) of the train number which can be provided by the user, if the ticket locking is successful, the current order is generated, the seat number which is locked by the user is fed back, and a payment entrance is provided for the user to continue to pay; if the interface is overtime due to the problems of the server network and the like, namely the ticket locking is overtime and the ticket locking is unsuccessful, corresponding order information is generated to enable the user to pay in advance, and then the asynchronous ticket locking or asynchronous ticket drawing operation is carried out.
And S130, after the current order is generated, carrying out asynchronous ticket locking or asynchronous ticket drawing according to the result of the synchronous ticket locking and the result of the payment of the user.
In the computer field, synchronization may be understood as after an operation is performed, a downstream may wait until the result of the operation is performed, and then continue to perform a next action; asynchronous is understood to mean that after an operation is executed, the downstream does not need to wait for the execution result of the operation, and can continue to execute the next action.
Based on this, in the embodiment of the invention, after the ticket is locked synchronously, the current order is generated according to the result, wherein if the result fails, the current ticket booking fails, the next step cannot be performed, when the synchronous ticket locking succeeds or is overtime, the next step of generating the order is performed to be paid by the user, and the server performs asynchronous ticket locking or asynchronous ticket drawing according to the result of the synchronous ticket locking and the result of the payment of the user.
That is, even if the synchronous ticket locking is overtime, the user does not need to wait for the synchronous ticket locking result all the time, the user can be paid in advance, and the server performs asynchronous ticket locking or asynchronous ticket drawing according to the result of the user payment; or if the synchronous ticket locking is successful and the current order is generated, asynchronous ticket drawing is carried out according to the payment result of the user. Therefore, the ticket booking process is realized through the synchronous link and the asynchronous link together, the ticket is drawn successfully, the experience of a user is improved, and the problem of inconsistent ticket drawing states caused by the problems of networks of a server or a ticket provider and the like is solved. For example, if the synchronous ticket locking is overtime, the prior art waits for the synchronous ticket locking result, and the overtime waiting usually has a certain time limit, and if the server has a problem in the network at this time, the time limit gives a feedback that the ticket locking is failed to the user, but the ticket locking is successful at one end of the ticket service provider, so that the state information of the two ends is inconsistent. The technical scheme of the embodiment of the invention avoids the problem.
Further, S130 includes:
when the result of the synchronous ticket locking is that the ticket locking is overtime, carrying out asynchronous ticket locking, and carrying out asynchronous ticket drawing according to the result of the asynchronous ticket locking and the result of user payment;
and when the result of the synchronous ticket locking is successful, performing asynchronous ticket drawing according to the result of the payment of the user.
Wherein, when the result of the synchronous ticket locking is that the ticket locking is overtime, the asynchronous ticket locking is carried out, and asynchronous ticket drawing is carried out according to the result of the asynchronous ticket locking and the result of user payment, comprising the following steps: when the synchronous ticket locking result is that the ticket locking is overtime, asynchronous ticket locking is carried out, and when the asynchronous ticket locking is successful, whether the payment result of the user is successful or not is judged; and when the payment result of the user is successful, asynchronous ticket drawing is carried out, otherwise, the ticket source is released.
When the result of the synchronous ticket locking is successful, asynchronous ticket drawing is carried out according to the result of the payment of the user, and the method comprises the following steps: when the ticket locking result is successful, judging whether the payment result of the user is successful; and when the payment result of the user is successful, asynchronous ticket drawing is carried out, otherwise, the ticket source is released.
According to the technical scheme of the embodiment, the ticket is synchronously locked according to the ticket booking information of the user, the current order is generated according to the result of the synchronous ticket locking so that the user can pay for the current order, asynchronous ticket locking or asynchronous ticket drawing is performed according to the result of the synchronous ticket locking and the result of the user payment after the current order is generated, and the ticket booking and drawing are completed by adopting two links, namely synchronous and asynchronous links, so that the consistency of the drawing state between the client and the supplier is ensured, the drawing rate is improved, the user experience is improved, and the economic loss caused by the inconsistency of the drawing state is avoided.
Example two
Fig. 2 is a flowchart of a method for increasing a ticket-out rate according to a second embodiment of the present invention, and the second embodiment of the present invention performs further optimization based on the first embodiment of the present invention. As shown in fig. 2, the method includes:
and S210, carrying out synchronous ticket locking according to the ticket booking information of the user.
S220, generating a current order according to the result of the synchronous ticket locking so that the user can pay for the current order, wherein the result of the synchronous ticket locking comprises the timeout or success of the ticket locking.
S230, when the result of the synchronous ticket locking is that the ticket locking is overtime, performing asynchronous ticket locking, and performing asynchronous ticket drawing according to the result of the asynchronous ticket locking and the result of user payment; and when the result of the synchronous ticket locking is successful, performing asynchronous ticket drawing according to the result of the payment of the user.
And S240, retrying according to the retrying times and frequency of the asynchronous ticket locking and the asynchronous ticket drawing before the asynchronous ticket locking or the asynchronous ticket drawing succeeds, and not exceeding the time of the asynchronous ticket locking or the time of the asynchronous ticket drawing.
Preferably, before synchronous ticket locking according to ticket booking information of a user, the method further comprises acquiring asynchronous control time, wherein the asynchronous control time is pre-configured according to service information of each provider, the service information comprises a maximum ticket locking time, a maximum ticket issuing time, a sale prohibition period and a maximum interface capacity supported by each provider, and the asynchronous control time comprises the time of asynchronous ticket locking, the time of asynchronous ticket issuing and retry times and frequency of the asynchronous ticket locking and the asynchronous ticket issuing.
Specifically, the maximum interface capability of different suppliers is different due to the fact that the infrastructure of the different suppliers is different, and in addition, the different suppliers have respective requirements on service information such as maximum ticket locking time, maximum ticket drawing time, forbidden sale period and the like. The method comprises the steps of determining asynchronous control time according to the service information, controlling retry times and frequency in asynchronous operation through the asynchronous control time, meeting requirements of providers to the maximum extent, controlling the access amount of a certain provider to prevent a system from being broken down when a large number of users access ticket purchasing APPs to purchase tickets, and shunting the users according to interface capabilities of the providers to enable a server to be matched with the providers with different interface capabilities.
Correspondingly, before the asynchronous ticket locking or the asynchronous ticket drawing succeeds, the retries are carried out according to the retries and the frequency of the asynchronous ticket locking and the asynchronous ticket drawing, and the time of the asynchronous ticket locking or the time of the asynchronous ticket drawing is not exceeded.
Specifically, when the asynchronous ticket locking and asynchronous ticket drawing time-out is unsuccessful, the server automatically repeats the ticket locking or ticket drawing process with the provider. The time consumed by the current ticket locking or ticket drawing can be known according to the repeated times and the time for waiting for the ticket locking or ticket drawing each time, the time is controlled within the time of asynchronous ticket locking or the time of asynchronous ticket drawing, if the time exceeds the time of asynchronous ticket locking or the time of asynchronous ticket drawing, the retry is stopped, the information of ticket locking or ticket drawing failure is directly fed back, and the user is requested to place an order again. The time of asynchronous ticket locking or the time of asynchronous ticket drawing does not exceed the maximum ticket locking time and the maximum ticket drawing time supported by the supplier, and the forbidden sale period of the supplier is excluded from the time that the user can place the order.
Further, the asynchronous control time also includes unpaid time and time spent paying to ticket out. The unpaid time is the time between the payment request sent to the user and the feedback information of successful payment, and is used for monitoring whether the payment process is completed within the unpaid time; the time spent from payment to ticket drawing is the time between the initiation of a payment request to the user and the success of asynchronous ticket drawing, and is used for monitoring whether the asynchronous ticket drawing process is completed within the time spent from the payment to the ticket drawing after the initiation of the payment request to the user.
And S250, before the asynchronous ticket locking or the asynchronous ticket drawing is successful, the repeated asynchronous ticket locking or asynchronous ticket drawing request is subjected to duplicate removal.
Specifically, in this embodiment, an nmq (new message queue) framework is used to implement the operations of asynchronous ticket locking and asynchronous ticket drawing, and before the asynchronous ticket locking or asynchronous ticket drawing succeeds, duplicate asynchronous ticket locking or asynchronous ticket drawing requests are removed. The NMQ framework is a message middleware component in the server, is a universal message queue system, is essentially an asynchronous transmission mode for realizing mutual communication among a plurality of different applications, and is compatible with an upstream module and a downstream module of the NMQ framework.
It should be noted that before the asynchronous ticket locking or ticket drawing succeeds, the server may issue corresponding service requests to the ticket locking or ticket drawing interface of the ticket provider many times, since the server may retry many times. Therefore, in order to ensure the consistency of the ticket issuing states of the server and the provider, the provider also needs to feed back the ticket-locked or ticket-issued message to the server after the ticket locking or ticket issuing is completed, so that the server does not retry for many times after receiving the message. In addition, the supplier side also needs to not repeat ticket locking or ticket drawing for receiving a repeat request from the server after the ticket is locked or drawn. Therefore, the condition that the states of the two ends are inconsistent due to the fact that the supplier draws tickets for many times because of the requests of the server for many times is avoided.
According to the method and the device, the configuration is carried out according to the basic service information of the suppliers before the synchronous ticket locking is carried out according to the ticket booking information of the users, the ticket locking or ticket drawing process is retried in the asynchronous control time, the repeated request is removed before the ticket locking or ticket drawing, the ticket drawing rate can be improved to the greatest extent, the repeated ticket drawing can be prevented, and in addition, the difference of user experience caused by different basic service capabilities of different suppliers can be eliminated.
EXAMPLE III
Fig. 3 is a schematic structural diagram of a device for increasing a ticket output rate in a third embodiment of the present invention. As shown in fig. 3, the apparatus for increasing the ticket drawing rate includes:
and the synchronous ticket locking module 310 is configured to lock a synchronous ticket according to the ticket booking information of the user.
And the order generating module 320 generates a current order according to a result of the synchronous ticket locking, so that the user can pay for the current order, wherein the result of the synchronous ticket locking includes that the ticket locking is overtime or successful.
And the asynchronous module 330 is configured to perform asynchronous ticket locking or asynchronous ticket drawing according to the result of the synchronous ticket locking and the result of the user payment after the current order is generated.
Further, the asynchronous module 330 includes:
the asynchronous ticket locking unit is used for carrying out asynchronous ticket locking when the result of synchronous ticket locking is that the ticket locking is overtime;
and the asynchronous ticket issuing unit is used for performing asynchronous ticket issuing according to the result of the user payment or performing asynchronous ticket issuing according to the result of the asynchronous ticket locking and the result of the user payment when the result of the synchronous ticket locking is that the ticket locking is successful.
Further, the asynchronous ticket issuing unit is specifically configured to:
when the ticket locking result is successful, judging whether the payment result of the user is successful; when the payment result of the user is successful, asynchronous ticket drawing is carried out, otherwise, the ticket source is released; or when the asynchronous ticket locking is successful, judging whether the payment result of the user is successful; and when the payment result of the user is successful, asynchronous ticket drawing is carried out, otherwise, the ticket source is released.
Further, the device for improving the ticket rate further comprises:
the system comprises an asynchronous control time acquisition module, a ticket booking module and a ticket checking module, wherein the asynchronous control time acquisition module is used for acquiring asynchronous control time before synchronous ticket locking according to ticket booking information of a user, the asynchronous control time is pre-configured according to service information of each provider, the service information comprises maximum ticket locking time, maximum ticket issuing time, a sale prohibition period and maximum interface capacity supported by each provider, and the asynchronous control time comprises asynchronous ticket locking time, asynchronous ticket issuing time, and retry times and frequency of the asynchronous ticket locking and the asynchronous ticket issuing;
correspondingly, the device also comprises:
and the retry module is used for retrying according to the retry times and frequency of the asynchronous ticket locking and the asynchronous ticket drawing before the asynchronous ticket locking or the asynchronous ticket drawing succeeds, and the time of the asynchronous ticket locking or the asynchronous ticket drawing is not exceeded.
Further, the asynchronous control time also comprises unpaid time and time spent from payment to ticket drawing;
the unpaid time is the time between the payment request sent to the user and the feedback information of successful payment, and is used for monitoring whether the payment process is completed within the unpaid time;
the time spent from payment to ticket drawing is the time between the initiation of a payment request to the user and the success of asynchronous ticket drawing, and is used for monitoring whether the asynchronous ticket drawing process is completed within the time spent from the payment to the ticket drawing after the initiation of the payment request to the user.
Further, the device for improving the ticket drawing rate realizes the operations of asynchronous ticket locking and asynchronous ticket drawing by utilizing an NMQ frame;
the device also includes:
and the duplicate removal module is used for removing duplicate of repeated asynchronous ticket locking or asynchronous ticket drawing requests before the asynchronous ticket locking or asynchronous ticket drawing succeeds.
The device for improving the ticket rate provided by the embodiment of the invention can execute the method for improving the ticket rate provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
Example four
Fig. 4 is a schematic structural diagram of a server in the fourth embodiment of the present invention. FIG. 4 illustrates a block diagram of an exemplary server 412 suitable for use in implementing embodiments of the present invention. The server 412 shown in fig. 4 is only an example and should not bring any limitations to the function and scope of use of the embodiments of the present invention.
As shown in FIG. 4, the server 412 is in the form of a general purpose computing device. Components of server 412 may include, but are not limited to: one or more processors or processing units 416, a system memory 428, and a bus 418 that couples the various system components including the system memory 428 and the processing unit 416.
The system memory 428 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)430 and/or cache memory 432. The server 412 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 434 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 4, commonly referred to as a "hard drive"). Although not shown in FIG. 4, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 418 by one or more data media interfaces. Memory 428 can include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
A program/utility 440 having a set (at least one) of program modules 442 may be stored, for instance, in memory 428, such program modules 442 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. The program modules 442 generally perform the functions and/or methodologies of the described embodiments of the invention.
The server 412 may also communicate with one or more external devices 414 (e.g., keyboard, pointing device, display 424, etc.), with one or more devices that enable a user to interact with the server 412, and/or with any devices (e.g., network card, modem, etc.) that enable the server 412 to communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interfaces 422. Also, server 412 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet) through network adapter 420. As shown, network adapter 420 communicates with the other modules of server 412 over bus 418. It should be appreciated that although not shown in FIG. 4, other hardware and/or software modules may be used in conjunction with the server 412, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
The processing unit 416 executes programs stored in the system memory 428 to perform various functional applications and data processing, for example, to implement the method for increasing the ticket rate according to the embodiment of the present invention, including:
carrying out synchronous ticket locking according to ticket booking information of a user;
generating a current order according to a synchronous ticket locking result for a user to pay for the current order, wherein the synchronous ticket locking result comprises the overtime or success of ticket locking;
and after the current order is generated, carrying out asynchronous ticket locking or asynchronous ticket drawing according to the result of the synchronous ticket locking and the result of user payment.
EXAMPLE five
The fifth embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method for increasing a ticket output rate according to the fifth embodiment of the present invention, where the method includes:
carrying out synchronous ticket locking according to ticket booking information of a user;
generating a current order according to a synchronous ticket locking result for a user to pay for the current order, wherein the synchronous ticket locking result comprises the overtime or success of ticket locking;
and after the current order is generated, carrying out asynchronous ticket locking or asynchronous ticket drawing according to the result of the synchronous ticket locking and the result of user payment.
Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "for example" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (12)
1. A method for increasing a ticket withdrawal rate, comprising:
carrying out synchronous ticket locking according to ticket booking information of a user;
generating a current order according to a synchronous ticket locking result for a user to pay for the current order, wherein the synchronous ticket locking result comprises the overtime or success of ticket locking;
after the current order is generated, asynchronous ticket locking or asynchronous ticket drawing is carried out according to the result of the synchronous ticket locking and the result of user payment;
after the current order is generated, performing asynchronous ticket locking or asynchronous ticket drawing according to the result of the synchronous ticket locking and the result of user payment, comprising the following steps:
when the result of the synchronous ticket locking is that the ticket locking is overtime, carrying out asynchronous ticket locking, and carrying out asynchronous ticket drawing according to the result of the asynchronous ticket locking and the result of user payment;
and when the result of the synchronous ticket locking is successful, performing asynchronous ticket drawing according to the result of the payment of the user.
2. The method for increasing the ticket drawing rate according to claim 1,
when the result of the synchronous ticket locking is that the ticket locking is overtime, asynchronous ticket locking is carried out, and asynchronous ticket drawing is carried out according to the result of the asynchronous ticket locking and the result of user payment, and the method comprises the following steps:
when the synchronous ticket locking result is that the ticket locking is overtime, asynchronous ticket locking is carried out, and when the asynchronous ticket locking is successful, whether the payment result of the user is successful or not is judged;
when the payment result of the user is successful, asynchronous ticket drawing is carried out, otherwise, the ticket source is released;
when the result of the synchronous ticket locking is successful, asynchronous ticket drawing is carried out according to the result of the payment of the user, and the method comprises the following steps:
when the ticket locking result is successful, judging whether the payment result of the user is successful;
and when the payment result of the user is successful, asynchronous ticket drawing is carried out, otherwise, the ticket source is released.
3. The method for increasing the ticket drawing rate according to claim 1, wherein before the synchronous ticket locking according to the ticket booking information of the user, the method further comprises the following steps:
acquiring asynchronous control time, wherein the asynchronous control time is pre-configured according to service information of each provider, the service information comprises maximum ticket locking time, maximum ticket issuing time, a sale prohibition period and maximum interface capacity supported by each provider, and the asynchronous control time comprises the asynchronous ticket locking time, the asynchronous ticket issuing time and retry times and frequency of the asynchronous ticket locking and the asynchronous ticket issuing;
correspondingly, the method further comprises the following steps:
before the asynchronous ticket locking or the asynchronous ticket drawing is successful, the retries are carried out according to the retries and the frequency of the asynchronous ticket locking and the asynchronous ticket drawing, and the time of the asynchronous ticket locking or the time of the asynchronous ticket drawing is not exceeded.
4. The method for increasing the ticket drawing rate according to claim 3, wherein the asynchronous control time further comprises unpaid time and time spent paying to draw a ticket;
the unpaid time is the time between the payment request sent to the user and the feedback information of successful payment, and is used for monitoring whether the payment process is completed within the unpaid time;
the time from the payment to the ticket drawing is the time from the payment request to the asynchronous ticket drawing success, and the time is used for monitoring whether the asynchronous ticket drawing process is completed within the time from the payment to the ticket drawing after the payment request is initiated to the user.
5. The method for increasing a ticket withdrawal rate of claim 1, further comprising:
and realizing the operations of asynchronous ticket locking and asynchronous ticket drawing by utilizing an NMQ framework, and before the asynchronous ticket locking or asynchronous ticket drawing succeeds, carrying out duplicate removal on repeated asynchronous ticket locking or asynchronous ticket drawing requests.
6. An apparatus for increasing a ticket output rate, comprising:
the synchronous ticket locking module is used for carrying out synchronous ticket locking according to ticket booking information of a user;
the order generation module is used for generating a current order according to a synchronous ticket locking result so that a user can pay for the current order, wherein the synchronous ticket locking result comprises the overtime or success of the ticket locking;
the asynchronous module is used for carrying out asynchronous ticket locking or asynchronous ticket drawing according to the result of the synchronous ticket locking and the result of user payment after the current order is generated;
the asynchronous module comprises:
the asynchronous ticket locking unit is used for carrying out asynchronous ticket locking when the result of synchronous ticket locking is that the ticket locking is overtime;
and the asynchronous ticket issuing unit is used for performing asynchronous ticket issuing according to the result of the user payment or performing asynchronous ticket issuing according to the result of the asynchronous ticket locking and the result of the user payment when the result of the synchronous ticket locking is that the ticket locking is successful.
7. The apparatus for increasing a ticket drawing rate according to claim 6, wherein the asynchronous ticket drawing unit is specifically configured to:
when the ticket locking result is successful, judging whether the payment result of the user is successful; when the payment result of the user is successful, asynchronous ticket drawing is carried out, otherwise, the ticket source is released; or
When the asynchronous ticket locking is successful, judging whether the payment result of the user is successful; and when the payment result of the user is successful, asynchronous ticket drawing is carried out, otherwise, the ticket source is released.
8. The apparatus for enhancing the ticket extraction rate of claim 6, further comprising:
the system comprises an asynchronous control time acquisition module, a ticket booking module and a ticket checking module, wherein the asynchronous control time acquisition module is used for acquiring asynchronous control time before synchronous ticket locking according to ticket booking information of a user, the asynchronous control time is pre-configured according to service information of each provider, the service information comprises maximum ticket locking time, maximum ticket issuing time, a sale prohibition period and maximum interface capacity supported by each provider, and the asynchronous control time comprises asynchronous ticket locking time, asynchronous ticket issuing time, and retry times and frequency of the asynchronous ticket locking and the asynchronous ticket issuing;
correspondingly, the device further comprises:
and the retry module is used for retrying according to the retry times and frequency of the asynchronous ticket locking and the asynchronous ticket drawing before the asynchronous ticket locking or the asynchronous ticket drawing succeeds, and the time of the asynchronous ticket locking or the asynchronous ticket drawing is not exceeded.
9. The apparatus for increasing the ticket drawing rate as claimed in claim 8, wherein the asynchronous control time further comprises unpaid time and time spent paying to draw the ticket;
the unpaid time is the time between the payment request sent to the user and the feedback information of successful payment, and is used for monitoring whether the payment process is completed within the unpaid time;
the time from the payment to the ticket drawing is the time from the payment request to the asynchronous ticket drawing success, and the time is used for monitoring whether the asynchronous ticket drawing process is completed within the time from the payment to the ticket drawing after the payment request is initiated to the user.
10. The apparatus for increasing the ticket drawing rate according to claim 6, wherein the apparatus utilizes an NMQ framework to realize the operations of asynchronous ticket locking and asynchronous ticket drawing;
the device further comprises:
and the duplicate removal module is used for removing duplicate of repeated asynchronous ticket locking or asynchronous ticket drawing requests before the asynchronous ticket locking or asynchronous ticket drawing succeeds.
11. A server, characterized in that the server comprises:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement a method of enhancing a ticket rate as recited in any of claims 1-5.
12. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method of increasing a ticket yield according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710915696.4A CN107679843B (en) | 2017-09-30 | 2017-09-30 | Method, device, server and storage medium for improving ticket drawing rate |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710915696.4A CN107679843B (en) | 2017-09-30 | 2017-09-30 | Method, device, server and storage medium for improving ticket drawing rate |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107679843A CN107679843A (en) | 2018-02-09 |
| CN107679843B true CN107679843B (en) | 2021-09-24 |
Family
ID=61138141
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710915696.4A Active CN107679843B (en) | 2017-09-30 | 2017-09-30 | Method, device, server and storage medium for improving ticket drawing rate |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107679843B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110297708B (en) * | 2018-03-22 | 2023-04-28 | 阿里巴巴集团控股有限公司 | Ticket issuing processing and scheduling method, server and ticket issuing platform |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101383057A (en) * | 2007-09-06 | 2009-03-11 | 上海遥薇实业有限公司 | Method for locking seat in sale of passenger transport tickets |
| CN102054204A (en) * | 2009-11-09 | 2011-05-11 | 阿里巴巴集团控股有限公司 | Method, system and device for automatically booking ticket |
| CN102201090A (en) * | 2011-07-13 | 2011-09-28 | 侯圣勇 | System and method for managing automatic ticketing |
| CN103886379A (en) * | 2014-03-27 | 2014-06-25 | 陆文清 | Optimized solution for online booking cinema ticket and other tickets |
| CN105678392A (en) * | 2015-12-25 | 2016-06-15 | 中国民航信息网络股份有限公司 | Prepaid flight seat sale system and method thereof |
| CN106709584A (en) * | 2017-03-20 | 2017-05-24 | 携程旅游网络技术（上海）有限公司 | Method and system for issuing ticket for air ticket order |
-
2017
- 2017-09-30 CN CN201710915696.4A patent/CN107679843B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101383057A (en) * | 2007-09-06 | 2009-03-11 | 上海遥薇实业有限公司 | Method for locking seat in sale of passenger transport tickets |
| CN102054204A (en) * | 2009-11-09 | 2011-05-11 | 阿里巴巴集团控股有限公司 | Method, system and device for automatically booking ticket |
| CN102201090A (en) * | 2011-07-13 | 2011-09-28 | 侯圣勇 | System and method for managing automatic ticketing |
| CN103886379A (en) * | 2014-03-27 | 2014-06-25 | 陆文清 | Optimized solution for online booking cinema ticket and other tickets |
| CN105678392A (en) * | 2015-12-25 | 2016-06-15 | 中国民航信息网络股份有限公司 | Prepaid flight seat sale system and method thereof |
| CN106709584A (en) * | 2017-03-20 | 2017-05-24 | 携程旅游网络技术（上海）有限公司 | Method and system for issuing ticket for air ticket order |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107679843A (en) | 2018-02-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111199401B (en) | Information processing method, device, terminal, server and storage medium | |
| CN115220876A (en) | Virtual resource creating method, device, program product, medium and electronic equipment | |
| CN107679843B (en) | Method, device, server and storage medium for improving ticket drawing rate | |
| US20210049561A1 (en) | Transaction processing method and device, electronic device and computer-readable storage medium | |
| CN112884181A (en) | Quota information processing method and device | |
| CN110782359A (en) | Policy recovery method and device, computer storage medium and electronic equipment | |
| CN108182628B (en) | Method, system, equipment and storage medium for ordering travel | |
| CN111124291A (en) | Data storage processing method and device of distributed storage system and electronic equipment | |
| CN110852819A (en) | Transaction processing method and device, storage medium and electronic equipment | |
| CN113778631A (en) | Distributed transaction compensation method and device, electronic equipment and readable storage medium | |
| CN110415112B (en) | Post-credit business processing method, device, equipment and storage medium | |
| CN113988844A (en) | Service subscription method, device and system | |
| CN109685508B (en) | Transaction data processing method and device, electronic equipment and readable storage medium | |
| CN111242753A (en) | Cross-platform operation control method and system | |
| CN111695985A (en) | System and method for processing voluntary deposit service of accumulation fund | |
| CN112163844A (en) | Capital supervision method, device, equipment and storage medium | |
| CN113781154A (en) | Information rollback method, system, electronic equipment and storage medium | |
| CN110910107A (en) | Transfer processing method, device, equipment and storage medium | |
| WO2023130612A1 (en) | Order payment method and apparatus, and server | |
| CN112950380B (en) | Block chain-based transaction consistency processing method and device | |
| EP4163843A1 (en) | Payment consolidation for a travel management system | |
| CN113821248B (en) | Service method of vehicle-end software, vehicle-end software and related equipment thereof | |
| CN112581179B (en) | Electronic coupon generation method and generation device | |
| CN117787963A (en) | Payment method, device, electronic equipment, medium and computer program product | |
| WO2021181822A1 (en) | Billing processing device, settlement system, billing processing method, and program |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |