TWM506330U - Electronic ticket buying system - Google Patents

Description

Electronic ticket purchase system

The present invention relates to an electronic ticket purchase system, and is particularly suitable for a system for electronic ticket purchase via a mobile device and direct access to an electronic ticket.

When making a ticket purchase, you can purchase it online through your personal computer, or you can purchase tickets at the ticketing endpoint or convenience. When using the computer to purchase tickets online, you need to use a credit card and other online credit card, and you need to use the convenience of super business or mail to the government to obtain the ticket, and will be charged a separate fee. If you want to pick up the ticket at the convenience store, you still need to operate the multimedia machine first, print the payment receipt to go to the cashier to make the payment and collect the ticket.

There is no handling fee for ticket purchase at the ticketing end point, but it needs to be at the end of the sales period and the number of ticketing endpoints is very small, which is also very inconvenient for users in some counties and cities. In order to facilitate the purchase of tickets, it is now possible to use the multimedia machine to purchase tickets, and then directly checkout at the cashier in the convenience store to obtain tickets immediately, except for exhibitions and concerts. In addition to event tickets such as stage plays, tickets such as credits or game points can also be purchased at a convenience store using a multimedia player, which is much more convenient for the user.

However, the method of purchasing tickets by using the multimedia machine requires the user to purchase the ticket from the convenience store, and when a plurality of users in the convenience store are waiting for the ticket purchase at the same time, the user in front needs to complete the purchase of the ticket. Tickets are purchased, and the purchase of tickets cannot be made immediately. After purchasing the ticket by online ticket purchase, although the user can purchase the ticket at any time and place and then go to the convenience store for payment and ticket collection, as mentioned above, it is still necessary to print the payment on the multimedia machine when the store is convenient. Documents, if other users are using multimedia machines, they also need to wait in line and lose the convenience of the convenience store.

In addition, when using a multimedia machine for ticket purchase, it is necessary to first print the thermal paper (ie, payment receipt) containing the payment information, then hold the thermal paper to the cashier counter to checkout, and then print the paper ticket. . Under the development of electronic and paperless and environmental protection appeals, many event tickets have also been sent using electronic coupons such as QR code, or you can directly enter electronic coupons without having to print out paper tickets. Voucher. One of the benefits of using electronic coupons is that you can directly enter the mobile phone without worrying about forgetting to bring paper coupons and not being able to enter the venue. Usually, the tickets have no other use after the event, so the use of electronic coupons can also be reduced. Waste of paper. However, such electronic coupons are limited to users who purchase tickets online and pay by credit card or transfer. For those who cannot use online ticket purchase or transfer payment, they still need to purchase physical tickets. Unable to choose to get an electronic ticket.

In view of this, the present invention provides an electronic ticket purchase system including: a first server, a second server, a mobile device, and a POS (Serviced Endpoint Sales System) cash register. The first server stores at least one ticket information, and can send a subscription result according to a ticket purchase request and at least one ticket information. And generating at least one electronic ticket according to a ticket information of the corresponding ticket purchase requirement in the at least one ticket information in response to a payment completion message. The generated at least one electronic ticket is resent. The second server is coupled to the first server via a network communication, can receive the order result from the first server, and generates and transmits a payment bar code according to a payment bar code request, and receives and stores the first server from the first server. Electronic ticket.

The mobile device connects the first server and the second server via network communication. The mobile device may generate a ticket purchase request with ticket information and transmit the ticket purchase request to the first server. After receiving the order result from the second server, the payment bar code request is transmitted to the second server according to the order result, the payment bar code from the second server is received and displayed, and at least one electronic ticket is received and displayed. The POS (Service Endpoint Sales System) cash register connects to the first server via network communication, scans the payment bar code displayed by the mobile device, and generates and sends a payment completion message to the first server.

