Content adaptation   

Abstract: A system includes a mobile device and an optimization server. The mobile device is capable of transmitting request data that includes a requested webpage and identification data. The optimization server is configured to receive response data that corresponds to the request data from a content server, to adapt the response data based on the identification data, and to transmit the adapted response data to the mobile device.

This application is a divisional of U.S. application Ser. No. 11/636,033, filed Dec. 8, 2006, titled “Content Adaptation,” which is incorporated herein by reference.

The Internet allows for vast amounts of information to be communicated over any number of interconnected networks, computers, and network devices. Typically, information or content is located at websites on one or more content servers, and a user can retrieve this content using a user agent, such as a web browser, running on a client device. For example, the user can input a webpage address into the web browser or access a web link, which sends requests to the server to access and provide to the user the content on the respective website. This type of communication is commonly referred to as “web browsing.”

Web browsing is enjoyed by millions of users on the Internet. Because web browsing has become so widespread, many websites provide more complicated, enhanced visual effects and features. These enhanced qualities are generally directed towards a user viewing the website from a typical computer, such as a laptop, PC, etc.

Mobile web browsing has gained some traction because of the increased network speed, improved browsers, more powerful devices, and better pricing plans. But significant challenges still remain for Internet browsing on a mobile phone to become more popular among users. Some end user challenges include the frustration over long download times, the lack of accessibility, the lack of performance, and the lack of usability. For example, it may take over a minute for a full download of www.msn.com from a mobile phone on a typical network without multipart encoding. Accessibility challenges include the inability of WAP 2.0 browsers to render rich HTML content; the lack of plug in support for rich multi-media content; and the lack of support for DHTML websites. Performance challenges include the large latency in wireless networks, the discrepancies between uplink and downlink bandwidth, and TCP limitations. Along with the accessibility and performance issues, usability challenges can include, among other things, attempting to fit a large complicated page onto a small screen. In addition to these challenges to the user, website developers also face challenges such as the lack of standards for defining the device and the browsers capability, and the large test matrix of a myriad device and browser combinations. For mobile web browsing to become more readily operable for the user, these issues must be addressed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an exemplary system.

FIG. 2 is a block diagram illustrating an embodiment of the exemplary system of FIG. 1.

FIG. 3 is a functional diagram illustrating an exemplary communication flow for the exemplary system of FIG. 2.

FIGS. 4A & 4B illustrate a Document Object Model tree structure and a corresponding webpage.

FIG. 5 is a flowchart representing the steps of an exemplary method for processing request data.

FIG. 6 is a flowchart representing the steps of an exemplary method for processing response data.

FIG. 7 is a flowchart representing the steps of an exemplary method for processing JavaScript coding.

FIG. 8 is a flowchart representing the steps of an exemplary method for providing content styling.

FIG. 9 is a flowchart representing the steps of an exemplary method for performing small screen adaptation of the original web page and paginating the response data.

FIG. 10 is a flowchart representing the steps of an exemplary method for performing form processing.

FIGS. 11A & 11B are block diagrams illustrating the exemplary effects of form processing.

Reference will now be made in detail to the exemplary embodiments implemented according to the invention, the examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.

FIG. 1 is a block diagram of an exemplary system. Exemplary system 100 can be any type of system that transmits data over a network, such as a wireless network, Internet, etc. For example, the exemplary system can include a browser requesting access to content from content servers through the Internet. The exemplary system can include, among other things, a user agent 102, a client device 104, a gateway 106, one or more networks 108, 112, an optimization server 110, a storage device 114, and one or more content servers 116-118.

User agent 102 is a client application used with a network protocol. For example, user agent 102 could be a web browser, a search engine crawler, a screen reader, or a Braille browser, and user agent 102 could be used to access the Internet. User agent 102 can be a software program that transmits request data (e.g., an HTTP/HTTPS/WAP/WAIS/Gopher/RTSP request, etc.) to a web server and receives response data in response to the request data. For example, user agent 102 can send request data to content servers 116-118 for a particular file or object data of a web page by its URL, and the content server of the web page can query the object data in a database and can send back the object data as part of the response data (e.g., HTTP/WAP response data) to the user agent. This process continues until every object in the web page has been downloaded to the user agent.

Client device 104 is a computer program or hardware device that can access remote services. Client device 104 can receive request data from user agent 102, can transmit the request data to the content servers, and can receive response data in response to the request data. For example, client device 104 can be Bytemobile Optimization Client Software. In some embodiments, user agent 102 and client device 104 can be housed in the same device, such as a computer, a PDA, a cell phone, a laptop, or any device accessing the Internet. In some embodiments, client device 104 can be removed and its functionality can be included in user agent 102.

Gateway 106 is a device that converts formatted data provided in one type of network to a particular format required for another type of network. Gateway 106, for example, may be a server, a router, a firewall server, a host, or a proxy server. The gateway 106 has the ability to transform the signals received from client device 104 into signals that network 108 can understand and vice versa. Gateway 106 may be capable of processing audio, video, and T.120 transmissions alone or in any combination, and is capable of full duplex media translations.

