Systems and methods for cryptographic authentication of contactless cards
US-2020106615-A1 · Apr 2, 2020 · US
US2023291749A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2023291749-A1 |
| Application number | US-202318199724-A |
| Country | US |
| Kind code | A1 |
| Filing date | May 19, 2023 |
| Priority date | Aug 11, 2020 |
| Publication date | Sep 14, 2023 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and methods for verified messaging through the interaction involving a short-range transceiver, such as a contactless card, a client device and a server are presented. Verified messaging may be provided in the context of using a client device to receive a user identifier from the user's short-range transceiver, such as a contactless card, and sending a messaging request with the user identifier to a server, which may look up client device information and compare with data about the client device accompanying the request. Matching received client device information to stored client device data based on a user identifier obtained from a short-range transceiver provides an enhanced ability to verify that the client device corresponds to the user associated with the short-range transceiver.
Opening claim text (preview).
1 - 30 . (canceled) 31 . A method for verified messaging, comprising: receiving, by a server, a message session request from a client device associated with a user, the message session request including a message payload; determining, by the server based on the message payload, a user identifier corresponding to a user, wherein the server is in data communication with a database storing user information for a plurality of users, the user information including, for each of the plurality of users, a user identifier and a client device address; identifying, by the server, a client device address for the user; determining, by the server, whether the client device address for the user corresponds to a source address accompanying the message session request; and sending, by the server, a response message to the client device, the response message addressed to the client device address. 32 . The method of claim 31 , wherein the response message is a short message service (SMS) message. 33 . The method of claim 32 , wherein the server is configured for data communication with an SMS gateway, and the response message is routed by the server to the SMS gateway. 34 . The method of claim 31 , wherein the message payload includes a token associated with the user. 35 . The method of claim 34 , further comprising authenticating, by the server, the user based on a user key obtained from the token. 36 . The method of claim 31 , further comprising: providing, by a card applet of a contactless card associated with the user after entry of the contactless card into a communication field of the client device, a uniform resource identifier (URI) into the short-range communication field of the client device, wherein the URI comprises a message destination address of the server and the message payload. 37 . The method of claim 36 , wherein the message payload includes a data item from the contactless card. 38 . The method of claim 37 , wherein the data item includes at least one selected from the group of a counter and a cryptogram generated using the counter. 39 . The method of claim 36 , wherein the message payload includes a token associated with the user. 40 . The method of claim 36 , wherein the message payload includes a request to engage in a verified message session. 41 . The method of claim 39 , wherein the message session request comprises a short message service (SMS) message. 42 . A system for verified messaging, comprising: a server in data communication with a client device associated with a user and a database storing user information for a plurality of users, the user information including, for each of the plurality of users, a user identifier and a client device address, wherein the server: receives a message session request from the client device, the message session request including a message payload, determines, based on the message payload, the user identifier, identifying a client device address for the user, determining whether the client device address for the user corresponds to a source address accompanying the message session request, and sending a response message to the client device, the response message addressed to the client device address. 43 . The system of claim 42 , wherein the client device address comprises a mobile phone number. 44 . The system of claim 41 , further comprising a contactless card associated with the user, wherein: the contactless card is configured for data communication via a short-range communication field of the client device, the contactless card comprises at least one card processor and at least one card memory, the at least one card memory stores data and a card applet, and after entry by the contactless card into the short-range communication field of the client device, the card applet provides a uniform resource identifier (URI). 45 . The system of claim 44 , wherein the URI comprises a message destination address of the server and a message payload. 46 . The system of claim 45 , wherein the message payload includes a user key and a cryptogram. 47 . The system of claim 46 , wherein: the card memory further includes a card number and a counter, and the cryptogram is generated using the user key, the card number, and the counter. 48 . A method for verified messaging, comprising: providing, by an applet of a contactless card for a user after entry of the contactless card into a communication field of a client device belonging to a user, the contactless card comprising at least one card processor and a card memory storing data and the card applet, a uniform resource identifier (URI) into the short-range communication field of the client device, the URI comprising a message destination address of a server and a message payload; receiving, by the server, a message session request from the client device, the message session request including the message payload; determining, by the server based on the message payload, a user identifier corresponding to the user; identifying, by the server, a client device address for the user; determining, by the server, whether the client device address for the user corresponds to a source address accompanying the message session request; and sending, by the server, a response message to the client device, the response message addressed to the client device address. 49 . The method of claim 48 , wherein the message payload includes a user key and a cryptogram. 50 . The method of claim 49 , wherein: the card memory further stores a card number, and the cryptogram is generated using the user key and the card number.
using an additional device, e.g. smartcard, SIM or a different communication terminal (cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234) · CPC title
the source of the received data · CPC title
Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD] · CPC title
Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication · CPC title
based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.