With the above system, the user can use the mobile device to purchase the ticket, and when the purchase is completed, the payment information can be directly obtained on the mobile device and displayed on the screen. Then, the mobile device is used to pay the cashier counters of each payable channel. When the payment is completed, the electronic ticket can be received without the need to print the paper ticket by the cashier counter. In this way, you can use your mobile device to purchase tickets at any time and any place, and you can use the action to display payment information directly, without having to print another paper to pay. Furthermore, when the payment is completed, the electronic ticket can be directly received by the mobile device without printing the paper ticket, and there is no need to worry about forgetting to carry the ticket or losing the ticket.

1 is a schematic diagram of an electronic ticket purchase system according to a first embodiment of the present creation. The electronic ticket purchase system of the embodiment includes a first server 10, a second server 20, a mobile device 30, and a POS cash register 40. Here, the first server 10 may be a ticket server provided at the ticket provider side, or a ticket server storing a lot of purchase ticket information. The second server 20 may be a host installed in each ticket channel or a server provided in an electronic ticket system provider. The mobile device 30 can be a smart phone or a tablet or the like. The settings of the above servers are only examples. Each server can also be set in the same host or in different hosts. Each host can be located in the same place or in different places. This creation is not limited to this. Here, the first server 10, the second server 20, the mobile device 30, and the POS cash register 40 are communicably connected via the network 50. Here, the network 50 can be a Wide Area Network (WAN) or a Local Area Network (LAN).

Please refer to FIG. 1 to FIG. 4 at the same time. FIG. 2 is a schematic block diagram of the first server of the first embodiment of the present invention, and FIG. 3 is a schematic block diagram of the second server of the first embodiment. Figure 4 is a schematic block diagram of the mobile device of the first embodiment of the present invention. The first server 10 includes a network module 11, a processing module 12, and a database 13. The network module 11 communicatively connects the second server 20 and the mobile device 30 via the network 50. The processing module 12 is connected to the network module 11 and the database 13. The database 13 stores information for storing at least one ticket. For example, if it is an event ticket, the ticket information may include, but is not limited to, an event name, an event time, a number of tickets that can be purchased, location information, and the like. For the game points, the ticket information may include, but is not limited to, a game name, a point value, a serial number, a password, and the like.

The second server 20 includes a network module 21, a code generation module 22, an order generation module 23, and a data repository 24. The network module 21 communicatively connects the first server 10 and the mobile device 20 via the network 50. The barcode generation module 22 and the order generation module 23 are respectively connected to the network module 21 and the data repository 24.

The mobile device 30 includes a wireless module 31, a display device 32, a processing unit 33, and a storage unit 34. The wireless module 31 communicably connects the first server 10 and the second server 20 via the network 50. The processing unit 33 is connected to the wireless module 31, the display device 32, and the storage unit 34, respectively.

The network module 11, the processing module 12, the network module 21, the barcode generating module 22, the order generating module 23, the wireless module 31, and the processing unit 33 can be implemented by one or more processing elements. The database 13, data repository 24, and storage unit 34 may be implemented by one or more storage elements. Here, the storage element may be, for example, a hard disk, a memory card, a volatile memory, or a non-volatile memory, but is not limited thereto. The display device 32 can be a touch screen or a general display screen.

The processing unit 33 of the mobile device 30 generates a ticket purchase request having a ticket information. Here, the purchased ticket may be a general event ticket, such as an exhibition, a stage play or a concert, etc., and may also be a ticket for a premium or a game point. Next, we will first explain the ticket for the concert. The user can operate the mobile device 30 to browse and select a concert in which the ticket can be purchased. First, the processing unit 33 of the mobile device 30 can access the purchase page of the concert ticket via the wireless module 31 via the network 50 to the second server 20, and display the content of the purchase page via the display device 32 for use. Purchase. Upon completion of the selection of the desired concert ticket, processing unit 33 may generate a ticket purchase request with ticket information that has been selected for purchase. The processing unit 33 transmits the ticket purchase request to the first server 10 via the wireless module 31.

