Electronic ticket interaction processing method, apparatus, and device

Abstract

Embodiments of the present specification disclose an electronic ticket interaction processing method, device and equipment. The scheme applied to a user mobile terminal includes: displaying a target electronic ticket; after the user mobile terminal approaches a merchant terminal, if a ticket exchange gesture operation performed by the user on the target electronic ticket is received, the target electronic ticket is transmitted from the user mobile terminal to the merchant terminal through short-distance wireless communication; after the merchant terminal performs a cancellation processing on the target electronic ticket transmitted, a processing result of the target electronic ticket is displayed.

Description

[0001] This application is a divisional application of the invention patent application filed on October 31, 2024, with application number 202411545457.0 and entitled "Electronic Ticket Interactive Processing Method, Apparatus and Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This specification relates to the field of electronic ticketing, and in particular to methods, apparatus and equipment for electronic ticket interactive processing. Background Technology

[0003] With the development of internet technology and the widespread use of smartphones, more and more businesses can be conducted through corresponding applications on smartphones, bringing great convenience to people's lives.

[0004] The ticketing sector is one of the areas where people easily experience convenience. Traditionally, physical tickets were used, requiring ticket holders to keep them safe at all times. Lost tickets were either irreplaceable or involved a cumbersome replacement process. When a physical ticket was needed, a merchant's ticket inspector would manually check each ticket at the gate. The user would hand the physical ticket to the inspector, who would verify the information. If correct, a portion of the ticket would typically be torn or cut off for verification, and the remaining portion returned to the user. This entire process was labor-intensive, prone to errors, and inefficient, impacting the speed of entry. Therefore, electronic tickets have gradually gained increasing use. Compared to physical tickets, electronic tickets offer improved security, greater convenience, reduced manpower costs, lower error rates, and increased efficiency.

[0005] Currently, electronic ticket verification is usually based on QR codes. Each electronic ticket contains a QR code. At the ticket gate, users need to open the electronic ticket on their mobile phones, show the corresponding QR code to the merchant's ticket inspector, and wait for the inspector's next step. The inspector will open the merchant's terminal's scanning function, scan the QR code, wait for the scan to succeed, and then click confirm to complete the verification of the electronic ticket.

[0006] While QR code-based electronic ticket verification has advantages over physical tickets, it can still lead to cumbersome and inconvenient user experiences in practice. Therefore, a more convenient electronic ticket verification solution is needed. Summary of the Invention

[0007] This specification provides one or more embodiments of an electronic ticket interactive processing method, apparatus, device, and storage medium to solve the following technical problem: the need for a more convenient electronic ticket verification and cancellation scheme.

[0008] To solve the above-mentioned technical problems, one or more embodiments of this specification are implemented as follows:

[0009] This specification provides one or more embodiments of an electronic ticket interactive processing method, applied to a user's mobile terminal, the method comprising:

[0010] Display the target e-ticket;

[0011] After the user's mobile terminal approaches the merchant's terminal, if a hand gesture operation is received from the user for the target e-ticket, the target e-ticket is transmitted from the user's mobile terminal to the merchant's terminal via short-range wireless communication.

[0012] After the merchant terminal verifies the target e-ticket, it displays the processing result of the target e-ticket.

[0013] This specification provides one or more embodiments of an electronic ticket interactive processing method, applied to a merchant terminal, the method comprising:

[0014] After the user's mobile terminal approaches the merchant's terminal, the target electronic ticket transmitted from the user's mobile terminal is received via short-range wireless communication. The transmission is triggered by the user's hand gesture operation on the target electronic ticket displayed on the user's mobile terminal.

[0015] The received target electronic ticket is then processed for verification.

[0016] This specification provides one or more embodiments of an electronic ticket interactive processing device, applied to a user's mobile terminal, the device comprising:

[0017] The e-ticket display module shows the target e-ticket;

[0018] The electronic ticket delivery module, after the user's mobile terminal approaches the merchant terminal, if it receives a hand gesture operation performed by the user for the target electronic ticket, then transmits the target electronic ticket from the user's mobile terminal to the merchant terminal through short-range wireless communication.

[0019] The processing result display module displays the processing result of the target electronic ticket after the merchant terminal performs the verification process on the target electronic ticket.

[0020] This specification provides one or more embodiments of an electronic ticket interactive processing device, applied to a merchant terminal, the device comprising:

[0021] The electronic ticket receiving module receives the target electronic ticket transmitted from the user's mobile terminal via short-range wireless communication after the user's mobile terminal approaches the merchant's terminal. The transmission is triggered by the user's handing gesture operation on the target electronic ticket displayed on the user's mobile terminal.

[0022] The electronic ticket verification module performs verification processing on the received target electronic ticket.

[0023] This specification provides one or more embodiments of an electronic ticket interactive processing device, applied to a user's mobile terminal, the device comprising:

[0024] At least one processor; and,

[0025] A memory communicatively connected to the at least one processor; wherein,

[0026] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform:

[0027] Display the target e-ticket;

[0028] After the user's mobile terminal approaches the merchant's terminal, if a hand gesture operation is received from the user for the target e-ticket, the target e-ticket is transmitted from the user's mobile terminal to the merchant's terminal via short-range wireless communication.

[0029] After the merchant terminal verifies the target e-ticket, it displays the processing result of the target e-ticket.

