Phone Number Accounts With Hidden Contact Addresses for Staged Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional user account creation processes are inefficient and user account creation processes are inefficient and user account creation processes are inefficient and user account management processes are inefficient and user account management processes are ineffective and user account management processes are ineffective due to issues with alphanumeric and email-based usernames, particularly for users without email addresses.
Innovation Solution
Implementing a method for creating user accounts based on a phone number, where a hidden contact address is initially assigned, allowing access to a subset of services, and a visible contact address can be assigned upon verification of continued user ownership, enabling access to a broader range of services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users register with alphanumeric usernames, then user accounts can be created, but users face availability issues and must manage multiple usernames across services
Solution Approach 1:
The patent applies universality by enabling phone numbers to serve multiple functions: as user identifiers for account creation, as contact addresses for service access, and as verification mechanisms. This eliminates the need for separate usernames across different services, as the phone number universally identifies the user across all services in the ecosystem.
2Adaptability or versatility
If users register with email addresses, then username availability issues are resolved, but users without email addresses cannot create accounts
Solution Approach 1:
The patent applies self-service by allowing users to register directly with their phone numbers without requiring email addresses or manual username selection. The system automatically verifies phone number ownership through SMS codes and creates accounts seamlessly, enabling users to complete registration independently and efficiently using a universally possessed identifier.
3Ease of operation
If phone number-based accounts are created immediately, then users can access services, but security verification and ownership confirmation are compromised
Solution Approach 1:
The patent applies preliminary action by performing phone number ownership verification through SMS code confirmation before granting full account access and service permissions. This preliminary verification step ensures that only the legitimate owner of the phone number can create and access the account, establishing security before service activation.
Solution Approach 2:
The patent applies dynamics by implementing a staged access model where account permissions evolve from limited to full access based on verification status. Initially, accounts have restricted access pending verification, then transition to full service access once ownership is confirmed, allowing the system to adapt security levels dynamically based on verification state.
4Ease of operation
If visible contact addresses are assigned to all users, then service access is simplified, but user privacy and security are compromised
Solution Approach 1:
The patent applies local quality by differentiating between verified and unverified user accounts in terms of contact address visibility. Verified users receive visible contact addresses that enable full service access, while unverified users have hidden contact addresses that limit access. This localized differentiation of contact address visibility based on verification status balances privacy protection with service accessibility.
Data Source
AI summary
This application sets forth techniques for managing user identifier-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 user identifier, (2) in response to authenticating that the first client computing device is associated with the user identifier: creating the user account based on the user identifier, creating a hidden contact address based on the user identifier, 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 user identifier: requiring the user account to be updated to be based on a different user identifier, or assigning, to the user account, a visible contact address based on the user identifier.


