Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

a new methodology of extracting the existing web page in real time for mobile browser

IP.com Disclosure Number: IPCOM000244263D
Publication Date: 2015-Nov-27
Document File: 3 page(s) / 55K

Publishing Venue

The IP.com Prior Art Database


This disclosure describes a new way of extracting existing desktop web page into a mobile supported one, it includes the look and feel transformation and the mobile browser specific characteristic compromising, which can lead us to save lots of our time from developing a new mobile page, we can make use of this technology to tremedously save our effort on mobile web app support.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 3

a new methodology of extracting the existing web page in real time for mobile browser

there are lots of web site which is mainly used for serve the desktop browser, but as mobile is becoming more and more popular these days, to serve the mobile browser is also becoming a necessary task for our web application. But most solution is to implement a new web application for it, or just make the web site to have multi-channel support, both of them are time consuming, this disclosure describe a new methodology to extract the existing desktop only support page into a new version which fit mobile's characteristic and save bandwidth/performance in real time

this disclosure includes following main ideas:

1> extract the existing desktop page based on widget granularity, re-factory it with necessary part for mobile

2> setup a dependency graph of executed user code, and performs slicing upon the dependency graph for mobile specific


1> save limited mobile bandwidth for better performance

2> extract and re-organized the web widget for better mobile usability

main steps:

1> scan nodes under in Breadth First Search: "/html/body/div[1]", "/htmlbody/div[2]", ...

2> then do deep first search on each level 1 node and find out the target extract candidate region

3> distinguish the proper region using position and width/height caculation via javascript according to mobile's screen size, default is 320px

4> re-style on the root node of the region and make it support multi-channel automatically in region granularity.

- if width i...