Method and Apparatus for Content Pre-Fetching and Preparation
First Claim
1. A method of maintaining data in an information network, comprising the steps of:
- storing replicas of content data in two or more stores; and
synchronizing the content data in each of the two or more stores, wherein timing of the synchronization process is a function of a user'"'"'s historical context information.
0 Assignments
0 Petitions

Accused Products

Abstract
A method of pre-fetching and preparing content in an information processing system is provided. The method includes the steps of generating at least one content pre-fetching policy and at least one content preparation policy, wherein each of the policies are at least in part a function of context information associated with a user. The content is pre-fetched based on information contained within the at least one content pre-fetching policy. Once the content has been pre-fetched, it is prepared based on information contained within the at least one content preparation policy. The context information associated with the user includes at least one of the user'"'"'s usage patterns, current location, future plans and preferences.
417 Citations
Device and Method for Distributing and Forwarding Requests to a Plurality of Web Servers in an Industrial Automation Arrangement | ||
Patent #
US 20110004664A1
Filed 07/02/2010
|
Current Assignee
Siemens AG
|
Original Assignee
Siemens AG
|
CONTENT MANAGEMENT | ||
Patent #
US 20110072110A1
Filed 11/30/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Christopher L. Scofield, David R. Richardson, Bradley E. Marshall, Swaminathan Sivasubramanian
|
CONTENT MANAGEMENT | ||
Patent #
US 20110078240A1
Filed 11/30/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Christopher L. Scofield, David R. Richardson, Bradley E. Marshall, Swaminathan Sivasubramanian
|
Apparatus and Method For Context-Aware Mobile Data Management | ||
Patent #
US 20110225368A1
Filed 03/15/2011
|
Current Assignee
Howard University
|
Original Assignee
Howard University
|
Request routing utilizing client location information | ||
Patent #
US 8,028,090 B2
Filed 11/17/2008
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Locality based content distribution | ||
Patent #
US 8,060,561 B2
Filed 06/27/2011
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Service provider registration by a content broker | ||
Patent #
US 8,065,417 B1
Filed 11/17/2008
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing CDN registration by a storage provider | ||
Patent #
US 8,060,616 B1
Filed 11/17/2008
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
CONTENT MANAGEMENT | ||
Patent #
US 20090248858A1
Filed 08/08/2008
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
System and method for efficient adaptation of multimedia message content | ||
Patent #
US 20040181550A1
Filed 03/13/2003
|
Current Assignee
Nokia Corporation
|
Original Assignee
Nokia Corporation
|
Managing content delivery network service providers | ||
Patent #
US 8,073,940 B1
Filed 11/17/2008
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing content delivery network service providers by a content broker | ||
Patent #
US 8,122,098 B1
Filed 11/17/2008
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing based on class | ||
Patent #
US 8,135,820 B2
Filed 04/29/2011
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing | ||
Patent #
US 8,156,243 B2
Filed 03/31/2008
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Application and network-based long poll request detection and cacheability assessment therefor | ||
Patent #
US 8,166,164 B1
Filed 10/14/2011
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
REQUEST AND RESPONSE CHARACTERISTICS BASED ADAPTATION OF DISTRIBUTED CACHING IN A MOBILE NETWORK | ||
Patent #
US 20120110110A1
Filed 10/17/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Management of pre-fetched mapping data incorporating user-specified locations | ||
Patent #
US 8,180,851 B1
Filed 09/26/2011
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Cache defeat detection and caching of content addressed by identifiers intended to defeat cache | ||
Patent #
US 8,190,701 B2
Filed 11/01/2011
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Updating routing information based on client location | ||
Patent #
US 8,234,403 B2
Filed 06/21/2011
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
ADAPTIVE NETWORK COMMUNICATION TECHNIQUES | ||
Patent #
US 20120198078A1
Filed 02/01/2011
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
Managing content delivery network service providers | ||
Patent #
US 8,239,514 B2
Filed 11/17/2011
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing using network computing components | ||
Patent #
US 8,239,571 B2
Filed 03/07/2011
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Locality based content distribution | ||
Patent #
US 8,275,874 B2
Filed 11/14/2011
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Map tile data pre-fetching based on mobile device generated event analysis | ||
Patent #
US 8,280,414 B1
Filed 09/26/2011
|
Current Assignee
Google Inc.
|
Original Assignee
Google Inc.
|
Application and network-based long poll request detection and cacheability assessment therefor | ||
Patent #
US 8,291,076 B2
Filed 03/05/2012
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Service provider registration by a content broker | ||
Patent #
US 8,301,778 B2
Filed 11/17/2011
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing CDN registration by a storage provider | ||
Patent #
US 8,301,748 B2
Filed 11/14/2011
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Social caching for device resource sharing and management | ||
Patent #
US 8,316,098 B2
Filed 04/19/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Content management | ||
Patent #
US 8,321,568 B2
Filed 03/31/2008
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing utilizing client location information | ||
Patent #
US 8,321,588 B2
Filed 09/14/2011
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Distributed management of keep-alive message signaling for mobile network resource conservation and optimization | ||
Patent #
US 8,326,985 B2
Filed 11/01/2011
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Content management | ||
Patent #
US 8,346,937 B2
Filed 11/30/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Content management | ||
Patent #
US 8,352,614 B2
Filed 11/30/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Content management | ||
Patent #
US 8,352,615 B2
Filed 11/30/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Content management | ||
Patent #
US 8,352,613 B2
Filed 11/30/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
System and method for a mobile device to use physical storage of another device for caching | ||
Patent #
US 8,356,080 B2
Filed 07/20/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Electronic-mail filtering for mobile devices | ||
Patent #
US 8,364,181 B2
Filed 12/10/2007
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Request routing based on class | ||
Patent #
US 8,386,596 B2
Filed 03/12/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing secure content in a content delivery network | ||
Patent #
US 8,397,073 B1
Filed 03/11/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Content management | ||
Patent #
US 8,402,137 B2
Filed 08/08/2008
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Context aware data presentation | ||
Patent #
US 8,412,675 B2
Filed 02/24/2006
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Managing tracking information entries in resource cache components | ||
Patent #
US 8,412,823 B1
Filed 03/27/2009
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Aligning data transfer to optimize connections established for transmission over a wireless network | ||
Patent #
US 8,417,823 B2
Filed 11/18/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Updating routing information based on client location | ||
Patent #
US 8,423,667 B2
Filed 06/21/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Flexible real-time inbox access | ||
Patent #
US 8,438,633 B1
Filed 12/18/2006
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Locality based content distribution | ||
Patent #
US 8,438,263 B2
Filed 09/13/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Incentive driven content delivery | ||
Patent #
US 8,447,831 B1
Filed 03/31/2008
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing processing | ||
Patent #
US 8,452,874 B2
Filed 11/22/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing using network computing components | ||
Patent #
US 8,458,250 B2
Filed 08/06/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing utilizing client location information | ||
Patent #
US 8,458,360 B2
Filed 09/15/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Dynamically translating resource identifiers for request routing using popularitiy information | ||
Patent #
US 8,463,877 B1
Filed 09/15/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Point of presence management in request routing | ||
Patent #
US 8,468,247 B1
Filed 09/28/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Publishing data in an information community | ||
Patent #
US 8,468,126 B2
Filed 12/14/2005
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
ONLINE AND DISTRIBUTED OPTIMIZATION FRAMEWORK FOR WIRELESS ANALYTICS | ||
Patent #
US 20130172041A1
Filed 01/19/2012
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
ONLINE AND DISTRIBUTED OPTIMIZATION FRAMEWORK FOR WIRELESS ANALYTICS | ||
Patent #
US 20130172043A1
Filed 07/13/2012
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
SYSTEMS AND METHODS FOR MANAGING A MEDIA CONTENT QUEUE | ||
Patent #
US 20130173796A1
Filed 12/30/2011
|
Current Assignee
UV Corporation
|
Original Assignee
United Video Properties Incorporated
|
Distributed caching in a wireless network of content delivered for a mobile application over a long-held request | ||
Patent #
US 8,484,314 B2
Filed 10/14/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Cloud-based Content Management System | ||
Patent #
US 20130185434A1
Filed 01/18/2012
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
CLOUD-BASED CONTENT MANAGEMENT SYSTEM | ||
Patent #
US 20130185439A1
Filed 03/06/2013
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
CONTENT MANAGEMENT | ||
Patent #
US 20130110916A1
Filed 12/19/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Provisioning applications for a mobile device | ||
Patent #
US 8,494,510 B2
Filed 12/06/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Managing CDN registration by a storage provider | ||
Patent #
US 8,495,220 B2
Filed 09/15/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Map tile data pre-fetching based on user activity analysis | ||
Patent #
US 8,204,966 B1
Filed 09/26/2011
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Data pre-fetching based on user demographics | ||
Patent #
US 8,509,816 B2
Filed 11/11/2011
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Service provider registration by a content broker | ||
Patent #
US 8,510,448 B2
Filed 09/13/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
DNS query processing using resource identifiers specifying an application broker | ||
Patent #
US 8,521,851 B1
Filed 03/27/2009
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing content delivery network service providers | ||
Patent #
US 8,521,880 B1
Filed 11/17/2008
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Dynamically translating resource identifiers for request routing using popularity information | ||
Patent #
US 8,521,885 B1
Filed 09/15/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Client side cache management | ||
Patent #
US 8,533,293 B1
Filed 03/31/2008
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Mobile network background traffic data management with optimized polling intervals | ||
Patent #
US 8,539,040 B2
Filed 02/28/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Managing resources using resource expiration data | ||
Patent #
US 8,543,702 B1
Filed 09/15/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Map tile data pre-fetching based on user activity analysis | ||
Patent #
US 8,549,105 B1
Filed 06/19/2012
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Secure end-to-end transport through intermediary nodes | ||
Patent #
US 8,549,587 B2
Filed 02/14/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
System and method for executing commands that are non-native to the native environment of a mobile device | ||
Patent #
US 8,561,086 B2
Filed 05/17/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Request routing management based on network components | ||
Patent #
US 8,577,992 B1
Filed 09/28/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
CONTENT MANAGEMENT | ||
Patent #
US 20130297717A1
Filed 03/11/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing content delivery network service providers | ||
Patent #
US 8,583,776 B2
Filed 08/06/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Data Archiving Approach Leveraging Database Layer Functionality | ||
Patent #
US 20130304707A1
Filed 05/08/2012
|
Current Assignee
SAP SE
|
Original Assignee
SAP SE
|
Network resource identification | ||
Patent #
US 8,601,090 B1
Filed 03/31/2008
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
SMART LOADING OF MAP TILES | ||
Patent #
US 20130325317A1
Filed 12/05/2012
|
Current Assignee
Apple Inc.
|
Original Assignee
Apple Inc.
|
Cache optimization | ||
Patent #
US 8,606,996 B2
Filed 03/31/2008
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Detecting and preserving state for satisfying application requests in a distributed proxy and cache system | ||
Patent #
US 8,621,075 B2
Filed 04/27/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Request routing processing | ||
Patent #
US 8,626,950 B1
Filed 12/03/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
SYSTEM AND METHOD FOR PROACTIVE RESOURCE ALLOCATION | ||
Patent #
US 20140016575A1
Filed 09/28/2011
|
Current Assignee
Ohio State Innovation Foundation
|
Original Assignee
Ohio State University
|
Cache state management on a mobile device to preserve user experience | ||
Patent #
US 8,635,339 B2
Filed 08/22/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Content management | ||
Patent #
US 8,639,817 B2
Filed 12/19/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Point of presence management in request routing | ||
Patent #
US 8,676,918 B2
Filed 09/15/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Management of pre-fetched mapping data incorporating user-specified locations | ||
Patent #
US 8,683,008 B1
Filed 08/04/2011
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Dynamically translating resource identifiers for request routing using popularity information | ||
Patent #
US 8,688,837 B1
Filed 03/27/2009
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Polling | ||
Patent #
US 8,693,494 B2
Filed 03/31/2008
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Moveable storage | ||
Patent #
US 8,700,666 B2
Filed 02/21/2012
|
Current Assignee
Comcast Cable Communications LLC
|
Original Assignee
Comcast Cable Communications LLC
|
Cache defeat detection and caching of content addressed by identifiers intended to defeat cache | ||
Patent #
US 8,700,728 B2
Filed 05/17/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Information caching system | ||
Patent #
US 8,706,805 B2
Filed 12/19/2011
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Cross-platform event engine | ||
Patent #
US 8,209,709 B2
Filed 07/05/2010
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Distributed system for cache defeat detection and caching of content addressed by identifiers intended to defeat cache | ||
Patent #
US 8,204,953 B2
Filed 11/01/2011
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
PREDICTIVE NETWORK SYSTEM AND METHOD | ||
Patent #
US 20140113600A1
Filed 09/28/2011
|
Current Assignee
Ohio State Innovation Foundation
|
Original Assignee
Ohio State University
|
Pre-fetching map data using variable map tile radius | ||
Patent #
US 8,711,181 B1
Filed 11/16/2011
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Request routing based on class | ||
Patent #
US 8,713,156 B2
Filed 02/13/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing utilizing cost information | ||
Patent #
US 8,732,309 B1
Filed 11/17/2008
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Electronic-mail filtering for mobile devices | ||
Patent #
US 8,738,050 B2
Filed 01/07/2013
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Mobile device equipped with mobile network congestion recognition to make intelligent decisions regarding connecting to an operator network | ||
Patent #
US 8,750,123 B1
Filed 07/31/2013
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Apparatus and method for context-aware mobile data management | ||
Patent #
US 8,751,743 B2
Filed 03/15/2011
|
Current Assignee
Howard University
|
Original Assignee
Howard University
|
Content management | ||
Patent #
US 8,756,325 B2
Filed 03/11/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing utilizing popularity information | ||
Patent #
US 8,756,341 B1
Filed 03/27/2009
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Maintaining an IP connection in a mobile network | ||
Patent #
US 8,761,756 B2
Filed 09/13/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks International Oy
|
Adaptive network communication techniques | ||
Patent #
US 8,769,000 B2
Filed 02/01/2011
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
Integrated messaging | ||
Patent #
US 8,774,844 B2
Filed 04/08/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Dynamic bandwidth adjustment for browsing or streaming activity in a wireless network based on prediction of user behavior when interacting with mobile applications | ||
Patent #
US 8,775,631 B2
Filed 02/25/2013
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Timing of keep-alive messages used in a system for mobile network resource conservation and optimization | ||
Patent #
US 8,782,222 B2
Filed 09/05/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Managing resources using resource expiration data | ||
Patent #
US 8,782,236 B1
Filed 06/16/2009
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Application discovery on mobile devices | ||
Patent #
US 8,787,947 B2
Filed 06/18/2008
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Managing content delivery network service providers by a content broker | ||
Patent #
US 8,788,671 B2
Filed 01/25/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Content delivery to a mobile device from a content service | ||
Patent #
US 8,793,305 B2
Filed 12/13/2007
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
System and method of a relay server for managing communications and notification between a mobile device and a web access server | ||
Patent #
US 8,799,410 B2
Filed 04/13/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Pre-fetching map tile data along a route | ||
Patent #
US 8,803,920 B2
Filed 07/11/2012
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Map tile data pre-fetching based on user activity analysis | ||
Patent #
US 8,805,959 B1
Filed 02/14/2013
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Maintaining mobile terminal information for secure communications | ||
Patent #
US 8,805,334 B2
Filed 09/05/2008
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Integrated messaging | ||
Patent #
US 8,805,425 B2
Filed 01/28/2009
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Mobile device power management in data synchronization over a mobile network with or without a trigger notification | ||
Patent #
US 8,811,952 B2
Filed 05/05/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Map tile data pre-fetching based on mobile device generated event analysis | ||
Patent #
US 8,812,031 B2
Filed 08/30/2012
|
Current Assignee
Google Inc.
|
Original Assignee
Google Inc.
|
Method and system for management of a virtual network connection without heartbeat messages | ||
Patent #
US 8,812,695 B2
Filed 04/03/2013
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Request routing in a networked environment | ||
Patent #
US 8,819,283 B2
Filed 09/28/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
File system hinting | ||
Patent #
US 8,825,724 B2
Filed 03/29/2012
|
Current Assignee
Avago Technologies International Sales Pte Limited
|
Original Assignee
LSI Corporation
|
System and method for tracking billing events in a mobile wireless network for a network operator | ||
Patent #
US 8,831,561 B2
Filed 04/28/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
System and method for making requests on behalf of a mobile device based on atomic processes for mobile network traffic relief | ||
Patent #
US 8,832,228 B2
Filed 04/26/2012
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Distributed caching for resource and mobile network traffic management | ||
Patent #
US 8,838,783 B2
Filed 07/05/2011
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Flexible real-time inbox access | ||
Patent #
US 8,839,412 B1
Filed 09/13/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Web-based access to data objects | ||
Patent #
US 8,838,744 B2
Filed 01/28/2009
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Mobile traffic categorization and policy for network use optimization while preserving user experience | ||
Patent #
US 8,843,153 B2
Filed 11/01/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
System for providing policy based content service in a mobile network | ||
Patent #
US 8,849,902 B2
Filed 06/24/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Application programming interface for prefetching map data | ||
Patent #
US 8,849,942 B1
Filed 08/21/2012
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Hierarchies and categories for management and deployment of policies for distributed wireless traffic optimization | ||
Patent #
US 8,861,354 B2
Filed 12/14/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Policy based content service | ||
Patent #
US 8,862,657 B2
Filed 01/25/2008
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
System of redundantly clustered machines to provide failover mechanisms for mobile traffic management and network resource conservation | ||
Patent #
US 8,868,753 B2
Filed 12/06/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Provisioning of e-mail settings for a mobile terminal | ||
Patent #
US 8,873,411 B2
Filed 01/12/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols | ||
Patent #
US 8,874,761 B2
Filed 03/15/2013
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Mobile application traffic optimization | ||
Patent #
US 8,886,176 B2
Filed 07/22/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Dynamically determining a tile budget when pre-fetching data in a client device | ||
Patent #
US 8,886,715 B1
Filed 11/16/2011
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
PRE-FETCHING IN DISTRIBUTED COMPUTING ENVIRONMENTS | ||
Patent #
US 20140344344A1
Filed 07/29/2014
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
Optimization of resource polling intervals to satisfy mobile device requests | ||
Patent #
US 8,903,954 B2
Filed 11/22/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Mobile virtual network operator | ||
Patent #
US 8,909,192 B2
Filed 08/11/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Bandwidth measurement | ||
Patent #
US 8,909,759 B2
Filed 10/12/2009
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Detection and management of user interactions with foreground applications on a mobile device in distributed caching | ||
Patent #
US 8,909,202 B2
Filed 01/07/2013
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
System and method for providing a network service in a distributed fashion to a mobile device | ||
Patent #
US 8,914,002 B2
Filed 08/11/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Optimization of mobile traffic directed to private networks and operator configurability thereof | ||
Patent #
US 8,918,503 B2
Filed 08/28/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Data services using location patterns and intelligent caching | ||
Patent #
US 8,924,503 B2
Filed 12/07/2011
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Latency measurement in resource requests | ||
Patent #
US 8,924,528 B1
Filed 09/28/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Network resource identification | ||
Patent #
US 8,930,544 B2
Filed 10/29/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Latency measurement in resource requests | ||
Patent #
US 8,930,513 B1
Filed 09/28/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing management based on network components | ||
Patent #
US 8,938,526 B1
Filed 09/28/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Method and apparatus for intercepting events in a communication system | ||
Patent #
US RE45,348 E1
Filed 03/16/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Data services using location patterns and intelligent caching | ||
Patent #
US 8,943,162 B2
Filed 12/11/2012
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Application and network-based long poll request detection and cacheability assessment therefor | ||
Patent #
US 8,966,066 B2
Filed 10/12/2012
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Management of pre-fetched mapping data incorporating user-specified locations | ||
Patent #
US 8,972,529 B1
Filed 03/04/2014
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Mobile device and method to utilize the failover mechanism for fault tolerance provided for mobile traffic management and network/device resource conservation | ||
Patent #
US 8,977,755 B2
Filed 12/06/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Monitoring mobile application activities for malicious traffic on a mobile device | ||
Patent #
US 8,984,581 B2
Filed 07/11/2012
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Connection architecture for a mobile network | ||
Patent #
US 8,989,728 B2
Filed 09/07/2006
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Translation of resource identifiers using popularity information upon client request | ||
Patent #
US 8,996,664 B2
Filed 08/26/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Point of presence management in request routing | ||
Patent #
US 9,003,035 B1
Filed 09/28/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Predictive content delivery | ||
Patent #
US 9,002,828 B2
Filed 01/02/2009
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Request routing processing | ||
Patent #
US 9,003,040 B2
Filed 04/29/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Flexible and dynamic integration schemas of a traffic management system with various network operators for network traffic alleviation | ||
Patent #
US 9,009,250 B2
Filed 12/07/2012
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Locality based content distribution | ||
Patent #
US 9,009,286 B2
Filed 05/06/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Caching adapted for mobile application behavior and network conditions | ||
Patent #
US 9,021,048 B2
Filed 10/14/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Updating routing information based on client location | ||
Patent #
US 9,021,127 B2
Filed 03/14/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Mobile network reporting and usage analytics system and method aggregated using a distributed traffic optimization system | ||
Patent #
US 9,021,021 B2
Filed 12/10/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Request routing utilizing client location information | ||
Patent #
US 9,021,129 B2
Filed 06/03/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing using network computing components | ||
Patent #
US 9,021,128 B2
Filed 05/17/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Content delivery reconciliation | ||
Patent #
US 9,026,616 B2
Filed 05/17/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Mobile network traffic coordination across multiple applications | ||
Patent #
US 9,043,433 B2
Filed 05/25/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Intelligent rendering of information in a limited display environment | ||
Patent #
US 9,047,142 B2
Filed 12/16/2010
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Mobile network traffic coordination across multiple applications | ||
Patent #
US 9,049,179 B2
Filed 01/20/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Location-based operations and messaging | ||
Patent #
US 9,055,102 B2
Filed 08/02/2010
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Selective data compression by a distributed traffic management system to reduce mobile data traffic and signaling traffic | ||
Patent #
US 9,060,032 B2
Filed 05/09/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Pre-fetching map data based on a tile budget | ||
Patent #
US 9,063,951 B1
Filed 11/16/2011
|
Current Assignee
Google Inc.
|
Original Assignee
Google Inc.
|
Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network | ||
Patent #
US 9,065,765 B2
Filed 10/08/2013
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks Inc
|
Distributed implementation of dynamic wireless traffic policy | ||
Patent #
US 9,077,630 B2
Filed 07/08/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Managing request routing information utilizing performance information | ||
Patent #
US 9,083,743 B1
Filed 06/20/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Translation of resource identifiers using popularity information upon client request | ||
Patent #
US 9,083,675 B2
Filed 06/04/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Device resources sharing for network resource conservation | ||
Patent #
US 9,084,105 B2
Filed 04/19/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Mobile network background traffic data management | ||
Patent #
US 9,100,873 B2
Filed 09/14/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Request routing management based on network components | ||
Patent #
US 9,106,701 B2
Filed 11/04/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Protecting user identity at a cloud using a distributed user identity system | ||
Patent #
US 9,104,858 B1
Filed 05/03/2012
|
Current Assignee
CA Inc. dba CA Technologies
|
Original Assignee
Symantec Corporation
|
Pre-fetching map tile data along a route | ||
Patent #
US 9,111,397 B2
Filed 06/24/2014
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Managing secure content in a content delivery network | ||
Patent #
US 9,130,756 B2
Filed 03/11/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Movable storage | ||
Patent #
US 9,129,217 B2
Filed 02/19/2014
|
Current Assignee
Comcast Cable Communications LLC
|
Original Assignee
Comcast Cable Communications LLC
|
Managing cache to prevent overloading of a wireless network due to user activity | ||
Patent #
US 9,131,397 B2
Filed 06/06/2013
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Automated profiling of resource usage | ||
Patent #
US 9,135,048 B2
Filed 09/20/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Processing DNS queries to identify pre-processing information | ||
Patent #
US 9,154,551 B1
Filed 06/11/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Optimized and selective management of policy deployment to mobile clients in a congested network to prevent further aggravation of network congestion | ||
Patent #
US 9,161,258 B2
Filed 03/15/2013
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks LLC
|
Request routing management based on network components | ||
Patent #
US 9,160,703 B2
Filed 12/10/2014
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing request routing information utilizing performance information | ||
Patent #
US 9,172,674 B1
Filed 06/20/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol | ||
Patent #
US 9,173,128 B2
Filed 03/06/2013
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Managing resources using resource expiration data | ||
Patent #
US 9,176,894 B2
Filed 07/14/2014
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Latency measurement in resource requests | ||
Patent #
US 9,185,012 B2
Filed 11/21/2014
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing using a popularity identifier at a DNS nameserver | ||
Patent #
US 9,191,458 B2
Filed 06/05/2014
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing in a networked environment | ||
Patent #
US 9,191,338 B2
Filed 08/25/2014
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Method and apparatus for pre-fetching remote resources for subsequent display on a mobile computing device | ||
Patent #
US 9,197,713 B2
Filed 12/09/2011
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Dynamic categorization of applications for network access in a mobile network | ||
Patent #
US 9,203,864 B2
Filed 02/04/2013
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks LLC
|
Mobile device having content caching mechanisms integrated with a network operator for traffic alleviation in a wireless network and methods therefor | ||
Patent #
US 9,208,123 B2
Filed 12/07/2012
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks LLC
|
Client side cache management | ||
Patent #
US 9,210,235 B2
Filed 08/28/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Cache optimization | ||
Patent #
US 9,208,097 B2
Filed 11/12/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Techniques for populating a content stream on a mobile device | ||
Patent #
US 9,225,522 B2
Filed 12/27/2013
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
LinkedIn Corporation
|
Managing resources in resource cache components | ||
Patent #
US 9,237,114 B2
Filed 03/14/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Mobile device with application or context aware fast dormancy | ||
Patent #
US 9,241,314 B2
Filed 03/15/2013
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks LLC
|
Automatic generation and distribution of policy information regarding malicious mobile traffic in a wireless network | ||
Patent #
US 9,239,800 B2
Filed 07/11/2012
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks LLC
|
Map tile data pre-fetching based on mobile device generated event analysis | ||
Patent #
US 9,245,046 B2
Filed 06/24/2014
|
Current Assignee
Google Inc.
|
Original Assignee
Google Inc.
|
Forward-based resource delivery network management techniques | ||
Patent #
US 9,246,776 B2
Filed 03/10/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Extending user relationships | ||
Patent #
US 9,251,193 B2
Filed 10/28/2007
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Managing content delivery network service providers | ||
Patent #
US 9,251,112 B2
Filed 08/26/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Latency measurement in resource requests | ||
Patent #
US 9,253,065 B2
Filed 11/21/2014
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Application or context aware fast dormancy | ||
Patent #
US 9,271,238 B2
Filed 03/15/2013
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks LLC
|
Request and response characteristics based adaptation of distributed caching in a mobile network | ||
Patent #
US 9,275,163 B2
Filed 10/17/2011
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Method and apparatus for pre-fetching place page data based upon analysis of user activities | ||
Patent #
US 9,275,374 B1
Filed 11/15/2011
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol | ||
Patent #
US 9,277,443 B2
Filed 12/07/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Processing encoded content | ||
Patent #
US 9,288,153 B2
Filed 06/13/2014
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing network computing components utilizing request routing | ||
Patent #
US 9,294,391 B1
Filed 06/04/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
System and method for a mobile device to use physical storage of another device for caching | ||
Patent #
US 9,300,719 B2
Filed 01/14/2013
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks Inc
|
Method and apparatus for pre-fetching place page data for subsequent display on a mobile computing device | ||
Patent #
US 9,305,107 B2
Filed 12/08/2011
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Dynamically determining a tile budget when pre-fetching data in a client device | ||
Patent #
US 9,307,045 B2
Filed 11/10/2014
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Systems and methods for application management of mobile device radio state promotion and demotion | ||
Patent #
US 9,307,493 B2
Filed 03/15/2013
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
System and method for reduction of mobile network traffic used for domain name system (DNS) queries | ||
Patent #
US 9,325,662 B2
Filed 01/09/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Automated profiling of resource usage | ||
Patent #
US 9,323,577 B2
Filed 09/20/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
User as an end point for profiling and optimizing the delivery of content and data in a wireless network | ||
Patent #
US 9,326,189 B2
Filed 02/04/2013
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks LLC
|
Locality based content distribution | ||
Patent #
US 9,332,078 B2
Filed 03/05/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Wireless traffic management system cache optimization using http headers | ||
Patent #
US 9,330,196 B2
Filed 06/14/2012
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks LLC
|
Prefetching and caching map data based on mobile network coverage | ||
Patent #
US 9,332,387 B2
Filed 05/02/2012
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Apparatus and method for context-aware mobile data management | ||
Patent #
US 9,392,073 B2
Filed 06/03/2014
|
Current Assignee
Howard University
|
Original Assignee
Howard University
|
Method of pre-fetching map data for rendering and offline routing | ||
Patent #
US 9,389,088 B2
Filed 07/11/2012
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Request routing processing | ||
Patent #
US 9,391,949 B1
Filed 12/03/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Content management | ||
Patent #
US 9,407,699 B2
Filed 01/27/2014
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Mobile application traffic optimization | ||
Patent #
US 9,407,713 B2
Filed 01/16/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Latency measurement in resource requests | ||
Patent #
US 9,407,681 B1
Filed 09/28/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Selective data compression by a distributed traffic management system to reduce mobile data traffic and signaling traffic | ||
Patent #
US 9,432,486 B2
Filed 05/16/2015
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Service provider registration by a content broker | ||
Patent #
US 9,444,759 B2
Filed 08/12/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing CDN registration by a storage provider | ||
Patent #
US 9,451,046 B2
Filed 07/22/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Smart loading of map tiles | ||
Patent #
US 9,453,734 B2
Filed 12/05/2012
|
Current Assignee
Apple Inc.
|
Original Assignee
Apple Inc.
|
System and method for providing a network service in a distributed fashion to a mobile device | ||
Patent #
US 9,473,914 B2
Filed 12/28/2014
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Apparatus and Method for Context-Aware Mobile Data Management | ||
Patent #
US 20160308996A1
Filed 06/22/2016
|
Current Assignee
Howard University
|
Original Assignee
Howard University
|
Processing of DNS queries | ||
Patent #
US 9,479,476 B2
Filed 03/13/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
ENABLING EFFICIENT PRE-LOADING OF DATA FOR A NETWORK CLIENT | ||
Patent #
US 20160323410A1
Filed 03/19/2014
|
Current Assignee
Telefonaktiebolaget LM Ericsson
|
Original Assignee
Telefonaktiebolaget LM Ericsson
|
Method and apparatus for pre-fetching remote resources for subsequent display on a mobile computing device | ||
Patent #
US 9,491,255 B2
Filed 11/23/2015
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Content distribution network | ||
Patent #
US 9,495,338 B1
Filed 01/28/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Point of presence management in request routing | ||
Patent #
US 9,497,259 B1
Filed 09/15/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing content delivery network service providers | ||
Patent #
US 9,515,949 B2
Filed 10/24/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing utilizing point of presence load information | ||
Patent #
US 9,525,659 B1
Filed 09/04/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
System and method for proactive resource allocation | ||
Patent #
US 9,531,522 B2
Filed 09/28/2011
|
Current Assignee
Ohio State Innovation Foundation
|
Original Assignee
Hesham El Gamal, Atilla Eryilmaz, John Tadrous
|
PREDICTIVE CACHING FOR CONTENT | ||
Patent #
US 20160381168A1
Filed 09/07/2016
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Network resource identification | ||
Patent #
US 9,544,394 B2
Filed 11/19/2014
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Pre-fetching map tile data along a route | ||
Patent #
US 9,563,976 B2
Filed 08/17/2015
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Request routing based on class | ||
Patent #
US 9,571,389 B2
Filed 04/28/2014
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Role-based access control using dynamically shared cloud accounts | ||
Patent #
US 9,571,479 B1
Filed 03/31/2014
|
Current Assignee
CA Inc. dba CA Technologies
|
Original Assignee
Symantec Corporation
|
Pre-fetching map data using variable map tile radius | ||
Patent #
US 9,569,463 B1
Filed 03/17/2014
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Managing content delivery network service providers | ||
Patent #
US 9,590,946 B2
Filed 01/21/2016
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Online and distributed optimization framework for wireless analytics | ||
Patent #
US 9,603,033 B2
Filed 01/19/2012
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Request routing using network computing components | ||
Patent #
US 9,608,957 B2
Filed 04/09/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Locality based content distribution | ||
Patent #
US 9,621,660 B2
Filed 04/26/2016
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Online and distributed optimization framework for wireless analytics | ||
Patent #
US 9,622,091 B2
Filed 07/13/2012
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Moveable storage | ||
Patent #
US 9,626,626 B2
Filed 08/03/2015
|
Current Assignee
Comcast Cable Communications LLC
|
Original Assignee
Comcast Cable Communications LLC
|
Protecting user identity at a cloud using a distributed user identity system | ||
Patent #
US 9,628,471 B1
Filed 06/01/2015
|
Current Assignee
CA Inc. dba CA Technologies
|
Original Assignee
Symantec Corporation
|
Dynamic content delivery | ||
Patent #
US 9,628,554 B2
Filed 12/01/2014
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Method and System for Providing Contextual Electronic Content | ||
Patent #
US 20170116342A1
Filed 07/15/2015
|
Current Assignee
BigTinCan Holdings Limited
|
Original Assignee
BigTinCan Holdings Limited
|
Predictive network system and method | ||
Patent #
US 9,680,766 B2
Filed 09/28/2011
|
Current Assignee
Ohio State Innovation Foundation
|
Original Assignee
Ohio State Innovation Foundation, University of Southern California
|
Managing request routing information utilizing client identifiers | ||
Patent #
US 9,712,484 B1
Filed 09/28/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing secure content in a content delivery network | ||
Patent #
US 9,712,325 B2
Filed 07/15/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Mobile device configured for communicating with another mobile device associated with an associated user | ||
Patent #
US 9,712,986 B2
Filed 03/22/2012
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
PREEMPTIVE CONTENT DISTRIBUTION | ||
Patent #
US 20170230475A1
Filed 02/08/2016
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Request routing utilizing cost information | ||
Patent #
US 9,734,472 B2
Filed 05/19/2014
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Mitigating network attacks | ||
Patent #
US 9,742,795 B1
Filed 09/24/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Data services using location patterns and intelligent caching | ||
Patent #
US 9,749,804 B2
Filed 09/19/2014
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Controlling the pre-delivery of content to a mobile device | ||
Patent #
US 9,769,279 B2
Filed 03/23/2015
|
Current Assignee
Opanga Networks Inc.
|
Original Assignee
Opanga Networks Inc.
|
Mitigating network attacks | ||
Patent #
US 9,774,619 B1
Filed 09/24/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
PREDICTIVE NETWORK SYSTEM AND METHOD | ||
Patent #
US 20170279739A1
Filed 06/09/2017
|
Current Assignee
Ohio State Innovation Foundation
|
Original Assignee
Ohio State Innovation Foundation, University of Southern California
|
Managing content delivery network service providers | ||
Patent #
US 9,787,599 B2
Filed 12/05/2016
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Point of presence management in request routing | ||
Patent #
US 9,787,775 B1
Filed 09/15/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing in a networked environment | ||
Patent #
US 9,794,216 B2
Filed 09/30/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Identifying sources of network attacks | ||
Patent #
US 9,794,281 B1
Filed 09/24/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing management based on network components | ||
Patent #
US 9,800,539 B2
Filed 07/23/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Method and apparatus for pre-fetching place page data for subsequent display on a mobile computing device | ||
Patent #
US 9,813,521 B2
Filed 04/04/2016
|
Current Assignee
Google LLC
|
Original Assignee
Google Inc.
|
Traffic surge management for points of presence | ||
Patent #
US 9,819,567 B1
Filed 03/30/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Operation modes for mobile traffic optimization and concurrent management of optimized and non-optimized traffic | ||
Patent #
US 9,832,095 B2
Filed 12/14/2012
|
Current Assignee
Seven Networks LLC
|
Original Assignee
Seven Networks LLC
|
Routing based request correlation | ||
Patent #
US 9,832,141 B1
Filed 05/13/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Techniques for populating a content stream on a mobile device | ||
Patent #
US 9,877,156 B2
Filed 01/14/2015
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Technology Licensing LLC
|
Traffic surge management for points of presence | ||
Patent #
US 9,887,932 B1
Filed 03/30/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing based on class | ||
Patent #
US 9,887,915 B2
Filed 01/17/2017
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Traffic surge management for points of presence | ||
Patent #
US 9,887,931 B1
Filed 03/30/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Client side cache management | ||
Patent #
US 9,888,089 B2
Filed 12/07/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Locality based content distribution | ||
Patent #
US 9,894,168 B2
Filed 04/10/2017
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Forward-based resource delivery network management techniques | ||
Patent #
US 9,893,957 B2
Filed 01/13/2016
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Apparatus and method for context-aware mobile data management | ||
Patent #
US 9,900,398 B2
Filed 06/22/2016
|
Current Assignee
Howard University
|
Original Assignee
Howard University
|
Latency measurement in resource requests | ||
Patent #
US 9,912,740 B2
Filed 06/23/2016
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing network computing components utilizing request routing | ||
Patent #
US 9,929,959 B2
Filed 03/21/2016
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing processing | ||
Patent #
US 9,930,131 B2
Filed 02/23/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Online and distributed optimization framework for wireless analytics | ||
Patent #
US 9,949,149 B2
Filed 01/17/2017
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Content delivery reconciliation | ||
Patent #
US 9,954,934 B2
Filed 04/22/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing content delivery network service providers by a content broker | ||
Patent #
US 9,985,927 B2
Filed 07/21/2014
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
External health checking of virtual private cloud network environments | ||
Patent #
US 9,992,086 B1
Filed 08/23/2016
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing utilizing client location information | ||
Patent #
US 9,992,303 B2
Filed 02/25/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Point of presence management in request routing | ||
Patent #
US 10,015,237 B2
Filed 02/23/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Automated profiling of resource usage | ||
Patent #
US 10,015,241 B2
Filed 04/25/2016
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Local resource delivery network | ||
Patent #
US 10,021,179 B1
Filed 02/21/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Updating routing information based on client location | ||
Patent #
US 10,027,582 B2
Filed 03/30/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Adaptive resolution of domain name requests in virtual private cloud network environments | ||
Patent #
US 10,033,691 B1
Filed 08/24/2016
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Routing mode and point-of-presence selection service | ||
Patent #
US 10,033,627 B1
Filed 12/18/2014
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Reserved cache space in content delivery networks | ||
Patent #
US 10,049,051 B1
Filed 12/11/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Uninterrupted playback of video streams using lower quality cached files | ||
Patent #
US 10,070,163 B2
Filed 10/17/2017
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request management for hierarchical cache | ||
Patent #
US 10,075,551 B1
Filed 06/06/2016
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Latency measurement in resource requests | ||
Patent #
US 10,079,742 B1
Filed 09/15/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Routing mode and point-of-presence selection service | ||
Patent #
US 10,091,096 B1
Filed 12/18/2014
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Routing mode and point-of-presence selection service | ||
Patent #
US 10,097,448 B1
Filed 12/18/2014
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Point of presence management in request routing | ||
Patent #
US 10,097,398 B1
Filed 09/28/2010
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Identifying targets of network attacks | ||
Patent #
US 10,097,566 B1
Filed 07/31/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Adaptive transfer rate for retrieving content from a server | ||
Patent #
US 10,110,694 B1
Filed 06/29/2016
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing content delivery network service providers | ||
Patent #
US 10,116,584 B2
Filed 08/21/2017
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing secure content in a content delivery network | ||
Patent #
US 10,135,620 B2
Filed 05/17/2017
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Cache optimization | ||
Patent #
US 10,157,135 B2
Filed 10/19/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Locality based content distribution | ||
Patent #
US 10,158,729 B2
Filed 02/08/2018
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Cloud-based content management system | ||
Patent #
US 10,164,896 B2
Filed 03/06/2013
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
System and method for efficient use of network bandwidth based on user profiles and other data | ||
Patent #
US 10,178,580 B2
Filed 08/14/2013
|
Current Assignee
Ohio State Innovation Foundation
|
Original Assignee
Ohio State Innovation Foundation
|
Routing based request correlation | ||
Patent #
US 10,180,993 B2
Filed 10/19/2017
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Predictive network system and method | ||
Patent #
US 10,187,327 B2
Filed 06/09/2017
|
Current Assignee
Ohio State Innovation Foundation
|
Original Assignee
Ohio State Innovation Foundation
|
Mitigating network attacks | ||
Patent #
US 10,200,402 B2
Filed 09/25/2017
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Source-dependent address resolution | ||
Patent #
US 10,205,698 B1
Filed 11/26/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Forward-based resource delivery network management techniques | ||
Patent #
US 10,218,584 B2
Filed 12/15/2017
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Point of presence based data uploading | ||
Patent #
US 10,225,326 B1
Filed 03/23/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Point of presence management in request routing | ||
Patent #
US 10,225,322 B2
Filed 06/17/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Processing DNS queries to identify pre-processing information | ||
Patent #
US 10,225,362 B2
Filed 07/15/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Translation of resource identifiers using popularity information upon client request | ||
Patent #
US 10,230,819 B2
Filed 02/24/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Preemptive content distribution | ||
Patent #
US 10,257,305 B2
Filed 02/08/2016
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Reserved cache space in content delivery networks | ||
Patent #
US 10,257,307 B1
Filed 12/11/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Cloud-based content management system | ||
Patent #
US 10,257,109 B2
Filed 01/18/2012
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Enhanced customer service for mobile carriers using real-time and historical mobile application and traffic or optimization data associated with mobile devices in a mobile network | ||
Patent #
US 10,263,899 B2
Filed 04/10/2013
|
Current Assignee
Seven Networks Inc
|
Original Assignee
Seven Networks LLC
|
Request routing using a popularity identifier to identify a cache component | ||
Patent #
US 10,264,062 B2
Filed 11/06/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Routing for origin-facing points of presence | ||
Patent #
US 10,270,878 B1
Filed 11/10/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing based on class | ||
Patent #
US 10,305,797 B2
Filed 02/05/2018
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Dynamic selection of security protocol | ||
Patent #
US 10,313,399 B2
Filed 12/28/2016
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Technology Licensing LLC
|
Enabling efficient pre-loading of data for a network client | ||
Patent #
US 10,313,472 B2
Filed 03/19/2014
|
Current Assignee
Telefonaktiebolaget LM Ericsson
|
Original Assignee
Telefonaktiebolaget LM Ericsson
|
Use of virtual endpoints to improve data transmission rates | ||
Patent #
US 10,348,639 B2
Filed 12/18/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Efficient region selection system for executing request-driven code | ||
Patent #
US 10,372,499 B1
Filed 12/27/2016
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing network computing components utilizing request routing | ||
Patent #
US 10,374,955 B2
Filed 03/26/2018
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Client-side predictive caching for content | ||
Patent #
US 10,389,838 B2
Filed 01/05/2017
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Moveable storage | ||
Patent #
US 10,430,720 B2
Filed 02/27/2017
|
Current Assignee
Comcast Cable Communications LLC
|
Original Assignee
Comcast Cable Communications LLC
|
Assignment of a POP to a DNS resolver based on volume of communications over a link between client devices and the POP | ||
Patent #
US 10,447,648 B2
Filed 06/19/2017
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Encrypted network addresses | ||
Patent #
US 10,469,513 B2
Filed 12/22/2016
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Traffic surge management for points of presence | ||
Patent #
US 10,469,355 B2
Filed 11/13/2017
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Adaptive resolution of domain name requests in virtual private cloud network environments | ||
Patent #
US 10,469,442 B2
Filed 07/23/2018
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing resources and entries in tracking information in resource cache components | ||
Patent #
US 10,491,534 B2
Filed 11/16/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Efficient serving of resources during server unavailability | ||
Patent #
US 10,503,613 B1
Filed 04/21/2017
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Digitally signed network address | ||
Patent #
US 10,505,961 B2
Filed 12/22/2016
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Content distribution network | ||
Patent #
US 10,506,029 B2
Filed 11/14/2016
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Network resource identification | ||
Patent #
US 10,511,567 B2
Filed 01/09/2017
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Segmented predictive caching for content | ||
Patent #
US 10,516,753 B2
Filed 02/18/2019
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
External health checking of virtual private cloud network environments | ||
Patent #
US 10,516,590 B2
Filed 05/31/2018
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing resources using resource expiration data | ||
Patent #
US 10,521,348 B2
Filed 11/02/2018
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request routing utilizing client location information | ||
Patent #
US 10,523,783 B2
Filed 05/30/2018
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Locality based content distribution | ||
Patent #
US 10,530,874 B2
Filed 12/17/2018
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Electronic device for performing operation corresponding to voice input | ||
Patent #
US 10,540,973 B2
Filed 05/30/2018
|
Current Assignee
Samsung Electronics Co. Ltd.
|
Original Assignee
Samsung Electronics Co. Ltd.
|
Automated profiling of resource usage | ||
Patent #
US 10,542,079 B2
Filed 06/27/2018
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Content management | ||
Patent #
US 10,554,748 B2
Filed 09/15/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Predictive caching for content | ||
Patent #
US 10,574,779 B2
Filed 09/07/2016
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Translation of resource identifiers using popularity information upon client request | ||
Patent #
US 10,574,787 B2
Filed 05/20/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Predictive content push-enabled content delivery network | ||
Patent #
US 10,592,578 B1
Filed 03/07/2018
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
DNS query processing based on application information | ||
Patent #
US 10,601,767 B2
Filed 08/22/2013
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Predictive network system and method | ||
Patent #
US 10,616,138 B2
Filed 01/18/2019
|
Current Assignee
Ohio State Innovation Foundation
|
Original Assignee
Ohio State Innovation Foundation
|
Selective routing of domain name system (DNS) requests | ||
Patent #
US 10,616,179 B1
Filed 06/25/2015
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Network addresses with encoded DNS-level information | ||
Patent #
US 10,616,250 B2
Filed 12/22/2016
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Context sensitive object management | ||
Patent #
US 10,623,408 B1
Filed 04/02/2012
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Source-dependent address resolution | ||
Patent #
US 10,645,056 B2
Filed 02/08/2019
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Content delivery reconciliation | ||
Patent #
US 10,645,149 B2
Filed 02/07/2018
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Request management for hierarchical cache | ||
Patent #
US 10,666,756 B2
Filed 09/10/2018
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
System and method for efficient use of network bandwidth based on user profiles and other data | ||
Patent #
US 10,681,585 B2
Filed 01/04/2019
|
Current Assignee
Ohio State Innovation Foundation
|
Original Assignee
Ohio State Innovation Foundation
|
Routing based request correlation | ||
Patent #
US 10,691,752 B2
Filed 12/26/2018
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Routing mode and point-of-presence selection service | ||
Patent #
US 10,728,133 B2
Filed 10/08/2018
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Uninterrupted playback of video streams using lower quality cached files | ||
Patent #
US 10,728,593 B2
Filed 08/01/2018
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Updating routing information based on client location | ||
Patent #
US 10,742,550 B2
Filed 06/26/2018
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Content management | ||
Patent #
US 10,771,552 B2
Filed 09/15/2012
|
Current Assignee
Christopher L. Scofield, David R. Richardson, Bradley E. Marshall, Amazon Technologies, Swaminathan Sivasubramanian
|
Original Assignee
Amazon Technologies
|
Latency measurement in resource requests | ||
Patent #
US 10,778,554 B2
Filed 09/17/2018
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing resources using resource expiration data | ||
Patent #
US 10,783,077 B2
Filed 08/02/2019
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Managing secure content in a content delivery network | ||
Patent #
US 10,785,037 B2
Filed 11/19/2018
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Intelligent dataset migration and delivery to mobile internet of things devices using fifth-generation networks | ||
Patent #
US 10,785,297 B2
Filed 10/23/2018
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Request routing based on class | ||
Patent #
US 10,797,995 B2
Filed 05/07/2019
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Context information processor, profile distribution unit and method for a communication network | ||
Patent #
US 10,798,019 B2
Filed 12/06/2018
|
Current Assignee
Huawei Technologies Co. Ltd.
|
Original Assignee
Huawei Technologies Co. Ltd.
|
Multi-region request-driven code execution system | ||
Patent #
US 10,831,549 B1
Filed 12/27/2016
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Resolution of domain name requests in heterogeneous network environments | ||
Patent #
US 10,862,852 B1
Filed 11/16/2018
|
Current Assignee
Amazon Technologies
|
Original Assignee
Amazon Technologies
|
Database management and synchronization across a peer-to-peer network | ||
Patent #
US 6,892,210 B1
Filed 12/31/2001
|
Current Assignee
Knapp Investment Company Limited
|
Original Assignee
Worldsync Inc.
|
Synchronizing databases | ||
Patent #
US 6,799,190 B1
Filed 04/11/2002
|
Current Assignee
Intellisync Corporation
|
Original Assignee
Intellisync Corporation
|
Cost-based optimization for content distribution using dynamic protocol selection and query resolution for cache server | ||
Patent #
US 6,542,964 B1
Filed 06/02/1999
|
Current Assignee
CA Inc. dba CA Technologies
|
Original Assignee
Blue Coat Systems Incorporated
|
Personalized network-based services | ||
Patent #
US 7,072,932 B1
Filed 08/26/1999
|
Current Assignee
Nokia of America Corporation
|
Original Assignee
Lucent Technologies Inc.
|
System and method for pushing information from a host system to a mobile data communication device | ||
Patent #
US 6,463,464 B1
Filed 03/17/2000
|
Current Assignee
Blackberry Limited
|
Original Assignee
Blackberry Limited
|
Method and apparatus for transmitting and receiving electronic mail based upon user availability | ||
Patent #
US 6,460,073 B1
Filed 07/13/1999
|
Current Assignee
NEC Corporation
|
Original Assignee
NEC Corporation
|
Dynamic cache replication in a internet environment through routers and servers utilizing a reverse tree generation | ||
Patent #
US 6,189,043 B1
Filed 06/09/1997
|
Current Assignee
ATT Inc.
|
Original Assignee
ATT Inc.
|
Method and system for increasing ease-of-use and bandwidth utilization in wireless devices | ||
Patent #
US 6,985,933 B1
Filed 05/30/2000
|
Current Assignee
Snap Inc.
|
Original Assignee
International Business Machines Corporation
|
Reliable data synchronization over unreliable networks | ||
Patent #
US 7,024,428 B1
Filed 07/31/2001
|
Current Assignee
Unwired Planet LLC
|
Original Assignee
Openwave Systems Incorporated
|
System and method for intelligent web content fetch and delivery of any whole and partial undelivered objects in ascending order of object size | ||
Patent #
US 6,854,018 B1
Filed 04/08/2000
|
Current Assignee
NEC Corporation
|
Original Assignee
NEC Corporation
|
Methods and systems for preemptive and predictive page caching for improved site navigation | ||
Patent #
US 6,871,218 B2
Filed 11/07/2001
|
Current Assignee
Oracle International Corporation
|
Original Assignee
Oracle International Corporation
|
System and method for dynamic profiling of users in one-to-one applications and for validating user rules | ||
Patent #
US 6,871,186 B1
Filed 11/13/1998
|
Current Assignee
Facebook Inc.
|
Original Assignee
New York University
|
Bionet method, system and personalized web content manager responsive to browser viewers' psychological preferences, behavioral responses and physiological stress indicators | ||
Patent #
US 6,904,408 B1
Filed 10/19/2000
|
Current Assignee
John Mccarthy, Eileen Mccarthy
|
Original Assignee
John Mccarthy, Eileen Mccarthy
|
Method and system for increasing ease-of-use and bandwidth utilization in wireless devices | ||
Patent #
US 6,968,380 B1
Filed 05/30/2000
|
Current Assignee
Time Warner Inc.
|
Original Assignee
International Business Machines Corporation
|
Method and apparatus for preserving changes to data | ||
Patent #
US 6,748,403 B1
Filed 01/13/2000
|
Current Assignee
Access Company Limited
|
Original Assignee
Palmsource Incorporated
|
Method and system for managing multiple database storage units | ||
Patent #
US 6,801,921 B2
Filed 07/17/2001
|
Current Assignee
Hitachi America Limited
|
Original Assignee
Hitachi America Limited
|
System and method for pushing information from a host system to a mobile data communication device | ||
Patent #
US 20030005066A1
Filed 07/29/2002
|
Current Assignee
Blackberry Limited
|
Original Assignee
Blackberry Limited
|
Method and apparatus for providing a flexible and scalable context service | ||
Patent #
US 20030018692A1
Filed 07/18/2002
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Information retrieval system including voice browser and data conversion server | ||
Patent #
US 20030125953A1
Filed 12/28/2001
|
Current Assignee
xAd Inc
|
Original Assignee
xAd Inc
|
Distributed synchronization of databases | ||
Patent #
US 20020049764A1
Filed 04/23/2001
|
Current Assignee
Intellisync Corporation
|
Original Assignee
PUMA TECHNOLOGY INC. DELAWARE CORPORATION
|
INFORMATION SYSTEM FOR MOBILE USERS | ||
Patent #
US 20020087655A1
Filed 05/14/1999
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Method and system for data management | ||
Patent #
US 20020107920A1
Filed 02/08/2001
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
Solid Information Technology
|
Generalized adaptive signal control method and system | ||
Patent #
US 20020116118A1
Filed 12/18/2000
|
Current Assignee
Exelis Incorporated
|
Original Assignee
ITT Manufacturing Enterprises Inc.
|
Method, apparatus and program for providing user-selected alerting signals in telecommunications devices | ||
Patent #
US 20020106074A1
Filed 02/05/2001
|
Current Assignee
Verizon Patent and Licensing Incorporated
|
Original Assignee
BBN Technologies
|
Automatic data update | ||
Patent #
US 20020133509A1
Filed 03/13/2001
|
Current Assignee
Agilent Technologies Incorporated
|
Original Assignee
Agilent Technologies Incorporated
|
Data base synchronizing system with at least two host databases and a remote database | ||
Patent #
US 6,466,951 B1
Filed 02/08/2000
|
Current Assignee
Optis Wireless Technology LLC
|
Original Assignee
Telefonaktiebolaget LM Ericsson
|
Global personalization engine | ||
Patent #
US 20020165967A1
Filed 05/02/2001
|
Current Assignee
LUTRIS TECHNOLOGIES INC.
|
Original Assignee
LUTRIS TECHNOLOGIES INC.
|
Distributed synchronization of databases | ||
Patent #
US 6,223,187 B1
Filed 11/30/1999
|
Current Assignee
Intellisync Corporation
|
Original Assignee
Puma Technology Inc.
|
Information processing system using information caching based on user activity | ||
Patent #
US 6,243,755 B1
Filed 07/15/1998
|
Current Assignee
Toshiba Corporation
|
Original Assignee
Toshiba Corporation
|
Using distributed history files in synchronizing databases | ||
Patent #
US 6,044,381 A
Filed 09/11/1997
|
Current Assignee
Intellisync Corporation
|
Original Assignee
Puma Technology Inc.
|
Method and apparatus for utility-directed prefetching of web pages into local cache using continual computation and user models | ||
Patent #
US 6,085,226 A
Filed 01/15/1998
|
Current Assignee
Microsoft Technology Licensing LLC
|
Original Assignee
Microsoft Corporation
|
Dictionary for encoding and retrieving hierarchical data processing information for a computer system | ||
Patent #
US 5,778,223 A
Filed 12/23/1996
|
Current Assignee
International Business Machines Corporation
|
Original Assignee
International Business Machines Corporation
|
Selective delivery of electronic messages in a multiple computer system based on context and environment of a user | ||
Patent #
US 5,493,692 A
Filed 12/03/1993
|
Current Assignee
UbiComm LLC
|
Original Assignee
Xerox Corporation
|
20 Claims
-
1. A method of maintaining data in an information network, comprising the steps of:
-
storing replicas of content data in two or more stores; and synchronizing the content data in each of the two or more stores, wherein timing of the synchronization process is a function of a user'"'"'s historical context information. - View Dependent Claims (2, 3, 4)
-
-
5. A method of pre-fetching and preparing content in an information processing system, the method comprising the steps of:
-
generating at least one content pre-fetching policy and at least one content preparation policy, wherein each of the policies are at least in part a function of context information associated with a user; pre-fetching content based on information contained within the at least one content pre-fetching policy; and preparing the pre-fetched content based on information contained within the at least one content preparation policy. - View Dependent Claims (6, 7, 8, 9, 10, 11, 12)
-
-
13. An apparatus for pre-fetching and preparing content in an information processing system, the apparatus comprising:
a processing device having a processor coupled to a memory, the processing device being operative for pre-fetching and preparing content and for generating pre-fetching and preparation policies. - View Dependent Claims (14, 15, 16, 17, 18)
-
19. An article of manufacture for maintaining data in an information network, the article of manufacture comprising a machine readable medium containing one or more programs which when executed implement the steps of:
-
storing replicas of content data in two or more stores; and synchronizing the content data in each of the two or more stores, wherein timing of the synchronization process is a function of a user'"'"'s historical context information.
-
-
20. An article of manufacture for pre-fetching and preparing content in an information processing system, the article of manufacture comprising a machine readable medium containing one or more programs which when executed implement the steps of:
-
generating at least one content pre-fetching policy and at least one content preparation policy, wherein each of the policies are at least in part a function of context information associated with a user; pre-fetching content based on information contained within the at least one content pre-fetching policy; and preparing the pre-fetched content based on information contained within the at least one content preparation policy.
-
1 Specification
This application is a divisional of U.S. application Ser. No. 10/112,206, filed on Mar. 29, 2006, the disclosure of which is incorporated by reference herein.
The present invention relates generally to an information processing system and, more particularly, to techniques for pre-fetching and preparing content.
Pervasive computing promises an environment in which people will be able to access any content, anywhere, at any time, and on any device. While pervasive computing offers several advantages, one of its shortcomings is that there may be increased access latency due to the extremely dynamic and variable nature of such an environment. In addition to the traditional problem of access latency due to network and server load, there are three additional factors that contribute to latency.
The first factor is device heterogeneity. That is, client devices have different form factors, modalities, and presentation formats. Due to this heterogeneity, it is necessary to have format transformation (or transcoding) capabilities in content delivery networks, especially for dynamically generated data. Such transcoding operations introduce latency that will be perceived by the user.
The second factor is network infrastructure. There are large variations in the physical characteristics of wireless channels which affect the performance perceived by the end user. This is due not only to the number of different such technologies available today but also to inherent properties of wireless channels such as multi-path fading problems, distance between client and base stations, and interference problems resulting from shared spectrum. A user'"'"'s experience of accessing services can change dramatically and is a function of the user'"'"'s location, the available link technologies and the number of active connections operating in the same frequency band.
The third factor is user context. Services that are available to the user may change as a function of time and as a function of the user'"'"'s context. For example, services accessed in a professional environment may be different from the services accessed in a home environment. In such a situation, discovering the appropriate services at each location and binding them (i.e., interconnecting the services to each other and to other application components) introduces additional latency.
Traditional caching schemes used on proxy servers or edge servers are not sufficient to reduce access latency in pervasive environments due, primarily, to two main reasons. First, content and applications are increasingly personalized to suit the tasks and tastes of individual users. Thus, content cached for one user is often unsuitable for other users. Second, increased user mobility potentially reduces access locality, thus reducing the effectiveness of caching.
Traditional caching schemes used on client devices are also not sufficient in pervasive environments. First, mobile and task-specialized devices may be resource constrained and thus may not be able to support a sufficiently large caching storage area. Second, many pervasive applications are context specific. For example, the content delivered to the device might be specific to the geographic location of the device. Thus, content cached for one location may not be suitable in other locations.
U.S. Pat. No. 5,493,692, entitled “Selective Delivery of Electronic Messages in a Multiple Computer System Based on Context and Environment of a User,” to Theimer et al. (hereinafter referred to as the '"'"'692 patent), which is hereby incorporated by reference herein, discloses a method for selectively delivering electronic messages to an identified user or users in a system of mobile and fixed devices, based on the context of the system and the environment of the identified user. However, the '"'"'692 patent does not include context information that includes historical information and future plans. Additionally, although the '"'"'692 patent uses current context information to deliver electronic messages, the '"'"'692 patent does not use context information to pre-distribute and pre-process all kinds of content, as well as to manage replication among multiple copies of content.
Pre-fetching based on hyperlinks (and more generally, application structure) has been studied and applied extensively. For example, a paper entitled “Pre-fetching Hyperlinks” by Dan Duchamp teaches a method for pre-fetching web pages into a client cache. This work makes predictions based on document content only, and does not make use of any other forms of context information. It also does not address the issues of preparation or replication management.
U.S. Pat. No. 6,243,755, entitled “Information Processing System Using Information Caching Based on User Activity,” to Takagi et al. (hereinafter referred to as the '"'"'755 patent), which is hereby incorporated by reference herein, discloses a system and method to predict the information that will be required in the future by individual users using computing devices and the time at which this information will be required, based upon knowledge of the users'"'"' activity schedule. The prediction is used to transfer the necessary information to the computing device at the necessary time via a network. However, the '"'"'755 patent does not teach either management of the replicated copies of content created due to pre-fetching, or preparation of content such as via binding and transcoding ahead of time.
It is therefore apparent that a need exists for improved techniques which avoid the problems associated with the conventional approaches.
The present invention is directed to techniques for processing content in a network wherein the content is prefetched and prepared for easy and efficient access by a user. The content is prefetched and prepared in accordance with context information of the user.
In one aspect of the invention, a method of processing content in a network is provided, wherein the method includes the steps of predicting a device used by a user to access content residing in the network, wherein the prediction of the device is at least in part a function of context information associated with the user; and processing the content for access by the user via the predicted device. The processing step includes the step of transcoding the content into a predetermined format such that the format is compatible with the predicted device.
In another aspect of the invention, a method of processing content in a network includes the steps of (1) predicting at least one content item to be requested by a user, wherein the prediction of the content item is at least in part a function of context information associated with the user, and (2) pre-processing the content item for access by the user. Additionally, the method includes the steps of pre-fetching the content item and transferring the content item to at least one replica store wherein the content item is held pending a request by the user.
In another aspect of the invention, a method of maintaining data in an information network, includes the steps of (1) storing replicas of content data in two or more replica stores wherein timing of the synchronization process is a function of a user'"'"'s historical context information.
In yet another aspect of the present invention, a method of pre-fetching and preparing content in an information processing system is provided. The method includes the steps of generating at least one content pre-fetching policy and at least one content preparation policy, wherein each of the policies are at least in part a function of context information associated with a user. The content is pre-fetched based on information contained within the at least one content pre-fetching policy. Once the content has been pre-fetched, it is prepared based on information contained within the at least one content preparation policy. The context information associated with the user includes at least one of the user'"'"'s usage patterns, current location, future plans and preferences.
The present invention increases responsiveness of access to pervasive applications by (1) predicting the future information access needs (including the device of access) of users by using context information, such as (but not limited to) the users'"'"' usage patterns, current location, and future plans, as well as their preferences, and (2) by using this prediction to pre-distribute the right content in the right form at the right time to the right locations, and to manage it appropriately.
For a better understanding of the invention, reference is made to the following description of exemplary embodiments thereof, and to the accompanying drawings, wherein:
It is to be appreciated that the term “data” as used herein is not limited to any particular format. For instance, “data” may include text, images, video, audio, etc. Also, the term “processor” as used herein is intended to include any processing device, such as, for example, one that includes a CPU (central processing unit). The term “memory” as used herein is intended to include memory associated with a processor or CPU, such as, for example, RAM, ROM, a fixed memory device (e.g., hard drive), a removable memory device (e.g., diskette), etc. In addition, the term “input/output devices” or “I/O devices” as used herein is intended to include, for example, one or more input devices, such as a keyboard for inputting data to the processing unit, and/or one or more output devices, such as a CRT display and/or printer, for providing results associated with the processing unit. It is also to be understood that various elements associated with a processor may be shared by other processors. Accordingly, software components including instructions or code for performing the methodologies of the invention, as described herein, may be stored in one or more of the associated memory devices (e.g., ROM, fixed or removable memory) and, when ready to be utilized, loaded in part or in whole (e.g., into RAM) and executed by a CPU.
It is also to be appreciated that the following terms, as used herein, are intended to have the following definitions. The term “content” refers to static and dynamic data, applications, multimedia, code, or anything that can be delivered electronically. The act of “binding” refers to interconnecting application components such as service components (e.g., Web services or Enterprise JavaBeans) and presentation components (e.g., servlets or Java Server Pages) together to form an entire workable application. A “client device” is a computational device, which is used by an end user, such as but not limited to a cellular phone, a personal digital assistant (PDA), a personal computer (PC), a Kiosk, a television or a vehicle. A “content group” is a unit of pre-fetching or fetching from the server. The content group may contain multiple content items or items that have not been accessed. A “content item” is a particular piece of content accessed by a user.
“Content preparation” includes, for example, transcoding and binding. A “content server” is a computational device for storing, managing, and distributing content, such as but not limited to a file server, an application server, a database server, or a web server. The content server includes the software residing thereon. The term “context” refers to the physical and virtual environment in which a computation task occurs. “Context attributes” include aspects of a context. An “edge server” is defined as a computational device and its software which are placed near the client devices in the network. The purpose of an edge server is to increase performance and availability. More specifically, an edge server is an intermediary node intended to increase performance, scalability, and availability by caching, load sharing, and pre-fetching. An edge server typically has a large amount of storage within which to cache content.
“Future context” refers to anticipated context based upon user input rather than derived from past historical context. “Historical context” refers to a record of past context, both physical and virtual. “Persistent context” refers to a pattern observed in the historical context. The term “pre-fetching” refers to the act of fetching (pulling) as well as of pushing content ahead of demand. A “replica store” is a functional unit that maintains synchronized copies of content, and serves that content to clients. “Replicas” are read/write copies of content. “Replication management” refers to the acts of creation, synchronization, and garbage collection. “Transcoding” is the act of transforming data from one format to another. Often, the transformation transforms the data into a format which is usable by a particular device. “Transient context” refers to current or recent context. A “user agent” is software through which a user interacts with the system. This software commonly resides on the client device. The user agent may change as the user moves location or changes devices.
“Pre-fetching” includes techniques that move content close to a user'"'"'s device before the content is accessed. “Preparation” includes techniques that process the content (e.g., transcoding or binding) before the content is accessed. Both pre-fetching and preparation of content can be broken down into three steps: (1) prediction based on the general notion of user context, including all forms of past and present behavior, and future plans, as well as environment, to predict the future behavior of a user, (2) the action itself (i.e., pre-fetching and/or preparation), and (3) replication management (i.e., management of the life cycle of multiple copies of content, including creation, consistency management, and deletion). “Context-based prediction” includes techniques which are described above in step (1). “Replication management” includes techniques which are described above in step (3).
The techniques for content preparation (e.g., transcoding and binding) differ significantly from those for pre-fetching. For example, in order to pre-transcode content, the device type used to access particular content must be predicted. Second, in order to pre-bind the components of applications, the relationships among application components must be tracked. Due to these differences, conventional pre-fetching cannot be easily applied or extended to support content preparation.
For example, the processor 110 may represent a microprocessor, central processing unit (CPU), digital signal processor (DSP), or application-specific integrated circuit (ASIC), as well as portions or combinations of these and other processing devices. The memory 120 is typically an electronic memory, but may comprise or include other types of storage devices, such as disk-based optical or magnetic memory. The control device 140 may be associated with the processor 110. The control device 140 may be further configured to transmit control signals.
The techniques of the present invention described herein may be implemented in whole or in part using software stored and executed using the respective memory and processor elements of the processing device 100. For example, the techniques may be implemented at least in part using one or more software programs stored in memory 120 and executed by processor 110. The particular manner in which such software programs may be stored and executed in device elements such as memory 120 and processor 110 is well understood in the art and therefore not described in detail herein.
It should be noted that the processing device 100 may include other elements not shown, or other types and arrangements of elements capable of providing the function of the present invention described herein.
An architectural overview of a system for content pre-fetching and preparation in accordance with the present invention is shown in
To pre-fetch and prepare the content based on policy information, a preferred embodiment uses two sets of functional units. The first set of functional units is used for pre-fetching and preparing content using the policy table 375, and includes content selection and synchronization 300, content preparation 305, replica store 310 and user agent 315. The second set is used to generate pre-fetching and preparation policies to populate the policy table 375, and includes access monitor 320, access record table 325, context collector 330, context history 335, context correlator 340, context miner 345, access pattern 350, persistent context 355, user preferences 360, device profiles 365, policy generator 370, policies 375, and content groups 380. The policies table 375, which is described in more detail below with reference to
Content is stored on and managed by content server 303 running on content host 205. Content server 303 receives content requests either from user agent 315, possibly through replica store 310, or from content selection and synchronization unit 300, which is described below with reference to
In a preferred embodiment, requests for content are sent to one or more content servers 303 by the content selection and synchronization unit 300. As its name implies, the content selection and synchronization unit 300 performs two functions: content selection—which is described with reference to
Policies table 375 comprises three major types of policies, i.e., content group definitions, pre-fetching policies and preparation policies. Content group definitions specify groups of content that are of interest to a particular user. In a preferred embodiment, content group definitions are entered in the system by an administrator or user. It is contemplated that content group definitions could be generated automatically by, for example, data mining techniques. Pre-fetching policies are utilized to inform the content selection and synchronization unit 300 that a set of content groups is to be pre-fetched and maintained at a set of replica stores 310. Pre-fetching policies trigger requests for content to be forwarded from the content servers 303 to the content selection and preparation unit 300. The content received by the content selection and preparation unit 300 is then forwarded to the content preparation unit 305. The preparation policies provide preparation instructions to the content preparation unit 305. Typical preparation instructions include transcoding directives assisting the preparation of content in a desired format. The preparation instructions may also instruct the content preparation unit 305 to bind services that will be needed to serve requests.
When the content selection and synchronization unit 300 receives content from content servers 303 as a result of a pre-fetching policy, the received content is forwarded to the content preparation unit 305, together with preparation policies. After the content is prepared in content preparation unit 305, the prepared content is transferred to replica stores 310. The role of a replica store 310 is to hold prepared content in anticipation of client requests. If a client requests a piece of content that has already been pre-fetched and is currently held in the replica store 310, the request is served from the cache of the replica store 310. If the desired content has not been pre-fetched, the replica store 310 forwards the request to the correct content server 303, on behalf of the user. A user agent 315, such as a Web browser, is typically employed to facilitate the interaction between a replica store and a user.
The generation of policies commences with the access monitor 320. All of a user'"'"'s requests for content are intercepted by the access monitor 320 before being forwarded to replica store 310. Generally, the role of the access monitor 320 is to track information regarding client requests that take place in the replica store 310. Access monitor 320 is described in further detail below with reference to
User preferences are maintained in user preferences table 360. User preferences are typically provided directly by the users and contain information regarding the users'"'"' behavior, needs for specific content in a specific form, and when the users are in a specific context.
Device profiles are maintained in device profiles table 365. Device profiles table 365 includes information on the individual capabilities of the various client devices that may be utilized. A more detailed description of the device profiles table 365 is given below with reference to
The device profiles 365, user preferences 360, persistent context 355, content groups 380 and access pattern 350 tables contain all of the information that is necessary to generate all of the policies that are stored within policies table 375. The act of generating the policies is performed by policy generator 370 unit and the resulting policies are stored in policies table 375.
It is contemplated that there may be one or more of each of the units illustrated in
It is also contemplated that policies may be manually supplied by administrators or users.
One function of the content selection and synchronization unit 300 is that of content selection. The process of content selection is illustrated in
The active policies identified in step 405 are processed in steps 410 through 435. Step 410 selects the next active policy. In step 420, a determination is made as to where the content group associated with the policy should be placed in the network. In step 425, the replica descriptor of the content is stored in the SyncDB table 1900. SyncDB table 1900, illustrated in
The particular order of the steps illustrated in
It should be noted that the process described above with reference to
Content synchronization in the content selection and synchronization unit 300 is the process that maintains consistency between content replicas in replica store 310 and a master copy on the content server 303.
Once the total amount of content groups are determined in step 500, in step 505 the process determines whether additional unprocessed content groups exist. If additional unprocessed content groups do exist, in step 510 the next row in SyncDB 1900 to be processed is located. In step 515, a determination is made as to whether the content group identified by the content group identification column 1905 should still be kept in the remote replica store identified by the replica descriptor column 1910. This determination is made by checking whether the expiration time column 1915 contains a value greater than the current time. If the expiration time 1915 indicates that the content group is no longer needed, the copy of the content group in the replica store is invalidated in step 520 and the corresponding row in SyncDB 1900 is purged. Otherwise, the synchronization process proceeds to step 525. In step 525, the set of all content items currently belonging to the content group is determined. The difference between this current set and the set in the replica store 310 is then calculated by examining the replica descriptor column 1910. This process identifies content items that have been added, modified, or deleted. In step 530, the content items in the calculated difference are fetched from the content server, if necessary, and forwarded to the content preparation unit 305.
In the current embodiment of the present invention, content synchronization is triggered by content updates on the content server 303. In an alternative embodiment of the invention, content synchronization may be triggered by demand requests at a replica store 310. Further, in step 500, the set of rows in SyncDB 1900 that need to be processed consists of the rows that simultaneously satisfy the following two conditions. First, the content group identification column 1905 identifies a content group to which the demanded items belong. Second, the replica descriptor column 1910 identifies the replica store to which the demand requests were directed.
In another embodiment of the present invention, content synchronization is triggered by lapses of fixed time intervals. Further, in step 500, all of the rows in SyncDB 1900 need to be processed. Alternatively, it is contemplated that content synchronization may also be triggered by a combination of two or more of the above events.
Referring now to
In an alternative embodiment, the access monitor 320 could monitor the network associated with the replica store 310, thereby listening to requests intended for the replica store 310 and recording the necessary information. Such a process improves the latency of requests.
It is contemplated that the information stored in the request descriptor column 710 could be combined with the information stored in the requester descriptor column 705. Additionally, it is contemplated that the access monitor 320 could lookup the user'"'"'s current context and include this information in one or more columns in the access record table 325. This would ease the burden on the correlator 340.
In an exemplary embodiment, the present invention uses a scaleable secure context service as a context collector 330. It is to be appreciated that other types of context collectors may be utilized. For example, in the '"'"'314 application context is collected from context drivers and reported in response to queries. The present invention uses historical context which is recorded in a context history table 335 as illustrated
As shown in
The location context driver 840 includes three sources of location data: (1) a cellular source such as, for example, a cellular telephone system, (2) a wireless local area network (LAN) source such as, for example, an 802.11 network, and (3) a second wireless personal area network (PAN) source such as, for example, a Bluetooth network. It is contemplated that an additional source of location data could be acquired from a device enabled with a network and a global positioning system (GPS) unit. When a request for location context arrives, the location context driver 840 queries one or more context sources for the required location information. It is contemplated that the location context source could, alternatively, send or push location context information to the location context driver 840. As part of the location context, the location context driver also returns the identity of the device that was used to sense the location. The device identification information could be recorded in the source field 930 of the context history table 335, as illustrated in
With continued reference to
The instant messaging context driver 815 maintains information regarding a subscriber'"'"'s instant messaging status. For example, the instant messaging context driver 815 is configured to obtain instant messaging status information from America On-Line (AOL), Sametime or any other instant messaging type of program. Each of the context sources sends context information via a context push interface 845. It is also contemplated that programming associated with the context drivers could be written to permit the context drivers to query their respective context sources as needed.
The mediator 805 is configured to use the context recorder 830 to record context information in the context history table 335 just before returning the query. The SCS API 800 has been augmented to allow context information to be recorded in the context history table 335 only, but not returned to the requester. It is contemplated that the context history table 335 may be populated in other ways, for example, the context collector could be modified to record all context information available to it independent of any requests.
In accordance with an embodiment of the present invention, the context service is queried to obtain the desired context information. Context information can be static or dynamic information, and requests for context information may be one time requests, event driven, or continuous. In each of these cases the context information may be recorded. It is contemplated that one or more parts of the context collector 330 may be modified to use the context recorder 830. Recording the context information in the context collector 330 may affect the granularity of the information available in the context history table 335. Further, useful data can be lost if it is filtered out before being recorded in the history table. The present invention allows users to adjust the granularity of the context history through the augmented SCS API 800.
Another function of the mediator 805 is to direct simple requests to the appropriate context driver such as drivers 815, 820, 835, and 840. For example, a request for a subscriber'"'"'s location would be directed to the location context driver 840 and a request for a subscriber'"'"'s instant messaging context would be directed to the instant messaging context driver 815. Additionally, another function of the mediator 805 is to aggregate different types of context to more efficiently process more complex requests. For example, a request regarding whether a subscriber is actually attending a meeting that appears on his or her calendar could be serviced by the mediator 805. However, this request would require the use of more than one of the context drivers shown in the present architecture. For this example, the mediator 805 would need to query both the calendar context driver 820 and the location context driver 840 and then compare the location of the current meeting with the subscriber'"'"'s present location. If the two locations are the “same”, then the request might be answered in the affirmative; if not, then the request would be answered in the negative. However, defining the term “same” with regard to such a query is a complex issue with many solutions. For example, cellular tower A may cover an office which has GPS coordinates (X, Y, Z). If these two location values are reported by two separate sources, the system must recognize that these two different representations are not inconsistent. One possible way to resolve the issue is to require the requester to specify how close the locations must be to be considered the same. Additionally, the system may include information regarding the dimensions of rooms available to it so that when a request arrives that requires the system to determine if something is inside or outside a room (or any place) it is capable of doing so.
It is contemplated that the individual context sources could aggregate context data to produce a single view of one type of context data. For example, an 802.11 context aggregator could collect 802.11 data from many access points. The 802.11 context aggregator could then analyze that data to determine a single location estimate. Requests made to the 802.11 context aggregator would then result in a single location estimate, possibly with associated quality of information estimates. Similarly, in a push scenario, the single location information could be sent to the context driver or to a downstream aggregator.
It is further contemplated that another individual context source, from the context service'"'"'s perspective, could itself aggregate context data from multiple different sources to define a new type of context. Additionally, context aggregators could be arranged in a hierarchical fashion, arbitrarily allowing more complex context data to be created. Thus, an architecture could be designed to address factors such as scalability, quality of information, administrative control, and so forth.
The context type column 905 contains information regarding the type of context. Context information recorded from the context recorder 330 could contain location, calendar, or instant messaging information.
The context attributes column 910 contains actual context information such as the GPS coordinates or the fact that someone is on a business trip.
The duration column 915 contains information which indicates the length of time that the context event took or is scheduled to take.
The context event column 920 contains information which describes the event with additional specificity. For example, when combined with information from the calendar context driver 820, the event might be labeled as, for example, a meeting, a conference call, vacation, or travel. The location context driver 840 may provide information which will cause the event information in column 920 to be, for example, room 205, Atlanta, or Poughkeepsie. GPS context events could be labeled as GPS, followed by the coordinates.
The supplier column 925 contains information which indicates the owner of the source of the context data. The source column 930 contains information which indicates the origin of the data. For example, the supplier of context received via a cellular telephone could be Verizon Wireless or Sprint, and the source could be the cellular tower sensing the telephone and the telephone sensed. For some context types the source information 930 will include information regarding the device that generated the context source information. In another example, where the context type is identified as virtual context in column 905, and context event column 920 contains information which indicates that the context event is e-mail, the context source could be a laptop computer, Blackberry, a two way pager, or any other device where the context subject accesses e-mail. In a facility which is wired for tracking individuals, the source of meeting information could be the room where the collection of people were sensed.
The subject(s) column 935 contains information indicating the person, persons, object, or objects that the context event is reporting about.
It is contemplated that additional columns may be included to contain additional information that can assist in interpreting the context. For example, when the context type 905 is location information, the additional information may indicate whether the origin is a global positioning system (GPS), a cellular network, an 802.11 network, a local area network (LAN) or a Bluetooth network.
The correlator 340 takes information from an access record table 325 and a context history table 335 as input and generates an access pattern 350 for each combination of context attribute values. Examples of context attribute values include access location and access device information. Because user behavior may demonstrate different characteristics under different circumstances, the present invention models access patterns separately for different context attributes.
In a preferred embodiment of the present invention, access patterns are modeled at the level of content groups. It is contemplated that access patterns may also be modeled at the level of individual content items.
The process starts at step 1200. In step 1205, the init node 1100 is created if it is not yet present. In steps 1210 to 1245, the input access records are iterated through and the access pattern 350 is updated accordingly. In step 1210, a determination is made as to whether any additional unprocessed access records exist. If no additional unprocessed access records exist, the process is ended, as indicated by step 1215. If additional unprocessed access records do exist, in step 1220 the next access record to be processed is located. In step 1225, a content node 1105 for the content group identified in the access record is created, if necessary. In step 1230, the set of access records that precede the current access record and whose timestamp is within the relationship window of the current record'"'"'s timestamp is computed. In step 1235, a determination is made on whether the set computed in step 1230 is empty. If the set is empty, the process proceeds to step 1240. Otherwise, the process proceeds to step 1245. In step 1240, if there is no arc yet from the init node 1100 to the node for the current content group, an arc with a weight value equal to one is drawn. Otherwise, the weight value associated with the arc is increased by one. In step 1245, for each content group identified by an access record in the set, an arc is drawn from that content group to the current content with a weight of one if no arc exists; otherwise, the weight associated with the arc is increased by one. According to a preferred embodiment of the present invention, the time of access and the relationship window are represented in physical time. It is also contemplated that the time of access and the relationship window may also be represented in logical time.
Referring now to
Returning to the flowchart illustrated in
Generally, the next part of the algorithm reads the context history table 335 and updates the statistics for all previously identified events as well as identifying potential candidates for new events. This portion of the algorithm is performed in a loop. The tracking table, which resulted from the input parameters which were read as input in step 1310, contains those context events which might be of interest.
More specifically, in step 1315, the next entry of the context history table 355 is read and checked to determine whether it represents a new event pattern. If this context history entry represents a new event pattern, it is added to a tracking list in step 1320. A new context event indicator in this tracking list entry is marked so that it will remain in the tracking list long enough to collect enough observations to determine whether it represents persistent context or an event which should be tracked. As indicated in step 1315, if the current entry from the context history table 355 represents a previously existing event pattern, the parameters associated with this event are updated in step 1330. In step 1335, a determination is made as to whether all events were processed. If all events were not processed, the process begins again at step 1315. This loop is repeated until there are no more events in the context history table 335, at which point the process continues with step 1340 illustrated in
The part of the algorithm shown in
With continuing reference to
Returning to step 1345, if the event being examined is not above the persistence threshold, a determination is made, in step 1355, as to whether the event is above the tracking threshold. If the event is above the tracking threshold, the event is moved to the tracking table in step 1360, if the event is not already present in the tracking table. Note that for events in the active context table, step 1360 removes the event from the active context table. For events which are already in the tracking table, step 1360 has no effect. If the event being examined is not above the tracking threshold, in step 1385, a determination is made as to whether the event is considered new (i.e., has the new event time out expired). If the event is no longer considered new, it is moved into the archive table in step 1365. Step 1365 removes the item from either the active context table or the tracking table, as appropriate. Returning to step 1385, if the event is still considered new, the algorithm proceeds, in step 1370, to check whether there is another event to process. If there is an additional event, then the algorithm returns again to step 1345. If there are no additional events to process, in step 1375 the active context table is stored as the persistent context table 355, replacing the existing table, and the tracking table is stored. The process associated with the context miner 345 ends at step 1380.
It is contemplated that, in this embodiment, items that are moved from the active context table to the tracking table may be processed twice. The processing time associated with the steps described with reference to
Policies are generated by the policy generator 370.
Groups of context attributes are then extracted in step 1720 from the persistent context records. For example, a persistent context record might indicate that a given user is always in his or her office between 9:00 a.m. and 10:00 a.m., which could be used to pre-fetch content to their office device(s) or the replica store(s) serving the device(s). In this case, the location and time attribute are grouped together with respective values equal to “office” and “9:00 to 10:00 a.m.”. Another example of a persistent context record might indicate that a given user always uses his or her BlackBerry device when he or she visits a particular location. In this case, the context attributes predict the device that the user will probably use, based on his or her persistent context. It is contemplated that other context attributes, could be used by the context miner 345 to make such device or pre-fetching predictions.
The next step, 1725, is to get user preferences from the user preferences table 360. There are three types of user preferences: user-defined contextual preferences, user-defined pre-fetching policies and user-defined preparation policies. From user-defined contextual preferences, additional groups of context attributes are extracted in step 1730. The correlation between context attributes and access patterns is generated by the correlator 340 and stored in the access pattern table 350. The format of access pattern records is described above with reference to
The next step taken by the policy generator 370 is to simplify these graphs in step 1740 by removing vertices of the graph based on any applicable removal policy such as least recently used (LRU). Although there are several ways to simplify these graphs, in this preferred embodiment, the removal policy drops all of the vertices with a weight value which is less than a predetermined threshold weight value. Thus, the policy generator 370 triggers only the pre-fetching and preparation of popular content groups. The predetermined threshold weight value can be specified off-line, either by the user or by an administrator. Alternatively, the threshold weight value can be computed online, based on different network conditions. The threshold weight value serves to control the number of policies that the system generates. It is contemplated that other removal policy criteria may be utilized.
After simplifying the probability graphs in step 1740, the policy generator 370 reads device profiles in step 1745 from the device profiles 365 table. The policy generator 370 then merges the device profiles with user-defined content preparation policies and context attributes which predict the device used, to generate content preparation policies in step 1750. With the simplified graphs obtained in step 1740, the policy generator 370, in step 1755, also generates content pre-fetching policies and adds user-defined pre-fetching policies to a list of content pre-fetching policies. In step 1760, the policy generator then stores all of the policies generated in step 1750 and 1755 in the policies table 375. The policy generator then determines whether there are additional groups of context attributes to process, in step 1765. If the answer is yes, the policy generator generates the associated policies following steps 1735 to 1760. Once all groups of context attributes associated with a user have been processed, the system checks, in step 1770, to determine whether there are additional users to process. If the answer is yes, the policy generator repeats steps 1715 to 1765: the extraction of access patterns, user preferences and associated device profiles to generate policies for that user. If the answer to step 1770 is no, as indicated by step 1775, the policy generator ends its execution until the next scheduled time for the generation of new policies.
It is contemplated that the policies table may contain additional fields or may only contain a subset of the fields described above. It is further contemplated that the time range 1810 and/or the device types 1815 could be considered types of context and could be included in the other applicable contexts 1820 rather than considered separately as described above with reference to this preferred embodiment.
Although illustrative embodiments of the present invention have been described herein with reference to the accompanying drawings, it is to be understood that the invention is not limited to those precise embodiments, and that various other changes and modifications may be made by one skilled in the art without departing from the scope or spirit of the invention. All such changes and modifications are intended to be included within the scope of the invention as defined by the appended claims.