Ticket verification method and device

Abstract

Embodiments of the present application provide a ticket verification method and device. The ticket verification method comprises: receiving, by a verification device, a data packet broadcast by a user device through a Bluetooth protocol; the data packet containing a user identifier; obtaining authentication user information corresponding to the user identifier, the authentication user information comprising authentication user identity information and authentication user ticket information; collecting an image of a user to be verified, and extracting user identity information of the user to be verified based on the collected image; and performing ticket verification on the user to be verified based on the user identity information of the user to be verified, the authentication user identity information and the authentication user ticket information, to obtain a verification result. The embodiments of the present application can improve the efficiency and accuracy of ticket verification, and the user has no awareness of the verification process, thereby improving the user experience.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a ticket verification method and device. Background Technology

[0002] Ticket verification typically refers to the systematic verification of the authenticity, validity, and consistency between the ticket holder and the ticket during the entry process in scenarios such as tourism, transportation, and performances.

[0003] Traditional ticket verification mainly relies on active scanning technologies such as QR codes. However, QR codes are easily affected by factors such as fiber optic cables and dirt, and scanning congestion is prone to occur during peak periods (such as when the audience is concentrated before the start of a concert), resulting in excessively long verification response times.

[0004] Therefore, there is an urgent need for an efficient ticket verification solution. Summary of the Invention

[0005] In view of this, embodiments of this application provide a ticket verification scheme to at least partially solve the above-mentioned problems.

[0006] According to a first aspect of the embodiments of this application, a ticket verification method is provided, applied to a verification device, the method comprising: The system receives data packets broadcast by a user device via the Bluetooth protocol; the data packets contain a user identifier. Obtain the authenticated user information corresponding to the user identifier, wherein the authenticated user information includes: authenticated user identity information and authenticated user ticketing information; Information is collected from users to be verified to obtain their identity information; Based on the identity information of the user to be verified, the identity information of the certified user, and the ticketing information of the certified user, ticket verification is performed on the user to be verified to obtain the verification result.

[0007] According to a second aspect of the embodiments of this application, a ticket verification method is provided, applied to a user equipment, the method comprising: When the user equipment is within the preset sensing range of the verification device, the user equipment reads the user identifier; The user equipment broadcasts a data packet containing the user identifier via Bluetooth protocol, so that the verification device can perform ticket verification for the user to be verified based on the authentication user information corresponding to the user identifier, and obtain the verification result.

[0008] According to a third aspect of the embodiments of this application, a verification device is provided, comprising: A first Bluetooth controller is configured to receive data packets broadcast by a user device via the Bluetooth protocol; the data packets contain a user identifier. The authentication information acquisition module is used to acquire the authentication user information corresponding to the user identifier, the authentication user information including: authentication user identity information and authentication user ticketing information; The information collector is used to collect information from users to be verified and obtain their identity information. The verification module performs ticket verification on the user to be verified based on the identity information of the user to be verified, the identity information of the certified user, and the ticketing information of the certified user, and obtains the verification result.

[0009] According to a fourth aspect of the embodiments of this application, a user equipment is provided, comprising: The identifier reading module is used to read the user identifier when the user equipment is within the preset sensing range of the verification device; The second Bluetooth controller is used by the user equipment to broadcast a data packet containing the user identifier via the Bluetooth protocol, so that the verification device can perform ticket verification for the user to be verified based on the authentication user information corresponding to the user identifier, and obtain the verification result.

[0010] According to a fifth aspect of the embodiments of this application, a ticket verification system is provided, including: a verification device as described in the third aspect above, and a user device as described in the fourth aspect above.

[0011] According to the ticket verification scheme provided in this application embodiment, when the user equipment is within the sensing range of the verification device, the Bluetooth broadcast function of the user equipment will be automatically activated. The verification device receives the data packet containing the user identifier broadcast by the user equipment via the Bluetooth protocol. The verification device obtains the authenticated user information corresponding to the user identifier. The authenticated user information includes: authenticated user identity information and authenticated user ticket information. The verification device collects information on the user to be verified and extracts the identity information of the user to be verified based on the collected image. Based on the identity information of the user to be verified, the authenticated user identity information, and the authenticated user ticket information, the verification device performs ticket verification on the user to be verified and obtains the verification result.

[0012] In this embodiment, when a user device approaches and enters the verification device's sensing range, a ticket verification process based on Bluetooth broadcasting is automatically triggered. This involves reconstructing the Bluetooth near-field communication protocol to send the user identifier from the user device to the verification device in real time. Then, based on the binding relationship between the user identifier and the authenticated user information, the authenticated user information corresponding to the user identifier is obtained. Finally, the obtained authenticated user information is compared with the collected user information to be verified to achieve ticket verification. This process deeply couples near-field sensing detection with the real-name authentication link, thereby enabling near-field sensing actions to trigger ticket verification. On one hand, this application triggers the ticket verification process only when the user device is within the near-field sensing range of the verification device, thus effectively ensuring the accuracy of the verification operation. On the other hand, during the verification process, since the user identifier is transmitted between the user device and the verification device via Bluetooth broadcasting, and the verification process does not require manual user intervention, the transmission response is fast and imperceptible to the user.

[0013] In summary, the embodiments of this application can improve the efficiency and accuracy of ticket verification, and the verification process is seamless for the user, thus improving the user experience. Attached Figure Description

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

[0015] Figure 1 This is a schematic diagram of an exemplary ticket verification system to which the ticket verification method of this application is applicable; Figure 2 This is a flowchart illustrating the steps of a ticket verification method according to an embodiment of this application. Figure 3 This is a flowchart illustrating the steps of another ticket verification method according to an embodiment of this application; Figure 4 This is a schematic diagram of the structure of a verification device according to an embodiment of this application; Figure 5 This is a schematic diagram of the structure of a user equipment according to an embodiment of this application; Figure 6 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application; Figure 7 This is an illustration of another ticket verification system according to an embodiment of this application; Figure 8 This is a schematic diagram of the ticket verification interaction of a ticket verification system according to an embodiment of this application. Detailed Implementation