[0030] This specification provides one or more embodiments of an electronic ticket interactive processing device, which is applied to a user's mobile terminal. The device includes:

[0031] At least one processor; and,

[0032] A memory communicatively connected to the at least one processor; wherein,

[0033] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform:

[0034] After the user's mobile terminal approaches the merchant's terminal, the target electronic ticket transmitted from the user's mobile terminal is received via short-range wireless communication. The transmission is triggered by the user's hand gesture operation on the target electronic ticket displayed on the user's mobile terminal.

[0035] The received target electronic ticket is then processed for verification.

[0036] This specification provides one or more embodiments of a non-volatile computer storage medium for use in a user mobile terminal. The medium stores computer-executable instructions, which are configured as follows:

[0037] Display the target e-ticket;

[0038] After the user's mobile terminal approaches the merchant's terminal, if a hand gesture operation is received from the user for the target e-ticket, the target e-ticket is transmitted from the user's mobile terminal to the merchant's terminal via short-range wireless communication.

[0039] After the merchant terminal verifies the target e-ticket, it displays the processing result of the target e-ticket.

[0040] This specification provides one or more embodiments of a non-volatile computer storage medium for use in a merchant terminal. The medium stores computer-executable instructions, which are configured as follows:

[0041] After the user's mobile terminal approaches the merchant's terminal, the target electronic ticket transmitted from the user's mobile terminal is received via short-range wireless communication. The transmission is triggered by the user's hand gesture operation on the target electronic ticket displayed on the user's mobile terminal.

[0042] The received target electronic ticket is then processed for verification.

[0043] The above-mentioned at least one technical solution adopted in one or more embodiments of this specification can achieve the following beneficial effects: Users can conveniently and quickly physically transfer the target electronic ticket to the merchant terminal by bringing their mobile terminal close to the merchant terminal and then performing a simple ticket handing gesture such as swiping the electronic ticket. Based on short-range communication such as near-field communication, the target electronic ticket can be quickly and physically transferred to the merchant terminal. The ticket inspector does not need to perform cumbersome operations such as opening a scanning page to scan the code. They only need to passively wait for the target electronic ticket to be transferred and then complete the remote verification of the target electronic ticket by performing a simple operation such as clicking to confirm. It is even possible to automatically confirm and verify the ticket at the merchant terminal without the need for a ticket inspector. The whole process is more reliable and convenient, which helps to improve the speed of user entry. In addition, it realizes a certain degree of simulation mapping of the action and feeling of handing over and receiving physical tickets. For both users and merchants, the interaction is more natural and smooth, and the experience is better. Attached Figure Description

[0044] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0045] Figure 1 A flowchart illustrating an electronic ticket interactive processing method provided in one or more embodiments of this specification;

[0046] Figure 2 A flowchart illustrating a pre-activated electronic ticket display scheme provided for one or more embodiments of this specification;

[0047] Figure 3 This is a flowchart illustrating a ticket verification scheme for a simultaneous entry ticket checking scenario provided in one or more embodiments of this specification.

[0048] Figure 4 This is a flowchart illustrating an electronic ticket package generation scheme for the scenario of multiple users in the same industry, provided by one or more embodiments of this specification.

[0049] Figure 5 A flowchart illustrating another electronic ticket interactive processing method provided in one or more embodiments of this specification;

[0050] Figures 6(a) to 6(c) Provided for one or more embodiments of this specification Figure 1 A schematic diagram of the page effect of one specific implementation scheme of the Chinese method;

[0051] Figure 7 A schematic diagram of the structure of an electronic ticket interactive processing device provided in one or more embodiments of this specification;

[0052] Figure 8 A schematic diagram of the structure of an electronic ticket interactive processing device provided in one or more embodiments of this specification;

[0053] Figure 9 A schematic diagram of the structure of an electronic ticket interactive processing device provided in one or more embodiments of this specification;

[0054] Figure 10 This is a schematic diagram of the structure of another electronic ticket interactive processing device provided in one or more embodiments of this specification. Detailed Implementation

[0055] This specification provides embodiments of electronic ticket interactive processing methods, apparatus, devices, and storage media.

[0056] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this application.

[0057] As mentioned in the background section, currently used QR code-based e-ticket verification solutions can still lead to inconvenient and redundant operations, especially in scenarios with long queues. Taking e-tickets for performances as an example, offline users often arrive early and wait a long time, making them very concerned about the speed of on-site e-ticket verification. QR code-based e-ticket verification remains cumbersome, and some users may even only start opening the QR code when they reach the ticket gate, further negatively impacting on-site verification efficiency.

[0058] To address these issues in existing technologies, this application considers that a seamless verification process can expedite user entry, thereby effectively enhancing the on-site experience and improving brand favorability. To achieve this, the solution in this application is based on proximity sensing between mobile phones. Users no longer need to access the ticketing details page to display a QR code, and merchants no longer need to open a QR code scanning interface. Users can send their purchased e-tickets to the merchant's mobile phone with a simple hand gesture (e.g., swiping up on the e-ticket). The merchant then completes the verification process by sensing the e-ticket, eliminating redundant steps for both parties and simulating real-world ticket checking. This effectively increases human interaction and enhances user brand favorability, memorability, and ease of use.

[0059] Based on this overall approach, the solution proposed in this application will be further explained below.

