Scenic spot ticket business distribution method and system
By setting up ticket distribution methods at the total sales and distribution ends in the scenic spot ticket distribution system, including ticket quota allocation and pre-sale request processing, the problem of overselling and ticketless in the peak season of scenic spots is solved, and the full utilization of sales capabilities and ticket conversion rate are achieved. Maximize the number of tickets to prevent scalpers from brushing tickets and ensure the confidentiality of user identity information.
Patent Information
- Application Number
- CN202410944416.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-15
- Publication Date
- 2024-11-08
AI Technical Summary
During the peak season, the oversale ticketing problem caused by multi-channel distribution in scenic spots has led to excessive flow of people, a decline in reputation and safety risks. The lack of tickets available at some distribution ends affects sales volume, resulting in loss of profits.
By establishing a ticket distribution system between the total sales end and the distribution end, the total sales end obtains ticket expected data and allocates ticket sales quota. The distribution end receives ticket purchase requests and forms cumulative ticket sales data. If the quota exceeds the limit, a pre-sale request will be sent. The pre-sale queue and ticket sales/refunds are uniformly processed, and encryption modules and identity verification modules are set to prevent repeated ticket purchases and ticket swipes.
It has achieved full use of sales capabilities on the distribution side, avoided overselling in scenic spots, maximized the overall ticket conversion rate, prevented scalpers from brushing tickets, ensured that user identity information is kept confidential, and improved the profit and customer satisfaction of the scenic spot.
Smart Images