[0016] To enable those skilled in the art to better understand the technical solutions in the embodiments of this application, the technical solutions in the embodiments of this application 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 application, all other embodiments obtained by those skilled in the art should fall within the protection scope of the embodiments of this application.

[0017] See Figure 1 , Figure 1 This is a schematic diagram of an exemplary ticket verification system for which the ticket verification method of this application is applicable. For ease of understanding, it is first described in conjunction with... Figure 1 The application scenarios of the ticket verification method provided in the embodiments of this application will be explained.

[0018] like Figure 1 As shown, the system 100 may include an authentication device 102 and a user device 104, and the authentication device 102 and the user device 104 transmit data via Bluetooth protocol.

[0019] Verification device 102 is the on-site execution terminal device of the ticket verification system. It is mainly used to collect relevant information of the user to be verified on-site and compare the above information with the authentication user information reserved during ticket purchase, thereby realizing the "person-ID-ticket" three-in-one verification and obtaining the verification result. Furthermore, verification device 102 can also be associated with access control devices (such as turnstiles). When the verification is successful, it can drive the turnstile to open.

[0020] User equipment 104 may include any suitable type of device. For example, in some embodiments, user equipment 104 may include a smartphone, a smartwatch, and / or any other suitable type of user equipment.

[0021] See Figure 2 , Figure 2 This is a flowchart illustrating the steps of a ticket verification method according to an embodiment of this application. Indicatively, the ticket verification method provided in this embodiment can be... Figure 1 The ticket verification device 102 in the ticket verification system shown executes the following steps: Step 202: Receive data packets broadcast by the user device via Bluetooth protocol; the data packets contain the user identifier.

[0022] Indicatively, a user identifier is an identification information used to uniquely represent a user.

[0023] In this embodiment, real-name authentication of users can be performed in advance. That is, an application or a mini-program embedded in an existing application can be deployed on the user's device, and the user can perform real-name authentication through the application or mini-program. For example, the application or mini-program can be implemented as follows: displaying an authentication interface and guiding the user to enter identity information; sending the user's entered identity information to the ticketing server so that the ticketing server can perform the following real-name authentication operation: comparing the user's identity information with the identity information reserved when purchasing the ticket; if the two match, the real-name authentication is successful, and the user is the authenticated user.