After receiving the ticket purchase request from the mobile device 30 via the network 50, the network module 11 of the first server 10 transmits an order based on the content of the ticket purchase request and the ticket information stored in the database 13. result. For example, the content of the ticket purchase request is the name of the concert, the date, the fare, the location, the number of sheets, and the number of sheets. The processing module 12 of the first server 10 is sent when the comparison database 13 is still available for purchase. A successful purchase order result. If there is no ticket available for purchase in the database 13, a result of the purchase failure is sent. The order result is sent to the second server 20 via the network 50. After receiving the order result, the second server 20 sends the order result to the mobile device 30 via the network 50.

At this point, the order for the ticket has been initially completed. If the order is successful, the next step is to pay the fee. The mobile device 30 receives the order result from the second server 20. If the received order result is a successful purchase, the mobile device 30 continues the subsequent payment. If the received order result is a purchase failure, the mobile device 30 needs to re-select the ticket to be purchased. Here, after the processing unit 33 of the mobile device 30 receives the order result via the wireless module 31, the received order result is displayed on the display device 32, and the order result may include the concert name, date, fare, location, and sheet. If the order is successful or fails, if the purchase result is successful, an option to display the payment barcode can be further displayed. In this way, the user can wait for the payment to be paid, and then click the option to display the payment barcode to display the payment barcode. When the processing unit 33 of the mobile device 30 receives the request for displaying the payment bar code generated by the option of displaying the payment bar code on the display device 32, the payment bar code request is transmitted to the second server 20 via the wireless module 31. .

After receiving the payment barcode request via the network module 21, the barcode generation module 22 of the second server 20 generates a payment barcode according to the payment barcode requirement. The generated payment barcode is transmitted to the mobile device 30 via the network module 21 via the network 50. The generated payment barcode is also stored in the data repository 34.

After the wireless module 31 of the mobile device 30 receives the payment barcode from the second server 20, the processing unit 33 displays the received payment barcode using the display device 32. At this time, the user can hold the mobile device 30 displaying the payment bar code to the POS cash register 40 to perform the payment process. In the payment process, the POS cash register 40 communicatively connects the first server 10 via the network 50 and scans the payment bar code displayed by the mobile device 30. The POS cash register 40 generates the information to be paid by scanning the payment barcode. After the user pays the fee according to the payment information, the POS cash register 40 generates and sends a payment completion message to the first server 10 according to the payment payment information in response to the payment confirmation signal.

The network module 11 of the first server 10 receives the payment completion message via the network 50, and the processing module 12 generates an electronic ticket based on the ticket information corresponding to the ticket purchase request in response to the payment completion message. Continuing the previous example, the ticket purchase ticket information is the concert name, date, fare, location and number of tickets. Upon receipt of the completion payment completion message, the electronic ticket is generated based on the ticket information. Then, the processing module 12 of the first server 10 sends the electronic ticket to the second server 20 via the network module 11.

After the network module 21 of the second server 20 receives the electronic ticket from the first server 10 via the network 50, the order generating module 23 generates an order information according to the electronic ticket and stores the order information in the data. In database 24. The order information may include an order number and an electronic ticket. Then, the order information is transmitted from the network module 21 to the mobile device 30 via the network 50. After receiving the order information via the wireless module 31, the processing unit 33 of the mobile device 30 may also store the order information of the electronic ticket in the storage unit 34, or further display the order information or the order information by using the display device 32. The electronic ticket in the middle. Continuing the above example, after receiving the order information, the user can select the content of the electronic ticket, and the processing unit 33 of the mobile device 30 displays the order information, such as a concert, through the display device 32 after receiving the request for displaying the order information. Information such as name, date, fare, location, and number of sheets, or simply a bar code containing the aforementioned ticket information. The user can display the electronic ticket to read the admission when he wants to enter the venue, without having to print out the paper ticket.

Thereby, the user can use the mobile device 30 to purchase the ticket, and after the purchase is completed, the payment information can be directly obtained on the mobile device 30 and displayed on the display device 32. Next, the mobile device 30 is further charged to the POS cash register 40 of the ticket purchase path, and when the payment is completed, the mobile ticket can be received by the mobile device 30 without printing the paper ticket by the POS cash register 40. In this way, the purchase of the ticket can be performed anytime and anywhere by using the mobile device 30, and the payment information can be directly displayed by the action display 30, and the paper can be paid without separately printing the paper. Moreover, when the payment is completed, the electronic ticket can be directly received by the mobile device 30 without printing the paper ticket, and there is no need to worry about forgetting to carry the ticket or losing the ticket.

