# US 2017/0374056 A1 · Single Sign-On Processing For Associated Mobile Applications

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

- Number: US 2017/0374056 A1
- Document ID: US20170374056A1
- Status: Published application
- Kind: A1
- Application number: 15/698,704
- Filed: 2017-09-08
- Published: 2017-12-28
- Earliest claimed: 2013-03-07
- Assignees: Fiserv, Inc.
- Applicants: Fiserv, Inc.
- Inventors: David Francis Scavo; Barbara Wilson Whiteside
- Web page: https://patentgrep.com/patent/US20170374056A1

## CPC

- H04L 63/0815: {providing single-sign-on or federations}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70)
- H04W 12/06: Authentication
- 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, methods and computer-readable media are disclosed for performing single sign-on processing between associated mobile applications. The single sign-on processing may include processing to generate an interaction session between a user and a back-end server associated with a mobile application based at least in part on one or more existing interaction sessions between the user and one or more back-end servers associated with one or more other mobile applications. In order to establish an interaction session with an associated back-end server, a mobile application may leverage existing interaction sessions that have already been established in connection with the launching of other associated mobile applications.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

A method for leveraging an initial server interaction session on behalf of a first mobile app for a continued server interaction session on behalf of a second mobile app, the method comprising:
receiving, by a first mobile app executing on a mobile device and on behalf of a user of the mobile device, a first indication to launch the first mobile app;
receiving, by the first mobile app on behalf of the user, first authentication credentials for authenticating the user with a back-end server associated with the first mobile app;
generating, by the first mobile app, a sign-in request comprising i) information identifying the back-end server and ii) the first authentication credentials;
transmitting, by the first mobile app, the sign-in request to an application linking server;
receiving, by the first mobile app, a sign-in response comprising a session identifier indicative of an initial interaction session established with the back-end server on behalf of the user;
storing, by the first mobile app in at least one of i) memory or ii) data storage of the mobile device, the session identifier;
subsequent to storing the session identifier, receiving a second indication to launch a second mobile app;
determining, by the second mobile app executing on the mobile device based at least in part on the session identifier, that the initial interaction session with the back-end server exists and is active; and
initiating, by the second mobile app on behalf of the user, a continued interaction session with the back-end server leveraging the initial interaction session without obtaining, by the second mobile app from the user, second authentication credentials for authenticating the user with the back-end server.

### Claim 22 (depends on 21)

The method of claim 21, wherein the sign-in response further comprises application association information comprising information identifying a set of associated mobile apps, including the first mobile app and the second mobile app, the sign-in response originating from the application linking server.

### Claim 23 (depends on 22)

The method of claim 22 further comprising generating, by the first mobile app, a presentation of the set of associated mobile apps for display via an interface.

### Claim 24 (depends on 23)

The method of claim 23 further comprising determining that the second mobile app was not launched by one of the set of associated mobile apps.

### Claim 25 (depends on 21)

The method of claim 21, wherein the session identifier is associated with a time to live (TTL) value indicative of a duration that the initial interaction session will remain active.

### Claim 26 (depends on 21)

The method of claim 21, wherein i) the sign-in response further comprises an application linking server session identifier, and ii) the application linking server session identifier further comprises a time to live (TTL) value indicative of a duration that an application linking server session will remain active.

### Claim 27 (depends on 21)

The method of claim 21, wherein the second mobile app is launched from a mobile device interface that is independent of a first mobile app interface.

### Claim 28 (depends on 21)

The method of claim 21, wherein i) the back-end server is a first back-end server, ii) the second mobile app is associated with a second back-end server, iii) the sign-in request is a first sign-in request, iv) the sign-in response is a first sign-in response, v) the session identifier is a first session identifier, vi) the interaction session is a first interaction session, and vii) the method further comprises
receiving, by the second mobile app on behalf of the user, third authentication credentials for authenticating the user with the second back-end server;
generating, by the second mobile app, a second sign-in request comprising i) information identifying the second back-end server and ii) the second authentication credentials;
transmitting, by the second mobile app, the second sign-in request to the application linking server;
receiving, by the second mobile app, a second sign-in response comprising a second session identifier indicative of a second interaction session established with the second back-end server on behalf of the user; and
storing, by the first mobile app in at least one of i) memory or ii) data storage of the mobile device, the second session identifier.

### Claim 29

A mobile device for leveraging an initial server interaction session on behalf of a first mobile app for a continued server interaction session on behalf of a second mobile app, the mobile device comprising at least one processor and at least one memory including program code, the at least one memory and the program code configured to, with the processor, cause the mobile device to at least:
receive, by a first mobile app executing on the mobile device and on behalf of a user of the mobile device, a first indication to launch the first mobile app;
receive, by the first mobile app on behalf of the user, first authentication credentials for authenticating the user with a back-end server associated with the first mobile app;
generate, by the first mobile app, a sign-in request comprising i) information identifying the back-end server and ii) the first authentication credentials;
transmit, by the first mobile app, the sign-in request to an application linking server;
receive, by the first mobile app, a sign-in response comprising a session identifier indicative of an initial interaction session established with the back-end server on behalf of the user;
store, by the first mobile app in at least one of i) memory or ii) data storage of the mobile device, the session identifier;
subsequent to storing the session identifier, receive a second indication to launch a second mobile app;
determine, by the second mobile app executing on the mobile device based at least in part on the session identifier, that the initial interaction session with the back-end server exists and is active; and
initiate, by the second mobile app on behalf of the user, a continued interaction session with the back-end server leveraging the initial interaction session without obtaining, by the second mobile app from the user, second authentication credentials for authenticating the user with the back-end server.

### Claim 30 (depends on 29)

