Patent Application Titled “Establishing A Shared Session Between Entities” Published Online (USPTO 20220012711): Patent Application

2022 JAN 31 (NewsRx) -- By a News Reporter-Staff News Editor at Insurance Daily News -- According to news reporting originating from Washington, D.C., by NewsRx journalists, a patent application by the inventors BESTER, Daniel Deetlefs (Stellenbosch, ZA); LE ROUX, Mercia (Stellenbosch, ZA); OOSTHUIZEN, Gerhard Gysbert (Stellenbosch, ZA); VAN DER MERWE, Jonathan Daniel (Stellenbosch, ZA); WESSELS, Tertius (Stellenbosch, ZA), filed on November 19, 2019, was made available online on January 13, 2022.

No assignee for this patent application has been made.

Reporters obtained the following quote from the background information supplied by the inventors: “Consumers are increasingly able to conduct transactions with merchants using their personal devices, such as mobile phones or wearable devices. Such transactions may make use of contactless communication interfaces, such as near field communication (NFC) or radio-frequency identification (RFID) interfaces or by either the consumer device or a merchant device capturing a graphical code.

“For example, US20130054413A1 discloses a contactless payment system for merchant transactions (e.g., a restaurant) which comprises generating, at the contactless payment system, a total bill of purchases associated with a consumer, associating a unique identifier of a RFID tag or a quick response (QR) code with the total bill, transmitting the total bill and associated unique identifier to a consumer accessible payment network, and receiving payment from the consumer for satisfaction of the total bill. The consumer submits the payment using a contactless-enabled device, such as a smartphone. The contactless-enabled device may interrogate the RFID tag or read the QR code to receive the unique identifier and a payment network link. Furthermore, the contactless-enabled device submits a payment transaction request to the payment network, where the payment transaction request includes the unique identifier and an account identifier. The payment network receives the payment transaction request and locates the total bill using the unique identifier as a key.

“However existing technological platforms may still require substantial interaction on the part of the consumer in order to initiate and/or complete payment in respect of the transaction. This consumer friction may be due to technical short comings associated with existing platforms and there is accordingly scope for improvement.

“The preceding discussion of the background to the invention is intended only to facilitate an understanding of the present invention. It should be appreciated that the discussion is not an acknowledgment or admission that any of the material referred to was part of the common general knowledge in the art as at the priority date of the application.”

In addition to obtaining background information on this patent application, NewsRx editors also obtained the inventors’ summary information for this patent application: “In accordance with an aspect of the invention there is provided a computer-implemented method comprising: receiving a first shared session request message being associated with a tag identifier and a first device associated with a first entity; associating the first device with a shared session associated with the tag identifier; receiving a second shared session request message being associated with the tag identifier and a second device associated with a second entity; and associating the second device with the shared session, wherein one or both of the first device and the second device having obtained the tag identifier from a tag provided by the first entity or the second entity, and wherein the shared session is configured for requesting and providing transaction-related data by and to at least one of the devices associated with the shared session.

“Further features provide for associating the first device or the second device with the shared session to include initiating a shared session in association with the tag identifier and the first device or the second device; for the method to include validating the tag identifier received from the first device or the second device; and for validating the tag identifier to include checking a list or data structure for a matching tag identifier.

“Yet further features provide for the tag identifier to be a cryptographic code configured for validation using a cryptographic process, and for validating the tag identifier to include using the cryptographic process to validate the tag identifier.

“Still further features provide for the method to include receiving a first transaction request message, including the tag identifier, from one of the first device or the second device and transmitting a second transaction request message, including the tag identifier, to the other of the second device or the first device, for the second transaction request message to be based on the first transaction request message.

“Even further features provide for the method to be conducted at a first device gateway in communication with a second device gateway via a communication network, for the first shared session request message to be a request to initiate the shared session, and for the method to include generating the tag identifier and transmitting the tag identifier to the first device.

“Further features provide for the method to include assigning a first access code to the first device, and for the tag identifier and first access code to be transmitted to the first device in a shared session response message.

“Yet further features provide for receiving the second shared session request message associated with the tag identifier to include receiving the second shared session request message from the second device via the second device gateway, for the second shared session request message to include the tag identifier and a second access code; and for the method to include storing the second access code in association with the tag identifier.

“Still further features provide for the second device to have obtained the tag identifier from the tag provided by the first entity.

“Even further features provide for the method to include transmitting a transaction request message to the second device gateway, the transaction request message including the tag identifier, the second access code and one or both of transaction request detail and transaction information detail; and for the transaction request message transmitted to the second device gateway to be based on a transaction request message received from the first device.