Networks 108 and 112 can include any combination of wide area networks (WANs), local area networks (LANs), or wireless networks suitable for networking communication such as Internet communication.

Optimization server (OS) 110 is a server that provides communication between gateway 106 and content servers 116-118. For example, OS 110 could be a Bytemobile Optimization Services Node. OS 110 can optimize performance by enabling significantly faster and more reliable service to customers. OS 110 can include optimization techniques, which are further described below.

Storage device 114 is a device that stores adaptation parameters relating to the specifications of user agent 102 and a device utilizing the user agent 102. In some embodiments, storage device 114 can be included with OS 110, local to OS 110, or remote from OS 110. The stored adaptation parameters can assist OS 1.10 in determining what kind of optimization techniques are provided to user agent 102 and the device. Storage device 114 can be any type of device that stores data.

Content servers 116-118 are servers that receive the request data from user agent 102, process the request data accordingly, and return the response data back to user agent 102. For example, content servers 116-118 can be a web server, an enterprise server, or any other type of server. Content servers 116-118 can be a computer or a computer program responsible for accepting HTTP requests from the user agent and serving the user agents with web pages.

FIG. 2 is a block diagram illustrating an embodiment of the exemplary system of FIG. 1. Mobile device 202 is a wireless device that can include, among other things, user agent 102 and/or client device 104. OS 110 may include, among other things, a request monitor 210, a content cache 220, a response monitor 230, an adaptor 240, and interfaces 250, 260. As stated above, in some embodiments, storage device 114 can be located within, local to, or remote from OS 110.

Request monitor 210 can be a software program or a hardware device that receives or intercepts the request data, such as an HTTP request for a specific URL, from mobile device 202. Request monitor 210 has the ability to extract identification data, from the request data and to provide the identification data to the storage device 114 in exchange for adaptation parameters, which can be provided to adaptor 240 for future processing. Identification data can include, among other things, the type of user agent and the type mobile device, and the adaptation parameters can include data describing the properties of the user agent and mobile device, such as screen size, etc. Request monitor 210 can also communicate with the content cache 220 to provide stored adapted response data (e.g., sub-pages) to the mobile device 202. Further, request monitor 210 can transmit the request data to content server 116 if the request data does not request the adapted response data.

Response monitor 230 can be a software program or a hardware device that receives response data from content server 116. After receiving the response data, response monitor 230 provides the content data to adaptor 240, which adapts the response data for mobile device 202. Depending upon whether the response data is to be adapted for the mobile device, response monitor 230 can provide either the response data or the adapted response data to mobile device 202.

Adaptor 240 can be a software program or a hardware device that receives the response data from response monitor 230 and adapts the response data in accordance with the adaptation parameters received from request monitor 210. This adaptation process will be further described below. Adaptor 240 can provide the adapted response data to response monitor 230 and/or content cache 220. In some embodiments, the adapted response data includes a main adapted sub-page and subsequent adapted sub-pages. The main adapted sub-page could be provided to the response monitor 230, which provides it to mobile device 202 for downloading and displaying. These sub-pages could be stored at content cache 220 for future referencing.

Content cache 220 is a device that stores adapted response data (e.g., adapted sub-pages) for future referencing. Content cache 220 can provide this adapted response data to request monitor 210, which can provide the adapted response data to mobile device 202 without having to re-request response data from content server 116. Content cache 220 can also provide adapted response data to response monitor 230, which transmits this data to mobile device 202. In some embodiments, content cache 220 can directly provide the adapted response data to mobile device 202.

Interfaces 250 and 260 are software programs or hardware devices that communicatively couple OS 110 with mobile device 202 and content server 116 through wired or wireless communication means. Each interface has the ability to communicate with the elements of OS 110, translate the communication so that the communication means can utilize the data, and transmit the translated communication across the corresponding communication means. In some embodiments, interfaces 250 and 260 can include encryption means and/or decryption means to encrypt communications leaving from and decrypt communications coming into OS 110.

FIG. 3 is a functional diagram illustrating an exemplary communication flow in the exemplary system of FIG. 2. It is assumed for the purposes of explaining this exemplary communication flow that the request data corresponds to a request for a URL and that content cache 220 has not stored any adapted response data corresponding to the requested URL. Further, while the exemplary communication flow illustrates OS 110 providing the content adaptation, in some embodiments, the user agent may include additional components to locally assist the content adaptation process by transferring or further translating the adapted information.

The user inputs a URL into a user agent of the mobile device 202. Mobile device 202 then transmits (302) the request data to OS 110. The request data can include, among other things, the requested URL and identification data identifying the mobile device and the type of user agent on the mobile device. The request data can be directed explicitly to a gateway or proxy and then to OS 110, or it can be directed to content server 116 and the request can be intercepted transparently by an inline proxy or gateway.