Figure CN118917969A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of data processing, and in particular to a scenic spot ticket distribution method and system. Background Art
[0002] For scenic spots, the main means of revenue is ticket sales. With the development of the Internet, the sales channels for scenic spot tickets have also increased. The multi-channel distribution method can increase scenic spot ticket sales to a certain extent and spread the ticket sales costs of scenic spots. However, multi-channel distribution will also lead to the problem of difficult control of ticket sales channels. For example, one of the traditional ticket distribution methods is to directly authorize distributors to sell tickets without any restrictions on sales volume. This distribution method will lead to serious overselling in scenic spots during peak seasons, and the overload of tourists in scenic spots will lead to a decline in reputation and even safety risks.
[0003] Based on the above considerations, most scenic spots will limit the ticket sales quota of each distributor to ensure that the total number of tickets sold will not exceed the upper limit of the scenic spot's passenger flow. However, this will also cause some distribution ends with strong marketing methods or good sales channels to have no tickets to sell after reaching the ticket sales quota, while other distribution ends still have remaining tickets but no one is interested in buying them. This will affect the sales quota of the scenic spot as a whole and lead to profit losses for the scenic spot. Summary of the invention
[0004] The technical problem to be solved by the present invention is how to make full use of the ticket sales capacity of the distribution end to increase the ticket sales of the scenic spot while avoiding serious overbooking of the scenic spot.
[0005] One of the technical solutions adopted by the present invention to solve the technical problem is: a scenic spot ticket distribution method, including a general sales end and multiple distribution ends, the scenic spot ticket distribution method includes the following steps:
[0006] The total sales end obtains the expected total ticket sales data S1 of the scenic spot, and distributes ticket sales quota data m1 to each distribution end;
[0007] Each of the distribution terminals receives the ticket purchase request and forms the accumulated ticket sales data m2;
[0008] If the cumulative ticket sales data m2 of any of the distribution terminals is less than or equal to the ticket sales quota data m1, the distribution terminal processes the ticket purchase request and updates the cumulative ticket sales data m2;
[0009] If the cumulative ticket sales data m2 of any of the distribution terminals is greater than the ticket sales quota data m1, the distribution terminal sends a pre-sale request to the general sales terminal;
[0010] The general sales end receives pre-sale requests from various distribution ends and forms a pre-sale queue;
[0011] The current time t and the deadline T are obtained. When the current time t is equal to the deadline T, each of the distribution terminals stops receiving ticket purchase requests from the client.
[0012] The total sales end obtains the number of pre-sale requests and the real-time ticket total sales data S2 in the pre-sale queue, and sells and / or refunds the pre-sale requests according to the number of pre-sale requests, the expected ticket total sales data S1 and the real-time ticket total sales data S2.
[0013] Furthermore, the total sales end obtains the expected total ticket sales data S1 of the scenic spot and distributes ticket sales quota data m1 to each distribution end, including the following steps:
[0014] The total sales end obtains the expected total ticket sales data S1 and the number of distribution ends n of the scenic spot;
[0015] Obtain the historical sales data of each distribution terminal and assign sales weights to each distribution terminal based on the historical sales data;
[0016] The ticket sales quota data m1 is allocated to each distribution terminal according to the expected total ticket sales data S1, the number of distribution terminals n and the sales weight of each distribution terminal.
[0017] Furthermore, the sum of the sales weights of each distribution terminal is equal to n.
[0018] Furthermore, the general sales end receives pre-sale requests from each distribution end and forms a pre-sale queue, including the following steps:
[0019] The general sales end takes the upper limit P of the number of pre-sale requests;
[0020] If the actual number of pre-sale requests received by the real-time general sales end is less than the upper limit P of the number of pre-sale requests, the general sales end receives the pre-sale requests from each distribution end, and arranges them in sequence according to the initiation order of each pre-sale request to form a pre-sale queue;
[0021] If the number of pre-sale requests in the pre-sale queue is greater than or equal to the upper limit P of the number of pre-sale requests, the general sales end rejects subsequent pre-sale requests from the distribution end.
[0022] Furthermore, the upper limit of the number of pre-sale requests P = Q + K1*(S1-S2) and P≤K2*S1, wherein Q is a fixed value of the number of pre-sale requests and Q is a positive integer, K1 is a first pre-sale coefficient and K1 is a positive integer, K2 is a second pre-sale coefficient and 0.1≤K2≤K1.
[0023] Further, the total sales end obtains the number of pre-sale requests and the real-time ticket total sales data S2 in the pre-sale queue, and sells and / or refunds the pre-sale requests according to the number of pre-sale requests, the expected ticket total sales data S1 and the real-time ticket total sales data S2, including the following steps:
[0024] The total sales end obtains the number of pre-sale requests in the pre-sale queue and the real-time data of total ticket sales S2;
[0025] If S1-S2 is greater than 0, and the number of pre-sale requests is less than or equal to S1-S2, then the pre-sale request is processed for ticketing;
[0026] If S1-S2 is greater than 0, and the number of pre-sale requests in the pre-sale queue is greater than S1-S2, then the pre-sale requests whose number is equal to S1-S2 are processed for ticketing, and the remaining pre-sale requests are processed for ticketing and / or refunding;
[0027] If S1-S2 is equal to 0, the remaining pre-sale requests are processed for ticket sales and / or refunds.
[0028] Furthermore, the ticket selling and / or ticket refunding processing for the remaining pre-sale requests includes the following steps:
[0029] Get the oversold quantity;
[0030] If the number of the remaining pre-sale requests is less than or equal to the oversold number, ticket sales are performed on the remaining pre-sale requests;
[0031] If the number of the remaining pre-sale requests is greater than the oversold number, a ticket sale process is performed on the portion of the remaining pre-sale requests that is equal to the oversold number, and a ticket refund process is performed on the portion that exceeds the oversold number.
[0032] Furthermore, the scenic spot ticket distribution method also includes the following steps:
[0033] Each of the distribution terminals receives a request for ticket purchase and obtains verification information;
[0034] The distributor encrypts the verification information to obtain a unique identification code and sends it to the general sales end;
[0035] The general sales end checks whether the unique identification code is repeated;
[0036] If yes, the first verification result is fed back to the distribution end, and the distribution end processes the ticket purchase request for refund;
[0037] If not, the second verification result is fed back to the distribution end.
[0038] Another technical solution adopted by the present invention to solve its technical problem is: a scenic spot ticket distribution system, used to execute the scenic spot ticket distribution method as described above, the scenic spot ticket distribution system includes a main sales end and multiple distribution ends communicatively connected to the main sales end.
[0039] Furthermore, it also includes an encryption module and an identity authentication module;
[0040] The encryption module is provided at the distribution end, and is used to encrypt the verification information obtained by the distribution end and obtain a unique identification code;
[0041] The identity verification module is arranged at the general sales end, and is used to check whether the unique identification codes from each distribution end are repeated.
[0042] It can be seen from the above technical solutions that in this application, a scenic spot ticket distribution method can control the sales volume of each distribution end through the general sales end to fully utilize the sales capacity of each distribution end, and avoid the serious overselling problem of the scenic spot during the peak season by allocating ticket quotas to each distribution end. At the same time, the general sales end will uniformly handle the excess pre-sale requests of each distribution end to maximize the overall ticket conversion rate. In addition, the unified processing of pre-sale requests by the general sales end can prevent scalpers from swiping a large number of tickets by controlling a single distribution end.
[0043] In addition, in the present application, a scenic spot ticket distribution system can implement the above method through the communication connection between the general sales end and the distribution end. At the same time, the encryption module and the identity authentication module are set to avoid repeated ticket purchases by the same user and achieve the effect of keeping user identity information confidential. BRIEF DESCRIPTION OF THE DRAWINGS
[0044] The present invention is further described below in conjunction with the accompanying drawings and embodiments.
[0045] Figure 1 It is a flow chart of a scenic spot ticket distribution method in a specific implementation mode of the present invention;
[0046] Figure 2 This is a flow chart of allocating ticket quota data m1 to the distribution terminal in a specific implementation manner of the present invention;
[0047] Figure 3 A flowchart of forming a pre-sale queue in a specific implementation manner of the present invention;
[0048] Figure 4 This is a flowchart of processing the pre-sale request in a specific implementation manner of the present invention;
[0049] Figure 5 A flowchart of verifying user identity in a specific implementation manner of the present invention; DETAILED DESCRIPTION
[0050] In order to make the technical means, creative features, objectives and effects achieved by the present invention easy to understand, the present invention is further explained below in conjunction with specific implementation methods.
[0051] The technical scheme in the embodiment of the present invention is described clearly and completely below. Obviously, the embodiment described is only one of the embodiments of the present invention, rather than all the embodiments. Based on the embodiment of the present invention, other embodiments promoted by ordinary technicians in this field all belong to the scope of protection of the present invention.
[0052] This application provides the following embodiment, please refer to Figure 1 As shown, a scenic spot ticket distribution method includes a general sales end and multiple distribution ends, and the scenic spot ticket distribution method includes the following steps:
[0053] S10, the total sales end obtains the expected total ticket sales data S1 of the scenic spot, and distributes ticket sales quota data m1 to each distribution end;
[0054] S20, each of the distribution terminals receives the ticket purchase request and generates cumulative ticket sales data m2;
[0055] S21, if the cumulative ticket sales data m2 of any of the distribution terminals is less than or equal to the ticket sales quota data m1, the distribution terminal processes the ticket purchase request and updates the cumulative ticket sales data m2;
[0056] S22: If the cumulative ticket sales data m2 of any of the distribution terminals is greater than the ticket sales quota data m1, the distribution terminal sends a pre-sale request to the general sales terminal;
[0057] S31, the general sales end receives pre-sale requests from various distribution ends and forms a pre-sale queue;
[0058] S40, obtaining the current time t and the deadline T, and when the current time t is equal to the deadline T, each of the distribution terminals stops receiving ticket purchase requests from the client;
[0059] S50, the total sales end obtains the number of pre-sale requests and the real-time data S2 of total ticket sales in the pre-sale queue, and sells and / or refunds the pre-sale requests according to the number of pre-sale requests, the expected data S1 of total ticket sales and the real-time data S2 of total ticket sales.
[0060] Among them, the expected total ticket sales data S1 is specifically the total number of tickets expected to be sold in a single performance of the scenic spot. The expected total ticket sales data S1 can be set according to the optimal capacity of the scenic spot, or the number of performances and seats in the scenic spot. The ticket quota data m1 is specifically the upper limit of the number of tickets that can be sold by a single distribution end, and the cumulative ticket sales data m2 is specifically the number of tickets sold by a single distribution end. The real-time data S2 of total ticket sales is the total number of tickets actually sold in real time. The sale of scenic spot tickets through the above-mentioned scenic spot ticket distribution method can make full use of the marketing advantages of each distribution end during the peak season to maximize the sales of tickets. If some distribution ends still have remaining tickets when the deadline T is reached, the total sales end can directly allocate the unsold tickets to the distribution end with sales demand through pre-sale requests to maximize the profitability of the scenic spot, while limiting the overselling of each distribution end to avoid excessive flow of people in the scenic spot.
[0061] In addition, the ticket pools between various distribution terminals are not directly connected, which can prevent scalpers from controlling a certain distribution port and using a unified sales pool to swipe tickets in large quantities through the distribution port, leaving normal consumers with no tickets to buy.
[0062] In some specific embodiments, the accumulated ticket sales data m2 of each distribution terminal may be the same or different, and this application does not impose any specific limitation on this.
[0063] In some further embodiments, please refer to Figure 2 As shown, in step S10, the total sales end obtains the expected total ticket sales data S1 of the scenic spot, and distributes ticket sales quota data m1 to each distribution end, including the following steps:
[0064] S11, the total sales end obtains the expected total ticket sales data S1 of the scenic spot and the number of distribution ends n;
[0065] S12, obtaining historical sales data of each distribution terminal and assigning sales weights to each distribution terminal according to the historical sales data;
[0066] S13. Allocate ticket sales quota data m1 to each distribution terminal according to the expected total ticket sales data S1, the number of distribution terminals n and the sales weight of each distribution terminal.
[0067] The sales capacity of each distribution terminal is determined by the historical sales data of each distribution terminal, and then differentiated ticket quota allocation is performed to further improve the utilization of the marketing capacity of different distributors. In a specific embodiment, the expected total ticket sales data S1 is 100, the number of distribution terminals n is 5, and the sales weight of each distribution terminal is 1, then the ticket quota data m1 allocated to each distribution terminal is 20.
[0068] In some further embodiments, the sum of the sub-sales weights of each distribution terminal is equal to n. The sum of the sub-sales weights of each distribution terminal being equal to n can ensure that the total amount of ticket sales data m1 of each distribution terminal does not exceed the expected total ticket sales data S1, thereby avoiding overselling.
[0069] In some further embodiments, please refer to Figure 3 As shown, in step S30, the general sales end receives pre-sale requests from each distribution end and forms a pre-sale queue, including the following steps:
[0070] S31, the general sales terminal obtains the upper limit P of the number of pre-sale requests;
[0071] S32. If the actual number of pre-sale requests received by the real-time general sales end is less than the upper limit P of the number of pre-sale requests, the general sales end receives the pre-sale requests from each distribution end, and arranges them in sequence according to the initiation order of each pre-sale request to form a pre-sale queue;
[0072] S33. If the number of pre-sale requests in the pre-sale queue is greater than or equal to the upper limit P of the number of pre-sale requests, the general sales end rejects subsequent pre-sale requests from the distribution end.
[0073] In order to maximize the conversion of pre-sale requests in the pre-sale queue into actual ticket sales, it is necessary to set an upper limit on the number of pre-sale requests to avoid a large number of users being refunded tickets, which may lead to a decline in sales reputation. In some specific embodiments, the pre-sale requests entering the pre-sale queue can send corresponding notification information to the client through the distribution end, and the pre-sale requests rejected by the general sales end will directly send a message of no ticket or ticket purchase failure to the client from the distribution end.
[0074] In some embodiments, the number of the upper limit P of the number of pre-sale requests may be a fixed value.
[0075] In some further embodiments, the upper limit of the number of pre-sale requests P = Q + K1*(S1-S2) and P≤K2*S1, wherein Q is a fixed value of the number of pre-sale requests and Q is a positive integer, K1 is a first pre-sale coefficient and K1 is a positive integer, K2 is a second pre-sale coefficient and 0.1≤K2≤K1.
[0076] Among them, Q is a fixed value of the number of pre-sale requests, and the value of Q can be set according to the actual situation. The value of K1 can be 1, 2, 3, 4, 5. In some preferred embodiments, the value of K1 is less than or equal to 3. In the above embodiment, as the real-time data S2 of the total ticket sales continues to increase, the number of pre-sale request upper limit P will also decrease. With such a design, when the sales speed of all distribution terminals is close to the same, no pre-sale requests will appear in the early stage. Therefore, in the later stage of sales, that is, when S2 is close to S1, the number of P will also approach Q, which can control the pre-sale requests sent by some distribution terminals within the range that can be processed. In some cases, at the beginning of ticket sales, some distribution terminals with better sales can quickly reach the ticket sales quota data m1 before other distribution terminals. At this time, some distribution terminals will initiate pre-sale requests. When the sales capacity of other distribution terminals is poor, the design of P = Q + K1 * (S1-S2) can increase the number of pre-sale requests at the beginning of ticket sales to ensure that when there are a large number of remaining tickets at other distribution terminals in the later stage, the pre-sale requests in the pre-sale queue can digest these remaining tickets to ensure the sales benefits of the scenic spot. P ≤ K2 * S1 sets an upper limit on the pre-sale quantity to prevent the pre-sale quantity from exceeding the actual ticket sales capacity.
[0077] In some further embodiments, please refer to Figure 4 As shown, in step S50, the total sales end obtains the number of pre-sale requests and the real-time ticket total sales data S2 in the pre-sale queue, and sells and / or refunds the pre-sale request according to the number of pre-sale requests, the expected ticket total sales data S1 and the real-time ticket total sales data S2, including the following steps:
[0078] S51, the total sales terminal obtains the number of pre-sale requests in the pre-sale queue and the real-time data of total ticket sales S2;
[0079] S52: If S1-S2 is greater than 0, and the number of pre-sale requests is less than or equal to S1-S2, then ticketing processing is performed on the pre-sale request;
[0080] S53. If S1-S2 is greater than 0, and the number of pre-sale requests in the pre-sale queue is greater than S1-S2, ticket sales are performed for the pre-sale requests whose number is equal to S1-S2, and ticket sales and / or ticket refunds are performed for the remaining pre-sale requests;
[0081] S54. If S1-S2 is equal to 0, the remaining pre-sale requests are processed for ticket sales and / or ticket refunds.
[0082] Among them, by comparing the number of pre-sale requests and real-time sales data, the general sales end can process the pre-sale requests according to the expected total ticket sales data S1 and the real-time sales data S2. In this way, the demand can be met in time and sales can be maximized when the tickets are not sold out. According to the number of pre-sale requests in the pre-sale queue and the real-time ticket total sales data S2, the general sales end can flexibly process the pre-sale requests for ticket sales and / or refunds. In this way, ticket resources can be reasonably allocated according to actual conditions to ensure the accuracy and fairness of sales. By processing pre-sale requests in a timely manner, the general sales end can meet customers' ticket purchase needs and improve customer satisfaction and experience. At the same time, for pre-sale requests that exceed the expected total ticket sales data S1, the general sales end can process refunds to avoid overselling and improve customer trust.
[0083] In some further embodiments, in step S53 and / or step S54, the ticket selling and / or ticket refunding processing for the remaining pre-sale requests includes the following steps:
[0084] Get the oversold quantity;
[0085] If the number of the remaining pre-sale requests is less than or equal to the oversold number, ticket sales are performed on the remaining pre-sale requests;
[0086] If the number of the remaining pre-sale requests is greater than the oversold number, a ticket sale process is performed on the portion of the remaining pre-sale requests that is equal to the oversold number, and a ticket refund process is performed on the portion that exceeds the oversold number.
[0087] In some further embodiments, please refer to Figure 5 As shown, the scenic spot ticket distribution method also includes the following steps:
[0088] S60, each of the distribution terminals receives a ticket purchase request and obtains verification information;
[0089] S70, the distribution end encrypts the verification information to obtain a unique identification code and sends it to the general sales end;
[0090] S80, the general sales end checks whether the unique identification code is repeated;
[0091] S81. If yes, the first verification result is fed back to the distribution end, and the distribution end performs a refund process on the ticket purchase request;
[0092] S82. If not, feed back the second verification result to the distribution end.
[0093] Among them, the verification information can be the identity information of the ticket purchaser or other information that can identify the uniqueness of the user, such as facial information, fingerprint information, etc. In addition, by obtaining the verification information and generating a unique identification code through each distribution end, the general sales end can check whether the unique identification code is repeated. This can ensure that the same ticket purchase request will not be repeatedly processed by multiple distribution ends, avoid the situation of repeated ticket sales, and ensure the accuracy and fairness of ticketing. By obtaining the verification information and generating a unique identification code when the distribution end receives the ticket purchase request, the general sales end can quickly determine the uniqueness of the ticket purchase request when checking the unique identification code. This can improve the processing efficiency of ticket purchase requests and reduce unnecessary ticket refund processing and communication delays. By verifying and checking the ticket purchase request, the general sales end can promptly discover the repeated unique identification code and require the distribution end to process the ticket refund. This helps to prevent malicious requests and fraudulent behavior and maintain the security and trust of the scenic spot ticketing system.
[0094] The present application also provides the following embodiment: a scenic spot ticket distribution system for executing the scenic spot ticket distribution method as described above, wherein the scenic spot ticket distribution system includes a main sales end and a plurality of distribution ends communicatively connected to the main sales end.
[0095] In some further embodiments, the scenic spot ticket distribution system further includes an encryption module and an identity verification module;
[0096] The encryption module is provided at the distribution end, and is used to encrypt the verification information obtained by the distribution end and obtain a unique identification code;
[0097] The identity verification module is arranged at the general sales end, and is used to check whether the unique identification codes from each distribution end are repeated.
[0098] Among them, the working principle and adjustment method of the scenic spot ticket distribution system of the present invention can refer to the various embodiments listed in the above-mentioned scenic spot ticket distribution method, and will not be repeated here.
[0099] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing related hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media provided in this application and used in the embodiments may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (SSRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.
[0100] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, device, article or method including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, device, article or method. In the absence of further restrictions, an element defined by the sentence "includes a ..." does not exclude the presence of other identical elements in the process, device, article or method including the element.
[0101] The above shows and describes the basic principles, main features and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The above embodiments and descriptions are only for explaining the principles of the present invention. Without departing from the spirit and scope of the present invention, the present invention may have various changes and improvements, which fall within the scope of the present invention. The scope of the present invention is defined by the attached claims and their equivalents.
Claims
1. A scenic spot ticket distribution method, comprising a general sales end and multiple distribution ends, It is characterized in that The scenic spot ticket distribution method comprises the following steps: The total sales end obtains the expected total ticket sales data S1 of the scenic spot, and distributes ticket sales quota data m1 to each distribution end; Each of the distribution terminals receives the ticket purchase request and forms the accumulated ticket sales data m2; If the cumulative ticket sales data m2 of any of the distribution terminals is less than or equal to the ticket sales quota data m1, the distribution terminal processes the ticket purchase request and updates the cumulative ticket sales data m2; If the cumulative ticket sales data m2 of any of the distribution terminals is greater than the ticket sales quota data m1, the distribution terminal sends a pre-sale request to the general sales terminal; The general sales end receives pre-sale requests from various distribution ends and forms a pre-sale queue; The current time t and the deadline T are obtained. When the current time t is equal to the deadline T, each of the distribution terminals stops receiving ticket purchase requests from the client. The total sales end obtains the number of pre-sale requests and the real-time ticket total sales data S2 in the pre-sale queue, and sells and / or refunds the pre-sale requests according to the number of pre-sale requests, the expected ticket total sales data S1 and the real-time ticket total sales data S2.
2. According to a scenic spot ticket distribution method described in claim 1, It is characterized in that The total sales end obtains the expected total ticket sales data S1 of the scenic spot and distributes the ticket sales quota data m1 to each distribution end, including the following steps: The total sales end obtains the expected total ticket sales data S1 and the number of distribution ends n of the scenic spot; Obtain the historical sales data of each distribution terminal and assign sales weights to each distribution terminal based on the historical sales data; The ticket sales quota data m1 is allocated to each distribution terminal according to the expected total ticket sales data S1, the number of distribution terminals n and the sales weight of each distribution terminal.
3. According to a scenic spot ticket distribution method described in claim 2, It is characterized in that The sum of the sales weights of each distribution terminal is equal to n.
4. According to a scenic spot ticket distribution method described in claim 1, It is characterized in that The general sales end receives pre-sale requests from each distribution end and forms a pre-sale queue, including the following steps: The general sales end takes the upper limit P of the number of pre-sale requests; If the actual number of pre-sale requests received by the real-time general sales end is less than the upper limit P of the number of pre-sale requests, the general sales end receives the pre-sale requests from each distribution end, and arranges them in sequence according to the initiation order of each pre-sale request to form a pre-sale queue; If the number of pre-sale requests in the pre-sale queue is greater than or equal to the upper limit P of the number of pre-sale requests, the general sales end rejects subsequent pre-sale requests from the distribution end.
5. According to a scenic spot ticket distribution method as described in claim 4, It is characterized in that The upper limit of the number of pre-sale requests P = Q + K1*(S1-S2) and P≤K2*S1, wherein Q is a fixed value of the number of pre-sale requests and Q is a positive integer, K1 is the first pre-sale coefficient and K1 is a positive integer, K2 is the second pre-sale coefficient and 0.1≤K2≤K1.
6. According to a scenic spot ticket distribution method described in claim 1, It is characterized in that The total sales end obtains the number of pre-sale requests and the real-time ticket total sales data S2 in the pre-sale queue, and sells and / or refunds the pre-sale requests according to the number of pre-sale requests, the expected ticket total sales data S1 and the real-time ticket total sales data S2, including the following steps: The total sales end obtains the number of pre-sale requests in the pre-sale queue and the real-time data of total ticket sales S2; If S1-S2 is greater than 0, and the number of pre-sale requests is less than or equal to S1-S2, then the pre-sale request is processed for ticketing; If S1-S2 is greater than 0, and the number of pre-sale requests in the pre-sale queue is greater than S1-S2, then the pre-sale requests whose number is equal to S1-S2 are processed for ticketing, and the remaining pre-sale requests are processed for ticketing and / or refunding; If S1-S2 is equal to 0, the remaining pre-sale requests are processed for ticket sales and / or refunds.
7. According to a scenic spot ticket distribution method as described in claim 6, It is characterized in that The ticket selling and / or ticket refunding processing for the remaining pre-sale requests includes the following steps: Get the oversold quantity; If the number of the remaining pre-sale requests is less than or equal to the oversold number, ticket sales are performed on the remaining pre-sale requests; If the number of the remaining pre-sale requests is greater than the oversold number, a ticket sale process is performed on the portion of the remaining pre-sale requests that is equal to the oversold number, and a ticket refund process is performed on the portion that exceeds the oversold number.
8. According to a scenic spot ticket distribution method described in claim 1, It is characterized in that The scenic spot ticket distribution method also includes the following steps: Each of the distribution terminals receives a request for ticket purchase and obtains verification information; The distributor encrypts the verification information to obtain a unique identification code and sends it to the general sales end; The general sales end checks whether the unique identification code is repeated; If yes, the first verification result is fed back to the distribution end, and the distribution end processes the ticket purchase request for refund; If not, the second verification result is fed back to the distribution end.
9. A scenic spot ticket distribution system, It is characterized in that Used to execute the scenic spot ticket distribution method as described in any one of claims 1 to 7, the scenic spot ticket distribution system includes a main sales end and a plurality of distribution ends communicatively connected to the main sales end.
10. According to the scenic spot ticket distribution system described in claim 9, It is characterized in that It also includes encryption modules and authentication modules; The encryption module is provided at the distribution end, and is used to encrypt the verification information obtained by the distribution end and obtain a unique identification code; The identity verification module is arranged at the general sales end, and is used to check whether the unique identification codes from each distribution end are repeated.