“Still further features provide for the method to include receiving a transaction response message from the second device gateway, for the transaction response message to include one or both of information requested by way of the information request detail and a confirmation of actions initiated in respect of the transaction request detail.

“Further features provide for the first entity to be a merchant and for the second entity to be a consumer.

“Further features provide for the second shared session message to include a pre-authorisation confirmation including a pre-authorised limit; for the first shared session message to include a payment request including an amount in respect of the transaction, and for the method to include automatically initiating processing of the payment in respect of the amount without second entity intervention if the amount is within the pre-authorised limit; for the method to include prompting the second entity via the second device for authorisation to process the payment in respect of the amount if the amount exceeds the pre-authorised limit; and for prompting the second entity for authorisation to process the payment in respect of the amount to include transmitting an authorisation request message to the second device, the authorisation request message including the amount and being configured to prompt the second entity for authorisation to process the payment in respect of the amount.

“Still further features provide for the pre-authorisation confirmation to be received in response to a second device gateway associated with the second device validating that the second entity is pre-authorised to conduct the transaction; for the pre-authorisation confirmation to be received from the second device gateway; and for the pre-authorisation confirmation to be received in response to the second device transmitting a shared session request message to the second device gateway, the shared session request message including the tag identifier and a device identifier which uniquely identifies the second device to the second device gateway.

“Yet further features provide for receiving the pre-authorisation confirmation to precede initiation of the transaction between the second entity and the first entity; for receiving the pre-authorisation confirmation to precede any payment obligation by the second entity in favour of the first entity; and for the pre-authorisation confirmation to be devoid of any personal information associated with the second entity.

“Further features provide for receiving the payment request to succeed initiation of the transaction between the second entity and the first entity; and for receiving the payment request to establish a payment obligation by the second entity in favour of the first entity.

“Still further features provide for initiating processing of the payment in respect of the amount to include forwarding the payment request to the second device gateway instructing payment of the amount against a financial account associated with the second entity in favour of a financial account associated with the first entity; for processing the payment in respect of the amount to include accessing details of a financial account associated with the first entity and transmitting a payment instruction message to a second device gateway associated with the second device, the payment instruction message including the amount and details of the financial account associated with the first entity.

“Other information may be requested and provided over the shared session, for example loyalty information, personal information and the like.

“In accordance with a further aspect of the invention there is provided a system comprising: a processor and a memory configured to provide computer program instructions to the processor to execute functions of components; a shared session message component for receiving a first shared session request message being associated with a tag identifier and a first device associated with a first entity; an associating component for associating the first device with a shared session associated with the tag identifier; the shared session message component further being for receiving a second shared session request message being associated with the tag identifier and a second device associated with a second entity; and the associating component further being for associating the second device with the shared session, wherein one or both of the first device and the second device having obtained the tag identifier from a tag provided by the first entity or the second entity, and wherein the shared session is configured for requesting and providing transaction-related data by and to at least one of the devices associated with the shared session.

“In accordance with a further aspect of the invention there is provided a computer program product comprising a computer-readable medium having stored computer-readable program code for performing the steps of: receiving a first shared session request message being associated with a tag identifier and a first device associated with a first entity; associating the first device with a shared session associated with the tag identifier; receiving a second shared session request message being associated with the tag identifier and a second device associated with a second entity; and associating the second device with the shared session, wherein one or both of the first device and the second device having obtained the tag identifier from a tag provided by the first entity or the second entity, and wherein the shared session is configured for requesting and providing transaction-related data by and to at least one of the devices associated with the shared session.

“Further features provide for the computer-readable medium to be a non-transitory computer-readable medium and for the computer-readable program code to be executable by a processing circuit.”

There is additional summary information. Please visit full patent to read further.”

The claims supplied by the inventors are:

“1. A computer-implemented method conducted at a first device gateway comprising: receiving a first shared session request message being associated with a tag identifier and a first device associated with a first entity; associating the first device with a shared session associated with the tag identifier; receiving, from a second device associated with a second entity, via a second device gateway, a second shared session request message, the second shared session request message including the tag identifier; and associating the second device with the shared session, wherein one or both of the first device and the second device having obtained the tag identifier from a tag provided by the first entity or the second entity, and wherein the shared session is configured for requesting and providing transaction-related data.

“2. The method as claimed in claim 1, wherein associating the first device or the second device with the shared session includes initiating a shared session in association with the tag identifier and the first device or the second device.

