Headless Browser Architecture for Secure Mobile Data Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile devices face challenges in accessing secured user data due to security considerations and resource limitations, particularly for small and mid-size banks, where developing customized mobile banking applications is expensive and account aggregation techniques fail if banks block access from third-party servers.
Innovation Solution
A system utilizing a native mobile application and a back-end server executing a headless browser, where the server communicates with a remote server through a configurable network service on the mobile device, masking the server's identity to bypass security blocks and offload processing, enabling secure access to secured data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If account aggregation is used to access secured data through an intermediary server, then mobile devices can access secured data without dedicated integration, but banks may block accesses from third-party servers for security reasons
Solution Approach 1:
The patent uses a headless browser as an intermediary component that runs on the mobile device itself, acting as a mediator between the native application and the remote server. This headless browser handles web-based authentication and data access protocols, allowing the system to access secured data through web interfaces without requiring dedicated API integrations with the bank's backend systems.
2Reliability
If customized mobile banking applications are developed for small and mid-size banks, then secure access to bank data is achieved, but development costs become prohibitively expensive
Solution Approach 1:
The patent implements a universal headless browser component that can handle multiple banking applications and protocols through a single native application interface. This multi-functional approach allows small and mid-size banks to access secured data without requiring separate customized integrations for each bank, significantly reducing development costs while maintaining security through centralized credential management.
3Adaptability or versatility
If processing power and battery life are increased to support full-featured mobile banking applications, then application functionality is improved, but device resource consumption increases
Solution Approach 1:
The patent extracts resource-intensive web browsing and authentication processing functions from the native application layer and implements them within a headless browser environment. This extraction allows the heavy computational tasks to be handled in a dedicated subsystem, improving application functionality while managing battery consumption more efficiently by isolating resource demands.
Data Source
AI summary
Systems, methods, and computer-readable storage devices to enable secured data access from a mobile device executing a native mobile application that operates in connection with a server executing a headless browser. The exemplary process includes receiving, at a server, at least registration data and browser state information, the registration data and the browser state information from a mobile device, a browser state database or a shared folder. The mobile device executing a native application and configured to host a configurable network service to connect to a website hosted by a remote server, the registration data including application identifier information associated with the native application and address data associated with the configurable network service. Then, establishing a secure connection between a headless browser, using the browser state information and the registration data, and the configurable network service, the headless browser comprising a web browser not having a corresponding displayed GUI.