IP Library › Granted Patent US 12,407,784
Granted Patent B2
US 12,407,784 · App. 18/355,855 · Granted Sep 2, 2025

Techniques for implementing phone number-based user accounts with permissions to access varying levels of services utilizing visible and hidden contact addresses

Inventors: Xudong Liu (Campbell, CA); Guozhi Huang (San Mateo, CA); Jonathon Sodos (Los Gatos, CA)
Assignee: Apple Inc.
H04M15/7556H04M1/27457H04M3/42382H04M2203/6081
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,407,784
App. No.
18/355,855
Granted
Sep 2, 2025
Kind
B2
Abstract

This application sets forth techniques for managing phone number-based user accounts. According to some embodiments, a server computing device can be configured to carry out the steps of (1) receiving, from a first client computing device, a request to create a user account based on a phone number, (2) in response to authenticating that the first client computing device is associated with the phone number: creating the user account based on the phone number, creating a hidden contact address based on the phone number, and assigning the hidden contact address to the user account, and (3) in response to receiving a notification that a second client computing device is associated with the phone number: requiring the user account to be updated to be based on a different phone number, or assigning, to the user account, a visible contact address based on the phone number.

Claims (76)

1. A method for managing phone number-based user accounts, the method comprising, by a server computing device:

receiving a request to create a user account based on a phone number;

authenticating an ownership of the phone number;

creating hidden and visible contact addresses based on the phone number, wherein the hidden contact address permits access to a first subset of services that omits at least a second subset of services that are otherwise accessible using the visible contact address;

assigning the hidden contact address to the user account and a first client computing device to permit the first client computing device to access the first subset of services; and

assigning the visible contact address to the user account and a second client computing device to permit the second client computing device to access the first and second subsets of services.

2. The method of claim 1 , wherein authenticating the ownership of the phone number comprises:

receiving, from a client computing device that issues the request, a first verification that a Subscriber Identity Module (SIM) accessible to the client computing device is associated with the phone number,

receiving, from the client computing device, a second verification that the client computing device received a Short Message Service (SMS) code, or

some combination thereof.

3. The method of claim 1 , further comprising, prior to assigning the visible contact address to the user account:

creating the visible contact address based on the phone number.

4. The method of claim 1 , wherein the first subset of services includes:

client computing device recovery services,

cloud sharing services, or

some combination thereof.

5. The method of claim 1 , wherein the second subset of services includes:

messaging-based communication services,

audio/video-based communication services, or

some combination thereof.

6. The method of claim 1 , wherein:

the first client computing device comprises a first type of client computing device,

the second client computing device comprises a second type of client computing device, and

the first and second types of client computing devices are distinct from one another.

7. The method of claim 1 , wherein creating the user account based on the phone number comprises assigning the phone number to the user account.

8. A non-transitory computer readable storage medium configured to store instructions that, when executed by at least one processor included in a server computing device, cause the server computing device to manage phone number-based user accounts, by carrying out steps that include:

receiving a request to create a user account based on a phone number;

authenticating an ownership of the phone number;

creating hidden and visible contact addresses based on the phone number, wherein the hidden contact address permits access to a first subset of services that omits at least a second subset of services that are otherwise accessible using the visible contact address;

assigning the hidden contact address to the user account and a first client computing device to permit the first client computing device to access the first subset of services; and

assigning the visible contact address to the user account and a second client computing device to permit the second client computing device to access the first and second subsets of services.

9. The non-transitory computer readable storage medium of claim 8 , wherein authenticating the ownership of the phone number comprises:

receiving, from a client computing device that issues the request, a first verification that a Subscriber Identity Module (SIM) accessible to the client computing device is associated with the phone number,

receiving, from the client computing device, a second verification that the client computing device received a Short Message Service (SMS) code, or

some combination thereof.

10. The non-transitory computer readable storage medium of claim 8 , wherein the steps further include, prior to assigning the visible contact address to the user account:

creating the visible contact address based on the phone number.

11. The non-transitory computer readable storage medium of claim 8 , wherein the first subset of services includes:

client computing device recovery services,

cloud sharing services, or

some combination thereof.

12. The non-transitory computer readable storage medium of claim 8 , wherein the second subset of services includes:

messaging-based communication services,

audio/video-based communication services, or

some combination thereof.