In addition, the purchase of event tickets is not limited to the above-mentioned concert tickets, but also includes tickets for various activities such as tickets, exhibitions, and stage plays. Ticket information, ordering results, e-tickets and order information required for ticket purchases will also display different information depending on the event ticket purchased. For example, in the case of a ticket, each information content may include the type of ride, the date of travel, the starting point, the destination, the fare and the number of sheets, and the exhibition name, the date of the exhibition, and the fare.

Next, please refer to FIG. 5, which is a schematic block diagram of the second server of the second embodiment of the present invention. The structure of the electronic ticket purchase system in this embodiment is substantially the same as that of the first embodiment, and the same components as those of the first embodiment are denoted by the same reference numerals, and the same components or structures will not be described again. . Please refer to the figures 1, 2, 4 and 5 at the same time. In some embodiments, the second server 20 further includes a ticket confirmation module 25, a member database 26 and a member verification module 27. The ticket verification module 25 is connected to the network module 21, and the member verification module 27 is connected to the network module 21 and the member database 26.

When the user wants to use the mobile device 30 to purchase a ticket, in order to be able to identify the ticket purchaser, the member login action may be performed first, so that the purchased electronic ticket can be stored for the member. In this way, when using different mobile devices and wanting to obtain the purchased electronic coupons, only the member login is required to view the electronic coupons that have been purchased. After the user first inputs the member account and password by using the user interface of the mobile device 30, the processing unit 33 executes the login procedure according to the received member account and password. In the login process, the processing unit 33 transmits the member login information including one of the member account and the password to the second server 20 via the wireless module 31 via the network 50. After the network module 21 of the second server 20 receives the member login information via the network 50, the member verification module 27 verifies whether the member login information corresponds to the member information already existing in the member database 26 according to the member login information; The successful login message is transmitted to the mobile device 30 via the network module 21 via the network 50. The wireless module 31 of the mobile device 30 receives the member login success message, that is, displays the ticket purchase page under the member login. The processing unit 33 of the mobile device 30 will bring in the member information in the ticket purchase request generated by the member login situation, so that the purchased electronic ticket can be stored corresponding to the member information.

In addition, in the embodiment, the processing module 12 of the first server 10 generates a serial number according to the ticket purchase request, and the network module 11 sends the serial number to the second server 20 through the network 50. The serial number will be associated with the content of the ticket purchase request, that is, the processing module 12 of the first server 10 will assign a serial number to each ticket purchase request. After the network module 21 of the second server 20 receives the serial number via the network 50, the ticket verification module 25 sends a ticket confirmation signal to the first servo via the network module 50 according to the serial number. 10. For example, if a concert ticket is purchased, and multiple users simultaneously operate their respective mobile devices for ticket purchase, a plurality of ticket ordering requests may be transmitted to the first server 10 in a short time. At this time, the processing module 12 of the first server 10 first assigns a set number to each ticket order, and transmits the serial number and the corresponding ticket purchase request from the network module 11 to the second through the network 50. Server 20.

Then, after receiving the ticket purchase request with the corresponding serial number, the network module 21 of the second server 20, by the ticket verification module 25 of the second server 20, will correspondingly purchase the ticket according to the serial number. The network module 21 transmits to the first server 10 via the network 50. After the network module 11 of the first server 10 receives the ticket purchase request including the serial number via the network 50, the processing module 12 of the first server 10 is further stored in the database 13 according to the serial number, the ticket purchase request, and the ticket purchase request. The ticket information is used to generate a subscription result, and the order result is transmitted by the network module 11 to the second server 20 via the network 50. After the network module 21 of the second server 20 receives the order result from the network 50, the network module 21 transmits the order result to the mobile device 30 via the network 50 again. Thereby, the ticket purchase request confirmation and the ticket matching are performed by sequentially transmitting the ticketing demand, thereby avoiding the problem that the ticket is repeatedly sold at the same position in the same concert.

