Electronic bill processing method, server, ticket checking terminal, ticket buying equipment and storage medium

Abstract

The embodiment of the invention provides an electronic bill processing method, a server, a ticket checking terminal, ticket buying equipment and a storage medium. The electronic bill processing method comprises the following steps: based on a ticket buying request of ticket buying equipment, collecting an equipment fingerprint of the ticket buying equipment; generating an electronic bill based on to-be-purchased ticket business information, the dynamic key of the electronic bill and the device fingerprint of the ticket purchasing device; and sending the electronic bill to the ticket buying equipment, so that the ticket buying equipment writes the electronic bill into a near field communication chip of the ticket buying equipment. According to the scheme, the offline availability, reliability and safety of electronic bill verification can be improved, and the user experience can be improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to an electronic ticket processing method, server, ticket verification terminal, ticket purchasing equipment, and storage medium. Background Technology

[0002] Traditional electronic tickets rely on online verification, but in certain use cases (including but not limited to concerts, trains, etc.), network congestion or signal interruption can easily occur, which can lead to delays or even failures in electronic ticket verification. In such cases, users usually need to repeatedly connect to the network to refresh the status of the electronic ticket. Therefore, the reliability of traditional electronic ticket verification methods is low and the user experience is poor. New technical solutions are needed to at least partially improve these problems. Summary of the Invention

[0003] In view of this, embodiments of this application provide an electronic invoice processing solution to at least partially solve the above-mentioned problems.

[0004] According to a first aspect of the embodiments of this application, an electronic ticket processing method is provided, comprising: collecting the device fingerprint of the ticket purchasing device based on a ticket purchase request; generating an electronic ticket based on the ticket information to be purchased, the electronic ticket dynamic key, and the device fingerprint of the ticket purchasing device; and sending the electronic ticket to the ticket purchasing device so that the ticket purchasing device can write the electronic ticket into the near-field communication chip of the ticket purchasing device.

[0005] According to a second aspect of the embodiments of this application, an electronic ticket processing method is provided, applied to a ticket verification terminal. The method includes: establishing a short-range communication connection with a ticket purchasing device; reading an electronic ticket verification data packet from a short-range communication chip of the ticket purchasing device through the short-range communication connection, wherein the electronic ticket verification data packet includes: ticketing information to be verified, a dynamic key for the electronic ticket to be verified, and a device fingerprint to be verified; generating an electronic ticket verification request based on the information contained in the electronic ticket verification data packet, and sending the electronic ticket verification request to a server; and receiving an electronic ticket verification result returned by the server based on the electronic ticket verification request.

[0006] According to a third aspect of the embodiments of this application, an electronic ticket processing method is provided, applied to a ticket purchasing device. The method includes: receiving an electronic ticket returned by a server based on a ticket purchasing request, wherein the electronic ticket includes: ticketing information, an electronic ticket dynamic key, and a device fingerprint of the ticket purchasing device; and storing the electronic ticket in an independent storage area of ​​a near-field communication chip of the ticket purchasing device.

[0007] According to a fourth aspect of the embodiments of this application, a server is provided, comprising: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus; the memory is used to store a computer program; and the processor is used to execute the method as described in any one of the first aspects by running the computer program stored in the memory.

[0008] According to a fifth aspect of the embodiments of this application, a ticket verification terminal is provided, comprising: a second short-range communication chip and a processor; wherein the second short-range communication chip is used to establish a short-range communication connection with a ticket purchasing device; the processor is used to read an electronic ticket verification data packet from the short-range communication chip of the ticket purchasing device through the short-range communication connection, wherein the electronic ticket verification data packet includes: ticketing information to be verified, an electronic ticket dynamic key to be verified, and a device fingerprint to be verified, wherein the electronic ticket dynamic key to be verified is obtained based on the identification information of the short-range communication chip of the ticket purchasing device; generate an electronic ticket verification request based on the information contained in the electronic ticket verification data packet, and send the electronic ticket verification request to a server; and receive an electronic ticket verification result returned by the server based on the electronic ticket verification request.

[0009] According to a sixth aspect of the embodiments of this application, a ticket purchasing device is provided, comprising: a near-field communication (NFC) chip and a processor; wherein the processor is configured to receive an electronic ticket returned by a server based on a ticket purchasing request, wherein the electronic ticket is an encrypted ticket, and the electronic ticket includes: ticketing information, an electronic ticket dynamic key, and a device fingerprint of the ticket purchasing device, wherein the electronic ticket dynamic key is obtained based on the identification information of the NFC chip of the ticket purchasing device; the NFC chip is configured to store the electronic ticket in an independent storage area.

[0010] According to a seventh aspect of the embodiments of this application, a computer storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the method as described in any one of the first, second, and third aspects.

[0011] According to an eighth aspect of the embodiments of this application, a computer program product is provided, including a computer program that, when executed by a processor, implements the method as described in any one of the first, second, and third aspects.

[0012] The electronic ticket processing scheme provided in this application embodiment allows the server to collect the device fingerprint of the ticketing device based on the ticket purchase request. Then, based on the ticket information to be purchased, the dynamic key of the electronic ticket, and the device fingerprint, an electronic ticket is generated and sent to the ticketing device for writing it into its short-range communication chip. Therefore, on the one hand, the electronic ticket processed by this application embodiment, written into the short-range communication chip, allows for offline verification during subsequent electronic ticket verification. This avoids delays or even failures in electronic ticket verification caused by network congestion or signal interruptions between the ticketing device and the server. Users also do not need to repeatedly refresh the electronic ticket status online during verification, thus improving both the reliability of electronic ticket verification and user experience. On the other hand, since the technical solution of this application embodiment generates electronic tickets based on the ticket information to be purchased, the dynamic key of the electronic ticket, and the device fingerprint of the ticketing device, the electronic ticket and the device fingerprint are well bound, reducing the risk of the electronic ticket data written to the short-range communication chip being copied or tampered with. This approach mitigates risks and enhances the data security of electronic invoices, thereby improving verification security. Furthermore, since the electronic invoices in this embodiment can be generated based on a dynamic key and written into a near-field communication chip, a dynamic verification mechanism can be used for subsequent verification. Utilizing the non-repeatable nature of the dynamic key effectively improves security. Compared to static QR code-based verification mechanisms, this significantly enhances dynamic anti-counterfeiting capabilities and reduces the risk of screenshots being shared and resold, effectively preventing illegal resale (i.e., scalping). Moreover, compared to other verification mechanisms such as dynamic QR codes, it avoids reliance on network access and screen-on operation, improving user experience. Therefore, this embodiment provides an electronic invoice processing solution that balances offline availability and reliability, security, and dynamic anti-counterfeiting capabilities, effectively improving user experience. Attached Figure Description

[0013] 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.

[0014] Figure 1This is a schematic diagram of an electronic ticket processing system applicable to the embodiments of this application.

[0015] Figure 2 This is a flowchart of the steps of an electronic ticket processing method according to an embodiment of this application.

[0016] Figure 3 This is a flowchart of another electronic ticket processing method according to an embodiment of this application.

[0017] Figure 4 This is a flowchart of another electronic ticket processing method according to an embodiment of this application.

[0018] Figure 5 This illustration shows a scenario diagram of an example of an electronic ticket processing scheme according to an embodiment of this application.

[0019] Figure 6 A schematic block diagram of an example server in an embodiment of this application is shown.

[0020] Figure 7 A schematic block diagram of an example ticket verification terminal according to an embodiment of this application is shown.

[0021] Figure 8 A schematic block diagram of an example ticket purchasing device according to an embodiment of this application is shown. Detailed Implementation

[0022] 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.

[0023] The specific implementation of the embodiments of this application will be further described below with reference to the accompanying drawings.

[0024] Figure 1 An exemplary electronic ticket processing system applicable to embodiments of this application is illustrated. For example... Figure 1 As shown, the electronic ticket processing system 100 may include a server 102, a ticket verification terminal 104, and a ticket purchasing device 106; the ticket purchasing device 106 may include a near-field communication chip 1062.

[0025] Server 102 can be any suitable device for storing information, data, programs, and / or any other suitable type of content, including but not limited to distributed storage system devices, server clusters, computing cloud server clusters, etc. In some alternative embodiments, server 102 can perform any suitable function. Optionally, server 102 can perform an electronic ticket processing method.

[0026] In some optional embodiments, when the server 102 executes the electronic ticket processing method of this application embodiment, it can first collect the device fingerprint of the ticketing device 106 based on the ticket purchase request of the ticketing device 106; then, it can generate an electronic ticket based on the ticket information to be purchased, the electronic ticket dynamic key, and the device fingerprint of the ticketing device 106; and then send the electronic ticket to the ticketing device 106 so that the ticketing device 106 can write the electronic ticket to the near-field communication chip 1062. Optionally, the server 102 can also obtain the identification information of the near-field communication chip 1062 based on the ticket purchase request, and generate the electronic ticket dynamic key based on the identification information.