13. The non-transitory computer readable storage medium of claim 8 , wherein:

the first client computing device comprises a first type of client computing device,

the second client computing device comprises a second type of client computing device, and

the first and second types of client computing devices are distinct from one another.

14. The non-transitory computer readable storage medium of claim 8 , wherein creating the user account based on the phone number comprises assigning the phone number to the user account.

15. A server computing device configured to manage phone number-based user accounts, the server computing device comprising:

at least one processor; and

at least one memory storing instructions that, when executed by the at least one processor, cause the server computing device to carry out steps that include:

receiving a request to create a user account based on a phone number;

authenticating an ownership of the phone number;

creating hidden and visible contact addresses based on the phone number, wherein the hidden contact address permits access to a first subset of services that omits at least a second subset of services that are otherwise accessible using the visible contact address;

assigning the hidden contact address to the user account and a first client computing device to permit the first client computing device to access the first subset of services; and

assigning the visible contact address to the user account and a second client computing device to permit the second client computing device to access the first and second subsets of services.

16. The server computing device of claim 15 , wherein authenticating the ownership of the phone number comprises:

receiving, from a client computing device that issues the request, a first verification that a Subscriber Identity Module (SIM) accessible to the client computing device is associated with the phone number,

receiving, from the client computing device, a second verification that the client computing device received a Short Message Service (SMS) code, or

some combination thereof.

17. The server computing device of claim 15 , wherein the steps further include, prior to assigning the visible contact address to the user account:

creating the visible contact address based on the phone number.

18. The server computing device of claim 15 , wherein the first subset of services includes:

client computing device recovery services,

cloud sharing services, or

some combination thereof.

19. The server computing device of claim 15 , wherein the second subset of services includes:

messaging-based communication services,

audio/video-based communication services, or

some combination thereof.

20. The server computing device of claim 15 , wherein:

the first client computing device comprises a first type of client computing device,

the second client computing device comprises a second type of client computing device, and

the first and second types of client computing devices are distinct from one another.

Continuity (3)
Continuation 17017560 · Sep 10, 2020
Provisional Application 63041912 · Jun 21, 2020
Related Publication 20240129411A1 · Apr 18, 2024
References Cited (27)
US 10506088B1 · Singh · 2019 [cited by applicant]
US 20030163706A1 · Cocchi · 2003 [cited by examiner]
US 20060240824A1 · Henderson et al. · 2006 [cited by applicant]
US 20080304518A1 · Cheng et al. · 2008 [cited by applicant]
US 20090279682A1 · Strandell et al. · 2009 [cited by applicant]
US 20130007900A1 · Santhanu · 2013 [cited by applicant]
US 20130222127A1 · Ray Avalani · 2013 [cited by examiner]
US 20130247149A1 · Sanft et al. · 2013 [cited by applicant]
US 20140254434A1 · Jain · 2014 [cited by examiner]
US 20150358808A1 · Jain et al. · 2015 [cited by applicant]
US 20160065553A1 · Lim · 2016 [cited by applicant]
US 20160286041A1 · Forsman et al. · 2016 [cited by applicant]
US 20170223537A1 · Lee et al. · 2017 [cited by applicant]
US 20190166255A1 · Reddy · 2019 [cited by examiner]
US 20200053214A1 · Kats · 2020 [cited by examiner]
US 20210400148A1 · Liu et al. · 2021 [cited by applicant]
CN 102027764A · 2011 [cited by applicant]
CN 107690802A · 2018 [cited by applicant]
CN 108605048A · 2018 [cited by applicant]
KR 20150061534A · 2015 [cited by applicant]
KR 20150100463A · 2015 [cited by applicant]
KR 20150128852A · 2015 [cited by applicant]
KR 20170015038A · 2017 [cited by applicant]
PCT Patent Application No. PCT/US2021/038243—International Search Report and Written Opinion dated Sep. 17, 2021. [cited by applicant]
Korean Patent Application No. 10-2022-7044950—Notice of Preliminary Rejection dated Sep. 25, 2023. [cited by applicant]
European Patent Application PCT/US2021/038243—Extended European Search Report dated Jun. 21, 2024. [cited by applicant]
Chinese Patent Application No. 202180044386.4; Office Action dated Apr. 27, 2025, 15 pages with machine translation. [cited by applicant]