[0024] Real-name authentication can be performed through the ticketing server, which can link the authenticated user's identity information and ticketing information, and generate a user identifier for each authenticated user. This user identifier is interconnected with the authenticated user's information (including the authenticated user's identity information and ticketing information). The authenticated user's identity information is information that identifies the authenticated user, such as: the authenticated user's identification information, and / or, the authenticated user's photo information, etc. The authenticated user's ticketing information includes the ticket details purchased by the authenticated user, such as: showtime information, performance time information, performance seat information, etc.

[0025] When a user device is within the preset sensing range of the verification device, it can broadcast data packets via Bluetooth to transmit the user identifier to the verification device, so that the verification device can perform subsequent ticket verification based on the user identifier.

[0026] The aforementioned preset sensing range can be a pre-defined range used to trigger the ticket verification process provided in this application embodiment. In other words, when a user enters this sensing range with their user device, the ticket verification process can be initiated. In this application embodiment, the specific content of the preset sensing range is not limited. For example, the aforementioned preset sensing range can be the Bluetooth signal sensing range of the verification device; that is, when the user device is within the Bluetooth sensing range of the verification device, it can broadcast a data packet containing the user's identifier via the Bluetooth protocol. Specifically, the verification device can broadcast a ticket verification notification via the Bluetooth protocol. When the user device receives the notification (at which point the user device is within the Bluetooth sensing range of the verification device), it can broadcast a data packet containing the user's identifier via the Bluetooth protocol. Alternatively, a near-field sensing component can be configured for the verification device, and the sensing area of ​​this component can be defined as the preset sensing range of the verification device. When the user approaches this component, the user device is within the preset sensing range of the verification device, and the user device can then broadcast a data packet containing the user's identifier via the Bluetooth protocol.

[0027] Optionally, in some embodiments, a near-field communication (NFC) coupling element, such as an NFC coil, can be pre-configured for the verification device. Verification trigger information is then set in the NFC coupling element through methods such as data programming. When the user device approaches the NFC coupling element and is within its sensing range, the user device can read the verification trigger information programmed into the NFC coupling element to trigger a data packet broadcast operation.

[0028] At ticket verification sites, there are usually many people waiting to be verified. To improve efficiency, multiple verification devices are typically set up to perform ticket verification in parallel. This situation may lead to the following problem: User device 1 is within the sensing range of the NFC coil configured for verification device 1, and user device 2 is within the sensing range of the NFC coil configured for verification device 2. Both user device 1 and user device 2 broadcast data packets via Bluetooth. Taking user device 1 as an example, its broadcast data packets may be received by both verification devices 1 and 2 simultaneously. In this case, verification devices 1 and 2 will perform ticket verification operations concurrently. If the user corresponding to user device 1 passes the ticket verification, the gate of verification device 2 will mistakenly open.

[0029] To address the aforementioned issues, in some embodiments of this application, the data packets broadcast by the user equipment may further include element identifiers.

[0030] Correspondingly, the process of obtaining the authenticated user information corresponding to the user identifier can include: Determine whether the component identifier in the data packet is the component identifier of the near-field communication coupling element configured with the verification device; if yes, obtain the authentication user information corresponding to the user identifier; if no, discard the data packet.

[0031] Schematic illustration: In the above embodiments of this application, verification trigger information and a component identifier for characterizing the near-field communication coupling element can be set in the near-field communication coupling element through methods such as data programming. When the user equipment approaches the near-field communication coupling element and is within the element sensing range of the near-field communication coupling element, the user equipment can read the verification trigger information and component identifier programmed into the near-field communication coupling element. Subsequently, a data packet containing the user identifier and the component identifier is broadcast.

[0032] Regarding the verification equipment, upon receiving a data packet broadcast by a user equipment, it first determines whether the element identifier within it matches the element identifier of its configured near-field communication coupling element. If so, it indicates that the user equipment sending the broadcast data packet is within the sensing range of its configured near-field communication coupling element, meaning the user holding that user equipment is the user to be verified, and subsequent steps can be executed. Conversely, if the element identifier in the data packet does not match the element identifier of its configured near-field communication coupling element, it indicates that the user equipment sending the broadcast data packet is not within the sensing range of its configured near-field communication coupling element. In this case, to avoid accidental gate opening, the received data packet can be discarded. Through the above embodiment, accidental gate opening can be avoided, improving the reliability of ticket verification.

[0033] Optionally, in some embodiments, the data packet may further include a transmission timestamp. This transmission timestamp can characterize the time when the user equipment broadcast the data packet.

[0034] After receiving the data packet broadcast by the user equipment, and before executing the subsequent step 204, the verification device can first determine whether the time interval between the data packet's reception timestamp and the aforementioned transmission timestamp is small, that is, whether the aforementioned time interval is within a preset valid interval range. If the aforementioned time interval is within the preset valid interval range, then the subsequent step 204 is executed; otherwise, if the aforementioned time interval exceeds the preset valid interval range, then the data packet is discarded.

[0035] In this embodiment, the specific value of the effective interval range is not limited and can be customized according to the actual situation. For example, the effective interval range can be set to (-30s, +30s). When the time interval between the sending timestamp and the receiving timestamp is less than 30s, the data packet is valid and subsequent step 204 can be executed; or, when the time interval between the receiving timestamp and the receiving timestamp is less than 30s, the data packet is valid and subsequent step 204 can be executed.

[0036] The above process, by adding a sending timestamp to the data packet and judging the time interval based on the receiving timestamp and the sending timestamp, can effectively prevent ticket verification fraud by using data packet replay attacks, that is, avoid the situation where previously sent data packets are resent to successfully pass ticket verification.

[0037] Optionally, in some embodiments, the user identifier included in the data packet may be an identifier ciphertext, and the data packet may also include signature data and key ciphertext.

[0038] The identifier ciphertext can be obtained by encrypting the user identifier using a preset symmetric key. After obtaining the identifier ciphertext, the symmetric key can be encrypted using the encryption public key to obtain the key ciphertext. Then, a signature data is generated based on the key ciphertext and the identifier ciphertext using the signing private key. Finally, the obtained identifier ciphertext, key ciphertext, and signature data are added to the data packet for broadcast.

[0039] Correspondingly, after receiving the data packet broadcast by the user equipment, and before executing the subsequent step 204, the verification device can first use a pre-set signature public key to verify the signature data; if the verification is successful, it uses a pre-set decryption private key to decrypt the key ciphertext to obtain the symmetric key, and uses the symmetric key to decrypt the identifier ciphertext in the data packet to obtain the user identifier.

[0040] The encryption and decryption mechanisms described above effectively prevent data packets from being forged or tampered with, improving the security of data packet transmission and thus enhancing the reliability of ticket verification.

[0041] In this embodiment, the specific structure of the data packets broadcast by the user equipment is not limited. For example, the data packets may include: signature data, timestamp, identifier ciphertext, and key ciphertext. Furthermore, for subsequent generation of audit logs, other information, such as user equipment device information, can be added to the data packets. For example, the structure of the data packet can be: {signature data||timestamp||UID ciphertext||key ciphertext||device information}.

[0042] In some examples of this application, the above steps can be performed in the order required. For example, after the verification device receives a data packet broadcast by the user equipment via Bluetooth protocol, it can perform operations to determine whether the element identifier in the data packet is the element identifier of the near-field communication coupling element configured by the verification device, and to determine whether the time interval between the receiving timestamp and the sending timestamp of the data packet is within a preset valid interval range, so as to determine whether the data packet should be discarded. The order of execution of the two operations is not restricted. After determining that the data packet does not need to be discarded, the operation of decrypting the identifier ciphertext can be performed first to obtain the user identifier, and then the authentication user information corresponding to the user identifier can be obtained.

[0043] Step 204: Obtain the authenticated user information corresponding to the user identifier. The authenticated user information includes: authenticated user identity information and authenticated user ticketing information.

[0044] To illustrate, after receiving a data packet broadcast by a user equipment, the verification device can query the pre-built association between user identifiers and authentication user information, thereby obtaining the authentication user information corresponding to the user identifier in the data packet.

[0045] In this embodiment, the specific method by which the verification device obtains the authenticated user information corresponding to the user identifier is not limited. For example, the verification device can pre-store the pre-built association between the user identifier and the authenticated user information locally. When a data packet is received, the authenticated user information corresponding to the user identifier can be retrieved locally. Alternatively, the association can be built and stored by other devices independent of the verification device (such as a ticketing server or a management server). When the verification device receives the data packet, it sends the user identifier in the data packet to the other device and receives the query results returned by the other device.

[0046] Step 206: Collect information from the user to be verified to obtain the user's identity information.

[0047] To illustrate, the user to be verified can be a user of the user device. The identity information of the user to be verified can be information that identifies the user's identity.

[0048] In this embodiment, the execution order of steps 204 and 206 is not limited. For example, step 204 can be executed first, followed by step 206; step 206 can be executed first, followed by step 204; or steps 204 and 206 can be executed in parallel.

[0049] In this embodiment of the application, the identity information of the user to be verified and the identity information of the authenticated user can be the same type of information. For example, when the identity information of the authenticated user includes the document information of the authenticated user (such as the document number), the identity information of the user to be verified can include the document information of the user to be verified. When the identity information of the authenticated user includes the facial information of the authenticated user (such as a photo or facial feature information), the identity information of the user to be verified can include the facial information of the user to be verified.

[0050] Optionally, in some embodiments, when the authenticated user identity information includes authenticated user document information, step 206 above may include: reading information from the document of the user to be verified to obtain the document information of the user to be verified.

[0051] To illustrate, when the authenticated user's identity information includes the authenticated user's identification document information, the verification device can read the identification document information of the user to be verified in real time. By comparing the authenticated user's identification document information with that of the user to be verified, it can determine whether the user to be verified is an authenticated user certified by the ticketing server, that is, whether the user to be verified is a ticket purchaser. In the above embodiment, user identity verification can be completed simply by configuring an identification document reader; therefore, the implementation cost is low.

[0052] Optionally, in some other embodiments, when the authentication user identity information includes the authentication user's facial information, the above step 206 may include: capturing a facial image of the user to be verified, and extracting the facial information of the user to be verified based on the captured image.

[0053] To illustrate, when the authenticated user's identity information includes the authenticated user's facial information, the verification device can capture facial images of the user to be verified in real time and extract information from the captured images to obtain the user's facial information. Then, by comparing the authenticated user's facial information with the user's facial information, it can be determined whether the user to be verified is an authenticated user certified by the ticketing server, that is, whether the user to be verified is a ticket purchaser.

[0054] The aforementioned method of user authentication via facial recognition verifies whether the user identifier on the user's device corresponds to the user being verified, effectively preventing the use or forgery of another person's user identifier and improving the accuracy of ticket verification. Furthermore, this process eliminates the need for users to carry identification documents or other related items, thus providing a superior user experience.

[0055] Step 208: Based on the identity information of the user to be verified, the identity information of the certified user, and the ticketing information of the certified user, perform ticket verification for the user to be verified and obtain the verification result.

[0056] To illustrate, after obtaining the identity information of the user to be verified, the identity information of the authenticated user, and the ticketing information of the authenticated user, a ticketing verification operation can be performed. For example, if the identity information of the user to be verified matches the identity information of the authenticated user, and the ticketing information of the authenticated user matches at the current moment, then it is determined that the user to be verified has passed the ticketing verification; otherwise, if the identity information of the user to be verified does not match the identity information of the authenticated user, and / or the ticketing information of the authenticated user does not match at the current moment, then it is determined that the user to be verified has failed the ticketing verification.

[0057] In addition, in some ticket verification scenarios, the ticket holder may hold a single-entry ticket, meaning that after the ticket holder passes the initial verification, they cannot travel again. Considering this, the ticket verification process can further consider whether the user identifier has been reused. In this case, the ticket verification operation can include: if the identity information of the user to be verified matches the identity information of the authenticated user, the ticket information of the authenticated user matches at the current moment, and the user identifier has not been reused (i.e., the user identifier does not exist in the audit log, or the user device corresponding to the user identifier has not been allowed to pass), then the user to be verified passes the ticket verification; conversely, if the identity information of the user to be verified does not match the identity information of the authenticated user, or the ticket information of the authenticated user does not match at the current moment, or the user identifier has been reused (i.e., the user identifier exists in the audit log, or the user device corresponding to the user identifier has been allowed to pass), then the user to be verified fails the ticket verification.

[0058] Furthermore, once a user awaiting verification passes ticket verification, they are confirmed as an authenticated user. In this case, the gate can be opened to allow the user to pass, and an audit log is generated and stored based on the user identifier, verification result, and other information. In this embodiment, the specific information and structure of the audit log are not limited and can be customized according to actual circumstances. For example, the generated audit log may include: time information, verification device identifier, user identifier, and verification result. Correspondingly, the structure of the audit log can be: {time||verification device identifier|user identifier||verification result}. After generating the audit log, it can be encrypted, and the encryption result can be uploaded to the ticketing server or a preset blockchain node. Conversely, if a user fails ticket verification, a verification failure message can be displayed, such as a text message indicating verification failure, or a voice or light alarm indicating verification failure, etc.

[0059] In this embodiment, when a user device approaches and enters the verification device's sensing range, a ticket verification process based on Bluetooth broadcasting is automatically triggered. This involves reconstructing the Bluetooth near-field communication protocol to send the user identifier from the user device to the verification device in real time. Then, based on the binding relationship between the user identifier and the authenticated user information, the authenticated user information corresponding to the user identifier is obtained. Finally, the obtained authenticated user information is compared with the collected user information to be verified to achieve ticket verification. This process deeply couples near-field sensing detection with the real-name authentication link, thereby enabling near-field sensing actions to trigger ticket verification. On one hand, this application triggers the ticket verification process only when the user device is within the near-field sensing range of the verification device, thus effectively ensuring the accuracy of the verification operation. On the other hand, during the verification process, since the user identifier is transmitted between the user device and the verification device via Bluetooth broadcasting, and the verification process does not require manual user intervention, the transmission response is fast and imperceptible to the user.

[0060] In summary, the embodiments of this application can improve the efficiency and accuracy of ticket verification, and the verification process is seamless for the user, thus improving the user experience.

[0061] See Figure 3 , Figure 3 This is a flowchart illustrating the steps of another ticket verification method according to an embodiment of this application. Indicatively, the ticket verification method provided in this embodiment can be... Figure 1 The ticket verification method, executed by user equipment 104 in the ticket verification system, includes the following steps: Step 302: When the user equipment is within the preset sensing range of the verification device, the user equipment reads the user identifier.

[0062] To illustrate, users can be pre-verified using their real-name information. This involves comparing the user's identity information with the identity information provided when purchasing tickets. If they match, the user is considered verified. The verified user's identity information and ticketing information can be linked, and a user identifier can be generated for each verified user. This user identifier is associated with the verified user's information (including the verified user's identity information and ticketing information). The verified user's identity information represents their identity, such as identification documents and / or a photograph. The verified user's ticketing information includes details of the tickets purchased, such as showtime, performance time, and seat location.

