# US 2023/0058201 A1 · Data processing method, apparatus, device and computer-readable storage medium

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0058201 A1
- Document ID: US20230058201A1
- Status: Published application
- Kind: A1
- Application number: 17/910,676
- Filed: 2021-01-20
- Published: 2023-02-23
- Earliest claimed: 2020-07-24
- Assignees: China Unionpay Co., Ltd.
- Applicants: China Unionpay Co., Ltd.
- Inventors: Chengchu ZHAN; Haijian JIANG; Zhenzhong ZOU; Jinren LIN; Gang LIU; Hua CAI
- Web page: https://patentgrep.com/patent/US20230058201A1

## CPC

- G06Q 20/354: {Card activation or deactivation}
- G06Q 20/38215: {Use of certificates or encrypted proofs of transaction rights}
- G06Q 20/3278: {RFID or NFC payments by means of M-devices}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

The application discloses a data processing method, apparatus, device and medium. The data processing method includes: receiving target activation data and a target activation instruction sent by a target server, wherein the target activation data includes a payment token to be activated corresponding to a payment card account number which needs to be activated; updating, in response to the target activation instruction, a target payment token in target personalized data to be the payment token to be activated, wherein a transaction card type indicated by the target personalized data is same as a transaction card type indicated by the target activation instruction; and setting the updated target payment token to be in an activated state.

## Claims

### Claim 1

A data processing method, comprising:
receiving target activation data and a target activation instruction sent by a target server, wherein the target activation data comprises a payment token to be activated corresponding to a payment card account number which needs to be activated;
updating, in response to the target activation instruction, a target payment token in target personalized data to be the payment token to be activated, wherein a transaction card type indicated by the target personalized data is same as a transaction card type indicated by the target activation instruction; and
setting the updated target payment token to be in an activated state.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the target personalized data comprises:
at least one type of data selected from the group consisting of
personalized data which is stored in a target security element and for which a payment token is in an activated state, and
personalized data which is stored in a target security element and for which a payment token is in an inactivated state.

### Claim 3

(canceled)

### Claim 4 (depends on 2)

The method according to claim 2, wherein in a case where the target personalized data comprises the personalized data which is stored in a target security element and for which a payment token is in an inactivated state, the target activation data further comprises the target personalized data;
wherein before the updating the target payment token in the target personalized data to be the payment token to be activated, the method further comprises:
storing the target personalized data in the target security element;
and after the setting the updated target payment token to be in the activated state, the method further comprises:
setting an activated payment token other than the updated target payment token to be in an inactivated stat.

### Claim 5

(canceled)

### Claim 6 (depends on 2)

The method according to claim 2, wherein the payment card account number which needs to be activated comprises a default payment card account number which needs to be set;
wherein before the receiving the target activation data and the target activation instruction sent by the target server, the method further comprises:
receiving the default payment card account number which needs to be set;
generating a default card setting request according to the default payment card account number which needs to be set; and
sending the default card setting request to the target server, wherein the default card setting request is configured to request the target server to feed back the target activation data and the target activation instruction corresponding to the default payment card account number which needs to be set.

### Claim 7 (depends on 2)

The method according to claim 2, wherein the payment card account number which needs to be activated comprises a default payment card account number which needs to be changed;
wherein before the receiving the target activation data and the target activation instruction sent by the target server, the method further comprises:
receiving the default payment card account number which needs to be changed;
generating a default card changing request according to the default payment card account number which needs to be changed; and
sending the default card changing request to the target server, wherein the default card changing request is configured to request the target server to feed back the target activation data and the target activation instruction corresponding to the default payment card account number which needs to be changed.

### Claim 8

A data processing method, comprising:
acquiring a target activation instruction and a payment token to be activated which is stored in association with a payment card account number which needs to be activated, wherein a transaction card type of the payment card account number which needs to be activated is same as a transaction card type indicated by the target activation instruction;
generating target activation data according to the payment token to be activated; and
sending the target activation data and the target activation instruction to a target electronic device, wherein the target activation instruction is configured to instruct the target electronic device to update a target payment token in target personalized data to be the payment token to be activated and set the updated target payment token to be in an activated state, wherein a transaction card type indicated by the target personalized data is same as the transaction card type indicated by the target activation instruction.

### Claim 9 (depends on 8)

The method according to claim 8, wherein before the generating the target activation data according to the payment token to be activated, the method further comprises:
acquiring the target personalized data; and
wherein the generating the target activation data according to the payment token to be activated comprises:
generating the target activation data according to the payment token to be activated and the target personalized data.

### Claim 10 (depends on 9)

The method according to claim 9, wherein before the acquiring the target personalized data, the method further comprises:
sending a data query request to the target electronic device, wherein the data query request is configured to query in a target security element of the target electronic device for the target personalized data; and
receiving a data query result fed back by the target electronic device; and
wherein the acquiring the target personalized data comprises:
acquiring the target personalized data in a case where the data query result indicates that the target personalized data has not been found in the target security element.

### Claim 11 (depends on 10)