[0060] This application's solution involves at least user mobile terminals and merchant terminals used for ticket verification, and may also involve the server-side of one or both of them. Firstly, combining... Figure 1 It is mainly described from the perspective of the user's mobile terminal. Figure 1 This is a flowchart illustrating an electronic ticket interactive processing method provided in one or more embodiments of this specification. The executing entity of this process may include a user's mobile terminal, specifically a client or mini-program of a corresponding application mounted on the user's mobile terminal; the user's mobile terminal may be, for example, a smartphone, smartwatch, tablet computer, portable game console, etc.

[0061] Figure 1 The process includes the following steps:

[0062] S102: Display the target e-ticket.

[0063] The target e-ticket can be displayed in a simplified form (e.g., labeled with a simple graphic as an e-ticket) or in a more detailed form (e.g., showing a detailed e-ticket appearance, just like a physical ticket). At least one interactive graphic representing the target e-ticket should be displayed so that the user can later use that graphic to perform more vivid gesture operations on the target e-ticket.

[0064] The target e-ticket can be displayed after entering the designated page of the corresponding application or mini-program. This entry action can be achieved by the user manually accessing the page, or it can be automatically triggered adaptively and in a timely manner.

[0065] S104: After the user's mobile terminal approaches the merchant's terminal, if a hand gesture operation is received from the user for the target electronic ticket, the target electronic ticket is transmitted from the user's mobile terminal to the merchant's terminal via short-range wireless communication.

[0066] In one or more embodiments of this specification, the user's actions during physical ticket inspection are simulated to a certain extent to perform electronic ticket handing, so as to obtain a smoother user experience that is consistent with the traditional ticket handing experience.

[0067] First, both the user's mobile terminal and the merchant's terminal support a specified short-range wireless communication method, enabling them to exchange information remotely. This information primarily includes the target electronic ticket. The short-range wireless communication method can be Near Field Communication (NFC), which has a shorter communication distance, facilitating precise interaction between the correct targets. Similarly, other short-range wireless communication methods, such as infrared and Bluetooth, can also be used.

[0068] For the current user, they can bring their mobile terminal close to the merchant terminal for ticket checking. When the user's mobile terminal is close enough to the merchant terminal, short-range wireless communication is possible between the two. The user can then perform a hand gesture operation on the displayed electronic ticket, thus outwardly handing the electronic ticket to the merchant terminal with this hand gesture. Technically, the electronic ticket is transmitted to the merchant terminal via short-range wireless communication, thereby truly achieving the effect of handing over the ticket. This combination makes the user feel as if they are handing over their physical ticket (represented by the electronic ticket) to a real ticket checker (represented by the merchant terminal), making the experience and process smoother. In this case, the hand gesture operation in this application can be understood as a pre-defined simulated physical delivery gesture operation.

[0069] The level of simulation can be determined based on actual needs, and corresponding ticket handing gestures can be pre-set. Priority can be given to two dimensions: ease of use for users and / or close resemblance to real ticket handing actions.

[0070] For example, if these two dimensions are considered in a relatively balanced way, the ticket handing gesture operation could be a swipe gesture operation (for example, the user presses and holds the displayed target e-ticket with their finger and swipes it upwards or more precisely towards the merchant terminal). Then, after the user's mobile terminal approaches the merchant terminal, if a swipe gesture operation is received for the target e-ticket, it can be determined whether the swipe gesture operation belongs to the ticket handing gesture operation (for example, here it is mainly to determine whether the executed swipe gesture operation is sufficiently consistent with the predetermined standard).

[0071] For example, if the focus is more on facilitating efficient execution by the user, the ticket handing gesture could be a waving action on the user's mobile device (e.g., the user waving their mobile phone towards the merchant's terminal, or the user pressing and holding the displayed e-ticket and then swinging the entire phone towards the merchant's terminal, etc.). This is easy for the user to execute and thus helps improve efficiency.

[0072] For example, if we focus more on the dimension of resembling the actual ticket handing action, the ticket handing gesture could be, for instance, a handing-over gesture (e.g., the user presses down on the displayed electronic ticket with one finger or two fingers of both hands, and then hands the phone to the merchant terminal).

[0073] S106: After the merchant terminal verifies the target electronic ticket, it displays the processing result of the target electronic ticket.

[0074] In one or more embodiments of this specification, the merchant terminal receives the target e-ticket and can automatically display it for verification, or the merchant's staff can manually confirm and verify it. Verification can be performed directly on the merchant terminal's local machine. More reliably, the verification process can involve a corresponding server, with the merchant terminal interacting with the server regarding the target e-ticket (at least including the merchant terminal requesting verification of the target e-ticket from the server) to complete the verification.

[0075] Similarly, when or after submitting a ticket using a mobile terminal, users can interact with the corresponding server in a timely manner (where, if necessary, the server can request the user to manually confirm the cancellation again to prevent accidental submission) to confirm the cancellation of the target e-ticket. For example, after receiving a ticket submission gesture from the user's mobile terminal, the server can send a cancellation request for the target e-ticket to the server (or it may passively wait for the server to query for confirmation; in this case, the merchant terminal can interact with the server first, and then the server can query the user's mobile terminal), so that the server can cooperate with the merchant terminal to complete the cancellation process. Furthermore, after successful cancellation, the server can display the tear-off visual effect of the target e-ticket and corresponding status prompts to the user, so that the user can clearly understand the current status of the target e-ticket's cancellation.