[0027] Optionally, the server 102 can store the electronic ticket dynamic key of the electronic ticket in the key list, store the device fingerprint of the ticketing device 106 in the first storage area, store the ticketing information in the second storage area, and mark the status of the electronic ticket dynamic key and the ticketing information respectively.

[0028] Subsequently, in some optional embodiments, when performing electronic ticket verification, the server 102 can receive an electronic ticket verification request from the ticket verification terminal 104, extract the electronic ticket verification information to be verified from the electronic ticket verification request, wherein the electronic ticket verification information to be verified includes: ticketing information to be verified, electronic ticket dynamic key to be verified, and device fingerprint to be verified; based on the extracted electronic ticket verification information to be verified, and the data stored in the key list, the first storage area and the second storage area respectively, the verification information to be verified is performed, and the electronic ticket verification result is returned to the ticket verification terminal 104.

[0029] The ticket verification terminal 104 in this embodiment can interact with the ticket purchasing device 106 to facilitate the verification of electronic tickets. The ticket verification terminal 104 can be constructed in any structure, and this embodiment does not impose any specific limitations. For example, the ticket verification terminal 104 may include another short-range communication chip (e.g., a second short-range communication chip 1042) to establish a short-range communication connection with the short-range communication chip 1062 of the ticket purchasing device 106.

[0030] In some optional embodiments, the ticket verification terminal 104 can execute an electronic ticket processing method. As an optional example, when executing the electronic ticket processing method, the ticket verification terminal 104 can first establish a short-range communication connection with the ticket purchasing device 106; then, through the short-range communication connection, it can read an electronic ticket verification data packet from the short-range communication chip 1062 of the ticket purchasing device 106, wherein the electronic ticket verification data packet includes: ticketing information to be verified, a dynamic key for the electronic ticket to be verified, and a device fingerprint to be verified; furthermore, the ticket verification terminal 104 can generate an electronic ticket verification request based on the information contained in the electronic ticket verification data packet, and send the electronic ticket verification request to the server 102; then, it can receive the electronic ticket verification result returned by the server 102 based on the electronic ticket verification request.

[0031] The ticketing device 106 in this embodiment may include any device suitable for displaying information and interacting with users (e.g., ticket purchasers, users of electronic tickets, etc.). Optionally, the ticketing device 106 may be a user device capable of receiving user ticket purchase operations and realizing the purchase of electronic tickets. For example, in some embodiments, the ticketing device 106 may include mobile devices (such as mobile phones), tablet computers, laptop computers, and / or any other suitable type of user device. The ticketing device 106 includes a near-field communication (NFC) chip 1062. The NFC chip 1062 may be a chip employing any near-field communication protocol; for example, the NFC chip 1062 may be, but is not limited to, an NFC (Near Field Communication) chip or an RFID (Radio Frequency Identification) chip. For ease of explanation of the embodiments of this application, the NFC chip 1062 may be used as an example in this document.

[0032] In some optional embodiments, the ticketing device 106 can execute an electronic ticket processing method. As an optional example, when executing the electronic ticket processing method, the ticketing device 106 can first receive an electronic ticket returned by the server 102 based on the ticket purchase request, wherein the electronic ticket includes: ticketing information, an electronic ticket dynamic key, and the device fingerprint of the ticketing device 106; and store the electronic ticket in the independent storage area of ​​the near-field communication chip 1062 of the ticketing device 106.

[0033] Subsequently, in some optional embodiments, the ticket purchasing device 106 can interact with the ticket verification terminal 104 when performing electronic ticket verification. For example, the ticket purchasing device 106 can establish a short-range communication connection with the ticket verification terminal 104. The ticket purchasing device 106 can provide the electronic ticket verification data packet from the short-range communication chip 1062 to the ticket verification terminal 104 through the short-range communication connection, thereby enabling the ticket verification terminal 104 to: read the electronic ticket verification data packet from the short-range communication chip 1062 of the ticket purchasing device 106 through the short-range communication connection. The electronic ticket verification data packet includes: ticketing information to be verified, the dynamic key of the electronic ticket to be verified, and the device fingerprint to be verified. Based on the information contained in the electronic ticket verification data packet, the terminal generates an electronic ticket verification request and sends the electronic ticket verification request to the server 102, and then receives the electronic ticket verification result returned by the server 102 based on the electronic ticket verification request.

[0034] Optionally, the ticketing device 106 can be connected to the communication network 1082 via one or more communication links, and the communication network 1082 can be linked to the server 102 via one or more communication links. Optionally, the ticket verification terminal 104 can be connected to the communication network 1084 via one or more communication links, and the communication network 1084 can be linked to the server 102 via one or more communication links. The communication links can be any communication links suitable for transmitting data between the ticketing device 106 and the server 102, such as network links, dial-up links, wireless links, hardwired links, any other suitable communication links, or any suitable combination of such links.

[0035] In some embodiments, communication networks 1082 and 1084 can be any suitable combination of one or more wired and / or wireless networks. For example, the communication network can include any one or more of the following: the Internet, intranet, wide area network (WAN), local area network (LAN), wireless network, digital subscriber line (DSL) network, frame relay network, asynchronous transfer mode (ATM) network, virtual private network (VPN), and / or any other suitable communication network. Optionally, communication networks 1082 and 1084 can be different communication networks, or they can be the same communication network.

[0036] To facilitate the explanation of the embodiments of this application, the above-mentioned contents will be described in detail in the embodiments of the electronic invoice processing method below, and will not be repeated here.

[0037] Based on the above-described electronic invoice processing system 100, this application provides some electronic invoice processing solutions, which are described below through multiple embodiments.

[0038] Figure 2 This is a flowchart illustrating the steps of an electronic invoice processing method according to an embodiment of this application. According to a first aspect of this application, an electronic invoice processing method is provided. Optionally, this electronic invoice processing method can be used in a server 102. (Refer to...) Figure 2 As shown, the electronic ticket processing method includes steps S202, S204, and S206, specifically: S202: Collect the device fingerprint of the ticketing device based on the ticket purchase request.

[0039] The ticketing device 106 can be used by users to purchase electronic tickets and also for ticket verification. Electronic tickets can be understood as concert tickets, train tickets, etc., and can be either non-real-name or real-name electronic tickets, as long as they meet the requirements. For example, in some embodiments, the ticketing device 106 can display an interface for purchasing electronic tickets (such as, but not limited to, application interfaces, mini-program interfaces, web page interfaces, etc.). The ticketing device 106 can receive the user's purchase operation for electronic tickets on this interface, generate a purchase request based on the purchase operation, and send the purchase request to the server 102.

[0040] The dynamic key for electronic invoices is a key used only once and has high security. The specific method for obtaining the dynamic key is not limited here; it can be generated using any dynamic key generation algorithm. In this embodiment, by generating a dynamic key for electronic invoices, the key's non-copyability can be guaranteed, improving security and enabling the one-time verification and use of the generated electronic invoice.

[0041] In some optional embodiments, the electronic ticket processing method in this application embodiment further includes: obtaining the identification information of the near-field communication chip 1062 based on the ticket purchase request, and generating an electronic ticket dynamic key based on the identification information of the near-field communication chip 1062.

[0042] In the above optional embodiments, the electronic ticket dynamic key can be a key generated based on the identification information of the near-field communication chip 1062 for single use, which has high security.

[0043] After receiving a purchase request, server 102 can obtain the identification information of the near-field communication (NFC) chip 1062 of ticketing device 106 to facilitate the subsequent generation of electronic tickets. This identification information uniquely identifies the NFC chip 1062. In some optional embodiments, the identification information can be the unique ID of the NFC chip 1062. For example, if the NFC chip 1062 is an NFC chip, the SE (Security Element) serial number (also known as SEID) of the NFC chip can be obtained as its identification information. However, this is not limited to this; other information that can uniquely identify the NFC chip can also be used as its identification information.

[0044] Optionally, the identification information of the near-field communication chip can be the SE serial number of the NFC chip, then the server 102 can generate an initial electronic ticket dynamic key (e.g., denoted as DK) based on the SE serial number.

[0045] It should be understood that in the above optional embodiments of this application, by obtaining the identification information of the near-field communication chip 1062 and generating the electronic ticket dynamic key based on the identification information, the electronic ticket can be generated based on the ticket information to be purchased, the electronic ticket dynamic key, and the device fingerprint of the ticketing device 106. Since the electronic ticket dynamic key is generated based on the identification information of the near-field communication chip 1062 of the ticketing device 106, the electronic ticket is not only bound to the device fingerprint of the ticketing device 106, but also to the identification information of the near-field communication chip 1062. Therefore, the risk of the electronic ticket data written to the near-field communication chip 1062 being copied or tampered with is better reduced, which is conducive to further improving the data security of the electronic ticket. For electronic ticket verification, the verification security can be better improved.

[0046] S204: Generate an electronic ticket based on the ticketing information to be purchased, the dynamic key of the electronic ticket, and the device fingerprint of the ticketing device.

[0047] The device fingerprint of the ticketing device 106 can identify the ticketing device 106. The device fingerprint can be generated by collecting the software and hardware feature information of the ticketing device 106 and combining them with a specific algorithm. It can highly identify or even uniquely identify the ticketing device 106. For example, it can be the digital fingerprint or identification code of the ticketing device 106.

