Granted Patent B2

US 12,271,889 · App. 16/888,504 · Granted Apr 8, 2025

Inventors: Jiajia Li (Hangzhou, CN); Fen Zhai (Hangzhou, CN); Fei Ni (Hangzhou, CN); Jiao Lu (Hangzhou, CN)

Assignee: Advanced New Technologies Co., Ltd.

G06Q20/3278G06Q20/108G06Q20/326G06Q20/401G06Q50/40G07B15/02H04W4/80H04W8/18H04W12/033H04W76/10G06Q2220/00G06Q2240/00

Abstract

Claims (52)

1. A method for fare payment performed by a terminal device that supports host-based card emulation (HCE), wherein the method comprises:

receiving an HCE-based routing instruction that includes an application identifier of an application installed on the terminal device from a fare collection device of a public transportation system;

in response to the HCE-based routing instruction, establishing a near field communication (NFC) connection with the fare collection device, wherein establishing the NFC connection comprises establishing a connection to the application;

receiving, from the fare collection device, and through the NFC connection, a public transportation system identifier that identifies the fare collection device;

obtaining, from locally pre-stored voucher-related information, and by using the public transportation system identifier, voucher-related information of a user that corresponds to the public transportation system identifier, wherein the voucher-related information of the user comprises an account identifier of the user, serialized number of the public transportation system that acknowledges a validity of payment-related information, a validity period of the payment-related information, a private key of the user, and a private key of the public transportation system;

generating payment-related information of the user based on the voucher-related information, wherein generating the payment-related information of the user comprises signing the account identifier of the user with the private key of the user and the private key of the public transportation system;

transforming the payment-related information into multiple data packets;

encrypting the multiple data packets based on an encryption algorithm that is agreed upon with the public transportation system to produce a respective encrypted data packet corresponding to each data packet; and

transmitting, according to the public transportation system identifier, the respective encrypted data packets to the fare collection device through the NFC connection.

2. The method of claim 1 , wherein the terminal device locally stores, at a local storage of the terminal device, different voucher-related information that is specific to different transportation systems.

3. The method of claim 1 , wherein the encrypted data packets are decryptable by the fare collection device based on a decryption algorithm corresponding to the encryption algorithm.

4. The method of claim 1 , wherein transforming, the payment-related information into the multiple data packets comprises:

receiving, by using the NFC connection, a data offset sent by the fare collection device; and

splitting the payment-related information into data packets based on the data offset.

5. The method of claim 1 , further comprising:

receiving, at the terminal device and by using the NFC connection, a verification result of the payment-related information that is sent by the fare collection device; and

displaying the verification result on the terminal device.

6. A non-transitory, computer-readable medium storing one or more instructions that when executed by a computer system comprising a terminal device cause the computer system to perform operations for fare payment, wherein the terminal device supports host-based card emulation (HCE), and wherein the operations comprise:

receiving an HCE-based routing instruction that includes an application identifier of an application installed on the terminal device from a fare collection device of a public transportation system;

in response to the HCE-based routing instruction, establishing a near field communication (NFC) connection with the fare collection device, wherein establishing the NFC connection comprises establishing a connection to the application;

receiving, from the fare collection device, and through the NFC connection, a public transportation system identifier that identifies the fare collection device;

obtaining, from locally pre-stored voucher-related information, and by using the public transportation system identifier, voucher-related information of a user that corresponds to the public transportation system identifier, wherein the voucher-related information of the user comprises an account identifier of the user, serialized number of the public transportation system that acknowledges a validity of payment-related information, a validity period of the payment-related information, a private key of the user, and a private key of the public transportation system;

generating payment-related information of the user based on the voucher-related information, wherein generating the payment-related information of the user comprises signing the account identifier of the user with the private key of the user and the private key of the public transportation system;

transforming the payment-related information into multiple data packets;

encrypting the multiple data packets based on an encryption algorithm that is agreed upon with the public transportation system to produce a respective encrypted data packet corresponding to each data packet; and

transmitting, according to the public transportation system identifier, the respective encrypted data packets to the fare collection device through the NFC connection.

7. The non-transitory, computer-readable medium of claim 6 , wherein the terminal device locally stores, at a local storage of the terminal device, different voucher-related information that is specific to different transportation systems.

8. The non-transitory, computer-readable medium of claim 6 , wherein the encrypted data packets are decryptable by the fare collection device based on a decryption algorithm corresponding to the encryption algorithm.

9. The non-transitory, computer-readable medium of claim 6 , wherein the operations further comprise:

receiving, at the terminal device and by using the NFC connection, a verification result of the payment-related information that is sent by the fare collection device; and

displaying the verification result on the terminal device.

10. The non-transitory, computer-readable medium of claim 6 , wherein transforming the payment-related information into the multiple data packets comprises:

receiving, by using the NFC connection, a data offset sent by the fare collection device; and

splitting the payment-related information into data packets based on the data offset.

11. A computer-implemented system, comprising:

a terminal device that supports host-based card emulation (HCE), wherein the terminal device comprises one or more computers and comprise one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations for fare payment, wherein the operations comprise:

receiving an HCE-based routing instruction that includes an application identifier of an application installed on the terminal device from a fare collection device of a public transportation system;

in response to the HCE-based routing instruction, establishing a near field communication (NFC) connection with the fare collection device, wherein establishing the NFC connection comprises establishing a connection to the application;

receiving, from the fare collection device, and through the NFC connection, a public transportation system identifier that identifies the fare collection device;

obtaining, from locally pre-stored voucher-related information, and by using the public transportation system identifier, voucher-related information of a user that corresponds to the public transportation system identifier, wherein the voucher-related information of the user comprises an account identifier of the user, serialized number of the public transportation system that acknowledges a validity of payment-related information, a validity period of the payment-related information, a private key of the user, and a private key of the public transportation system;

generating payment-related information of the user based on the voucher-related information, wherein generating the payment-related information of the user comprises signing the account identifier of the user with the private key of the user and the private key of the public transportation system;

transforming the payment-related information into multiple data packets;

encrypting the multiple data packets based on an encryption algorithm that is agreed upon with the public transportation system to produce a respective encrypted data packet corresponding to each data packet; and

transmitting, according to the public transportation system identifier, the respective encrypted data packets to the fare collection device through the NFC connection.

12. The computer-implemented system of claim 11 , wherein the terminal device locally stores, at a local storage of the terminal device, different voucher-related information that is specific to different transportation systems.

13. The computer-implemented system of claim 11 , wherein the encrypted data packets are decryptable by the fare collection device based on a decryption algorithm corresponding to the encryption algorithm.

14. The computer-implemented system of claim 11 , wherein the operations further comprise:

receiving, at the terminal device and by using the NFC connection, a verification result of the payment-related information that is sent by the fare collection device; and

displaying the verification result on the terminal device.

15. The computer-implemented system of claim 11 , wherein transforming the payment-related information into the multiple data packets comprises:

receiving, by using the NFC connection, a data offset sent by the fare collection device; and

splitting the payment-related information into data packets based on the data offset.

Assignments (3)

Priority Claims (1)

Continuity (2)

References Cited (38)