[0076] The verification process may involve verifying relevant data, such as the electronic ticket number, verification number, and the random number to be verified used in this transaction, in order to establish trust relationships among multiple parties and confirm the user's true intentions.

[0077] pass Figure 1 This method allows users to easily and physically transfer their e-tickets to the merchant's terminal by simply bringing their mobile device close to the terminal and using gestures such as swiping the e-ticket. Based on short-range communication technologies like Near Field Communication (NFC), this allows for rapid and wireless transfer of the target e-ticket. Ticket inspectors no longer need to perform cumbersome tasks like opening a QR code scanning page; they simply wait for the e-ticket to arrive and then easily verify it by clicking "confirm." In some cases, the merchant's terminal can even automatically confirm and verify the ticket without an inspector. The entire process is more reliable and convenient, helping to speed up user entry. Furthermore, it simulates the tactile feedback of handing over and receiving physical tickets to a certain extent, resulting in a more natural and fluid interaction and a better experience for both users and merchants.

[0078] based on Figure 1 In addition to the method described herein, this specification also provides some specific implementation schemes and extension schemes of this method, which will be further explained below.

[0079] In the traditional QR code-based ticket verification process, users need to open the ticket, present it, and verify it; merchants need to open the QR code, wait for successful scanning, and click confirm to complete the verification. Both users and merchants need to perform three steps each, and these steps are not simultaneous, making the process redundant and inconvenient. However, the solution provided in this application allows merchants and users to execute actions more concurrently, with simplified procedures for both parties. The process is convenient and possesses a vivid and interactive feel reminiscent of natural physics. Based on this idea, although the solution in this application also needs to display the target e-ticket, it is not actually necessary to display the QR code corresponding to the target e-ticket. In the traditional solution, the QR code is used to represent the target e-ticket, and the QR code is located in a relatively deep access path. Therefore, in order to better reflect the convenience of this application compared to the traditional solution in the step of displaying the target e-ticket, a simpler form of the target e-ticket with a shallower access path can be displayed. In the simplified form, the QR code corresponding to the target e-ticket is not displayed. In this way, users can operate to display the target e-ticket more quickly, which not only improves convenience, but also improves privacy and security (QR codes are highly exposed and may be maliciously scanned before ticket inspection).

[0080] In one or more embodiments of this specification, a pre-activated electronic ticket display scheme is provided to further reduce the user's operational burden. See [link to relevant documentation]. Figure 2 , Figure 2 This is a flowchart illustrating the pre-activated e-ticket display scheme.

[0081] Figure 2 The process includes the following steps:

[0082] S202: Before the user's mobile terminal approaches the merchant terminal, determine whether an activation signal is received from the merchant terminal or an auxiliary activation terminal deployed in advance in coordination with the merchant terminal.

[0083] Since the influence range of merchant terminals is relatively limited, when there are many users waiting to have their tickets checked, one or more auxiliary activation terminals can be deployed near them based on their location distribution. For example, the merchant terminal can be deployed at the ticket gate corresponding to the target e-ticket, and the auxiliary activation terminals can be deployed along the ticket gate path (where users waiting to have their tickets checked will queue). For example, an appropriate distance can be set (e.g., a few meters or even tens of meters), and the auxiliary activation terminals can be deployed at locations close to the merchant terminal. In this way, the mobile terminals of the users closest to the ticket gate can be affected (i.e., activated).

[0084] The activation signal, especially, can be transmitted via a small-area directional antenna to precisely affect the desired group of users without affecting others in the vicinity who are not checking tickets.

[0085] S204: If so, under the activation of the activation signal, the corresponding business page will be automatically opened on the user's mobile terminal, and the target electronic ticket will be displayed on the business page.

[0086] In one or more embodiments of this specification, the target electronic ticket is actively displayed on the user's mobile terminal by an activation signal. If the user's mobile terminal is in a screen-off state, the screen can be automatically turned on and displayed again. In this way, no manual operation is required from the user, and the user can prepare for ticket inspection in advance. In particular, it can avoid the adverse effects on ticket inspection efficiency caused by users who do not prepare to display their electronic tickets in advance in traditional solutions.

[0087] Furthermore, activation signals can be responded to in a differentiated manner on the user's mobile terminal based on the actual situation. For example, if an activation signal is received and the user is currently performing an operation, the response to the activation signal can be temporarily suspended to avoid interrupting the user's operation and causing a bad experience. Or, by analyzing the strength or changes in the strength of the activation signal, the distance or the current ticket checking speed can be estimated, and the target electronic ticket can be automatically displayed at an appropriate time, rather than necessarily displaying the target electronic ticket immediately.

[0088] In one or more embodiments of this specification, in practical applications, there are situations where multiple people enter together for ticket checking, such as a family or a company team. For this situation, traditional QR code-based ticket checking solutions typically involve: for a family, one person usually buys tickets for the whole family, generating a corresponding number of QR codes, which need to be scanned sequentially by switching pages during ticket checking; for a company team, each member typically buys their own tickets, generates their own QR code, and presents their own QR code sequentially during ticket checking. It is clear that neither solution is efficient and suffers from the same problems mentioned in the background. Based on the basic solution of this application, further improvements are considered to enhance the ticket checking and verification efficiency in scenarios where multiple people enter together.