Request monitor 210 extracts the identification data from the request data and then transmits (304) the identification data to storage device 114. Responsive to the identification data, storage device 114 returns (306) adaptation parameters to request monitor 210. In some embodiments, the adaptation parameters may include, among other things, the following data:

Adaptation parameters Meaning/Use JavaScript support whether the device supports JavaScript Screen width usable screen width in pixels Screen height usable screen height in pixels Markup language usually XHTML or XHTML/MP Color depth bit-depth used for image transcoding/byte-reduction Maximum bytes per page devices generally have problems when the page size exceeds this limit Maximum images per page some devices have problems when the number of images exceeds this limit Maximum links per page few devices have problems when the number of links exceeds this limit Font-size support whether variable font-sizes can be used Font-family support whether variable font-families can be used Preferred font-family default font-family of the device Minimum font size the smallest size where differences in font size are no longer rendered Maximum font size the largest size where differences in font size are no longer rendered Number of available font how many different font sizes can be specified between sizes min and max where each font size is rendered differently HTML table support whether the browser can render tables Previous sub-page soft-key The key number in the handset keypad to link to the “Previous sub-page” action Next sub-page soft-key The key number in the handset keypad to link to the “Next sub-page” action Top of page soft-key The key number in the handset keypad to link to the “Top of the page” action Bottom of page soft-key The key number in the handset keypad to link to the “bottom of page” action Referring page soft-key The key number in the handset keypad to link to the “Previously viewed site” action Maximum URL length Some devices cannot handle long URLs Maximum HTML title length Used to chop title for browser which don\'t manage long titles properly User Agent Used for device-specific adaptations

Upon receiving the adaptation parameters, request monitor 210 can forward (308) the adaptation parameters to adaptor 240 for future referencing. In some embodiments, adaptor 240 receives the identification data from request monitor 210, stores it, and exchanges the identification data for the adaptation parameters located in storage device 114.

After communicating with adaptor 240, request monitor 210 forwards (310) the request data to content server 116. Subsequently, content server 116 provides (312) response data (e.g., HTTP response), associated with the request data, to response monitor 230 of OS 110. The response data can include, among other things, an HTML document, a Cascaded Style Sheet Files, and one or more JavaScript files, all of which constitute the requested webpage. These web pages include a collection of nested HTML elements, represented by tags. The OS 110 can utilize a parser to create a data structure that stores the tags found in the HTML document for accessing and manipulating each individual element in the HTML document. Because HTML tags can be nested, this data structure is likely to be in the form of a tree.

The Document Object Model (DOM) interface is a standard method to access this tree-like data structure, commonly referred to as the DOM tree of the HTML document, and represents the requested web page. The embodiments described herein generally assume a DOM tree as the input, but it would be readily appreciated by one of ordinary skill in the art that any other type of data structure representing a web page can be used. Further, it would be readily appreciated by one of ordinary skill in the art that any other method for accessing and traversing the elements in the webpage can be used.

The following sample HTML document illustrates some key concepts:

<html> <head>

Download full PDF for full patent description/claims.




You can also Monitor Keywords and Search for tracking patents relating to this Content adaptation patent application.

Patent Applications in related categories:

20130117660 - Automated document revision markup and change control - Automated comparison of Darwin Information Typing Architecture (DITA) documents for revision mark-up includes reading document data from first and second DITA documents into respective document object model trees of nodes, and identifying and collapsing emphasis subtree nodes in the trees into their parent nodes, the collapsing caching emphasis data from ...

20130117658 - Block zoom on a mobile electronic device - A device, system and method are provided for processing structured documents, such as webpages, for display. Various elements within the structured document are parsed and rendered by an electronic device for outputting to an external or integrated display. In response to a detected scaling instruction, such as a zoom in ...

20130117656 - Conversion of web template designs - A portion of the CMS stage of web site development is automated to convert a static markup language mockup and its referenced resources into a renderable CMS web template. One or more features in the mockup are represented by one or more static markup language elements, which are replaced by ...

20130117657 - Designing interactive web templates - A web template author can author interactive web templates via a static markup language-based authoring tool. The web template author can insert static markup language snippets representing one or more configurable controls of a web template into a static markup language-based authoring tool. Each snippet includes a definition of a ...

20130117659 - Dynamic server-side image sizing for fidelity improvements - Dynamically-generated images sized according to a requesting web client application display resolution are provided. The client application may calculate a target display resolution and pass the target display resolution as an input parameter with a request to a server for application content. The server may use the desired size input ...

20130117661 - Formatting system monitoring information - Embodiments disclosed herein relate to formatting system monitoring information. In one embodiment, a processor formats information related to monitoring a system. The formatted information may be related to components in a system. In one embodiment, the processor formats received information related to the system. The processor may output the formatted ...


###


Other recent patent applications listed under the agent :