[0063] When the user device is within the preset detection range of the verification device, the ticket verification process can be initiated. From the user device's perspective, the user's identifier can be read.

[0064] The aforementioned preset sensing range can be a pre-defined range used to trigger the ticket verification process provided in this application embodiment. In other words, when a user enters this sensing range with their user device, the ticket verification process can be initiated. In this application embodiment, the specific content of the preset sensing range is not limited. For example, the preset sensing range can be the Bluetooth signal sensing range of the verification device; that is, when the user device is within the Bluetooth sensing range of the verification device, the user identifier can be read. Specifically, the verification device can broadcast a ticket verification notification via Bluetooth. When the user device receives the notification (at which point the user device will be within the Bluetooth sensing range of the verification device), it can perform a user identifier reading operation, for example, by reading the user identifier from a memory in the user device that stores the user identifier. Alternatively, a near-field sensing component can be configured for the verification device, and the sensing range of this component can be defined as the preset sensing range of the verification device. When the user approaches this component, the user device is within the preset sensing range of the verification device, and the user device can then perform a user identifier reading operation.

[0065] Step 304: The user equipment broadcasts a data packet containing the user identifier via Bluetooth protocol, so that the verification device can perform ticket verification for the user to be verified based on the authentication user information corresponding to the user identifier, and obtain the verification result.

