Identity Map for Cross-Device Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile gaming platforms face challenges in managing user authentication credentials across multiple devices and platforms, leading to reduced effectiveness and stability, as well as the inability to associate different devices with a single user identity, and lack of management for multiple execution states of gaming applications.
Innovation Solution
An identity service generates a stored 'identity map' that associates user authentication credentials with a single user identity across devices, allowing seamless access to game states and managing multiple execution states, enabling users to play games on different devices with synchronized progress.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple authentication credentials are managed across different devices, then user accessibility is improved, but system complexity increases
Solution Approach 1:
The patent introduces an intermediary authentication service that acts as a mediator between multiple devices and authentication credentials. This service receives authentication credentials from various devices, determines their association with a single user identity, and manages the mapping between different credentials and devices, thereby reducing the complexity at individual device level while maintaining cross-device accessibility
Solution Approach 2:
The authentication service is designed to handle multiple authentication credentials from different devices and platforms, making it universal. It can process authentication requests from various device types (mobile devices, tablets, etc.) and associate them with a single user identity, allowing one authentication system to serve multiple functions and devices without requiring device-specific authentication mechanisms
2Ease of operation
If user identity is associated with multiple devices, then user experience is improved, but authentication stability deteriorates
Solution Approach 1:
The system implements feedback mechanisms where authentication behavior from one device can influence the association with other devices. When a user authenticates on a new device, the system receives feedback about this authentication event and updates the user identity mapping accordingly. This feedback loop allows the system to dynamically adjust device associations based on actual user behavior, maintaining stability while improving user experience
Solution Approach 2:
The system performs preliminary actions by pre-establishing authentication behavior patterns and device associations before actual authentication events occur. It analyzes authentication behavior in advance and creates expected mappings between devices and user identities, which then guide subsequent authentication decisions and maintain consistent user experience across devices while ensuring authentication stability
3Adaptability or versatility
If multiple execution states are managed, then application versatility is improved, but data management complexity increases
Solution Approach 1:
The patent segments the execution state management into distinct components: identifying execution states, associating them with user identities, and managing their synchronization across devices. This segmentation allows the system to handle multiple execution states (different game versions, progress levels, etc.) separately and systematically, reducing the overall complexity of data management while maintaining application versatility
Solution Approach 2:
The execution state management structure uses a nested organization where execution states are nested within user identity mappings, which are in turn nested within device associations. This nested structure allows multiple execution states to be organized hierarchically under a single user identity, making it easier to manage and retrieve the appropriate state without overwhelming complexity
Data Source
AI summary
An identity authenticator receives a first authentication credential from a first application at a first computing device. The identity authenticator then determines that the first authentication credential is associated with a second authentication credential for the first application at a second computing device based on a stored authentication identity. The identity authenticator then provides a stored execution state for the first application to the first computing device, wherein the stored execution state is associated, based on the stored authentication identity, with at least one of the first authentication credential or the second authentication credential.