Subaccount Authorization System for Developer User Access Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The telephony market lacks an efficient system for managing relationships between software developers and application users, with complex billing structures acting as a barrier to entry for new developers, hindering the growth of the application ecosystem.
Innovation Solution
A system and method that utilizes subaccounts to authorize and connect application developers and users, allowing developers to create applications with varying permissions and usage metrics, while enabling users to access multiple applications through a single account, with a centralized platform for distribution and compensation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a centralized platform with subaccounts is implemented to manage developer-user relationships, then the ease of operation and developer attraction improves, but the system complexity increases
Solution Approach 1:
The system segments user identities into multiple subaccounts, each associated with specific applications and permission profiles. This segmentation allows the platform to manage complex developer-user relationships through organized, isolated units rather than monolithic account structures, improving operational ease while systematically managing complexity.
Solution Approach 2:
The patent introduces an intermediary authorization system that mediates between developers and users. This intermediary layer handles permission management, subaccount creation, and relationship orchestration, shielding end users and developers from underlying system complexity while enabling sophisticated relationship management.
2Adaptability or versatility
If variable rate billing is used for telephony services, then the adaptability to different service levels improves, but the device complexity and barrier to entry for developers increases
Solution Approach 1:
The system enables self-service billing through automated subaccount management and permission-based access control. Developers can create subaccounts and define permission profiles without manual intervention, and the system automatically handles usage tracking and billing calculations, reducing the operational complexity of variable rate billing while maintaining adaptability.
Solution Approach 2:
The patent implements parameter-based permission profiles that allow flexible configuration of access levels, usage limits, and billing parameters. By changing these parameters dynamically rather than restructuring the entire billing system, the platform achieves adaptability to different service levels while keeping the underlying billing complexity manageable.
3Manufacturing precision
If subaccounts with permission profiles are created for each application, then the manufacturing precision of access control improves, but the quantity of accounts and system complexity increases
Solution Approach 1:
The subaccount structure serves multiple functions simultaneously: it acts as an access control mechanism, a billing unit, an application association container, and a permission profile holder. This multi-functionality reduces the need for separate specialized accounts for each function, thereby reducing the total number of accounts needed while maintaining precise access control.
Solution Approach 2:
The system implements a nested account structure where subaccounts are nested within user accounts, and permission profiles are nested within subaccounts. This hierarchical nesting organizes the account structure efficiently, allowing precise access control through layered permissions while avoiding the need for a flat, expansive account system that would require managing numerous independent accounts.
Data Source
Figure 1
Figure 2
Figure 3A~3C
AI summary
A system and method for authorizing application use of a user that can include creating a developer account associated with an application of an application platform; receiving an authorization request to authorize the application to act on a user account; creating a subaccount of a user, wherein the subaccount is associated with the developer account; creating an authorization record, that includes setting a permission profile for the subaccount; and returning a subaccount identifier to the developer.