|Publication number||US8195763 B2|
|Application number||US 11/490,495|
|Publication date||5 Jun 2012|
|Filing date||21 Jul 2006|
|Priority date||22 Jul 2005|
|Also published as||CA2513016A1, EP1908213A1, EP1908213A4, EP1908213B1, US8930494, US20070180125, US20120210131, WO2007009257A1|
|Publication number||11490495, 490495, US 8195763 B2, US 8195763B2, US-B2-8195763, US8195763 B2, US8195763B2|
|Inventors||Michael Knowles, David Tapuska, Tatiana Kalougina|
|Original Assignee||Research In Motion Limited|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (62), Non-Patent Citations (18), Referenced by (11), Classifications (17), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
A portion of this specification contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyrights whatsoever.
This specification relates generally to mobile data communication systems, and more particularly to a method for securely synchronizing cache contents of a mobile Internet browser with a proxy server.
Mobile communication devices are becoming increasingly popular for business and personal use due to a relatively recent increase in number of services and features that the devices and mobile infrastructures support. Handheld mobile communication devices, sometimes referred to as mobile stations, are essentially portable computers having wireless capability, and come in various forms. These include Personal Digital Assistants (PDAs), cellular phones and smart phones.
It is known in the art to provide local file caching. One approach is set forth in GloMop: Global Mobile Computing By Proxy, published Sep. 13, 1995, by the GloMop Group, wherein PC Card hard drives are used as portable file caches for storing, as an example, all of the users' email and Web caches. The user synchronizes the file caches and the proxy server keeps track of the contents. Mobile applications (clients) are able to check the file caches before asking for information from the proxy server by having the server verify that the local version of a given file is current.
A detailed description of the preferred embodiment is set forth in detail below, with reference to the following drawings, in which:
In general, there is provided a secure method of synchronizing cache contents of a mobile browser with a server, comprising initiating a session between the browser and server, including transmission of browser state information regarding the cache contents and an authentication key to the server, maintaining a record of data sent from the server to the browser for storage in the cache, maintaining a record of the state information regarding the cache contents transmitted from the browser to the server; and transmitting data requests from the browser to the server, in response to which the server uses the authentication key to generate a message authentication code that includes a cryptographic hash of data, and accesses each record of data and returns only data that does not already form part of the cache contents, and wherein the returned data includes a result of a hash of data generated using the authentication key for authentication by the browser before updating the cache contents with the data.
The method set forth herein has specific application to a secure system for communicating information between an enterprise or proxy server and a mobile Internet browser using an HTTP-like protocol, referred to herein as the Browser Session Management (BSM) protocol, that provides a control channel between the proxy server and the mobile device browser, so that the mobile device browser can communicate to the proxy server what data the mobile device browser has cached (from previous browsing). The BSM protocol is an “out of band” protocol in that BSM communications are in addition to the usual stream of HTTP requests from the mobile device browser to the proxy server, and provides “metadata” relating to cache contents. This metadata is used by the proxy server when handling subsequent requests from the mobile device browser, to determine what data to send to the mobile device browser, thereby significantly reducing data transfer on subsequent requests relative to the prior art methodology discussed above.
Because the proxy server is aware of what the mobile device browser has stored in its cache, the amount of data sent to the mobile device browser may be reduced, thereby increasing the performance of the mobile device browser and reducing operational cost. For example, if after the first request the CNN.com banner is cached and if the proxy server “knows” that the information has been cached then there will be no need to send the CNN.com banner to the mobile device browser upon subsequent visits to the CNN web site.
In contrast to the prior art GloMop caching methodology discussed above, the exemplary method set forth herein synchronizes the cache contents when the mobile device browser connects to the proxy server in order to initiate a session and keeps track of changes to the cache via knowledge of what data has been sent to the mobile device browser in combination with state information periodically received from the mobile device browser identifying what has actually been cached. Also, as set forth in greater detail below, the proxy server uses this cache knowledge to determine what to send back to the mobile device browser. In contrast, the prior art GloMop methodology does not contemplate sending any state information to the proxy server for identifying what has actually been cached in the device. Moreover, the prior art GloMop approach first checks the local cache, and then queries the proxy server to determine whether a particular data item in the cache is current or not. According to the GloMop prior art, the proxy server does not use its own knowledge of the mobile device browser cache to determine what to send back to the mobile device browser.
Additional aspects and advantages will be apparent to a person of ordinary skill in the art, residing in the details of construction and operation as more fully hereinafter described and claimed, reference being had to the accompanying drawings.
In terms of Web browsing functionality, the device 1 communicates with enterprise or proxy server 9 using HTTP over an IP protocol optimized for mobile environments. In some embodiments, the device 1 communicates with the proxy server 9 using HTTP over TCP/IP, over a variant of TCP/IP optimized for mobile use (e.g. Wireless Profiled TCP), or over other, proprietary protocols. For example, according to the communications protocol of
The communication between the device 1 and proxy server 9 is optionally encrypted with an encryption scheme, such as Triple Data Encryption Algorithm (TDEA, formerly referred to as Triple Data Encryption Standard (Triple DES)), as is known in the art. The proxy server 9 enables Internet access, preprocesses and compresses HTML and XML content from the Web server 15 before sending it to the device 1, transcodes content type, stores HTTP cookies on behalf of the device 1, and supports certificate authority authentications, etc.
In order to indicate device browser state information to the proxy server 9, three transitional state messages are defined herein, as follows: CONNECT, UPDATE and DISCONNECT, each of which conforms to the exemplary BSM protocol. As shown in
The CONNECT transitional message creates a new session with a connection identifier carried in the payload, device information and state data (e.g. current cache and device information) in the form of a set of hash functions for use by the proxy server 9 in preparing a response. Specific care is taken not to identify to the proxy server 9 what cookies or cache entries are contained on the device 1. Only hash values of the state data are sent to the proxy server 9 in order to protect the identity of state data on the device 1.
The CONNECT message also contains a unique authentication key for generating a MAC (Message Authentication Code) using a Hash Message Authentication Code (HMAC) algorithm that incorporates a cryptographic hash function in combination with the authentication key. Each portion of a multi-part document from the proxy server 9 also contains an HMAC, generated using the authentication key, that is used for authenticating the proxy server 9 before adding that portion to the device cache. This prevents a third party from creating its own multi-part document and sending it to the device 1 for injecting cache entries that could be used to extract personal information from the user.
The UPDATE transition message notifies the proxy server 9 of changes that have occurred on the device 1 since the last CONNECT message or the last UPDATE message, between the device 1 and proxy server 9 (e.g. new cache entries added because of a push, or invoking the “Low Memory Manager” (LMM) or other memory-space preservation policies on the device and purging items from the cache).
The DISCONNECT transition message notifies the proxy server 9 that the device 1 will no longer send any more messages using the connection identifier specified in the payload. The proxy server 9 can then de-allocate any memory reserved for the connect session between the device 1 and proxy server 9. Upon receiving the disconnect message, the proxy server 9 deletes any session cookies for the device 1 (if it is processing cookies) along with state information. Receiving a request on the identified connection after the DISCONNECT has been received, and before any subsequent CONNECT message has been received, is defined as an error.
Since state is indicated from the device 1 to the proxy server 9, and state may be stored in transient memory within proxy server 9, a mechanism is provided for the proxy server 9 to return to the device 1 a message indicating that the session the device is trying to use is not valid. Once this occurs, the device 1 issues a new CONNECT message and establishes a new session with the proxy server 9, and re-issues the original request.
The data protocol set forth herein is similar to HTTP in order to reduce complexity and to reuse code that already exists for the HTTP protocol. Thus, data transmission according to this protocol begins with a STATE keyword; followed by a BSM (Browser Session Management) protocol identifier and a “Content-Length” header. The end of the “headers” is indicated by a double CRLF (a sequence of control characters consisting of a carriage return (CR) and a line feed (LF)), much like HTTP. After the double CRLF pair (i.e. \r\n) a WBXML (WAP Binary Extensible Markup Language) encoded document is inserted as the message payload. The WBXML document is later decoded using a DTD (Document Type Definition) and codebook, as discussed in greater detail below. The indication of the protocol version refers to what version of the DTD to validate the request against (ie. BSM/1.1 stipulates using version 1.1 of the DTD). It should be noted that WBXML encoding of the contents of BSM messages is set forth to allow for more efficient processing of the BSM message at the device 1, but that in alternate embodiments, the BSM message may be formatted as normal (textual) XML.
The following is an example communication using the protocol according to the preferred embodiment:
<WBXML Encoded document of length 40 bytes>
In the foregoing, the first four lines form the CONNECT message from the device 1 to the proxy server 9, and the last two lines are the response from the proxy server 9.
An exemplary XML document, is as follows:
<!DOCTYPE bsm PUBLIC “-// DTD BSM 1.0//EN”
<bsm id=“2” hmac=”12345678901234567890”>
<entry urlHash=“FEEDDEED01” dataHash=“FDDEDEED11”
In the example, the state data includes the URL of an HTML page within the device cache. It will be noted that the XML document payload includes a connection identifier (i.e. bsm id=“2”), a value indicating when the document was last modified (i.e. etag=“SomeEtag”), a page expiry (i.e. expiry=“256712323”), and hash values for a URL (i.e. entry urlHash=“FEEDDEED01”) and a data attribute (i.e. entry dataHash=“FDDEDEED11”) rather than transmitting the actual URL and data attribute themselves. Thus, as shown in
In the first case, if both the dataHash and the urlHash of the retrieved portion match the dataHash and urlHash of a cache entry that the proxy server 9 knows the device 1 has, then the server 13 simply omits this portion from the response, as the device 1 still has a valid entry in its cache.
In the second case, if the dataHash of the retrieved portion matches the dataHash of a cache entry that the proxy server 9 knows the device 1 has, but the urlHash of the retrieved portion does not match the urlHash of that cache entry, the server 13 inlines this updated portion in the combined response to the device 1. However, because the dataHash matches a dataHash of an entry that already exists on the device 1, the inlined response does not include the actual data, but instead only includes a new HTTP header whose value is the new dataHash. When the device 1 receives this inlined portion, it detects the special header, looks for the cache entry with that dataHash, and either creates or updates its cache entry for that URL with the data corresponding to the dataHash by copying that data from the other cache entry (the cache for device 1 is modified to have two indexes, one to retrieve cache entries by URL, the other to retrieve cache entries by dataHash). Finally, if the proxy server 9 already has a cache entry for the urlHash, it updates that entry with the new dataHash; otherwise it creates a new entry for this portion.
In the third case, if the dataHash of the retrieved portion does not match the dataHash of any of the cache entries that the proxy server 9 has received from the device 1 in the BSM messages, then the server inlines the entire portion (headers and new data), since this portion has been updated and the device 1 does not contain the updated value anywhere in its cache.
Although not indicated in
An exemplary DTD, according to the preferred embodiment, is as follows:
bsm (cache?, device)>
cache (size, (entry)+)>
action (add|remove|remove_all|quick_add) “add”
device (version, memfree)>
size 9 (instead of action)
Finally, an exemplary codebook, is as follows:
As is well known in the art, the codebook is used as a transformation for compressing the XML document to WBXML, wherein each text token is represented by a single byte from the codebook.
As discussed above, the proxy server 9 transmits multi-part documents in a proprietary format of compressed HTML, interspersed with data for images and other auxiliary files (which may or may not be related to the main HTML Web page). However, in a departure from conventional HTML, each document part may also include a response code (e.g. “200” for OK, or “304” for “not modified” to indicate that the specified document part has already been cached in the device 1). This may be used for selective downloading of document parts rather than entire documents and for indicating when a part (e.g. image) is about to expire. This is useful, for example, when one Web page links to another page containing one or more common elements.
Of course, certain device requests (e.g. page refresh) will always result in a full document download, irrespective of device state information stored in the proxy server 9.
It is contemplated that the inclusion of response codes may be used by heuristic processes within the proxy server 9 to learn user behaviour and modify downloading of documents based on tracking the history of certain changes reflected in the hash value (e.g. the server 9 may learn to download a certain page (e.g. CNN news) at a particular time each day based the user's history of issuing requests for that page at regular times. As discussed above, because the downloaded documents are multi-part and contain embedded response codes, only those portions of the document that have changed are actually downloaded.
As indicated above, the protocol of the preferred embodiment is preferably carried over a proprietary IPPP transport layer, but can also be easily adapted to run over TCP/IP on a specific port. The protocol is preferably implemented as a handler in the proxy server 9, thereby simplifying any currently existing protocol. (e.g. to avoid overloading a current HTTP protocol).
A person skilled in the art, having read this description of the preferred embodiment, may conceive of variations and alternative embodiments. For example, the conditional transfer of data based on communication of state information, as set forth above, may also be applied to separately transmitting individual portions of the multipart document as opposed to transmitting the entire document at once.
In some embodiments, the proxy server 9 uses heuristic algorithms to learn what additional data requests the device may make based on knowledge of the current request, and knowledge of past activity. In some instances, the device may follow a pattern of requesting a first Web page, and then a second Web page. For example, the device may first request the “cnn.com” Web page, and then request the “cnn.com/news” Web page. The proxy server 9 learns this pattern, and whenever the device requests the first Web page, the proxy server 9 determines that the device is likely to then request the second Web page. The proxy server 9 then fetches the second Web page, and uses its knowledge of the data cached on the device 1 (i.e. from the state information transferred to the proxy server 9 during initiation of the present connection) to determine whether the second Web page already exists within the data cached on the device. If so, the proxy server 9 includes information about the second Web page via response codes embedded within the response provided for the first Web page. If the device 1 requires the second Web page, then the device 1 can reference its cache and can avoid having to make a request to the proxy server 9 for the second Web page.
In other embodiments, heuristic processes within the proxy server 9 learn user behaviour and modify downloading of documents based on tracking the history of certain changes reflected in the hash value (e.g. the proxy server 9 may learn to download a certain page (e.g. CNN news) at a particular time each day based the user's history of issuing requests for that page at regular times). As discussed, because the downloaded documents are multi-part and contain embedded response codes, only those portions of the document that have changed are actually downloaded.
All such variations and alternative embodiments are believed to be within the ambit of the claims appended hereto.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5864837||12 Jun 1996||26 Jan 1999||Unisys Corporation||Methods and apparatus for efficient caching in a distributed environment|
|US6041357 *||6 Feb 1997||21 Mar 2000||Electric Classified, Inc.||Common session token system and protocol|
|US6055569||27 Jan 1998||25 Apr 2000||Go Ahead Software Inc.||Accelerating web access by predicting user action|
|US6061794 *||30 Sep 1997||9 May 2000||Compaq Computer Corp.||System and method for performing secure device communications in a peer-to-peer bus architecture|
|US6115754||29 Dec 1997||5 Sep 2000||Nortel Networks Limited||System and method for appending location information to a communication sent from a mobile terminal operating in a wireless communication system to an internet server|
|US6233318 *||5 Nov 1996||15 May 2001||Comverse Network Systems, Inc.||System for accessing multimedia mailboxes and messages over the internet and via telephone|
|US6286032||5 Oct 1999||4 Sep 2001||Motorola, Inc.||Method and apparatus in a communication network for updating and maintaining record data|
|US6341316||28 Apr 2000||22 Jan 2002||Avantgo, Inc.||System, method, and computer program product for synchronizing content between a server and a client based on state information|
|US6393468||9 Jan 1998||21 May 2002||British Telecommunications Public Limited Company||Data access control|
|US6415276||13 Aug 1999||2 Jul 2002||University Of New Mexico||Bayesian belief networks for industrial processes|
|US6615267||10 Jun 1999||2 Sep 2003||Motorola, Inc.||System and method for delivery of information over narrow-band communications links|
|US6813690||16 Oct 2001||2 Nov 2004||Network Appliance, Inc.||Caching media data using content-sensitive identifiers|
|US6950863||21 Dec 2000||27 Sep 2005||Cisco Technology, Inc.||Method and system for verifying a software upgrade for a communication device|
|US7000032||3 Jul 2001||14 Feb 2006||Ianywhere Solutions, Inc.||System, method, and computer program product for syncing to mobile devices|
|US7092370||16 Aug 2001||15 Aug 2006||Roamware, Inc.||Method and system for wireless voice channel/data channel integration|
|US7330883||15 Mar 2000||12 Feb 2008||Cricket Communications, Inc.||System and method for sending local information from a wireless browser to a web server|
|US7383389||28 Apr 2004||3 Jun 2008||Sybase, Inc.||Cache management system providing improved page latching methodology|
|US20010027450||19 Mar 2001||4 Oct 2001||Takashi Shinoda||Method of detecting changed contents|
|US20020002627||20 Jun 2001||3 Jan 2002||Graham Stead||Method and system for interconnecting remote intelligent devices with a network|
|US20020004813||5 Mar 2001||10 Jan 2002||Alok Agrawal||Methods and systems for partial page caching of dynamically generated content|
|US20020042920||9 Oct 2001||11 Apr 2002||United Video Properties, Inc.||Systems and methods for supplementing on-demand media|
|US20020052916||28 Jun 2001||2 May 2002||Avantgo, Inc.||System, Method, and computer program product for customizing channels, content, and data for mobile devices|
|US20020107935||12 Jan 2001||8 Aug 2002||Epicrealm Inc.||Method and system for community data caching|
|US20020138551 *||13 Feb 2001||26 Sep 2002||Aventail Corporation||Distributed cache for state transfer operations|
|US20020160790||8 May 2002||31 Oct 2002||Schwartz Bruce V.||Method and architecture for interactive two-way communication devices to interact with a network|
|US20030074425 *||11 Oct 2002||17 Apr 2003||Mvp Kabushiki Kaisha||Browser with proxy server and information copying system|
|US20030079039||16 Oct 2001||24 Apr 2003||Forkner Damien R.||Web server utilizing a state machine and user token|
|US20030088421 *||25 Jun 2002||8 May 2003||International Business Machines Corporation||Universal IP-based and scalable architectures across conversational applications using web services for speech and audio processing resources|
|US20030088580||7 Nov 2001||8 May 2003||Sachin Desai||Methods and systems for preemptive and predictive page caching for improved site navigation|
|US20030110266||10 Dec 2001||12 Jun 2003||Cysive, Inc.||Apparatus and method of using session state data across sessions|
|US20030112772 *||26 Nov 2002||19 Jun 2003||Spacenet, Inc.||System and method for acceleration of a secure transmission over satellite|
|US20030120647||12 Feb 2003||26 Jun 2003||Alex Aiken||Method and apparatus for indexing document content and content comparison with World Wide Web search service|
|US20030177194||17 Mar 2003||18 Sep 2003||Stephen Crocker||Data replication system and method|
|US20030202649||29 May 2003||30 Oct 2003||Castel, Inc.||Call center management systems|
|US20040073626 *||21 Dec 2001||15 Apr 2004||Major Harry R.||Information browser system and method for a wireless communication device|
|US20040117486||17 Dec 2002||17 Jun 2004||International Business Machines Corporation||Secure cache of web session information using web browser cookies|
|US20040162885||18 Feb 2003||19 Aug 2004||Garg Sharad K.||Reducing communication for reads and updates in distributed object systems|
|US20040203670||27 Feb 2004||14 Oct 2004||Openwave Systems Inc.||Wireless mobile devices having improved operation during network unavailability|
|US20040220975||19 Feb 2004||4 Nov 2004||Hypertrust Nv||Additional hash functions in content-based addressing|
|US20040248558||4 Jun 2003||9 Dec 2004||Chandhok Ravinder Paul||Method and apparatus for translating resource names in a wireless environment|
|US20040249824||5 Jun 2003||9 Dec 2004||International Business Machines Corporation||Semantics-bases indexing in a distributed data processing system|
|US20050060498||15 Sep 2003||17 Mar 2005||Curtis John D.||Method, system and program product for caching data objects|
|US20050065950 *||12 Nov 2004||24 Mar 2005||Naren Chaganti||Online repository for personal information|
|US20050076087 *||7 May 2004||7 Apr 2005||Vulcan Portals Inc.||Method and system for email synchronization for an electronic device|
|US20050094782||29 Oct 2004||5 May 2005||Lg Electronics Inc.||Telephone number retrieval system & method|
|US20050117558||2 Dec 2004||2 Jun 2005||Deutsches Zentrum Fur Luft-Und Raumfahrt E. V.||Method for reducing data transport volume in data networks|
|US20050138176||22 Dec 2004||23 Jun 2005||Slipstream Data Inc.||Meta-data based method for local cache utilization|
|US20050144439||13 Sep 2004||30 Jun 2005||Nam Je Park||System and method of managing encryption key management system for mobile terminals|
|US20060036754||7 Apr 2005||16 Feb 2006||International Business Machines Corporation||Web service simple object access protocol request response processing|
|US20060056415||8 Nov 2005||16 Mar 2006||Ji-Woong Lee||Method and system for detailed accounting of packet data|
|US20060218402||2 Jun 2006||28 Sep 2006||Sonic Mobility Inc.||Proxy method and system for secure wireless administration of managed entities|
|US20060251047||9 Feb 2006||9 Nov 2006||Michael Shenfield||System and method of representing data entities of standard device applications as built-in components|
|US20070150524||14 Oct 2004||28 Jun 2007||Johan Eker||Uptating data in a mobile terminal|
|US20070156852||30 Dec 2005||5 Jul 2007||Prabakar Sundarrajan||System and method for performing flash crowd caching of dynamically generated objects in a data communication network|
|US20080134018||31 Oct 2007||5 Jun 2008||Mainstream Scientific, Llc||Component for Coordinating the Accessing and Rendering of an Application Media Package|
|CA2379082A1||27 Mar 2002||27 Sep 2003||Ibm Canada Limited-Ibm Canada Limitee||Secure cache of web session information using web browser cookies|
|EP1154356A1||9 May 2000||14 Nov 2001||Alcatel Alsthom Compagnie Generale D'electricite||Caching of files during loading from a distributed file system|
|EP1202585A2||24 Oct 2001||2 May 2002||Nokia Corporation||Use of a service in a mobile communication system|
|EP1441470A1||21 Jan 2003||28 Jul 2004||Hewlett-Packard Company||Network attached storage method and system|
|WO1999017227A1||28 Sep 1998||8 Apr 1999||Ibm||Method and system for prefetching information|
|WO2001061438A2||20 Feb 2001||23 Aug 2001||Permabit Inc||A data repository and method for promoting network storage of data|
|WO2003088566A1||9 Apr 2002||23 Oct 2003||Ericsson Telefon Ab L M||Secure file transfer|
|1||"Optimizing Web Delivery Over Wireless Links: Design, Implementation, and Experiences". Rajiv Chakravorty, Andrew Clark and Ian Pratt. IEEE Journal on Selected Areas in Communications, vol. 23, No. 2, Feb. 2005 pp. 402-416.|
|2||"The Design and Implementation of the FreeBSD Operting System" Marshall Kirk McKusick; Geroge V. Neville-Neil. Published by: Addison-Welsey Professional. ISBN-13: 978-0-201-70245-3, Published: Aug. 2, 2004.|
|3||"Wireless markup language specification version 1.1", Internet Citation, [Online] XP002161009 Retrieved from the Internet URL:http://www1.wapforum.org/tech/documents/SPEC-WML-19990616.pdf, Jun. 16, 1999.|
|4||"Wireless markup language specification version 1.1", Internet Citation, [Online] XP002161009 Retrieved from the Internet URL:http://www1.wapforum.org/tech/documents/SPEC-WMLl-19990616.pdf.|
|5||European Patent Application No. 06761161.6 Supplementary Search Report dated Dec. 22, 2009.|
|6||European Patent Application No. 06761164.0 Supplementary Search Report dated Dec. 14, 2009.|
|7||European Search Report of EP 06 76 1162 dated Oct. 31, 2008.|
|8||European Search Report of EP 06 76 1166 dated Aug. 21, 2008.|
|9||GloMop: Global Mobile Computing by Proxy, GloMop Group, Sep. 13, 1995, pp. 1-12.|
|10||Ibrahim T. I. et al: "Neural nets based predictive prefetching to tolerate WWW latency" Distributed Computing Systems, 2000. Proceedings. 20th International Conference on Taipei, Taiwan Apr. 10-13, 2000, Los Alamitos, CA, USA, IEEE Comput. Soc, US, Apr. 10, 2000, pp. 636-643, XP010379077, ISBN: 978-0/7695-0601-2.|
|11||Jesse Anton et al: "Web Caching for Database Applications With Oracle Web Cache" ACM Proceedings of SIGMOD. International Conference on Management of Data, XX, XX, Jun. 4, 2002, pp. 594-599, XP001152240 ISBN: 978-1-58113-497-1.|
|12||Jiun-Long Huang, et al: "A QoS-aware transcoding proxy using on-demand data broadcasting" INFOCOM 2004. Twenty-Third Annual Joint Conference of the IEEE Computer and Communications Societies, IEEE, Piscataway, NJ, USA, vol. 3, Mar. 7, 2004. XP010740561.|
|13||Kahol et al.: "A Strategy to Manage Cache Consistency in a Disconnected Distributed Environment" [Online] Jul. 2001, p. 686-700, XP002501708. Retrieved from the Internet: URL:http://ieeexplore.ieee.org/stamp/stamp.jsp? arnumber=00940744>.|
|14||Loon T. S. et al.: "Alleviating the latency and bandwidth problems in WWW browsing" Proceedings of the USENIX Symposium on Internet Technologies and Systems, XX, XX, Dec. 8, 1997, pp. 219-230, XP002109263.|
|15||May, Michael, Jun. 19, 2008, Supplementary European Search Report.|
|16||Supplementary European Search Report of Jan. 14, 2009.|
|17||William H. Collins of Ericsson et al.: "Method of recognizing duplicates in received information" Research Disclosure, Mason Publications, Hampshire, GB, vol. 440, No. 45, Dec. 1, 2000, XP007127230 ISSN: 0374-4353.|
|18||Zhu et al.: "Using Markov Models for Web site Link Prediction" Proceedings of the Thirteenth ACM conference on Hypertext and Hypermedia, [online] Jun. 11, 2002-Jun. 15, 2002; pp. 169-170, XP002559093.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8683005 *||31 Mar 2010||25 Mar 2014||Emc Corporation||Cache-based mobile device network resource optimization|
|US8799467 *||9 Sep 2011||5 Aug 2014||Microsoft Corporation||Storage and communication de-duplication|
|US8799480||18 Jul 2011||5 Aug 2014||Movik Networks||Content pre-fetching and CDN assist methods in a wireless mobile network|
|US8930494 *||24 Apr 2012||6 Jan 2015||Blackberry Limited||Secure method of synchronizing cache contents of a mobile browser with a server|
|US9088461 *||21 Jun 2012||21 Jul 2015||International Business Machines Corporation||Common web accessible data store for client side page processing|
|US9088462 *||12 Feb 2013||21 Jul 2015||International Business Machines Corporation||Common web accessible data store for client side page processing|
|US20100269154 *||21 Oct 2010||Research In Motion Limited||Method of communciating state information between a server and a mobile device browser with version handling|
|US20110202634 *||18 Aug 2011||Surya Kumar Kovvali||Charging-invariant and origin-server-friendly transit caching in mobile networks|
|US20120210131 *||24 Apr 2012||16 Aug 2012||Research In Motion Limited||Secure method of synchronizing cache contents of a mobile browser with a server|
|US20130346535 *||12 Feb 2013||26 Dec 2013||International Business Machines Corporation||Common web accessible data store for client side page processing|
|US20130346542 *||21 Jun 2012||26 Dec 2013||International Business Machines Corporation||Common web accessible data store for client side page processing|
|U.S. Classification||709/217, 709/219, 709/218|
|Cooperative Classification||H04L9/3242, H04L2209/60, H04L63/12, H04L67/02, H04L9/12, G06F17/30902, H04L2209/80, H04L2209/76|
|European Classification||H04L29/08N1, G06F17/30W9C, H04L63/12, H04L9/32L4, H04L9/12|
|6 Oct 2006||AS||Assignment|
Owner name: RESEARCH IN MOTION LIMITED, CANADA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KNOWLES, MICHAEL;TAPUSKA, DAVID;KALOUGINA, TATIANA;SIGNING DATES FROM 20060721 TO 20060921;REEL/FRAME:018363/0341
|11 Jun 2014||AS||Assignment|
Owner name: BLACKBERRY LIMITED, ONTARIO
Free format text: CHANGE OF NAME;ASSIGNOR:RESEARCH IN MOTION LIMITED;REEL/FRAME:033134/0228
Effective date: 20130709
|7 Dec 2015||FPAY||Fee payment|
Year of fee payment: 4