[0066] To illustrate, after reading the user identifier, the user device can broadcast a data packet containing the read user identifier via Bluetooth protocol.

[0067] After receiving the aforementioned data packet, the verification device can, on the one hand, obtain the authenticated user information corresponding to the user identifier, including the authenticated user's identity information and ticketing information; on the other hand, it can collect information on the user to be verified to obtain the user's identity information. Then, based on the user's identity information, the authenticated user's identity information, and the authenticated user's ticketing information, it performs ticket verification on the user to be verified to obtain the verification result.

[0068] This application embodiment is an embodiment of a ticket verification method on the user equipment side. Therefore, the focus is on explaining the operation steps performed on the user equipment side. As for the operation steps performed on the verification equipment side, please refer to the description of the corresponding part in the aforementioned method embodiment applied to the verification equipment, and will not be repeated here.

[0069] In this embodiment, when a user device approaches and enters the verification device's sensing range, a ticket verification process based on Bluetooth broadcasting is automatically triggered. This involves reconstructing the Bluetooth near-field communication protocol to send the user identifier from the user device to the verification device in real time. Then, based on the binding relationship between the user identifier and the authenticated user information, the authenticated user information corresponding to the user identifier is obtained. Finally, the obtained authenticated user information is compared with the collected user information to be verified to achieve ticket verification. This process deeply couples near-field sensing detection with the real-name authentication link, thereby enabling near-field sensing actions to trigger ticket verification. On one hand, this application triggers the ticket verification process only when the user device is within the near-field sensing range of the verification device, thus effectively ensuring the accuracy of the verification operation. On the other hand, during the verification process, since the user identifier is transmitted between the user device and the verification device via Bluetooth broadcasting, and the verification process does not require manual user intervention, the transmission response is fast and imperceptible to the user.

[0070] In summary, the embodiments of this application can improve the efficiency and accuracy of ticket verification, and the verification process is seamless for the user, thus improving the user experience.

[0071] Optionally, in some embodiments, the verification device is configured with a near-field communication coupling element.

[0072] Correspondingly, the above-mentioned reading of the user identifier by the user equipment when it is within the preset sensing range of the verification equipment may include: When the user equipment is within the sensing range of the near-field communication coupling element, the user equipment reads the verification trigger information in the near-field communication coupling element; in response to reading the verification trigger information from the near-field communication coupling element, the user identifier reading operation is performed.

[0073] Schematic illustration: Near-field communication (NFC) coupling elements, such as NFC coils, can be pre-configured for the verification device. Verification trigger information can be set in the NFC coupling element through methods such as data programming. When the user device approaches the NFC coupling element and is within its sensing range, the user device can read the aforementioned verification trigger information programmed into the NFC coupling element to trigger a user identifier reading operation.

[0074] The aforementioned configuration of a near-field communication coupling element, which triggers ticket verification by bringing the user device close to the element, eliminates the need for complex user actions such as unlocking the device or accessing the application interface. Instead, a simple "touch" (bringing the device close to the coupling element) initiates the verification process, resulting in a better user experience. Furthermore, external environmental factors do not affect the coupling operation within the near-field communication magnetic field, thus providing stronger anti-interference capabilities and higher reliability.

[0075] Optionally, in some embodiments, the verification trigger information above also includes a component identifier of the near-field communication coupling element; the data packet contains the component identifier.

[0076] Schematic illustration: In the above embodiments of this application, verification trigger information can be set in the near-field communication coupling element by means of data burning, etc. This information may also include a component identifier used to characterize the near-field communication coupling element. When the user equipment approaches the near-field communication coupling element and is within the component sensing area of ​​the near-field communication coupling element, the user equipment can read the verification trigger information burned into the near-field communication coupling element. Subsequently, a data packet containing the user identifier and the component identifier is broadcast.

[0077] Regarding the verification equipment, upon receiving a data packet broadcast by a user equipment (UE), it first determines whether the component identifier within the packet matches the component identifier of its own configured near-field communication (NFC) coupling element. If so, it indicates that the UE sending the broadcast data packet is located within the component sensing area of ​​its configured NFC coupling element, meaning the user holding that UE is the user to be verified, and subsequent steps can be executed. Conversely, if the component identifier in the data packet does not match the component identifier of its configured NFC coupling element, it indicates that the UE sending the broadcast data packet is not located within the component sensing area of ​​its configured NFC coupling element. In this case, to prevent the gate from opening erroneously, the received data packet can be discarded. Through the above embodiment, erroneous gate opening can be avoided, improving the reliability of ticket verification.

[0078] Optionally, in some embodiments, the ticket verification method may further include: Display the authentication interface; receive the authentication user identity information entered in the authentication interface, and send the authentication user identity information to the ticketing server so that the ticketing server can generate a user identifier, which corresponds to the authentication user identity information and the authentication user ticketing information; receive and store the user identifier returned by the ticketing server.

[0079] To illustrate, before performing ticket verification, users can undergo real-name authentication. An authentication interface can be displayed on the user's device, guiding them to enter their identity information. The user device then sends this information to the ticketing server for authentication. Upon successful authentication, the ticketing server generates a user identifier and returns it to the user's device. This generated user identifier corresponds to both the authenticated user's identity information and ticketing information, and is stored in association on the ticketing server, or sent by the ticketing server to the verification device for associated storage.

[0080] In the above embodiments, users can be guided to complete real-name authentication by providing an authentication interface, and a user identifier bound to the user information can be generated and stored. Subsequent ticket verification can then be performed by transmitting the user identifier to compare user information and verify tickets. This effectively reduces the consumption of storage resources and the amount of data transmitted, thereby improving the efficiency of ticket verification.

[0081] Optionally, in some embodiments, the ticket verification method may further include: Display contactless ticket verification guidance information, which guides the user to touch the near-field communication coupling element through the user equipment, so that the user equipment is in the sensing area of ​​the near-field communication coupling element.