The mobile device of claim 29, wherein the sign-in response further comprises application association information comprising information identifying a set of associated mobile apps, including the first mobile app and the second mobile app, the sign-in response originating from the application linking server.

### Claim 31 (depends on 30)

The mobile device of claim 30, wherein the memory and program code are further configured to, with the processor, cause the mobile device to generate, by the first mobile app, a presentation of the set of associated mobile apps for display via an interface.

### Claim 32 (depends on 31)

The mobile device of claim 31, wherein the memory and program code are further configured to, with the processor, cause the mobile device to determine that the second mobile app was not launched by one of the set of associated mobile apps.

### Claim 33 (depends on 29)

The mobile device of claim 29, wherein the session identifier is associated with a time to live (TTL) value indicative of a duration that the initial interaction session will remain active.

### Claim 34 (depends on 29)

The mobile device of claim 29, wherein i) the sign-in response further comprises an application linking server session identifier, and ii) the application linking server session identifier further comprises a time to live (TTL) value indicative of a duration that an application linking server session will remain active.

### Claim 35 (depends on 29)

The mobile device of claim 29, wherein the second mobile app is launched from a mobile device interface that is independent of a first mobile app interface.

### Claim 36 (depends on 29)

The mobile device of claim 29, wherein i) the back-end server is a first back-end server, ii) the second mobile app is associated with a second back-end server, iii) the sign-in request is a first sign-in request, iv) the sign-in response is a first sign-in response, v) the session identifier is a first session identifier, vi) the interaction session is a first interaction session, and vii) the memory and program code are further configured to, with the processor, cause the mobile device to:
receive, by the second mobile app on behalf of the user, third authentication credentials for authenticating the user with the second back-end server;
generate, by the second mobile app, a second sign-in request comprising i) information identifying the second back-end server and ii) the second authentication credentials;
transmit, by the second mobile app, the second sign-in request to the application linking server;
receive, by the second mobile app, a second sign-in response comprising a second session identifier indicative of a second interaction session established with the second back-end server on behalf of the user; and
store, by the first mobile app in at least one of i) memory or ii) data storage of the mobile device, the second session identifier.

### Claim 37

A computer program product for leveraging an initial server interaction session on behalf of a first mobile app for a continued server interaction session on behalf of a second mobile app, the computer program product comprising at least one non-transitory computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising:
an executable portion configured to receive, by a first mobile app executing on a mobile device and on behalf of a user of the mobile device, a first indication to launch the first mobile app;
an executable portion configured to receive, by the first mobile app on behalf of the user, first authentication credentials for authenticating the user with a back-end server associated with the first mobile app;
an executable portion configured to generate, by the first mobile app, a sign-in request comprising i) information identifying the back-end server and ii) the first authentication credentials;
an executable portion configured to transmit, by the first mobile app, the sign-in request to an application linking server;
an executable portion configured to receive, by the first mobile app, a sign-in response comprising a session identifier indicative of an initial interaction session established with the back-end server on behalf of the user;
an executable portion configured to store, by the first mobile app in at least one of i) memory or ii) data storage of the mobile device, the session identifier;
an executable portion configured to, subsequent to storing the session identifier, receive a second indication to launch a second mobile app;
an executable portion configured to determine, by the second mobile app executing on the mobile device based at least in part on the session identifier, that the initial interaction session with the back-end server exists and is active; and
an executable portion configured to initiate, by the second mobile app on behalf of the user, a continued interaction session with the back-end server leveraging the initial interaction session without obtaining, by the second mobile app from the user, second authentication credentials for authenticating the user with the back-end server.

### Claim 38 (depends on 37)

The computer program product of claim 37, wherein the sign-in response further comprises application association information comprising information identifying a set of associated mobile apps, including the first mobile app and the second mobile app, the sign-in response originating from the application linking server.

### Claim 39 (depends on 38)

The computer program product of claim 38, wherein the computer-readable program code portions further comprise an executable instruction configured to generate, by the first mobile app, a presentation of the set of associated mobile apps for display via an interface.

### Claim 40 (depends on 39)

The computer program product of claim 39, wherein the computer-readable program code portions further comprise an executable instruction configured to determine that the second mobile app was not launched by one of the set of associated mobile apps.

### Claim 41 (depends on 37)

The computer program product of claim 37, wherein the session identifier is associated with a time to live (TTL) value indicative of a duration that the initial interaction session will remain active.

### Claim 42 (depends on 37)

The computer program product of claim 37, wherein i) the sign-in response further comprises an application linking server session identifier, and ii) the application linking server session identifier further comprises a time to live (TTL) value indicative of a duration that an application linking server session will remain active.

### Claim 43 (depends on 37)

The computer program product of claim 37, wherein the second mobile app is launched from a mobile device interface that is independent of a first mobile app interface.

### Claim 44 (depends on 37)

The computer program product of claim 37, wherein i) the back-end server is a first back-end server, ii) the second mobile app is associated with a second back-end server, iii) the sign-in request is a first sign-in request, iv) the sign-in response is a first sign-in response, v) the session identifier is a first session identifier, vi) the interaction session is a first interaction session, and vii) wherein the computer-readable program code portions further comprise:
an executable instruction configured to receive, by the second mobile app on behalf of the user, third authentication credentials for authenticating the user with the second back-end server;
an executable instruction configured to generate, by the second mobile app, a second sign-in request comprising i) information identifying the second back-end server and ii) the second authentication credentials;
an executable instruction configured to transmit, by the second mobile app, the second sign-in request to the application linking server;
an executable instruction configured to receive, by the second mobile app, a second sign-in response comprising a second session identifier indicative of a second interaction session established with the second back-end server on behalf of the user; and
an executable instruction configured to store, by the first mobile app in at least one of i) memory or ii) data storage of the mobile device, the second session identifier.
