Third-Party Intermediary for Application Usage Permission Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing application distribution markets lack the ability to actively improve download and usage efficiency of software applications, as developers and operators can only passively receive download metrics without interacting with distributors or users to enhance promotion capabilities.
Innovation Solution
A method and apparatus for requesting and acquiring usage permissions, where a third-party system receives download information from a first application, authenticates it, and requests the first application's server to configure usage permissions, thereby expanding download channels and improving efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a third-party system receives and authenticates download information from a first application to enable downloading a second application, then the download channel for the second application is expanded and download efficiency is improved, but the system complexity increases due to the need for authentication and permission configuration mechanisms
Solution Approach 1:
The patent introduces a third-party system as an intermediary between the first application and the second application download process. This intermediary receives download information, performs authentication, and coordinates with the first application's server to configure usage permissions. The intermediary mechanism enables expanded download channels without requiring direct complex integration between the first and second applications, thus improving download efficiency while managing system complexity through a dedicated mediation layer.
2Adaptability or versatility
If the third-party system requests and configures usage permissions for the first account, then the promotional capabilities and usage efficiency are improved, but the loss of information increases due to the additional data transmission and processing steps
Solution Approach 1:
The patent implements preliminary action by having the third-party system receive and authenticate download information before the actual download process begins. The usage permission configuration is requested and prepared in advance through the first application's server. This preliminary authentication and permission setup ensures that when the download occurs, all necessary information is already validated and configured, minimizing information loss during the actual download and usage process.
3Ease of operation
If the first application is unable to acquire the first application for downloading the second application, then the ease of operation is maintained with simple download processes, but the productivity decreases due to the inability to request and configure usage permissions
Solution Approach 1:
The third-party system serves as an intermediary that bridges the gap between the simple download interface of the first application and the complex permission configuration requirements. Users interact with the familiar simple download process in the first application, while the intermediary handles the backend authentication and permission configuration with the first application's server. This maintains ease of operation for users while enabling the productivity-enhancing permission configuration capability through the intermediary's automated processes.
Data Source
AI summary
The present disclosure discloses a method performed at a computer acting as a third-party system for requesting for a usage permission. The third-party system receives download information sent by means of a page of a first application, the download information at least including a download identifier, and the download identifier being used for indicating a first device identifier of a first device running the first application, a first account logging into the first application, and a second application identifier of a downloaded second application. After authenticating the download information, the third-party system requests a server of the first application to configure the usage permission for the first account in response to an authentication result and return such configuration to the first application running at the first device.