[0082] Indicatively, before ticket verification, the user can be guided to perform a "tap" operation (i.e., enter the sensing area of ​​the near-field communication coupling element) by displaying inductive ticket verification guidance information. When the user performs the above operation, the ticket verification scheme provided in this application embodiment is triggered, thereby realizing fast ticket verification.

[0083] See Figure 4 , Figure 4 This is a schematic diagram of a verification device according to an embodiment of this application. The verification device includes: The first Bluetooth controller 402 is used to receive data packets broadcast by the user device via the Bluetooth protocol; the data packets contain a user identifier. The authentication information acquisition module 404 is used to acquire the authentication user information corresponding to the user identifier. The authentication user information includes: authentication user identity information and authentication user ticketing information. Information collector 406 is used to collect information from users to be verified and obtain the identity information of the users to be verified. The verification module 408 is used to perform ticket verification on the user to be verified based on the user's identity information, the certified user's identity information, and the certified user's ticketing information, and to obtain the verification result.

[0084] Optionally, in some embodiments, the verification device is configured with a near-field communication coupling element, and the data packet also includes an element identifier; The authentication information retrieval module 404 is specifically used for: Determine whether the component identifier in the data packet is the component identifier of the near-field communication coupling element configured in the verification device; If so, obtain the authenticated user information corresponding to the user identifier; If not, discard the data packet.

[0085] Alternatively, in some embodiments, the data packets are broadcast by the user equipment when the user equipment is within the sensing range of the near-field communication coupling element.

[0086] Optionally, in some embodiments, the data packet further includes a transmission timestamp. The apparatus also includes: The judgment module is used to determine whether the time interval between the received timestamp and the sent timestamp of the data packet is within a preset valid interval range before obtaining the authentication user information corresponding to the user identifier; if yes, the authentication information acquisition module 404 is triggered; if no, the data packet is discarded.

[0087] Optionally, in some embodiments, the user identifier included in the data packet is an identifier ciphertext, and the data packet also includes signature data and key ciphertext.

[0088] Before obtaining the authenticated user information corresponding to the user identifier, the device also includes: The decryption module is used to verify the signature data using a pre-set signature public key before obtaining the authenticated user information corresponding to the user identifier. If the verification is successful, the pre-set decryption private key is used to decrypt the key ciphertext to obtain the symmetric key, and the symmetric key is used to decrypt the identifier ciphertext to obtain the user identifier.

[0089] Optionally, in some embodiments, the authenticated user identity information includes the authenticated user's facial information; Information collector 406 is specifically used for: The system collects facial images of users to be verified and extracts their facial information based on the collected images.

[0090] Optionally, in some embodiments, the authenticated user identity information includes authenticated user document information; Information collector 406 is specifically used for: The system reads the information from the user's identification documents to obtain the user's identification information.

[0091] Optionally, in some embodiments, the verification module 408 is specifically used for: If the identity information of the user to be verified matches the identity information of the authenticated user, and the ticketing information of the authenticated user matches at the current moment, then it is determined that the user to be verified has passed the ticketing verification. If the identity information of the user to be verified does not match the identity information of the authenticated user, and / or the ticketing information of the authenticated user does not match at the current time, then it is determined that the user to be verified has failed the ticketing verification.

[0092] The verification device in this embodiment is used to implement the ticket verification method applied to the verification device in the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here. Furthermore, the functional implementation of each module in the verification device of this embodiment can be referred to the description of the corresponding part in the foregoing method embodiments, which will also not be repeated here.

[0093] See Figure 5 , Figure 5 This is a structural block diagram of a user equipment according to an embodiment of this application. The user equipment provided in this application embodiment includes: The identifier reading module 502 is used to read the user identifier when the user equipment is within the preset sensing range of the verification device; The second Bluetooth controller 504 is used by the user equipment to broadcast a data packet containing the user identifier via the Bluetooth protocol, so that the verification device can perform ticket verification on the user to be verified based on the authentication user information corresponding to the user identifier, and obtain the verification result.

[0094] Optionally, in some embodiments, the verification device is configured with a near-field communication coupling element.

[0095] The identifier reading module 502 is specifically used for: When the user equipment is within the sensing range of the near-field communication coupling element, the user equipment reads the verification trigger information in the near-field communication coupling element; In response to reading the verification trigger information from the near-field communication coupling element, a user identifier reading operation is performed.

[0096] Optionally, in some embodiments, the verification trigger information includes a component identifier of the near-field communication coupling element; the data packet contains the component identifier.

[0097] Optionally, in some embodiments, the user equipment further includes: The interaction module is used to display the authentication interface before reading the user identifier; receive the authentication user identity information entered in the authentication interface, and send the authentication user identity information to the ticketing server so that the ticketing server can generate a user identifier, which corresponds to the authentication user identity information and the authentication user ticketing information; and receive and store the user identifier returned by the ticketing server.

[0098] Optionally, in some embodiments, the user equipment further includes: The guidance module is used to display contactless ticket verification guidance information before reading the user's identifier. The contactless ticket verification guidance information is used to guide the user to touch the near-field communication coupling element through the user equipment so that the user equipment is in the sensing area of ​​the near-field communication coupling element.

[0099] The user equipment in this embodiment is used to implement the ticket verification method applied to the user equipment in the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here. Furthermore, the functional implementation of each module in the user equipment of this embodiment can refer to the description of the corresponding part in the foregoing method embodiments, which will also not be repeated here.

[0100] Reference Figure 6 This document illustrates a schematic diagram of an electronic device according to an embodiment of this application. The specific embodiments of this application do not limit the specific implementation of the electronic device.

[0101] like Figure 6 As shown, the electronic device may include: a processor 602, a communications interface 604, a memory 606, and a communications bus 608.

[0102] in: The processor 602, communication interface 604, and memory 606 communicate with each other via communication bus 608.

[0103] Communication interface 604 is used for communication with other electronic devices.

[0104] The processor 602 is used to execute program 610, which can specifically execute the relevant steps in any of the above ticket verification method embodiments.

[0105] Indicatively, program 610 may include program code that includes computer operation instructions.