[0048] In some optional embodiments, the device fingerprint of the ticketing device 106 can be generated using the unique ID of the ticketing device 106. For example, one or more of the following data that can uniquely identify the ticketing device 106, including but not limited to UDID (Unique Device Identifier), IMEI (International Mobile Equipment Identity), MEID (Mobile Equipment Identifier), etc., can be used as or used to generate the device fingerprint of the ticketing device 106, or other data can be used, without specific limitations.

[0049] In some alternative embodiments, the device fingerprint of the ticketing device 106 can also directly use the unique ID of one of its chips or modules. For example, in some embodiments, the device fingerprint of the ticketing device 106 can use the unique ID of its near-field communication (NFC) chip 1062. For example, if the NFC chip 1062 is an NFC chip, the SE serial number of the NFC chip can be obtained as the device fingerprint of the ticketing device 106.

[0050] Ticketing information can uniquely identify a specific electronic ticket. For example, ticketing information can include at least a unique identifier for the electronic ticket, such as a ticket ID. Alternatively, in addition to a unique identifier, ticketing information can also include one or more combinations of information such as ticket name, order information, event and session information, and seat information.

[0051] Optionally, the server 102 can obtain the device fingerprint of the ticketing device 106 (for example, it can be understood as the SE serial number of the NFC chip of the ticketing device), and generate a data packet of the electronic ticket based on the ticketing information of the electronic ticket to be purchased for the ticketing request, the generated electronic ticket dynamic key, and the device fingerprint of the ticketing device 106.

[0052] For example, the data packet of an electronic ticket may include ticketing information to be purchased (such as ticket ID), electronic ticket dynamic key DK, and device fingerprint of the ticketing device (such as the SE serial number of the NFC chip of the ticketing device).

[0053] S206: Send the electronic ticket to the ticket purchasing device so that the ticket purchasing device can write the electronic ticket into the short-range communication chip of the ticket purchasing device.

[0054] The server 102 can directly send the electronic ticket data packet to the ticket purchasing device 106, or process the electronic ticket data packet before sending it to the ticket purchasing device 106. Optionally, after receiving the generated electronic ticket data packet, the ticket purchasing device 106 can write the electronic ticket data packet into a certain storage area of ​​the near-field communication chip 1062.

[0055] Based on this, the electronic ticket processing method in steps S202-S206 of this application embodiment has two advantages. First, the electronic ticket obtained through the processing of this application embodiment is written into the near-field communication chip 1062. During subsequent electronic ticket verification, offline verification and identification can be achieved based on the communication of the near-field communication chip 1062, thereby avoiding the problem of electronic ticket verification delays or even failures caused by network congestion or signal interruptions between the ticketing device and the server. Users also do not need to repeatedly refresh the electronic ticket status during the electronic ticket verification process. Therefore, this not only improves the reliability of electronic ticket verification but also enhances the user experience. Second, since the technical solution of this application embodiment generates electronic tickets based on the ticket information to be purchased, the electronic ticket dynamic key, and the device fingerprint of the ticketing device 106, the electronic ticket and the device fingerprint of the ticketing device 106 are well bound, thus reducing the need for writing to the near-field communication chip 1062. The risk of electronic ticket data being copied or tampered with by the communication chip 1062 is mitigated, thus improving the data security of electronic tickets. For electronic ticket verification, this significantly enhances verification security. Furthermore, since the electronic tickets in this embodiment can be generated based on a dynamic key and written into the short-range communication chip 1062, a dynamic verification mechanism can be used for subsequent verification. Utilizing the non-repeatable nature of the dynamic key effectively improves security. Compared to verification mechanisms based on static QR codes, this significantly enhances the dynamic anti-counterfeiting capability of electronic ticket verification and further reduces the risk of electronic tickets being screenshotted, disseminated, and resold. It effectively prevents illegal resale (i.e., scalping). Moreover, compared to other electronic ticket verification mechanisms such as those based on dynamic QR codes, it further avoids reliance on network and screen-on operation, improving user experience. Therefore, this embodiment provides an electronic ticket processing solution that balances offline availability and reliability, security, and dynamic anti-counterfeiting capabilities, effectively improving user experience.

[0056] In some optional embodiments, step S206 may include: performing private key signing on the electronic ticket and sending the signed electronic ticket to the ticket purchasing device so that the ticket purchasing device can write the signed electronic ticket into the short-range communication chip of the ticket purchasing device.

[0057] Electronic tickets can be signed using any private key signing algorithm, including but not limited to RSA, DSA, elliptic curve-based signing algorithms (such as EdDSA and ECDSA), and hash-based signing algorithms, as long as the requirements are met.