Please refer to FIG. 6 and FIG. 7 respectively, which are schematic diagrams of the electronic ticket purchase system of the third embodiment and a schematic block diagram of the second server. The structure of the electronic ticket voucher system in this embodiment is substantially the same as that of the first embodiment, and the same components as the first embodiment are denoted by the same component symbols, and the same components or structures and connection relationships will also be No further explanation. Please refer to the figures 2, 4, 6 and 7 at the same time. In this embodiment, the electronic ticket purchase system further includes another mobile device 60, and the second server 20 further includes a ticket confirmation module 28 and a point. Ticket verification module 29.

The processing unit 33 of the mobile device 30, when receiving the ticket information corresponding to one of the selected electronic coupons, generates a ticket request including the ticket collector information and the selected electronic ticket, and transmits the ticket request through the network module. 11 is transmitted to the second server 20 via the network 50. For example, when a user purchases a plurality of tickets and wants to transfer one or more of the tickets to another user, the displayed device can be displayed and selected through the display device 32 of the mobile device 30. For the electronic ticket to be transmitted in the voucher, the user then inputs the information of the invoice to be transmitted. The processing unit 33 of the mobile device 30, after receiving the ticket collector information and the selected electronic ticket, generates a ticket request based on the ticket collector information and the selected electronic ticket. The ticket collector information may include a phone number, an email address, or a member account information, as long as the ticket collector information can be sent according to the information. Subsequently, the wireless module 31 of the mobile device 30 transmits the ticket request to the second server 20 via the network 50.

The network module 21 of the second server 20 receives the ticket request through the network 50, and the ticket confirmation module 28 generates a ticket result having a ticket verification code according to the ticket request and stores it in the data database 24 . At the same time, the network module 21 transmits the ticket result to the mobile device 30 via the network 50. In addition, the ticket verification module 28 of the second server 20 can also generate a ticket notification including a ticket verification code, and the network module 21 transmits a ticket through the network 50 according to the ticket information. One of the verification codes is notified to another mobile device 60. For example, when the ticket confirmation module 28 of the second server 20 receives the ticket request including the ticket collector information and the corresponding electronic ticket, after confirming that the ticket can be divided, the ticket is confirmed. The module 28 generates a ticket verification code corresponding to the ticket request. Next, the network module 21 transmits the result of the ticket containing the ticket verification code to the mobile device 30 via the network 50. After receiving the result of the ticket, the wireless module 31 of the mobile device 30 can be transmitted to the other mobile device 60 via the network 50 via the wireless module 31. Or, as described above, the ticket confirmation module 28 of the second server 20 generates a ticket notification including the ticket verification code, and then directly transmits the ticket information to the other through the network 50 via the wireless module 31. A mobile device 60.

After receiving the ticket verification code, the other mobile device 60 can use another mobile device 60 to open a user interface and input the received ticket verification code, and then transmit to the second servo via the network 50. The device 20 performs verification code verification to obtain an electronic ticket. After the network module 21 of the second server 20 receives the ticket verification code via the network 50, and after the ticket verification module 29 confirms that the ticket verification code is correct, the network module 21 transmits the corresponding score via the network 50. The electronic ticket of the ticket verification code is sent to another mobile device 60. At this time, in order to facilitate the management of the subsequent electronic ticket and the order, the order generating module 23 of the second server 20 can confirm the electronic code corresponding to the ticket verification code after the ticket verification module 29 confirms that the ticket verification code is correct. The ticket and the ticket collector information generate another order information and store the other order information in the data repository 24. Among them, another order information includes another order number, electronic ticket and ticket collector information. In addition, the order generating module 23 of the second server 20 can also update the order information stored in the data database 24, and delete the electronic ticket that has been selected and sent out from the order information to avoid duplication of the electronic ticket. send.