[0106] Processor 602 may be a CPU, an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application. The electronic device includes one or more processors, which may be processors of the same type, such as one or more CPUs; or processors of different types, such as one or more CPUs and one or more ASICs.

[0107] Memory 606 is used to store program 610. Memory 606 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0108] Program 610 may include multiple computer instructions. Specifically, program 610 may use multiple computer instructions to cause processor 602 to perform the operation corresponding to any of the methods described in the foregoing multiple method embodiments.

[0109] The specific implementation of each step in program 610 can be found in the corresponding steps and units described in the above method embodiments, and has corresponding beneficial effects, which will not be repeated here. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the devices and modules described above can be referred to the corresponding process descriptions in the foregoing method embodiments, and will not be repeated here.

[0110] This application also provides a computer storage medium storing a computer program thereon, which, when executed by a processor, implements the method described in any of the foregoing method embodiments. The computer storage medium includes, but is not limited to, compact disc read-only memory (CD-ROM), random access memory (RAM), floppy disk, hard disk, or magneto-optical disk.

[0111] This application also provides a computer program product, including computer instructions that instruct a computing device to perform an operation corresponding to any of the methods in the above-described multiple method embodiments.

[0112] This application also provides a ticket verification system, see [link to relevant documentation]. Figure 1 The ticket verification system may include: the verification device in the above verification device embodiment, and the user device in the above user device embodiment.

[0113] Alternatively, in some embodiments, see Figure 7 The ticket verification system may also include a management terminal 106 and a ticketing server 108. The management terminal 106 can be located at the verification site and connected to the verification devices 102 via a network, used for centralized management of each verification device 102. For example, the management terminal 106 can receive a query request for authenticated user information containing a user identifier sent by the verification device 102, obtain the corresponding authenticated user information from the ticketing server 108, and return it to the user device. The ticketing server 108 can store the association between the user identifier and the authenticated user information.

[0114] See Figure 8 , Figure 8 This is a schematic diagram illustrating the ticket verification interaction of a ticket verification system according to an embodiment of this application. For ease of understanding, the following is combined with... Figure 8 ,right Figure 7 The ticket verification process of the ticket verification system shown is explained below: A complete ticket verification plan can include two parts: the first part is the preliminary preparation; the second part is the actual verification.

[0115] The aforementioned preliminary preparations include: Phase 1, User Authentication. The user device displays an authentication interface, where the user enters their identity information. The user device then sends this information to the ticketing server for real-name authentication. Upon successful authentication, the ticketing server generates an electronic certificate containing the authenticated user's name, ID number, photo, and other identity information. Furthermore, it can generate a user identifier corresponding to this identity information. Additionally, to better guide the user, an option can be added to the electronic certificate to display contactless ticket verification guidance information. When the user selects to display this information, the user device will show the guidance information to guide them to perform a "tap" (close-to-the-field communication coupling element) operation.

[0116] Phase 2, Device Binding. NFC coils (an example of a near-field communication coupling element) can be programmed, and a coil identifier (an example of an element identifier) ​​can be set for the coil; corresponding NFC coils can be configured for each gate (an example of a verification device), and the gate can be bound to the corresponding coil identifier.

[0117] The aforementioned actual verification portion includes: Phase 3: User Trigger Initiation. The user to be verified performs a tap operation by holding their mobile phone (an example of a user device) near the sensing area of ​​the NFC coil configured for the gate (e.g., distance ≤ 3cm). When the Bluetooth protocol module in the phone detects a strong Bluetooth signal (e.g., ≥ -45dBm), it broadcasts a data packet containing the user identifier. Furthermore, to enhance data transmission security, the data packet may also include signature data, timestamps, and mobile phone information. Additionally, the user identifier can be encrypted and then added to the broadcast data packet.

[0118] Phase 4: Two-way authentication. After receiving the data packet, the gate can decrypt the ciphertext using a pre-agreed public key to obtain the user's identifier. Additionally, to ensure real-time ticket verification, it can also verify whether the timestamp in the data packet is within a preset valid timestamp window. If it is, subsequent steps are executed; otherwise, the data packet is discarded.

[0119] Phase 5: Real-name Link Verification. The turnstile sends a verification request to the management terminal. This request message may include: coil identifier, decrypted user identifier, and turnstile location information. After receiving the request message, the management terminal can query the ticketing server to obtain: authenticated user identity information (such as user name, ID number, facial features, etc.) and authenticated user ticketing information (ticket session information, time information, etc.).

[0120] Phase 6: Multimodal Decision Making. After receiving the above information, the turnstile can perform the following three verification operations: compare the similarity between the facial features extracted by the on-site camera and the received facial features to see if it is greater than a preset similarity threshold (e.g., 98%); verify whether the current time is within the ticket validity period; and check whether the user ID has already been used on this turnstile. If any of the above verification operations fails, it is determined that the ticket verification has failed, and an audible and visual alarm will be triggered.

[0121] Phase 7: Release and Audit If all three verifications above are passed, the ticket verification is confirmed to be successful. At this point, the gate can be opened by the gate motor, and a green light can be flashed to indicate passage.

[0122] After verification is completed, an audit log can be generated and stored. The log may include: time, coil identifier (or the gate identifier corresponding to the coil), user identifier, verification result, etc.

[0123] Furthermore, it should be noted that the user-related information (including but not limited to user identity information, user ticketing information, etc.) and data involved in the embodiments of this application are all information and data authorized by the user or fully authorized by all parties. The collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0124] It should be noted that, depending on the implementation needs, the various components / steps described in the embodiments of this application can be broken down into more components / steps, or two or more components / steps or parts of the operation of components / steps can be combined into new components / steps to achieve the purpose of the embodiments of this application.

