# US 2019/0297027 A1 · Sharing account data between different interfaces to a service

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

- Number: US 2019/0297027 A1
- Document ID: US20190297027A1
- Status: Published application
- Kind: A1
- Application number: 16/430,295
- Filed: 2019-06-03
- Published: 2019-09-26
- Earliest claimed: 2014-05-28
- Assignees: Apple Inc.
- Applicants: Apple Inc.
- Inventors: Andrew R. WHALLEY; Bob BRADLEY; Kenneth C. MCLEOD
- Web page: https://patentgrep.com/patent/US20190297027A1

## CPC

- H04L 47/803: {Application aware}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/53: using third party service providers
- H04W 4/00: Services specially adapted for wireless communication networks; Facilities therefor
- H04W 12/08: Access security
- H04W 12/086: using security domains
- H04W 12/12: Detection or prevention of fraud
- 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

Some embodiments provide a method for an electronic device. The method stores user data associated with a web-based third party service based on user interaction with a web domain for the third party service through a web browser. The method receives a request from a service-specific application to utilize the user data stored for the third party service. The method provides the user data to the application only when the application is verified by the web domain for receiving user data associated with the third party service.

## Claims

### Claim at position 1

1-12. (canceled)

### Claim 13

A machine readable medium storing a program for execution by at least one processing unit of an electronic device, the program comprising sets of instructions for:
from a first interface to a third-party web service, receiving a request to utilize user data stored on the electronic device relating to user interaction with the third-party web service through a second interface to the third-party web service;
determining whether the first and second interfaces to the third-party web service are verified to share the user data relating to the third-party web service; and
only when the first and second interfaces are verified to share the user data, allowing the first interface to access and utilize the stored user data.

### Claim 14 (depends on 13)

The machine readable medium of claim 13, wherein the program is a daemon that operates in a background of the electronic device as part of an operating system of the electronic device.

### Claim 15 (depends on 13)

The machine readable medium of claim 13, wherein the set of instructions for determining whether the first and second interfaces are verified to share the user data comprises a set of instructions for querying a database for a 3-tuple of the first interface, the second interface, and a type of data requested.

### Claim 16 (depends on 13)

The machine readable medium of claim 13, wherein the request is received through an API exposed to the first interface.

### Claim 17 (depends on 13)

The machine readable medium of claim 13, wherein the first interface is an application specific to the third-party web service and the second interface is a web page of the third-party web service accessed through a web browser.

### Claim 18 (depends on 13)

The machine readable medium of claim 13, wherein the first and second interfaces are first and second web pages of the third-party web service accessed through a web browser, wherein the first and second web pages are accessed at different web domains.

### Claim 19

For a mobile device, a method comprising:
from a particular application installed on the mobile device, retrieving a list of web domains stored with the particular application;
for a particular web domain in the list of web domains, retrieving a list of applications allowed access to user interaction data for the particular web domain;
when the particular application is on the list of applications retrieved from the particular web domain, storing a verified relationship between the particular application and the particular web domain.

### Claim 20 (depends on 19)

The method of claim 19, wherein each web domain in the list of web domains is paired with a type of user interaction data and each application in the list of applications is paired with a type of user interaction data.

### Claim 21 (depends on 20)

The method of claim 20, wherein the verified relationship is only stored between the particular application and the particular web domain when a particular type of user interaction data is paired with both the particular application and the particular web domain.

### Claim 22 (depends on 21)

The method of claim 21, wherein the verified relationship is stored as a record in a database that indicates the particular application, particular web domain, and the particular type of user interaction data.

### Claim 23 (depends on 20)

The method of claim 20, wherein at least one web domain is listed more than once in the list of web domains and paired with several types of user interaction data.

### Claim 24 (depends on 19)

The method of claim 19 further comprising:
receiving a request from the particular application to utilize user interaction data stored on the mobile device based on interaction with the particular web domain;
based on the stored verified relationship, granting the particular application access to the requested user interaction data.

### Claim 25

A device comprising:
a memory; and
at least one processor configured to:
from a first interface to a third-party web service, receive a request to utilize user data stored on the device relating to user interaction with the third-party web service through a second interface to the third-party web service;
determine whether the first and second interfaces to the third-party web service are verified to share the user data relating to the third-party web service; and
allow the first interface to access and utilize the user data stored on the device exclusively when the first and second interfaces are verified to share the user data.

### Claim 26 (depends on 25)

The device of claim 25, wherein the at least one processor is configured to determine whether the first and second interfaces are verified to share the user data by querying a database for a 3-tuple of the first interface, the second interface, and a type of data requested.

### Claim 27 (depends on 25)

The device of claim 25, wherein the request is received through an API exposed to the first interface.

### Claim 28 (depends on 25)

The device of claim 25, wherein the first interface comprises an application specific to the third-party web service and the second interface comprises a web page of the third-party web service accessed through a web browser.

### Claim 29 (depends on 25)

The device of claim 25, wherein the first and second interfaces comprise first and second web pages of the third-party web service accessed through a web browser, wherein the first and second web pages are accessed at different web domains.

### Claim 30 (depends on 25)

The device of claim 25, wherein the at least one processor is further configured to allow the first interface to locally access, on the device, the user data stored on the device exclusively when the first and second interfaces are verified to share the user data.

### Claim 31 (depends on 30)

The device of claim 30, wherein the user data stored on the device comprise a login credential for the third-party web service.

### Claim 32 (depends on 13)

The machine readable medium of claim 13, wherein the user data stored on the electronic device comprise a login credential for the third-party web service.