In this way, the user can purchase a plurality of electronic coupons to enjoy the discount, and then electronically distribute the electronic coupons to other users without having to print the coupons for distribution to other users.

Referring to FIG. 1 to FIG. 4 at the same time, the third embodiment of the present invention is to use the electronic ticket purchase system as shown in the first embodiment to purchase tickets such as game points. When the game points are to be purchased, the ticket information may include, but is not limited to, a game name, a point value, a serial number, a password, and the like. The system architecture of the present embodiment is substantially the same as that of the first embodiment, and the same components and structures will be denoted by the same reference numerals and will not be described again.

When the mobile device 30 is used for ticket purchase, the user can operate the mobile device 30 to browse and select tickets such as game points or credits that can be purchased. First, the processing unit 33 of the mobile device 30 can be connected to the second server 20 via the network 50 via the network 50 to read the purchase point of the game points or credits, and display the content of the purchase page via the display device 32. In order to facilitate the user to purchase. Upon completion of the selection of the desired game points or credits voucher, processing unit 33 may generate a ticket purchase request with ticket information that has been selected for purchase. The processing unit 33 transmits the ticket purchase request to the first server 10 via the wireless module 31.

After receiving the ticket purchase request from the mobile device 30 via the network 50, the network module 11 of the first server 10 transmits an order based on the content of the ticket purchase request and the ticket information stored in the database 13. result. For example, the content of the ticket purchase request is a game name, a point value, and the like. When the processing module 12 of the first server 10 has a corresponding game name and a point value in the comparison database 13, the purchase is possible. That is, a successful purchase order result is sent. If there is no ticket available for purchase in the database 13, a result of the purchase failure is sent. The order result is sent to the second server 20 via the network 50. After receiving the order result, the second server 20 sends the order result to the mobile device 30 via the network 50.

At this point, the order for the ticket has been initially completed. If the order is successful, the next step is to pay the fee. The mobile device 30 receives the order result from the second server 20. If the received order result is a successful purchase, the mobile device 30 continues the subsequent payment. If the received order result is a purchase failure, the mobile device 30 needs to re-select the ticket to be purchased. Here, after the processing unit 33 of the mobile device 30 receives the order result via the wireless module 31, the received order result is displayed on the display device 32, and the order result may include the game name, the point value, the purchase quantity, and the order success. Or failure, if the purchase result is successful, an option to display the payment barcode may be further displayed. In this way, the user can wait for the payment to be paid, and then click the option to display the payment barcode to display the payment barcode. When the processing unit 33 of the mobile device 30 receives the request for displaying the payment bar code generated by the option of displaying the payment bar code on the display device 32, the payment bar code request is transmitted to the second server 20 via the wireless module 31. .

After receiving the payment barcode request via the network module 21, the barcode generation module 22 of the second server 20 generates a payment barcode according to the payment barcode requirement. The generated payment barcode is transmitted to the mobile device 30 via the network module 21 via the network 50. The generated payment barcode is also stored in the data repository 34.

After the wireless module 31 of the mobile device 30 receives the payment barcode from the second server 20, the processing unit 33 displays the received payment barcode using the display device 32. At this time, the user can hold the mobile device 30 displaying the payment bar code to the POS cash register 40 to perform the payment process. In the payment process, the POS cash register 40 communicatively connects the first server 10 via the network 50 and scans the payment bar code displayed by the mobile device 30. The POS cash register 40 generates the information to be paid by scanning the payment barcode. After the user pays the fee according to the payment information, the POS cash register 40 generates and sends a payment completion message to the first server 10 according to the payment payment information in response to the payment confirmation signal.

The network module 11 of the first server 10 receives the payment completion message via the network 50, and the processing module 12 generates an electronic ticket based on the ticket information corresponding to the ticket purchase request in response to the payment completion message. According to the previous example, the coupon information purchased by the ticket purchase ticket is the game name, the point value and the purchase quantity. After receiving the completion payment completion message, a set of stored value serial number and password are selected according to the game name and the point value. The electronic ticket is generated according to the game name, the point value, the stored value serial number and the password. Then, the processing module 12 of the first server 10 sends the electronic ticket to the second server 20 via the network module 11.