[0125] The methods described in the embodiments of this application can be implemented in hardware, firmware, or as software or computer code that can be stored in a recording medium (such as a CD-ROM, RAM, floppy disk, hard disk, or magneto-optical disk), or as computer code downloaded over a network that is originally stored in a remote recording medium or a non-transitory machine-readable medium and will be stored in a local recording medium. Thus, the methods described herein can be stored on a recording medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware (such as an Application Specific Integrated Circuit (ASIC) or a Field Programmable Gate Array (FPGA)). It is understood that the computer, processor, microprocessor controller, or programmable hardware includes storage components (e.g., Random Access Memory (RAM), Read-Only Memory (ROM), Flash Memory, etc.) capable of storing or receiving software or computer code, which, when accessed and executed by the computer, processor, or hardware, implements the methods described herein. Furthermore, when a general-purpose computer accesses code used to implement the methods shown herein, the execution of the code transforms the general-purpose computer into a dedicated computer for executing the methods shown herein.

[0126] Those skilled in the art will recognize that the units and method steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this application.

[0127] The above embodiments are only used to illustrate the embodiments of this application, and are not intended to limit the embodiments of this application. Those skilled in the art can make various changes and modifications without departing from the spirit and scope of the embodiments of this application. Therefore, all equivalent technical solutions also fall within the scope of the embodiments of this application, and the patent protection scope of the embodiments of this application should be defined by the claims.

Claims

1. A ticket verification method, applied to a verification device, the method comprising: Receive data packets broadcast by user devices via Bluetooth protocol; The data packet contains a user identifier; Obtain the authenticated user information corresponding to the user identifier, wherein the authenticated user information includes: authenticated user identity information and authenticated user ticketing information; Information is collected from users to be verified to obtain their identity information; Based on the identity information of the user to be verified, the identity information of the certified user, and the ticketing information of the certified user, ticket verification is performed on the user to be verified to obtain the verification result.

2. The method according to claim 1, wherein, The verification device is equipped with a near-field communication coupling element, and the data packet also includes an element identifier; The step of obtaining the authenticated user information corresponding to the user identifier includes: Determine whether the component identifier in the data packet is the component identifier of the near-field communication coupling element configured in the verification device; If so, obtain the authenticated user information corresponding to the user identifier; If not, discard the data packet.

3. The method according to claim 2, wherein, The data packet is broadcast by the user equipment when the user equipment is within the sensing range of the near-field communication coupling element.

4. The method according to any one of claims 1-3, wherein, The data packet also includes: a sending timestamp; Before obtaining the authenticated user information corresponding to the user identifier, the method further includes: Determine whether the time interval between the received timestamp and the sent timestamp of the data packet is within a preset valid interval range; If so, proceed with the step of obtaining the authenticated user information corresponding to the user identifier; If not, discard the data packet.

5. The method according to any one of claims 1-3, wherein, The user identifier contained in the data packet is an identifier ciphertext, and the data packet also includes: signature data and key ciphertext; Before obtaining the authenticated user information corresponding to the user identifier, the method further includes: The signature data is verified using a pre-defined signature public key; If the verification is successful, the key ciphertext is decrypted using the pre-set decryption private key to obtain the symmetric key, and the identifier ciphertext is decrypted using the symmetric key to obtain the user identifier.

6. The method according to any one of claims 1-3, wherein, The authenticated user's identity information includes the authenticated user's facial information or the authenticated user's identification document information; The process of collecting information from the user to be verified, and obtaining the user's identity information, includes: Facial images of the user to be verified are captured, and facial information of the user to be verified is extracted based on the captured images; Alternatively, information can be read from the identification documents of the user to be verified to obtain the identification information of the user to be verified.

7. A ticket verification method, applied to a user equipment, the method comprising: When the user equipment is within the preset sensing range of the verification device, the user equipment reads the user identifier; The user equipment broadcasts a data packet containing the user identifier via Bluetooth protocol, so that the verification device can perform ticket verification for the user to be verified based on the authentication user information corresponding to the user identifier, and obtain the verification result.

8. The method according to claim 7, wherein, The verification device is equipped with a near-field communication coupling element; When the user equipment is within the preset sensing range of the verification device, the user equipment reads the user identifier, including: When the user equipment is within the element sensing range of the near-field communication coupling element, the user equipment reads the verification trigger information in the near-field communication coupling element; In response to reading the verification trigger information from the near-field communication coupling element, a user identifier reading operation is performed.

9. The method according to claim 8, wherein, The verification trigger information includes the component identifier of the near-field communication coupling element; the data packet includes the component identifier.

10. The method according to any one of claims 7-9, wherein, Prior to reading the user identifier, the method further includes: Display the authentication interface; The system receives the authenticated user identity information entered in the authentication interface and sends the authenticated user identity information to the ticketing server so as to generate a user identifier through the ticketing server. The user identifier corresponds to the authenticated user identity information and the authenticated user ticketing information. Receive and store the user identifier returned by the ticketing server.

11. The method according to claim 8 or 9, wherein, Prior to reading the user identifier, the method further includes: The system displays ticket verification guidance information, which guides the user to touch the near-field communication coupling element through the user equipment, so that the user equipment is in the sensing area of ​​the near-field communication coupling element.

12. A verification device, comprising: The first Bluetooth controller is used to receive data packets broadcast by the user device via the Bluetooth protocol; The data packet contains a user identifier; The authentication information acquisition module is used to acquire the authentication user information corresponding to the user identifier, the authentication user information including: authentication user identity information and authentication user ticketing information; The information collector is used to collect information from users to be verified and obtain their identity information. The verification module performs ticket verification on the user to be verified based on the identity information of the user to be verified, the identity information of the certified user, and the ticketing information of the certified user, and obtains the verification result.

13. The device according to claim 12, wherein, The verification device is equipped with a near-field communication coupling element; the data packet also includes an element identifier; The authentication information acquisition module is specifically used for: Determine whether the component identifier in the data packet is the component identifier of the near-field communication coupling element configured in the verification device; If so, obtain the authenticated user information corresponding to the user identifier; If not, discard the data packet.

14. The device according to claim 13, wherein, The data packet is broadcast by the user equipment when the user equipment is within the sensing range of the near-field communication coupling element.

15. A user equipment, comprising: The identifier reading module is used to read the user identifier when the user equipment is within the preset sensing range of the verification device; The second Bluetooth controller is used to broadcast a data packet containing the user identifier via the Bluetooth protocol, so that the verification device can perform ticket verification for the user to be verified based on the authentication user information corresponding to the user identifier, and obtain the verification result.

Images