[0089] Figure 3 This is a flowchart illustrating a ticket verification scheme for a peer-to-peer entry scenario provided in one or more embodiments of this specification.

[0090] Figure 3 The process includes the following steps:

[0091] S302: On the user's mobile terminal, multiple target electronic tickets are acquired, and the electronic ticket package is automatically generated accordingly, wherein the multiple target electronic tickets correspond to different user identity information.

[0092] In one or more embodiments of this specification, multiple target e-tickets can be purchased through the same order on a user's mobile terminal, which is especially suitable for family scenarios. Of course, for team scenarios, one user can also purchase tickets for others.

[0093] S304: Display the electronic ticket package containing the multiple target electronic tickets.

[0094] The e-ticket package displays multiple target e-tickets as a whole, eliminating the need to switch between displaying different target e-tickets separately during the subsequent ticket checking process.

[0095] S306: After the user's mobile terminal approaches the merchant terminal, if a hand gesture operation is received from the user for the entire electronic ticket package, the entire electronic ticket package is transmitted from the user's mobile terminal to the merchant terminal via short-range wireless communication, so that the merchant terminal can perform verification processing on the entire electronic ticket package.

[0096] In this scenario, among the multiple users associated with an electronic ticket package, one user can perform a ticket handover gesture once, which enables ticket checking for all users, resulting in high efficiency.

[0097] Furthermore, for scenarios involving multiple users traveling together, since many individuals still purchase tickets individually rather than collectively, an electronic ticket package generation solution is provided. (See [link to solution]). Figure 4 , Figure 4 This is a flowchart illustrating the scheme.

[0098] S402: Before displaying the electronic ticket package containing multiple target electronic tickets, before one or more other mobile terminals of other users approach the user's mobile terminal, an identifiable dominant position signal is sent to the surrounding environment, so that each of the other mobile terminals responds to the dominant position signal and preferentially performs the short-range wireless communication with the user's mobile terminal.

[0099] In one or more embodiments of this specification, one of the multiple users in a group (their mobile terminal) collects everyone's electronic tickets in advance, similar to the method of collecting tickets via a hand gesture. This mobile terminal establishes its position by sending a dominance signal to its surroundings, enabling other users' mobile terminals to recognize that they need to pass their electronic tickets to this user's mobile terminal, rather than other mobile terminals, thus reducing the possibility of mistransmission.

[0100] In addition, whether it is a single-person or multi-person scenario, if necessary, users can withdraw the current remote transfer before the core verification is completed within a certain time.

[0101] S404: After one or more other users' other mobile terminals approach the user's mobile terminal, in response to the other user's handing gesture operation for the other target electronic ticket performed on the corresponding other mobile terminal, receive the target electronic ticket transmitted from the other mobile terminal via short-range wireless communication.

[0102] In this way, users' mobile terminals can quickly collect target e-tickets from other users in the same industry. To facilitate verification, users of the mobile terminals can also pre-specify the number of target e-tickets to be collected, and collection will automatically stop once the number is reached.

[0103] S406: Generate the electronic ticket package based on each of the target electronic tickets.

[0104] Within the e-ticket package, users can also view detailed identifiers for each user, such as nicknames. This makes it easy to generate e-ticket packages and verify the user to whom each e-ticket belongs.

[0105] The above description is primarily from the perspective of the user's mobile terminal. Based on the same idea, one or more embodiments of this specification also provide a flowchart of another electronic ticket interaction processing method, described from the perspective of the merchant terminal. See [link to relevant documentation]. Figure 5 Merchant terminals can be mobile terminals held by the merchant's staff or fixed devices installed at the ticket gate.

[0106] Figure 5 The method described above is applied to merchant terminals and mainly includes the following steps:

[0107] S502: After the user's mobile terminal approaches the merchant's terminal, the target electronic ticket transmitted from the user's mobile terminal is received via short-range wireless communication. The transmission is triggered by the user performing a ticket handing gesture operation on the target electronic ticket displayed on the user's mobile terminal.

[0108] S504: Perform verification processing on the received target electronic ticket.

[0109] The specifics will not be elaborated here; you can refer to the preceding explanations for a better understanding.

[0110] Based on the foregoing description, and more intuitively, one or more embodiments of this specification also provide an application scenario where... Figure 1 A specific implementation scheme of the Chinese method, and multiple page effect illustrations of the specific implementation scheme, combined with Figures 6(a) to 6(c) The diagram has been partially obscured due to privacy concerns, but this does not affect the understanding of the solution.

[0111] Figures 6(a) and 6(b) show the page effect on the user's mobile terminal, and Figure 6(c) shows the page effect on the merchant's terminal. This specific implementation plan, from the perspective of different terminals, is divided into the following two parts:

[0112] The first part, the process from when the user presents the e-ticket to when it is redeemed, includes:

[0113] 1. On the homepage of the corresponding ticketing application, users can long-press any e-ticket in the ticket list without clicking into the e-ticket details page. This will bring up the e-ticket's QR code and related entry information (as mentioned earlier, displaying a simplified version of the e-ticket without exposing the QR code is also acceptable). Users can use methods such as entering a password or facial recognition to authenticate and authorize the transaction information. After bringing the e-ticket close to the merchant terminal used for ticket verification, NFC technology is used to transfer the e-ticket. Swiping up and releasing the finger will transfer the e-ticket to the merchant terminal for display. The corresponding voucher number and verification number can be obtained from the e-ticket.

