# US 11,443,313 B2 · Methods and systems for authorizing a real-time transaction with a third party platform

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

- Number: US 11,443,313 B2
- Document ID: US11443313B2
- Status: Granted
- Kind: B2
- Application number: 16/025,684
- Filed: 2018-07-02
- Published: 2020-01-02
- Granted: 2022-09-13
- Earliest claimed: 2018-07-02
- Assignees: Honda Motor Co., Ltd.
- Applicants: Honda Motor Co., Ltd.
- Inventors: Narendran Ravi
- Web page: https://patentgrep.com/patent/US11443313B2

## CPC

- G06Q 20/4012: {Verifying personal identification numbers [PIN]}
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 20/0855: {involving a third party}
- G06Q 20/127: {Shopping or accessing services according to a time-limitation}
- G06Q 20/3829: {involving key management}
- G06Q 20/4014: {Identity check for transactions}
- H04L 63/0435: {wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for symmetric key encryption H04L9/06)}
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04W 12/06: Authentication
- 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
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Systems and methods for authorizing a real-time transaction with a third party platform (TPP). The system includes a memory that stores instructions for authorizing the real-time transaction with the TPP. The system also includes a processor configured to execute the instructions. The instructions cause the processor to: generate a tokenized personal identification number (PIN) based on a request to register with the TPP, the request including a customer PIN and an authorization token; transmit the tokenized PIN and the authorization token to the TPP, wherein the TPP stores the tokenized PIN and the authorization token; in response to receipt, at the TPP, of a request for the real-time transaction from a customer, receive the tokenized PIN from the TPP; decrypt the tokenized PIN to extract the customer PIN; and transmit instructions including the customer PIN to a service provider, the instructions comprising a command to provide access to a vehicle.

## Claims

### Claim 1

A system comprising:
a memory that stores instructions for authorizing a real-time transaction with a third party platform (TPP); and
a processor configured to execute the instructions, wherein the instructions cause the processor to:
receive, from an application, a request to register the TPP to provide services to a vehicle of a customer, wherein the request includes a customer personal identification number (PIN) and an authorization token;
generate a tokenized PIN from the customer PIN received in the request to register the TPP;
transmit the tokenized PIN and the authorization token to the TPP;
receive, from the TPP based on a request for a real-time transaction for the customer, an access request to access the vehicle, wherein the access request indicates the tokenized PIN;
extract the customer PIN from the tokenized PIN; and
transmit instructions including the customer PIN, as extracted from the tokenized PIN, to a telematics service provider that is different than the TPP and provides access to the vehicle, the instructions comprising a command to provide access to the vehicle based on the access request.

### Claim 2 (depends on 1)

The system of claim 1, wherein generating the tokenized PIN comprises encrypting the customer PIN and extracting the customer PIN comprises decrypting the tokenized PIN.

### Claim 3 (depends on 2)

The system of claim 2, wherein encrypting the customer PIN comprises concatenating the customer PIN with a key and a SALT.

### Claim 4 (depends on 2)

The system of claim 2, wherein the encrypting the customer PIN and decrypting the tokenized PIN are based on a symmetric-key process that utilizes a common key.

### Claim 5 (depends on 1)

The system of claim 1, wherein the instructions further cause the processor to validate the authorization token after receiving the tokenized PIN from the TPP.

### Claim 6 (depends on 1)

The system of claim 1, wherein generating the tokenized PIN is based on validating, with the telematics service provider, the customer PIN received in the request to register the TPP.

### Claim 7 (depends on 1)

The system of claim 1, wherein the instructions further cause the processor to delete the tokenized PIN and the customer PIN from the memory after transmitting the tokenized PIN and the authorization token to the TPP.

### Claim 8

A method for authorizing a real-time transaction with a third party platform (TPP) comprising:
receiving, from an application, a request to register the TPP to provide services to a vehicle of a customer, wherein the request includes a customer personal identification number (PIN) and an authorization token;
generating a tokenized PIN from the customer PIN received in the request to register the TPP;
transmitting the tokenized PIN and the authorization token to the TPP;
receiving, from the TPP based on a request for a real-time transaction for the customer, an access request to access the vehicle, wherein the access request indicates the tokenized PIN;
extracting the customer PIN from the tokenized PIN; and
transmitting instructions including the customer PIN, as extracted from the tokenized PIN, to a telematics service provider that is different than the TPP and provides access to the vehicle, the instructions comprising a command to provide access to the vehicle based on the access request.

### Claim 9 (depends on 8)

The method of claim 8, wherein generating the tokenized PIN comprises encrypting the customer PIN and extracting the customer PIN comprises decrypting the tokenized PIN.

### Claim 10 (depends on 9)

The method of claim 9, wherein encrypting the customer PIN comprises concatenating the customer PIN with a key and a SALT.

### Claim 11 (depends on 9)

The method of claim 9, wherein the encrypting the customer PIN and decrypting the tokenized PIN are based on a symmetric-key process that utilizes a common key.

### Claim 12 (depends on 8)

The method of claim 8, further comprising validating the authorization token after receiving the tokenized PIN from the TPP.

### Claim 13 (depends on 8)

The method of claim 8, wherein generating the tokenized PIN is based on validating, with the telematics service provider, the customer PIN received in the request to register the TPP.

### Claim 14 (depends on 8)

The method of claim 8, further comprising deleting the tokenized PIN and the customer PIN from a memory after transmitting the tokenized PIN and the authorization token to the TPP.

### Claim 15

A non-transitory computer-readable storage medium containing executable computer program code, the code comprising instructions configured to cause a processor to:
receive, from an application, a request to register the TPP to provide services to a vehicle of a customer, wherein the request includes a customer personal identification number (PIN) and an authorization token;
generate a tokenized PIN from the customer PIN received in the request to register the TPP;
transmit the tokenized PIN and the authorization token to the TPP;
receive, from the TPP based on a request for a real-time transaction for the customer, an access request to access the vehicle, wherein the access request indicates the tokenized PIN;
extract the customer PIN from the tokenized PIN; and
transmit instructions including the customer PIN, as extracted from the tokenized PIN, to a telematics service provider that is different than the TPP and provides access to the vehicle, the instructions comprising a command to provide access to the vehicle based on the access request.

### Claim 16 (depends on 15)

The medium of claim 15, wherein generating the tokenized PIN comprises encrypting the customer PIN and extracting the customer PIN comprises decrypting the tokenized PIN.

### Claim 17 (depends on 16)

The medium of claim 16, wherein the encrypting the customer PIN and decrypting the tokenized PIN are based on a symmetric-key process that utilizes the key when encrypting the customer PIN and decrypting the tokenized PIN.

### Claim 18 (depends on 15)

The medium of claim 15, wherein, the code further causes the processor to validate the authorization token after receiving the tokenized PIN from the TPP.

### Claim 19 (depends on 15)

The medium of claim 15, wherein generating the tokenized PIN is based on validating, with the telematics service provider, the customer PIN received in the request to register the TPP.

### Claim 20 (depends on 15)

The medium of claim 15, wherein the code further causes the processor to delete the tokenized PIN and the customer PIN from a memory after transmitting the tokenized PIN and the authorization token to the TPP.