“3. The method as claimed in claim 1, including validating the tag identifier received from the first device or the second device.

“4. The method as claimed in claim 3, wherein validating the tag identifier includes checking a list or data structure for a matching tag identifier.

“5. The method as claimed in claim 3, wherein the tag identifier is a cryptographic code configured for validation using a cryptographic process, and wherein validating the tag identifier includes using the cryptographic process to validate the tag identifier.

“6. The method as claimed in claim 1, including receiving a first transaction request message, including the tag identifier, from one of the first device or the second device and transmitting a second transaction request message, including the tag identifier, to the other of the second device or the first device, wherein the second transaction request message is based on the first transaction request message.

“7. The method as claimed in claim 1, wherein the first device gateway communicates with the second device gateway via a communication network, wherein the first shared session request message is a request to initiate the shared session, and wherein the method includes generating the tag identifier and transmitting the tag identifier to the first device.

“8. The method as claimed in claim 7, including assigning a first access code to the first device, and wherein the tag identifier and the first access code are transmitted to the first device in a shared session response message.

“9. The method as claimed in claim 7, wherein the second shared session request message includes a second access code.

“10. The method as claimed in claim 9, including storing the second access code in association with the tag identifier.

“11. The method as claimed in claim 7, the second device having obtained the tag identifier from the tag provided by the first entity.

“12. The method as claimed in claim 9, including transmitting, via the shared session, a transaction request message to the second device gateway, the transaction request message including the tag identifier, the second access code and one or both of transaction request detail and transaction information detail.

“13. The method as claimed in claim 12, wherein the transaction request message transmitted to the second device gateway is based on a transaction request message received from the first device.

“14. The method as claimed in claim 12, including receiving, via the shared session, a transaction response message from the second device gateway, the transaction response message including one or both of information requested by way of the transaction request detail and a confirmation of actions initiated in respect of the transaction request detail.

“15. The method as claimed in claim 1, wherein the first entity is a merchant and the second entity is a consumer.

“16. A system comprising a processor and a memory configured to provide computer program instructions to the processor to execute functions of components, the system including a first device gateway including: a shared session message component for receiving a first shared session request message being associated with a tag identifier and a first device associated with a first entity; an associating component for associating the first device with a shared session associated with the tag identifier; the shared session message component further being for receiving, from a second device associated with a second entity, via a second device gateway, a second shared session request message, the second shared session request message including the tag identifier; and the associating component further being for associating the second device with the shared session, wherein one or both of the first device and the second device having obtained the tag identifier from a tag provided by the first entity or the second entity, and wherein the shared session is configured for requesting and providing transaction-related data.

“17. A computer program product comprising a computer-readable medium having stored computer-readable program code for performing, at a first device gateway, the steps of: receiving a first shared session request message being associated with a tag identifier and a first device associated with a first entity; associating the first device with a shared session associated with the tag identifier; receiving, from a second device associated with a second entity, via a second device gateway, a second shared session request message, the second shared session request message including the tag identifier; and associating the second device with the shared session, wherein one or both of the first device and the second device having obtained the tag identifier from a tag provided by the first entity or the second entity, and wherein the shared session is configured for requesting and providing transaction-related data.

“18. The method as claimed in claim 1, wherein the second shared session request message includes data usable by the second device gateway for controlling requests for information from other entities.

“19. The method as claimed in claim 1, wherein the tag identifier includes information usable in identifying the first device gateway.

“20. The method as claimed in claim 1, wherein the shared session is initially independent of any transaction, wherein the shared session is a digital communication conduit via which entities can exchange data pursuant to entering into and completing a transaction.

“21. The method as claimed in claim 12, wherein the transaction request detail includes a list of information about or associated with the second entity that is requested by one or both of the first device and first device gateway, including one or more of the group of: personal information; a billing address; a shipping address; loyalty data; health insurance data; and, source of funds data.”

For more information, see this patent application: BESTER, Daniel Deetlefs; LE ROUX, Mercia; OOSTHUIZEN, Gerhard Gysbert; VAN DER MERWE, Jonathan Daniel; WESSELS, Tertius. Establishing A Shared Session Between Entities. Filed November 19, 2019 and posted January 13, 2022. Patent URL: https://appft.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PG01&p=1&u=%2Fnetahtml%2FPTO%2Fsrchnum.html&r=1&f=G&l=50&s1=%2220220012711%22.PGNR.&OS=DN/20220012711&RS=DN/20220012711

(Our reports deliver fact-based news of research and discoveries from around the world.)