[0114] Referring to Figure 6(a), the left image shows the ticket list, the middle image shows that the user has popped up a certain e-ticket, and the page displays information such as the e-ticket's activity introduction, price, and QR code. The right image shows the effect of the e-ticket moving upward and scaling when the user presses and releases the finger, and then the e-ticket will continue to move upward to show that it has been passed on.

[0115] 2. After sending the electronic ticket verification request to the server, the front end displays the ticket verification process. If the verification is successful, it will be connected with the animated ticket tearing and the relevant status will be revealed. During the transaction, user data is encrypted and decrypted. After the animation ends, the ticket code will be displayed as used, and the ticket checking process is completed quickly.

[0116] See Figure 6(b), where the left image shows that the electronic ticket has been transmitted and is in the "checking" state, the middle image shows that it has been successfully verified and displays the corresponding animation, and the right image shows that the electronic ticket is in the "used" state, that is, it has been successfully verified.

[0117] Part Two, the process of merchants receiving and verifying e-tickets, includes:

[0118] 1. Merchants no longer need to enter the traditional QR code scanning page. The merchant terminal can receive the electronic ticket sent by the user by swiping up through NFC technology when it is close to the user. Clicking on the verification will trigger a verification and tearing animation to quickly complete the verification process.

[0119] 2. During verification, the merchant terminal or user mobile terminal can interact with the server to verify or compare information such as verification number, voucher number, and random number provided by one or more parties. If the verification passes or the comparison matches, the verification is successful; otherwise, the verification fails. Alternatively, the verification can be repeated to perform the same verification and comparison process or the verification can be abandoned. After successful verification and comparison, the payment system and transaction processing platform begin to process the user's electronic QR code information, automatically deducting funds from the user's account and transferring them to the merchant's account through the payment system. At this time, the interface will indicate that the verification was successful.

[0120] Referring to Figure 6(c), the left image shows the animation of the e-ticket being transmitted, which zooms in from the top and moves to the center. Merchants can click the button below to reject or cancel the e-ticket. The middle image shows the e-ticket in the "Canceling" state after clicking the cancel button. The right image shows the e-ticket has been successfully canceled.

[0121] As can be seen in this specific implementation plan, the device sensing between users and merchants is used to quickly and physically verify tickets remotely, reducing operation steps and improving ticket checking efficiency. Moreover, it adds fun and novelty by simulating everyday operation actions, making the operation experience smoother, easier to understand and operate, and improving the user experience.

[0122] Based on the same idea, one or more embodiments of this specification also provide apparatus and devices corresponding to the above methods, such as... Figures 7-10 As shown. The apparatus and equipment are capable of performing the above methods and related alternatives accordingly.

[0123] Figure 7 This is a schematic diagram of an electronic ticket interactive processing device provided in one or more embodiments of this specification. The device is applied to a user's mobile terminal and includes:

[0124] Electronic ticket display module 702 displays the target electronic ticket;

[0125] The electronic ticket delivery module 704, after the user's mobile terminal approaches the merchant terminal, if it receives a hand gesture operation performed by the user for the target electronic ticket, then transmits the target electronic ticket from the user's mobile terminal to the merchant terminal through short-range wireless communication.

[0126] The processing result display module 706 displays the processing result of the target electronic ticket after the merchant terminal performs the verification process on the target electronic ticket.

[0127] Optionally, the electronic ticket display module 702 displays a simplified version of the target electronic ticket, wherein the QR code corresponding to the target electronic ticket is not displayed in the simplified version.

[0128] Optionally, the electronic ticket display module 702 determines whether it receives an activation signal from the merchant terminal or an auxiliary activation terminal deployed in advance in cooperation with the merchant terminal before the user's mobile terminal approaches the merchant terminal.

[0129] If so, upon activation of the activation signal, the corresponding business page will automatically open on the user's mobile terminal, and the target electronic ticket will be displayed on the business page.

[0130] Optionally, the merchant terminal is deployed at the ticket gate corresponding to the target electronic ticket;

[0131] The auxiliary activation terminal is deployed on the ticket inspection path leading to the ticket gate.

[0132] Optionally, the ticket handing gesture operation includes a predetermined physical delivery simulated gesture operation.

[0133] Optionally, the electronic ticket delivery module 704, after the user's mobile terminal approaches the merchant's terminal, if it receives a swipe gesture operation performed on the target electronic ticket, determines whether the swipe gesture operation belongs to the ticket handover gesture operation.

[0134] Optionally, after receiving the user's hand gesture operation for the target electronic ticket, the electronic ticket delivery module 704 sends a verification request for the target electronic ticket to the server so that the server can cooperate with the merchant terminal to implement the verification process.

[0135] After the verification process is successful, the visual effect of tearing the target electronic ticket is displayed, along with corresponding status prompts.

[0136] Optionally, the electronic ticket display module 702 displays an electronic ticket package containing multiple target electronic tickets, and the ticket handing gesture operation is performed on the entire electronic ticket package;

[0137] The electronic ticket delivery module 704 transmits the entire electronic ticket package from the user's mobile terminal to the merchant terminal via short-range wireless communication, so that the merchant terminal can perform verification processing on the entire electronic ticket package.