After the network module 21 of the second server 20 receives the electronic ticket from the first server 10 via the network 50, the order generating module 23 generates an order information according to the electronic ticket and stores the order information in the data. In database 24. The order information may include an order number and an electronic ticket. Then, the order information is transmitted from the network module 21 to the mobile device 30 via the network 50. After receiving the order information via the wireless module 31, the processing unit 33 of the mobile device 30 may also store the order information of the electronic ticket in the storage unit 34, or further display the order information or the order information by using the display device 32. The electronic ticket in the middle. Continuing the above example, after receiving the order information, the user can select to view the contents of the electronic ticket, and the processing unit 33 of the mobile device 30 displays the order information, such as the game name, through the display device 32 after receiving the request for displaying the order information. Information such as point value, stored value number and password. The user can enter the stored value number and password in the game to be added, that is, the added value of the point is completed, and the paper ticket containing the stored value number is not required to be printed.

Thereby, the user can use the mobile device 30 to purchase the ticket, and after the purchase is completed, the payment information can be directly obtained on the mobile device 30 and displayed on the display device 32. Next, the mobile device 30 is further charged to the POS cash register 40 of the ticket purchase path, and when the payment is completed, the mobile ticket can be received by the mobile device 30 without printing the paper ticket by the POS cash register 40. In this way, the purchase of the ticket can be performed anytime and anywhere by using the mobile device 30, and the payment information can be directly displayed by the action display 30, and the paper can be paid without separately printing the paper. Moreover, the electronic ticket can also be directly received by the mobile device 30 after the payment is completed, without reprinting the paper ticket, and there is no need to worry about losing the ticket.

Although the present invention is disclosed above in the foregoing embodiments, it is not intended to limit the present invention. Any one skilled in the art can make some modifications and retouchings without departing from the spirit and scope of the present invention. The scope of patent protection shall be subject to the definition of the scope of the patent application attached to this specification.

10‧‧‧First server
11‧‧‧Network Module
12‧‧‧Processing module
13‧‧‧Database
20‧‧‧Second server
21‧‧‧Network Module
22‧‧‧ barcode generation module
23‧‧‧Order Generation Module
24‧‧‧Data Database
25‧‧‧With ticket confirmation module
26‧‧‧Member Database
27‧‧‧Member Verification Module
28‧‧‧Segment confirmation module
29‧‧‧Note verification module
30, 60‧‧‧ mobile devices
31‧‧‧Wireless Module
32‧‧‧Display device
33‧‧‧Processing unit
34‧‧‧ storage unit
40‧‧‧POS Cash Register
50‧‧‧Network

[Fig. 1] is a schematic diagram of an electronic ticket purchase system according to a first embodiment of the present invention; [Fig. 2] is a schematic block diagram of a first server according to the first embodiment of the present creation; [Fig. 3] a schematic block diagram of a second server according to the first embodiment of the present invention; [Fig. 4] is a schematic block diagram of a mobile device according to the first embodiment of the present creation; [Fig. 5] is based on the present creation 2 is a schematic block diagram of a second server according to a third embodiment of the present invention; [FIG. 7] is a schematic diagram of a third embodiment according to the present creation A schematic block diagram of the second server.

10‧‧‧First server

20‧‧‧Second server

30‧‧‧Mobile devices

40‧‧‧POS Cash Register

50‧‧‧Network

Claims (12)