[0058] It should be understood that in this embodiment, the generated electronic ticket is privately key signed by the server 102, and the ticket purchasing device 106 writes the signed electronic ticket into the near-field communication chip 1062. On the one hand, this allows the ticket purchasing device 106 to perform offline verification and recognition of the electronic ticket without needing to connect to the network during the verification stage. This avoids the problem of verification delays or even failures caused by network congestion or signal interruptions between the ticket purchasing device and the server. Users also do not need to repeatedly connect to the network to refresh the electronic ticket status during the verification process. Therefore, this not only improves the reliability of electronic ticket verification but also enhances the user experience. On the other hand, since the entire electronic ticket (such as all data in the electronic ticket's data packet) is encrypted during the private key signing process, any minor modification to the electronic ticket can cause the signature verification to fail. Therefore, this ensures... The possibility of forging electronic tickets is greatly reduced, as is the risk of electronic tickets being tampered with. On the other hand, since the server 102 performs private key signing on the generated electronic tickets, the subsequent electronic ticket verification stage can accurately determine whether the electronic ticket was issued by the issuer holding the corresponding private key, thus ensuring the legitimacy of the electronic ticket's identity. Furthermore, the electronic tickets written into the ticketing device 106 in this embodiment of the application can improve the security of electronic tickets through the coordinated use of private key signing and the electronic ticket dynamic key. This ensures that even if malicious individuals guess or intercept the electronic ticket dynamic key, they cannot forge electronic tickets with private key signing. In addition, even if the private key signature is difficult to crack, the electronic ticket dynamic key can also prevent the reuse of legally signed electronic tickets, thus significantly improving the security level of electronic tickets.

[0059] In some optional embodiments, the ticketing device 106 can store electronic tickets in a separate storage area of ​​the near-field communication chip 1062. In this embodiment, the separate storage area of ​​the near-field communication chip 1062 can refer to a storage area in the near-field communication chip 1062 that is isolated from the operating system.

[0060] It should be understood that by storing electronic tickets in an independent storage area, interference with the operating system caused by electronic ticket writing and verification can be avoided. This also allows the ticketing device 106 to perform offline verification and recognition of electronic tickets without needing to be connected to the network. This avoids the problem of delays or even failures in electronic ticket verification caused by network congestion or signal interruption between the ticketing device and the server. Users also do not need to repeatedly connect to the network to refresh the electronic ticket status during the electronic ticket verification process. Therefore, this not only improves the reliability of electronic ticket verification but also enhances the user experience.

[0061] In some optional embodiments, the electronic ticket processing method in this application further includes: storing the electronic ticket dynamic key of the electronic ticket in a key list, storing the device fingerprint of the ticket purchasing device in a first storage area, and storing the ticketing information in a second storage area; and marking the status of the electronic ticket dynamic key and the ticketing information respectively.

[0062] In this embodiment, the server 102 can store the dynamic key of the electronic ticket in a key list and mark the status of the dynamic keys in the key list. For example, for the dynamic key of an electronic ticket that has not been verified and used, a status information indicating that the dynamic key is a valid key can be marked, while for the dynamic key of an electronic ticket that has been verified and used, a status information indicating that the dynamic key is an invalid key can be marked.

[0063] Understandably, server 102 stores the dynamic key of each generated electronic ticket in the key list, which can be used conveniently when verifying electronic tickets in the future. This can effectively prevent electronic tickets from being verified multiple times, reduce the risk of repeated use of electronic tickets, and improve the reliability and security of electronic ticket verification.

[0064] In this embodiment, the server 102 can store the device fingerprint of the ticketing device 106 in a first storage area. The first storage area can be a storage area in any storage unit capable of data storage, such as a memory or database.

[0065] Understandably, the server 102 stores the device fingerprint of the corresponding ticketing device 106 in the first storage area for each generated electronic ticket, which can be used in subsequent electronic ticket verification to achieve accurate and reliable electronic ticket verification.

[0066] In this embodiment, the server 102 can store ticketing information in a second storage area and mark the status of the ticketing information in the second storage area. The second storage area can be any storage area in a storage unit capable of data storage, such as a memory or database. The second storage area and the first storage area can be different storage areas in the same storage unit, or they can be storage areas in different storage units. For example, ticketing information for unverified electronic tickets can be marked with status information indicating that the ticketing information is in an unused state, while ticketing information for verified electronic tickets can be marked with status information indicating that the ticketing information is in a used state. As another example, electronic tickets with risks can also be marked with status information indicating that the ticketing information is in a risky state.

[0067] Understandably, server 102 stores ticketing information for each generated electronic ticket in a second storage area, which is convenient for subsequent electronic ticket verification. This effectively avoids the situation where electronic tickets are repeatedly verified and passes verification, reduces the risk of repeated use of electronic tickets, and improves the reliability and security of electronic ticket verification.

[0068] In some optional embodiments, during the verification stage of electronic invoices, the electronic invoice processing method in this application embodiment may further include the following steps T202~T204: T202: Receives an electronic ticket verification request from the ticket verification terminal, and extracts the electronic ticket verification information from the electronic ticket verification request. The electronic ticket verification information includes: ticketing information to be verified, dynamic key of the electronic ticket to be verified, and device fingerprint to be verified.

[0069] In some embodiments, during electronic ticket verification, a user can bring their ticket purchasing device 106 close to the ticket verification terminal 104, and the ticket verification terminal 104 can establish a short-range communication connection with the ticket purchasing device 106. For example, if the short-range communication chip 1062 of the ticket purchasing device 106 is an NFC chip, then the ticket verification terminal 104 may include another short-range communication chip (e.g., a second short-range communication chip 1042) that is also an NFC chip, and the ticket purchasing device 106 can establish an NFC connection with the ticket verification terminal 104.

[0070] Optionally, the ticket verification terminal 104 can then read the electronic ticket verification data packet from the short-range communication chip 1062 of the ticketing device 106 via a short-range communication connection. The electronic ticket verification data packet includes: ticketing information to be verified, a dynamic key for the electronic ticket to be verified, and a device fingerprint to be verified. The dynamic key for the electronic ticket to be verified is obtained based on the identification information of the short-range communication chip 1062 of the ticketing device 106. The ticket verification terminal 104 can then generate an electronic ticket verification request based on the information contained in the electronic ticket verification data packet and send the electronic ticket verification request to the server 102.

[0071] After receiving the electronic invoice verification request, server 102 can extract the relevant information to be verified from the electronic invoice verification request to facilitate the electronic invoice verification.

[0072] T204: Based on the extracted electronic ticket verification information, as well as the data stored in the key list, the first storage area, and the second storage area respectively, verify the verification information and return the electronic ticket verification result to the ticket verification terminal.

[0073] Optionally, the server 102 can verify the extracted dynamic key of the electronic ticket to be verified based on the dynamic keys of the electronic ticket stored in the key list and the status of their tags; it can verify the extracted device fingerprint to be verified based on the device fingerprint stored in the first storage area; and it can verify the extracted ticket information to be verified based on the ticket information and its status stored in the second storage area. Optionally, when verifying the information to be verified, if the verification meets the predetermined conditions, the server 102 can return a verification result to the ticket verification terminal 104 to indicate that the electronic ticket verification has passed; and if the verification does not meet the preset conditions, the server 102 can return a verification result to the ticket verification terminal 104 to indicate that the electronic ticket verification has failed.

[0074] Based on this, the optional implementation of steps T202 to T204 in the embodiments of this application involves extracting the electronic ticket verification information, including the ticketing information to be verified, the dynamic key of the electronic ticket to be verified, and the device fingerprint to be verified, from the electronic ticket verification request received by the ticket verification terminal 104. Then, based on the electronic ticket verification information and the data stored in the key list, the first storage area, and the second storage area, the verification information is reasonably verified. This can accurately realize the verification of electronic tickets and improve the reliability and security of offline verification and recognition of electronic tickets.

[0075] In some optional embodiments, after receiving the electronic ticket verification request from the ticket verification terminal 104, the server 102 can perform signature verification on the electronic ticket information to be verified extracted from the electronic ticket verification request to determine whether the private key signature of the electronic ticket is valid, so as to reduce the risk of forged or tampered electronic tickets being verified and improve the reliability of electronic ticket verification.

[0076] For example, in some optional embodiments, the information to be verified in the electronic ticket can be verified in step T204 by the following steps T2042~T2048: T2042: Perform a first comparison between the ticketing information to be verified and the ticketing information stored in the second storage area, and determine whether the ticketing information to be verified indicates that the ticket is available.

[0077] For example, in some embodiments, when a ticket is in an unused state and not in a risky state, it can be determined that the ticket is in an available state. Optionally, the "suspicious ticket transfer" state in the following embodiments can be a type of risky state.

[0078] Optionally, during the first comparison, it can be determined whether the ticket information to be verified exists in the ticket information stored in the second storage area. If it exists, it can be determined whether the status marked by the ticket information to be verified is an available status. If it is an available status, the result of the first comparison can be determined to be "yes", and the first comparison passes. Otherwise, if it does not exist, or if it is determined that the status marked by the ticket information to be verified is not an available status (for example, when it is marked as a used status and / or a risk status), the result of the first comparison is determined to be "no", and the first comparison fails.

[0079] It should be noted that the above description of the first comparison, which first "determines whether the ticket information to be verified exists in the ticket information stored in the second storage area" and then "determines whether the status marked by the ticket information to be verified is an available status", is only an illustrative example. In actual applications, the execution order of "determining whether the ticket information to be verified exists in the ticket information stored in the second storage area" and "determining whether the status marked by the ticket information to be verified is an available status" can be changed according to actual needs, and can also be executed in any order or in parallel.

[0080] T2044: Perform a second comparison between the dynamic key of the electronic invoice to be verified and the dynamic keys stored in the key list, and determine whether the dynamic key of the electronic invoice to be verified is a valid key.

[0081] Optionally, during the second comparison, it can be determined whether the dynamic key of the electronic bill to be verified exists in the dynamic keys stored in the key list. If it exists, it can be determined whether the state marked by the dynamic key of the electronic bill to be verified is a valid key state. If it is a valid key state, the result of the second comparison can be determined to be "yes", and the second comparison passes. Otherwise, if it does not exist, or if it is determined that the state marked by the dynamic key of the electronic bill to be verified is not a valid key state (for example, when it is marked as an invalid key), the result of the second comparison can be determined to be "no", and the second comparison fails.

[0082] It should be noted that the above description of the second comparison, which first "determines whether the dynamic key to be verified exists in the dynamic keys stored in the key list" and then "determines whether the state marked by the dynamic key to be verified is a valid key state", is only an illustrative example. In actual applications, the execution order of "determining whether the dynamic key to be verified exists in the dynamic keys stored in the key list" and "determining whether the state marked by the dynamic key to be verified is a valid key state" can be changed according to actual needs, and can also be executed in any order or in parallel.

[0083] Alternatively, if the key list is a valid key list, then during the second comparison, it can be directly determined whether the dynamic key of the electronic ticket to be verified exists in the dynamic keys stored in the valid key list. If it does, the result of the second comparison can be determined to be "yes"; otherwise, the result of the second comparison can be determined to be "no".

[0084] T2046: Perform a third comparison between the device fingerprint to be verified and the device fingerprint stored in the first storage area, and determine whether the device fingerprint to be verified is the same as the device fingerprint corresponding to the ticket purchasing device of the electronic ticket.

[0085] Optionally, during the third comparison, it can be determined whether the device fingerprint to be verified exists in the first storage area. If it exists, it can be determined whether the device fingerprint to be verified is the same as the device fingerprint corresponding to the electronic ticket purchasing device. If it is the same as the device fingerprint corresponding to the electronic ticket purchasing device, the result of the third comparison is determined to be "yes" and the third comparison passes. Otherwise, if it does not exist, or if it is determined that the device fingerprint to be verified is different from the device fingerprint corresponding to the electronic ticket purchasing device, the result of the third comparison is determined to be "no" and the third comparison fails.

[0086] To illustrate this, let's consider an example. After user A purchases a ticket through device A, the server can store the dynamic key of the electronic ticket purchased through device A in a key list, store the device fingerprint of device A (assuming the SEID of the NCF chip can be used directly as the device fingerprint) in the first storage area, and store the ticketing information PW_A in the second storage area. In an illegal resale scenario (i.e., a scalper scenario), user A transfers the electronic ticket from device A to user B's device B. Device B stores the electronic ticket in its near-field communication chip (such as an NFC chip). During electronic ticket verification, the ticket verification terminal 104 extracts the verification information of the electronic ticket corresponding to device B. Since the ticket verification terminal 104 is interacting with device B's near-field communication chip (such as an NFC chip), the device fingerprint it can extract is also device B's device fingerprint (i.e., the SEID of device B's NFC chip). Therefore, when determining whether the fingerprint of the device to be verified is the same as the fingerprint of the electronic ticket purchasing device in the third comparison, there will inevitably be situations where the extracted fingerprint of the device to be verified (i.e., the fingerprint of device B) does not exist in the first storage area, or the fingerprint of the device to be verified is different from the fingerprint of device A (i.e., the electronic ticket purchasing device) corresponding to the ticketing information PW_A stored on the server. In such cases, the result of the third comparison will be "no," and the third comparison will fail. However, if there is no illegal reselling, the ticket verification terminal 104 interacts with the near-field communication chip of device A. The extracted fingerprint of the device to be verified will then be the fingerprint of device A. Therefore, the fingerprint of the device to be verified will be the same as the fingerprint of the device A (i.e., the electronic ticket purchasing device). In such cases, the result of the third comparison will be "yes," and the third comparison will pass.

[0087] It should be noted that the above description of the third comparison, which first "determines whether the device fingerprint stored in the first storage area exists and then "determines whether the device fingerprint to be verified is the same as the device fingerprint corresponding to the electronic ticket purchase device", is only an illustrative example. In actual applications, the execution order of "determining whether the device fingerprint stored in the first storage area exists and "determining whether the device fingerprint to be verified is the same as the device fingerprint corresponding to the electronic ticket purchase device" can be changed according to actual needs, and can also be executed in any order or in parallel.

[0088] It should also be noted that the execution order of the above steps T2042, T2044, and T2046 is not specifically limited in this embodiment of the application. They can be executed in any order, or in part in sequence or in parallel, as long as the verification can be completed.

[0089] T2048: If the results of the first comparison, the second comparison, and the third comparison are all yes, then the electronic invoice verification is confirmed to be successful.

[0090] If the results of the first comparison, the second comparison, and the third comparison are all yes, it means that the ticket information to be verified indicates whether the ticket is available, the dynamic key of the electronic ticket to be verified is a valid key, and the device fingerprint to be verified is the same as the device fingerprint corresponding to the ticket purchase device of the electronic ticket. Therefore, the information to be verified of the electronic ticket meets the relevant characteristics of an unverified electronic ticket, and thus it can be determined that the electronic ticket has been verified.

[0091] Based on this, through the optional implementation of steps T2042~T2048 above, by comparing the ticket information to be verified, comparing the dynamic key of the electronic ticket to be verified, and comparing the device fingerprint to be verified, the electronic ticket can be verified if the results of the first comparison, the second comparison, and the third comparison are all positive. Through the triple comparison verification method, it can be ensured that electronic tickets that are usable (i.e., the ticket is in an available state), have not been verified and used (i.e., the dynamic key of the electronic ticket is a valid key), and whose device fingerprint to be verified is the same as the device fingerprint corresponding to the ticket purchase device can be verified, thereby ensuring the convenience, reliability, and security of offline verification and identification of electronic tickets, and facilitating the prevention of illegal resale (i.e., anti-scalping).

[0092] In some optional embodiments, the electronic ticket processing method in this application further includes: if the result of the third comparison indicates that the device fingerprint to be verified is different from the device fingerprint corresponding to the ticket purchasing device of the electronic ticket, then the verification fails, and the electronic ticket is marked as a suspicious transfer ticket.

[0093] It should be understood that if the device fingerprint to be verified in the information to be verified for an electronic ticket is different from the device fingerprint corresponding to the ticket purchase device, it means that the ticket purchase device performing the ticket verification operation with the ticket verification terminal is not the original ticket purchase device that is verifying the electronic ticket. That is, the electronic ticket may have gone through a transfer process from the original ticket purchase device to the ticket purchase device that is currently verifying it. This transfer process is usually highly related to scalped tickets or the resale of non-compliant tickets.

[0094] Therefore, in this embodiment of the application, when the server 102 verifies the information to be verified for the electronic ticket, if the result of the third comparison indicates that the fingerprint of the device to be verified is different from the fingerprint of the device corresponding to the ticket purchase device of the electronic ticket (that is, the result of the third comparison is "no"), then the third comparison fails, the electronic ticket verification fails, the electronic ticket verification is rejected, and the electronic ticket is marked as a suspicious resale ticket. This can achieve cross-device interception of scalped tickets or non-compliant resale tickets, thereby effectively preventing illegal resale (i.e., anti-scalping) and risk control of non-compliant ticket resale. It also provides the possibility for the issuer to hold scalped tickets or non-compliant ticket resale accountable.

[0095] Optionally, the aforementioned suspicious resale status can be considered as a risk status. Therefore, the server 102 can mark the ticketing information of the electronic tickets stored in the second storage area with a risk status mark indicating that the ticketing information is a suspicious resale.

[0096] In some optional embodiments, the electronic ticket processing method in this application further includes: if the verification result indicates that the electronic ticket verification is successful, generating a random string and sending the random string to the ticket purchasing device through the ticket verification terminal, so as to overwrite the dynamic key of the electronic ticket in the ticket purchasing device with the random string.

[0097] After the electronic ticket verification is successful, the server 102 can generate a random string using any random string generation algorithm and send it to the ticket verification terminal 104. The ticket verification terminal 104 can then send the string to the ticket purchasing device 106 via a short-range communication (NRCM) connection. For example, if the NRCM chip 1062 of the ticket purchasing device 106 is an NFC chip and the NRCM connection is an NFC connection, the ticket verification terminal 104 can use an NFC write command to write the random string into the independent storage area of ​​the NRCM chip 1062 of the ticket purchasing device 106, thereby overwriting the dynamic key of the electronic ticket in the ticket purchasing device 106 with the random string.

[0098] It should be understood that by generating a random string to overwrite the dynamic key of the electronic ticket in the ticketing device 106 in this embodiment of the application, the situation in which a single electronic ticket in the same ticketing device 106 is repeatedly verified can be avoided, thereby reducing the risk of repeated use of electronic tickets and improving the reliability and security of electronic ticket verification.

[0099] Optionally, if the verification result indicates that the electronic ticket verification is successful, the server 102 can also mark the electronic ticket dynamic key of the electronic ticket in the key list as an invalid key. This further prevents the electronic ticket from being verified multiple times, reduces the risk of repeated use of electronic tickets, and improves the reliability and security of electronic ticket verification.

[0100] In other embodiments, the electronic ticket processing method may include: if the verification result indicates that the electronic ticket has passed verification, sending a clearing command to the ticket purchasing device through the ticket verification terminal, so that the ticket purchasing device clears the dynamic key of the electronic ticket in the ticket purchasing device based on the clearing command. This can also prevent the electronic ticket from being verified repeatedly.

[0101] In some alternative embodiments, after the verification result indicates that the electronic ticket has been verified, the electronic ticket dynamic key in the ticketing device 106 may not be overwritten or cleared. Instead, the electronic ticket dynamic key of the electronic ticket in the key list of the server 102 may be marked as an invalid key or cleared, as long as the requirements are met.

[0102] Optionally, when overwriting or clearing data (such as the dynamic key for electronic tickets) in the ticketing device 106, the operating system of the ticketing terminal can issue an instruction to clear or overwrite the corresponding data stored in the near-field communication chip 1062. Alternatively, other feasible methods can be used; there is no single limitation.

[0103] In some optional embodiments, the electronic ticket processing method in this application embodiment further includes: obtaining the spatiotemporal characteristic information of the electronic ticket from the electronic ticket verification request.

[0104] Optionally, the spatiotemporal characteristics of the electronic ticket may include the ticketing time information and ticketing location information corresponding to the electronic ticket. For example, the ticketing time information may include at least one of the ticket usage time information and verification time information; the ticketing location information may include at least one of the ticket usage location information and verification location information. For example, taking a concert ticket as an example, the usage time information may be the performance time of the concert corresponding to the ticket, the usage location information may be the performance location of the concert corresponding to the ticket, the verification time information may be the verification time of the concert ticket, and the verification location information may be the verification location of the concert ticket. As another example, taking a train ticket as an example, the usage time information may be the departure time and travel time of the train corresponding to the ticket, the usage location information may be the route information of the train corresponding to the ticket, the verification time information may be the verification time of the train ticket, and the verification location information may be the verification location of the train ticket. In some optional embodiments, the server 102 may extract the ticket usage time information and / or usage location information from the ticket information carried in the electronic ticket verification request, and may extract the ticket verification time information and / or verification location information carried in the electronic ticket verification request and determined by the ticket verification terminal 104 during ticket verification.

[0105] In some optional embodiments, before verifying the information to be verified of the electronic ticket in step T204, the electronic ticket processing method further includes: verifying the ticketing time and ticketing location of the electronic ticket based on spatiotemporal feature information; if the verification is successful, then performing the verification operation based on the extracted information to be verified of the electronic ticket, as well as the data stored in the key list, the first storage area, and the second storage area respectively, to verify the information to be verified.

[0106] For example, when verifying the ticketing time of electronic tickets based on spatiotemporal feature information, the ticketing time verification passes if the ticketing time information of the electronic ticket meets the predetermined time conditions, otherwise the verification fails. For example, assuming that the ticketing time information includes usage time information and verification time information, if the usage time information meets the predetermined usage time and the verification time information meets the predetermined verification time, the ticketing time verification passes, otherwise the verification fails.

[0107] For example, when verifying the ticketing location of electronic tickets based on spatiotemporal feature information, the ticketing location verification passes if the ticketing location information of the electronic ticket meets the preset location conditions, otherwise the verification fails. For example, assuming that the ticketing location information includes usage location information and verification location information, if the usage location information meets the predetermined usage location and the verification location information meets the predetermined verification location, the ticketing location verification passes, otherwise the verification fails.

[0108] Optionally, once both the ticket time verification and ticket location verification are successful, step T204 can be executed to continue verifying the information to be verified on the electronic ticket.

[0109] To facilitate understanding, we can use the verification of electronic concert tickets as an example. For instance, if the extracted spatiotemporal feature information of the electronic ticket (i.e., the concert ticket) includes usage time information and verification time information, and the usage time information indicates that the concert performance time is 19:00~22:00, and the verification time information indicates that the verification time for the concert ticket is 17:30, assuming the preset usage time is 19:00~22:00 and the preset verification time is 17:00~22:00, then the usage time information matches the preset usage time, and the verification time information matches the preset verification time, so the ticket time verification can be determined to be successful. However, if the usage time information indicates that the concert performance time is 14:00~17:00 and / or the verification time information indicates that the verification time for the concert ticket is 12:30, then the usage time information does not match the preset usage time and / or the verification time information does not match the preset verification time, so the ticket time verification can be determined to be unsuccessful. For example, if the extracted spatiotemporal feature information of the electronic ticket includes usage location information and verification location information, and the usage location information indicates that the concert performance location is venue A, and the verification location information indicates that the concert verification location is venue A, assuming the preset usage location is venue A, and the preset verification location is venue A, then the usage location information matches the preset usage location, and the verification location information matches the preset verification location, so it can be determined that the ticket location verification is successful; if the usage location information indicates that the concert performance location is venue B and / or the verification location information indicates that the concert ticket verification location is venue B, then the usage location information does not match the preset usage location and / or the verification location information does not match the preset verification location, so it can be determined that the ticket location verification is unsuccessful. Once both the ticket time verification and ticket location verification are successful, the server 102 can perform the verification operation in step T204 based on the extracted electronic ticket information to be verified, as well as the data stored in the key list, the first storage area, and the second storage area, to continue verifying the concert ticket electronically and return the electronic ticket verification result to the ticket verification terminal 104. It is understood that the times and locations mentioned above are merely examples and are not intended to limit the scope of this application's embodiments.

[0110] If the ticketing time verification and / or ticketing location verification fails, it indicates that the electronic ticket being verified may be a problematic ticket or an incorrect ticket that does not meet the requirements for the ticketing time and / or ticketing location. For example, taking concert tickets as an example, in some cases, users arrive at the concert venue too early for verification or only verify the ticket after the concert has ended, resulting in the ticket being invalid. In other cases, users go to the wrong concert venue for verification, also resulting in the ticket being invalid.

[0111] It should be understood that the above-described implementation scheme of this application, by verifying the ticketing time and ticketing location of electronic tickets based on spatiotemporal feature information, and then performing the operation of verifying the information to be verified of electronic tickets in step T204 after the verification is passed, can filter out problematic tickets or erroneous tickets that do not meet the requirements for ticketing time and / or ticketing location, avoid verifying the information to be verified for problematic tickets or erroneous tickets that do not meet the requirements for ticketing time and / or ticketing location, and help improve the efficiency and reliability of electronic ticket verification.

[0112] It is understood that the foregoing description of the electronic invoice processing method is merely an exemplary description of the embodiments of this application and is not intended to limit the embodiments of this application in any way.

[0113] Figure 3 This is a flowchart illustrating the steps of another electronic ticket processing method according to an embodiment of this application. According to a second aspect of an embodiment of this application, an electronic ticket processing method is provided. Optionally, this method can be applied to a ticket verification terminal 104. (Refer to...) Figure 3 As shown, the electronic ticket processing method may include the following steps S302, S304, S306, and S308, specifically: S302: Establish a short-range communication connection with the ticketing equipment.

[0114] S304: Read electronic ticket verification data packets from the short-range communication chip of the ticketing device via a short-range communication connection.

[0115] In this embodiment of the application, the electronic ticket verification data packet includes: ticketing information to be verified, the electronic ticket dynamic key to be verified, and the device fingerprint to be verified.

[0116] S306: Based on the information contained in the electronic invoice verification data packet, generate an electronic invoice verification request and send the electronic invoice verification request to the server.

[0117] S308: Receive the electronic invoice verification result returned by the server based on the electronic invoice verification request.

[0118] Based on this, the electronic ticket processing method in steps S302-S308 of the present application embodiment has the following advantages: First, the verification data packet of the electronic ticket is stored in the short-range communication chip 1062 of the ticketing device 106. During electronic ticket verification, the verification terminal 104 can connect with the ticketing device 106 via short-range communication to read the verification data packet and generate an electronic ticket verification request based on the information contained in the verification data packet. This allows the electronic ticket verification request to be sent to the server 102 for offline verification and identification, thus avoiding delays or even failures in electronic ticket verification caused by network congestion or signal interruption between the ticketing device and the server. Users also do not need to repeatedly refresh the electronic ticket status during the verification process, which not only improves the reliability of electronic ticket verification but also enhances the user experience. Second, since the electronic ticket verification data packet includes the ticketing information to be verified, the dynamic key of the electronic ticket to be verified, and the verification... The device fingerprint authentication method is used. When the server verifies electronic tickets, it does so based on an electronic ticket verification request. This request is generated based on information contained in the electronic ticket verification data packet, enabling accurate verification and improving the reliability and security of offline electronic ticket verification. Furthermore, since the dynamic key of the electronic ticket to be verified is included in the electronic ticket verification data packet, a dynamic verification mechanism can be used for subsequent verification. By utilizing the non-repeatable nature of the dynamic key, security is effectively improved. Compared to electronic ticket verification mechanisms based on static QR codes, this method significantly enhances the dynamic anti-counterfeiting capability of electronic ticket verification and further reduces the risk of electronic tickets being screenshotted, spread, and resold. It effectively prevents illegal resale (i.e., scalping). Moreover, compared to other electronic ticket verification mechanisms such as those based on dynamic QR codes, it further avoids reliance on network access and screen-on operation, thus improving user experience. Therefore, the technical solution of this application provides an electronic ticket processing solution that balances offline availability and reliability, security, and possesses good dynamic anti-counterfeiting capabilities, effectively improving user experience.

[0119] In some optional embodiments, the dynamic key for the electronic ticket to be verified is obtained based on the identification information of the short-range communication chip of the ticketing device. This further improves the reliability and security of offline verification and identification of electronic tickets.

[0120] It should be understood that the relevant content of the electronic ticket processing method in the second aspect has been described in the aforementioned method embodiment of the first aspect. The relevant content and beneficial effects can be understood in conjunction with the content of the previous embodiments, and will not be repeated here.

[0121] Figure 4This is a flowchart illustrating the steps of another electronic ticket processing method according to an embodiment of this application. According to a third aspect of an embodiment of this application, an electronic ticket processing method is provided. Optionally, this method can be applied to a ticket purchasing device 106. (Refer to...) Figure 4 As shown, the electronic ticket processing method may include the following steps S402 and S404, specifically: S402: Receive the electronic ticket returned by the server based on the ticket purchase request.

[0122] In this embodiment of the application, the electronic ticket includes: ticketing information, electronic ticket dynamic key, and device fingerprint of the ticketing device.

[0123] S404: Store electronic tickets in a separate storage area of ​​the short-range communication chip of the ticketing device.

[0124] Based on this, the electronic ticket processing method in steps S402-S404 of this application embodiment has two aspects. First, in this application embodiment, the ticket purchasing device 106 receives the electronic ticket returned by the server 102 based on the ticket purchase request and stores the electronic ticket in the independent storage area of ​​its near-field communication chip 1062. Therefore, in subsequent electronic ticket verification, offline verification and identification can be achieved based on the communication of the near-field communication chip, thereby avoiding the problem of electronic ticket verification delay or even failure caused by network congestion or signal interruption between the ticket purchasing device and the server. Users do not need to repeatedly refresh the electronic ticket status during the electronic ticket verification process. Therefore, it is not only beneficial to improve the reliability of electronic ticket verification, but also beneficial to improve the user experience. In addition, storing the electronic ticket in the independent storage area of ​​the near-field communication chip 1062 can also avoid interference to the operating system caused by electronic ticket writing and verification. Second, since the generated electronic ticket includes ticketing information, electronic ticket dynamic key, and the device fingerprint of the ticket purchasing device, from The electronic ticket is well bound to the device fingerprint of the ticketing device 106, thus reducing the risk of the electronic ticket data written to the near-field communication chip 1062 being copied or tampered with, thereby improving the data security of the electronic ticket. For electronic ticket verification, this significantly enhances verification security. Furthermore, since the electronic ticket includes a dynamic key written to the near-field communication chip 1062, a dynamic verification mechanism can be used for subsequent verification. By utilizing the non-repeatable nature of the dynamic key, security is effectively improved. Compared to electronic ticket verification mechanisms based on static QR codes, this significantly enhances the dynamic anti-counterfeiting capability of electronic ticket verification and further reduces the risk of electronic tickets being screenshotted, spread, and resold, effectively preventing illegal resale (i.e., preventing scalping). Compared to other electronic ticket verification mechanisms such as those based on dynamic QR codes, this also avoids reliance on network and screen-on operation, improving user experience. Therefore, the technical solution of this application provides an electronic ticket processing solution that balances offline availability and reliability, security, and possesses good dynamic anti-counterfeiting capabilities, effectively improving user experience.

[0125] Optionally, the electronic ticket can be an encrypted ticket. In some optional embodiments, the dynamic key of the electronic ticket is obtained based on the identification information of the near-field communication chip 1062 of the ticketing device 106. It should be understood that since the dynamic key of the electronic ticket is generated based on the identification information of the near-field communication chip 1062 of the ticketing device 106, the electronic ticket is not only bound to the device fingerprint of the ticketing device 106, but also to the identification information of the near-field communication chip 1062. Therefore, the risk of the electronic ticket data written to the near-field communication chip 1062 being copied or tampered with is better reduced, which is conducive to further improving the data security of the electronic ticket. For electronic ticket verification, it can better improve the verification security.

[0126] In some optional embodiments, the electronic ticket verification method further includes: establishing a short-range communication connection with the ticket verification terminal 104, and providing the ticket verification terminal 104 with an electronic ticket verification data packet from the short-range communication chip 1062 via the short-range communication connection. The electronic ticket verification data packet includes: ticketing information to be verified, a dynamic key for the electronic ticket to be verified, and a device fingerprint to be verified. This facilitates the ticket verification terminal 104 in obtaining the electronic ticket verification data packet, enabling reliable verification of the electronic ticket.

[0127] In some optional embodiments, a random string is received by the ticket verification terminal 104 to overwrite the dynamic key of the electronic ticket in the ticketing device. It should be understood that overwriting the dynamic key of the electronic ticket in the ticketing device 106 with a random string in this embodiment of the application can prevent a single electronic ticket in the same ticketing device 106 from being verified multiple times, reducing the risk of repeated use of electronic tickets and improving the reliability and security of electronic ticket verification.

[0128] It should be understood that the relevant content of the electronic invoice processing method in the third aspect has been described in the aforementioned method embodiment of the first aspect. The relevant content and beneficial effects can be understood in conjunction with the content of the previous embodiments, and will not be repeated here.

[0129] Below, refer to Figure 5 The illustrated scenario provides an exemplary description of the implementation process of the electronic ticket processing scheme in this application embodiment. When understanding this scenario example, it can be applied to the scenario of concert ticket purchase and ticket verification.

[0130] The process of generating electronic invoices: such as Figure 5As shown, users can purchase tickets through the concert ticketing interface using ticketing device 106. Ticketing device 106 can generate a purchase request based on the user's action and send it to server 102. Then, server 102 can generate a data packet for the electronic ticket of the concert based on the purchase request from ticketing device 106 and write the data packet into the short-range communication chip 1062 of ticketing device 106. Figure 5 The example near-field communication (NFC) chip 1062 is used as an example. Optionally, the server 102 can obtain the identification information of the NFC chip 1062 from the ticket purchase request of the ticket purchase device 106, and collect the device fingerprint of the ticket purchase device 106. Then, based on the identification information of the NFC chip 1062, it generates a dynamic key for the electronic ticket. Based on the ticket information to be purchased, the dynamic key for the electronic ticket, and the device fingerprint of the ticket purchase device 106, it generates an electronic ticket. The server can then perform private key signing on the electronic ticket and send the signed electronic ticket to the ticket purchase device 106, so that the ticket purchase device 106 can write the electronic ticket into the independent storage area of ​​the NFC chip 1062. Furthermore, the server 102 can store the dynamic key for the electronic ticket in a key list, store the device fingerprint in a first storage area, and store the ticket information in a second storage area. It can also mark the status of the dynamic key for the electronic ticket and the ticket information.

[0131] The verification process for electronic invoices: such as Figure 5 As shown, during concert ticket verification, the ticket purchasing device 106 can be online or offline. The user can bring the ticket purchasing device 106 close to the ticket verification terminal 104, and the ticket verification terminal 104 can establish a short-range communication connection with the short-range communication chip 1062 of the ticket purchasing device 106. Figure 5(In this example, an NFC connection can be used). Then, the ticket verification terminal 104 can read the electronic ticket verification data packet from the near-field communication chip 1062 of the ticketing device 106 via NFC connection. This electronic ticket verification data packet includes: ticketing information to be verified, the dynamic key of the electronic ticket to be verified, and the device fingerprint to be verified. The dynamic key of the electronic ticket to be verified is obtained based on the identification information of the near-field communication chip 1062 of the ticketing device 106. Based on the information contained in the electronic ticket verification data packet, an electronic ticket verification request is generated and sent to the server 102. The server 102 can then receive the electronic ticket verification request and extract the information to be verified from it. This information includes: ticketing information to be verified, the dynamic key of the electronic ticket to be verified, and the device fingerprint to be verified. Based on the extracted information and the data stored in the key list, the first storage area, and the second storage area, the server verifies the information and returns the electronic ticket verification result to the ticket verification terminal 104. Optionally, server 102 determines whether the electronic ticket verification passes through a first comparison, a second comparison, and a third comparison. For example, if the results of the first comparison, the second comparison, and the third comparison are all yes, then the electronic ticket verification is considered successful. If the electronic ticket verification passes, server 102 can generate a random string and send it to ticket verification terminal 104. Ticket verification terminal 104 writes the random string to the NFC chip of ticketing device 106 via an NFC write command, thereby overwriting the electronic ticket dynamic key in ticketing device 106 with the random string. Server 102 then marks the electronic ticket dynamic key of this electronic ticket in the key list as an invalid key, thus completing the verification and cancellation of a single concert ticket. If the result of the third comparison indicates that the device fingerprint to be verified is different from the device fingerprint corresponding to the ticketing device of the electronic ticket, then the verification fails directly. Server 102 then marks the electronic ticket as suspicious for resale, thereby preventing illegal resale (i.e., anti-scalping) and controlling the risk of non-compliant ticket resale.

[0132] It should be understood that the above Figure 5 The content can also be understood by referring to the preceding text, and the above... Figure 5 The examples provided are for illustrative purposes only and are not intended to limit any aspects of the embodiments described in this application.

[0133] According to a fourth aspect of the embodiments of this application, a server 102 is provided, comprising: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; the memory is used to store a computer program; and the processor is used to execute the electronic ticket processing method described in the first aspect by running the computer program stored in the memory.

[0134] Figure 6 A schematic block diagram of an example server in an embodiment of this application is shown. This application does not limit the specific implementation of the server 102; however, it is exemplarily shown below. Figure 6 The server 102 provided in this application embodiment may include: a processor 1002, a communications interface 1004, a memory 1006, and a communication bus 1008. Wherein: The processor 1002, communication interface 1004, and memory 1006 communicate with each other via communication bus 1008.

[0135] Communication interface 1004 is used to communicate with other electronic devices or servers.

[0136] The processor 1002 is used to execute the computer program 1010, specifically the relevant steps in the method embodiment of the first aspect described above.

[0137] Specifically, computer program 1010 may include program code that includes computer operation instructions.

[0138] The processor 1002 may be a CPU, a GPU (Graphics Processing Unit), an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application. The one or more processors included in the smart device may be processors of the same type, such as one or more CPUs; or they may be processors of different types, such as one or more CPUs and one or more ASICs.

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

[0140] Specifically, computer program 1010 can be used to cause processor 1002 to execute the methods in any of the embodiments of the first aspect described above.

[0141] The specific implementation of each step in computer program 1010 can be found in the corresponding steps and units described in any of the embodiments of the electronic ticket processing method in the first aspect mentioned above, and 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 aforementioned method embodiments, and will not be repeated here.

[0142] The server 102 in this embodiment has been described in detail in the aforementioned embodiment of the electronic invoice processing method. Therefore, its related content and beneficial effects can be understood by referring to the above-mentioned method embodiment, and will not be repeated here.

[0143] According to a fifth aspect of the embodiments of this application, a ticket verification terminal 104 is provided. (See also...) Figure 7 As shown, the ticket verification terminal 104 may include: a second short-range communication chip 1042 and a processor 1044; wherein, the second short-range communication chip 1042 is used to establish a short-range communication connection with the ticket purchasing device 106; the processor 1044 is used to read an electronic ticket verification data packet from the short-range communication chip 1062 of the ticket purchasing device 106 through the short-range communication connection, wherein the electronic ticket verification data packet includes: ticketing information to be verified, an electronic ticket dynamic key to be verified, and a device fingerprint to be verified, wherein the electronic ticket dynamic key to be verified is obtained based on the identification information of the short-range communication chip 1062 of the ticket purchasing device 106; based on the information contained in the electronic ticket verification data packet, generate an electronic ticket verification request and send the electronic ticket verification request to the server 102; and receive the electronic ticket verification result returned by the server 102 based on the electronic ticket verification request.

[0144] According to a sixth aspect of the embodiments of this application, a ticket purchasing device 106 is provided. (Refer to...) Figure 8 As shown, the ticketing device 106 may include a near-field communication (NFC) chip 1062 and a processor 1064. The processor 1064 is used to receive an electronic ticket returned by the server 102 based on a ticket purchase request. The electronic ticket is an encrypted ticket and includes ticketing information, a dynamic key for the electronic ticket, and a device fingerprint of the ticketing device. The dynamic key for the electronic ticket is obtained based on the identification information of the NFC chip 1062 of the ticketing device 106. The NFC chip 1062 is used to store the electronic ticket in an independent storage area.

[0145] The server 102, ticket verification terminal 104, and ticket purchasing device 106 in this application embodiment have been described in detail in the previous embodiments. Therefore, their related content and beneficial effects can be understood by referring to the previous embodiments, and will not be repeated here.

[0146] According to a seventh aspect of the embodiments of this application, this application also provides a computer storage medium storing a computer program thereon. When executed by a processor, the computer program implements the electronic ticket processing method described in any one of the multiple method embodiments of the first, second, and third aspects. Optionally, the computer storage medium includes, but is not limited to, a compact disc read-only memory (CD-ROM), a random access memory (RAM), a floppy disk, a hard disk, or a magneto-optical disk.

[0147] According to an eighth aspect of the embodiments of this application, the embodiments of this application also provide a computer program product, including a computer program that, when executed by a processor, implements the electronic ticket processing method as described in any of the embodiments of the plurality of method embodiments in the first, second, and third aspects above.

[0148] The computer storage medium / computer program product embodiments in this application have been described in detail in the foregoing electronic ticket processing method embodiments. Therefore, their related content and beneficial effects can be understood by referring to the above method embodiments, and will not be repeated here.

[0149] Furthermore, it should be noted that the user-related information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to sample data used for training the model, data used for analysis, stored data, displayed data, etc.) involved in the embodiments of this application are all information and data authorized by the user or fully authorized by all parties. Moreover, 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.

[0150] 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.

[0151] 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.

[0152] 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 specific applications, but such implementations should not be considered beyond the scope of the embodiments of this application.

[0153] The term "comprising" and its variations as used herein are open-ended, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". It should be noted that the concepts of "first", "second", etc., mentioned in the embodiments of this application are only used to distinguish different devices, modules, or units, and are not used to limit the order of functions performed by these devices, modules, or units or their interdependencies. It should be noted that the modifications of "a" and "a plurality" mentioned in the embodiments of this application are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0154] 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 method for processing electronic invoices, comprising: Based on the ticket purchase request from the ticket purchase device, collect the device fingerprint of the ticket purchase device; An electronic ticket is generated based on the ticket information to be purchased, the dynamic key of the electronic ticket, and the device fingerprint of the ticket purchasing device; The electronic ticket is sent to the ticket purchasing device so that the ticket purchasing device can write the electronic ticket into the short-range communication chip of the ticket purchasing device.

2. The method according to claim 1, wherein, The method further includes: Based on the ticket purchase request, the identification information of the near-field communication chip is obtained, and based on the identification information, the dynamic key of the electronic ticket is generated.

3. The method according to claim 1, wherein, The step of sending the electronic ticket to the ticket purchasing device, so that the ticket purchasing device can write the electronic ticket into the short-range communication chip of the ticket purchasing device, includes: The electronic ticket is signed with a private key, and the signed electronic ticket is sent to the ticket purchasing device so that the ticket purchasing device can write the signed electronic ticket into the short-range communication chip of the ticket purchasing device.

4. The method according to any one of claims 1-3, wherein, The method further includes: The electronic ticket dynamic key of the electronic ticket is stored in the key list, the device fingerprint is stored in the first storage area, and the ticketing information is stored in the second storage area; Furthermore, status markers are applied to the electronic ticket dynamic key and the ticketing information, respectively.

5. The method according to claim 4, wherein, The method further includes: Receive an electronic ticket verification request from a ticket verification terminal, and extract the electronic ticket verification information from the electronic ticket verification request. The electronic ticket verification information includes: ticketing information to be verified, electronic ticket dynamic key to be verified, and device fingerprint to be verified. Based on the extracted information to be verified of the electronic ticket, as well as the data stored in the key list, the first storage area, and the second storage area, the information to be verified is verified, and the electronic ticket verification result is returned to the ticket verification terminal.

6. The method according to claim 5, wherein, The method further includes: obtaining the spatiotemporal feature information of the electronic invoice from the electronic invoice verification request; Before verifying the information to be verified based on the extracted information to be verified from the electronic ticket, and the data stored in the key list, the first storage area, and the second storage area respectively, the method further includes: Based on the aforementioned spatiotemporal feature information, the ticketing time and ticketing location of the electronic ticket are verified. If the verification is successful, the operation of verifying the information to be verified based on the extracted electronic ticket information, the key list, the data stored in the first storage area and the second storage area respectively, is performed.

7. The method according to claim 5, wherein, The verification of the information to be verified based on the extracted electronic ticket information, and the data stored in the key list, the first storage area, and the second storage area, includes: The ticketing information to be verified is compared with the ticketing information stored in the second storage area to determine whether the ticket indicated by the ticketing information to be verified is in an available state. A second comparison is performed between the dynamic key of the electronic invoice to be verified and the dynamic keys stored in the key list, and it is determined whether the dynamic key of the electronic invoice to be verified is a valid key. Furthermore, the device fingerprint to be verified is compared with the device fingerprint stored in the first storage area in a third comparison, and it is determined whether the device fingerprint to be verified is the same as the device fingerprint corresponding to the ticket purchasing device of the electronic ticket. If the results of the first comparison, the second comparison, and the third comparison are all yes, then the electronic invoice verification is confirmed to be successful.

8. The method according to claim 7, wherein, The method further includes: If the result of the third comparison indicates that the device fingerprint to be verified is different from the device fingerprint corresponding to the ticket purchasing device of the electronic ticket, the verification fails, and the electronic ticket is marked as a suspicious transfer ticket.

9. The method according to claim 8, wherein, The method further includes: If the verification result indicates that the electronic ticket verification is successful, a random string is generated and sent to the ticket purchasing device through the ticket verification terminal, so as to overwrite the electronic ticket dynamic key in the ticket purchasing device with the random string.

10. An electronic ticket processing method, applied to a ticket verification terminal, the method comprising: Establish a short-range communication connection with the ticketing equipment; Through the short-range communication connection, an electronic ticket verification data packet is read from the short-range communication chip of the ticketing device. The electronic ticket verification data packet includes: ticketing information to be verified, a dynamic key for the electronic ticket to be verified, and a device fingerprint to be verified. Based on the information contained in the electronic invoice verification data packet, an electronic invoice verification request is generated and sent to the server. Receive the electronic invoice verification result returned by the server based on the electronic invoice verification request.

11. An electronic ticket processing method, applied to a ticket purchasing device, the method comprising: The receiving server returns an electronic ticket based on the ticket purchase request, wherein the electronic ticket includes: ticketing information, a dynamic key for the electronic ticket, and the device fingerprint of the ticket purchase device; The electronic ticket is stored in the independent storage area of ​​the short-range communication chip of the ticketing device.

12. The method according to claim 11, wherein, The method further includes: A short-range communication connection is established with the ticket verification terminal. Through the short-range communication connection, an electronic ticket verification data packet from the short-range communication chip is provided to the ticket verification terminal. The electronic ticket verification data packet includes: ticket information to be verified, a dynamic key for the electronic ticket to be verified, and a device fingerprint to be verified.

13. The method according to claim 11, wherein, The method further includes: A random string is received through the ticket verification terminal to overwrite the dynamic key of the electronic ticket in the ticket purchasing device.

14. A server, comprising: The processor, the communication interface, the memory, and the communication bus are provided, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus. The memory is used to store computer programs; The processor is configured to perform the method as described in any one of claims 1-9 by running the computer program stored in the memory.

15. A ticket verification terminal, comprising: The second short-range communication chip and processor; among which, The second short-range communication chip is used to establish a short-range communication connection with the ticketing device; The processor is configured to read an electronic ticket verification data packet from the short-range communication chip of the ticketing device via the short-range communication connection, wherein the electronic ticket verification data packet includes: ticketing information to be verified, a dynamic key for the electronic ticket to be verified, and a device fingerprint to be verified; generate an electronic ticket verification request based on the information contained in the electronic ticket verification data packet, and send the electronic ticket verification request to the server; and receive the electronic ticket verification result returned by the server based on the electronic ticket verification request.

16. A ticket purchasing device, comprising: Near-field communication chips and processors; among them, The processor is used to receive an electronic ticket returned by the server based on the ticket purchase request. The electronic ticket includes: ticketing information, a dynamic key for the electronic ticket, and the device fingerprint of the ticket purchase device. The near-field communication chip is used to store the electronic ticket in an independent storage area.

17. A computer storage medium having a computer program stored thereon, which, when executed by a processor, implements the method as described in any one of claims 1-13.

18. A computer program product comprising a computer program that, when executed by a processor, implements the method as described in any one of claims 1-13.

Images