[0138] Optionally, before displaying the electronic ticket package containing multiple target electronic tickets, and after one or more other users' other mobile terminals approach the user's mobile terminal, the electronic ticket display module 702, in response to the other user's handing gesture operation for other target electronic tickets performed on the corresponding other mobile terminal, receives the target electronic tickets transmitted from the other mobile terminal via short-range wireless communication.

[0139] The electronic ticket package is generated based on each of the target electronic tickets.

[0140] Optionally, the electronic ticket delivery module 704 sends an identifiable dominant position signal to the surrounding environment before one or more other mobile terminals of other users approach the user's mobile terminal, so that each of the other mobile terminals responds to the dominant position signal and preferentially conducts the short-range wireless communication with the user's mobile terminal.

[0141] Optionally, before displaying the electronic ticket package containing multiple target electronic tickets, the electronic ticket delivery module 704 automatically generates the electronic ticket package by purchasing the multiple target electronic tickets through the same order on the user's mobile terminal, wherein the multiple target electronic tickets correspond to different user identity information.

[0142] Optionally, the short-range wireless communication includes near-field communication.

[0143] Figure 8 This is a schematic diagram of another electronic ticket interactive processing device provided in one or more embodiments of this specification. The device is applied to a merchant terminal and includes:

[0144] The electronic ticket receiving module 802 receives the target electronic ticket transmitted from the user's mobile terminal via short-range wireless communication after the user's mobile terminal approaches the merchant's terminal. The transmission is triggered by the user performing a hand gesture operation on the target electronic ticket displayed on the user's mobile terminal.

[0145] The electronic ticket verification module 804 verifies the received target electronic ticket.

[0146] Figure 9 This is a schematic diagram of the structure of an electronic ticket interactive processing device provided in one or more embodiments of this specification. The device is applied to a user's mobile terminal and includes:

[0147] At least one processor; and,

[0148] A memory communicatively connected to the at least one processor; wherein,

[0149] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform:

[0150] Display the target e-ticket;

[0151] After the user's mobile terminal approaches the merchant's terminal, if a hand gesture operation is received from the user for the target e-ticket, the target e-ticket is transmitted from the user's mobile terminal to the merchant's terminal via short-range wireless communication.

[0152] After the merchant terminal verifies the target e-ticket, it displays the processing result of the target e-ticket.

[0153] Figure 10 This is a schematic diagram of another electronic ticket interactive processing device provided in one or more embodiments of this specification. The device is applied to a merchant terminal and includes:

[0154] At least one processor; and,

[0155] A memory communicatively connected to the at least one processor; wherein,

[0156] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform:

[0157] After the user's mobile terminal approaches the merchant's terminal, the target electronic ticket transmitted from the user's mobile terminal is received via short-range wireless communication. The transmission is triggered by the user's hand gesture operation on the target electronic ticket displayed on the user's mobile terminal.

[0158] The received target electronic ticket is then processed for verification.

[0159] Based on the same idea, one or more embodiments of this specification also provide a non-volatile computer storage medium for use in a user mobile terminal, wherein the medium stores computer-executable instructions, the computer-executable instructions being configured as follows:

[0160] Display the target e-ticket;

[0161] After the user's mobile terminal approaches the merchant's terminal, if a hand gesture operation is received from the user for the target e-ticket, the target e-ticket is transmitted from the user's mobile terminal to the merchant's terminal via short-range wireless communication.

[0162] After the merchant terminal verifies the target e-ticket, it displays the processing result of the target e-ticket.

[0163] Based on the same idea, one or more embodiments of this specification also provide another non-volatile computer storage medium for use in merchant terminals, wherein the medium stores computer-executable instructions, the computer-executable instructions being configured as follows:

[0164] After the user's mobile terminal approaches the merchant's terminal, the target electronic ticket transmitted from the user's mobile terminal is received via short-range wireless communication. The transmission is triggered by the user's hand gesture operation on the target electronic ticket displayed on the user's mobile terminal.

[0165] The received target electronic ticket is then processed for verification.

[0166] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0167] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0168] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0169] For ease of description, the above devices are described in terms of function, divided into various units. Of course, in implementing this specification, the functions of each unit can be implemented in one or more software and / or hardware components.

[0170] Those skilled in the art will understand that the embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the embodiments of this specification can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0171] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0172] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0173] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0174] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0175] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0176] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0177] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0178] This specification can be described in the general context of computer-executable instructions that are executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This specification can also be practiced in distributed computing environments, where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0179] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments of apparatus, devices, and non-volatile computer storage media are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0180] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0181] The above description is merely one or more embodiments of this specification and is not intended to limit this specification. Various modifications and variations can be made to the one or more embodiments of this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of one or more embodiments of this specification should be included within the scope of the claims of this specification.

Claims

1. An electronic ticket interactive processing method, applied to a user's mobile terminal, the method comprising: Send an identifiable dominant position signal to the surrounding environment so that other mobile terminals of one or more other users can identify, based on the dominant position signal, that they need to pass their own electronic ticket to the user's mobile terminal, rather than other mobile terminals; After the other mobile terminal approaches the user's mobile terminal, the target electronic ticket is received from the other mobile terminal via short-range wireless communication; Generate an electronic ticket package based on each of the target electronic tickets; The entire electronic ticket package is transferred from the user's mobile terminal to the merchant terminal, so that the merchant terminal can perform verification processing on the entire electronic ticket package.