An electronic ticket purchase system includes: a first server storing at least one ticket information, transmitting a subscription result according to a ticket purchase request and the at least one ticket information, responding to a payment completion message according to the at least one One of the ticket information corresponding to the ticket purchase request generates at least one electronic ticket, and sends the generated at least one electronic ticket; a second server is connected to the first via a network communication The server receives the subscription result from the first server, generates and transmits a payment barcode according to a payment barcode request, and receives and stores the at least one electronic ticket from the first server; The network communication connects the first server and the second server to generate the ticket purchase request with the ticket information, and transmits the ticket purchase request to the first server, and receives the second server from the second server The order result, according to the order result, transmitting the payment bar code request to the second server, receiving and displaying the payment bar code from the second server, and receiving and Displaying the at least one electronic ticket; and a POS (Service Endpoint Sales System) cash register, connecting the first server via the network communication, scanning the payment barcode displayed by the mobile device, and generating and transmitting the payment Complete the message to the first server. The electronic ticket electronic ticket purchase system of claim 1, wherein the first server comprises: a network module, wherein the second server and the mobile device are connected via the network communication; a group, connecting the network module, generating a serial number according to the ticket purchase request, sending the serial number to the second server via the network module, according to the serial number, the ticket purchase request and the at least one ticket The information generates the order result, and the order result is sent to the second server via the network module, and the at least one electronic ticket is generated according to the ticket information corresponding to the ticket purchase request in response to the payment completion message, and The network module sends the at least one electronic ticket to the second server; and a database storing the serial number, the order result, and the at least one electronic ticket ticket. The electronic ticket purchase system of claim 2, wherein the second server comprises: a network module, the first server and the mobile device are connected via the network; and a ticket confirmation mode The group is connected to the network module, sends a ticket confirmation signal to the first server according to the serial number, and receives the order result from the first server, and then sends the order result to the mobile device. The electronic ticket purchase system of claim 3, wherein the second server further comprises: a code generation module connected to the network module, generating the payment barcode according to the payment barcode requirement, and transmitting the payment Bar code to the mobile device; an order generating module, connecting the network module, receiving the at least one electronic ticket from the first server, and generating an order information according to the at least one electronic ticket, wherein the order information An order number and the at least one electronic ticket are included; and a data database is connected to the barcode generation module and the order generation module to store the payment barcode and the order information. The electronic ticket purchase system of claim 1, wherein the mobile device comprises: a wireless module, wherein the first server and the second server are communicably connected via the network; a display device; a processing unit Coupling the wireless module and the display device to generate the ticket purchase request having the ticket information, transmitting the ticket purchase request to the first server via the wireless module, and transmitting the wireless message according to the order result The module transmits the payment barcode request to the second server, displays the payment barcode and the at least one electronic ticket via the display device, and a storage unit, connects the processing unit, and stores the at least one electronic ticket. The electronic ticket purchase system of claim 5, wherein the processing unit of the mobile device receives the ticket holder information corresponding to the selected at least one electronic ticket, and transmits the information including the ticket holder and One of the selected at least one electronic ticket is requested to be sent to the second server. The electronic ticket purchase system as claimed in claim 5, further comprising another mobile device, wherein the second server transmits the notification of the one of the ticket verification codes to the other action according to the receipt information Device. The electronic ticket voucher system of any one of claims 6 or 7, wherein the invoicing information is a phone number or an e-mail address. The electronic ticket purchase system of claim 6, wherein the second server comprises: a network module, wherein the first server and the mobile device are connected via the network; a ticket confirmation module Connecting the network module, generating a ticket result having a one-way verification code according to the ticket request, and transmitting the result of the ticket to the mobile device; and a data database connecting the ticket confirmation module , store the ticket verification code and the ticket request. The electronic ticket purchase system of claim 9, wherein the second server further comprises: a ticket verification module, connected to the data database, and receiving a ticket confirmation message from one of the other mobile devices. The ticket confirmation message includes the ticket verification code, and when the ticket verification module confirms that the ticket verification code in the ticket confirmation message is correct, the at least one electronic ticket corresponding to the ticket verification code is transmitted to The other mobile device. The electronic ticket purchase system of claim 1, wherein the at least one electronic ticket comprises a stored value serial number and a password. The electronic ticket purchase system of claim 1, wherein the second server comprises: a network module, the first server and the mobile device are connected via the network; a member database, storing There is at least one member information; and a member verification module, connecting the network module and the member database, and verifying, according to the member login information, whether the member login information corresponds to the at least one member information in the member database.