The method according to claim 10, wherein the payment card account number which needs to be activated comprises a default payment card account number which needs to be set;
wherein before the acquiring the target activation instruction and the payment token to be activated which is stored in association with the payment card account number which needs to be activated, the method further comprises:
receiving a default card setting request sent by the target electronic device; and
parsing, in response to the default card setting request, the default card setting request to obtain information of the default card setting request, wherein the information of the default card setting request comprises the default payment card account number which needs to be set.

### Claim 12 (depends on 11)

The method according to claim 11, wherein after the sending the target activation data and the target activation instruction to the target electronic device, the method further comprises:
receiving an activation result sent by the target electronic device, wherein the activation result is configured to indicate that the target electronic device has set the payment token to be activated to be in an activated state;
setting, in response to the activation result, a payment card attribute corresponding to the payment card account number which needs to be activated as a target attribute, wherein the target attribute indicates a default payment card for the target electronic device; and
setting a token state corresponding to the payment token to be activated to be an activated state; and
establishing an association relationship between the payment token to be activated and the target electronic device.

### Claim 13 (depends on 10)

The method according to claim 10, wherein the payment card account number which needs to be activated comprises a default payment card account number which needs to be changed;
wherein before the acquiring the target activation instruction and the payment token to be activated which is stored in association with the payment card account number which needs to be activated, the method further comprises:
receiving a default card changing request sent by the target electronic device; and
parsing, in response to the default card changing request, the default card changing request to obtain information of the default card changing request, wherein the information of the default card changing request comprises the default payment card account number which needs to be changed.

### Claim 14 (depends on 13)

The method according to claim 13, wherein before the sending the data query request to the target electronic device, the method further comprises:
acquiring a target payment card account number, wherein a payment card attribute corresponding to the target payment card account number is a target attribute, and the target attribute indicates a default payment card for the target electronic device; and
wherein the sending the data query request to the target electronic device comprises:
sending the data query request to the target electronic device in a case where a payment card type of the target payment card account number is different from a payment card type of the default payment card account number which needs to be changed.

### Claim 15 (depends on 14)

The method according to claim 14, wherein after the sending the target activation data and the target activation instruction to the target electronic device, the method further comprises:
receiving an activation result sent by the target electronic device, wherein the activation result is configured to indicate that the target electronic device has set the payment token to be activated to be in an activated state;
setting, in response to the activation result, a payment card attribute corresponding to the payment card account number which needs to be activated as the target attribute and a payment card attribute corresponding to the target payment card account number as a non-target attribute; and
setting a token state corresponding to the payment token to be activated to an activated state, and setting a token state corresponding to the target payment token which is stored in association with the target payment card account number to an inactivated state; and
establishing an association relationship between the payment token to be activated and the target electronic device, and deleting an association relationship between the target payment token and the target electronic device.

### Claim 16 (depends on 8)

The method according to claim 8, wherein before the acquiring the target activation instruction and the payment token to be activated which is stored in association with the payment card account number which needs to be activated, the method further comprises:
receiving a payment card binding request sent by the target electronic device;
parsing, in response to the payment card binding request, the payment card binding request to obtain information of the payment card binding request, wherein the information of the payment card binding request comprises a payment card account number which needs to be bound;
generating a token generation request according to the payment card account number which needs to be bound;
sending the token generation request to a payment token management server, wherein the token generation request is configured to request the payment token management server to generate a payment token corresponding to the payment card account number which needs to be bound;
receiving the payment token corresponding to the payment card account number which needs to be bound fed back by the payment token management server; and
storing the payment card account number which needs to be bound and the payment token corresponding to the payment card account number which needs to be bound in association with each other.

### Claim 17 (depends on 8)

The method according to claim 8, wherein the method further comprises:
receiving a state changing request;
parsing, in response to the state changing request, the state changing request to obtain information of the state changing request, wherein the information of the state changing request comprises a payment card account number whose state needs to be changed and a target payment state of the target electronic device;
acquiring a payment token whose state is to be changed and which is stored in association with the payment card account number whose state needs to be changed; and
updating a token state corresponding to the payment token whose state is to be changed to be the target payment state.

### Claim at position 18

-19. (canceled)

### Claim 20 (depends on 8)

The method according to claim 8, wherein the method further comprises:
receiving a transaction request sent by an target acquiring device;
parsing, in response to the transaction request, the transaction request to obtain information of the transaction request, wherein the information of the transaction request comprises the target payment token;
querying for a token state corresponding to the target payment token;
refusing to execute a transaction corresponding to the transaction request in a case where the token state corresponding to the target payment token is an abnormal state; and
wherein the abnormal state comprises any one of a loss-reported state and an unbound state.

### Claim at position 20

-23. (canceled)

### Claim 24 (depends on 1)

A data processing device comprising: a processor and a memory storing computer program instructions;
wherein the processor is configured to execute the computer program instructions to implement the data processing method according to claim 1.

### Claim 25 (depends on 1)

A computer-readable storage medium storing computer program instructions, wherein the computer program instructions are executed by a processor to implement the data processing method according to claim 1.

### Claim 26 (depends on 9)

A data processing device comprising: a processor and a memory storing computer program instructions;
wherein the processor is configured to execute the computer program instructions to implement the data processing method according to claim 9.

### Claim 27 (depends on 9)

A computer-readable storage medium storing computer program instructions, wherein the computer program instructions are executed by a processor to implement the data processing method according to claim 9.
