US 12,133,076 B2
Secured data access from a mobile device executing a native mobile application and a headless browser
Charles Eric Smith, Dripping Springs, TX (US); Chris Dutrow, Laurel, MD (US); and Sergio Gustavo Ayestaran, Buenos Aires (AR)
Assigned to AppBrilliance, Inc., Dripping Springs, TX (US)
Filed by AppBrilliance, Inc., Dripping Springs, TX (US)
Filed on May 10, 2023, as Appl. No. 18/195,470.
Application 18/195,470 is a continuation of application No. 17/018,388, filed on Sep. 11, 2020, granted, now 11,689,927.
Application 17/018,388 is a continuation of application No. 15/981,705, filed on May 16, 2018, granted, now 10,785,651, issued on Sep. 22, 2020.
Application 15/981,705 is a continuation of application No. 15/474,981, filed on Mar. 30, 2017, granted, now 10,009,773, issued on Jun. 26, 2018.
Claims priority of provisional application 62/316,373, filed on Mar. 31, 2016.
Prior Publication US 2023/0276234 A1, Aug. 31, 2023
This patent is subject to a terminal disclaimer.
Int. Cl. H04W 12/08 (2021.01); G06Q 40/02 (2023.01); H04B 1/3827 (2015.01); H04L 9/40 (2022.01); H04W 12/06 (2021.01); H04W 12/086 (2021.01); H04L 67/02 (2022.01)
CPC H04W 12/08 (2013.01) [G06Q 40/02 (2013.01); H04B 1/3827 (2013.01); H04L 63/168 (2013.01); H04W 12/068 (2021.01); H04W 12/086 (2021.01); H04L 67/02 (2013.01)] 19 Claims
OG exemplary drawing
 
1. A mobile device comprising:
a wireless transceiver;
a processor;
a display device; and
memory storing instructions executable by the processor to perform operations comprising:
receiving, at a native application and via the wireless transceiver, access credential data;
providing the access credential data from the native application to a headless browser running on the processor;
initiating a secured connection from the headless browser to a remote server that hosts a website, the remote server supporting access to secured data;
sending, by the headless browser via the secured connection, the access credential data to the remote server;
receiving first web page data of the website from the remote server via the secured connection;
parsing the first web page data to identify user-specific data, wherein identifying the user-specific data comprises accessing a mapping between the native application and the website, and the mapping is determined based on a scraping operation performed on the website, through a supported language interpreted by a web browser;
sending the user-specific data to the native application for display in a graphical user interface on the display device;
receiving a user command via a user input device on the mobile device;
sending, by the headless browser and via the secured connection, a request to the remote server to access the secured data based on the user command; and
receiving, by the headless browser via the secured connection, at least a portion of the secured data.