Systems and methods for verified communication between mobile applications

US12307460B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-12307460-B2
Application numberUS-202418755209-A
CountryUS
Kind codeB2
Filing dateJun 26, 2024
Priority dateMay 19, 2022
Publication dateMay 20, 2025
Grant dateMay 20, 2025

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Systems and methods for establishing trust between a conventional mobile application and a micro application are disclosed. In accordance with aspects, a method may include authenticating user credentials with a backend processing infrastructure of a provider of a mobile application, wherein the authenticating generates session information; receiving, at the mobile application, a uniform resource identifier (URI), wherein the URI includes the session information as a parameter of the URI; receiving, at the mobile application, a user-activation of the URI; receiving, at the backend processing infrastructure of the provider of the mobile application and from a backend processing infrastructure of a third party, the session information; verifying, by the backend processing infrastructure of the provider of the mobile application the session information; and sending, by the backend processing infrastructure of the provider of the mobile application and to the backend processing infrastructure of the third party, requested user information.

First claim

Opening claim text (preview).

The invention claimed is: 1. A method comprising: authenticating, by a mobile application provider computer program, a user of a mobile application executed by a user mobile electronic device based on authentication credentials received from the mobile application; setting, by the mobile application provider computer program, a cookie in a mobile browser cache on the user mobile electronic device, wherein the cookie comprises a user identifier for the user; presenting, by the mobile application, a selectable feature for a third-party offer comprising a uniform resource identifier (URI) for a third-party mobile application; launching, by the mobile application, the third-party mobile application by activating the URI in response to selection of the selectable feature, wherein the third-party mobile application is configured to launch a hidden iFrame that is embedded in the third-party mobile application; receiving, by the mobile application provider computer program, the user identifier from the hidden iFrame in the third-party mobile application; verifying, by the mobile application provider computer program, that the cookie is present in the mobile browser cache; communicating, by the mobile application provider computer program, verification of a presence of the cookie to the hidden iFrame in the third-party mobile application, wherein the hidden iFrame or the third-party mobile application is configured to communicate the user identifier to a third-party mobile application provider computer program; receiving, by the third-party mobile application, a request for user information and the user identifier from the third-party mobile application provider computer program; retrieving, by the third-party mobile application provider computer program, the user information associated with the user identifier; and returning, by the mobile application provider computer program, the user information to the third-party mobile application provider computer program. 2. The method of claim 1 , wherein the hidden iFrame is launched in a domain for the mobile application. 3. The method of claim 1 , wherein the hidden iFrame is sized to be transparent. 4. The method of claim 1 , wherein the hidden iFrame executes a script to communicate the user identifier to the third-party mobile application provider computer program. 5. The method of claim 4 , wherein the script first passes the user identifier to the third-party mobile application and then to the third-party mobile application provider computer program. 6. The method of claim 1 , wherein the URI further comprises a third-party identifier that identifies a third party associated with the third-party mobile application. 7. The method of claim 6 , wherein the mobile application sends the third-party identifier to a mobile device operating system. 8. The method of claim 7 , wherein the mobile device operating system downloads and launches a micro-application provided by the third party. 9. The method of claim 1 , wherein the cookie comprises a session cookie that has an expiration. 10. The method of claim 1 , wherein the user information comprises an address or payment information associated with the user identifier. 11. A system, comprising: a user mobile electronic device executing a mobile application; a mobile application provider backend executing a mobile application provider computer program; and a third-party mobile application provider backend executing a third-party mobile application provider computer program: wherein: the mobile application provider computer program is configured to authenticate a user of the mobile application based on authentication credentials received from the mobile application; the mobile application provider computer program is configured to set a cookie in a mobile browser cache on the user mobile electronic device, wherein the cookie comprises a user identifier for the user; the mobile application is configured to present a selectable feature for a third-party offer comprising a uniform resource identifier (URI) for a third-party mobile application; the mobile application is configured to launch the third-party mobile application by activating the URI in response to selection of the selectable feature; the third-party mobile application is configured to launch a hidden iFrame that is embedded in the third-party mobile application; the mobile application provider computer program is configured to receive the user identifier from the hidden iFrame in the third-party mobile application; the mobile application provider computer program is configured to verify that the cookie is present in the mobile browser cache; the mobile application provider computer program is configured to communicate verification of a presence of the cookie to the hidden iFrame in the third-party mobile application; the hidden iFrame or the third-party mobile application is configured to communicate the user identifier to the third-party mobile application provider computer program; the third-party mobile application is configured to receive a request for user information and the user identifier from the third-party mobile application provider computer program; the third-party mobile application provider computer program is configured to retrieve the user information associated with the user identifier; and the mobile application provider computer program is configured to return the user information to the third-party mobile application provider computer program. 12. The system of claim 11 , wherein the hidden iFrame is launched in a domain for the mobile application. 13. The system of claim 11 , wherein the hidden iFrame is sized to be transparent. 14. The system of claim 11 , wherein the hidden iFrame is configured to execute a script to communicate the user identifier to the third-party mobile application provider computer program. 15. The system of claim 14 , wherein the script first passes the user identifier to the third-party mobile application and then to the third-party mobile application provider computer program. 16. The system of claim 11 , wherein the URI further comprises a third-party identifier that identifies a third party associated with the third-party mobile application. 17. The system of claim 16 , wherein the mobile application is configured to send the third-party identifier to a mobile device operating system. 18. The system of claim 17 , wherein the mobile device operating system is configured to download and launch a micro-application provided by the third party. 19. The system of claim 11 , wherein the cookie comprises a session cookie that has an expiration. 20. The system of claim 11 , wherein the user information comprises an address or payment information associated with the user identifier.

Assignees

Inventors

Classifications

  • H04L67/53Primary

    using third party service providers · CPC title

  • Payment applications installed on the mobile devices · CPC title

  • using biometric data, e.g. fingerprints, iris scans or voiceprints · CPC title

  • Electronic credentials · CPC title

  • Biometric identity checks · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US12307460B2 cover?
Systems and methods for establishing trust between a conventional mobile application and a micro application are disclosed. In accordance with aspects, a method may include authenticating user credentials with a backend processing infrastructure of a provider of a mobile application, wherein the authenticating generates session information; receiving, at the mobile application, a uniform resour…
Who is the assignee on this patent?
Jpmorgan Chase Bank Na
What technology area does this patent fall under?
Primary CPC classification H04L67/53. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue May 20 2025 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 3 related publications on this page (citations in our corpus or others sharing the same primary CPC).