Ad Server Transaction Processing via Intermediary Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing ad server systems face challenges in processing transactions seamlessly on Internet-connectable devices, often resulting in incomplete transactions due to login encumbrances and resource utilization inefficiencies, while struggling to provide user-specific and relevant advertisements effectively.
Innovation Solution
The system processes ad server transactions by determining user interactions with advertisements, initiating transactions with a transaction server, and offloading transactional processes to the ad server, allowing for seamless user authentication and transaction completion without requiring complex advertiser application logic, thereby reducing resource utilization and enhancing user engagement.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If ad server systems process transactions directly on Internet-connectable devices, then user-specific and relevant advertisements can be provided, but transaction failures occur due to login encumbrances and resource utilization inefficiencies
Solution Approach 1:
The patent extracts the transaction processing function from the ad server system and relocates it to a dedicated transaction server. This separation allows the ad server to focus on advertisement delivery while the transaction server handles authentication and transaction completion, thereby reducing device complexity and improving transaction reliability by removing login encumbrances from the user device flow.
Solution Approach 2:
The patent introduces a transaction server as an intermediary between the ad server and the user device. This intermediary handles the complex authentication and transaction processing, shielding the user device from complexity while ensuring reliable transaction completion. The transaction server acts as a mediator that coordinates between advertisement delivery and transaction fulfillment.
2Ease of operation
If complex advertiser application logic is implemented on Internet-connectable devices, then seamless user authentication can be achieved, but device resources are inefficiently utilized
Solution Approach 1:
The patent extracts complex authentication logic from advertiser applications on Internet-connectable devices and relocates it to a transaction server. This extraction maintains seamless user authentication by handling complex logic centrally while reducing device resource utilization by removing heavy processing requirements from user devices.
Solution Approach 2:
The transaction server provides self-service authentication capabilities, handling user verification and transaction processing without requiring complex local logic on user devices. This allows seamless authentication while minimizing device resource usage, as the server independently manages the authentication process.
3Productivity
If advertiser applications handle transaction logic locally, then transaction processing can be completed, but resource utilization inefficiencies and transaction failures increase
Solution Approach 1:
The patent introduces a transaction server as an intermediary that improves both transaction processing efficiency and completion rate. By centralizing transaction logic on a dedicated server with appropriate resources and reliability mechanisms, the system achieves efficient processing while reducing failures that occur when logic is distributed across multiple advertiser applications on user devices.
Data Source
AI summary
Computer systems and methods for processing ad server transactions are provided. In some embodiments, the computer systems and methods may comprise determining an application to execute on an Internet-connectable device in response to a user interaction with an advertisement displayed on the Internet-connectable device; causing the Internet-connectable device to execute the application; receiving a security token, wherein the security token indicates successful authentication of the user by a transaction server associated with the application; after receiving the security token, initiating at least one transaction with the transaction server on behalf of the application in response to a user action within the application; and communicating results of the at least one transaction to the user.