2. The method of claim 1, further comprising: Display an e-ticket package containing multiple target e-tickets; After the user's mobile terminal approaches the merchant's terminal, if a hand gesture operation is received from the user for the entire electronic ticket package, the entire electronic ticket package is transmitted from the user's mobile terminal to the merchant's terminal via short-range wireless communication. After the merchant terminal verifies the entire electronic ticket package, it displays the processing result of the entire electronic ticket package.

3. The method as described in claim 2, wherein displaying the electronic ticket package containing multiple target electronic tickets specifically includes: An e-ticket package is displayed, which contains multiple simplified versions of the target e-tickets, wherein the QR code corresponding to the target e-ticket is not displayed in the simplified version.

4. The method as described in claim 2, wherein displaying the electronic ticket package containing multiple target electronic tickets specifically includes: Before the user's mobile terminal approaches the merchant's terminal, it is determined whether an activation signal is received from the merchant's terminal or an auxiliary activation terminal deployed in advance in coordination with the merchant's terminal. If so, upon activation of the activation signal, the corresponding business page will automatically open on the user's mobile terminal, and an e-ticket package containing multiple target e-tickets will be displayed on the business page.

5. The method as described in claim 4, wherein the merchant terminal is deployed at the ticket gate corresponding to the target electronic ticket; The auxiliary activation terminal is deployed on the ticket inspection path leading to the ticket gate.

6. The method of claim 2, wherein the ticket handing gesture operation includes a predetermined physical delivery simulated gesture operation.

7. The method as described in claim 2 or 6, wherein after the user's mobile terminal approaches the merchant's terminal, the method further comprises: If a swipe gesture is received for the target electronic ticket, it is determined whether the swipe gesture is a ticket handover gesture.

8. The method of claim 2, wherein after receiving the user's gesture operation for submitting the target electronic ticket, the method further comprises: Send a verification request for the target e-ticket to the server so that the server can cooperate with the merchant terminal to perform the verification process; After the verification process is successful, the visual effect of tearing the target electronic ticket is displayed, along with corresponding status prompts.

9. The method of claim 1, wherein the short-range wireless communication includes near-field communication.

10. An electronic ticket interactive processing device, applied to a user's mobile terminal, the device comprising: The electronic ticket delivery module sends an identifiable dominant position signal to the surrounding environment, so that other mobile terminals of one or more other users can identify, based on the dominant position signal, that they need to deliver their own electronic tickets to the user's mobile terminal, rather than to other mobile terminals. After the other mobile terminal approaches the user's mobile terminal, the target electronic ticket is received from the other mobile terminal via short-range wireless communication; The electronic ticket display module generates electronic ticket packages based on each of the target electronic tickets. The electronic ticket delivery module transmits the entire electronic ticket package from the user's mobile terminal to the merchant terminal, so that the merchant terminal can perform verification processing on the entire electronic ticket package.

11. The apparatus of claim 10, wherein the electronic ticket display module displays an electronic ticket package containing multiple target electronic tickets; The electronic ticket delivery module, after the user's mobile terminal approaches the merchant terminal, if it receives a hand gesture operation performed by the user on the entire electronic ticket package, then transmits the entire electronic ticket package from the user's mobile terminal to the merchant terminal via short-range wireless communication. Also includes: The processing result display module displays the processing result of the electronic ticket package after the merchant terminal has processed the verification of the electronic ticket package.

12. The apparatus of claim 11, wherein the electronic ticket display module displays a simplified version of the target electronic ticket, wherein... In this simplified form, the QR code corresponding to the target electronic ticket is not displayed.

13. The apparatus of claim 11, wherein the electronic ticket display module determines, before the user's mobile terminal approaches the merchant terminal, whether it receives an activation signal from the merchant terminal or an auxiliary activation terminal pre-deployed in conjunction with the merchant terminal; If so, upon activation of the activation signal, the corresponding business page will automatically open on the user's mobile terminal, and the target electronic ticket will be displayed on the business page.

14. The apparatus of claim 13, wherein the merchant terminal is deployed at the ticket gate corresponding to the target electronic ticket; The auxiliary activation terminal is deployed on the ticket inspection path leading to the ticket gate.

15. The apparatus of claim 11, wherein the ticket handing gesture operation includes a predetermined physical delivery simulated gesture operation.

16. The apparatus of claim 11 or 15, wherein the electronic ticket delivery module, after the user's mobile terminal approaches the merchant's terminal, if it receives a swipe gesture operation performed on the target electronic ticket, determines whether the swipe gesture operation belongs to the ticket delivery gesture operation.

17. An electronic ticket interactive processing device, applied to a user's mobile terminal, the device comprising: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform: Send an identifiable dominant position signal to the surrounding environment so that other mobile terminals of one or more other users can identify, based on the dominant position signal, that they need to pass their own electronic ticket to the user's mobile terminal, rather than other mobile terminals; After the other mobile terminal approaches the user's mobile terminal, the target electronic ticket is received from the other mobile terminal via short-range wireless communication; Generate an electronic ticket package based on each of the target electronic tickets; The entire electronic ticket package is transferred from the user's mobile terminal to the merchant terminal, so that the merchant terminal can perform verification processing on the entire electronic ticket package.

Images