US20120110171A1 - Application and network-based long poll request detection and cacheability assessment therefor - Google Patents

Application and network-based long poll request detection and cacheability assessment therefor Download PDF

Info

Publication number
US20120110171A1
US20120110171A1 US13/274,248 US201113274248A US2012110171A1 US 20120110171 A1 US20120110171 A1 US 20120110171A1 US 201113274248 A US201113274248 A US 201113274248A US 2012110171 A1 US2012110171 A1 US 2012110171A1
Authority
US
United States
Prior art keywords
request
application
response
requests
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
US13/274,248
Other versions
US8166164B1 (en
Inventor
Michael Luna
Andrei Tsõmbaljuk
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Seven Networks Inc
Original Assignee
Seven Networks Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Seven Networks Inc filed Critical Seven Networks Inc
Priority to US13/274,248 priority Critical patent/US8166164B1/en
Assigned to SEVEN NETWORKS, INC. reassignment SEVEN NETWORKS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: TSOMBALJUK, ANDREI, LUNA, MICHAEL
Application granted granted Critical
Publication of US8166164B1 publication Critical patent/US8166164B1/en
Publication of US20120110171A1 publication Critical patent/US20120110171A1/en
Assigned to SEVEN NETWORKS, LLC reassignment SEVEN NETWORKS, LLC ENTITY CONVERSION Assignors: SEVEN NETWORKS, INC.
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61BDIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B3/00Apparatus for testing the eyes; Instruments for examining the eyes
    • A61B3/10Objective types, i.e. instruments for examining the eyes independent of the patients' perceptions or reactions
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61BDIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B3/00Apparatus for testing the eyes; Instruments for examining the eyes
    • A61B3/10Objective types, i.e. instruments for examining the eyes independent of the patients' perceptions or reactions
    • A61B3/1005Objective types, i.e. instruments for examining the eyes independent of the patients' perceptions or reactions for measuring distances inside the eye, e.g. thickness of the cornea
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61BDIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B5/00Measuring for diagnostic purposes; Identification of persons
    • A61B5/103Detecting, measuring or recording devices for testing the shape, pattern, colour, size or movement of the body or parts thereof, for diagnostic purposes
    • A61B5/107Measuring physical dimensions, e.g. size of the entire body or parts thereof
    • A61B5/1076Measuring physical dimensions, e.g. size of the entire body or parts thereof for measuring dimensions inside body cavities, e.g. using catheters
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61FFILTERS IMPLANTABLE INTO BLOOD VESSELS; PROSTHESES; DEVICES PROVIDING PATENCY TO, OR PREVENTING COLLAPSING OF, TUBULAR STRUCTURES OF THE BODY, e.g. STENTS; ORTHOPAEDIC, NURSING OR CONTRACEPTIVE DEVICES; FOMENTATION; TREATMENT OR PROTECTION OF EYES OR EARS; BANDAGES, DRESSINGS OR ABSORBENT PADS; FIRST-AID KITS
    • A61F2/00Filters implantable into blood vessels; Prostheses, i.e. artificial substitutes or replacements for parts of the body; Appliances for connecting them with the body; Devices providing patency to, or preventing collapsing of, tubular structures of the body, e.g. stents
    • A61F2/02Prostheses implantable into the body
    • A61F2/14Eye parts, e.g. lenses, corneal implants; Implanting instruments specially adapted therefor; Artificial eyes
    • A61F2/16Intraocular lenses
    • A61F2/1694Capsular bag spreaders therefor
    • GPHYSICS
    • G01MEASURING; TESTING
    • G01BMEASURING LENGTH, THICKNESS OR SIMILAR LINEAR DIMENSIONS; MEASURING ANGLES; MEASURING AREAS; MEASURING IRREGULARITIES OF SURFACES OR CONTOURS
    • G01B3/00Measuring instruments characterised by the use of mechanical techniques
    • G01B3/56Gauges for measuring angles or tapers, e.g. conical calipers
    • G01B3/563Protractors
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/12Avoiding congestion; Recovering from congestion
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60Network streaming of media packets
    • H04L65/61Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
    • H04L65/613Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for the control of the source by the destination
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/2866Architectures; Arrangements
    • H04L67/288Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/2866Architectures; Arrangements
    • H04L67/289Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/535Tracking the activity of the user
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/568Storing data temporarily at an intermediate stage, e.g. caching
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/568Storing data temporarily at an intermediate stage, e.g. caching
    • H04L67/5682Policies or rules for updating, deleting or replacing the stored data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/18Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61BDIAGNOSIS; SURGERY; IDENTIFICATION
    • A61B3/00Apparatus for testing the eyes; Instruments for examining the eyes
    • A61B3/10Objective types, i.e. instruments for examining the eyes independent of the patients' perceptions or reactions
    • A61B3/117Objective types, i.e. instruments for examining the eyes independent of the patients' perceptions or reactions for examining the anterior chamber or the anterior chamber angle, e.g. gonioscopes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/1045Proxies, e.g. for session initiation protocol [SIP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04Registration at HLR or HSS [Home Subscriber Server]

Definitions

  • 61/533,007 entitled “DISTRIBUTED CACHING IN A WIRELESS NETWORK OF CONTENT DELIVERED FOR A MOBILE APPLICATION OVER A LONG-HELD REQUEST”, which was filed on Sep. 9, 2011, and U.S. Provisional Patent Application No. 61/533,021 entitled “APPLICATION AND NETWORK-BASED LONG POLL REQUEST DETECTION AND CACHEABILITY ASSESSMENT THEREFOR”, which was filed on Sep. 9, 2011, the contents of which are all incorporated by reference herein.
  • the mobile application model has significantly changed consumption of content managed on the Internet.
  • joining social media and instant messaging applications increasingly popular mobile gaming applications such as Angry Birds
  • Angry Birds is just one example of the many available applications that constantly signal the mobile network for updates at hundreds and even thousands of times per hour.
  • traditional practices of providing all-you-can-eat data plans have become a thing of the past.
  • the data tsunami is affecting the mobile ecosystem as a whole, and end-users are feeling the brunt of the wrath as operators scramble to find the best solution.
  • the applications that contribute to mobile data consumption can further include, for example, push email, instant messaging, visual voicemail, voice and video telephony, and others which may require an always-on of frequent IP connections and frequent transmit of small bits of data. Further, these applications poll their host servers with varying polling characteristics, due to the nature of the application, user activity, and/or nature of data being exchanged. For example, one category of polling can be represented by a persistent IP connection, such as one established by long polling or COMET style push, which is a web application model where long-held request (e.g., long-held HTTP requests) allows server to push data to the client when this data becomes available.
  • long polling e.g., long-held HTTP requests
  • the persistent connection allows emulation of content push from server to client (e.g., mobile client). Specifically, when a response is not available when the request is sent, the server holds the request until information becomes available to be sent to the client. In general, the client immediately re-issues a request to the server, which the server then responds to or holds until a response is available.
  • client e.g., mobile client
  • This behavior of long polls or other types of persistent connections is different from other types of polling. Due to the different caching requirements of different types of polling, different classes of polling patterns, such as long poll patterns and characteristics need to be detected for effective caching and assessment of cacheability.
  • FIG. 1A illustrates an example diagram of a system where a host server facilitates management of traffic, content caching, and/or resource conservation between mobile devices (e.g., wireless devices) and an application server or content provider in a wireless network (or broadband network) for resource conservation.
  • a host server facilitates management of traffic, content caching, and/or resource conservation between mobile devices (e.g., wireless devices) and an application server or content provider in a wireless network (or broadband network) for resource conservation.
  • FIG. 1B illustrates an example diagram of a proxy and cache system distributed between the host server and device which facilitates network traffic management between a device and an application server/content provider for resource conservation and content caching.
  • FIG. 2A depicts a block diagram illustrating an example of client-side components in a distributed proxy and cache system residing on a mobile device (e.g., wireless device) that manages traffic in a wireless network (or broadband network) for resource conservation, content caching, and/or traffic management.
  • a mobile device e.g., wireless device
  • a wireless network or broadband network
  • FIG. 2B depicts a block diagram illustrating another example of components in the application behavior detector and the caching policy manager in the local proxy on the client-side of the distributed proxy system shown in the example of FIG. 2A .
  • FIG. 3A depicts a block diagram illustrating an example of server-side components in a distributed proxy and cache system that manages traffic in a wireless network (or broadband network) for resource conservation, content caching, and/or traffic management.
  • FIG. 3B depicts a block diagram illustrating another example of components in the caching policy manager in the proxy server on the server-side of the distributed proxy system shown in the example of FIG. 3A .
  • FIG. 4A depicts a timing diagram showing how data requests from a mobile device (e.g., any wireless device) to an application server/content provider in a wireless network (or broadband network) can be coordinated by a distributed proxy system in a manner such that network and battery resources are conserved through using content caching and monitoring performed by the distributed proxy system.
  • a mobile device e.g., any wireless device
  • an application server/content provider in a wireless network or broadband network
  • FIG. 4B depicts an interaction diagram showing how application polls having data requests from a mobile device (e.g., any wireless device) to an application server/content provider in a wireless network (or broadband network) can be can be cached on the local proxy and managed by the distributed caching system.
  • a mobile device e.g., any wireless device
  • an application server/content provider in a wireless network or broadband network
  • FIG. 5 depicts a diagram showing one example process for implementing a hybrid IP and SMS power saving mode on a mobile device (e.g., any wireless device) using a distributed proxy and cache system (e.g., such as the distributed system shown in the example of FIG. 1B ).
  • a mobile device e.g., any wireless device
  • a distributed proxy and cache system e.g., such as the distributed system shown in the example of FIG. 1B .
  • FIG. 6 depicts a flow diagram illustrating an example process for distributed content caching between a mobile device (e.g., any wireless device) and remote proxy and the distributed management of content caching.
  • a mobile device e.g., any wireless device
  • FIG. 7 depicts an interaction diagram showing cache management by a distributed proxy system of content delivered to a mobile application over a long-held request while ensuring freshness of content delivered.
  • FIG. 8 depicts a timing diagram showing hunting mode behavior in a long poll request and a timing diagram showing timing characteristics when the long poll has settled.
  • FIG. 9 depicts a flow chart illustrating an example process for caching content pushed to a mobile device (e.g., any wireless device) in a persistent connection from a content server over a wireless network (or broadband network).
  • a mobile device e.g., any wireless device
  • a wireless network or broadband network
  • FIG. 10 depicts a diagram showing example processes that occur when removing a stored response from the local cache on a mobile device (e.g., any wireless device) for a long poll request.
  • a mobile device e.g., any wireless device
  • FIG. 11 depicts a flow chart illustrating an example process for using cached content provided over a long-held connection via a wireless network (or broadband network) to satisfy mobile client requests on a mobile device (e.g., any wireless device).
  • a wireless network or broadband network
  • FIG. 12 depicts a flow chart illustrating an example process for caching content received at a mobile device (e.g., any wireless device) over a persistent connection over a wireless network (or broadband network).
  • a mobile device e.g., any wireless device
  • a wireless network or broadband network
  • FIG. 13 depicts a flow chart illustrating an example process for detecting a long poll request initiated at a mobile device (e.g., any wireless device).
  • a mobile device e.g., any wireless device.
  • FIG. 14 depicts a flow chart illustrating an example process for determining whether to cache content received in long poll requests of an application on a mobile device using timing intervals in a request-response timing sequence.
  • FIG. 15 depicts a flow chart illustrating an example process for detecting requests for a persistent connection (e.g., long poll requests, long-held HTTP requests, or HTTP streaming requests) from an application using relative timings in request-response timing sequences.
  • a persistent connection e.g., long poll requests, long-held HTTP requests, or HTTP streaming requests
  • FIG. 16 depicts a flow chart illustrating an example process for determining whether to cache content received for an application over long-held connections on a mobile device.
  • FIG. 17A depicts an example of a timing diagram showing timing characteristics for request-response sequences.
  • FIG. 17B depicts an example of a timing diagram showing timing characteristics for request-response sequences characteristic of a long poll.
  • FIG. 18 depicts example timing diagrams showing timing characteristics for various types of request-response sequences.
  • FIG. 19 shows a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.
  • Embodiments of the present disclosure include systems and methods for application and network-based long poll request detection and cacheability assessment therefor.
  • a long poll request initiated at a mobile device can be detected by determining relative timings between a first request initiated by the application, a response received responsive to the first request, and a second request initiated subsequent to the first request also by the application.
  • the relative timings can be used to determine whether requests generated by the application are long poll requests.
  • it can be determined that content received for the application is cacheable, when the received responses indicate repeatability, and/or when the relative timings depict some pattern that may be reproducible.
  • a long-held request generally includes and can refer to, connections between a client (e.g., an application, a mobile application on a device, or a device such as a mobile device or wireless device) and a server that is held open even if content is not available to be sent back to the client.
  • the connection can be maintained between the client and server, until content becomes available at the server to be sent to the client.
  • the client e.g., end user computer or mobile device such as a mobile phone, or a Machine to Machine (M2M) device
  • M2M Machine to Machine
  • the client typically will immediately re-issue a request to connect again to the server which holds the connection open until requested content becomes available for the client device.
  • a long-held requested connection can include, for example, a persistent connection, a persistent HTTP connection, long poll-type request, HTTP streaming, or any other types of connections suited for push or emulated content push.
  • One embodiment of the disclosed technology includes, a system that optimizes multiple aspects of the connection with wired and wireless networks, broadband networks, and devices through a comprehensive view of device and application activity including: loading, current application needs on a device, controlling the type of access (push vs. pull or hybrid), location, concentration of users in a single area, time of day, how often the user interacts with the application, content or device, and using this information to shape traffic to a cooperative client/server or simultaneously mobile devices without a cooperative client. Because the disclosed server is not tied to any specific network provider it has visibility into the network performance across all service providers. This enables optimizations to be applied to devices regardless of the operator or service provider, thereby enhancing the user experience and managing network utilization while roaming.
  • Bandwidth has been considered a major issue in wireless networks today. More and more research has been done related to the need for additional bandwidth to solve access problems—many of the performance enhancing solutions and next generation standards, such as those commonly referred to as 4G, namely LTE, 4G, and WiMAX are focused on providing increased bandwidth. Although partially addressed by the standards a key problem that remains is lack of bandwidth on the signaling channel more so than the data channel and the standard does not address battery life very well.
  • Embodiments of the disclosed technology includes, for example, alignment of requests from multiple applications to minimize the need for several polling requests; leverage specific content types to determine how to proxy/manage a connection/content; and apply specific heuristics associated with device, user behavioral patterns (how often they interact with the device/application) and/or network parameters.
  • Embodiments of the present technology can further include, moving recurring HTTP polls performed by various widgets, RSS readers, etc., to remote network node (e.g., Network Operation Center (NOC)), thus considerably lowering device battery/power consumption, radio channel signaling and bandwidth usage. Additionally, the offloading can be performed transparently so that existing applications do not need to be changed.
  • NOC Network Operation Center
  • this can be implemented using a local proxy on the mobile device (e.g., any wireless device) which automatically detects recurring requests for the same content (RSS feed, Widget data set) that matches a specific rule (e.g., happens every 15 minutes).
  • the local proxy can automatically cache the content on the mobile device while delegating the polling to the server (e.g., a proxy server operated as an element of a communications network).
  • the server can then notify the mobile/client proxy if the content changes, and if content has not changed (or not changed sufficiently, or in an identified manner or amount) the mobile proxy provides the latest version in its cache to the user (without need to utilize the radio at all).
  • the mobile or wireless device e.g., a mobile phone, smart phone, M2M module/MODEM, or any other wireless devices, etc.
  • the mobile or wireless device does not need to open (e.g., thus powering on the radio) or use a data connection if the request is for content that is monitored and that has been not flagged as new/changed.
  • the logic for automatically adding content sources/application servers (e.g., including URLs/content) to be monitored can also check for various factors like how often the content is the same, how often the same request is made (is there a fixed interval/pattern?), which application is requesting the data, etc. Similar rules to decide between using the cache and request the data from the original source may also be implemented and executed by the local proxy and/or server.
  • content sources/application servers e.g., including URLs/content
  • the disclosed technology allows elimination of unnecessary chatter from the network, benefiting the operators trying to optimize the wireless spectrum usage.
  • the distributed proxy system By detecting the rate and type of requests to a content source or application server (which may be identified by a URI or URL), combined with determining the state information of the mobile device (e.g., whether the backlight is on or off) or the user, the distributed proxy system (e.g., the local proxy and/or the proxy server) can, for example, determine the difference between content that is programmatically refreshed and content that is requested by the user in the foreground. Using this information, along with the network conditions such as the TCP connection delay and/or Round Trip Time (RTT), current radio coverage statistics, the disclosed proxy system can determine whether to and when to cache content locally on the mobile device (e.g., any wireless device), to satisfy future content requests. If content is already cached, then the cached version can be presented to the user. If not, the request is passed through over the mobile network to the content server and the retrieved content can be presented.
  • RTT Round Trip Time
  • the disclosed distributed proxy system can determine and utilize the “criticality of an application” as a factor.
  • financial applications may be considered time critical so that these application requests are not cached but instead allowed to go over the wireless broadband or mobile network to retrieve current data.
  • An application by name or type, can be considered critical at the time of provisioning or determined by programmatic observation of user interaction over time. That is, the sever-side component of the distributed proxy system can be provisioned with “profiles” which indicate the criticality of the application. This profile can be communicated to the device-side component of the proxy system during initialization or subsequent establishment of polling requests.
  • a set of criteria can be applied to content sources/application servers (e.g., each associated resource or resource identifier) to determine the suitability of related content for caching (size, etc.).
  • the profile can further be used to identify applications for which caching will typically not be appropriate, such as the Google Market.
  • the pattern e.g., periodicity or time interval
  • a specific identifier e.g., a resource of resource identifier
  • the distributed system such that polling behavior can be determined, and the content cached accordingly.
  • a message can be transmitted to the server-side component of the disclosed proxy system requesting that that the content associated with the content source/application server be monitored for changes.
  • the server detects that the content has been altered, the server transmits a message to the device-side component instructing it to invalidate whatever cache elements are associated with that URI.
  • memory usage parameters of a mobile device are factored in when caching.
  • the client-side component of the disclosed distributed proxy will usually not use more than the specified percentage of available memory space for cache entries (e.g., as specified by the device manufacturer, operating system, applications, etc.).
  • the client-side component of the distributed proxy can implement a configurable limit on the total number of cache entries stored across multiple applications or on a per-application basis.
  • Cache entries stored on the mobile device can be aged out automatically by the client-side component of the distributed proxy as determined, for example, by configurable parameters (e.g., by the user, based on application-need, network service provider requirements, OS requirements, etc.). Additionally, cache elements may be removed to remain in compliance with disk usage or entry count restrictions. In some instances, the client-side component can invalidate the entire cache storage should the server-side proxy become unavailable. In one embodiment, the client-side component of the distributed proxy system can encrypt cached content.
  • FIG. 1A illustrates an example diagram of a system where a host server 100 facilitates management of traffic, content caching, and/or resource conservation between clients (e.g., mobile devices, any wireless device or clients/applications on client devices 150 ) and an application server or content provider 110 in a wireless network (or broad band network) 106 or 108 for resource conservation.
  • clients e.g., mobile devices, any wireless device or clients/applications on client devices 150
  • an application server or content provider 110 in a wireless network (or broad band network) 106 or 108 for resource conservation.
  • the client devices 150 can be any system and/or device, and/or any combination of devices/systems that is able to establish a connection, including wired, wireless, cellular connections with another device, a server and/or other systems such as host server 100 and/or application server/content provider 110 .
  • Client devices 150 will typically include a display and/or other output functionalities to present information and data exchanged between among the devices 150 and/or the host server 100 and/or application server/content provider 110 .
  • the client devices 150 can include mobile, hand held or portable devices, wireless devices, or non-portable devices and can be any of, but not limited to, a server desktop, a desktop computer, a computer cluster, or portable devices, including a notebook, a laptop computer, a handheld computer, a palmtop computer, a mobile phone, a cell phone, a smart phone, a PDA, a Blackberry device, a Palm device, a handheld tablet (e.g., an iPad or any other tablet), a hand held console, a hand held gaming device or console, any SuperPhone such as the iPhone, and/or any other portable, mobile, hand held devices, or fixed wireless interface such as a M2M device, etc.
  • the client devices 150 , host server 100 , and application server 110 are coupled via a network 106 and/or a network 108 .
  • the devices 150 and host server 100 may be directly connected to one another.
  • the input mechanism on client devices 150 can include touch screen keypad (including single touch, multi-touch, gesture sensing in 2D or 3D, etc.), a physical keypad, a mouse, a pointer, a track pad, motion detector (e.g., including 1-axis, 2-axis, 3-axis accelerometer, etc.), a light sensor, capacitance sensor, resistance sensor, temperature sensor, proximity sensor, a piezoelectric device, device orientation detector (e.g., electronic compass, tilt sensor, rotation sensor, gyroscope, accelerometer), or a combination of the above.
  • touch screen keypad including single touch, multi-touch, gesture sensing in 2D or 3D, etc.
  • a physical keypad e.g., a mouse, a pointer, a track pad
  • motion detector e.g., including 1-axis, 2-axis, 3-axis accelerometer, etc.
  • a light sensor e.g., including 1-axis, 2-axis, 3-axis accelerometer, etc.
  • Context awareness at client devices 150 generally includes, by way of example but not limitation, client device 150 operation or state acknowledgement, management, user activity/behavior/interaction awareness, detection, sensing, tracking, trending, and/or application (e.g., mobile applications) type, behavior, activity, operating state, etc.
  • Context awareness in the present disclosure also includes knowledge and detection of network side contextual data and can include network information such as network capacity, bandwidth, traffic, type of network/connectivity, and/or any other operational state data.
  • Network side contextual data can be received from and/or queried from network service providers (e.g., cell provider 112 and/or Internet service providers) of the network 106 and/or network 108 (e.g., by the host server and/or devices 150 ).
  • the application context awareness may also be received from or obtained/queried from the respective application/service providers 110 (by the host 100 and/or client devices 150 ).
  • the host server 100 can use, for example, contextual information obtained for client devices 150 , networks 106 / 108 , applications (e.g., mobile applications), application server/provider 110 , or any combination of the above, to manage the traffic in the system to satisfy data needs of the client devices 150 (e.g., to satisfy application or any other request including HTTP request).
  • the traffic is managed by the host server 100 to satisfy data requests made in response to explicit or non-explicit user 103 requests and/or device/application maintenance tasks.
  • the traffic can be managed such that network consumption, for example, use of the cellular network is conserved for effective and efficient bandwidth utilization.
  • the host server 100 can manage and coordinate such traffic in the system such that use of device 150 side resources (e.g., including but not limited to battery power consumption, radio use, processor/memory use) are optimized with a general philosophy for resource conservation while still optimizing performance and user experience.
  • device 150 side resources e.g., including but not limited to battery power consumption, radio use, processor/memory use
  • the device 150 can observe user activity (for example, by observing user keystrokes, backlight status, or other signals via one or more input mechanisms, etc.) and alters device 150 behaviors.
  • the device 150 can also request the host server 100 to alter the behavior for network resource consumption based on user activity or behavior.
  • the traffic management for resource conservation is performed using a distributed system between the host server 100 and client device 150 .
  • the distributed system can include proxy server and cache components on the server side 100 and on the device/client side, for example, as shown by the server cache 135 on the server 100 side and the local cache 185 on the client 150 side.
  • Functions and techniques disclosed for context aware traffic management for resource conservation in networks (e.g., network 106 and/or 108 ) and devices 150 reside in a distributed proxy and cache system.
  • the proxy and cache system can be distributed between, and reside on, a given client device 150 in part or in whole and/or host server 100 in part or in whole.
  • the distributed proxy and cache system are illustrated with further reference to the example diagram shown in FIG. 1B .
  • Functions and techniques performed by the proxy and cache components in the client device 150 , the host server 100 , and the related components therein are described, respectively, in detail with further reference to the examples of FIG. 2-3 .
  • client devices 150 communicate with the host server 100 and/or the application server 110 over network 106 , which can be a cellular network and/or a broadband network.
  • network 106 can be a cellular network and/or a broadband network.
  • the host server 100 can communicate with the application server/providers 110 over the network 108 , which can include the Internet (e.g., a broadband network).
  • the networks 106 and/or 108 over which the client devices 150 , the host server 100 , and/or application server 110 communicate, may be a cellular network, a broadband network, a telephonic network, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet, or any combination thereof.
  • the Internet can provide file transfer, remote log in, email, news, RSS, cloud-based services, instant messaging, visual voicemail, push mail, VoIP, and other services through any known or convenient protocol, such as, but is not limited to the TCP/IP protocol, UDP, HTTP, DNS, FTP, UPnP, NSF, ISDN, PDH, RS-232, SDH, SONET, etc.
  • the networks 106 and/or 108 can be any collection of distinct networks operating wholly or partially in conjunction to provide connectivity to the client devices 150 and the host server 100 and may appear as one or more networks to the serviced systems and devices.
  • communications to and from the client devices 150 can be achieved by, an open network, such as the Internet, or a private network, broadband network, such as an intranet and/or the extranet.
  • communications can be achieved by a secure communications protocol, such as secure sockets layer (SSL), or transport layer security (TLS).
  • SSL secure sockets layer
  • TLS transport layer security
  • communications can be achieved via one or more networks, such as, but are not limited to, one or more of WiMax, a Local Area Network (LAN), Wireless Local Area Network (WLAN), a Personal area network (PAN), a Campus area network (CAN), a Metropolitan area network (MAN), a Wide area network (WAN), a Wireless wide area network (WWAN), or any broadband network, and further enabled with technologies such as, by way of example, Global System for Mobile Communications (GSM), Personal Communications Service (PCS), Bluetooth, WiFi, Fixed Wireless Data, 2G, 2.5G, 3G, 4G, IMT-Advanced, pre-4G, LTE Advanced, mobile WiMax, WiMax 2, WirelessMAN-Advanced networks, enhanced data rates for GSM evolution (EDGE), General packet radio service (GPRS), enhanced GPRS, iBurst, UMTS, HSPDA, HSUPA, HSPA, UMTS-TDD, 1xRTT, EV-DO, messaging protocols such as, TCP/IP, SMS, MMS, extensible messaging and presence protocol
  • FIG. 1B illustrates an example diagram of a proxy and cache system distributed between the host server 100 and device 150 which facilitates network traffic management between the device 150 and an application server/content provider 100 (e.g., a source server) for resource conservation and content caching.
  • an application server/content provider 100 e.g., a source server
  • the distributed proxy and cache system can include, for example, the proxy server 125 (e.g., remote proxy) and the server cache, 135 components on the server side.
  • the server-side proxy 125 and cache 135 can, as illustrated, reside internal to the host server 100 .
  • the proxy server 125 and cache 135 on the server-side can be partially or wholly external to the host server 100 and in communication via one or more of the networks 106 and 108 .
  • the proxy server 125 may be external to the host server and the server cache 135 may be maintained at the host server 100 .
  • the proxy server 125 may be within the host server 100 while the server cache is external to the host server 100 .
  • each of the proxy server 125 and the cache 135 may be partially internal to the host server 100 and partially external to the host server 100 .
  • the distributed system can also, include, in one embodiment, client-side components, including by way of example but not limitation, a local proxy 175 (e.g., a mobile client on a mobile device) and/or a local cache 185 , which can, as illustrated, reside internal to the device 150 (e.g., a mobile device).
  • client-side components including by way of example but not limitation, a local proxy 175 (e.g., a mobile client on a mobile device) and/or a local cache 185 , which can, as illustrated, reside internal to the device 150 (e.g., a mobile device).
  • the client-side proxy 175 and local cache 185 can be partially or wholly external to the device 150 and in communication via one or more of the networks 106 and 108 .
  • the local proxy 175 may be external to the device 150 and the local cache 185 may be maintained at the device 150 .
  • the local proxy 175 may be within the device 150 while the local cache 185 is external to the device 150 .
  • each of the proxy 175 and the cache 185 may be partially internal to the host server 100 and partially external to the host server 100 .
  • the distributed system can include an optional caching proxy server 199 .
  • the caching proxy server 199 can be a component which is operated by the application server/content provider 110 , the host server 100 , or a network service provider 112 , and or any combination of the above to facilitate network traffic management for network and device resource conservation.
  • Proxy server 199 can be used, for example, for caching content to be provided to the device 150 , for example, from one or more of, the application server/provider 110 , host server 100 , and/or a network service provider 112 .
  • Content caching can also be entirely or partially performed by the remote proxy 125 to satisfy application requests or other data requests at the device 150 .
  • characteristics of user activity/behavior and/or application behavior at a mobile device 150 can be tracked by the local proxy 175 and communicated, over the network 106 to the proxy server 125 component in the host server 100 , for example, as connection metadata.
  • the proxy server 125 which in turn is coupled to the application server/provider 110 provides content and data to satisfy requests made at the device 150 .
  • the local proxy 175 can identify and retrieve mobile device properties, including one or more of, battery level, network that the device is registered on, radio state, or whether the mobile device is being used (e.g., interacted with by a user). In some instances, the local proxy 175 can delay, expedite (prefetch), and/or modify data prior to transmission to the proxy server 125 , when appropriate, as will be further detailed with references to the description associated with the examples of FIG. 2-3 .
  • the local database 185 can be included in the local proxy 175 or coupled to the local proxy 175 and can be queried for a locally stored response to the data request prior to the data request being forwarded on to the proxy server 125 .
  • Locally cached responses can be used by the local proxy 175 to satisfy certain application requests of the mobile device 150 , by retrieving cached content stored in the cache storage 185 , when the cached content is still valid.
  • the proxy server 125 of the host server 100 can also delay, expedite, or modify data from the local proxy prior to transmission to the content sources (e.g., the application server/content provider 110 ).
  • the proxy server 125 uses device properties and connection metadata to generate rules for satisfying request of applications on the mobile device 150 .
  • the proxy server 125 can gather real time traffic information about requests of applications for later use in optimizing similar connections with the mobile device 150 or other mobile devices.
  • the local proxy 175 and the proxy server 125 are transparent to the multiple applications executing on the mobile device.
  • the local proxy 175 is generally transparent to the operating system or platform of the mobile device and may or may not be specific to device manufacturers.
  • the local proxy 175 is optionally customizable in part or in whole to be device specific.
  • the local proxy 175 may be bundled into a wireless model, a firewall, and/or a router.
  • the host server 100 can in some instances, utilize the store and forward functions of a short message service center (SMSC) 112 , such as that provided by the network service provider, in communicating with the device 150 in achieving network traffic management.
  • SMSC short message service center
  • 112 can also utilize any other type of alternative channel including USSD or other network control mechanisms.
  • the host server 100 can forward content or HTTP responses to the SMSC 112 such that it is automatically forwarded to the device 150 if available, and for subsequent forwarding if the device 150 is not currently available.
  • the disclosed distributed proxy and cache system allows optimization of network usage, for example, by serving requests from the local cache 185 , the local proxy 175 reduces the number of requests that need to be satisfied over the network 106 . Further, the local proxy 175 and the proxy server 125 may filter irrelevant data from the communicated data. In addition, the local proxy 175 and the proxy server 125 can also accumulate low priority data and send it in batches to avoid the protocol overhead of sending individual data fragments. The local proxy 175 and the proxy server 125 can also compress or transcode the traffic, reducing the amount of data sent over the network 106 and/or 108 . The signaling traffic in the network 106 and/or 108 can be reduced, as the networks are now used less often and the network traffic can be synchronized among individual applications.
  • the local proxy 175 can reduce the number of times the radio module is powered up.
  • the local proxy 175 and the proxy server 125 can work in conjunction to accumulate low priority data and send it in batches to reduce the number of times and/or amount of time when the radio is powered up.
  • the local proxy 175 can synchronize the network use by performing the batched data transfer for all connections simultaneously.
  • FIG. 2A depicts a block diagram illustrating an example of client-side components in a distributed proxy and cache system residing on a device 250 that manages traffic in a wireless network for resource conservation, content caching, and/or traffic management.
  • the device 250 which can be a portable or mobile device (e.g., any wireless device), such as a portable phone, generally includes, for example, a network interface 208 an operating system 204 , a context API 206 , and mobile applications which may be proxy-unaware 210 or proxy-aware 220 .
  • the device 250 is specifically illustrated in the example of FIG. 2 as a mobile device, such is not a limitation and that device 250 may be any portable/mobile or non-portable device able to receive, transmit signals to satisfy data requests over a network including wired or wireless networks (e.g., WiFi, cellular, Bluetooth, etc.).
  • wired or wireless networks e.g., WiFi, cellular, Bluetooth, etc.
  • the network interface 208 can be a networking module that enables the device 250 to mediate data in a network with an entity that is external to the host server 250 , through any known and/or convenient communications protocol supported by the host and the external entity.
  • the network interface 208 can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 2G, 3G, 3.5G, 4G, LTE, etc.), Bluetooth, or whether or not the connection is via a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, a bridge router, a hub, a digital media receiver, and/or a repeater.
  • a network adaptor card e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 2G, 3G, 3.5G, 4G, LTE, etc.
  • Bluetooth or whether
  • Device 250 can further include, client-side components of the distributed proxy and cache system which can include, a local proxy 275 (e.g., a mobile client of a mobile device) and a cache 285 .
  • the local proxy 275 includes a user activity module 215 , a proxy API 225 , a request/transaction manager 235 , a caching policy manager 245 having an application protocol module 248 , a traffic shaping engine 255 , and/or a connection manager 265 .
  • the traffic shaping engine 255 may further include an alignment module 256 and/or a batching module 257
  • the connection manager 265 may further include a radio controller 266 .
  • the request/transaction manager 235 can further include an application behavior detector 236 and/or a prioritization engine 241 , the application behavior detector 236 may further include a pattern detector 237 and/or and application profile generator 239 . Additional or less components/modules/engines can be included in the local proxy 275 and each illustrated component.
  • a “module,” “a manager,” a “handler,” a “detector,” an “interface,” a “controller,” a “normalizer,” a “generator,” an “invalidator,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor.
  • the module, manager, handler, detector, interface, controller, normalizer, generator, invalidator, or engine can be centralized or its functionality distributed.
  • the module, manager, handler, detector, interface, controller, normalizer, generator, invalidator, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor.
  • a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid.
  • Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.
  • a portion of the distributed proxy and cache system for network traffic management resides in or is in communication with device 250 , including local proxy 275 (mobile client) and/or cache 285 .
  • the local proxy 275 can provide an interface on the device 250 for users to access device applications and services including email, IM, voice mail, visual voicemail, feeds, Internet, games, productivity tools, or other applications, etc.
  • the proxy 275 is generally application independent and can be used by applications (e.g., both proxy-aware and proxy-unaware applications 210 and 220 or mobile applications) to open TCP connections to a remote server (e.g., the server 100 in the examples of FIG. 1A-1B and/or server proxy 125 / 325 shown in the examples of FIG. 1B and FIG. 3A ).
  • a remote server e.g., the server 100 in the examples of FIG. 1A-1B and/or server proxy 125 / 325 shown in the examples of FIG. 1B and FIG. 3A .
  • the local proxy 275 includes a proxy API 225 which can be optionally used to interface with proxy-aware applications 220 (or applications (e.g., mobile applications) on a mobile device (e.g., any wireless device)).
  • the applications 210 and 220 can generally include any user application, widgets, software, HTTP-based application, web browsers, video or other multimedia streaming or downloading application, video games, social network applications, email clients, RSS management applications, application stores, document management applications, productivity enhancement applications, etc.
  • the applications can be provided with the device OS, by the device manufacturer, by the network service provider, downloaded by the user, or provided by others.
  • the local proxy 275 includes or is coupled to a context API 206 , as shown.
  • the context API 206 may be a part of the operating system 204 or device platform or independent of the operating system 204 , as illustrated.
  • the operating system 204 can include any operating system including but not limited to, any previous, current, and/or future versions/releases of, Windows Mobile, iOS, Android, Symbian, Palm OS, Brew MP, Java 2 Micro Edition (J2ME), Blackberry, etc.
  • the context API 206 may be a plug-in to the operating system 204 or a particular client/application on the device 250 .
  • the context API 206 can detect signals indicative of user or device activity, for example, sensing motion, gesture, device location, changes in device location, device backlight, keystrokes, clicks, activated touch screen, mouse click or detection of other pointer devices.
  • the context API 206 can be coupled to input devices or sensors on the device 250 to identify these signals. Such signals can generally include input received in response to explicit user input at an input device/mechanism at the device 250 and/or collected from ambient signals/contextual cues detected at or in the vicinity of the device 250 (e.g., light, motion, piezoelectric, etc.).
  • the user activity module 215 interacts with the context API 206 to identify, determine, infer, detect, compute, predict, and/or anticipate, characteristics of user activity on the device 250 .
  • Various inputs collected by the context API 206 can be aggregated by the user activity module 215 to generate a profile for characteristics of user activity. Such a profile can be generated by the user activity module 215 with various temporal characteristics.
  • user activity profile can be generated in real-time for a given instant to provide a view of what the user is doing or not doing at a given time (e.g., defined by a time window, in the last minute, in the last 30 seconds, etc.), a user activity profile can also be generated for a ‘session’ defined by an application or web page that describes the characteristics of user behavior with respect to a specific task they are engaged in on the device 250 , or for a specific time period (e.g., for the last 2 hours, for the last 5 hours).
  • characteristic profiles can be generated by the user activity module 215 to depict a historical trend for user activity and behavior (e.g., 1 week, 1 mo., 2 mo., etc.). Such historical profiles can also be used to deduce trends of user behavior, for example, access frequency at different times of day, trends for certain days of the week (weekends or week days), user activity trends based on location data (e.g., IP address, GPS, or cell tower coordinate data) or changes in location data (e.g., user activity based on user location, or user activity based on whether the user is on the go, or traveling outside a home region, etc.) to obtain user activity characteristics.
  • location data e.g., IP address, GPS, or cell tower coordinate data
  • changes in location data e.g., user activity based on user location, or user activity based on whether the user is on the go, or traveling outside a home region, etc.
  • user activity module 215 can detect and track user activity with respect to applications, documents, files, windows, icons, and folders on the device 250 .
  • the user activity module 215 can detect when an application or window (e.g., a web browser or any other type of application) has been exited, closed, minimized, maximized, opened, moved into the foreground, or into the background, multimedia content playback, etc.
  • an application or window e.g., a web browser or any other type of application
  • characteristics of the user activity on the device 250 can be used to locally adjust behavior of the device (e.g., mobile device or any wireless device) to optimize its resource consumption such as battery/power consumption and more generally, consumption of other device resources including memory, storage, and processing power.
  • the use of a radio on a device can be adjusted based on characteristics of user behavior (e.g., by the radio controller 266 of the connection manager 265 ) coupled to the user activity module 215 .
  • the radio controller 266 can turn the radio on or off, based on characteristics of the user activity on the device 250 .
  • the radio controller 266 can adjust the power mode of the radio (e.g., to be in a higher power mode or lower power mode) depending on characteristics of user activity.
  • characteristics of the user activity on device 250 can also be used to cause another device (e.g., other computers, a mobile device, a wireless device, or a non-portable device) or server (e.g., host server 100 and 300 in the examples of FIG. 1A-B and FIG. 3A ) which can communicate (e.g., via a cellular or other network) with the device 250 to modify its communication frequency with the device 250 .
  • another device e.g., other computers, a mobile device, a wireless device, or a non-portable device
  • server e.g., host server 100 and 300 in the examples of FIG. 1A-B and FIG. 3A
  • the local proxy 275 can use the characteristics information of user behavior determined by the user activity module 215 to instruct the remote device as to how to modulate its communication frequency (e.g., decreasing communication frequency, such as data push frequency if the user is idle, requesting that the remote device notify the device 250 if new data, changed, data, or data of a certain level of importance becomes available, etc.).
  • decreasing communication frequency such as data push frequency if the user is idle
  • the user activity module 215 can, in response to determining that user activity characteristics indicate that a user is active after a period of inactivity, request that a remote device (e.g., server host server 100 and 300 in the examples of FIG. 1A-B and FIG. 3A ) send the data that was buffered as a result of the previously decreased communication frequency.
  • a remote device e.g., server host server 100 and 300 in the examples of FIG. 1A-B and FIG. 3A
  • the local proxy 275 can communicate the characteristics of user activity at the device 250 to the remote device (e.g., host server 100 and 300 in the examples of FIG. 1A-B and FIG. 3A ) and the remote device determines how to alter its own communication frequency with the device 250 for network resource conservation and conservation of device 250 resources.
  • the remote device e.g., host server 100 and 300 in the examples of FIG. 1A-B and FIG. 3A
  • the remote device determines how to alter its own communication frequency with the device 250 for network resource conservation and conservation of device 250 resources.
  • One embodiment of the local proxy 275 further includes a request/transaction manager 235 , which can detect, identify, intercept, process, manage, data requests initiated on the device 250 , for example, by applications 210 and/or 220 , and/or directly/indirectly by a user request.
  • the request/transaction manager 235 can determine how and when to process a given request or transaction, or a set of requests/transactions, based on transaction characteristics.
  • the request/transaction manager 235 can prioritize requests or transactions made by applications and/or users at the device 250 , for example by the prioritization engine 241 . Importance or priority of requests/transactions can be determined by the request/transaction manager 235 by applying a rule set, for example, according to time sensitivity of the transaction, time sensitivity of the content in the transaction, time criticality of the transaction, time criticality of the data transmitted in the transaction, and/or time criticality or importance of an application making the request.
  • transaction characteristics can also depend on whether the transaction was a result of user-interaction or other user-initiated action on the device (e.g., user interaction with a application (e.g., a mobile application)).
  • a time critical transaction can include a transaction resulting from a user-initiated data transfer, and can be prioritized as such.
  • Transaction characteristics can also depend on the amount of data that will be transferred or is anticipated to be transferred as a result of the requested transaction.
  • the connection manager 265 can adjust the radio mode (e.g., high power or low power mode via the radio controller 266 ) based on the amount of data that will need to be transferred.
  • the radio controller 266 /connection manager 265 can adjust the radio power mode (high or low) based on time criticality/sensitivity of the transaction.
  • the radio controller 266 can trigger the use of high power radio mode when a time-critical transaction (e.g., a transaction resulting from a user-initiated data transfer, an application running in the foreground, any other event meeting a certain criteria) is initiated or detected.
  • a time-critical transaction e.g., a transaction resulting from a user-initiated data transfer, an application running in the foreground, any other event meeting a certain criteria
  • the priorities can be set by default, for example, based on device platform, device manufacturer, operating system, etc.
  • Priorities can alternatively or in additionally be set by the particular application; for example, the Facebook application (e.g., a mobile application) can set its own priorities for various transactions (e.g., a status update can be of higher priority than an add friend request or a poke request, a message send request can be of higher priority than a message delete request, for example), an email client or IM chat client may have its own configurations for priority.
  • the prioritization engine 241 may include set of rules for assigning priority.
  • the prioritization engine 241 can also track network provider limitations or specifications on application or transaction priority in determining an overall priority status for a request/transaction. Furthermore, priority can in part or in whole be determined by user preferences, either explicit or implicit. A user, can in general, set priorities at different tiers, such as, specific priorities for sessions, or types, or applications (e.g., a browsing session, a gaming session, versus an IM chat session, the user may set a gaming session to always have higher priority than an IM chat session, which may have higher priority than web-browsing session).
  • a user can set application-specific priorities, (e.g., a user may set Facebook-related transactions to have a higher priority than Linkedln-related transactions), for specific transaction types (e.g., for all send message requests across all applications to have higher priority than message delete requests, for all calendar-related events to have a high priority, etc.), and/or for specific folders.
  • application-specific priorities e.g., a user may set Facebook-related transactions to have a higher priority than Linkedln-related transactions
  • specific transaction types e.g., for all send message requests across all applications to have higher priority than message delete requests, for all calendar-related events to have a high priority, etc.
  • the prioritization engine 241 can track and resolve conflicts in priorities set by different entities. For example, manual settings specified by the user may take precedence over device OS settings, network provider parameters/limitations (e.g., set in default for a network service area, geographic locale, set for a specific time of day, or set based on service/fee type) may limit any user-specified settings and/or application-set priorities. In some instances, a manual synchronization request received from a user can override some, most, or all priority settings in that the requested synchronization is performed when requested, regardless of the individually assigned priority or an overall priority ranking for the requested action.
  • network provider parameters/limitations e.g., set in default for a network service area, geographic locale, set for a specific time of day, or set based on service/fee type
  • a manual synchronization request received from a user can override some, most, or all priority settings in that the requested synchronization is performed when requested, regardless of the individually assigned priority or an overall priority ranking for the requested
  • Priority can be specified and tracked internally in any known and/or convenient manner, including but not limited to, a binary representation, a multi-valued representation, a graded representation and all are considered to be within the scope of the disclosed technology.
  • Table I above shows, for illustration purposes, some examples of transactions with examples of assigned priorities in a binary representation scheme. Additional assignments are possible for additional types of events, requests, transactions, and as previously described, priority assignments can be made at more or less granular levels, e.g., at the session level or at the application level, etc.
  • lower priority requests/transactions can include, updating message status as being read, unread, deleting of messages, deletion of contacts; higher priority requests/transactions, can in some instances include, status updates, new IM chat message, new email, calendar event update/cancellation/deletion, an event in a mobile gaming session, or other entertainment related events, a purchase confirmation through a web purchase or online, request to load additional or download content, contact book related events, a transaction to change a device setting, location-aware or location-based events/transactions, or any other events/request/transactions initiated by a user or where the user is known to be, expected to be, or suspected to be waiting for a response, etc.
  • Inbox pruning events are generally considered low priority and absent other impending events, generally will not trigger use of the radio on the device 250 .
  • pruning events to remove old email or other content can be ‘piggy backed’ with other communications if the radio is not otherwise on, at the time of a scheduled pruning event. For example, if the user has preferences set to ‘keep messages for 7 days old,’ then instead of powering on the device radio to initiate a message delete from the device 250 the moment that the message has exceeded 7 days old, the message is deleted when the radio is powered on next. If the radio is already on, then pruning may occur as regularly scheduled.
  • the request/transaction manager 235 can use the priorities for requests (e.g., by the prioritization engine 241 ) to manage outgoing traffic from the device 250 for resource optimization (e.g., to utilize the device radio more efficiently for battery conservation). For example, transactions/requests below a certain priority ranking may not trigger use of the radio on the device 250 if the radio is not already switched on, as controlled by the connection manager 265 . In contrast, the radio controller 266 can turn on the radio such a request can be sent when a request for a transaction is detected to be over a certain priority level.
  • priority assignments (such as that determined by the local proxy 275 or another device/entity) can be used cause a remote device to modify its communication with the frequency with the mobile device or wireless device.
  • the remote device can be configured to send notifications to the device 250 when data of higher importance is available to be sent to the mobile device or wireless device.
  • transaction priority can be used in conjunction with characteristics of user activity in shaping or managing traffic, for example, by the traffic shaping engine 255 .
  • the traffic shaping engine 255 can, in response to detecting that a user is dormant or inactive, wait to send low priority transactions from the device 250 , for a period of time.
  • the traffic shaping engine 255 can allow multiple low priority transactions to accumulate for batch transferring from the device 250 (e.g., via the batching module 257 ).
  • the priorities can be set, configured, or readjusted by a user. For example, content depicted in Table I in the same or similar form can be accessible in a user interface on the device 250 and for example, used by the user to adjust or view the priorities.
  • the batching module 257 can initiate batch transfer based on certain criteria. For example, batch transfer (e.g., of multiple occurrences of events, some of which occurred at different instances in time) may occur after a certain number of low priority events have been detected, or after an amount of time elapsed after the first of the low priority event was initiated. In addition, the batching module 257 can initiate batch transfer of the cumulated low priority events when a higher priority event is initiated or detected at the device 250 . Batch transfer can otherwise be initiated when radio use is triggered for another reason (e.g., to receive data from a remote device such as host server 100 or 300 ). In one embodiment, an impending pruning event (pruning of an inbox), or any other low priority events, can be executed when a batch transfer occurs.
  • an impending pruning event pruning of an inbox
  • the batching capability can be disabled or enabled at the event/transaction level, application level, or session level, based on any one or combination of the following: user configuration, device limitations/settings, manufacturer specification, network provider parameters/limitations, platform-specific limitations/settings, device OS settings, etc.
  • batch transfer can be initiated when an application/window/file is closed out, exited, or moved into the background; users can optionally be prompted before initiating a batch transfer; users can also manually trigger batch transfers.
  • the local proxy 275 locally adjusts radio use on the device 250 by caching data in the cache 285 .
  • the radio controller 266 need not activate the radio to send the request to a remote entity (e.g., the host server 100 , 300 , as shown in FIG. 1A and FIG. 3A or a content provider/application server such as the server/provider 110 shown in the examples of FIG. 1A and FIG. 1B ).
  • the local proxy 275 can use the local cache 285 and the cache policy manager 245 to locally store data for satisfying data requests to eliminate or reduce the use of the device radio for conservation of network resources and device battery consumption.
  • the local repository 285 can be queried to determine if there is any locally stored response, and also determine whether the response is valid. When a valid response is available in the local cache 285 , the response can be provided to the application on the device 250 without the device 250 needing to access the cellular network or wireless broadband network.
  • the local proxy 275 can query a remote proxy (e.g., the server proxy 325 of FIG. 3A ) to determine whether a remotely stored response is valid. If so, the remotely stored response (e.g., which may be stored on the server cache 135 or optional caching server 199 shown in the example of FIG. 1B ) can be provided to the mobile device, possibly without the mobile device 250 needing to access the cellular network, thus relieving consumption of network resources.
  • a remote proxy e.g., the server proxy 325 of FIG. 3A
  • the local proxy 275 can send the data request to a remote proxy (e.g., server proxy 325 of FIG. 3A ) which forwards the data request to a content source (e.g., application server/content provider 110 of FIG. 1A ) and a response from the content source can be provided through the remote proxy, as will be further described in the description associated with the example host server 300 of FIG. 3A .
  • the cache policy manager 245 can manage or process requests that use a variety of protocols, including but not limited to HTTP, HTTPS, IMAP, POP, SMTP, XMPP, and/or ActiveSync.
  • the caching policy manager 245 can locally store responses for data requests in the local database 285 as cache entries, for subsequent use in satisfying same or similar data requests.
  • the caching policy manager 245 can request that the remote proxy monitor responses for the data request and the remote proxy can notify the device 250 when an unexpected response to the data request is detected. In such an event, the cache policy manager 245 can erase or replace the locally stored response(s) on the device 250 when notified of the unexpected response (e.g., new data, changed data, additional data, etc.) to the data request. In one embodiment, the caching policy manager 245 is able to detect or identify the protocol used for a specific request, including but not limited to HTTP, HTTPS, IMAP, POP, SMTP, XMPP, and/or ActiveSync.
  • application specific handlers (e.g., via the application protocol module 246 of the caching policy manager 245 ) on the local proxy 275 allows for optimization of any protocol that can be port mapped to a handler in the distributed proxy (e.g., port mapped on the proxy server 325 in the example of FIG. 3A ).
  • the local proxy 275 notifies the remote proxy such that the remote proxy can monitor responses received for the data request from the content source for changed results prior to returning the result to the device 250 , for example, when the data request to the content source has yielded same results to be returned to the mobile device.
  • the local proxy 275 can simulate application server responses for applications on the device 250 , using locally cached content. This can prevent utilization of the cellular network for transactions where new/changed data is not available, thus freeing up network resources and preventing network congestion.
  • the local proxy 275 includes an application behavior detector 236 to track, detect, observe, monitor, applications (e.g., proxy-aware and/or unaware applications 210 and 220 ) accessed or installed on the device 250 .
  • application behaviors, or patterns in detected behaviors (e.g., via the pattern detector 237 ) of one or more applications accessed on the device 250 can be used by the local proxy 275 to optimize traffic in a wireless network needed to satisfy the data needs of these applications.
  • the traffic shaping engine 255 can align content requests made by at least some of the applications over the network (wireless network) (e.g., via the alignment module 256 ).
  • the alignment module 256 can delay or expedite some earlier received requests to achieve alignment.
  • the traffic shaping engine 255 can utilize the connection manager to poll over the network to satisfy application data requests.
  • Content requests for multiple applications can be aligned based on behavior patterns or rules/settings including, for example, content types requested by the multiple applications (audio, video, text, etc.), device (e.g., mobile or wireless device) parameters, and/or network parameters/traffic conditions, network service provider constraints/specifications, etc.
  • the pattern detector 237 can detect recurrences in application requests made by the multiple applications, for example, by tracking patterns in application behavior.
  • a tracked pattern can include, detecting that certain applications, as a background process, poll an application server regularly, at certain times of day, on certain days of the week, periodically in a predictable fashion, with a certain frequency, with a certain frequency in response to a certain type of event, in response to a certain type user query, frequency that requested content is the same, frequency with which a same request is made, interval between requests, applications making a request, or any combination of the above, for example.
  • Such recurrences can be used by traffic shaping engine 255 to offload polling of content from a content source (e.g., from an application server/content provider 110 of FIG. 1A ) that would result from the application requests that would be performed at the mobile device or wireless device 250 to be performed instead, by a proxy server (e.g., proxy server 125 of FIG. 1B or proxy server 325 of FIG. 3A ) remote from the device 250 .
  • Traffic shaping engine 255 can decide to offload the polling when the recurrences match a rule.
  • the offloading of the polling can decrease the amount of bandwidth consumption needed by the mobile device 250 to establish a wireless (cellular or other wireless broadband) connection with the content source for repetitive content polls.
  • the remote entity to which polling is offloaded can notify the device 250 .
  • the remote entity may be the host server 300 as shown in the example of FIG. 3A .
  • the local proxy 275 can mitigate the need/use of periodic keep-alive messages (heartbeat messages) to maintain TCP/IP connections, which can consume significant amounts of power thus having detrimental impacts on mobile device battery life.
  • the connection manager 265 in the local proxy e.g., the heartbeat manager 267
  • the heartbeat manager 267 can prevent any or all of these heartbeat messages from being sent over the cellular, or other network, and instead rely on the server component of the distributed proxy system (e.g., shown in FIG. 1B ) to generate the and send the heartbeat messages to maintain a connection with the backend (e.g., application server/provider 110 in the example of FIG. 1A ).
  • the server component of the distributed proxy system e.g., shown in FIG. 1B
  • the backend e.g., application server/provider 110 in the example of FIG. 1A .
  • the local proxy 275 generally represents any one or a portion of the functions described for the individual managers, modules, and/or engines.
  • the local proxy 275 and device 250 can include additional or less components; more or less functions can be included, in whole or in part, without deviating from the novel art of the disclosure.
  • FIG. 2B depicts a block diagram illustrating another example of components in the application behavior detector 236 and the caching policy manager 245 in the local proxy 275 on the client-side of the distributed proxy system shown in the example of FIG. 2A .
  • the caching policy manager 245 includes a cache appropriateness decision engine 246 , a poll schedule generator 247 , an application protocol module 248 , a cache or connect selection engine 249 and/or a local cache invalidator 244 .
  • the cache appropriateness decision engine 246 can further include a timing predictor 246 a and/or a content predictor 246 b and the cache or connect selection engine 249 includes a response scheduler 249 a .
  • One embodiment of caching policy manager 245 includes an application cache policy repository 243 .
  • the application behavior detector 236 includes a pattern detector 237 , a poll interval detector 238 , an application profile generator 239 , and/or a priority engine 241 .
  • the poll interval detector 238 may further include a long poll detector 238 a having a response/request tracking engine 238 b .
  • the poll interval detector 238 may further include a long poll hunting detector 238 c .
  • the application profile generator 239 can further include a response delay interval tracker 239 a.
  • One embodiment further includes an application profile repository 242 which can be used by the local proxy 275 to store information or metadata regarding application profiles (e.g., behavior, patterns, type of HTTP requests, etc.)
  • the cache appropriateness decision engine 246 can detect, assess, or determine, whether content from a content source (e.g., application server/content provider 110 in the example of FIG. 1B ) with which a mobile device (e.g., any wireless device) 250 interacts, has content that may be suitable for caching.
  • content from a given application server/content provider e.g., the server/content provider 110 of FIG. 1B
  • the local proxy applies a selection criteria to store the content from the host server which is requested by an application as cached elements in a local cache on the mobile device to satisfy subsequent requests made by the application.
  • the cache appropriateness decision engine 246 further based on detected patterns of requests sent from the mobile device 250 (e.g., by a application (e.g., a mobile application) or other types of clients on the device 250 ) and/or patterns of received responses can detect predictability in requests and/or responses. If the requests are made with some identifiable pattern (e.g., regular intervals, intervals having a detectable pattern, or trend (e.g., increasing, decreasing, constant) etc.) the timing predictor 246 a can determine that the requests made by a given application on a device is predictable and identify it to be potentially appropriate for caching, at least from a timing standpoint.
  • some identifiable pattern e.g., regular intervals, intervals having a detectable pattern, or trend (e.g., increasing, decreasing, constant) etc.
  • An identifiable pattern or trend can generally include any application or client behavior which may be simulated either locally, for example, on the local proxy 275 on the mobile device 250 or simulated remotely, for example, by the proxy server 325 on the host 300 , or a combination of local and remote simulation to emulate application behavior.
  • the local proxy 175 can begin to cache responses on a third request when the response delay times for the first two responses are the same, substantially the same, or detected to be increasing in intervals.
  • Increasing response delays with same responses for long polls can indicate a hunting period (e.g., a period in which the application/client on the mobile device is seeking the longest time between a request and response that a given network will allow, a timing diagram showing timing characteristics is illustrated in FIG. 8 ), as detected by the long poll hunting detector 238 c of the application behavior detector 236 .
  • a hunting period e.g., a period in which the application/client on the mobile device is seeking the longest time between a request and response that a given network will allow, a timing diagram showing timing characteristics is illustrated in FIG. 8 .
  • T indicates the delay time between when a request is sent and when a response (e.g., the response header) is detected/received for consecutive requests:
  • this may indicate a hunting pattern for a long poll when network timeout has not yet been reached or exceeded. Furthermore, if the responses R 0 , R 1 , and R 2 received for the three requests are the same, R 2 can be cached. In this example, R 2 is cached during the long poll hunting period, without waiting for the long poll to settle, thus expediting response caching (e.g., this is optional accelerated caching behavior which can be implemented for all or select applications).
  • the local proxy 275 can specify information that can be extracted from the timing sequence shown above (e.g., polling schedule, polling interval, polling type) to the proxy server and begin caching and to request the proxy server to begin polling and monitoring the source (e.g., using any of T 0 , T 1 , T 2 as polling intervals but typically T 2 , or the largest detected interval without timing out, and for which responses from the source is received will be sent to the proxy server 325 of FIG. 3A for use in polling the content source (e.g., application server/service provider 310 )).
  • the content source e.g., application server/service provider 310
  • the application e.g., a mobile application
  • client may still be hunting for a time interval for which a response can be reliably received from the content source (e.g., application/server server/provider 110 or 310 ), and as such caching typically should not begin until the request/response intervals indicate the same time interval or an increasing time interval, for example, for a long poll type request.
  • content source e.g., application/server server/provider 110 or 310
  • T indicates the delay time between when a request is sent and when a response (e.g., the response header) is detected/received for consecutive requests:
  • T 3 Time out at 700 s. (+/ ⁇ tolerance)
  • T 3 likely exceeded the network time out during a long poll hunting period.
  • a response likely was not received since the connection was terminated by the network, application, server, or other reason before a response was sent or available.
  • the local proxy 275 can then use the response for caching (if the content repeatability condition is met).
  • the local proxy can also use T 4 as the poll interval in the polling schedule set for the proxy server to monitor/poll the content source.
  • caching can begin while long polls are in hunting mode in the event of detecting increasing response delays, as long as responses are received and not timed out for a given request. This can be referred to as the optional accelerated caching during long poll hunting. Caching can also begin after the hunting mode (e.g., after the poll requests have settled to a constant or near constant delay value) has completed. Note that hunting may or may not occur for long polls and when hunting occurs, the proxy 275 can generally detect this and determine whether to begin to cache during the hunting period (increasing intervals with same responses) or wait until the hunt settles to a stable value.
  • the timing predictor 246 a of the cache appropriateness decision engine 246 can track timing of responses received from outgoing requests from a application (e.g., a mobile application) or client, to detect any identifiable patterns which can be partially wholly reproducible, such that locally cached responses can be provided to the requesting client on the mobile device 250 in a manner that simulates content source (e.g., application server/content provider 110 or 310 ) behavior. For example, the manner in which (e.g., from a timing standpoint) responses or content would be delivered to the requesting application/client on the device 250 . This ensures preservation of user experience when responses to application or mobile client requests are served from a local and/or remote cache instead of being retrieved/received directly from the content source (e.g., application, content provider 110 or 310 ).
  • the decision engine 246 or the timing predictor 246 a determines the timing characteristics a given application (e.g., a mobile application) or client from, for example, the request/response tracking engine 238 a and/or the application profile generator 239 (e.g., the response delay interval tracker 239 a ). Using the timing characteristics, the predictor 246 a determines whether the content received in response to the requests are suitable or are potentially suitable for caching.
  • a given application e.g., a mobile application
  • the application profile generator 239 e.g., the response delay interval tracker 239 a
  • poll request intervals between two consecutive requests from a given application can be used to determine whether request intervals are repeatable (e.g., constant, near constant, increasing with a pattern, decreasing with a pattern, etc.) and can be predicted and thus reproduced at least some of the times either exactly or approximated within a tolerance level.
  • the timing characteristics of a given request type for a specific application, or for multiple requests of an application, or for multiple applications can be stored in the application profile repository 242 .
  • the application profile repository 242 can generally store any type of information or metadata regarding application request/response characteristics including timing patterns, timing repeatability, content repeatability, etc.
  • the application profile repository 242 can also store metadata indicating the type of request used by a given application (e.g., long polls, long-held HTTP requests, HTTP streaming, push, COMET push, etc.)
  • Application profiles indicating request type by applications can be used when subsequent same/similar requests are detected, or when requests are detected from an application which has already been categorized. In this manner, timing characteristics for the given request type or for requests of a specific application which has been tracked and/or analyzed, need not be reanalyzed.
  • Application profiles can be associated with a time-to-live (e.g., or a default expiration time).
  • a time-to-live e.g., or a default expiration time
  • the use of an expiration time for application profiles, or for various aspects of an application or request's profile can be used on a case by case basis.
  • the time-to-live or actual expiration time of application profile entries can be set to a default value or determined individually, or a combination thereof.
  • Application profiles can also be specific to wireless networks, physical networks, network operators, or specific carriers, for example.
  • a given application profile may also be treated or processed differently (e.g., different behavior of the local proxy 275 and the remote proxy 325 ) depending on the mobile account associated with a mobile device from which the application is being accessed. For example, a higher paying account, or a premier account may allow more frequent access of the wireless network or higher bandwidth allowance thus affecting the caching policies implemented between the local proxy 275 and proxy server 325 with an emphasis on better performance compared to conservation of resources.
  • a given application profile may also be treated or processed differently under different wireless network conditions (e.g., based on congestion or network outage, etc.).
  • the cache appropriateness decision engine 246 can definitively identify repeatability or identify indications of repeatability, potential repeatability, or predictability in responses received from a content source (e.g., the content host/application server 110 shown in the example of FIG. 1A-B ). Repeatability can be detected by, for example, tracking at least two responses received from the content source and determines if the two responses are the same. The two responses may or may not be responses sent in response to consecutive requests. In one embodiment, hash values of the responses received for requests from a given application are used to determine repeatability of content (with or without heuristics) for the application in general and/or for the specific request. Additional same responses may be required for some applications or under certain circumstances.
  • Repeatability in received content need not be 100% ascertained.
  • responses can be determined to be repeatable if a certain number or a certain percentage of responses are the same, or similar.
  • the certain number or certain percentage of same/similar responses can be tracked over a select period of time, set by default or set based on the application generating the requests (e.g., whether the application is highly dynamic with constant updates or less dynamic with infrequent updates). Any indicated predictability or repeatability, or possible repeatability can be utilized by the distributed system in caching content to be provided to a requesting application or client on the mobile device 250 ,
  • cache appropriateness can be determined, tracked, and managed for multiple clients or applications on the mobile device 250 . Cache appropriateness can also be determined for different requests or request types initiated by a given client or application on the mobile device 250 .
  • the caching policy manager 245 along with the timing predictor 246 a and/or the content predictor 246 b which heuristically determines or estimates predictability or potential predictability, can track, manage and store cacheability information for various application or various requests for a given application.
  • Cacheability information may also include conditions (e.g., an application can be cached at certain times of the day, or certain days of the week, or certain requests of a given application can be cached, or all requests with a given destination address can be cached) under which caching is appropriate which can be determined and/or tracked by the cache appropriateness decision engine 246 and stored and/or updated when appropriate in the application cache policy repository 243 coupled to the cache appropriateness decision engine 246 .
  • conditions e.g., an application can be cached at certain times of the day, or certain days of the week, or certain requests of a given application can be cached, or all requests with a given destination address can be cached
  • the information in the application cache policy repository 243 regarding cacheability of requests, applications, and/or associated conditions can be used later on when same requests are detected.
  • the decision engine 246 , and/or the timing and content predictors 246 a/b need not track and reanalyze request/response timing and content characteristics to make an assessment regarding cacheability.
  • the cacheability information can in some instances be shared with local proxies of other mobile devices, by way of direct communication or via the host server (e.g., proxy server 325 of host server 300 ).
  • cacheability information detected by the local proxy 275 on various mobile devices can be sent to a remote host server or a proxy server 325 on the host server (e.g., host server 300 or proxy server 325 shown in the example of FIG. 3A , host 100 and proxy server 125 in the example of FIG. 1A-B ).
  • the remote host or proxy server can then distribute the information regarding application-specific, request-specific cacheability information and/or any associated conditions to various mobile devices or their local proxies in a wireless network or across multiple wireless networks (same service provider or multiple wireless service providers) for their use.
  • the selection criteria can further include, by way of example, but not limitation, state of the mobile device indicating whether the mobile device is active or inactive, network conditions, and/or radio coverage statistics.
  • the cache appropriateness decision engine 246 can any one or any combination of the criteria, and in any order, in identifying sources for which caching may be suitable.
  • the cache policy manager 245 can proceed to cache the associated content received from the identified sources by storing content received from the content source as cache elements in a local cache (e.g., local cache 185 or 285 shown in the examples of FIG. 1B and FIG. 2A , respectively) on the mobile device 250 .
  • the content source can also be identified to a proxy server (e.g., proxy server 125 or 325 shown in the examples of FIG. 1B and FIG. 3A , respectively) remote from and in wireless communication with the mobile device 250 such that the proxy server can monitor the content source (e.g., application server/content provider 110 ) for new or changed data.
  • the local proxy e.g., the local proxy 175 or 275 of FIG. 1B and FIG. 2A , respectively
  • the local proxy can identify to the proxy server that content received from a specific application server/content provider is being stored as cached elements in the local cache.
  • the cache policy manager 245 can, upon receiving future polling requests to contact the application server/content host (e.g., 110 or 310 ), can retrieve the cached elements from the local cache to respond to the polling request made at the mobile device 250 such that a radio of the mobile device is not activated to service the polling request.
  • Such servicing and fulfilling application e.g., a mobile application
  • requests locally via a local cache entries allow for more efficient resource and mobile network traffic utilization and management since network bandwidth and other resources need not be used to request/receive poll responses which may have not changed from a response that has already been received at the mobile device 250 .
  • the local proxy 275 upon receipt of an outgoing request from its mobile device 250 or from an application or other type of client on the mobile device 250 can intercept the request and determine whether a cached response is available in the local cache 285 of the mobile device 250 . If so, the outgoing request is responded to, by the local proxy 275 using the cached response on the cache of the mobile device. As such, the outgoing request can be filled or satisfied without a need to send the outgoing request over the wireless network, thus conserving network resources and battery consumption.
  • the responding to the requesting application/client on the device 250 is timed to correspond to a manner in which the content server would have responded to the outgoing request over a persistent connection (e.g., over the persistent connection, or long-held HTTP connection, long poll type connection, that would have been established absent interception by the local proxy).
  • the timing of the response can be emulated or simulated by the local proxy 275 to preserve application behavior such that end user experience is not affected, or minimally affected by serving stored content from the local cache 285 rather than fresh content received from the intended content source (e.g., content host/application server 110 of FIG. 1A-B ).
  • the timing can be replicated exactly or estimated within a tolerance parameter, which may go unnoticed by the user or treated similarly by the application so as to not cause operation issues.
  • the outgoing request can be a request for a persistent connection intended for the content server (e.g., application server/content provider of examples of FIG. 1A-1B ).
  • a persistent connection e.g., long poll, COMET-style push or any other push simulation in asynchronous HTTP requests, long-held HTTP request, HTTP streaming, or others
  • server a content source
  • the connection is held for some time after a request is sent.
  • the connection can typically be persisted between the mobile device and the server until content is available at the server to be sent to the mobile device.
  • the connection may also terminate due to network reasons (e.g., socket closure) if a response is not sent.
  • the manner of response of the content server can be simulated by allowing a time interval to elapse before responding to the outgoing request with the cached response.
  • the length of the time interval can be determined on a request by request basis or on an application by application (client by client basis), for example.
  • the time interval is determined based on request characteristics (e.g., timing characteristics) of an application on the mobile device from which the outgoing request originates. For example, poll request intervals (e.g., which can be tracked, detected, determined by the long poll detector 238 a of the poll interval detector 238 ) can be used to determine the time interval to wait before responding to a request with a local cache entry and managed by the response scheduler 249 a.
  • request characteristics e.g., timing characteristics
  • the cache policy manager 245 includes a poll schedule generator 247 which can generate a polling schedule for one or more applications on the mobile device 250 .
  • the polling schedule can specify a polling interval that can be employed by the proxy server (e.g., proxy server 125 or 325 shown in the examples of FIG. 1B and FIG. 3A ) in monitoring the content source for one or more applications.
  • the polling schedule can be determined, for example, based on the interval between the polling requests directed to the content source from the mobile device.
  • the poll interval detector 238 of the application behavior detector 236 can monitor polling requests directed to a content source from the mobile device 250 in order to determine an interval between the polling requests made from any or all applications (e.g., including mobile applications).
  • the poll interval detector 238 can track requests and responses for applications or clients on the device 250 .
  • consecutive requests are tracked prior to detection of an outgoing request initiated from the application (e.g., a mobile application) on the mobile device 250 , by the same mobile client or application.
  • an outgoing request from a mobile device 250 is detected to be for a persistent connection (e.g., a long poll, COMET style push, and long-held (HTTP) request) based on timing characteristics of prior requests from the same application or client on the mobile device 250 .
  • requests and/or corresponding responses can be tracked by the request/response tracking engine 238 b of the long poll detector 238 a of the poll interval detector 238 .
  • the timing characteristics of the consecutive requests can be determined to set up a polling schedule for the application or client.
  • the polling schedule can be used to monitor the content source (content source/application server) for content changes such that cached content stored on the local cache in the mobile device 250 can be appropriated managed (e.g., updated or discarded).
  • the timing characteristics can include, for example, a response delay time (‘D’) and/or an idle time (‘IT’).
  • response/request tracking engine 238 b can track requests and responses to determine, compute, and/or estimate, the timing diagrams for applicant or client requests.
  • the response/request tracking engine 238 b detects a first request (Request 0 ) initiated by a client on the mobile device and a second request (Request 1 ) initiated by the client on the mobile device after a response is received at the mobile device responsive to the first request.
  • the second request is one that is subsequent to the first request.
  • the relationship between requests can be seen in the following timing diagrams of FIG. 17A-17B .
  • the response/request tracking engine 238 b can track requests and responses to determine, compute, and/or estimate, the timing diagrams for applicant or client requests.
  • the response/request tracking engine 238 b can detect a first request initiated by a client on the mobile device and a second request initiated by the client on the mobile device after a response is received at the mobile device responsive to the first request.
  • the second request is one that is subsequent to the first request.
  • the response/request tracking engine 238 b further determines relative timings between the first, second requests, and the response received in response to the first request.
  • the relative timings can be used by the long poll detector 238 a to determine whether requests generated by the application are long poll requests.
  • the first and second requests that are used by the response/request tracking engine 238 b in computing the relative timings are selected for use after a long poll hunting period has settled or in the event when long poll hunting does not occur.
  • Timing characteristics that are typical of a long poll hunting period is illustrated in the example of FIG. 8 and can be, for example, detected by the long poll hunting detector 238 c .
  • the long poll hunting detector 238 c can identify or detect hunting mode, by identifying increasing request intervals (e.g., increasing delays), for example.
  • the long poll hunting detector 238 a can also detect hunting mode by detecting increasing request intervals, followed by a request with no response (e.g., connection timed out), or by detecting increasing request intervals followed by a decrease in the interval.
  • the long poll hunting detector 238 c can apply a filter value or a threshold value to request-response time delay value (e.g., an absolute value) above which the detected delay can be considered to be a long poll request-response delay
  • the filter value can be any suitable value characteristic of long polls and/or network conditions (e.g., 2 s, 5 s, 10 s, 15 s, 20 s., etc.) can be used as a filter or threshold value.
  • the response delay time (‘D’) refers to the start time to receive a response after a request has been sent and the idle refers to time to send a subsequent request after the response has been received.
  • the outgoing request is detected to be for a persistent connection based on a comparison (e.g., performed by the tracking engine 238 b ) of the response delay time relative (‘D’) or average of (‘D’) (e.g., any average over any period of time) to the idle time (‘IT’), for example, by the long poll detector 238 a .
  • the number of averages used can be fixed, dynamically adjusted, or changed over a longer period of time.
  • the requests initiated by the client are determined to be long poll requests if the response delay time interval is greater than the idle time interval (D>IT or D>>IT).
  • the tracking engine 238 b of the long poll detector computes, determines, or estimates the response delay time interval as the amount of time elapsed between time of the first request and initial detection or full receipt of the response.
  • a request is detected to be for a persistent connection when the idle time (‘IT’) is short since persistent connections, established in response to long poll requests or long poll HTTP requests, for example, can also be characterized in detecting immediate or near-immediate issuance of a subsequent request after receipt of a response to a previous request (e.g., IT ⁇ 0).
  • the idle time (‘IT”) can also be used to detect such immediate or near-immediate re-request to identify long poll requests.
  • the absolute or relative timings determined by the tracking engine 238 b are used to determine whether the second request is immediately or near-immediately re-requested after the response to the first request is received.
  • a request may be categorized as a long poll request if D+RT+IT ⁇ D+RT since IT is small for this to hold true.
  • IT may be determined to be small if it is less than a threshold value.
  • the threshold value could be fixed or calculated over a limited time period (a session, a day, a month, etc.), or calculated over a longer time period (e.g., several months or the life of the analysis).
  • the average IT can be determined, and the threshold can be determined using this average IT (e.g., the average IT less a certain percentage may be used as the threshold).
  • a fixed threshold can take upon any value including by way of example but not limitation (e.g., 1 s. 2 s. 3 s. . . . etc.).
  • the long poll detector 238 a can compare the relative timings (e.g., determined by the tracker engine 238 b ) to request-response timing characteristics for other applications to determine whether the requests of the application are long poll requests. For example, the requests initiated by a client or application can be determined to be long poll requests if the response delay interval time (‘D’) or the average response delay interval time (e.g., averaged over x number of requests or any number of delay interval times averaged over x amount of time) is greater than a threshold value.
  • D response delay interval time
  • the average response delay interval time e.g., averaged over x number of requests or any number of delay interval times averaged over x amount of time
  • the threshold value can be determined using response delay interval times for requests generated by other clients, for example by the request/response tracking engine 238 b and/or by the application profile generator 239 (e.g., the response delay interval tracker 239 a ).
  • the other clients may reside on the same mobile device and the threshold value is determined locally by components on the mobile device.
  • the threshold value can be determined for all requests over all resources server over all networks, for example.
  • the threshold value can be set to a specific constant value (e.g., 30 seconds, for example) to be used for all requests, or any request which does not have an applicable threshold value (e.g., long poll is detected if D>30 seconds).
  • the other clients reside on different mobile devices and the threshold can be determined by a proxy server (e.g., proxy server 325 of the host 300 shown in the example of FIG. 3A-B ) which is external to the mobile device and able to communicate over a wireless network with the multiple different mobile devices, as will be further described with reference to FIG. 3B .
  • a proxy server e.g., proxy server 325 of the host 300 shown in the example of FIG. 3A-B
  • the threshold can be determined by a proxy server (e.g., proxy server 325 of the host 300 shown in the example of FIG. 3A-B ) which is external to the mobile device and able to communicate over a wireless network with the multiple different mobile devices, as will be further described with reference to FIG. 3B .
  • the cache policy manager 245 sends the polling schedule to the proxy server (e.g., proxy server 125 or 325 shown in the examples of FIG. 1B and FIG. 3A ) and can be used by the proxy server in monitoring the content source, for example, for changed or new content (updated response different from the cached response associated with a request or application).
  • a polling schedule sent to the proxy can include multiple timing parameters including but not limited to interval (time from request 1 to request 2 ), a time out interval (time to wait for response, used in long polls, for example). Referring to the timing diagram of a request/response timing sequence shown in the example of FIG. 17A-B , the timing intervals ‘RI’, ‘D’, ‘RT’, and/or ‘IT’, or some statistical manipulation of the above values (e.g., average, standard deviation, etc.) may all or in part be sent to the proxy server.
  • the timing intervals ‘RI’, ‘D’, ‘RT’, and/or ‘IT’ may all or in part
  • the various timing intervals in a request/response timing sequence can be sent to the proxy server 325 for use in polling the content source (e.g., application server/content host 110 ).
  • the local proxy 275 can also identify to the proxy server 325 that a given application or request to be monitored is a long poll request (e.g., instructing the proxy server to set a ‘long poll flag’, for example).
  • the proxy server uses the various timing intervals to determine when to send keep-alive indications on behalf of mobile devices.
  • the local cache invalidator 244 of the caching policy manager 245 can invalidate cache elements in the local cache (e.g., cache 185 or 285 ) when new or changed data (e.g., updated response) is detected from the application server/content source for a given request.
  • the cached response can be determined to be invalid for the outgoing request based on a notification received from the proxy server (e.g., proxy 325 or the host server 300 ).
  • the source which provides responses to requests of the mobile client can be monitored to determine relevancy of the cached response stored in the cache of the mobile device 250 for the request.
  • the cache invalidator 244 can further remove/delete the cached response from the cache of the mobile device when the cached response is no longer valid for a given request or a given application.
  • the cached response is removed from the cache after it is provided once again to an application which generated the outgoing request after determining that the cached response is no longer valid.
  • the cached response can be provided again without waiting for the time interval or provided again after waiting for a time interval (e.g., the time interval determined to be specific to emulate the response delay in a long poll).
  • the time interval is the response delay ‘D’ or an average value of the response delay ‘D’ over two or more values.
  • the new or changed data can be, for example, detected by the proxy server (e.g., proxy server 125 or 325 shown in the examples of FIG. 1B and FIG. 3A ).
  • the proxy server e.g., proxy server 125 or 325 shown in the examples of FIG. 1B and FIG. 3A .
  • the use of the radio on the mobile device 250 can be enabled (e.g., by the local proxy or the cache policy manager 245 ) to satisfy the subsequent polling requests, as further described with reference to the interaction diagram of FIG. 4B .
  • the cache policy manager 245 includes a cache or connect selection engine 249 which can decide whether to use a locally cached entry to satisfy a poll/content request generated at the mobile device 250 by an application or widget.
  • the local proxy 275 or the cache policy manger 245 can intercept a polling request, made by an application (e.g., mobile application) on the mobile device, to contact the application server/content provider.
  • the selection engine 249 can determine whether the content received for the intercepted request has been locally stored as cache elements for deciding whether the a radio of the mobile device needs to be activated to satisfy the request made by the application (e.g., a mobile application) and also determine whether the cached response is still valid for the outgoing request prior to responding to the outgoing request using the cached response.
  • the local proxy 275 in response to determining that relevant cached content exists and is still valid, can retrieve the cached elements from the local cache to provide a response to the application which made the polling request such that a radio of the mobile device is not activated to provide the response to the application.
  • the local proxy 275 continues to provide the cached response each time the outgoing request is received until the updated response different from the cached response is detected.
  • a new request for a given request is transmitted over the wireless network for an updated response.
  • the request can be transmitted to the application server/content provider (e.g., server/host 110 ) or the proxy server on the host server (e.g., proxy 325 on the host 300 ) for a new and updated response.
  • the cached response can be provided again as a response to the outgoing request if a new response is not received within the time interval, prior to removal of the cached response from the cache on the mobile device; an example process flow is illustrated in the flow chart of FIG. 10 .
  • FIG. 3A depicts a block diagram illustrating an example of server-side components (host server 300 and proxy server 325 ) in a distributed proxy and cache system that manages traffic in a wireless network for resource conservation, content caching, and/or traffic management.
  • server-side components host server 300 and proxy server 325
  • FIG. 3A depicts a block diagram illustrating an example of server-side components (host server 300 and proxy server 325 ) in a distributed proxy and cache system that manages traffic in a wireless network for resource conservation, content caching, and/or traffic management.
  • the host server 300 generally includes, for example, a network interface 308 and/or one or more repositories 312 , 314 , 316 .
  • server 300 may be any portable/mobile or non-portable device, server, cluster of computers and/or other types of processing units (e.g., any number of a machine shown in the example of FIG. 11 ) able to receive, transmit signals to satisfy data requests over a network including any wired or wireless networks (e.g., WiFi, cellular, Bluetooth, etc.).
  • wired or wireless networks e.g., WiFi, cellular, Bluetooth, etc.
  • the network interface 308 can include networking module(s) or devices(s) that enable the server 300 to mediate data in a network with an entity that is external to the host server 300 , through any known and/or convenient communications protocol supported by the host and the external entity. Specifically, the network interface 308 allows the server 308 to communicate with multiple devices including mobile phone devices 350 , and/or one or more application servers/content providers 310 .
  • the host server 300 can store information about connections (e.g., network characteristics, conditions, types of connections, etc.) with devices in the connection metadata repository 312 . Additionally, any information about third party application or content providers can also be stored in 312 . The host server 300 can store information about devices (e.g., hardware capability, properties, device settings, device language, network capability, manufacturer, device model, OS, OS version, etc.) in the device information repository 314 . Additionally, the host server 300 can store information about network providers and the various network service areas in the network service provider repository 316 .
  • connections e.g., network characteristics, conditions, types of connections, etc.
  • devices e.g., hardware capability, properties, device settings, device language, network capability, manufacturer, device model, OS, OS version, etc.
  • the host server 300 can store information about network providers and the various network service areas in the network service provider repository 316 .
  • the communication enabled by network interface 308 allows for simultaneous connections (e.g., including cellular connections) with devices 350 and/or connections (e.g., including wired/wireless, HTTP, Internet connections, LAN, WiFi, etc.) with content servers/providers 310 , to manage the traffic between devices 350 and content providers 310 , for optimizing network resource utilization and/or to conserver power (battery) consumption on the serviced devices 350 .
  • the host server 300 can communicate with mobile devices 350 serviced by different network service providers and/or in the same/different network service areas.
  • the host server 300 can operate and is compatible with devices 350 with varying types or levels of mobile capabilities, including by way of example but not limitation, 1G, 2G, 2G transitional (2.5G, 2.75G), 3G (IMT-2000), 3G transitional (3.5G, 3.75G, 3.9G), 4G (IMT-advanced), etc.
  • the network interface 308 can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G type networks such as, LTE, WiMAX, etc.), Bluetooth, WiFi, or any other network whether or not connected via a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, a bridge router, a hub, a digital media receiver, and/or a repeater.
  • a network adaptor card e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G type networks such as, LTE, WiMAX, etc.
  • the host server 300 can further include, server-side components of the distributed proxy and cache system which can include, a proxy server 325 and a server cache 335 .
  • the proxy server 325 can include an HTTP access engine 345 , a caching policy manager 355 , a proxy controller 365 , a traffic shaping engine 375 , a new data detector 347 and/or a connection manager 395 .
  • the HTTP access engine 345 may further include a heartbeat manager 398 the proxy controller 365 may further include a data invalidator module 358 the traffic shaping engine 375 may further include a control protocol 376 and a batching module 377 . Additional or less components/modules/engines can be included in the proxy server 325 and each illustrated component.
  • a “module,” “a manager,” a “handler,” a “detector,” an “interface,” a “controller,” a “normalizer,” a “generator,” an “invalidator,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor.
  • the module, manager, handler, detector, interface, controller, normalizer, generator, invalidator, or engine can be centralized or its functionality distributed.
  • the module, manager, handler, detector, interface, controller, normalizer, generator, invalidator, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor.
  • a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid.
  • Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.
  • the request may be intercepted and routed to the proxy server 325 , which is coupled to the device 350 and the application server/content provider 310 .
  • the proxy server is able to communicate with the local proxy (e.g., proxy 175 and 275 of the examples of FIG. 1 and FIG. 2 respectively) of the mobile device 350 , the local proxy forwards the data request to the proxy server 325 for, in some instances, further processing, and if needed, for transmission to the application server/content server 310 for a response to the data request.
  • the local proxy e.g., proxy 175 and 275 of the examples of FIG. 1 and FIG. 2 respectively
  • the host 300 or the proxy server 325 in the host server 300 can utilize intelligent information provided by the local proxy in adjusting its communication with the device in such a manner that optimizes use of network and device resources.
  • the proxy server 325 can identify characteristics of user activity on the device 350 to modify its communication frequency. The characteristics of user activity can be determined by, for example, the activity/behavior awareness module 366 in the proxy controller 365 , via information collected by the local proxy on the device 350 .
  • communication frequency can be controlled by the connection manager 395 of the proxy server 325 , for example, to adjust push frequency of content or updates to the device 350 .
  • push frequency can be decreased by the connection manager 395 when characteristics of the user activity indicate that the user is inactive.
  • the connection manager 395 can adjust the communication frequency with the device 350 to send data that was buffered as a result of decreased communication frequency, to the device 350 .
  • the proxy server 325 includes priority awareness of various requests, transactions, sessions, applications, and/or specific events. Such awareness can be determined by the local proxy on the device 350 and provided to the proxy server 325 .
  • the priority awareness module 367 of the proxy server 325 can generally assess the priority (e.g., including time-criticality, time-sensitivity, etc.) of various events or applications; additionally, the priority awareness module 367 can track priorities determined by local proxies of devices 350 .
  • the connection manager 395 can further modify communication frequency (e.g., use or radio as controlled by the radio controller 396 ) of the server 300 with the devices 350 .
  • the server 300 can notify the device 350 , thus requesting use of the radio if it is not already in use, when data or updates of an importance/priority level which meets a criteria becomes available to be sent.
  • the proxy server 325 can detect multiple occurrences of events (e.g., transactions, content, data received from server/provider 310 ) and allow the events to accumulate for batch transfer to device 350 .
  • Batch transfer can be cumulated and transfer of events can be delayed based on priority awareness and/or user activity/application behavior awareness, as tracked by modules 366 and/or 367 .
  • batch transfer of multiple events (of a lower priority) to the device 350 can be initiated by the batching module 377 when an event of a higher priority (meeting a threshold or criteria) is detected at the server 300 .
  • batch transfer from the server 300 can be triggered when the server receives data from the device 350 , indicating that the device radio is already in use and is thus on.
  • the proxy server 325 can order the each messages/packets in a batch for transmission based on event/transaction priority, such that higher priority content can be sent first, in case connection is lost or the battery dies, etc.
  • the server 300 caches data (e.g., as managed by the caching policy manager 355 ) such that communication frequency over a network (e.g., cellular network) with the device 350 can be modified (e.g., decreased).
  • the data can be cached, for example in the server cache 335 , for subsequent retrieval or batch sending to the device 350 to potentially decrease the need to turn on the device 350 radio.
  • the server cache 335 can be partially or wholly internal to the host server 300 , although in the example of FIG. 3A , it is shown as being external to the host 300 .
  • the server cache 335 may be the same as and/or integrated in part or in whole with another cache managed by another entity (e.g., the optional caching proxy server 199 shown in the example of FIG. 1B ), such as being managed by an application server/content provider 110 , a network service provider, or another third party.
  • another entity e.g., the optional caching proxy server 199 shown in the example of FIG. 1B
  • the optional caching proxy server 199 shown in the example of FIG. 1B
  • an application server/content provider 110 e.g., a network service provider, or another third party.
  • content caching is performed locally on the device 350 with the assistance of host server 300 .
  • proxy server 325 in the host server 300 can query the application server/provider 310 with requests and monitor changes in responses. When changed or new responses are detected (e.g., by the new data detector 347 ), the proxy server 325 can notify the mobile device 350 , such that the local proxy on the device 350 can make the decision to invalidate (e.g., indicated as out-dated) the relevant cache entries stored as any responses in its local cache.
  • the data invalidator module 368 can automatically instruct the local proxy of the device 350 to invalidate certain cached data, based on received responses from the application server/provider 310 . The cached data is marked as invalid, and can get replaced or deleted when new content is received from the content server 310 .
  • data change can be detected by the detector 347 in one or more ways.
  • the server/provider 310 can notify the host server 300 upon a change.
  • the change can also be detected at the host server 300 in response to a direct poll of the source server/provider 310 .
  • the proxy server 325 can in addition, pre-load the local cache on the device 350 with the new/updated data. This can be performed when the host server 300 detects that the radio on the mobile device is already in use, or when the server 300 has additional content/data to be sent to the device 350 .
  • One or more the above mechanisms can be implemented simultaneously or adjusted/configured based on application (e.g., different policies for different servers/providers 310 ).
  • the source provider/server 310 may notify the host 300 for certain types of events (e.g., events meeting a priority threshold level).
  • the provider/server 310 may be configured to notify the host 300 at specific time intervals, regardless of event priority.
  • the proxy server 325 of the host 300 can monitor/track responses received for the data request from the content source for changed results prior to returning the result to the mobile device, such monitoring may be suitable when data request to the content source has yielded same results to be returned to the mobile device, thus preventing network/power consumption from being used when no new/changes are made to a particular requested.
  • the local proxy of the device 350 can instruct the proxy server 325 to perform such monitoring or the proxy server 325 can automatically initiate such a process upon receiving a certain number of the same responses (e.g., or a number of the same responses in a period of time) for a particular request.
  • the server 300 for example, through the activity/behavior awareness module 366 , is able to identify or detect user activity, at a device that is separate from the mobile device 350 .
  • the module 366 may detect that a user's message inbox (e.g., email or types of inbox) is being accessed. This can indicate that the user is interacting with his/her application using a device other than the mobile device 350 and may not need frequent updates, if at all.
  • a user's message inbox e.g., email or types of inbox
  • the server 300 can thus decrease the frequency with which new or updated content is sent to the mobile device 350 , or eliminate all communication for as long as the user is detected to be using another device for access.
  • Such frequency decrease may be application specific (e.g., for the application with which the user is interacting with on another device), or it may be a general frequency decrease (e.g., since the user is detected to be interacting with one server or one application via another device, he/she could also use it to access other services) to the mobile device 350 .
  • the host server 300 is able to poll content sources 310 on behalf of devices 350 to conserve power or battery consumption on devices 350 .
  • certain applications on the mobile device 350 can poll its respective server 310 in a predictable recurring fashion.
  • Such recurrence or other types of application behaviors can be tracked by the activity/behavior module 366 in the proxy controller 365 .
  • the host server 300 can thus poll content sources 310 for applications on the mobile device 350 , that would otherwise be performed by the device 350 through a wireless (e.g., including cellular connectivity).
  • the host server can poll the sources 310 for new or changed data by way of the HTTP access engine 345 to establish HTTP connection or by way of radio controller 396 to connect to the source 310 over the cellular network.
  • the new data detector can notify the device 350 that such data is available and/or provide the new/changed data to the device 350 .
  • the connection manager 395 determines that the mobile device 350 is unavailable (e.g., the radio is turned off) and utilizes SMS to transmit content to the device 350 , for instance via the SMSC shown in the example of FIG. 1B .
  • SMS is used to transmit invalidation messages, batches of invalidation messages, or even content in the case the content is small enough to fit into just a few (usually one or two) SMS messages. This avoids the need to access the radio channel to send overhead information.
  • the host server 300 can use SMS for certain transactions or responses having a priority level above a threshold or otherwise meeting a criteria.
  • the server 300 can also utilize SMS as an out-of-band trigger to maintain or wake-up an IP connection as an alternative to maintaining an always-on IP connection.
  • connection manager 395 in the proxy server 325 can generate and/or transmit heartbeat messages on behalf of connected devices 350 , to maintain a backend connection with a provider 310 for applications running on devices 350 .
  • local cache on the device 350 can prevent any or all heartbeat messages needed to maintain TCP/IP connections required for applications, from being sent over the cellular, or other network, and instead rely on the proxy server 325 on the host server 300 to generate and/or send the heartbeat messages to maintain a connection with the backend (e.g., application server/provider 110 in the example of FIG. 1A ).
  • the proxy server can generate the keep-alive (heartbeat) messages independent of the operations of the local proxy on the mobile device.
  • the repositories 312 , 314 , and/or 316 can additionally store software, descriptive data, images, system information, drivers, and/or any other data item utilized by other components of the host server 300 and/or any other servers for operation.
  • the repositories may be managed by a database management system (DBMS), for example but not limited to, Oracle, DB2, Microsoft Access, Microsoft SQL Server, PostgreSQL, MySQL, FileMaker, etc.
  • DBMS database management system
  • the repositories can be implemented via object-oriented technology and/or via text files, and can be managed by a distributed database management system, an object-oriented database management system (OODBMS) (e.g., ConceptBase, FastDB Main Memory Database Management System, JDOInstruments, ObjectDB, etc.), an object-relational database management system (ORDBMS) (e.g., Informix, OpenLink Virtuoso, VMDS, etc.), a file system, and/or any other convenient or known database management package.
  • OODBMS object-oriented database management system
  • ORDBMS object-relational database management system
  • FIG. 3B depicts a block diagram illustrating another example of components in the caching policy manager 355 in the proxy server 325 on the server-side of the distributed proxy system shown in the example of FIG. 3A .
  • the caching policy manager 355 can further include, an application protocol module 356 , a content source monitoring engine 357 having a poll schedule manager 358 , and/or an updated or new content detector 359 .
  • the poll schedule manager 358 further includes a host timing simulator 358 a and/or a long poll request detector/manager 358 b.
  • the proxy server (e.g., the proxy server 125 or 325 of the examples of FIG. 1B and FIG. 3A ) can monitor a content source for new or changed data, for example, via the monitoring engine 357 .
  • the proxy server is an entity external to the mobile device 250 of FIG. 2A-B .
  • the content source e.g., application server/content provider 110 of FIG. 1B
  • the content source can be monitored, for example, by the monitoring engine 357 at a frequency that is based on polling frequency of the content source at the mobile device.
  • the poll schedule can be, for example, generated by the local proxy and sent to the proxy server.
  • the poll frequency can be tracked and/or managed by the poll schedule manager 358 .
  • the proxy server can poll the host (e.g., content provider/application server) on behalf of the mobile device and simulate the polling behavior of the client to the host, via the host timing simulator 358 a .
  • the polling behavior can be simulated to include characteristics of a long poll request-response sequences experienced in a persistent connection with the host (e.g., by the long poll request detector/manager 358 b ).
  • the local proxy 275 on the device-side and/or the proxy server 325 on the server-side can verify whether application and application server/content host behavior match or can be represented by this predicted pattern.
  • the local proxy and/or the proxy server can detect deviations and when appropriate, re-evaluate and compute, determine, or estimate another polling interval.
  • the caching policy manager 355 on the server-side of the distribute proxy can, in conjunction with, or independent of the proxy server 275 on the mobile device, identify or detect long poll requests. For example, the caching policy manager 355 can determine a threshold value to be used in comparison with a response delay interval time (interval time ‘D’ shown in the example timing diagram of FIG.
  • 17A-B in a request-response sequence for an application request to identify or detect long poll requests, possible long poll requests (e.g., requests for a persistent connection with a host with which the client communicates, including but not limited to, a long-held HTTP request, a persistent connection enabling COMET style push, request for HTTP streaming, etc.), or other requests which can otherwise be treated as a long poll request.
  • possible long poll requests e.g., requests for a persistent connection with a host with which the client communicates, including but not limited to, a long-held HTTP request, a persistent connection enabling COMET style push, request for HTTP streaming, etc.
  • the threshold value can be determined by the proxy 325 using response delay interval times for requests generated by clients/applications across mobile devices which may be serviced by multiple different cellular or wireless networks. Since the proxy 325 resides on host 300 is able to communicate with multiple mobile devices via multiple networks, the caching policy manager 355 has access to application/client information at a global level which can be used in setting threshold values to categorize and detect long polls.
  • the caching policy manager 355 can set one or more threshold values to be used in comparison with response delay interval times for long poll detection.
  • Threshold values set by the proxy server 325 can be static or dynamic, and can be associated with conditions and/or a time-to-live (an expiration time/date in relative or absolute terms).
  • the caching policy manager 35 of the proxy 325 can determine the threshold value, in whole or in part, further based on network delays of a given wireless network, networks serviced by a given carrier (service provider), or multiple wireless networks.
  • the proxy 325 can also determine the threshold value for identification of long poll requests based on delays of one or more application server/content provider (e.g., 110 ) to which application, mobile application, or mobile client requests are directed.
  • the proxy server can detect new or changed data at a monitored content source and transmits a message to the mobile device notifying it of such a change such that the mobile device (or the local proxy on the mobile device) can take appropriate action (e.g., to invalidate the cache elements in the local cache.
  • the proxy server e.g., the caching policy manager 355
  • the proxy server upon detecting new or changed data, can also store the new or changed data in its cache (e.g., the server cache 135 or 335 of the examples of FIG. 1B and FIG. 3A , respectively).
  • the new/updated data stored in the server cache can in some instances, be used to satisfy content requests at the mobile device, for example, after the proxy server has notified the mobile device of the new/changed content and that the locally cached content has been invalidated.
  • FIG. 4A depicts a diagram showing how data requests from a mobile device 450 to an application server/content provider 495 in a wireless network can be coordinated by a distributed proxy system 460 in a manner such that network and battery resources are conserved through using content caching and monitoring performed by the distributed proxy system 460 .
  • the mobile device 450 In satisfying application or client requests on a mobile device 450 without the distributed proxy system 460 , the mobile device 450 , or the software widget executing on the device 450 performs a data request 402 (e.g., an HTTP GET, POST, or other request) directly to the application server 495 and receives a response 404 directly from the server/provider 495 . If the data has been updated, the widget on the mobile device 450 can refreshes itself to reflect the update and waits for small period of time and initiates another data request to the server/provider 495 .
  • a data request 402 e.g., an HTTP GET, POST, or other request
  • the widget on the mobile device 450 can refreshes itself to reflect the update and waits for small period of time and initiates another data request to the server/provider 495 .
  • the requesting client or software widget 455 on the device 450 can utilize the distributed proxy system 460 in handling the data request made to server/provider 495 .
  • the distributed proxy system 460 can include a local proxy 465 (which is typically considered a client-side component of the system 460 and can reside on the mobile device 450 ), a caching proxy 475 (considered a server-side component 470 of the system 460 and can reside on the host server 485 or be wholly or partially external to the host server 485 ), a host server 485 .
  • the local proxy 465 can be connected to the caching proxy 475 and host server 485 via any network or combination of networks.
  • the widget 455 can perform the data request 406 via the local proxy 465 .
  • the local proxy 465 can intercept the requests made by device applications, and can identify the connection type of the request (e.g., an HTTP get request or other types of requests).
  • the local proxy 465 can then query the local cache for any previous information about the request (e.g., to determine whether a locally stored response is available and/or still valid). If a locally stored response is not available or if there is an invalid response stored, the local proxy 465 can update or store information about the request, the time it was made, and any additional data, in the local cache. The information can be updated for use in potentially satisfying subsequent requests.
  • the local proxy 465 can then send the request to the host server 485 and the host server 485 can perform the request 406 and returns the results in response 408 .
  • the local proxy 465 can store the result and in addition, information about the result and returns the result to the requesting widget 455 .
  • the local proxy 465 can notify 410 the server 485 that the request should be monitored (e.g., steps 412 and 414 ) for result changes prior to returning a result to the local proxy 465 or requesting widget 455 .
  • the local proxy 465 can now store the results into the local cache. Now, when the data request 416 , for which a locally response is available, is made by the widget 455 and intercepted at the local proxy 465 , the local proxy 465 can return the response 418 from the local cache without needing to establish a connection communication over the wireless network.
  • the server proxy performs the requests marked for monitoring 420 to determine whether the response 422 for the given request has changed.
  • the host server 485 can perform this monitoring independently of the widget 455 or local proxy 465 operations. Whenever an unexpected response 422 is received for a request, the server 485 can notify the local proxy 465 that the response has changed (e.g., the invalidate notification in step 424 ) and that the locally stored response on the client should be erased or replaced with a new response.
  • a subsequent data request 426 by the widget 455 from the device 450 results in the data being returned from host server 485 (e.g., via the caching proxy 475 ) and in step 428 , the request is satisfied from the caching proxy 475 .
  • the wireless (cellular) network is intelligently used when the content/data for the widget or software application 455 on the mobile device 450 has actually changed. As such, the traffic needed to check for the changes to application data is not performed over the wireless (cellular) network. This reduces the amount of generated network traffic and shortens the total time and the number of times the radio module is powered up on the mobile device 450 , thus reducing battery consumption, and in addition, frees up network bandwidth.
  • FIG. 4B depicts an interaction diagram showing how application polls having data requests made by an application/widget 455 (e.g., mobile application) on a mobile device to an application server/content provider 495 in a wireless network can be cached on the local proxy 465 and managed by the distributed caching system (including local proxy 465 and the host server 485 (having server cache 435 or caching proxy server 475 ).
  • an application/widget 455 e.g., mobile application
  • the application/widget 455 e.g., mobile application/widget
  • the poll can locally be intercepted 434 on the mobile device by local proxy 465 .
  • the local proxy 465 can detect that the cached content is available for the polled content in the request and can thus retrieve a response from the local cache to satisfy the intercepted poll 436 , without requiring use of wireless network bandwidth or other wireless network resources.
  • the application/widget 455 e.g., mobile application/widget
  • the application/widget 455 polls the application server/provider 440 .
  • the poll is intercepted 442 by the local proxy 465 and detects that cache content is unavailable in the local cache and decides to set up the polled source for caching 444 .
  • the poll is forwarded to the content source 446 .
  • the application server/provider 495 receives the poll request from the application and provides a response to satisfy the current request 448 .
  • the mobile application/widget 455 receives the response from the application server/provider to satisfy the request.
  • the local proxy 465 tracks the polling frequency of the application and can set up a polling schedule to be sent to the host server 452 .
  • the local proxy sends the cache set up to the host server 454 .
  • the host server 485 can use the cache set up which includes, for example, an identification of the application server/provider to be polled and optionally a polling schedule 456 .
  • the host server 485 can now poll the application server/provider 495 to monitor responses to the request 458 , on behalf of the mobile device.
  • the application server receives the poll from the host server and responds 460 .
  • the host server 485 determines that the same response has been received and polls the application server 495 , for example, according to the specified polling schedule 462 .
  • the application server/content provider 495 receives the poll and responds accordingly 464 .
  • the host server 485 detects changed or new responses, and notifies the local proxy 465 .
  • the host server 485 can additional store the changed or new response in the server cache or caching proxy 468 .
  • the local proxy 465 receives notification from the host server 485 that new or changed data is now available and can invalidate the affected cache entries 470 .
  • the application/widget 455 e.g., mobile application/widget
  • the local proxy determines that no valid cache entry is available and instead retrieves a response from the server cache 474 , for example, through an HTTP connection.
  • the host server 485 receives the request for the new response and sends the response back to the local proxy 475 .
  • the request is thus satisfied from the server cache or caching proxy 478 without the need for the mobile device to utilize its radio or to consume mobile network bandwidth thus conserving network resources.
  • the local proxy 465 in response to determining that no valid cache entry is available, forwards the poll to the application server/provider 482 over the mobile network.
  • the application server/provider 495 receives the poll and sends the response back to the mobile device 484 over the mobile network. The request is thus satisfied from the server/provider using the mobile network 486 .
  • FIG. 5 depicts a diagram showing one example process for implementing a hybrid IP and SMS power saving mode on a mobile device 550 using a distributed proxy and cache system (e.g., such as the distributed system shown in the example of FIG. 1B ).
  • a distributed proxy and cache system e.g., such as the distributed system shown in the example of FIG. 1B .
  • the local proxy (e.g., proxy 175 in the example of FIG. 1B ) monitors the device for user activity.
  • server push is active. For example, always-on-push IP connection can be maintained and if available, SMS triggers can be immediately sent to the mobile device 550 as it becomes available.
  • the local proxy can adjust the device to go into the power saving mode.
  • the local proxy receives a message or a correspondence from a remote proxy (e.g., the server proxy 135 in the example of FIG. 1B ) on the server-side of the distributed proxy and cache system
  • the local proxy can respond with a call indicating that the device 550 is currently in power save mode (e.g., via a power save remote procedure call).
  • the local proxy can take the opportunity to notify multiple accounts or providers (e.g., 510 A, and 510 B) of the current power save status (e.g., timed to use the same radio power-on event).
  • the response from the local proxy can include a time (e.g., the power save period) indicating to the remote proxy (e.g., server proxy 135 ) and/or the application server/providers 510 A/B when the device 550 is next able to receive changes or additional data.
  • a default power savings period can be set by the local proxy.
  • the wait period communicated to the servers 510 A/B can be the existing period, rather than an incremented time period.
  • the remote proxy server upon receipt of power save notification from the device 550 , can stop sending changes (data or SMS's) for the period of time requested (the wait period).
  • any notifications received can be acted upon and changes sent to the device 550 , for example, as a single batched event or as individual events. If no notifications come in, then push can be resumed with the data or an SMS being sent to the device 550 .
  • the proxy server can time the poll or data collect event to optimize batch sending content to the mobile device 550 to increase the chance that the client will receive data at the next radio power on event.
  • the wait period can be updated in operation in real time to accommodate operating conditions.
  • the local proxy can adjust the wait period on the fly to accommodate the different delays that occur in the system.
  • Detection of user activity in step 508 at the device 550 causes the power save mode to be exited.
  • the device 550 exits power save mode, it can begin to receive any changes associated with any pending notifications. If a power saving period has expired, then no power save cancel call may be needed as the proxy server will already be in traditional push operation mode.
  • power save mode is not applied when the device 550 is plugged into a charger. This setting can be reconfigured or adjusted by the user or another party. In general, the power save mode can be turned on and off, for example, by the user via a user interface on device 550 . In general, timing of power events to receive data can be synchronized with any power save calls to optimize radio use.
  • FIG. 6 depicts another flow diagram 600 illustrating an example process for distributed content caching between a mobile device and a proxy server and the distributed management of content caching.
  • the disclosed technology is a distributed caching model with various aspects of caching tasks split between the client-side/mobile device side (e.g., mobile device 450 in the example of FIG. 4A ) and the server side (e.g., server side 470 including the host server 485 and/or the optional caching proxy 475 ).
  • client-side/mobile device side e.g., mobile device 450 in the example of FIG. 4A
  • server side e.g., server side 470 including the host server 485 and/or the optional caching proxy 475 .
  • the device-side responsibilities can include, deciding whether a response to a particular request can be and/or should be cached.
  • the device-side of the proxy can make this decision based on information (e.g., timing characteristics, detected pattern, detected pattern with heuristics, indication of predictability or repeatability) collected from/during both request and response, and cache it (e.g., storing it in a local cache on the mobile device).
  • the device side can also notify the server-side in the distributed cache system of the local cache event and notify it monitor the content source (e.g., application server/content provider 110 of FIG. 1A-B ).
  • the device side can further instruct the server side of the distributed proxy to periodically validate the cache response (e.g., by way of polling, or sending polling requests to the content source).
  • the device side can further decide whether a response to a particular cache request should be returned from the local cache (e.g., whether a cache hit is detected).
  • the decision can be made by the device side (e.g., the local proxy on the device) using information collected from/during request and/or responses received from the content source.
  • the server-side responsibilities can include, validating cached responses for relevancy (e.g., determine whether a cached response is still valid or relevant to its associated request).
  • the server-side can send the mobile device an invalidation request to notify the device side when a cached response is detected to be no longer valid or no longer relevant (e.g., the server invalidates a given content source).
  • the device side then can remove the response from the local cache.
  • the diagram of FIG. 6 illustrates caching logic processes performed for each detected or intercepted request (e.g., HTTP request) detected at a mobile device (e.g., client-side of the distributed proxy).
  • a mobile device e.g., client-side of the distributed proxy.
  • the client-side of the proxy e.g., local proxy 275 shown in FIG. 2A-B or mobile device 450 of FIG. 4A
  • receives a request from an application, mobile application or mobile client.
  • URL is normalized and in step the client-side checks to determine if the request is cacheable, in step 606 .
  • the request is sent to the source (application server/content provider) in step 608 and the response is received 610 and delivered to the requesting application 622 , similar to a request-response sequence without interception by the client side proxy.
  • the client-side looks up the cache to determine whether a cache entry exists for the current request. If so, in step 624 , the client-side can determine whether the entry is valid and if so, the client side can check the request to see if includes a validator (e.g., a modified header or an entity tag) in step 628 .
  • a validator e.g., a modified header or an entity tag
  • the concept of validation is eluded to in section 13.3 of RFC 2616 which describes in possible types of headers. and forms a validating response 632 if so to be delivered to the requesting application in step 622 .
  • a response is formed from the local cache in step 630 and delivered to the requesting application in step 622 .
  • This validation step can be used for content that would otherwise normally be considered un-cacheable.
  • the client side of the proxy sends the request to the content source (application server/content host) and receives a response directly fro the source in step 618 .
  • Alternative processing may be performed if the content is determined to include non-cacheable content.
  • the request is also sent in step 616 .
  • the client side checks the response to determine if it is cacheable in step 626 . If so, the response is cached in step 620 . The client then sends another poll in step 614 and then delivers the response to the requesting application in step 622 .
  • FIG. 7 depicts an interaction diagram showing cache management by a distributed proxy system 760 of content delivered to an application 755 (e.g., mobile application) over a long-held request while ensuring freshness of content delivered.
  • application 755 e.g., mobile application
  • the diagram illustrates an example process for how cached responses received in long-held requests (e.g., long-held HTTP request, long polls, or HTTP streaming) are provided to the requesting application 755 and management of expired/invalid/non-relevant cache entries.
  • a long-held request can be any request for a persistent connection that is held between the device and the server until a response is available at the server to be sent (or pushed) to the device.
  • the long-held request or long-held HTTP request can allow the device/server interaction to simulate content push over the persistent connection (e.g., COMET style push), for example, over a persisted connection over HTTP.
  • the application 755 sends a request which is detected and intercepted by the local proxy 765 on the mobile device 750 on the client/device-side of the proxy system 760 .
  • the request-response sequence 702 , 704 , 706 , and 708 shown occurs after a long poll hunting period, which may sometimes be performed by the application (e.g., a mobile application) sending long poll requests.
  • the long poll hunting period may or may not be performed, but when performed, allows the requesting application 755 to find the longest amount of time it can hold a request with the end server/provider 795 open before the connection times out (e.g., due to network reason, such as socket closures).
  • a timing diagram showing characteristics request-response timing sequences is further illustrated in the example of FIG. 8 .
  • the device proxy 750 or local proxy 765 is able to detect request-response pattern sequences initiated from the application 755 while long poll hunting and can wait until the hunting period has settled prior to caching responses from long poll request.
  • the request-response steps shown between 702 and 710 occur after any long poll hunting request/response pairs, if it was performed by the requesting application 755 .
  • the request is sent to the server/provider 795 in step 704 and the request times out or closes in 706 , when the server 795 sends a response in step 708 back to the application 755 on the device side 750 .
  • the response, when sent is also intercepted by the local proxy 760 on the mobile side 750 of the distributed proxy 760 , for local caching.
  • the local proxy 765 notifies the server-side 770 of the proxy of the system 760 and requests that the server-side 770 proxy (e.g., the host server 785 ) begin to monitor the server/provider 790 in step 712 .
  • the server-side proxy 770 now begins to send requests to the server/provider in order to monitor responses received 716 from the server/provider 795 .
  • the local proxy 765 determines that a local cache entry now exists and waits for a period of time (e.g., a long poll interval) 720 before providing the cached response back to the application 755 , in step 722 .
  • the local proxy 765 allows the period of time to elapse to simulate the actual behavior of the server/provider 795 with the application 755 , since in an actual long poll request which goes over the network, a response is not received until after some delay, characteristic of the given long poll.
  • another request is sent from the application (e.g., a mobile application) 755 when the response from the server/provider 795 in step 726 is validated.
  • the local proxy 765 waits for an interval in step 728 before replying with the cache entry in step 744 .
  • the server-side proxy 770 in monitoring responses sends a request in step 730 to the server/provider 795 and detects content change in the response received 732 from the server/provider 795 in step 734 .
  • the server-side 770 proxy thus caches the changed/updated response data at the server-side proxy in step 736 and notifies the local proxy 765 to invalidate the associated cache entry 738 .
  • the local proxy 765 in response to receiving an invalidation notice, sets the associated entry to be invalidated as being ‘transient’ in step 740 , or otherwise annotated or indicated to be marked for deletion or removal. At this point, the local proxy 765 replies to the application 755 again with the transient cache in step 744 .
  • the local proxy 765 also connects to the server-side proxy 770 to obtain the new cached data at the server-side 770 , in step 742 , and receives a response (the new/updated response) at step 746 .
  • the local proxy 765 now can reply with the response received from the server cache, in step 750 .
  • the application e.g., a mobile application
  • the subsequent request 752 is sent to the local proxy 765 for processing (e.g., forwarded to the application server/content provider 795 ) in step 754 .
  • FIG. 8 depicts a timing diagram 800 showing hunting mode behavior 805 in a long poll request and a timing diagram showing timing characteristics when the long poll has settled 810 .
  • the request times are held for an increasing amount of time (180, 360 . . . 1024 s.) until a request times out without receiving a response from the server (as shown in 802 , 804 , 806 , 808 ). After this time is detected, the request times are now held at some time less than the time it took for a time out (e.g., now 500 s.) and used to send future long poll requests.
  • the diagram 810 shows the timing characteristics of request/response pairs after the long poll hunting period has settled. These characteristics can be detected and identified in operation by the local proxy and/or the remote proxy for handling during caching.
  • the distributed caching system can either begin caching (optionally) while the application is still in long poll hunting mode, or begin caching after the hunting period 805 has completed and the application is in settled mode as in 810 .
  • the response is not cached until the local or remote proxy can verify that a subsequent received response meets cacheability conditions.
  • long poll hunting may or may not be performed by mobile apps or clients but the distributed system includes mechanisms to detect long poll hunting activity for application long polls and can simply ignore the long poll hunting requests and begin caching after the hunting period has elapsed and the long polls have settled at some constant or near constant interval value or apply logic to begin caching during the hunting period, thus enabling accelerated caching to enhance performance and improve user experience.
  • FIG. 9 depicts a flow chart illustrating an example process for caching content pushed to a mobile device in a persistent connection from a content server over a wireless network.
  • a request initiated from a mobile client on a mobile device is detected.
  • the request is detected to be a long poll request (e.g., long-held request, long-held-HTTP request) or one for any type of persistent connection (e.g., enabling push emulation by the server, COMET style push, HTTP streaming, etc.).
  • process 904 it is determined that a cached response is available on a cache of the mobile device for the request from the mobile device.
  • a content server is monitored for an updated response different from the cached response associated with the request, for example, by a proxy server able to establish wireless connectivity to the mobile device.
  • process 908 it is determined whether the cached response is still valid, prior to responding to the outgoing request using the cached response. If not, the process flow continues to process ‘A’ continued in the example of FIG. 10 .
  • the updated content/response for the outgoing request can be detected by the proxy server and also optionally cached at the proxy server for retrieval by the mobile device.
  • a time interval is allowed to elapse.
  • the time interval can be determined by a poll request interval by detecting, for example, the two consecutive requests from an application which generated the outgoing request from the mobile device.
  • the two consecutive requests can be tracked prior to detection of the outgoing request initiated from the application (e.g., a mobile application) on the mobile device.
  • process 912 to the outgoing request is responded to, using the cached response on the cache of the mobile device timed to correspond to a manner in which the content server would respond to the outgoing request.
  • the outgoing request can be filled without a need to send the outgoing request over the wireless network.
  • the request may still be sent over the network, for other reasons.
  • the manner of response of the content server can be simulated by allowing the time interval to elapse before responding to the outgoing request with the cached response.
  • the time interval can be determined based on request characteristics of an application on the mobile device from which the outgoing request originates.
  • the cached response is continued to be provided each time the outgoing request is received until the updated response different from the cached response is detected.
  • FIG. 10 depicts a diagram showing example processes that occur when removing a stored response from the local cache on a mobile device for a long poll request.
  • a cached response stored on the mobile device is no longer valid for a request.
  • the cached response can be determined to be invalid for an outgoing request based on a notification received from a proxy server coupled to the content server, which monitors the content server for updated responses that are different from the cached response stored at the local cache on the mobile device.
  • the cached response is simply removed from the cache, in process 1004 .
  • the cached response is provided again to an application which generated the outgoing request (immediately without waiting for a time interval), in process 1006 , and then removed from the cache in 1008 .
  • a time interval is allowed to elapse after determination of invalid cached response, in process 1010 . Then, the cached is provided once again to an application which generated the outgoing request in step 1012 , before removing the cached response from the cache in step 1014 .
  • a new response to the request is transmitted over the wireless network in step 1016 after determining that a cached response stored on the mobile device is no longer valid for the request.
  • a time interval is allowed to elapse in step 1018 before determining whether a response has been received from the host (step 1020 . If not, the cached response (the one determined to be no longer valid) is provided once again to an application in step 1022 which generated the outgoing request prior to removal from the cache, in step 1024
  • FIG. 11 depicts a flow chart illustrating an example process for using cached content provided over a long-held connection via a wireless network to satisfy mobile client requests on a mobile device.
  • indication of repeatability is detected in responses received for requests from a mobile client on a mobile device.
  • the repeatability can be determined when two responses received from the prior requests are the same. For example, hash values of the responses received for the prior requests are used to determined repeatability.
  • a cached response is stored on the mobile device for the mobile client, when the responses received in prior requests from the mobile client indicate repeatability in responses.
  • a request initiated from the mobile client is detected on the mobile device. The request is detected to be one for a long-held connection over which content is pushed to the mobile client when available.
  • the long held connection may be a long-held HTTP connection suited for content push from the content server.
  • process 1108 it is determined whether the cached response for the request is available on the mobile device. If so, in process 1110 , the manner in which a source to which the request is directed would respond to the request is simulated. In process 1112 , the request is responded to using the cached response already stored on the mobile device. For example, the cached response already on the mobile device is provided to the mobile client after a time interval has elapsed. In process 1114 , the request is satisfied without a need to send the request over the wireless network.
  • a source which provides responses to requests of the mobile client can be monitored to determine relevancy of the cached response stored in the cache of the mobile device for the request.
  • the source is monitored by an entity external from the mobile device.
  • FIG. 12 depicts a flow chart illustrating an example process for caching content received at a mobile device via a persistent connection over a wireless network.
  • a request generated by a application (e.g., a mobile application) on the mobile device is intercepted at the mobile device.
  • the request can be intercepted by a local proxy on the mobile device.
  • it is determined that the request is to establish the persistent connection with an application server hosting the application (e.g., a mobile application).
  • the outgoing request can be detected to be for the persistent connection based on timing characteristics of prior requests generated by a same application or client on the mobile device.
  • the timing characteristics can include, one or more of, a response delay time to receive a response after a request has been sent and an idle time to send a subsequent request after the response has been received.
  • the outgoing request is detected to be for the persistent connection based on a comparison of the response/delay time relative to the idle time. For example, the outgoing request is detected to be for the persistent connection when the idle time is short compared to the response/delay time. The outgoing request can also be detected to be for the persistent connection if the idle time indicates a immediate or near-immediate issuance of the subsequent request after receipt of the response.
  • a request (e.g., a long-held HTTP request) initiated from the mobile client is detected on the mobile device.
  • a cached response is provided to the application (e.g., a mobile application) from a cache of the mobile device to satisfy the request without sending the request over the wireless network.
  • the cached response can be provided to the application (e.g., a mobile application) after a time interval has elapsed.
  • a source for updates to the cached response for the request is monitored.
  • the cached response can be provided by a local proxy on the mobile device and the source can be monitored by a proxy server wirelessly coupled to the mobile device and able to communicate with the local proxy.
  • an updated response for the request is cached.
  • the updated response for the request can be detected by the proxy server and stored at a remote cache on the proxy server.
  • the updated response can be provided to the application (e.g., a mobile application) by the proxy server.
  • the proxy server can notify local proxy that the cached response is no longer valid when updates to the cached response are detected from the source.
  • the updated response for the request is provided to the application (e.g., a mobile application).
  • FIG. 13 depicts a flow chart illustrating an example process for detecting a long poll request initiated at a mobile device.
  • a first request initiated by a client on a mobile device is detected.
  • a response is received at the mobile device responsive to the first request.
  • a second request initiated by the client on the mobile device is detected. The second request is detected after the response is received, and it typically is the request immediately following the first request (e.g., no intervening requests between the first and second requests).
  • the response/delay interval time is computed as time between the time of the first request and receipt of the response.
  • the idle time interval is computed as time between the time of the response to time of the second request.
  • a response/delay time interval relative to an idle time interval is used to determine whether requests initiated by the client are long poll requests. The process can continue at flow B as illustrated in FIG. 14 to illustrate additional example processes for identifying a long poll and content caching and serving content from the cache.
  • a third request from the application can be detected. Based on the third request, a trend can be determined, identified, or estimated in response/delays based on when responses for the second and third requests are received.
  • the trend may indicate an increase in response/delays, and in one embodiment, the increase indicates cacheability for the long poll requests and a third response received is stored as cache elements in a local cache. Similarly, if the trend indicates that the response delays are constant or substantially constant then the repeatability criteria for caching are met and a third response received can be stored as cache elements in a local cache.
  • substantially constant response/delay includes a tolerance within 0-5%, 5-10%, 10-15%, or 15-20% of one of the response/delays.
  • content received for the application is determined to be cacheable when the received responses indicate repeatability. For example, a third response is received to the third request; and repeatability can be indicated when the first, second, and third responses are the same. Alternatively, repeatability criteria may be met when any two out of the first, second, and third responses are the same. In the case of two responses where the first response is received to the first request, a second response is received to the second request, repeatability can be indicated when the first and second responses are the same.
  • any response received for the requesting application may not be cached yet until a next request (e.g., fourth request or any subsequent requests) is received.
  • the request may be cached upon the next request-response sequence which increases in delay interval compared to the prior decreasing delay interval.
  • a response received for the fourth request or any subsequent request can be cached responsive to detection of an increase in delay interval from the previous delay interval, for the fourth request-response delay.
  • the fourth response can be cached responsive to detecting repeatability in content with prior responses.
  • the fourth response is cached responsive to detecting that it is the same with at least one or two prior responses or cached responsive to detecting that it is the same with at least three prior responses.
  • FIG. 14 depicts a flow chart illustrating an example process for caching content received in long poll requests of an application on a mobile device using timing intervals in a request-response timing sequence.
  • process 1402 it is determined whether the response/delay time interval is greater than the idle time interval. If so, the requests initiated by the client are determined to be long poll requests, as in step 1406 .
  • process 1404 it is determined, for example, if the response/delay interval time is greater than a threshold value. If so, the requests initiated by the client are determined to be long poll requests as in step 1406 . In process 1406 , it is determined that the requests initiated by, the client are long poll requests (e.g., a long-held HTTP request, or any request suitable to emulate content push such as one for a persistent connection enabling COMET style push).
  • long poll requests e.g., a long-held HTTP request, or any request suitable to emulate content push such as one for a persistent connection enabling COMET style push.
  • the threshold value can be determined by the local proxy or another entity. In one embodiment, the threshold value is determined using response/delay interval times for requests generated by other clients. The other clients can be those that reside on the same mobile device and the threshold value can be determined by the local proxy on the mobile device.
  • the threshold can thus be determined by a proxy server which is external to the mobile device, and able to communicate over a wireless network with the different mobile devices. Both clients on the mobile device and clients on other devices can be used to determine the threshold, in combination or in separation.
  • the threshold value can be determined, in part or in whole, based on network delays or other network-related latencies.
  • the network delays can include delays in a cellular network or over the Internet, and can be determined by the local proxy and/or the proxy server. Indications and further information regarding mobile network delays (e.g., cell network) can be provided by cell service providers or carriers, for example.
  • the threshold value is determined in part or in whole, based on delays of servers (e.g., the application server/content host 110 of FIG. 1A-B ) to which the requests are directed, for example, due to internal delays (e.g., server upgrade, server maintenance, server malfunction, etc.) or network-related delays affecting the specific destination server.
  • servers e.g., the application server/content host 110 of FIG. 1A-B
  • internal delays e.g., server upgrade, server maintenance, server malfunction, etc.
  • network-related delays affecting the specific destination server.
  • the relative timings can be determined by a local proxy on the mobile device and used by a proxy server remote from the mobile device to monitor a host to which the requests generated by the application are directed for updated responses different from those stored in the local cache for corresponding requests.
  • the relative timings are detected by a proxy server remote from and coupled to the mobile device.
  • responses received for the requests generated by the application are analyzed.
  • process 1410 it is determined whether content received for the application is cacheable.
  • the content can be determined to be cacheable, for example, when the received responses indicate repeatability.
  • the local proxy and/or the proxy server can detect repeatability in the received response and determine that the content received for the application is cacheable.
  • hash values of the responses are compared to detect repeatability by a local proxy on the mobile device or by a proxy server remote from and coupled to the mobile device.
  • Repeatability can be determined when at least two responses received for the requests from the application are the same. In some instances, more than two same responses may be required to satisfy the requirement for content repeatability.
  • the number of responses that need to be the same before caching begins may be set by default and be the same for all applications, or on a case by case basis with or without conditions and expiry time/dates.
  • the content received for the application is stored as cache elements in a local cache of the mobile device.
  • subsequent requests generated by the application are received.
  • subsequent requests generated by the application are responded to using the cache elements stored on the mobile device.
  • the relative timings between responses and requests can be used when responding to requests using cached content on the mobile device to correspond to a manner in which the content server would respond to the outgoing request.
  • FIG. 15 depicts a flow chart illustrating an example process for detecting requests for a persistent connection (e.g., long poll requests, long-held HTTP requests, HTTP streaming requests) from an application using relative timings in request-response timing sequences.
  • a persistent connection e.g., long poll requests, long-held HTTP requests, HTTP streaming requests
  • the relative timings between a first request initiated by the application, a response received responsive to the first request, and a second request initiated subsequent to the first request also by the application are determined.
  • the relative timings can be used to determine whether requests generated by the application are long poll requests. Note that, in general, the first and second requests for use in computing the relative timings are selected for use after a long poll hunting period has settled or detected in the absence of a long poll hunting period. Alternatively, the first and second requests can be detected during a long poll hunting period and used to perform the analysis.
  • a timing diagram showing example timing characteristics of a long poll hunt is illustrated in the example of FIG. 8 .
  • the relative timings can be determined by for example, determining a first request time when the first request is initiated, determining a response time when the response to the first request is received, and/or determining a second request time when the second request, subsequent to the first request is initiated by the application.
  • process 1504 it is determined if the second request is immediately or near-immediately re-requested after the response to the first request is received. If so, it can be determined that requests of the application are long poll requests or can be treated/processed/cached/managed as a long poll request, as in process 1508 .
  • process 1506 it is determined if the response/delay interval time is greater than request-response timing characteristics for other applications. If so, it can be determined that requests of the application are long poll requests or can be treated/processed/cached/managed as a long poll request, as in process 1508 .
  • FIG. 16 depicts a flow chart illustrating an example process for determining whether to cache content received for an application over long-held connections on a mobile device.
  • a response/delay of a request from the application is determined.
  • the response/delay time is illustrated and labeled as time interval ‘D’ in the example request-response timing sequence shown in FIG. 17 (e.g., the amount of time elapsed between when a request is sent and when a response is detected).
  • the response delay time can in general, be determined by a local proxy (e.g., device-side proxy) and/or the server-side proxy (e.g., proxy server).
  • the response/delay can be used alone or in combination with other timing characteristics to characterize applications or requests for use in setting polling intervals to optimize distributed caching.
  • an expected response/delay is determined for other applications accessing a same wireless network as mobile device.
  • the other applications can reside on the same mobile device and/or include applications which reside on other mobile devices serviced by the same wireless network (e.g., the same network operator, carrier, service provider, and/or the same physical infrastructure, and/or the same logical network).
  • applications which reside on devices serviced by different wireless networks e.g., different carriers or different physical networks
  • process 1606 the expected response/delay and the response/delay of the detected request is compared.
  • process 1608 it is determined that requests generated by the application are requests for long-held connections if the response/delay of the application is greater than the expected response/delay. As such it is determined that requests generated by the application are requests for long-held connections, or it is determined that requests generated by the application are to be processed and treated as requests for long-held connections.
  • process 1610 it is determined that content received for the application is cacheable, when the received responses indicate repeatability. For example, in detecting a second response received for the second request, repeatability in timing of the first request and the first response, and of the second request and the second response can be detected if present.
  • the content received for the application is stored as cache elements in a local cache of the mobile device, for example, if the timing for the request-response pairs is detected to be repeatable.
  • the caching can begin during long poll hunting (e.g., first, second, and/or subsequent requests are part of a long hung sequence and one or more of the responses are cached). Caching while the application is in the hunting period can accelerate or expedite the caching process (e.g., begin caching sooner) to enhance performance since cache elements on the local proxy on the mobile device can be used sooner to serve application requests.
  • the caching may also occur in the absence of long poll hunts (e.g., the first and second requests are regular requests) or after long poll hunting has settled (e.g., the first and second requests described in this flow chart occur after the hunting period).
  • subsequent requests generated by the application are responded to using the cache elements stored on the mobile device, to satisfy the subsequent requests without a need to send the outgoing request over the wireless network.
  • the responses are provided in a manner that is timed to correspond to a manner in which a content server would respond, using the response/delay interval time.
  • FIG. 17A depicts an example of a timing diagram 1700 showing timing characteristics for request and response sequences.
  • the present technology includes a distributed caching model which involves cooperation of the device-side proxy and server-side.
  • the client-side component needs to notify the server-side proxy and also providing a rate that a particular resource (application server/content provider) must be polled at (to verify validity of cached content).
  • the server-side proxy can then monitor the resource for changes (validating resource) and, once a change is detected, the server-side component can notify the device-side component by sending an invalidation request.
  • the client-side component needs to provide a correct and suitable polling interval to the server-side proxy (e.g., the interval at which the server-side proxy is polling the resource to monitor it) for optimal performance, since if the polling interval is too low, the load is unnecessarily increased on the server-side proxy and by increasing the polling interval, the local proxy risks providing the expired/irrelevant information to the user at the user device.
  • a correct and suitable polling interval e.g., the interval at which the server-side proxy is polling the resource to monitor it
  • timing characteristics of request-responses sequences between a requesting client/application and content provider/application server can be used to determine application behavior and/or to categorize request type. Such information can be used to determine, identify, estimate, or predict an application's polling intervals such that an optimal polling interval that the server-side proxy needs to monitor the resource at can be determined and provided to the server-side proxy.
  • the timing characteristics can include, for example, response/delay time to receive a response after a request has been sent; and an idle time to send a subsequent request after the response has been received.
  • the relationships of the various time intervals in a response-request sequence can be seen in the timing diagram 1700 .
  • Each request-response time sequence can be described using all or some of the following events: 1) Start sending request ( 1705 ); 2) Request sent; 3) Response start ( 1710 ); 4) Response end ( 1720 ); 5) Next request send ( 1715 ).
  • the ‘Response Start’ 1710 ) indicates when the first bytes of response (HEADER) arrived and the ‘Response end 1715 ’ indicates when all response content has been received.
  • the device-side can calculate the following intervals shown in 1700 :
  • RI 1708 Request interval—Time between “Request Sent 0 ” and “Request Sent 1 .
  • D 1704 Delay—Time between ‘Request sent’ and “First bytes of response (HEADER) arrived.”
  • IT 1706 Idle time—Time between ‘Whole Response content received 0 ” and ‘Request Sent 1 ”
  • RT 1712 Response time—Time between “First bytes of response (HEADER) arrived.” and ‘Whole Response content received”
  • the device-side component of the distributed proxy can keep track of individual timing intervals in a request-response sequence and compare the values, in a relative (e.g., bigger or smaller than another interval) or absolute manner (specific duration, long, short compared to a dynamic or static threshold value, etc.).
  • the device-side component can track these interval values over time, check for stable components and determine or identify tendencies or patterns.
  • the device-side component can detect increasing or decreasing ‘D’ 1704 in the case of long poll hunting mode for long poll requests.
  • FIG. 17B depicts an example of a timing diagram 1750 showing timing characteristics for request/response sequences characteristic of a long poll. Note that timing diagram 1750 may not be applicable to high latency long polls.
  • a request can be detected, determined, or to be a long poll request based on a comparison of the response/delay time (D 1754 ) relative to the idle time (IT 1756 ) between request 0 1755 and response start time 1760 .
  • the request can be detected to be a long poll request when the idle time is short compared to the response delay time (IT 1756 ⁇ D 1754 ).
  • the request can also be determined to be a long poll when IT 1756 is zero or substantially zero ( ⁇ 0).
  • the request can be determined or categorized as a long poll request if the idle time (IT 1756 ) indicates an immediate or near-immediate issuance of the subsequent request after receipt of the response (e.g., a short IT 1756 ).
  • the response time ‘RT’ 1762 can be used to determine bit rate (e.g., size in byte*8/time).
  • FIG. 18 depicts example timing diagrams 1800 showing timing characteristics for various types of request-response sequences.
  • Sequence 1802 is characterized by a short ‘D’, short ‘RT’, and long ‘IT’. Thus sequence 1802 may be a typical poll. Sequence 1804 is characterized by a short ‘D’, a short ‘RT’, a short ‘IT’ and is indicative of a high polling rate. Sequence 1804 may also indicate that a user is actively interacting with the application and/or actively refreshing the application.
  • Sequence 1806 is characterized by a short ‘D’, a long ‘RT’ and short ‘IT,’ which can indicate possible streaming.
  • Sequence 1808 is characterized by a short ‘D’, a long ‘RT, and a long ‘IT’ which can indicate polling of large content.
  • Sequence 1810 is characterized by a long ‘D,’ a short ‘RT,’ and a long ‘IT, which may indicate a long poll with high latency allowed on the application level.
  • Sequence 1812 which has a long ‘D’, a short ‘RT’, and a short ‘IT’ may indicate a long poll.
  • Sequence 1814 having a long ‘D’, long ‘RT’ and short ‘IT’ can indicate streaming or long poll of large content.
  • Sequence 1816 has a long ‘D’ a ‘long ‘RT’, and long ‘IT’ can be a combination of 1814 and 1810 .
  • FIG. 19 shows a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.
  • the machine operates as a standalone device or may be connected (e.g., networked) to other machines.
  • the machine may operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.
  • the machine may be a server computer, a client computer, a personal computer (PC), a user device, a tablet PC, a laptop computer, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, an iPhone, an iPad, a Blackberry, a processor, a telephone, a web appliance, a network router, switch or bridge, a console, a hand-held console, a (hand-held) gaming device, a music player, any portable, mobile, hand-held device, tablet, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.
  • PC personal computer
  • PDA personal digital assistant
  • machine-readable medium or machine-readable storage medium is shown in an exemplary embodiment to be a single medium, the term “machine-readable medium” and “machine-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions.
  • the term “machine-readable medium” and “machine-readable storage medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the presently disclosed technique and innovation.
  • routines executed to implement the embodiments of the disclosure may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.”
  • the computer programs typically comprise one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processing units or processors in a computer, cause the computer to perform operations to execute elements involving the various aspects of the disclosure.
  • machine-readable storage media machine-readable media, or computer-readable (storage) media
  • recordable type media such as volatile and non-volatile memory devices, floppy and other removable disks, hard disk drives, optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), among others, and transmission type media such as digital and analog communication links.
  • CD ROMS Compact Disk Read-Only Memory
  • DVDs Digital Versatile Disks
  • transmission type media such as digital and analog communication links.
  • the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.”
  • the terms “connected,” “coupled,” or any variant thereof means any connection or coupling, either direct or indirect, between two or more elements; the coupling of connection between the elements can be physical, logical, or a combination thereof.
  • the words “herein,” “above,” “below,” and words of similar import when used in this application, shall refer to this application as a whole and not to any particular portions of this application.
  • words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively.
  • the word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.

Abstract

Systems and methods for application and network-based long poll request detection and cacheability assessment therefore are disclosed. In one aspect, embodiments of the present disclosure include a method, which may be implemented on a distributed proxy and cache system, including, determining relative timings between a first request initiated by the application, a response received responsive to the first request, and a second request initiated subsequent to the first request also by the application, and/or using the relative timings to determine whether requests generated by the application are long poll requests. The relative timings can be used to determine whether the second request is immediately or near-immediately re-requested after the response to the first request is received. The relative timings can also be compared to request-response timing characteristics for other applications to determine whether the requests of the application are long poll requests.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • This application claims the benefit of U.S. Provisional Patent Application No. 61/408,858 entitled “CROSS APPLICATION TRAFFIC COORDINATION”, which was filed on Nov. 1, 2010, U.S. Provisional Patent Application No. 61/408,839 entitled “ACTIVITY SESSION AS METHOD OF OPTIMIZING NETWORK RESOURCE USE”, which was filed on Nov. 1, 2010, U.S. Provisional Patent Application No. 61/408,829 entitled “DISTRIBUTED POLICY MANAGEMENT”, which was filed on Nov. 1, 2010, U.S. Provisional Patent Application No. 61/408,846 entitled “INTELLIGENT CACHE MANAGEMENT IN CONGESTED WIRELESS NETWORKS”, which was filed on Nov. 1, 2010, U.S. Provisional Patent Application No. 61/408,854 entitled “INTELLIGENT MANAGEMENT OF NON-CACHEABLE CONTENT IN WIRELESS NETWORKS”, which was filed on Nov. 1, 2010, U.S. Provisional Patent Application No. 61/408,826 entitled “ONE WAY INTELLIGENT HEARTBEAT”, which was filed on Nov. 1, 2010, U.S. Provisional Patent Application No. 61/408,820 entitled “TRAFFIC CATEGORIZATION AND POLICY DRIVING RADIO STATE”, which was filed on Nov. 1, 2010, U.S. Provisional Patent Application No. 61/416,020 entitled “ALIGNING BURSTS FROM SERVER TO CLIENT”, which was filed on Nov. 22, 2010, U.S. Provisional Patent Application No. 61/416,033 entitled “POLLING INTERVAL FUNCTIONS”, which was filed on Nov. 22, 2010, U.S. Provisional Patent Application No. 61/430,828 entitled “DOMAIN NAME SYSTEM WITH NETWORK TRAFFIC HARMONIZATION”, which was filed on Jan. 7, 2011, U.S. Provisional Patent Application No. 61/532,857 entitled “CACHE DEFEAT DETECTION AND CACHING OF CONTENT ADDRESSED BY IDENTIFIERS INTENDED TO DEFEAT CACHE”, which was filed on Sep. 9, 2011, U.S. Provisional Patent Application No. 61/533,007 entitled “DISTRIBUTED CACHING IN A WIRELESS NETWORK OF CONTENT DELIVERED FOR A MOBILE APPLICATION OVER A LONG-HELD REQUEST”, which was filed on Sep. 9, 2011, and U.S. Provisional Patent Application No. 61/533,021 entitled “APPLICATION AND NETWORK-BASED LONG POLL REQUEST DETECTION AND CACHEABILITY ASSESSMENT THEREFOR”, which was filed on Sep. 9, 2011, the contents of which are all incorporated by reference herein.
  • This application is related to U.S. patent application Ser. No. 13/176,537 [Attorney Docket No. 76443-8107.US01] entitled “DISTRIBUTED CACHING AND RESOURCE AND MOBILE NETWORK TRAFFIC MANAGEMENT,” which was filed on Jul. 5, 2011, the contents of which are herein incorporated by reference.
  • This application is related to U.S. patent application Ser. No. ______ [Attorney Docket No. 76443-8138.US01] entitled “Distributed Caching In A Wireless Network Of Content Delivered For A Mobile Application Over A Long-Held Request”, which is concurrently filed herewith, and the contents of which are herein incorporated by reference.
  • This application is related to U.S. patent application Ser. No. ______ [Attorney Docket No. 76443-8134.US01] entitled “Caching Adapted for Mobile Application Behavior and Network Conditions,” which is concurrently filed herewith, and the contents of which are herein incorporated by reference.
  • This application is related to U.S. patent application Ser. No. ______ [Attorney Docket No. 76443-8134.US02] entitled “Request and Response Characteristics based Adaptation of Distributed Caching In A Mobile Network”, which is concurrently filed herewith, and the contents of which are herein incorporated by reference.
  • BACKGROUND
  • The mobile application model has significantly changed consumption of content managed on the Internet. For example, joining social media and instant messaging applications, increasingly popular mobile gaming applications such as Angry Birds, are some of the latest types of applications to send mobile signaling and data consumption skyrocketing. Angry Birds is just one example of the many available applications that constantly signal the mobile network for updates at hundreds and even thousands of times per hour. As such, traditional practices of providing all-you-can-eat data plans have become a thing of the past. The data tsunami is affecting the mobile ecosystem as a whole, and end-users are feeling the brunt of the wrath as operators scramble to find the best solution.
  • The applications that contribute to mobile data consumption can further include, for example, push email, instant messaging, visual voicemail, voice and video telephony, and others which may require an always-on of frequent IP connections and frequent transmit of small bits of data. Further, these applications poll their host servers with varying polling characteristics, due to the nature of the application, user activity, and/or nature of data being exchanged. For example, one category of polling can be represented by a persistent IP connection, such as one established by long polling or COMET style push, which is a web application model where long-held request (e.g., long-held HTTP requests) allows server to push data to the client when this data becomes available.
  • The persistent connection allows emulation of content push from server to client (e.g., mobile client). Specifically, when a response is not available when the request is sent, the server holds the request until information becomes available to be sent to the client. In general, the client immediately re-issues a request to the server, which the server then responds to or holds until a response is available. This behavior of long polls or other types of persistent connections is different from other types of polling. Due to the different caching requirements of different types of polling, different classes of polling patterns, such as long poll patterns and characteristics need to be detected for effective caching and assessment of cacheability.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1A illustrates an example diagram of a system where a host server facilitates management of traffic, content caching, and/or resource conservation between mobile devices (e.g., wireless devices) and an application server or content provider in a wireless network (or broadband network) for resource conservation.
  • FIG. 1B illustrates an example diagram of a proxy and cache system distributed between the host server and device which facilitates network traffic management between a device and an application server/content provider for resource conservation and content caching.
  • FIG. 2A depicts a block diagram illustrating an example of client-side components in a distributed proxy and cache system residing on a mobile device (e.g., wireless device) that manages traffic in a wireless network (or broadband network) for resource conservation, content caching, and/or traffic management.
  • FIG. 2B depicts a block diagram illustrating another example of components in the application behavior detector and the caching policy manager in the local proxy on the client-side of the distributed proxy system shown in the example of FIG. 2A.
  • FIG. 3A depicts a block diagram illustrating an example of server-side components in a distributed proxy and cache system that manages traffic in a wireless network (or broadband network) for resource conservation, content caching, and/or traffic management.
  • FIG. 3B depicts a block diagram illustrating another example of components in the caching policy manager in the proxy server on the server-side of the distributed proxy system shown in the example of FIG. 3A.
  • FIG. 4A depicts a timing diagram showing how data requests from a mobile device (e.g., any wireless device) to an application server/content provider in a wireless network (or broadband network) can be coordinated by a distributed proxy system in a manner such that network and battery resources are conserved through using content caching and monitoring performed by the distributed proxy system.
  • FIG. 4B depicts an interaction diagram showing how application polls having data requests from a mobile device (e.g., any wireless device) to an application server/content provider in a wireless network (or broadband network) can be can be cached on the local proxy and managed by the distributed caching system.
  • FIG. 5 depicts a diagram showing one example process for implementing a hybrid IP and SMS power saving mode on a mobile device (e.g., any wireless device) using a distributed proxy and cache system (e.g., such as the distributed system shown in the example of FIG. 1B).
  • FIG. 6 depicts a flow diagram illustrating an example process for distributed content caching between a mobile device (e.g., any wireless device) and remote proxy and the distributed management of content caching.
  • FIG. 7 depicts an interaction diagram showing cache management by a distributed proxy system of content delivered to a mobile application over a long-held request while ensuring freshness of content delivered.
  • FIG. 8 depicts a timing diagram showing hunting mode behavior in a long poll request and a timing diagram showing timing characteristics when the long poll has settled.
  • FIG. 9 depicts a flow chart illustrating an example process for caching content pushed to a mobile device (e.g., any wireless device) in a persistent connection from a content server over a wireless network (or broadband network).
  • FIG. 10 depicts a diagram showing example processes that occur when removing a stored response from the local cache on a mobile device (e.g., any wireless device) for a long poll request.
  • FIG. 11 depicts a flow chart illustrating an example process for using cached content provided over a long-held connection via a wireless network (or broadband network) to satisfy mobile client requests on a mobile device (e.g., any wireless device).
  • FIG. 12 depicts a flow chart illustrating an example process for caching content received at a mobile device (e.g., any wireless device) over a persistent connection over a wireless network (or broadband network).
  • FIG. 13 depicts a flow chart illustrating an example process for detecting a long poll request initiated at a mobile device (e.g., any wireless device).
  • FIG. 14 depicts a flow chart illustrating an example process for determining whether to cache content received in long poll requests of an application on a mobile device using timing intervals in a request-response timing sequence.
  • FIG. 15 depicts a flow chart illustrating an example process for detecting requests for a persistent connection (e.g., long poll requests, long-held HTTP requests, or HTTP streaming requests) from an application using relative timings in request-response timing sequences.
  • FIG. 16 depicts a flow chart illustrating an example process for determining whether to cache content received for an application over long-held connections on a mobile device.
  • FIG. 17A depicts an example of a timing diagram showing timing characteristics for request-response sequences.
  • FIG. 17B depicts an example of a timing diagram showing timing characteristics for request-response sequences characteristic of a long poll.
  • FIG. 18 depicts example timing diagrams showing timing characteristics for various types of request-response sequences.
  • FIG. 19 shows a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.
  • DETAILED DESCRIPTION
  • The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding of the disclosure. However, in certain instances, well-known or conventional details are not described in order to avoid obscuring the description. References to one or an embodiment in the present disclosure can be, but not necessarily are, references to the same embodiment; and, such references mean at least one of the embodiments.
  • Reference in this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not other embodiments.
  • The terms used in this specification generally have their ordinary meanings in the art, within the context of the disclosure, and in the specific context where each term is used. Certain terms that are used to describe the disclosure are discussed below, or elsewhere in the specification, to provide additional guidance to the practitioner regarding the description of the disclosure. For convenience, certain terms may be highlighted, for example using italics and/or quotation marks. The use of highlighting has no influence on the scope and meaning of a term; the scope and meaning of a term is the same, in the same context, whether or not it is highlighted. It will be appreciated that same thing can be said in more than one way.
  • Consequently, alternative language and synonyms may be used for any one or more of the terms discussed herein, nor is any special significance to be placed upon whether or not a term is elaborated or discussed herein. Synonyms for certain terms are provided. A recital of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification including examples of any terms discussed herein is illustrative only, and is not intended to further limit the scope and meaning of the disclosure or of any exemplified term. Likewise, the disclosure is not limited to various embodiments given in this specification.
  • Without intent to limit the scope of the disclosure, examples of instruments, apparatus, methods and their related results according to the embodiments of the present disclosure are given below. Note that titles or subtitles may be used in the examples for convenience of a reader, which in no way should limit the scope of the disclosure. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. In the case of conflict, the present document, including definitions will control.
  • Embodiments of the present disclosure include systems and methods for application and network-based long poll request detection and cacheability assessment therefor.
  • For example, a long poll request initiated at a mobile device can be detected by determining relative timings between a first request initiated by the application, a response received responsive to the first request, and a second request initiated subsequent to the first request also by the application. The relative timings can be used to determine whether requests generated by the application are long poll requests. Furthermore, using the relative timings and received responsive to the requests generated by the application, it can be determined that content received for the application is cacheable, when the received responses indicate repeatability, and/or when the relative timings depict some pattern that may be reproducible.
  • A long-held request generally includes and can refer to, connections between a client (e.g., an application, a mobile application on a device, or a device such as a mobile device or wireless device) and a server that is held open even if content is not available to be sent back to the client. The connection can be maintained between the client and server, until content becomes available at the server to be sent to the client. In general, once a response with content is sent back to the client (e.g., end user computer or mobile device such as a mobile phone, or a Machine to Machine (M2M) device)) the connection terminates (e.g., terminated by the server). The client typically will immediately re-issue a request to connect again to the server which holds the connection open until requested content becomes available for the client device.
  • A long-held requested connection can include, for example, a persistent connection, a persistent HTTP connection, long poll-type request, HTTP streaming, or any other types of connections suited for push or emulated content push.
  • One embodiment of the disclosed technology includes, a system that optimizes multiple aspects of the connection with wired and wireless networks, broadband networks, and devices through a comprehensive view of device and application activity including: loading, current application needs on a device, controlling the type of access (push vs. pull or hybrid), location, concentration of users in a single area, time of day, how often the user interacts with the application, content or device, and using this information to shape traffic to a cooperative client/server or simultaneously mobile devices without a cooperative client. Because the disclosed server is not tied to any specific network provider it has visibility into the network performance across all service providers. This enables optimizations to be applied to devices regardless of the operator or service provider, thereby enhancing the user experience and managing network utilization while roaming. Bandwidth has been considered a major issue in wireless networks today. More and more research has been done related to the need for additional bandwidth to solve access problems—many of the performance enhancing solutions and next generation standards, such as those commonly referred to as 4G, namely LTE, 4G, and WiMAX are focused on providing increased bandwidth. Although partially addressed by the standards a key problem that remains is lack of bandwidth on the signaling channel more so than the data channel and the standard does not address battery life very well.
  • Embodiments of the disclosed technology includes, for example, alignment of requests from multiple applications to minimize the need for several polling requests; leverage specific content types to determine how to proxy/manage a connection/content; and apply specific heuristics associated with device, user behavioral patterns (how often they interact with the device/application) and/or network parameters.
  • Embodiments of the present technology can further include, moving recurring HTTP polls performed by various widgets, RSS readers, etc., to remote network node (e.g., Network Operation Center (NOC)), thus considerably lowering device battery/power consumption, radio channel signaling and bandwidth usage. Additionally, the offloading can be performed transparently so that existing applications do not need to be changed.
  • In some embodiments, this can be implemented using a local proxy on the mobile device (e.g., any wireless device) which automatically detects recurring requests for the same content (RSS feed, Widget data set) that matches a specific rule (e.g., happens every 15 minutes). The local proxy can automatically cache the content on the mobile device while delegating the polling to the server (e.g., a proxy server operated as an element of a communications network). The server can then notify the mobile/client proxy if the content changes, and if content has not changed (or not changed sufficiently, or in an identified manner or amount) the mobile proxy provides the latest version in its cache to the user (without need to utilize the radio at all). This way the mobile or wireless device (e.g., a mobile phone, smart phone, M2M module/MODEM, or any other wireless devices, etc.) does not need to open (e.g., thus powering on the radio) or use a data connection if the request is for content that is monitored and that has been not flagged as new/changed.
  • The logic for automatically adding content sources/application servers (e.g., including URLs/content) to be monitored can also check for various factors like how often the content is the same, how often the same request is made (is there a fixed interval/pattern?), which application is requesting the data, etc. Similar rules to decide between using the cache and request the data from the original source may also be implemented and executed by the local proxy and/or server.
  • For example, when the request comes at an unscheduled/unexpected time (user initiated check), or after every (n) consecutive times the response has been provided from the cache, etc., or if the application is running in the background vs. in a more interactive mode of the foreground. As more and more mobile applications or wireless enabled applications base their features on resources available in the network, this becomes increasingly important. In addition, the disclosed technology allows elimination of unnecessary chatter from the network, benefiting the operators trying to optimize the wireless spectrum usage.
  • Intelligent Cache Management
  • By detecting the rate and type of requests to a content source or application server (which may be identified by a URI or URL), combined with determining the state information of the mobile device (e.g., whether the backlight is on or off) or the user, the distributed proxy system (e.g., the local proxy and/or the proxy server) can, for example, determine the difference between content that is programmatically refreshed and content that is requested by the user in the foreground. Using this information, along with the network conditions such as the TCP connection delay and/or Round Trip Time (RTT), current radio coverage statistics, the disclosed proxy system can determine whether to and when to cache content locally on the mobile device (e.g., any wireless device), to satisfy future content requests. If content is already cached, then the cached version can be presented to the user. If not, the request is passed through over the mobile network to the content server and the retrieved content can be presented.
  • To preserve user experience, the disclosed distributed proxy system can determine and utilize the “criticality of an application” as a factor. For example, financial applications may be considered time critical so that these application requests are not cached but instead allowed to go over the wireless broadband or mobile network to retrieve current data. An application, by name or type, can be considered critical at the time of provisioning or determined by programmatic observation of user interaction over time. That is, the sever-side component of the distributed proxy system can be provisioned with “profiles” which indicate the criticality of the application. This profile can be communicated to the device-side component of the proxy system during initialization or subsequent establishment of polling requests.
  • A set of criteria (e.g., including application profile information) can be applied to content sources/application servers (e.g., each associated resource or resource identifier) to determine the suitability of related content for caching (size, etc.). The profile can further be used to identify applications for which caching will typically not be appropriate, such as the Google Market. Additionally, the pattern (e.g., periodicity or time interval) of each request as identified by a specific identifier (e.g., a resource of resource identifier) associated with a content source/application server can be monitored by the distributed system such that polling behavior can be determined, and the content cached accordingly.
  • When content from a content source/application server has been identified as suitable for caching, a message can be transmitted to the server-side component of the disclosed proxy system requesting that that the content associated with the content source/application server be monitored for changes. When the server detects that the content has been altered, the server transmits a message to the device-side component instructing it to invalidate whatever cache elements are associated with that URI.
  • In some instances, memory usage parameters of a mobile device (e.g., as described by the carrier configuration) are factored in when caching. As such, the client-side component of the disclosed distributed proxy will usually not use more than the specified percentage of available memory space for cache entries (e.g., as specified by the device manufacturer, operating system, applications, etc.). In addition to total memory usage, the client-side component of the distributed proxy can implement a configurable limit on the total number of cache entries stored across multiple applications or on a per-application basis.
  • Cache entries stored on the mobile device (e.g., any wireless device) can be aged out automatically by the client-side component of the distributed proxy as determined, for example, by configurable parameters (e.g., by the user, based on application-need, network service provider requirements, OS requirements, etc.). Additionally, cache elements may be removed to remain in compliance with disk usage or entry count restrictions. In some instances, the client-side component can invalidate the entire cache storage should the server-side proxy become unavailable. In one embodiment, the client-side component of the distributed proxy system can encrypt cached content.
  • FIG. 1A illustrates an example diagram of a system where a host server 100 facilitates management of traffic, content caching, and/or resource conservation between clients (e.g., mobile devices, any wireless device or clients/applications on client devices 150) and an application server or content provider 110 in a wireless network (or broad band network) 106 or 108 for resource conservation.
  • The client devices 150 can be any system and/or device, and/or any combination of devices/systems that is able to establish a connection, including wired, wireless, cellular connections with another device, a server and/or other systems such as host server 100 and/or application server/content provider 110. Client devices 150 will typically include a display and/or other output functionalities to present information and data exchanged between among the devices 150 and/or the host server 100 and/or application server/content provider 110.
  • For example, the client devices 150 can include mobile, hand held or portable devices, wireless devices, or non-portable devices and can be any of, but not limited to, a server desktop, a desktop computer, a computer cluster, or portable devices, including a notebook, a laptop computer, a handheld computer, a palmtop computer, a mobile phone, a cell phone, a smart phone, a PDA, a Blackberry device, a Palm device, a handheld tablet (e.g., an iPad or any other tablet), a hand held console, a hand held gaming device or console, any SuperPhone such as the iPhone, and/or any other portable, mobile, hand held devices, or fixed wireless interface such as a M2M device, etc. In one embodiment, the client devices 150, host server 100, and application server 110 are coupled via a network 106 and/or a network 108. In some embodiments, the devices 150 and host server 100 may be directly connected to one another.
  • The input mechanism on client devices 150 can include touch screen keypad (including single touch, multi-touch, gesture sensing in 2D or 3D, etc.), a physical keypad, a mouse, a pointer, a track pad, motion detector (e.g., including 1-axis, 2-axis, 3-axis accelerometer, etc.), a light sensor, capacitance sensor, resistance sensor, temperature sensor, proximity sensor, a piezoelectric device, device orientation detector (e.g., electronic compass, tilt sensor, rotation sensor, gyroscope, accelerometer), or a combination of the above.
  • Signals received or detected indicating user activity at client devices 150 through one or more of the above input mechanism, or others, can be used in the disclosed technology in acquiring context awareness at the client device 150. Context awareness at client devices 150 generally includes, by way of example but not limitation, client device 150 operation or state acknowledgement, management, user activity/behavior/interaction awareness, detection, sensing, tracking, trending, and/or application (e.g., mobile applications) type, behavior, activity, operating state, etc.
  • Context awareness in the present disclosure also includes knowledge and detection of network side contextual data and can include network information such as network capacity, bandwidth, traffic, type of network/connectivity, and/or any other operational state data. Network side contextual data can be received from and/or queried from network service providers (e.g., cell provider 112 and/or Internet service providers) of the network 106 and/or network 108 (e.g., by the host server and/or devices 150). In addition to application context awareness as determined from the client 150 side, the application context awareness may also be received from or obtained/queried from the respective application/service providers 110 (by the host 100 and/or client devices 150).
  • The host server 100 can use, for example, contextual information obtained for client devices 150, networks 106/108, applications (e.g., mobile applications), application server/provider 110, or any combination of the above, to manage the traffic in the system to satisfy data needs of the client devices 150 (e.g., to satisfy application or any other request including HTTP request). In one embodiment, the traffic is managed by the host server 100 to satisfy data requests made in response to explicit or non-explicit user 103 requests and/or device/application maintenance tasks. The traffic can be managed such that network consumption, for example, use of the cellular network is conserved for effective and efficient bandwidth utilization. In addition, the host server 100 can manage and coordinate such traffic in the system such that use of device 150 side resources (e.g., including but not limited to battery power consumption, radio use, processor/memory use) are optimized with a general philosophy for resource conservation while still optimizing performance and user experience.
  • For example, in context of battery conservation, the device 150 can observe user activity (for example, by observing user keystrokes, backlight status, or other signals via one or more input mechanisms, etc.) and alters device 150 behaviors. The device 150 can also request the host server 100 to alter the behavior for network resource consumption based on user activity or behavior.
  • In one embodiment, the traffic management for resource conservation is performed using a distributed system between the host server 100 and client device 150. The distributed system can include proxy server and cache components on the server side 100 and on the device/client side, for example, as shown by the server cache 135 on the server 100 side and the local cache 185 on the client 150 side.
  • Functions and techniques disclosed for context aware traffic management for resource conservation in networks (e.g., network 106 and/or 108) and devices 150, reside in a distributed proxy and cache system. The proxy and cache system can be distributed between, and reside on, a given client device 150 in part or in whole and/or host server 100 in part or in whole. The distributed proxy and cache system are illustrated with further reference to the example diagram shown in FIG. 1B. Functions and techniques performed by the proxy and cache components in the client device 150, the host server 100, and the related components therein are described, respectively, in detail with further reference to the examples of FIG. 2-3.
  • In one embodiment, client devices 150 communicate with the host server 100 and/or the application server 110 over network 106, which can be a cellular network and/or a broadband network. To facilitate overall traffic management between devices 150 and various application servers/content providers 110 to implement network (bandwidth utilization) and device resource (e.g., battery consumption), the host server 100 can communicate with the application server/providers 110 over the network 108, which can include the Internet (e.g., a broadband network).
  • In general, the networks 106 and/or 108, over which the client devices 150, the host server 100, and/or application server 110 communicate, may be a cellular network, a broadband network, a telephonic network, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet, or any combination thereof. For example, the Internet can provide file transfer, remote log in, email, news, RSS, cloud-based services, instant messaging, visual voicemail, push mail, VoIP, and other services through any known or convenient protocol, such as, but is not limited to the TCP/IP protocol, UDP, HTTP, DNS, FTP, UPnP, NSF, ISDN, PDH, RS-232, SDH, SONET, etc.
  • The networks 106 and/or 108 can be any collection of distinct networks operating wholly or partially in conjunction to provide connectivity to the client devices 150 and the host server 100 and may appear as one or more networks to the serviced systems and devices. In one embodiment, communications to and from the client devices 150 can be achieved by, an open network, such as the Internet, or a private network, broadband network, such as an intranet and/or the extranet. In one embodiment, communications can be achieved by a secure communications protocol, such as secure sockets layer (SSL), or transport layer security (TLS).
  • In addition, communications can be achieved via one or more networks, such as, but are not limited to, one or more of WiMax, a Local Area Network (LAN), Wireless Local Area Network (WLAN), a Personal area network (PAN), a Campus area network (CAN), a Metropolitan area network (MAN), a Wide area network (WAN), a Wireless wide area network (WWAN), or any broadband network, and further enabled with technologies such as, by way of example, Global System for Mobile Communications (GSM), Personal Communications Service (PCS), Bluetooth, WiFi, Fixed Wireless Data, 2G, 2.5G, 3G, 4G, IMT-Advanced, pre-4G, LTE Advanced, mobile WiMax, WiMax 2, WirelessMAN-Advanced networks, enhanced data rates for GSM evolution (EDGE), General packet radio service (GPRS), enhanced GPRS, iBurst, UMTS, HSPDA, HSUPA, HSPA, UMTS-TDD, 1xRTT, EV-DO, messaging protocols such as, TCP/IP, SMS, MMS, extensible messaging and presence protocol (XMPP), real time messaging protocol (RTMP), instant messaging and presence protocol (IMPP), instant messaging, US SD, IRC, or any other wireless data networks, broadband networks, or messaging protocols.
  • FIG. 1B illustrates an example diagram of a proxy and cache system distributed between the host server 100 and device 150 which facilitates network traffic management between the device 150 and an application server/content provider 100 (e.g., a source server) for resource conservation and content caching.
  • The distributed proxy and cache system can include, for example, the proxy server 125 (e.g., remote proxy) and the server cache, 135 components on the server side. The server-side proxy 125 and cache 135 can, as illustrated, reside internal to the host server 100. In addition, the proxy server 125 and cache 135 on the server-side can be partially or wholly external to the host server 100 and in communication via one or more of the networks 106 and 108. For example, the proxy server 125 may be external to the host server and the server cache 135 may be maintained at the host server 100. Alternatively, the proxy server 125 may be within the host server 100 while the server cache is external to the host server 100. In addition, each of the proxy server 125 and the cache 135 may be partially internal to the host server 100 and partially external to the host server 100.
  • The distributed system can also, include, in one embodiment, client-side components, including by way of example but not limitation, a local proxy 175 (e.g., a mobile client on a mobile device) and/or a local cache 185, which can, as illustrated, reside internal to the device 150 (e.g., a mobile device).
  • In addition, the client-side proxy 175 and local cache 185 can be partially or wholly external to the device 150 and in communication via one or more of the networks 106 and 108. For example, the local proxy 175 may be external to the device 150 and the local cache 185 may be maintained at the device 150. Alternatively, the local proxy 175 may be within the device 150 while the local cache 185 is external to the device 150. In addition, each of the proxy 175 and the cache 185 may be partially internal to the host server 100 and partially external to the host server 100.
  • In one embodiment, the distributed system can include an optional caching proxy server 199. The caching proxy server 199 can be a component which is operated by the application server/content provider 110, the host server 100, or a network service provider 112, and or any combination of the above to facilitate network traffic management for network and device resource conservation. Proxy server 199 can be used, for example, for caching content to be provided to the device 150, for example, from one or more of, the application server/provider 110, host server 100, and/or a network service provider 112. Content caching can also be entirely or partially performed by the remote proxy 125 to satisfy application requests or other data requests at the device 150.
  • In context aware traffic management and optimization for resource conservation in a network (e.g., cellular or other wireless networks), characteristics of user activity/behavior and/or application behavior at a mobile device (e.g., any wireless device) 150 can be tracked by the local proxy 175 and communicated, over the network 106 to the proxy server 125 component in the host server 100, for example, as connection metadata. The proxy server 125 which in turn is coupled to the application server/provider 110 provides content and data to satisfy requests made at the device 150.
  • In addition, the local proxy 175 can identify and retrieve mobile device properties, including one or more of, battery level, network that the device is registered on, radio state, or whether the mobile device is being used (e.g., interacted with by a user). In some instances, the local proxy 175 can delay, expedite (prefetch), and/or modify data prior to transmission to the proxy server 125, when appropriate, as will be further detailed with references to the description associated with the examples of FIG. 2-3.
  • The local database 185 can be included in the local proxy 175 or coupled to the local proxy 175 and can be queried for a locally stored response to the data request prior to the data request being forwarded on to the proxy server 125. Locally cached responses can be used by the local proxy 175 to satisfy certain application requests of the mobile device 150, by retrieving cached content stored in the cache storage 185, when the cached content is still valid.
  • Similarly, the proxy server 125 of the host server 100 can also delay, expedite, or modify data from the local proxy prior to transmission to the content sources (e.g., the application server/content provider 110). In addition, the proxy server 125 uses device properties and connection metadata to generate rules for satisfying request of applications on the mobile device 150. The proxy server 125 can gather real time traffic information about requests of applications for later use in optimizing similar connections with the mobile device 150 or other mobile devices.
  • In general, the local proxy 175 and the proxy server 125 are transparent to the multiple applications executing on the mobile device. The local proxy 175 is generally transparent to the operating system or platform of the mobile device and may or may not be specific to device manufacturers. In some instances, the local proxy 175 is optionally customizable in part or in whole to be device specific. In some embodiments, the local proxy 175 may be bundled into a wireless model, a firewall, and/or a router.
  • In one embodiment, the host server 100 can in some instances, utilize the store and forward functions of a short message service center (SMSC) 112, such as that provided by the network service provider, in communicating with the device 150 in achieving network traffic management. Note that 112 can also utilize any other type of alternative channel including USSD or other network control mechanisms. As will be further described with reference to the example of FIG. 3, the host server 100 can forward content or HTTP responses to the SMSC 112 such that it is automatically forwarded to the device 150 if available, and for subsequent forwarding if the device 150 is not currently available.
  • In general, the disclosed distributed proxy and cache system allows optimization of network usage, for example, by serving requests from the local cache 185, the local proxy 175 reduces the number of requests that need to be satisfied over the network 106. Further, the local proxy 175 and the proxy server 125 may filter irrelevant data from the communicated data. In addition, the local proxy 175 and the proxy server 125 can also accumulate low priority data and send it in batches to avoid the protocol overhead of sending individual data fragments. The local proxy 175 and the proxy server 125 can also compress or transcode the traffic, reducing the amount of data sent over the network 106 and/or 108. The signaling traffic in the network 106 and/or 108 can be reduced, as the networks are now used less often and the network traffic can be synchronized among individual applications.
  • With respect to the battery life of the mobile device 150, by serving application or content requests from the local cache 185, the local proxy 175 can reduce the number of times the radio module is powered up. The local proxy 175 and the proxy server 125 can work in conjunction to accumulate low priority data and send it in batches to reduce the number of times and/or amount of time when the radio is powered up. The local proxy 175 can synchronize the network use by performing the batched data transfer for all connections simultaneously.
  • FIG. 2A depicts a block diagram illustrating an example of client-side components in a distributed proxy and cache system residing on a device 250 that manages traffic in a wireless network for resource conservation, content caching, and/or traffic management.
  • The device 250, which can be a portable or mobile device (e.g., any wireless device), such as a portable phone, generally includes, for example, a network interface 208 an operating system 204, a context API 206, and mobile applications which may be proxy-unaware 210 or proxy-aware 220. Note that the device 250 is specifically illustrated in the example of FIG. 2 as a mobile device, such is not a limitation and that device 250 may be any portable/mobile or non-portable device able to receive, transmit signals to satisfy data requests over a network including wired or wireless networks (e.g., WiFi, cellular, Bluetooth, etc.).
  • The network interface 208 can be a networking module that enables the device 250 to mediate data in a network with an entity that is external to the host server 250, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface 208 can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 2G, 3G, 3.5G, 4G, LTE, etc.), Bluetooth, or whether or not the connection is via a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, a bridge router, a hub, a digital media receiver, and/or a repeater.
  • Device 250 can further include, client-side components of the distributed proxy and cache system which can include, a local proxy 275 (e.g., a mobile client of a mobile device) and a cache 285. In one embodiment, the local proxy 275 includes a user activity module 215, a proxy API 225, a request/transaction manager 235, a caching policy manager 245 having an application protocol module 248, a traffic shaping engine 255, and/or a connection manager 265. The traffic shaping engine 255 may further include an alignment module 256 and/or a batching module 257, the connection manager 265 may further include a radio controller 266. The request/transaction manager 235 can further include an application behavior detector 236 and/or a prioritization engine 241, the application behavior detector 236 may further include a pattern detector 237 and/or and application profile generator 239. Additional or less components/modules/engines can be included in the local proxy 275 and each illustrated component.
  • As used herein, a “module,” “a manager,” a “handler,” a “detector,” an “interface,” a “controller,” a “normalizer,” a “generator,” an “invalidator,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module, manager, handler, detector, interface, controller, normalizer, generator, invalidator, or engine can be centralized or its functionality distributed. The module, manager, handler, detector, interface, controller, normalizer, generator, invalidator, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor.
  • As used herein, a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid. Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.
  • In one embodiment, a portion of the distributed proxy and cache system for network traffic management resides in or is in communication with device 250, including local proxy 275 (mobile client) and/or cache 285. The local proxy 275 can provide an interface on the device 250 for users to access device applications and services including email, IM, voice mail, visual voicemail, feeds, Internet, games, productivity tools, or other applications, etc.
  • The proxy 275 is generally application independent and can be used by applications (e.g., both proxy-aware and proxy- unaware applications 210 and 220 or mobile applications) to open TCP connections to a remote server (e.g., the server 100 in the examples of FIG. 1A-1B and/or server proxy 125/325 shown in the examples of FIG. 1B and FIG. 3A). In some instances, the local proxy 275 includes a proxy API 225 which can be optionally used to interface with proxy-aware applications 220 (or applications (e.g., mobile applications) on a mobile device (e.g., any wireless device)).
  • The applications 210 and 220 can generally include any user application, widgets, software, HTTP-based application, web browsers, video or other multimedia streaming or downloading application, video games, social network applications, email clients, RSS management applications, application stores, document management applications, productivity enhancement applications, etc. The applications can be provided with the device OS, by the device manufacturer, by the network service provider, downloaded by the user, or provided by others.
  • One embodiment of the local proxy 275 includes or is coupled to a context API 206, as shown. The context API 206 may be a part of the operating system 204 or device platform or independent of the operating system 204, as illustrated. The operating system 204 can include any operating system including but not limited to, any previous, current, and/or future versions/releases of, Windows Mobile, iOS, Android, Symbian, Palm OS, Brew MP, Java 2 Micro Edition (J2ME), Blackberry, etc.
  • The context API 206 may be a plug-in to the operating system 204 or a particular client/application on the device 250. The context API 206 can detect signals indicative of user or device activity, for example, sensing motion, gesture, device location, changes in device location, device backlight, keystrokes, clicks, activated touch screen, mouse click or detection of other pointer devices. The context API 206 can be coupled to input devices or sensors on the device 250 to identify these signals. Such signals can generally include input received in response to explicit user input at an input device/mechanism at the device 250 and/or collected from ambient signals/contextual cues detected at or in the vicinity of the device 250 (e.g., light, motion, piezoelectric, etc.).
  • In one embodiment, the user activity module 215 interacts with the context API 206 to identify, determine, infer, detect, compute, predict, and/or anticipate, characteristics of user activity on the device 250. Various inputs collected by the context API 206 can be aggregated by the user activity module 215 to generate a profile for characteristics of user activity. Such a profile can be generated by the user activity module 215 with various temporal characteristics. For instance, user activity profile can be generated in real-time for a given instant to provide a view of what the user is doing or not doing at a given time (e.g., defined by a time window, in the last minute, in the last 30 seconds, etc.), a user activity profile can also be generated for a ‘session’ defined by an application or web page that describes the characteristics of user behavior with respect to a specific task they are engaged in on the device 250, or for a specific time period (e.g., for the last 2 hours, for the last 5 hours).
  • Additionally, characteristic profiles can be generated by the user activity module 215 to depict a historical trend for user activity and behavior (e.g., 1 week, 1 mo., 2 mo., etc.). Such historical profiles can also be used to deduce trends of user behavior, for example, access frequency at different times of day, trends for certain days of the week (weekends or week days), user activity trends based on location data (e.g., IP address, GPS, or cell tower coordinate data) or changes in location data (e.g., user activity based on user location, or user activity based on whether the user is on the go, or traveling outside a home region, etc.) to obtain user activity characteristics.
  • In one embodiment, user activity module 215 can detect and track user activity with respect to applications, documents, files, windows, icons, and folders on the device 250. For example, the user activity module 215 can detect when an application or window (e.g., a web browser or any other type of application) has been exited, closed, minimized, maximized, opened, moved into the foreground, or into the background, multimedia content playback, etc.
  • In one embodiment, characteristics of the user activity on the device 250 can be used to locally adjust behavior of the device (e.g., mobile device or any wireless device) to optimize its resource consumption such as battery/power consumption and more generally, consumption of other device resources including memory, storage, and processing power. In one embodiment, the use of a radio on a device can be adjusted based on characteristics of user behavior (e.g., by the radio controller 266 of the connection manager 265) coupled to the user activity module 215. For example, the radio controller 266 can turn the radio on or off, based on characteristics of the user activity on the device 250. In addition, the radio controller 266 can adjust the power mode of the radio (e.g., to be in a higher power mode or lower power mode) depending on characteristics of user activity.
  • In one embodiment, characteristics of the user activity on device 250 can also be used to cause another device (e.g., other computers, a mobile device, a wireless device, or a non-portable device) or server (e.g., host server 100 and 300 in the examples of FIG. 1A-B and FIG. 3A) which can communicate (e.g., via a cellular or other network) with the device 250 to modify its communication frequency with the device 250. The local proxy 275 can use the characteristics information of user behavior determined by the user activity module 215 to instruct the remote device as to how to modulate its communication frequency (e.g., decreasing communication frequency, such as data push frequency if the user is idle, requesting that the remote device notify the device 250 if new data, changed, data, or data of a certain level of importance becomes available, etc.).
  • In one embodiment, the user activity module 215 can, in response to determining that user activity characteristics indicate that a user is active after a period of inactivity, request that a remote device (e.g., server host server 100 and 300 in the examples of FIG. 1A-B and FIG. 3A) send the data that was buffered as a result of the previously decreased communication frequency.
  • In addition, or in alternative, the local proxy 275 can communicate the characteristics of user activity at the device 250 to the remote device (e.g., host server 100 and 300 in the examples of FIG. 1A-B and FIG. 3A) and the remote device determines how to alter its own communication frequency with the device 250 for network resource conservation and conservation of device 250 resources.
  • One embodiment of the local proxy 275 further includes a request/transaction manager 235, which can detect, identify, intercept, process, manage, data requests initiated on the device 250, for example, by applications 210 and/or 220, and/or directly/indirectly by a user request. The request/transaction manager 235 can determine how and when to process a given request or transaction, or a set of requests/transactions, based on transaction characteristics.
  • The request/transaction manager 235 can prioritize requests or transactions made by applications and/or users at the device 250, for example by the prioritization engine 241. Importance or priority of requests/transactions can be determined by the request/transaction manager 235 by applying a rule set, for example, according to time sensitivity of the transaction, time sensitivity of the content in the transaction, time criticality of the transaction, time criticality of the data transmitted in the transaction, and/or time criticality or importance of an application making the request.
  • In addition, transaction characteristics can also depend on whether the transaction was a result of user-interaction or other user-initiated action on the device (e.g., user interaction with a application (e.g., a mobile application)). In general, a time critical transaction can include a transaction resulting from a user-initiated data transfer, and can be prioritized as such. Transaction characteristics can also depend on the amount of data that will be transferred or is anticipated to be transferred as a result of the requested transaction. For example, the connection manager 265, can adjust the radio mode (e.g., high power or low power mode via the radio controller 266) based on the amount of data that will need to be transferred.
  • In addition, the radio controller 266/connection manager 265 can adjust the radio power mode (high or low) based on time criticality/sensitivity of the transaction. The radio controller 266 can trigger the use of high power radio mode when a time-critical transaction (e.g., a transaction resulting from a user-initiated data transfer, an application running in the foreground, any other event meeting a certain criteria) is initiated or detected.
  • In general, the priorities can be set by default, for example, based on device platform, device manufacturer, operating system, etc. Priorities can alternatively or in additionally be set by the particular application; for example, the Facebook application (e.g., a mobile application) can set its own priorities for various transactions (e.g., a status update can be of higher priority than an add friend request or a poke request, a message send request can be of higher priority than a message delete request, for example), an email client or IM chat client may have its own configurations for priority. The prioritization engine 241 may include set of rules for assigning priority.
  • The prioritization engine 241 can also track network provider limitations or specifications on application or transaction priority in determining an overall priority status for a request/transaction. Furthermore, priority can in part or in whole be determined by user preferences, either explicit or implicit. A user, can in general, set priorities at different tiers, such as, specific priorities for sessions, or types, or applications (e.g., a browsing session, a gaming session, versus an IM chat session, the user may set a gaming session to always have higher priority than an IM chat session, which may have higher priority than web-browsing session). A user can set application-specific priorities, (e.g., a user may set Facebook-related transactions to have a higher priority than Linkedln-related transactions), for specific transaction types (e.g., for all send message requests across all applications to have higher priority than message delete requests, for all calendar-related events to have a high priority, etc.), and/or for specific folders.
  • The prioritization engine 241 can track and resolve conflicts in priorities set by different entities. For example, manual settings specified by the user may take precedence over device OS settings, network provider parameters/limitations (e.g., set in default for a network service area, geographic locale, set for a specific time of day, or set based on service/fee type) may limit any user-specified settings and/or application-set priorities. In some instances, a manual synchronization request received from a user can override some, most, or all priority settings in that the requested synchronization is performed when requested, regardless of the individually assigned priority or an overall priority ranking for the requested action.
  • Priority can be specified and tracked internally in any known and/or convenient manner, including but not limited to, a binary representation, a multi-valued representation, a graded representation and all are considered to be within the scope of the disclosed technology.
  • TABLE I
    Change Change
    (initiated on device) Priority (initiated on server) Priority
    Send email High Receive email High
    Delete email Low Edit email Often not
    (Un)read email Low possible to sync
    (Low if
    possible)
    Move message Low New email in deleted Low
    Read more High items
    Download High Delete an email Low
    attachment (Un)Read an email Low
    New Calendar event High Move messages Low
    Edit/change Calendar High Any calendar change High
    event Any contact change High
    Add a contact High Wipe/lock device High
    Edit a contact High Settings change High
    Search contacts High Any folder change High
    Change a setting High Connector restart High (if no
    Manual send/receive High changes nothing
    is sent)
    IM status change Medium Social Network Medium
    Status Updates
    Auction outbid or High Sever Weather Alerts High
    change notification
    Weather Updates Low News Updates Low
  • Table I above shows, for illustration purposes, some examples of transactions with examples of assigned priorities in a binary representation scheme. Additional assignments are possible for additional types of events, requests, transactions, and as previously described, priority assignments can be made at more or less granular levels, e.g., at the session level or at the application level, etc.
  • As shown by way of example in the above table, in general, lower priority requests/transactions can include, updating message status as being read, unread, deleting of messages, deletion of contacts; higher priority requests/transactions, can in some instances include, status updates, new IM chat message, new email, calendar event update/cancellation/deletion, an event in a mobile gaming session, or other entertainment related events, a purchase confirmation through a web purchase or online, request to load additional or download content, contact book related events, a transaction to change a device setting, location-aware or location-based events/transactions, or any other events/request/transactions initiated by a user or where the user is known to be, expected to be, or suspected to be waiting for a response, etc.
  • Inbox pruning events (e.g., email, or any other types of messages), are generally considered low priority and absent other impending events, generally will not trigger use of the radio on the device 250. Specifically, pruning events to remove old email or other content can be ‘piggy backed’ with other communications if the radio is not otherwise on, at the time of a scheduled pruning event. For example, if the user has preferences set to ‘keep messages for 7 days old,’ then instead of powering on the device radio to initiate a message delete from the device 250 the moment that the message has exceeded 7 days old, the message is deleted when the radio is powered on next. If the radio is already on, then pruning may occur as regularly scheduled.
  • The request/transaction manager 235, can use the priorities for requests (e.g., by the prioritization engine 241) to manage outgoing traffic from the device 250 for resource optimization (e.g., to utilize the device radio more efficiently for battery conservation). For example, transactions/requests below a certain priority ranking may not trigger use of the radio on the device 250 if the radio is not already switched on, as controlled by the connection manager 265. In contrast, the radio controller 266 can turn on the radio such a request can be sent when a request for a transaction is detected to be over a certain priority level.
  • In one embodiment, priority assignments (such as that determined by the local proxy 275 or another device/entity) can be used cause a remote device to modify its communication with the frequency with the mobile device or wireless device. For example, the remote device can be configured to send notifications to the device 250 when data of higher importance is available to be sent to the mobile device or wireless device.
  • In one embodiment, transaction priority can be used in conjunction with characteristics of user activity in shaping or managing traffic, for example, by the traffic shaping engine 255. For example, the traffic shaping engine 255 can, in response to detecting that a user is dormant or inactive, wait to send low priority transactions from the device 250, for a period of time. In addition, the traffic shaping engine 255 can allow multiple low priority transactions to accumulate for batch transferring from the device 250 (e.g., via the batching module 257). In one embodiment, the priorities can be set, configured, or readjusted by a user. For example, content depicted in Table I in the same or similar form can be accessible in a user interface on the device 250 and for example, used by the user to adjust or view the priorities.
  • The batching module 257 can initiate batch transfer based on certain criteria. For example, batch transfer (e.g., of multiple occurrences of events, some of which occurred at different instances in time) may occur after a certain number of low priority events have been detected, or after an amount of time elapsed after the first of the low priority event was initiated. In addition, the batching module 257 can initiate batch transfer of the cumulated low priority events when a higher priority event is initiated or detected at the device 250. Batch transfer can otherwise be initiated when radio use is triggered for another reason (e.g., to receive data from a remote device such as host server 100 or 300). In one embodiment, an impending pruning event (pruning of an inbox), or any other low priority events, can be executed when a batch transfer occurs.
  • In general, the batching capability can be disabled or enabled at the event/transaction level, application level, or session level, based on any one or combination of the following: user configuration, device limitations/settings, manufacturer specification, network provider parameters/limitations, platform-specific limitations/settings, device OS settings, etc. In one embodiment, batch transfer can be initiated when an application/window/file is closed out, exited, or moved into the background; users can optionally be prompted before initiating a batch transfer; users can also manually trigger batch transfers.
  • In one embodiment, the local proxy 275 locally adjusts radio use on the device 250 by caching data in the cache 285. When requests or transactions from the device 250 can be satisfied by content stored in the cache 285, the radio controller 266 need not activate the radio to send the request to a remote entity (e.g., the host server 100, 300, as shown in FIG. 1A and FIG. 3A or a content provider/application server such as the server/provider 110 shown in the examples of FIG. 1A and FIG. 1B). As such, the local proxy 275 can use the local cache 285 and the cache policy manager 245 to locally store data for satisfying data requests to eliminate or reduce the use of the device radio for conservation of network resources and device battery consumption.
  • In leveraging the local cache, once the request/transaction manager 225 intercepts a data request by an application on the device 250, the local repository 285 can be queried to determine if there is any locally stored response, and also determine whether the response is valid. When a valid response is available in the local cache 285, the response can be provided to the application on the device 250 without the device 250 needing to access the cellular network or wireless broadband network.
  • If a valid response is not available, the local proxy 275 can query a remote proxy (e.g., the server proxy 325 of FIG. 3A) to determine whether a remotely stored response is valid. If so, the remotely stored response (e.g., which may be stored on the server cache 135 or optional caching server 199 shown in the example of FIG. 1B) can be provided to the mobile device, possibly without the mobile device 250 needing to access the cellular network, thus relieving consumption of network resources.
  • If a valid cache response is not available, or if cache responses are unavailable for the intercepted data request, the local proxy 275, for example, the caching policy manager 245, can send the data request to a remote proxy (e.g., server proxy 325 of FIG. 3A) which forwards the data request to a content source (e.g., application server/content provider 110 of FIG. 1A) and a response from the content source can be provided through the remote proxy, as will be further described in the description associated with the example host server 300 of FIG. 3A. The cache policy manager 245 can manage or process requests that use a variety of protocols, including but not limited to HTTP, HTTPS, IMAP, POP, SMTP, XMPP, and/or ActiveSync. The caching policy manager 245 can locally store responses for data requests in the local database 285 as cache entries, for subsequent use in satisfying same or similar data requests.
  • The caching policy manager 245 can request that the remote proxy monitor responses for the data request and the remote proxy can notify the device 250 when an unexpected response to the data request is detected. In such an event, the cache policy manager 245 can erase or replace the locally stored response(s) on the device 250 when notified of the unexpected response (e.g., new data, changed data, additional data, etc.) to the data request. In one embodiment, the caching policy manager 245 is able to detect or identify the protocol used for a specific request, including but not limited to HTTP, HTTPS, IMAP, POP, SMTP, XMPP, and/or ActiveSync. In one embodiment, application specific handlers (e.g., via the application protocol module 246 of the caching policy manager 245) on the local proxy 275 allows for optimization of any protocol that can be port mapped to a handler in the distributed proxy (e.g., port mapped on the proxy server 325 in the example of FIG. 3A).
  • In one embodiment, the local proxy 275 notifies the remote proxy such that the remote proxy can monitor responses received for the data request from the content source for changed results prior to returning the result to the device 250, for example, when the data request to the content source has yielded same results to be returned to the mobile device. In general, the local proxy 275 can simulate application server responses for applications on the device 250, using locally cached content. This can prevent utilization of the cellular network for transactions where new/changed data is not available, thus freeing up network resources and preventing network congestion.
  • In one embodiment, the local proxy 275 includes an application behavior detector 236 to track, detect, observe, monitor, applications (e.g., proxy-aware and/or unaware applications 210 and 220) accessed or installed on the device 250. Application behaviors, or patterns in detected behaviors (e.g., via the pattern detector 237) of one or more applications accessed on the device 250 can be used by the local proxy 275 to optimize traffic in a wireless network needed to satisfy the data needs of these applications.
  • For example, based on detected behavior of multiple applications, the traffic shaping engine 255 can align content requests made by at least some of the applications over the network (wireless network) (e.g., via the alignment module 256). The alignment module 256 can delay or expedite some earlier received requests to achieve alignment. When requests are aligned, the traffic shaping engine 255 can utilize the connection manager to poll over the network to satisfy application data requests. Content requests for multiple applications can be aligned based on behavior patterns or rules/settings including, for example, content types requested by the multiple applications (audio, video, text, etc.), device (e.g., mobile or wireless device) parameters, and/or network parameters/traffic conditions, network service provider constraints/specifications, etc.
  • In one embodiment, the pattern detector 237 can detect recurrences in application requests made by the multiple applications, for example, by tracking patterns in application behavior. A tracked pattern can include, detecting that certain applications, as a background process, poll an application server regularly, at certain times of day, on certain days of the week, periodically in a predictable fashion, with a certain frequency, with a certain frequency in response to a certain type of event, in response to a certain type user query, frequency that requested content is the same, frequency with which a same request is made, interval between requests, applications making a request, or any combination of the above, for example.
  • Such recurrences can be used by traffic shaping engine 255 to offload polling of content from a content source (e.g., from an application server/content provider 110 of FIG. 1A) that would result from the application requests that would be performed at the mobile device or wireless device 250 to be performed instead, by a proxy server (e.g., proxy server 125 of FIG. 1B or proxy server 325 of FIG. 3A) remote from the device 250. Traffic shaping engine 255 can decide to offload the polling when the recurrences match a rule. For example, there are multiple occurrences or requests for the same resource that have exactly the same content, or returned value, or based on detection of repeatable time periods between requests and responses such as a resource that is requested at specific times during the day. The offloading of the polling can decrease the amount of bandwidth consumption needed by the mobile device 250 to establish a wireless (cellular or other wireless broadband) connection with the content source for repetitive content polls.
  • As a result of the offloading of the polling, locally cached content stored in the local cache 285 can be provided to satisfy data requests at the device 250, when content change is not detected in the polling of the content sources. As such, when data has not changed, application data needs can be satisfied without needing to enable radio use or occupying cellular bandwidth in a wireless network. When data has changed and/or new data has been received, the remote entity to which polling is offloaded, can notify the device 250. The remote entity may be the host server 300 as shown in the example of FIG. 3A.
  • In one embodiment, the local proxy 275 can mitigate the need/use of periodic keep-alive messages (heartbeat messages) to maintain TCP/IP connections, which can consume significant amounts of power thus having detrimental impacts on mobile device battery life. The connection manager 265 in the local proxy (e.g., the heartbeat manager 267) can detect, identify, and intercept any or all heartbeat (keep-alive) messages being sent from applications.
  • The heartbeat manager 267 can prevent any or all of these heartbeat messages from being sent over the cellular, or other network, and instead rely on the server component of the distributed proxy system (e.g., shown in FIG. 1B) to generate the and send the heartbeat messages to maintain a connection with the backend (e.g., application server/provider 110 in the example of FIG. 1A).
  • The local proxy 275 generally represents any one or a portion of the functions described for the individual managers, modules, and/or engines. The local proxy 275 and device 250 can include additional or less components; more or less functions can be included, in whole or in part, without deviating from the novel art of the disclosure.
  • FIG. 2B depicts a block diagram illustrating another example of components in the application behavior detector 236 and the caching policy manager 245 in the local proxy 275 on the client-side of the distributed proxy system shown in the example of FIG. 2A.
  • In one embodiment, the caching policy manager 245 includes a cache appropriateness decision engine 246, a poll schedule generator 247, an application protocol module 248, a cache or connect selection engine 249 and/or a local cache invalidator 244. The cache appropriateness decision engine 246 can further include a timing predictor 246 a and/or a content predictor 246 b and the cache or connect selection engine 249 includes a response scheduler 249 a. One embodiment of caching policy manager 245 includes an application cache policy repository 243.
  • In one embodiment, the application behavior detector 236 includes a pattern detector 237, a poll interval detector 238, an application profile generator 239, and/or a priority engine 241. The poll interval detector 238 may further include a long poll detector 238 a having a response/request tracking engine 238 b. The poll interval detector 238 may further include a long poll hunting detector 238 c. The application profile generator 239 can further include a response delay interval tracker 239 a.
  • The pattern detector 237, application profile generator 239, and the priority engine 241 were also described in association with the description of the pattern detector shown in the example of FIG. 2A. One embodiment further includes an application profile repository 242 which can be used by the local proxy 275 to store information or metadata regarding application profiles (e.g., behavior, patterns, type of HTTP requests, etc.)
  • The cache appropriateness decision engine 246 can detect, assess, or determine, whether content from a content source (e.g., application server/content provider 110 in the example of FIG. 1B) with which a mobile device (e.g., any wireless device) 250 interacts, has content that may be suitable for caching. In some instances, content from a given application server/content provider (e.g., the server/content provider 110 of FIG. 1B) is determined to be suitable for caching based on a set of criteria, for example, criteria specifying time criticality of the content that is being requested from the content source. In one embodiment, the local proxy (e.g., the local proxy 175 or 275 of FIG. 1B and FIG. 2A) applies a selection criteria to store the content from the host server which is requested by an application as cached elements in a local cache on the mobile device to satisfy subsequent requests made by the application.
  • The cache appropriateness decision engine 246, further based on detected patterns of requests sent from the mobile device 250 (e.g., by a application (e.g., a mobile application) or other types of clients on the device 250) and/or patterns of received responses can detect predictability in requests and/or responses. If the requests are made with some identifiable pattern (e.g., regular intervals, intervals having a detectable pattern, or trend (e.g., increasing, decreasing, constant) etc.) the timing predictor 246 a can determine that the requests made by a given application on a device is predictable and identify it to be potentially appropriate for caching, at least from a timing standpoint. An identifiable pattern or trend can generally include any application or client behavior which may be simulated either locally, for example, on the local proxy 275 on the mobile device 250 or simulated remotely, for example, by the proxy server 325 on the host 300, or a combination of local and remote simulation to emulate application behavior.
  • In one embodiment, for a long poll type request, the local proxy 175 can begin to cache responses on a third request when the response delay times for the first two responses are the same, substantially the same, or detected to be increasing in intervals. In general, the received responses for the first two responses should be the same, and upon verifying that the third response received for the third request is the same (e.g., if R0=R1=R2), the third response can be locally cached on the mobile device. Less or more same responses may be required to begin caching, depending on the type of application, type of data, type of content, or user preferences, or carrier/network operator specifications.
  • Increasing response delays with same responses for long polls can indicate a hunting period (e.g., a period in which the application/client on the mobile device is seeking the longest time between a request and response that a given network will allow, a timing diagram showing timing characteristics is illustrated in FIG. 8), as detected by the long poll hunting detector 238 c of the application behavior detector 236.
  • An example can be described below using T0, T1, T2, where T indicates the delay time between when a request is sent and when a response (e.g., the response header) is detected/received for consecutive requests:

  • T0=Response0(t)−Request0(t)=180 s. (+/−tolerance)

  • T1=Response1(t)−Request1(t)=240 s. (+/−tolerance)

  • T2=Response2(t)−Request2(t)=500 s. (+/−tolerance)
  • In the example timing sequence shown above, T0<T1<T2, this may indicate a hunting pattern for a long poll when network timeout has not yet been reached or exceeded. Furthermore, if the responses R0, R1, and R2 received for the three requests are the same, R2 can be cached. In this example, R2 is cached during the long poll hunting period, without waiting for the long poll to settle, thus expediting response caching (e.g., this is optional accelerated caching behavior which can be implemented for all or select applications).
  • As such, the local proxy 275 can specify information that can be extracted from the timing sequence shown above (e.g., polling schedule, polling interval, polling type) to the proxy server and begin caching and to request the proxy server to begin polling and monitoring the source (e.g., using any of T0, T1, T2 as polling intervals but typically T2, or the largest detected interval without timing out, and for which responses from the source is received will be sent to the proxy server 325 of FIG. 3A for use in polling the content source (e.g., application server/service provider 310)).
  • However, if the time intervals are detected to be getting shorter, the application (e.g., a mobile application)/client may still be hunting for a time interval for which a response can be reliably received from the content source (e.g., application/server server/provider 110 or 310), and as such caching typically should not begin until the request/response intervals indicate the same time interval or an increasing time interval, for example, for a long poll type request.
  • An example of handling a detected decreasing delay can be described below using T0, T1, T2, T3, and T4 where T indicates the delay time between when a request is sent and when a response (e.g., the response header) is detected/received for consecutive requests:

  • T0=Response0(t)−Request0(t)=180 s. (+/−tolerance)

  • T1=Response1(t)−Request1(t)=240 s. (+/−tolerance)

  • T2=Response2(t)−Request2(t)=500 s. (+/−tolerance)

  • T3=Time out at 700 s. (+/−tolerance)

  • T4=Response4(t)−Request4(t)=600 (+/−tolerance)
  • If a pattern for response delays T1<T2<T3>T4 is detected, as shown in the above timing sequence, (e.g., detected by the long poll hunting detector 238 c of the application behavior detector 236), it can be determined that T3 likely exceeded the network time out during a long poll hunting period. In Request 3, a response likely was not received since the connection was terminated by the network, application, server, or other reason before a response was sent or available. On Request 4 (after T4), if a response (e.g., Response 4) is detected or received, the local proxy 275 can then use the response for caching (if the content repeatability condition is met). The local proxy can also use T4 as the poll interval in the polling schedule set for the proxy server to monitor/poll the content source.
  • Note that the above description shows that caching can begin while long polls are in hunting mode in the event of detecting increasing response delays, as long as responses are received and not timed out for a given request. This can be referred to as the optional accelerated caching during long poll hunting. Caching can also begin after the hunting mode (e.g., after the poll requests have settled to a constant or near constant delay value) has completed. Note that hunting may or may not occur for long polls and when hunting occurs, the proxy 275 can generally detect this and determine whether to begin to cache during the hunting period (increasing intervals with same responses) or wait until the hunt settles to a stable value.
  • In one embodiment, the timing predictor 246 a of the cache appropriateness decision engine 246 can track timing of responses received from outgoing requests from a application (e.g., a mobile application) or client, to detect any identifiable patterns which can be partially wholly reproducible, such that locally cached responses can be provided to the requesting client on the mobile device 250 in a manner that simulates content source (e.g., application server/content provider 110 or 310) behavior. For example, the manner in which (e.g., from a timing standpoint) responses or content would be delivered to the requesting application/client on the device 250. This ensures preservation of user experience when responses to application or mobile client requests are served from a local and/or remote cache instead of being retrieved/received directly from the content source (e.g., application, content provider 110 or 310).
  • In one embodiment, the decision engine 246 or the timing predictor 246 a determines the timing characteristics a given application (e.g., a mobile application) or client from, for example, the request/response tracking engine 238 a and/or the application profile generator 239 (e.g., the response delay interval tracker 239 a). Using the timing characteristics, the predictor 246 a determines whether the content received in response to the requests are suitable or are potentially suitable for caching. For example, poll request intervals between two consecutive requests from a given application can be used to determine whether request intervals are repeatable (e.g., constant, near constant, increasing with a pattern, decreasing with a pattern, etc.) and can be predicted and thus reproduced at least some of the times either exactly or approximated within a tolerance level.
  • In some instances, the timing characteristics of a given request type for a specific application, or for multiple requests of an application, or for multiple applications can be stored in the application profile repository 242. The application profile repository 242 can generally store any type of information or metadata regarding application request/response characteristics including timing patterns, timing repeatability, content repeatability, etc.
  • The application profile repository 242 can also store metadata indicating the type of request used by a given application (e.g., long polls, long-held HTTP requests, HTTP streaming, push, COMET push, etc.) Application profiles indicating request type by applications can be used when subsequent same/similar requests are detected, or when requests are detected from an application which has already been categorized. In this manner, timing characteristics for the given request type or for requests of a specific application which has been tracked and/or analyzed, need not be reanalyzed.
  • Application profiles can be associated with a time-to-live (e.g., or a default expiration time). The use of an expiration time for application profiles, or for various aspects of an application or request's profile can be used on a case by case basis. The time-to-live or actual expiration time of application profile entries can be set to a default value or determined individually, or a combination thereof. Application profiles can also be specific to wireless networks, physical networks, network operators, or specific carriers, for example.
  • A given application profile may also be treated or processed differently (e.g., different behavior of the local proxy 275 and the remote proxy 325) depending on the mobile account associated with a mobile device from which the application is being accessed. For example, a higher paying account, or a premier account may allow more frequent access of the wireless network or higher bandwidth allowance thus affecting the caching policies implemented between the local proxy 275 and proxy server 325 with an emphasis on better performance compared to conservation of resources. A given application profile may also be treated or processed differently under different wireless network conditions (e.g., based on congestion or network outage, etc.).
  • The cache appropriateness decision engine 246 (e.g., the content predictor 246 b) can definitively identify repeatability or identify indications of repeatability, potential repeatability, or predictability in responses received from a content source (e.g., the content host/application server 110 shown in the example of FIG. 1A-B). Repeatability can be detected by, for example, tracking at least two responses received from the content source and determines if the two responses are the same. The two responses may or may not be responses sent in response to consecutive requests. In one embodiment, hash values of the responses received for requests from a given application are used to determine repeatability of content (with or without heuristics) for the application in general and/or for the specific request. Additional same responses may be required for some applications or under certain circumstances.
  • Repeatability in received content need not be 100% ascertained. For example, responses can be determined to be repeatable if a certain number or a certain percentage of responses are the same, or similar. The certain number or certain percentage of same/similar responses can be tracked over a select period of time, set by default or set based on the application generating the requests (e.g., whether the application is highly dynamic with constant updates or less dynamic with infrequent updates). Any indicated predictability or repeatability, or possible repeatability can be utilized by the distributed system in caching content to be provided to a requesting application or client on the mobile device 250,
  • Note that cache appropriateness can be determined, tracked, and managed for multiple clients or applications on the mobile device 250. Cache appropriateness can also be determined for different requests or request types initiated by a given client or application on the mobile device 250. The caching policy manager 245, along with the timing predictor 246 a and/or the content predictor 246 b which heuristically determines or estimates predictability or potential predictability, can track, manage and store cacheability information for various application or various requests for a given application. Cacheability information may also include conditions (e.g., an application can be cached at certain times of the day, or certain days of the week, or certain requests of a given application can be cached, or all requests with a given destination address can be cached) under which caching is appropriate which can be determined and/or tracked by the cache appropriateness decision engine 246 and stored and/or updated when appropriate in the application cache policy repository 243 coupled to the cache appropriateness decision engine 246.
  • The information in the application cache policy repository 243 regarding cacheability of requests, applications, and/or associated conditions can be used later on when same requests are detected. In this manner, the decision engine 246, and/or the timing and content predictors 246 a/b need not track and reanalyze request/response timing and content characteristics to make an assessment regarding cacheability. In addition, the cacheability information can in some instances be shared with local proxies of other mobile devices, by way of direct communication or via the host server (e.g., proxy server 325 of host server 300).
  • For example, cacheability information detected by the local proxy 275 on various mobile devices can be sent to a remote host server or a proxy server 325 on the host server (e.g., host server 300 or proxy server 325 shown in the example of FIG. 3A, host 100 and proxy server 125 in the example of FIG. 1A-B). The remote host or proxy server can then distribute the information regarding application-specific, request-specific cacheability information and/or any associated conditions to various mobile devices or their local proxies in a wireless network or across multiple wireless networks (same service provider or multiple wireless service providers) for their use.
  • The selection criteria can further include, by way of example, but not limitation, state of the mobile device indicating whether the mobile device is active or inactive, network conditions, and/or radio coverage statistics. The cache appropriateness decision engine 246 can any one or any combination of the criteria, and in any order, in identifying sources for which caching may be suitable.
  • Once application servers/content providers having identified or detected content that is potentially suitable for local caching on the mobile device 250, the cache policy manager 245 can proceed to cache the associated content received from the identified sources by storing content received from the content source as cache elements in a local cache (e.g., local cache 185 or 285 shown in the examples of FIG. 1B and FIG. 2A, respectively) on the mobile device 250. The content source can also be identified to a proxy server (e.g., proxy server 125 or 325 shown in the examples of FIG. 1B and FIG. 3A, respectively) remote from and in wireless communication with the mobile device 250 such that the proxy server can monitor the content source (e.g., application server/content provider 110) for new or changed data. Similarly, the local proxy (e.g., the local proxy 175 or 275 of FIG. 1B and FIG. 2A, respectively) can identify to the proxy server that content received from a specific application server/content provider is being stored as cached elements in the local cache.
  • Once content has been locally cached, the cache policy manager 245 can, upon receiving future polling requests to contact the application server/content host (e.g., 110 or 310), can retrieve the cached elements from the local cache to respond to the polling request made at the mobile device 250 such that a radio of the mobile device is not activated to service the polling request. Such servicing and fulfilling application (e.g., a mobile application) requests locally via a local cache entries allow for more efficient resource and mobile network traffic utilization and management since network bandwidth and other resources need not be used to request/receive poll responses which may have not changed from a response that has already been received at the mobile device 250.
  • For example, the local proxy 275, upon receipt of an outgoing request from its mobile device 250 or from an application or other type of client on the mobile device 250 can intercept the request and determine whether a cached response is available in the local cache 285 of the mobile device 250. If so, the outgoing request is responded to, by the local proxy 275 using the cached response on the cache of the mobile device. As such, the outgoing request can be filled or satisfied without a need to send the outgoing request over the wireless network, thus conserving network resources and battery consumption.
  • In one embodiment, the responding to the requesting application/client on the device 250 is timed to correspond to a manner in which the content server would have responded to the outgoing request over a persistent connection (e.g., over the persistent connection, or long-held HTTP connection, long poll type connection, that would have been established absent interception by the local proxy). The timing of the response can be emulated or simulated by the local proxy 275 to preserve application behavior such that end user experience is not affected, or minimally affected by serving stored content from the local cache 285 rather than fresh content received from the intended content source (e.g., content host/application server 110 of FIG. 1A-B). The timing can be replicated exactly or estimated within a tolerance parameter, which may go unnoticed by the user or treated similarly by the application so as to not cause operation issues.
  • For example, the outgoing request can be a request for a persistent connection intended for the content server (e.g., application server/content provider of examples of FIG. 1A-1B). In a persistent connection (e.g., long poll, COMET-style push or any other push simulation in asynchronous HTTP requests, long-held HTTP request, HTTP streaming, or others) with a content source (server), the connection is held for some time after a request is sent. The connection can typically be persisted between the mobile device and the server until content is available at the server to be sent to the mobile device. Thus, there typically can be some delay in time between when a long poll request is sent and when a response is received from the content source. If a response is not provided by the content source for a certain amount of time, the connection may also terminate due to network reasons (e.g., socket closure) if a response is not sent.
  • Thus, to emulate a response from a content server sent over a persistent connection (e.g., a long poll style connection), the manner of response of the content server can be simulated by allowing a time interval to elapse before responding to the outgoing request with the cached response. The length of the time interval can be determined on a request by request basis or on an application by application (client by client basis), for example.
  • In one embodiment, the time interval is determined based on request characteristics (e.g., timing characteristics) of an application on the mobile device from which the outgoing request originates. For example, poll request intervals (e.g., which can be tracked, detected, determined by the long poll detector 238 a of the poll interval detector 238) can be used to determine the time interval to wait before responding to a request with a local cache entry and managed by the response scheduler 249 a.
  • One embodiment of the cache policy manager 245 includes a poll schedule generator 247 which can generate a polling schedule for one or more applications on the mobile device 250. The polling schedule can specify a polling interval that can be employed by the proxy server (e.g., proxy server 125 or 325 shown in the examples of FIG. 1B and FIG. 3A) in monitoring the content source for one or more applications. The polling schedule can be determined, for example, based on the interval between the polling requests directed to the content source from the mobile device. In one embodiment, the poll interval detector 238 of the application behavior detector 236 can monitor polling requests directed to a content source from the mobile device 250 in order to determine an interval between the polling requests made from any or all applications (e.g., including mobile applications).
  • For example, the poll interval detector 238 can track requests and responses for applications or clients on the device 250. In one embodiment, consecutive requests are tracked prior to detection of an outgoing request initiated from the application (e.g., a mobile application) on the mobile device 250, by the same mobile client or application. In one embodiment, an outgoing request from a mobile device 250 is detected to be for a persistent connection (e.g., a long poll, COMET style push, and long-held (HTTP) request) based on timing characteristics of prior requests from the same application or client on the mobile device 250. For example, requests and/or corresponding responses can be tracked by the request/response tracking engine 238 b of the long poll detector 238 a of the poll interval detector 238.
  • The timing characteristics of the consecutive requests can be determined to set up a polling schedule for the application or client. The polling schedule can be used to monitor the content source (content source/application server) for content changes such that cached content stored on the local cache in the mobile device 250 can be appropriated managed (e.g., updated or discarded). In one embodiment, the timing characteristics can include, for example, a response delay time (‘D’) and/or an idle time (‘IT’).
  • The response delay time and idle time typical of a long poll are illustrated in the timing diagram shown below and also described further in detail with references to FIG. 17A-B. In one embodiment, the response/request tracking engine 238 b can track requests and responses to determine, compute, and/or estimate, the timing diagrams for applicant or client requests.
  • For example, the response/request tracking engine 238 b detects a first request (Request 0) initiated by a client on the mobile device and a second request (Request 1) initiated by the client on the mobile device after a response is received at the mobile device responsive to the first request. The second request is one that is subsequent to the first request. The relationship between requests can be seen in the following timing diagrams of FIG. 17A-17B.
  • In one embodiment, the response/request tracking engine 238 b can track requests and responses to determine, compute, and/or estimate, the timing diagrams for applicant or client requests. The response/request tracking engine 238 b can detect a first request initiated by a client on the mobile device and a second request initiated by the client on the mobile device after a response is received at the mobile device responsive to the first request. The second request is one that is subsequent to the first request.
  • The response/request tracking engine 238 b further determines relative timings between the first, second requests, and the response received in response to the first request. In general, the relative timings can be used by the long poll detector 238 a to determine whether requests generated by the application are long poll requests.
  • Note that in general, the first and second requests that are used by the response/request tracking engine 238 b in computing the relative timings are selected for use after a long poll hunting period has settled or in the event when long poll hunting does not occur. Timing characteristics that are typical of a long poll hunting period is illustrated in the example of FIG. 8 and can be, for example, detected by the long poll hunting detector 238 c. In other words, the requests tracked by the response/request tracking engine 238 b and used for determining whether a given request is a long poll occurs after the long poll has settled (e.g., shown in 810 of FIG. 8 after the hunting mode 805 has completed).
  • In one embodiment, the long poll hunting detector 238 c can identify or detect hunting mode, by identifying increasing request intervals (e.g., increasing delays), for example. The long poll hunting detector 238 a can also detect hunting mode by detecting increasing request intervals, followed by a request with no response (e.g., connection timed out), or by detecting increasing request intervals followed by a decrease in the interval. In addition, the long poll hunting detector 238 c can apply a filter value or a threshold value to request-response time delay value (e.g., an absolute value) above which the detected delay can be considered to be a long poll request-response delay, The filter value can be any suitable value characteristic of long polls and/or network conditions (e.g., 2 s, 5 s, 10 s, 15 s, 20 s., etc.) can be used as a filter or threshold value.
  • The response delay time (‘D’) refers to the start time to receive a response after a request has been sent and the idle refers to time to send a subsequent request after the response has been received. In one embodiment, the outgoing request is detected to be for a persistent connection based on a comparison (e.g., performed by the tracking engine 238 b) of the response delay time relative (‘D’) or average of (‘D’) (e.g., any average over any period of time) to the idle time (‘IT’), for example, by the long poll detector 238 a. The number of averages used can be fixed, dynamically adjusted, or changed over a longer period of time. For example, the requests initiated by the client are determined to be long poll requests if the response delay time interval is greater than the idle time interval (D>IT or D>>IT). In one embodiment, the tracking engine 238 b of the long poll detector computes, determines, or estimates the response delay time interval as the amount of time elapsed between time of the first request and initial detection or full receipt of the response.
  • In one embodiment, a request is detected to be for a persistent connection when the idle time (‘IT’) is short since persistent connections, established in response to long poll requests or long poll HTTP requests, for example, can also be characterized in detecting immediate or near-immediate issuance of a subsequent request after receipt of a response to a previous request (e.g., IT ˜0). As such the idle time (‘IT”) can also be used to detect such immediate or near-immediate re-request to identify long poll requests. The absolute or relative timings determined by the tracking engine 238 b are used to determine whether the second request is immediately or near-immediately re-requested after the response to the first request is received. For example, a request may be categorized as a long poll request if D+RT+IT˜D+RT since IT is small for this to hold true. IT may be determined to be small if it is less than a threshold value. Note that the threshold value could be fixed or calculated over a limited time period (a session, a day, a month, etc.), or calculated over a longer time period (e.g., several months or the life of the analysis). For example, for every request, the average IT can be determined, and the threshold can be determined using this average IT (e.g., the average IT less a certain percentage may be used as the threshold). This can allow the threshold to automatically adapt over time to network conditions and changes in server capability, resource availability or server response. A fixed threshold can take upon any value including by way of example but not limitation (e.g., 1 s. 2 s. 3 s. . . . etc.).
  • In one embodiment, the long poll detector 238 a can compare the relative timings (e.g., determined by the tracker engine 238 b) to request-response timing characteristics for other applications to determine whether the requests of the application are long poll requests. For example, the requests initiated by a client or application can be determined to be long poll requests if the response delay interval time (‘D’) or the average response delay interval time (e.g., averaged over x number of requests or any number of delay interval times averaged over x amount of time) is greater than a threshold value.
  • The threshold value can be determined using response delay interval times for requests generated by other clients, for example by the request/response tracking engine 238 b and/or by the application profile generator 239 (e.g., the response delay interval tracker 239 a). The other clients may reside on the same mobile device and the threshold value is determined locally by components on the mobile device. The threshold value can be determined for all requests over all resources server over all networks, for example. The threshold value can be set to a specific constant value (e.g., 30 seconds, for example) to be used for all requests, or any request which does not have an applicable threshold value (e.g., long poll is detected if D>30 seconds).
  • In some instances, the other clients reside on different mobile devices and the threshold can be determined by a proxy server (e.g., proxy server 325 of the host 300 shown in the example of FIG. 3A-B) which is external to the mobile device and able to communicate over a wireless network with the multiple different mobile devices, as will be further described with reference to FIG. 3B.
  • In one embodiment, the cache policy manager 245 sends the polling schedule to the proxy server (e.g., proxy server 125 or 325 shown in the examples of FIG. 1B and FIG. 3A) and can be used by the proxy server in monitoring the content source, for example, for changed or new content (updated response different from the cached response associated with a request or application). A polling schedule sent to the proxy can include multiple timing parameters including but not limited to interval (time from request 1 to request 2), a time out interval (time to wait for response, used in long polls, for example). Referring to the timing diagram of a request/response timing sequence shown in the example of FIG. 17A-B, the timing intervals ‘RI’, ‘D’, ‘RT’, and/or ‘IT’, or some statistical manipulation of the above values (e.g., average, standard deviation, etc.) may all or in part be sent to the proxy server.
  • For example, in the case when the local proxy 275 detects a long poll, the various timing intervals in a request/response timing sequence (e.g., ‘D’, ‘RT’, and/or ‘IT’) can be sent to the proxy server 325 for use in polling the content source (e.g., application server/content host 110). The local proxy 275 can also identify to the proxy server 325 that a given application or request to be monitored is a long poll request (e.g., instructing the proxy server to set a ‘long poll flag’, for example). In addition, the proxy server uses the various timing intervals to determine when to send keep-alive indications on behalf of mobile devices.
  • The local cache invalidator 244 of the caching policy manager 245 can invalidate cache elements in the local cache (e.g., cache 185 or 285) when new or changed data (e.g., updated response) is detected from the application server/content source for a given request. The cached response can be determined to be invalid for the outgoing request based on a notification received from the proxy server (e.g., proxy 325 or the host server 300). The source which provides responses to requests of the mobile client can be monitored to determine relevancy of the cached response stored in the cache of the mobile device 250 for the request. For example, the cache invalidator 244 can further remove/delete the cached response from the cache of the mobile device when the cached response is no longer valid for a given request or a given application.
  • In one embodiment, the cached response is removed from the cache after it is provided once again to an application which generated the outgoing request after determining that the cached response is no longer valid. The cached response can be provided again without waiting for the time interval or provided again after waiting for a time interval (e.g., the time interval determined to be specific to emulate the response delay in a long poll). In one embodiment, the time interval is the response delay ‘D’ or an average value of the response delay ‘D’ over two or more values.
  • The new or changed data can be, for example, detected by the proxy server (e.g., proxy server 125 or 325 shown in the examples of FIG. 1B and FIG. 3A). When a cache entry for a given request/poll has been invalidated, the use of the radio on the mobile device 250 can be enabled (e.g., by the local proxy or the cache policy manager 245) to satisfy the subsequent polling requests, as further described with reference to the interaction diagram of FIG. 4B.
  • One embodiment of the cache policy manager 245 includes a cache or connect selection engine 249 which can decide whether to use a locally cached entry to satisfy a poll/content request generated at the mobile device 250 by an application or widget. For example, the local proxy 275 or the cache policy manger 245 can intercept a polling request, made by an application (e.g., mobile application) on the mobile device, to contact the application server/content provider. The selection engine 249 can determine whether the content received for the intercepted request has been locally stored as cache elements for deciding whether the a radio of the mobile device needs to be activated to satisfy the request made by the application (e.g., a mobile application) and also determine whether the cached response is still valid for the outgoing request prior to responding to the outgoing request using the cached response.
  • In one embodiment, the local proxy 275, in response to determining that relevant cached content exists and is still valid, can retrieve the cached elements from the local cache to provide a response to the application which made the polling request such that a radio of the mobile device is not activated to provide the response to the application. In general, the local proxy 275 continues to provide the cached response each time the outgoing request is received until the updated response different from the cached response is detected.
  • When it is determined that the cached response is no longer valid, a new request for a given request is transmitted over the wireless network for an updated response. The request can be transmitted to the application server/content provider (e.g., server/host 110) or the proxy server on the host server (e.g., proxy 325 on the host 300) for a new and updated response. In one embodiment the cached response can be provided again as a response to the outgoing request if a new response is not received within the time interval, prior to removal of the cached response from the cache on the mobile device; an example process flow is illustrated in the flow chart of FIG. 10.
  • FIG. 3A depicts a block diagram illustrating an example of server-side components (host server 300 and proxy server 325) in a distributed proxy and cache system that manages traffic in a wireless network for resource conservation, content caching, and/or traffic management.
  • The host server 300 generally includes, for example, a network interface 308 and/or one or more repositories 312, 314, 316. Note that server 300 may be any portable/mobile or non-portable device, server, cluster of computers and/or other types of processing units (e.g., any number of a machine shown in the example of FIG. 11) able to receive, transmit signals to satisfy data requests over a network including any wired or wireless networks (e.g., WiFi, cellular, Bluetooth, etc.).
  • The network interface 308 can include networking module(s) or devices(s) that enable the server 300 to mediate data in a network with an entity that is external to the host server 300, through any known and/or convenient communications protocol supported by the host and the external entity. Specifically, the network interface 308 allows the server 308 to communicate with multiple devices including mobile phone devices 350, and/or one or more application servers/content providers 310.
  • The host server 300 can store information about connections (e.g., network characteristics, conditions, types of connections, etc.) with devices in the connection metadata repository 312. Additionally, any information about third party application or content providers can also be stored in 312. The host server 300 can store information about devices (e.g., hardware capability, properties, device settings, device language, network capability, manufacturer, device model, OS, OS version, etc.) in the device information repository 314. Additionally, the host server 300 can store information about network providers and the various network service areas in the network service provider repository 316.
  • The communication enabled by network interface 308 allows for simultaneous connections (e.g., including cellular connections) with devices 350 and/or connections (e.g., including wired/wireless, HTTP, Internet connections, LAN, WiFi, etc.) with content servers/providers 310, to manage the traffic between devices 350 and content providers 310, for optimizing network resource utilization and/or to conserver power (battery) consumption on the serviced devices 350. The host server 300 can communicate with mobile devices 350 serviced by different network service providers and/or in the same/different network service areas. The host server 300 can operate and is compatible with devices 350 with varying types or levels of mobile capabilities, including by way of example but not limitation, 1G, 2G, 2G transitional (2.5G, 2.75G), 3G (IMT-2000), 3G transitional (3.5G, 3.75G, 3.9G), 4G (IMT-advanced), etc.
  • In general, the network interface 308 can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G type networks such as, LTE, WiMAX, etc.), Bluetooth, WiFi, or any other network whether or not connected via a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, a bridge router, a hub, a digital media receiver, and/or a repeater.
  • The host server 300 can further include, server-side components of the distributed proxy and cache system which can include, a proxy server 325 and a server cache 335. In one embodiment, the proxy server 325 can include an HTTP access engine 345, a caching policy manager 355, a proxy controller 365, a traffic shaping engine 375, a new data detector 347 and/or a connection manager 395.
  • The HTTP access engine 345 may further include a heartbeat manager 398 the proxy controller 365 may further include a data invalidator module 358 the traffic shaping engine 375 may further include a control protocol 376 and a batching module 377. Additional or less components/modules/engines can be included in the proxy server 325 and each illustrated component.
  • As used herein, a “module,” “a manager,” a “handler,” a “detector,” an “interface,” a “controller,” a “normalizer,” a “generator,” an “invalidator,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module, manager, handler, detector, interface, controller, normalizer, generator, invalidator, or engine can be centralized or its functionality distributed. The module, manager, handler, detector, interface, controller, normalizer, generator, invalidator, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor. As used herein, a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid. Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.
  • In the example of a device (e.g., mobile device 350) making an application or content request to an application server or content provider 310, the request may be intercepted and routed to the proxy server 325, which is coupled to the device 350 and the application server/content provider 310. Specifically, the proxy server is able to communicate with the local proxy (e.g., proxy 175 and 275 of the examples of FIG. 1 and FIG. 2 respectively) of the mobile device 350, the local proxy forwards the data request to the proxy server 325 for, in some instances, further processing, and if needed, for transmission to the application server/content server 310 for a response to the data request.
  • In such a configuration, the host 300, or the proxy server 325 in the host server 300 can utilize intelligent information provided by the local proxy in adjusting its communication with the device in such a manner that optimizes use of network and device resources. For example, the proxy server 325 can identify characteristics of user activity on the device 350 to modify its communication frequency. The characteristics of user activity can be determined by, for example, the activity/behavior awareness module 366 in the proxy controller 365, via information collected by the local proxy on the device 350.
  • In one embodiment, communication frequency can be controlled by the connection manager 395 of the proxy server 325, for example, to adjust push frequency of content or updates to the device 350. For instance, push frequency can be decreased by the connection manager 395 when characteristics of the user activity indicate that the user is inactive. In one embodiment, when the characteristics of the user activity indicate that the user is subsequently active after a period of inactivity, the connection manager 395 can adjust the communication frequency with the device 350 to send data that was buffered as a result of decreased communication frequency, to the device 350.
  • In addition, the proxy server 325 includes priority awareness of various requests, transactions, sessions, applications, and/or specific events. Such awareness can be determined by the local proxy on the device 350 and provided to the proxy server 325. The priority awareness module 367 of the proxy server 325 can generally assess the priority (e.g., including time-criticality, time-sensitivity, etc.) of various events or applications; additionally, the priority awareness module 367 can track priorities determined by local proxies of devices 350.
  • In one embodiment, through priority awareness, the connection manager 395 can further modify communication frequency (e.g., use or radio as controlled by the radio controller 396) of the server 300 with the devices 350. For example, the server 300 can notify the device 350, thus requesting use of the radio if it is not already in use, when data or updates of an importance/priority level which meets a criteria becomes available to be sent.
  • In one embodiment, the proxy server 325 can detect multiple occurrences of events (e.g., transactions, content, data received from server/provider 310) and allow the events to accumulate for batch transfer to device 350. Batch transfer can be cumulated and transfer of events can be delayed based on priority awareness and/or user activity/application behavior awareness, as tracked by modules 366 and/or 367. For example, batch transfer of multiple events (of a lower priority) to the device 350 can be initiated by the batching module 377 when an event of a higher priority (meeting a threshold or criteria) is detected at the server 300. In addition, batch transfer from the server 300 can be triggered when the server receives data from the device 350, indicating that the device radio is already in use and is thus on. In one embodiment, the proxy server 325 can order the each messages/packets in a batch for transmission based on event/transaction priority, such that higher priority content can be sent first, in case connection is lost or the battery dies, etc.
  • In one embodiment, the server 300 caches data (e.g., as managed by the caching policy manager 355) such that communication frequency over a network (e.g., cellular network) with the device 350 can be modified (e.g., decreased). The data can be cached, for example in the server cache 335, for subsequent retrieval or batch sending to the device 350 to potentially decrease the need to turn on the device 350 radio. The server cache 335 can be partially or wholly internal to the host server 300, although in the example of FIG. 3A, it is shown as being external to the host 300. In some instances, the server cache 335 may be the same as and/or integrated in part or in whole with another cache managed by another entity (e.g., the optional caching proxy server 199 shown in the example of FIG. 1B), such as being managed by an application server/content provider 110, a network service provider, or another third party.
  • In one embodiment, content caching is performed locally on the device 350 with the assistance of host server 300. For example, proxy server 325 in the host server 300 can query the application server/provider 310 with requests and monitor changes in responses. When changed or new responses are detected (e.g., by the new data detector 347), the proxy server 325 can notify the mobile device 350, such that the local proxy on the device 350 can make the decision to invalidate (e.g., indicated as out-dated) the relevant cache entries stored as any responses in its local cache. Alternatively, the data invalidator module 368 can automatically instruct the local proxy of the device 350 to invalidate certain cached data, based on received responses from the application server/provider 310. The cached data is marked as invalid, and can get replaced or deleted when new content is received from the content server 310.
  • Note that data change can be detected by the detector 347 in one or more ways. For example, the server/provider 310 can notify the host server 300 upon a change. The change can also be detected at the host server 300 in response to a direct poll of the source server/provider 310. In some instances, the proxy server 325 can in addition, pre-load the local cache on the device 350 with the new/updated data. This can be performed when the host server 300 detects that the radio on the mobile device is already in use, or when the server 300 has additional content/data to be sent to the device 350.
  • One or more the above mechanisms can be implemented simultaneously or adjusted/configured based on application (e.g., different policies for different servers/providers 310). In some instances, the source provider/server 310 may notify the host 300 for certain types of events (e.g., events meeting a priority threshold level). In addition, the provider/server 310 may be configured to notify the host 300 at specific time intervals, regardless of event priority.
  • In one embodiment, the proxy server 325 of the host 300 can monitor/track responses received for the data request from the content source for changed results prior to returning the result to the mobile device, such monitoring may be suitable when data request to the content source has yielded same results to be returned to the mobile device, thus preventing network/power consumption from being used when no new/changes are made to a particular requested. The local proxy of the device 350 can instruct the proxy server 325 to perform such monitoring or the proxy server 325 can automatically initiate such a process upon receiving a certain number of the same responses (e.g., or a number of the same responses in a period of time) for a particular request.
  • In one embodiment, the server 300, for example, through the activity/behavior awareness module 366, is able to identify or detect user activity, at a device that is separate from the mobile device 350. For example, the module 366 may detect that a user's message inbox (e.g., email or types of inbox) is being accessed. This can indicate that the user is interacting with his/her application using a device other than the mobile device 350 and may not need frequent updates, if at all.
  • The server 300, in this instance, can thus decrease the frequency with which new or updated content is sent to the mobile device 350, or eliminate all communication for as long as the user is detected to be using another device for access. Such frequency decrease may be application specific (e.g., for the application with which the user is interacting with on another device), or it may be a general frequency decrease (e.g., since the user is detected to be interacting with one server or one application via another device, he/she could also use it to access other services) to the mobile device 350.
  • In one embodiment, the host server 300 is able to poll content sources 310 on behalf of devices 350 to conserve power or battery consumption on devices 350. For example, certain applications on the mobile device 350 can poll its respective server 310 in a predictable recurring fashion. Such recurrence or other types of application behaviors can be tracked by the activity/behavior module 366 in the proxy controller 365. The host server 300 can thus poll content sources 310 for applications on the mobile device 350, that would otherwise be performed by the device 350 through a wireless (e.g., including cellular connectivity). The host server can poll the sources 310 for new or changed data by way of the HTTP access engine 345 to establish HTTP connection or by way of radio controller 396 to connect to the source 310 over the cellular network. When new or changed data is detected, the new data detector can notify the device 350 that such data is available and/or provide the new/changed data to the device 350.
  • In one embodiment, the connection manager 395 determines that the mobile device 350 is unavailable (e.g., the radio is turned off) and utilizes SMS to transmit content to the device 350, for instance via the SMSC shown in the example of FIG. 1B. SMS is used to transmit invalidation messages, batches of invalidation messages, or even content in the case the content is small enough to fit into just a few (usually one or two) SMS messages. This avoids the need to access the radio channel to send overhead information. The host server 300 can use SMS for certain transactions or responses having a priority level above a threshold or otherwise meeting a criteria. The server 300 can also utilize SMS as an out-of-band trigger to maintain or wake-up an IP connection as an alternative to maintaining an always-on IP connection.
  • In one embodiment, the connection manager 395 in the proxy server 325 (e.g., the heartbeat manager 398) can generate and/or transmit heartbeat messages on behalf of connected devices 350, to maintain a backend connection with a provider 310 for applications running on devices 350.
  • For example, in the distributed proxy system, local cache on the device 350 can prevent any or all heartbeat messages needed to maintain TCP/IP connections required for applications, from being sent over the cellular, or other network, and instead rely on the proxy server 325 on the host server 300 to generate and/or send the heartbeat messages to maintain a connection with the backend (e.g., application server/provider 110 in the example of FIG. 1A). The proxy server can generate the keep-alive (heartbeat) messages independent of the operations of the local proxy on the mobile device.
  • The repositories 312, 314, and/or 316 can additionally store software, descriptive data, images, system information, drivers, and/or any other data item utilized by other components of the host server 300 and/or any other servers for operation. The repositories may be managed by a database management system (DBMS), for example but not limited to, Oracle, DB2, Microsoft Access, Microsoft SQL Server, PostgreSQL, MySQL, FileMaker, etc.
  • The repositories can be implemented via object-oriented technology and/or via text files, and can be managed by a distributed database management system, an object-oriented database management system (OODBMS) (e.g., ConceptBase, FastDB Main Memory Database Management System, JDOInstruments, ObjectDB, etc.), an object-relational database management system (ORDBMS) (e.g., Informix, OpenLink Virtuoso, VMDS, etc.), a file system, and/or any other convenient or known database management package.
  • FIG. 3B depicts a block diagram illustrating another example of components in the caching policy manager 355 in the proxy server 325 on the server-side of the distributed proxy system shown in the example of FIG. 3A.
  • The caching policy manager 355, in one embodiment, can further include, an application protocol module 356, a content source monitoring engine 357 having a poll schedule manager 358, and/or an updated or new content detector 359. In one embodiment, the poll schedule manager 358 further includes a host timing simulator 358 a and/or a long poll request detector/manager 358 b.
  • In one embodiment, the proxy server (e.g., the proxy server 125 or 325 of the examples of FIG. 1B and FIG. 3A) can monitor a content source for new or changed data, for example, via the monitoring engine 357. The proxy server, as shown, is an entity external to the mobile device 250 of FIG. 2A-B. The content source (e.g., application server/content provider 110 of FIG. 1B) can be one that has been identified to the proxy server (e.g., by the local proxy) as having content that is being locally cached on a mobile device (e.g., mobile device 150 or 250). The content source can be monitored, for example, by the monitoring engine 357 at a frequency that is based on polling frequency of the content source at the mobile device. The poll schedule can be, for example, generated by the local proxy and sent to the proxy server. The poll frequency can be tracked and/or managed by the poll schedule manager 358.
  • For example, the proxy server can poll the host (e.g., content provider/application server) on behalf of the mobile device and simulate the polling behavior of the client to the host, via the host timing simulator 358 a. The polling behavior can be simulated to include characteristics of a long poll request-response sequences experienced in a persistent connection with the host (e.g., by the long poll request detector/manager 358 b). Note that once a polling interval/behavior is set, the local proxy 275 on the device-side and/or the proxy server 325 on the server-side can verify whether application and application server/content host behavior match or can be represented by this predicted pattern. In general, the local proxy and/or the proxy server can detect deviations and when appropriate, re-evaluate and compute, determine, or estimate another polling interval.
  • In one embodiment, the caching policy manager 355 on the server-side of the distribute proxy can, in conjunction with, or independent of the proxy server 275 on the mobile device, identify or detect long poll requests. For example, the caching policy manager 355 can determine a threshold value to be used in comparison with a response delay interval time (interval time ‘D’ shown in the example timing diagram of FIG. 17A-B) in a request-response sequence for an application request to identify or detect long poll requests, possible long poll requests (e.g., requests for a persistent connection with a host with which the client communicates, including but not limited to, a long-held HTTP request, a persistent connection enabling COMET style push, request for HTTP streaming, etc.), or other requests which can otherwise be treated as a long poll request.
  • For example, the threshold value can be determined by the proxy 325 using response delay interval times for requests generated by clients/applications across mobile devices which may be serviced by multiple different cellular or wireless networks. Since the proxy 325 resides on host 300 is able to communicate with multiple mobile devices via multiple networks, the caching policy manager 355 has access to application/client information at a global level which can be used in setting threshold values to categorize and detect long polls.
  • By tracking response delay interval times across applications across devices over different or same networks, the caching policy manager 355 can set one or more threshold values to be used in comparison with response delay interval times for long poll detection. Threshold values set by the proxy server 325 can be static or dynamic, and can be associated with conditions and/or a time-to-live (an expiration time/date in relative or absolute terms).
  • In addition, the caching policy manager 35 of the proxy 325 can determine the threshold value, in whole or in part, further based on network delays of a given wireless network, networks serviced by a given carrier (service provider), or multiple wireless networks. The proxy 325 can also determine the threshold value for identification of long poll requests based on delays of one or more application server/content provider (e.g., 110) to which application, mobile application, or mobile client requests are directed.
  • The proxy server can detect new or changed data at a monitored content source and transmits a message to the mobile device notifying it of such a change such that the mobile device (or the local proxy on the mobile device) can take appropriate action (e.g., to invalidate the cache elements in the local cache. In some instances, the proxy server (e.g., the caching policy manager 355) upon detecting new or changed data, can also store the new or changed data in its cache (e.g., the server cache 135 or 335 of the examples of FIG. 1B and FIG. 3A, respectively). The new/updated data stored in the server cache can in some instances, be used to satisfy content requests at the mobile device, for example, after the proxy server has notified the mobile device of the new/changed content and that the locally cached content has been invalidated.
  • FIG. 4A depicts a diagram showing how data requests from a mobile device 450 to an application server/content provider 495 in a wireless network can be coordinated by a distributed proxy system 460 in a manner such that network and battery resources are conserved through using content caching and monitoring performed by the distributed proxy system 460.
  • In satisfying application or client requests on a mobile device 450 without the distributed proxy system 460, the mobile device 450, or the software widget executing on the device 450 performs a data request 402 (e.g., an HTTP GET, POST, or other request) directly to the application server 495 and receives a response 404 directly from the server/provider 495. If the data has been updated, the widget on the mobile device 450 can refreshes itself to reflect the update and waits for small period of time and initiates another data request to the server/provider 495.
  • In one embodiment, the requesting client or software widget 455 on the device 450 can utilize the distributed proxy system 460 in handling the data request made to server/provider 495. In general, the distributed proxy system 460 can include a local proxy 465 (which is typically considered a client-side component of the system 460 and can reside on the mobile device 450), a caching proxy 475 (considered a server-side component 470 of the system 460 and can reside on the host server 485 or be wholly or partially external to the host server 485), a host server 485. The local proxy 465 can be connected to the caching proxy 475 and host server 485 via any network or combination of networks.
  • When the distributed proxy system 460 is used for data/application requests, the widget 455 can perform the data request 406 via the local proxy 465. The local proxy 465, can intercept the requests made by device applications, and can identify the connection type of the request (e.g., an HTTP get request or other types of requests). The local proxy 465 can then query the local cache for any previous information about the request (e.g., to determine whether a locally stored response is available and/or still valid). If a locally stored response is not available or if there is an invalid response stored, the local proxy 465 can update or store information about the request, the time it was made, and any additional data, in the local cache. The information can be updated for use in potentially satisfying subsequent requests.
  • The local proxy 465 can then send the request to the host server 485 and the host server 485 can perform the request 406 and returns the results in response 408. The local proxy 465 can store the result and in addition, information about the result and returns the result to the requesting widget 455.
  • In one embodiment, if the same request has occurred multiple times (within a certain time period) and it has often yielded same results, the local proxy 465 can notify 410 the server 485 that the request should be monitored (e.g., steps 412 and 414) for result changes prior to returning a result to the local proxy 465 or requesting widget 455.
  • In one embodiment, if a request is marked for monitoring, the local proxy 465 can now store the results into the local cache. Now, when the data request 416, for which a locally response is available, is made by the widget 455 and intercepted at the local proxy 465, the local proxy 465 can return the response 418 from the local cache without needing to establish a connection communication over the wireless network.
  • In addition, the server proxy performs the requests marked for monitoring 420 to determine whether the response 422 for the given request has changed. In general, the host server 485 can perform this monitoring independently of the widget 455 or local proxy 465 operations. Whenever an unexpected response 422 is received for a request, the server 485 can notify the local proxy 465 that the response has changed (e.g., the invalidate notification in step 424) and that the locally stored response on the client should be erased or replaced with a new response.
  • In this case, a subsequent data request 426 by the widget 455 from the device 450 results in the data being returned from host server 485 (e.g., via the caching proxy 475) and in step 428, the request is satisfied from the caching proxy 475. Thus, through utilizing the distributed proxy system 460 the wireless (cellular) network is intelligently used when the content/data for the widget or software application 455 on the mobile device 450 has actually changed. As such, the traffic needed to check for the changes to application data is not performed over the wireless (cellular) network. This reduces the amount of generated network traffic and shortens the total time and the number of times the radio module is powered up on the mobile device 450, thus reducing battery consumption, and in addition, frees up network bandwidth.
  • FIG. 4B depicts an interaction diagram showing how application polls having data requests made by an application/widget 455 (e.g., mobile application) on a mobile device to an application server/content provider 495 in a wireless network can be cached on the local proxy 465 and managed by the distributed caching system (including local proxy 465 and the host server 485 (having server cache 435 or caching proxy server 475).
  • In one example, when the application/widget 455 (e.g., mobile application/widget) polls an application server/provider 432, the poll can locally be intercepted 434 on the mobile device by local proxy 465. The local proxy 465 can detect that the cached content is available for the polled content in the request and can thus retrieve a response from the local cache to satisfy the intercepted poll 436, without requiring use of wireless network bandwidth or other wireless network resources. The application/widget 455 (e.g., mobile application/widget) can subsequently receive a response to the poll from a cache entry 438.
  • In another example, the application/widget 455 (e.g., mobile application/widget) polls the application server/provider 440. The poll is intercepted 442 by the local proxy 465 and detects that cache content is unavailable in the local cache and decides to set up the polled source for caching 444. To satisfy the request, the poll is forwarded to the content source 446. The application server/provider 495 receives the poll request from the application and provides a response to satisfy the current request 448. In 450, the mobile application/widget 455 receives the response from the application server/provider to satisfy the request.
  • In conjunction, in order to set up content caching, the local proxy 465 tracks the polling frequency of the application and can set up a polling schedule to be sent to the host server 452. The local proxy sends the cache set up to the host server 454. The host server 485 can use the cache set up which includes, for example, an identification of the application server/provider to be polled and optionally a polling schedule 456. The host server 485 can now poll the application server/provider 495 to monitor responses to the request 458, on behalf of the mobile device. The application server receives the poll from the host server and responds 460. The host server 485 determines that the same response has been received and polls the application server 495, for example, according to the specified polling schedule 462. The application server/content provider 495 receives the poll and responds accordingly 464.
  • The host server 485 detects changed or new responses, and notifies the local proxy 465. The host server 485 can additional store the changed or new response in the server cache or caching proxy 468. The local proxy 465 receives notification from the host server 485 that new or changed data is now available and can invalidate the affected cache entries 470. The next time the application/widget 455 (e.g., mobile application/widget) generates the same request for the same server/content provider 472, the local proxy determines that no valid cache entry is available and instead retrieves a response from the server cache 474, for example, through an HTTP connection. The host server 485 receives the request for the new response and sends the response back to the local proxy 475. The request is thus satisfied from the server cache or caching proxy 478 without the need for the mobile device to utilize its radio or to consume mobile network bandwidth thus conserving network resources.
  • Alternatively, when the application generates the same request in step 480, the local proxy 465, in response to determining that no valid cache entry is available, forwards the poll to the application server/provider 482 over the mobile network. The application server/provider 495 receives the poll and sends the response back to the mobile device 484 over the mobile network. The request is thus satisfied from the server/provider using the mobile network 486.
  • FIG. 5 depicts a diagram showing one example process for implementing a hybrid IP and SMS power saving mode on a mobile device 550 using a distributed proxy and cache system (e.g., such as the distributed system shown in the example of FIG. 1B).
  • In step 502, the local proxy (e.g., proxy 175 in the example of FIG. 1B) monitors the device for user activity. When the user is determined to be active, server push is active. For example, always-on-push IP connection can be maintained and if available, SMS triggers can be immediately sent to the mobile device 550 as it becomes available.
  • In process 504, after the user has been detected to be inactive or idle over a period of time (e.g., the example is shown for a period of inactivity of 20 min.), the local proxy can adjust the device to go into the power saving mode. In the power saving mode, when the local proxy receives a message or a correspondence from a remote proxy (e.g., the server proxy 135 in the example of FIG. 1B) on the server-side of the distributed proxy and cache system, the local proxy can respond with a call indicating that the device 550 is currently in power save mode (e.g., via a power save remote procedure call). In some instances, the local proxy can take the opportunity to notify multiple accounts or providers (e.g., 510A, and 510B) of the current power save status (e.g., timed to use the same radio power-on event).
  • In one embodiment, the response from the local proxy can include a time (e.g., the power save period) indicating to the remote proxy (e.g., server proxy 135) and/or the application server/providers 510A/B when the device 550 is next able to receive changes or additional data. A default power savings period can be set by the local proxy.
  • In one embodiment, if new, changed, or different data or event is received before the end of any one power saving period, then the wait period communicated to the servers 510A/B can be the existing period, rather than an incremented time period. In response, the remote proxy server, upon receipt of power save notification from the device 550, can stop sending changes (data or SMS's) for the period of time requested (the wait period). At the end of the wait period, any notifications received can be acted upon and changes sent to the device 550, for example, as a single batched event or as individual events. If no notifications come in, then push can be resumed with the data or an SMS being sent to the device 550. The proxy server can time the poll or data collect event to optimize batch sending content to the mobile device 550 to increase the chance that the client will receive data at the next radio power on event.
  • Note that the wait period can be updated in operation in real time to accommodate operating conditions. For example, the local proxy can adjust the wait period on the fly to accommodate the different delays that occur in the system.
  • Detection of user activity in step 508 at the device 550 causes the power save mode to be exited. When the device 550 exits power save mode, it can begin to receive any changes associated with any pending notifications. If a power saving period has expired, then no power save cancel call may be needed as the proxy server will already be in traditional push operation mode.
  • In one embodiment, power save mode is not applied when the device 550 is plugged into a charger. This setting can be reconfigured or adjusted by the user or another party. In general, the power save mode can be turned on and off, for example, by the user via a user interface on device 550. In general, timing of power events to receive data can be synchronized with any power save calls to optimize radio use.
  • FIG. 6 depicts another flow diagram 600 illustrating an example process for distributed content caching between a mobile device and a proxy server and the distributed management of content caching.
  • As shown in the distributed system interaction diagram in the example of FIG. 4A, the disclosed technology is a distributed caching model with various aspects of caching tasks split between the client-side/mobile device side (e.g., mobile device 450 in the example of FIG. 4A) and the server side (e.g., server side 470 including the host server 485 and/or the optional caching proxy 475).
  • In general the device-side responsibilities can include, deciding whether a response to a particular request can be and/or should be cached. The device-side of the proxy can make this decision based on information (e.g., timing characteristics, detected pattern, detected pattern with heuristics, indication of predictability or repeatability) collected from/during both request and response, and cache it (e.g., storing it in a local cache on the mobile device). The device side can also notify the server-side in the distributed cache system of the local cache event and notify it monitor the content source (e.g., application server/content provider 110 of FIG. 1A-B).
  • The device side can further instruct the server side of the distributed proxy to periodically validate the cache response (e.g., by way of polling, or sending polling requests to the content source). The device side can further decide whether a response to a particular cache request should be returned from the local cache (e.g., whether a cache hit is detected). The decision can be made by the device side (e.g., the local proxy on the device) using information collected from/during request and/or responses received from the content source.
  • In general, the server-side responsibilities can include, validating cached responses for relevancy (e.g., determine whether a cached response is still valid or relevant to its associated request). The server-side can send the mobile device an invalidation request to notify the device side when a cached response is detected to be no longer valid or no longer relevant (e.g., the server invalidates a given content source). The device side then can remove the response from the local cache.
  • The diagram of FIG. 6 illustrates caching logic processes performed for each detected or intercepted request (e.g., HTTP request) detected at a mobile device (e.g., client-side of the distributed proxy). In step 602, the client-side of the proxy (e.g., local proxy 275 shown in FIG. 2A-B or mobile device 450 of FIG. 4A) receives a request (from an application, mobile application or mobile client). In step 604, URL is normalized and in step the client-side checks to determine if the request is cacheable, in step 606. If the request is determined to be not cacheable in step 612, the request is sent to the source (application server/content provider) in step 608 and the response is received 610 and delivered to the requesting application 622, similar to a request-response sequence without interception by the client side proxy.
  • If the request is determined to be cacheable, in step 612, the client-side looks up the cache to determine whether a cache entry exists for the current request. If so, in step 624, the client-side can determine whether the entry is valid and if so, the client side can check the request to see if includes a validator (e.g., a modified header or an entity tag) in step 628. For example, the concept of validation is eluded to in section 13.3 of RFC 2616 which describes in possible types of headers. and forms a validating response 632 if so to be delivered to the requesting application in step 622. If the request does not include a validator as determined by step 628, a response is formed from the local cache in step 630 and delivered to the requesting application in step 622. This validation step can be used for content that would otherwise normally be considered un-cacheable.
  • If, instead, in step 624, the cache entry is found but determined to be no longer valid or invalid, the client side of the proxy, sends the request to the content source (application server/content host) and receives a response directly fro the source in step 618. Alternative processing may be performed if the content is determined to include non-cacheable content. Similarly, if in step 612, a cache entry was not found during the look up, the request is also sent in step 616. Once the response is received, the client side checks the response to determine if it is cacheable in step 626. If so, the response is cached in step 620. The client then sends another poll in step 614 and then delivers the response to the requesting application in step 622.
  • FIG. 7 depicts an interaction diagram showing cache management by a distributed proxy system 760 of content delivered to an application 755 (e.g., mobile application) over a long-held request while ensuring freshness of content delivered.
  • The diagram illustrates an example process for how cached responses received in long-held requests (e.g., long-held HTTP request, long polls, or HTTP streaming) are provided to the requesting application 755 and management of expired/invalid/non-relevant cache entries. A long-held request can be any request for a persistent connection that is held between the device and the server until a response is available at the server to be sent (or pushed) to the device. The long-held request or long-held HTTP request can allow the device/server interaction to simulate content push over the persistent connection (e.g., COMET style push), for example, over a persisted connection over HTTP.
  • In step 702, the application 755 sends a request which is detected and intercepted by the local proxy 765 on the mobile device 750 on the client/device-side of the proxy system 760. Note that the request- response sequence 702, 704, 706, and 708 shown occurs after a long poll hunting period, which may sometimes be performed by the application (e.g., a mobile application) sending long poll requests. The long poll hunting period may or may not be performed, but when performed, allows the requesting application 755 to find the longest amount of time it can hold a request with the end server/provider 795 open before the connection times out (e.g., due to network reason, such as socket closures).
  • A timing diagram showing characteristics request-response timing sequences is further illustrated in the example of FIG. 8. In general, the device proxy 750 or local proxy 765 is able to detect request-response pattern sequences initiated from the application 755 while long poll hunting and can wait until the hunting period has settled prior to caching responses from long poll request. The request-response steps shown between 702 and 710 occur after any long poll hunting request/response pairs, if it was performed by the requesting application 755.
  • The request is sent to the server/provider 795 in step 704 and the request times out or closes in 706, when the server 795 sends a response in step 708 back to the application 755 on the device side 750. The connection times out when the server 795 sends a response in step 708 due to the nature of the long-held request send in step 702. The response, when sent is also intercepted by the local proxy 760 on the mobile side 750 of the distributed proxy 760, for local caching.
  • Once cached, the local proxy 765 notifies the server-side 770 of the proxy of the system 760 and requests that the server-side 770 proxy (e.g., the host server 785) begin to monitor the server/provider 790 in step 712. In step 714, the server-side proxy 770 now begins to send requests to the server/provider in order to monitor responses received 716 from the server/provider 795.
  • The next time the application 755 sends the request 718, the local proxy 765 determines that a local cache entry now exists and waits for a period of time (e.g., a long poll interval) 720 before providing the cached response back to the application 755, in step 722. The local proxy 765 allows the period of time to elapse to simulate the actual behavior of the server/provider 795 with the application 755, since in an actual long poll request which goes over the network, a response is not received until after some delay, characteristic of the given long poll.
  • Starting at step 724, another request is sent from the application (e.g., a mobile application) 755 when the response from the server/provider 795 in step 726 is validated. The local proxy 765 waits for an interval in step 728 before replying with the cache entry in step 744. However, in the interim, the server-side proxy 770 in monitoring responses sends a request in step 730 to the server/provider 795 and detects content change in the response received 732 from the server/provider 795 in step 734. The server-side 770 proxy thus caches the changed/updated response data at the server-side proxy in step 736 and notifies the local proxy 765 to invalidate the associated cache entry 738.
  • The local proxy 765, in response to receiving an invalidation notice, sets the associated entry to be invalidated as being ‘transient’ in step 740, or otherwise annotated or indicated to be marked for deletion or removal. At this point, the local proxy 765 replies to the application 755 again with the transient cache in step 744. The local proxy 765 also connects to the server-side proxy 770 to obtain the new cached data at the server-side 770, in step 742, and receives a response (the new/updated response) at step 746.
  • The next time the same request is sent from the application (e.g., a mobile application) in step 748, the local proxy 765 now can reply with the response received from the server cache, in step 750. Thus, even in the event when a cache entry has been invalidated, the application (e.g., a mobile application) request need not be sent over the network (e.g., wireless, or cellular network) to receive a current/relevant response. The subsequent request 752 is sent to the local proxy 765 for processing (e.g., forwarded to the application server/content provider 795) in step 754.
  • FIG. 8 depicts a timing diagram 800 showing hunting mode behavior 805 in a long poll request and a timing diagram showing timing characteristics when the long poll has settled 810.
  • In hunting mode 805, the request times are held for an increasing amount of time (180, 360 . . . 1024 s.) until a request times out without receiving a response from the server (as shown in 802, 804, 806, 808). After this time is detected, the request times are now held at some time less than the time it took for a time out (e.g., now 500 s.) and used to send future long poll requests. The diagram 810 shows the timing characteristics of request/response pairs after the long poll hunting period has settled. These characteristics can be detected and identified in operation by the local proxy and/or the remote proxy for handling during caching. As previously described, the distributed caching system can either begin caching (optionally) while the application is still in long poll hunting mode, or begin caching after the hunting period 805 has completed and the application is in settled mode as in 810. In general, if a decrease in time interval is detected, the response is not cached until the local or remote proxy can verify that a subsequent received response meets cacheability conditions.
  • In general, long poll hunting may or may not be performed by mobile apps or clients but the distributed system includes mechanisms to detect long poll hunting activity for application long polls and can simply ignore the long poll hunting requests and begin caching after the hunting period has elapsed and the long polls have settled at some constant or near constant interval value or apply logic to begin caching during the hunting period, thus enabling accelerated caching to enhance performance and improve user experience.
  • FIG. 9 depicts a flow chart illustrating an example process for caching content pushed to a mobile device in a persistent connection from a content server over a wireless network.
  • In process 902, a request initiated from a mobile client on a mobile device is detected. The request is detected to be a long poll request (e.g., long-held request, long-held-HTTP request) or one for any type of persistent connection (e.g., enabling push emulation by the server, COMET style push, HTTP streaming, etc.).
  • In process 904, it is determined that a cached response is available on a cache of the mobile device for the request from the mobile device. In process 906, a content server is monitored for an updated response different from the cached response associated with the request, for example, by a proxy server able to establish wireless connectivity to the mobile device.
  • In process 908, it is determined whether the cached response is still valid, prior to responding to the outgoing request using the cached response. If not, the process flow continues to process ‘A’ continued in the example of FIG. 10. The updated content/response for the outgoing request can be detected by the proxy server and also optionally cached at the proxy server for retrieval by the mobile device.
  • If the cached response is determined to be valid, in process 910, a time interval is allowed to elapse. The time interval can be determined by a poll request interval by detecting, for example, the two consecutive requests from an application which generated the outgoing request from the mobile device. The two consecutive requests can be tracked prior to detection of the outgoing request initiated from the application (e.g., a mobile application) on the mobile device.
  • In process 912, to the outgoing request is responded to, using the cached response on the cache of the mobile device timed to correspond to a manner in which the content server would respond to the outgoing request. Thus, the outgoing request can be filled without a need to send the outgoing request over the wireless network. However, even though that the request can be filled or is filled without the need to go over the network, the request may still be sent over the network, for other reasons.
  • The manner of response of the content server can be simulated by allowing the time interval to elapse before responding to the outgoing request with the cached response. In one embodiment, the time interval can be determined based on request characteristics of an application on the mobile device from which the outgoing request originates. In process 914, the cached response is continued to be provided each time the outgoing request is received until the updated response different from the cached response is detected.
  • FIG. 10 depicts a diagram showing example processes that occur when removing a stored response from the local cache on a mobile device for a long poll request.
  • In process 1002, it is determined that a cached response stored on the mobile device is no longer valid for a request. The cached response can be determined to be invalid for an outgoing request based on a notification received from a proxy server coupled to the content server, which monitors the content server for updated responses that are different from the cached response stored at the local cache on the mobile device.
  • In one example, the cached response is simply removed from the cache, in process 1004. In a second example, the cached response is provided again to an application which generated the outgoing request (immediately without waiting for a time interval), in process 1006, and then removed from the cache in 1008.
  • In another example, a time interval is allowed to elapse after determination of invalid cached response, in process 1010. Then, the cached is provided once again to an application which generated the outgoing request in step 1012, before removing the cached response from the cache in step 1014.
  • In yet another example, a new response to the request is transmitted over the wireless network in step 1016 after determining that a cached response stored on the mobile device is no longer valid for the request. A time interval is allowed to elapse in step 1018 before determining whether a response has been received from the host (step 1020. If not, the cached response (the one determined to be no longer valid) is provided once again to an application in step 1022 which generated the outgoing request prior to removal from the cache, in step 1024
  • FIG. 11 depicts a flow chart illustrating an example process for using cached content provided over a long-held connection via a wireless network to satisfy mobile client requests on a mobile device.
  • In process 1102 indication of repeatability is detected in responses received for requests from a mobile client on a mobile device. In one embodiment, the repeatability can be determined when two responses received from the prior requests are the same. For example, hash values of the responses received for the prior requests are used to determined repeatability.
  • In process 1104, a cached response is stored on the mobile device for the mobile client, when the responses received in prior requests from the mobile client indicate repeatability in responses. In process 1106, a request initiated from the mobile client is detected on the mobile device. The request is detected to be one for a long-held connection over which content is pushed to the mobile client when available. The long held connection may be a long-held HTTP connection suited for content push from the content server.
  • In process 1108, it is determined whether the cached response for the request is available on the mobile device. If so, in process 1110, the manner in which a source to which the request is directed would respond to the request is simulated. In process 1112, the request is responded to using the cached response already stored on the mobile device. For example, the cached response already on the mobile device is provided to the mobile client after a time interval has elapsed. In process 1114, the request is satisfied without a need to send the request over the wireless network.
  • Concurrently and/or independently, a source which provides responses to requests of the mobile client can be monitored to determine relevancy of the cached response stored in the cache of the mobile device for the request. The source is monitored by an entity external from the mobile device.
  • FIG. 12 depicts a flow chart illustrating an example process for caching content received at a mobile device via a persistent connection over a wireless network.
  • In process 1202, a request generated by a application (e.g., a mobile application) on the mobile device is intercepted at the mobile device. The request can be intercepted by a local proxy on the mobile device. In process 1204, it is determined that the request is to establish the persistent connection with an application server hosting the application (e.g., a mobile application). The outgoing request can be detected to be for the persistent connection based on timing characteristics of prior requests generated by a same application or client on the mobile device.
  • The timing characteristics can include, one or more of, a response delay time to receive a response after a request has been sent and an idle time to send a subsequent request after the response has been received.
  • In one embodiment, the outgoing request is detected to be for the persistent connection based on a comparison of the response/delay time relative to the idle time. For example, the outgoing request is detected to be for the persistent connection when the idle time is short compared to the response/delay time. The outgoing request can also be detected to be for the persistent connection if the idle time indicates a immediate or near-immediate issuance of the subsequent request after receipt of the response.
  • In process 1206, a request (e.g., a long-held HTTP request) initiated from the mobile client is detected on the mobile device. In process 1208, a cached response is provided to the application (e.g., a mobile application) from a cache of the mobile device to satisfy the request without sending the request over the wireless network. The cached response can be provided to the application (e.g., a mobile application) after a time interval has elapsed. In process 1210, a source for updates to the cached response for the request is monitored. The cached response can be provided by a local proxy on the mobile device and the source can be monitored by a proxy server wirelessly coupled to the mobile device and able to communicate with the local proxy.
  • In process 1212, an updated response for the request is cached. The updated response for the request can be detected by the proxy server and stored at a remote cache on the proxy server. In addition, the updated response can be provided to the application (e.g., a mobile application) by the proxy server. The proxy server can notify local proxy that the cached response is no longer valid when updates to the cached response are detected from the source. In process 1214, the updated response for the request is provided to the application (e.g., a mobile application).
  • FIG. 13 depicts a flow chart illustrating an example process for detecting a long poll request initiated at a mobile device.
  • In process 1302, a first request initiated by a client on a mobile device is detected. In process 1304, a response is received at the mobile device responsive to the first request. In process 1306, a second request initiated by the client on the mobile device is detected. The second request is detected after the response is received, and it typically is the request immediately following the first request (e.g., no intervening requests between the first and second requests).
  • In process 1308, the response/delay interval time is computed as time between the time of the first request and receipt of the response. In process 1310, the idle time interval is computed as time between the time of the response to time of the second request. In process 1312, a response/delay time interval relative to an idle time interval is used to determine whether requests initiated by the client are long poll requests. The process can continue at flow B as illustrated in FIG. 14 to illustrate additional example processes for identifying a long poll and content caching and serving content from the cache.
  • Note that after detection of first and second requests, and simultaneous with or after the processing thereof, a third request from the application can be detected. Based on the third request, a trend can be determined, identified, or estimated in response/delays based on when responses for the second and third requests are received.
  • The trend may indicate an increase in response/delays, and in one embodiment, the increase indicates cacheability for the long poll requests and a third response received is stored as cache elements in a local cache. Similarly, if the trend indicates that the response delays are constant or substantially constant then the repeatability criteria for caching are met and a third response received can be stored as cache elements in a local cache. In general, substantially constant response/delay includes a tolerance within 0-5%, 5-10%, 10-15%, or 15-20% of one of the response/delays.
  • Note that content received for the application is determined to be cacheable when the received responses indicate repeatability. For example, a third response is received to the third request; and repeatability can be indicated when the first, second, and third responses are the same. Alternatively, repeatability criteria may be met when any two out of the first, second, and third responses are the same. In the case of two responses where the first response is received to the first request, a second response is received to the second request, repeatability can be indicated when the first and second responses are the same.
  • In one embodiment, in response to detecting at least one decreasing delay interval from the trend, any response received for the requesting application may not be cached yet until a next request (e.g., fourth request or any subsequent requests) is received. The request may be cached upon the next request-response sequence which increases in delay interval compared to the prior decreasing delay interval. For example, a response received for the fourth request or any subsequent request can be cached responsive to detection of an increase in delay interval from the previous delay interval, for the fourth request-response delay.
  • The fourth response can be cached responsive to detecting repeatability in content with prior responses. For example, the fourth response is cached responsive to detecting that it is the same with at least one or two prior responses or cached responsive to detecting that it is the same with at least three prior responses.
  • FIG. 14 depicts a flow chart illustrating an example process for caching content received in long poll requests of an application on a mobile device using timing intervals in a request-response timing sequence.
  • In process 1402, it is determined whether the response/delay time interval is greater than the idle time interval. If so, the requests initiated by the client are determined to be long poll requests, as in step 1406.
  • In process 1404, it is determined, for example, if the response/delay interval time is greater than a threshold value. If so, the requests initiated by the client are determined to be long poll requests as in step 1406. In process 1406, it is determined that the requests initiated by, the client are long poll requests (e.g., a long-held HTTP request, or any request suitable to emulate content push such as one for a persistent connection enabling COMET style push).
  • In general, the threshold value can be determined by the local proxy or another entity. In one embodiment, the threshold value is determined using response/delay interval times for requests generated by other clients. The other clients can be those that reside on the same mobile device and the threshold value can be determined by the local proxy on the mobile device.
  • Other clients can also reside on different mobile devices. The threshold can thus be determined by a proxy server which is external to the mobile device, and able to communicate over a wireless network with the different mobile devices. Both clients on the mobile device and clients on other devices can be used to determine the threshold, in combination or in separation.
  • In one embodiment, the threshold value can be determined, in part or in whole, based on network delays or other network-related latencies. The network delays can include delays in a cellular network or over the Internet, and can be determined by the local proxy and/or the proxy server. Indications and further information regarding mobile network delays (e.g., cell network) can be provided by cell service providers or carriers, for example.
  • In one embodiment, the threshold value is determined in part or in whole, based on delays of servers (e.g., the application server/content host 110 of FIG. 1A-B) to which the requests are directed, for example, due to internal delays (e.g., server upgrade, server maintenance, server malfunction, etc.) or network-related delays affecting the specific destination server.
  • In one embodiment, the relative timings can be determined by a local proxy on the mobile device and used by a proxy server remote from the mobile device to monitor a host to which the requests generated by the application are directed for updated responses different from those stored in the local cache for corresponding requests. Alternatively, the relative timings are detected by a proxy server remote from and coupled to the mobile device. In process 1408, responses received for the requests generated by the application are analyzed.
  • In process 1410, it is determined whether content received for the application is cacheable. The content can be determined to be cacheable, for example, when the received responses indicate repeatability. The local proxy and/or the proxy server can detect repeatability in the received response and determine that the content received for the application is cacheable. In one embodiment, hash values of the responses are compared to detect repeatability by a local proxy on the mobile device or by a proxy server remote from and coupled to the mobile device.
  • Repeatability can be determined when at least two responses received for the requests from the application are the same. In some instances, more than two same responses may be required to satisfy the requirement for content repeatability. The number of responses that need to be the same before caching begins may be set by default and be the same for all applications, or on a case by case basis with or without conditions and expiry time/dates.
  • In process 1412, the content received for the application is stored as cache elements in a local cache of the mobile device. In process 1414, subsequent requests generated by the application are received. In process 1416, subsequent requests generated by the application are responded to using the cache elements stored on the mobile device. The relative timings between responses and requests can be used when responding to requests using cached content on the mobile device to correspond to a manner in which the content server would respond to the outgoing request.
  • FIG. 15 depicts a flow chart illustrating an example process for detecting requests for a persistent connection (e.g., long poll requests, long-held HTTP requests, HTTP streaming requests) from an application using relative timings in request-response timing sequences.
  • In process 1502, the relative timings between a first request initiated by the application, a response received responsive to the first request, and a second request initiated subsequent to the first request also by the application are determined. In one embodiment, the relative timings can be used to determine whether requests generated by the application are long poll requests. Note that, in general, the first and second requests for use in computing the relative timings are selected for use after a long poll hunting period has settled or detected in the absence of a long poll hunting period. Alternatively, the first and second requests can be detected during a long poll hunting period and used to perform the analysis.
  • A timing diagram showing example timing characteristics of a long poll hunt is illustrated in the example of FIG. 8. The relative timings can be determined by for example, determining a first request time when the first request is initiated, determining a response time when the response to the first request is received, and/or determining a second request time when the second request, subsequent to the first request is initiated by the application.
  • In process 1504, it is determined if the second request is immediately or near-immediately re-requested after the response to the first request is received. If so, it can be determined that requests of the application are long poll requests or can be treated/processed/cached/managed as a long poll request, as in process 1508.
  • In process 1506, it is determined if the response/delay interval time is greater than request-response timing characteristics for other applications. If so, it can be determined that requests of the application are long poll requests or can be treated/processed/cached/managed as a long poll request, as in process 1508.
  • FIG. 16 depicts a flow chart illustrating an example process for determining whether to cache content received for an application over long-held connections on a mobile device.
  • In process 1602, a response/delay of a request from the application is determined. The response/delay time is illustrated and labeled as time interval ‘D’ in the example request-response timing sequence shown in FIG. 17 (e.g., the amount of time elapsed between when a request is sent and when a response is detected). The response delay time, can in general, be determined by a local proxy (e.g., device-side proxy) and/or the server-side proxy (e.g., proxy server). The response/delay can be used alone or in combination with other timing characteristics to characterize applications or requests for use in setting polling intervals to optimize distributed caching.
  • In process 1604, an expected response/delay is determined for other applications accessing a same wireless network as mobile device. The other applications can reside on the same mobile device and/or include applications which reside on other mobile devices serviced by the same wireless network (e.g., the same network operator, carrier, service provider, and/or the same physical infrastructure, and/or the same logical network). In some instances, applications which reside on devices serviced by different wireless networks (e.g., different carriers or different physical networks)
  • In process 1606, the expected response/delay and the response/delay of the detected request is compared. In process 1608, it is determined that requests generated by the application are requests for long-held connections if the response/delay of the application is greater than the expected response/delay. As such it is determined that requests generated by the application are requests for long-held connections, or it is determined that requests generated by the application are to be processed and treated as requests for long-held connections.
  • In process 1610, it is determined that content received for the application is cacheable, when the received responses indicate repeatability. For example, in detecting a second response received for the second request, repeatability in timing of the first request and the first response, and of the second request and the second response can be detected if present. In process 1612, the content received for the application is stored as cache elements in a local cache of the mobile device, for example, if the timing for the request-response pairs is detected to be repeatable.
  • Note that in general, the caching can begin during long poll hunting (e.g., first, second, and/or subsequent requests are part of a long hung sequence and one or more of the responses are cached). Caching while the application is in the hunting period can accelerate or expedite the caching process (e.g., begin caching sooner) to enhance performance since cache elements on the local proxy on the mobile device can be used sooner to serve application requests. The caching may also occur in the absence of long poll hunts (e.g., the first and second requests are regular requests) or after long poll hunting has settled (e.g., the first and second requests described in this flow chart occur after the hunting period).
  • In process 1614, subsequent requests generated by the application are responded to using the cache elements stored on the mobile device, to satisfy the subsequent requests without a need to send the outgoing request over the wireless network. In responding to the subsequent requests using the cached response on the mobile device cache, the responses are provided in a manner that is timed to correspond to a manner in which a content server would respond, using the response/delay interval time.
  • FIG. 17A depicts an example of a timing diagram 1700 showing timing characteristics for request and response sequences.
  • The present technology includes a distributed caching model which involves cooperation of the device-side proxy and server-side. In order for it to work after caching a response, the client-side component needs to notify the server-side proxy and also providing a rate that a particular resource (application server/content provider) must be polled at (to verify validity of cached content). After receiving this notification, the server-side proxy can then monitor the resource for changes (validating resource) and, once a change is detected, the server-side component can notify the device-side component by sending an invalidation request.
  • The client-side component needs to provide a correct and suitable polling interval to the server-side proxy (e.g., the interval at which the server-side proxy is polling the resource to monitor it) for optimal performance, since if the polling interval is too low, the load is unnecessarily increased on the server-side proxy and by increasing the polling interval, the local proxy risks providing the expired/irrelevant information to the user at the user device.
  • As previously described, timing characteristics of request-responses sequences between a requesting client/application and content provider/application server can be used to determine application behavior and/or to categorize request type. Such information can be used to determine, identify, estimate, or predict an application's polling intervals such that an optimal polling interval that the server-side proxy needs to monitor the resource at can be determined and provided to the server-side proxy.
  • The timing characteristics can include, for example, response/delay time to receive a response after a request has been sent; and an idle time to send a subsequent request after the response has been received. The relationships of the various time intervals in a response-request sequence can be seen in the timing diagram 1700.
  • Each request-response time sequence can be described using all or some of the following events: 1) Start sending request (1705); 2) Request sent; 3) Response start (1710); 4) Response end (1720); 5) Next request send (1715). The ‘Response Start’ 1710) indicates when the first bytes of response (HEADER) arrived and the ‘Response end 1715’ indicates when all response content has been received.
  • Using these events, the device-side can calculate the following intervals shown in 1700:
  • 1. RI 1708—Request interval—Time between “Request Sent 0” and “Request Sent 1.
  • 2. D 1704—Delay—Time between ‘Request sent’ and “First bytes of response (HEADER) arrived.”
  • 3. IT 1706—Idle time—Time between ‘Whole Response content received 0” and ‘Request Sent 1
  • 4. RT 1712—Response time—Time between “First bytes of response (HEADER) arrived.” and ‘Whole Response content received”
  • The following relationship of the timing characteristic in a request-response sequence: RI=D+RT+IT can be considered to extract application behavior information for use in caching content in a distributed fashion. Relative comparisons between different intervals can also be used to characterize the application and its requests.
  • In general, the device-side component of the distributed proxy can keep track of individual timing intervals in a request-response sequence and compare the values, in a relative (e.g., bigger or smaller than another interval) or absolute manner (specific duration, long, short compared to a dynamic or static threshold value, etc.). The device-side component can track these interval values over time, check for stable components and determine or identify tendencies or patterns. For example, the device-side component can detect increasing or decreasing ‘D’ 1704 in the case of long poll hunting mode for long poll requests. FIG. 17B depicts an example of a timing diagram 1750 showing timing characteristics for request/response sequences characteristic of a long poll. Note that timing diagram 1750 may not be applicable to high latency long polls.
  • In one embodiment, a request can be detected, determined, or to be a long poll request based on a comparison of the response/delay time (D 1754) relative to the idle time (IT 1756) between request 0 1755 and response start time 1760. For example, the request can be detected to be a long poll request when the idle time is short compared to the response delay time (IT 1756<D 1754). The request can also be determined to be a long poll when IT 1756 is zero or substantially zero (˜0).
  • In addition, the request can be determined or categorized as a long poll request if the idle time (IT 1756) indicates an immediate or near-immediate issuance of the subsequent request after receipt of the response (e.g., a short IT 1756). In addition, a request can be determined to be a long poll if RI 1758 =D 1754+RT 1762+IT 1756 ˜D 1754+RT 1762. In one embodiment, the response time ‘RT’ 1762 can be used to determine bit rate (e.g., size in byte*8/time).
  • In general, different combinations of time intervals provide indications about polling pattern of the specific application or request and can be used by the device-side component to generate a polling interval for the server-side component to use in monitoring the content source. FIG. 18 depicts example timing diagrams 1800 showing timing characteristics for various types of request-response sequences.
  • In the figure, 8 time line combinations are illustrated, each containing 2 blocks of request-response sequences. In each sequence, the dotted line indicates a response in a request-response interval. Sequence 1802 is characterized by a short ‘D’, short ‘RT’, and long ‘IT’. Thus sequence 1802 may be a typical poll. Sequence 1804 is characterized by a short ‘D’, a short ‘RT’, a short ‘IT’ and is indicative of a high polling rate. Sequence 1804 may also indicate that a user is actively interacting with the application and/or actively refreshing the application.
  • Sequence 1806 is characterized by a short ‘D’, a long ‘RT’ and short ‘IT,’ which can indicate possible streaming. Sequence 1808 is characterized by a short ‘D’, a long ‘RT, and a long ‘IT’ which can indicate polling of large content. Sequence 1810 is characterized by a long ‘D,’ a short ‘RT,’ and a long ‘IT, which may indicate a long poll with high latency allowed on the application level.
  • Sequence 1812, which has a long ‘D’, a short ‘RT’, and a short ‘IT’ may indicate a long poll. Sequence 1814, having a long ‘D’, long ‘RT’ and short ‘IT’ can indicate streaming or long poll of large content. Sequence 1816 has a long ‘D’ a ‘long ‘RT’, and long ‘IT’ can be a combination of 1814 and 1810.
  • FIG. 19 shows a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.
  • In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.
  • The machine may be a server computer, a client computer, a personal computer (PC), a user device, a tablet PC, a laptop computer, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, an iPhone, an iPad, a Blackberry, a processor, a telephone, a web appliance, a network router, switch or bridge, a console, a hand-held console, a (hand-held) gaming device, a music player, any portable, mobile, hand-held device, tablet, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.
  • While the machine-readable medium or machine-readable storage medium is shown in an exemplary embodiment to be a single medium, the term “machine-readable medium” and “machine-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” and “machine-readable storage medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the presently disclosed technique and innovation.
  • In general, the routines executed to implement the embodiments of the disclosure, may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically comprise one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processing units or processors in a computer, cause the computer to perform operations to execute elements involving the various aspects of the disclosure.
  • Moreover, while embodiments have been described in the context of fully functioning computers and computer systems, those skilled in the art will appreciate that the various embodiments are capable of being distributed as a program product in a variety of forms, and that the disclosure applies equally regardless of the particular type of machine or computer-readable media used to actually effect the distribution.
  • Further examples of machine-readable storage media, machine-readable media, or computer-readable (storage) media include but are not limited to recordable type media such as volatile and non-volatile memory devices, floppy and other removable disks, hard disk drives, optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), among others, and transmission type media such as digital and analog communication links.
  • Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof, means any connection or coupling, either direct or indirect, between two or more elements; the coupling of connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.
  • The above detailed description of embodiments of the disclosure is not intended to be exhaustive or to limit the teachings to the precise form disclosed above. While specific embodiments of, and examples for, the disclosure are described above for illustrative purposes, various equivalent modifications are possible within the scope of the disclosure, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative embodiments may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or subcombinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed in parallel, or may be performed at different times. Further any specific numbers noted herein are only examples: alternative implementations may employ differing values or ranges.
  • The teachings of the disclosure provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various embodiments described above can be combined to provide further embodiments.
  • Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the disclosure can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further embodiments of the disclosure.
  • These and other changes can be made to the disclosure in light of the above Detailed Description. While the above description describes certain embodiments of the disclosure, and describes the best mode contemplated, no matter how detailed the above appears in text, the teachings can be practiced in many ways. Details of the system may vary considerably in its implementation details, while still being encompassed by the subject matter disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the disclosure should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the disclosure with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the disclosure to the specific embodiments disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the disclosure encompasses not only the disclosed embodiments, but also all equivalent ways of practicing or implementing the disclosure under the claims.
  • While certain aspects of the disclosure are presented below in certain claim forms, the inventors contemplate the various aspects of the disclosure in any number of claim forms. For example, while only one aspect of the disclosure is recited as a means-plus-function claim under 35 U.S.C. §112, ¶6, other aspects may likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. (Any claims intended to be treated under 35 U.S.C. §112, ¶6 will begin with the words “means for”.) Accordingly, the applicant reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the disclosure.

Claims (30)

1. A method for detecting a long poll request initiated at a mobile device, the method, comprising:
detecting a first request initiated by a client on the mobile device;
detecting a second request initiated by the client on the mobile device after a first response is received at the mobile device responsive to the first request;
using a response delay time interval relative to an idle time interval to determine whether requests initiated by the client are long poll requests;
wherein, the response delay time interval is between time of the first request and receipt of the response;
wherein, the idle time interval is between time of the response to time of the second request.
2. The method of claim 1, further comprising, detecting a third request, and detecting a trend in response delays based on when responses for the second and third requests are received.
3. The method of claim 2, wherein, the trend indicates an increase in response delays;
wherein, the increase indicates cacheability for the long poll requests and a third response received is stored as cache elements in a local cache.
4. The method of claim 2, wherein, the trend indicates that the response delays are constant or substantially constant; wherein, the trend indicates cacheability for the long poll requests and a third response received is stored as cache elements in a local cache.
5. The method of claim 2, further comprising,
in response to detecting at least one decreasing delay interval from the trend; waiting for a fourth request to be received;
wherein, a fourth response received for the fourth request is cached responsive to detection of an increase in delay interval from the previous delay interval;
the fourth response is cached responsive to detecting repeatability in content with prior responses.
6. The method of claim 5, the fourth response is cached responsive to detecting that it is the same with at least one or two prior responses.
7. The method of claim 4, wherein, substantially constant includes a tolerance within 0-5%, 5-10%, 10-15%, or 15-20% of one of the response delays.
8. The method of claim 1, further comprising,
determining that content received for the application is cacheable, when the received responses indicate repeatability, using the responses received for the requests generated by the application;
storing the content received for the application as cache elements in a local cache of the mobile device responsive to determining cache-ability;
responding to subsequent requests generated by the application using the cache elements stored on the mobile device, to satisfy the subsequent requests without a need to send the outgoing request over a wireless network.
9. The method of claim 8, wherein, the first response is received response to the first request, a second response is received response to the second request, and repeatability is indicated when the first and second responses are the same.
10. The method of claim 2, wherein, the third response is received response to the third request; and repeatability is indicated when the first, second, and third responses are the same or when any two out of the first, second, and third responses are the same.
11. The method of claim 8, further comprising,
timing responses to the subsequent requests using the cached response on the cache of the mobile device to correspond to a manner in which a content server would respond, using the response delay interval time.
12. The method of claim 1, wherein, the requests initiated by the client are determined to be long poll requests if the response delay time interval is greater than the idle time interval.
13. The method of claim 1, wherein, the requests initiated by the client are determined to be long poll requests if the response delay interval time is greater than a threshold value; wherein, the threshold value is determined by a proxy server external to the mobile device, the proxy server being able to communicate over a wireless network with the different mobile devices.
14. The method of claim 13, further comprising, determining the threshold value using response delay interval times for requests generated by other clients.
15. The method of claim 14, wherein, the other clients reside on the same mobile device and the threshold value is determined by a local proxy on the mobile device.
16. The method of claim 15, wherein, the other clients reside on different mobile devices.
17. The method of claim 14, further comprising, determining the threshold value based on network delays.
18. The method of claim 14, further comprising, determining the threshold value based on delays of servers to which the requests are directed.
19. A system for determining whether to cache content received from long poll requests of an application on a mobile device, the system, comprising:
means for, detecting that requests generated by the application are long poll requests using relative timings between a first request initiated by the application, a first response received responsive to the first request, and a second request initiated subsequent to the first request also by the application;
means for determining that content received for the application is cacheable, when the received responses indicate repeatability, using the responses received responsive to the requests generated by the application;
means for, storing the content received for the application as cache elements in a local cache of the mobile device responsive to determining that cache-ability;
means for, responding to subsequent requests generated by the application using the cache elements stored on the mobile device, to satisfy the subsequent requests without a need to send the outgoing request over a wireless network.
20. The system of claim 19, further comprising,
means for, detecting a second response received for the second request;
means for, detecting repeatability in timing of the first request and the first response and of the second request and the second response;
wherein, the content received for the application is stored as cache elements in the local cache of the mobile device if the timing is detected to be repeatable;
21. The system of claim 19, wherein, the first and second requests for use in computing the relative timings are selected for use after a long poll hunting period has settled.
22. The system of claim 19, wherein, the first and second requests for use in computing the relative timings are detected during a long poll hunting period.
23. A machine-readable storage medium having stored thereon instructions which when executed by a processor causes the processor to perform a method for detecting requests for a persistent connection from an application, the method, comprising:
determining relative timings between a first request initiated by the application, a response received responsive to the first request, and a second request initiated subsequent to the first request also by the application;
using the relative timings to determine whether requests generated by the application are long poll requests.
24. The method of claim 23, wherein, the relative timings are determined by:
determining a first request time when the first request is initiated;
determining a response time when the response to the first request is received;
determining a second request time when the second request, subsequent to the first request initiated by the application; wherein, the application is a mobile client residing on a mobile device; wherein, the long poll requests are initiated over a cellular network.
25. The method of claim 23, wherein, the relative timings are used to determine whether the second request is immediately or near-immediately re-requested after the response to the first request is received.
26. The method of claim 23, further comprising, comparing the relative timings to request-response timing characteristics for other applications to determine whether the requests of the application are long poll requests.
27. A system for caching content received for long poll requests initiated at a mobile device, the system, comprising:
a local proxy on the mobile device which determines relative timings between a first request initiated by the application, a response received responsive to the first request, and a second request initiated subsequent to the first request also by the application;
wherein, the relative timings are used to determine whether requests generated by the application are long poll requests;
the local proxy further stores storing the content received for the application as cache elements in a local cache of the mobile device responsive to detection that at least two responses received for the requests from the application are the same;
28. The system of claim 27, wherein, the first and second requests occur after a long poll hunting period or during a long poll hunting period.
29. The system of claim 27, further comprising a proxy server external to the mobile device, the proxy server being able to wirelessly communicate with the local proxy on the mobile device;
wherein, the proxy server monitors a host for updated responses different from those stored in the local cache for corresponding requests initiated by the application on the mobile device;
wherein, the proxy server monitors is able to wirelessly communicate with multiple mobile devices in a wireless network and monitor the host on behalf of multiple mobile devices running the same application;
wherein, the local proxy responds to subsequent requests generated by the application using the cache elements stored on the mobile device, to satisfy the subsequent requests without a need to send the request over a wireless network.
30. The system of claim 27, wherein, the relative timings are used by the proxy server remote from the mobile device to monitor a host to which the requests generated by the application are directed.
US13/274,248 2010-11-01 2011-10-14 Application and network-based long poll request detection and cacheability assessment therefor Expired - Fee Related US8166164B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US13/274,248 US8166164B1 (en) 2010-11-01 2011-10-14 Application and network-based long poll request detection and cacheability assessment therefor

Applications Claiming Priority (15)

Application Number Priority Date Filing Date Title
US40882610P 2010-11-01 2010-11-01
US40884610P 2010-11-01 2010-11-01
US40885810P 2010-11-01 2010-11-01
US40883910P 2010-11-01 2010-11-01
US40885410P 2010-11-01 2010-11-01
US40882010P 2010-11-01 2010-11-01
US40882910P 2010-11-01 2010-11-01
US41602010P 2010-11-22 2010-11-22
US41603310P 2010-11-22 2010-11-22
US201161430828P 2011-01-07 2011-01-07
US201161533007P 2011-09-09 2011-09-09
US201161532857P 2011-09-09 2011-09-09
US201161533021P 2011-09-09 2011-09-09
PCT/US2011/056478 WO2012060997A2 (en) 2010-11-01 2011-10-14 Application and network-based long poll request detection and cacheability assessment therefor
US13/274,248 US8166164B1 (en) 2010-11-01 2011-10-14 Application and network-based long poll request detection and cacheability assessment therefor

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US13/412,338 Continuation US8291076B2 (en) 2010-11-01 2012-03-05 Application and network-based long poll request detection and cacheability assessment therefor
US13/412,338 Continuation-In-Part US8291076B2 (en) 2010-11-01 2012-03-05 Application and network-based long poll request detection and cacheability assessment therefor

Publications (2)

Publication Number Publication Date
US8166164B1 US8166164B1 (en) 2012-04-24
US20120110171A1 true US20120110171A1 (en) 2012-05-03

Family

ID=51982900

Family Applications (3)

Application Number Title Priority Date Filing Date
US13/274,248 Expired - Fee Related US8166164B1 (en) 2010-11-01 2011-10-14 Application and network-based long poll request detection and cacheability assessment therefor
US13/412,338 Expired - Fee Related US8291076B2 (en) 2010-11-01 2012-03-05 Application and network-based long poll request detection and cacheability assessment therefor
US13/651,247 Expired - Fee Related US8966066B2 (en) 2010-11-01 2012-10-12 Application and network-based long poll request detection and cacheability assessment therefor

Family Applications After (2)

Application Number Title Priority Date Filing Date
US13/412,338 Expired - Fee Related US8291076B2 (en) 2010-11-01 2012-03-05 Application and network-based long poll request detection and cacheability assessment therefor
US13/651,247 Expired - Fee Related US8966066B2 (en) 2010-11-01 2012-10-12 Application and network-based long poll request detection and cacheability assessment therefor

Country Status (2)

Country Link
US (3) US8166164B1 (en)
WO (1) WO2012060997A2 (en)

Cited By (62)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120290717A1 (en) * 2011-04-27 2012-11-15 Michael Luna Detecting and preserving state for satisfying application requests in a distributed proxy and cache system
US8316098B2 (en) 2011-04-19 2012-11-20 Seven Networks Inc. Social caching for device resource sharing and management
US8326985B2 (en) 2010-11-01 2012-12-04 Seven Networks, Inc. Distributed management of keep-alive message signaling for mobile network resource conservation and optimization
US8364181B2 (en) 2007-12-10 2013-01-29 Seven Networks, Inc. Electronic-mail filtering for mobile devices
US8412675B2 (en) 2005-08-01 2013-04-02 Seven Networks, Inc. Context aware data presentation
US8417823B2 (en) 2010-11-22 2013-04-09 Seven Network, Inc. Aligning data transfer to optimize connections established for transmission over a wireless network
US8438633B1 (en) 2005-04-21 2013-05-07 Seven Networks, Inc. Flexible real-time inbox access
US8468126B2 (en) 2005-08-01 2013-06-18 Seven Networks, Inc. Publishing data in an information community
US8484314B2 (en) 2010-11-01 2013-07-09 Seven Networks, Inc. Distributed caching in a wireless network of content delivered for a mobile application over a long-held request
US8494510B2 (en) 2008-06-26 2013-07-23 Seven Networks, Inc. Provisioning applications for a mobile device
US8549587B2 (en) 2002-01-08 2013-10-01 Seven Networks, Inc. Secure end-to-end transport through intermediary nodes
US8561086B2 (en) 2005-03-14 2013-10-15 Seven Networks, Inc. System and method for executing commands that are non-native to the native environment of a mobile device
US8693494B2 (en) 2007-06-01 2014-04-08 Seven Networks, Inc. Polling
US8700728B2 (en) 2010-11-01 2014-04-15 Seven Networks, Inc. Cache defeat detection and caching of content addressed by identifiers intended to defeat cache
US8750123B1 (en) 2013-03-11 2014-06-10 Seven Networks, Inc. Mobile device equipped with mobile network congestion recognition to make intelligent decisions regarding connecting to an operator network
US8761756B2 (en) 2005-06-21 2014-06-24 Seven Networks International Oy Maintaining an IP connection in a mobile network
US8774844B2 (en) 2007-06-01 2014-07-08 Seven Networks, Inc. Integrated messaging
US8775631B2 (en) 2012-07-13 2014-07-08 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
US8787947B2 (en) 2008-06-18 2014-07-22 Seven Networks, Inc. Application discovery on mobile devices
US8799410B2 (en) 2008-01-28 2014-08-05 Seven Networks, Inc. System and method of a relay server for managing communications and notification between a mobile device and a web access server
US8805334B2 (en) 2004-11-22 2014-08-12 Seven Networks, Inc. Maintaining mobile terminal information for secure communications
US8812695B2 (en) 2012-04-09 2014-08-19 Seven Networks, Inc. Method and system for management of a virtual network connection without heartbeat messages
US8832228B2 (en) 2011-04-27 2014-09-09 Seven Networks, Inc. System and method for making requests on behalf of a mobile device based on atomic processes for mobile network traffic relief
US8838783B2 (en) 2010-07-26 2014-09-16 Seven Networks, Inc. Distributed caching for resource and mobile network traffic management
US8843153B2 (en) 2010-11-01 2014-09-23 Seven Networks, Inc. Mobile traffic categorization and policy for network use optimization while preserving user experience
US8849902B2 (en) 2008-01-25 2014-09-30 Seven Networks, Inc. System for providing policy based content service in a mobile network
US8861354B2 (en) 2011-12-14 2014-10-14 Seven Networks, Inc. Hierarchies and categories for management and deployment of policies for distributed wireless traffic optimization
US8868753B2 (en) 2011-12-06 2014-10-21 Seven Networks, Inc. System of redundantly clustered machines to provide failover mechanisms for mobile traffic management and network resource conservation
US8874761B2 (en) 2013-01-25 2014-10-28 Seven Networks, Inc. Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols
US8873411B2 (en) 2004-12-03 2014-10-28 Seven Networks, Inc. Provisioning of e-mail settings for a mobile terminal
US8886176B2 (en) 2010-07-26 2014-11-11 Seven Networks, Inc. Mobile application traffic optimization
US8903954B2 (en) 2010-11-22 2014-12-02 Seven Networks, Inc. Optimization of resource polling intervals to satisfy mobile device requests
US8909202B2 (en) 2012-01-05 2014-12-09 Seven Networks, Inc. Detection and management of user interactions with foreground applications on a mobile device in distributed caching
US8909759B2 (en) 2008-10-10 2014-12-09 Seven Networks, Inc. Bandwidth measurement
US20140365576A1 (en) * 2012-01-26 2014-12-11 Ofer Eliassaf Identifying a push communication pattern
US8918503B2 (en) 2011-12-06 2014-12-23 Seven Networks, Inc. Optimization of mobile traffic directed to private networks and operator configurability thereof
USRE45348E1 (en) 2004-10-20 2015-01-20 Seven Networks, Inc. Method and apparatus for intercepting events in a communication system
US8966066B2 (en) 2010-11-01 2015-02-24 Seven Networks, Inc. Application and network-based long poll request detection and cacheability assessment therefor
US8984581B2 (en) 2011-07-27 2015-03-17 Seven Networks, Inc. Monitoring mobile application activities for malicious traffic on a mobile device
US9002828B2 (en) 2007-12-13 2015-04-07 Seven Networks, Inc. Predictive content delivery
US9009250B2 (en) 2011-12-07 2015-04-14 Seven Networks, Inc. Flexible and dynamic integration schemas of a traffic management system with various network operators for network traffic alleviation
US9021048B2 (en) 2010-11-01 2015-04-28 Seven Networks, Inc. Caching adapted for mobile application behavior and network conditions
US9021021B2 (en) 2011-12-14 2015-04-28 Seven Networks, Inc. Mobile network reporting and usage analytics system and method aggregated using a distributed traffic optimization system
US9043433B2 (en) 2010-07-26 2015-05-26 Seven Networks, Inc. Mobile network traffic coordination across multiple applications
US9055102B2 (en) 2006-02-27 2015-06-09 Seven Networks, Inc. Location-based operations and messaging
US9060032B2 (en) 2010-11-01 2015-06-16 Seven Networks, Inc. Selective data compression by a distributed traffic management system to reduce mobile data traffic and signaling traffic
US9065765B2 (en) 2013-07-22 2015-06-23 Seven Networks, Inc. Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network
US9077630B2 (en) 2010-07-26 2015-07-07 Seven Networks, Inc. Distributed implementation of dynamic wireless traffic policy
US9161258B2 (en) 2012-10-24 2015-10-13 Seven Networks, Llc Optimized and selective management of policy deployment to mobile clients in a congested network to prevent further aggravation of network congestion
US9173128B2 (en) 2011-12-07 2015-10-27 Seven Networks, Llc Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol
US9203864B2 (en) 2012-02-02 2015-12-01 Seven Networks, Llc Dynamic categorization of applications for network access in a mobile network
US9241314B2 (en) 2013-01-23 2016-01-19 Seven Networks, Llc Mobile device with application or context aware fast dormancy
US9251193B2 (en) 2003-01-08 2016-02-02 Seven Networks, Llc Extending user relationships
US9307493B2 (en) 2012-12-20 2016-04-05 Seven Networks, Llc Systems and methods for application management of mobile device radio state promotion and demotion
US9326189B2 (en) 2012-02-03 2016-04-26 Seven Networks, Llc User as an end point for profiling and optimizing the delivery of content and data in a wireless network
US9325662B2 (en) 2011-01-07 2016-04-26 Seven Networks, Llc System and method for reduction of mobile network traffic used for domain name system (DNS) queries
US9330196B2 (en) 2010-11-01 2016-05-03 Seven Networks, Llc Wireless traffic management system cache optimization using http headers
US20170034211A1 (en) * 2015-07-27 2017-02-02 Swisscom Ag Systems and methods for identifying phishing websites
US20170289363A1 (en) * 2011-11-10 2017-10-05 Microsoft Technology Licensing, Llc Application resource usage information
US9832095B2 (en) 2011-12-14 2017-11-28 Seven Networks, Llc Operation modes for mobile traffic optimization and concurrent management of optimized and non-optimized traffic
US10263899B2 (en) 2012-04-10 2019-04-16 Seven Networks, Llc 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
US10735307B1 (en) * 2019-01-10 2020-08-04 Ebay Inc. Network latency measurement and analysis system

Families Citing this family (65)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8107921B2 (en) 2008-01-11 2012-01-31 Seven Networks, Inc. Mobile virtual network operator
US8521078B2 (en) * 2008-03-21 2013-08-27 Qualcomm Incorporated Common interface protocol for sending FR-RDS messages in wireless communication systems
US9367680B2 (en) 2008-10-21 2016-06-14 Lookout, Inc. System and method for mobile communication device application advisement
US9235704B2 (en) 2008-10-21 2016-01-12 Lookout, Inc. System and method for a scanning API
US8060936B2 (en) 2008-10-21 2011-11-15 Lookout, Inc. Security status and information display system
US9043919B2 (en) 2008-10-21 2015-05-26 Lookout, Inc. Crawling multiple markets and correlating
US8533844B2 (en) 2008-10-21 2013-09-10 Lookout, Inc. System and method for security data collection and analysis
US8984628B2 (en) 2008-10-21 2015-03-17 Lookout, Inc. System and method for adverse mobile application identification
US8087067B2 (en) 2008-10-21 2011-12-27 Lookout, Inc. Secure mobile platform system
US8347386B2 (en) 2008-10-21 2013-01-01 Lookout, Inc. System and method for server-coupled malware prevention
US9781148B2 (en) 2008-10-21 2017-10-03 Lookout, Inc. Methods and systems for sharing risk responses between collections of mobile communications devices
US8051480B2 (en) 2008-10-21 2011-11-01 Lookout, Inc. System and method for monitoring and analyzing multiple interfaces and multiple protocols
US8108933B2 (en) 2008-10-21 2012-01-31 Lookout, Inc. System and method for attack and malware prevention
US8855601B2 (en) 2009-02-17 2014-10-07 Lookout, Inc. System and method for remotely-initiated audio communication
US8467768B2 (en) 2009-02-17 2013-06-18 Lookout, Inc. System and method for remotely securing or recovering a mobile device
US9042876B2 (en) 2009-02-17 2015-05-26 Lookout, Inc. System and method for uploading location information based on device movement
US8538815B2 (en) 2009-02-17 2013-09-17 Lookout, Inc. System and method for mobile device replacement
US9955352B2 (en) 2009-02-17 2018-04-24 Lookout, Inc. Methods and systems for addressing mobile communications devices that are lost or stolen but not yet reported as such
US8275859B2 (en) * 2009-03-31 2012-09-25 International Business Machines Corporation Selective partial updates of web content
US8223693B2 (en) * 2009-06-23 2012-07-17 Mediatek Inc. PTA method and apparatus utilizing the same
US8863167B2 (en) 2009-10-29 2014-10-14 Motorola Mobility Llc System providing sponsored content
US8335596B2 (en) * 2010-07-16 2012-12-18 Verizon Patent And Licensing Inc. Remote energy management using persistent smart grid network context
US10051073B1 (en) * 2010-12-31 2018-08-14 EMC IP Holding Company LLC Cloud information services
CN102724103B (en) * 2011-03-30 2015-04-01 国际商业机器公司 Proxy server, hierarchical network system and distributed workload management method
US8738765B2 (en) * 2011-06-14 2014-05-27 Lookout, Inc. Mobile device DNS optimization
US8788881B2 (en) 2011-08-17 2014-07-22 Lookout, Inc. System and method for mobile device push communications
US10613982B1 (en) 2012-01-06 2020-04-07 Seagate Technology Llc File-aware caching driver
US9268692B1 (en) 2012-04-05 2016-02-23 Seagate Technology Llc User selectable caching
US9542324B1 (en) 2012-04-05 2017-01-10 Seagate Technology Llc File associated pinning
US9407443B2 (en) 2012-06-05 2016-08-02 Lookout, Inc. Component analysis of software applications on computing devices
US9589129B2 (en) 2012-06-05 2017-03-07 Lookout, Inc. Determining source of side-loaded software
US8655307B1 (en) 2012-10-26 2014-02-18 Lookout, Inc. System and method for developing, updating, and using user device behavioral context models to modify user, device, and application state, settings and behavior for enhanced user security
EP3364705A1 (en) * 2012-12-03 2018-08-22 Telefonaktiebolaget LM Ericsson (publ) Method and data transmitting node for controlling a polling procedure
US9654353B2 (en) * 2012-12-13 2017-05-16 Level 3 Communications, Llc Framework supporting content delivery with rendezvous services network
US9208215B2 (en) 2012-12-27 2015-12-08 Lookout, Inc. User classification based on data gathered from a computing device
US9374369B2 (en) 2012-12-28 2016-06-21 Lookout, Inc. Multi-factor authentication and comprehensive login system for client-server networks
US8855599B2 (en) 2012-12-31 2014-10-07 Lookout, Inc. Method and apparatus for auxiliary communications with mobile communications device
US10977425B1 (en) * 2013-03-13 2021-04-13 Sprint Communications Company L.P. Dynamic resource refresh
US20140274185A1 (en) * 2013-03-14 2014-09-18 Aliphcom Intelligence device connection for wireless media ecosystem
US10699273B2 (en) 2013-03-14 2020-06-30 Lookout, Inc. System and method for authorizing payment transaction based on device locations
US9852416B2 (en) 2013-03-14 2017-12-26 Lookout, Inc. System and method for authorizing a payment transaction
US9307412B2 (en) 2013-04-24 2016-04-05 Lookout, Inc. Method and system for evaluating security for an interactive service operation by a mobile device
US9819552B2 (en) * 2013-07-02 2017-11-14 Seven Networks, Llc Modeling network signaling in a mobile network
US9426249B2 (en) * 2013-08-05 2016-08-23 Salesforce.Com, Inc. Providing an improved web user interface framework for building web applications
US9524157B2 (en) 2013-08-06 2016-12-20 Salesforce.Com, Inc. Providing an improved web user interface framework for building web applications
US9642008B2 (en) 2013-10-25 2017-05-02 Lookout, Inc. System and method for creating and assigning a policy for a mobile communications device based on personal data
US10122747B2 (en) 2013-12-06 2018-11-06 Lookout, Inc. Response generation after distributed monitoring and evaluation of multiple devices
US9753796B2 (en) 2013-12-06 2017-09-05 Lookout, Inc. Distributed monitoring, evaluation, and response for multiple devices
US9473799B1 (en) * 2013-12-17 2016-10-18 Amazon Technologies, Inc. Resource data query processing
US9397904B2 (en) * 2013-12-30 2016-07-19 International Business Machines Corporation System for identifying, monitoring and ranking incidents from social media
CN103888346A (en) 2014-03-24 2014-06-25 北京智谷睿拓技术服务有限公司 Information sending method and information sending device
CN103888916A (en) * 2014-03-24 2014-06-25 北京智谷睿拓技术服务有限公司 Information sending method and information sending device
WO2016128885A1 (en) * 2015-02-09 2016-08-18 Laurus Labs Private Limited A process for preparation of cobicistat
WO2016178816A1 (en) 2015-05-01 2016-11-10 Lookout, Inc. Determining source of side-loaded software
US10133682B2 (en) * 2015-11-17 2018-11-20 Airwatch Llc Managing grouped student devices with timed locks
WO2017210198A1 (en) 2016-05-31 2017-12-07 Lookout, Inc. Methods and systems for detecting and preventing network connection compromise
CN107067244B (en) 2016-11-03 2020-09-29 阿里巴巴集团控股有限公司 Service implementation method, payment method, service implementation device and payment server
WO2018160828A1 (en) 2017-03-02 2018-09-07 Carrier Corporation A wireless communication system and method to reduce energy consumption of wireless devices
US10218697B2 (en) 2017-06-09 2019-02-26 Lookout, Inc. Use of device risk evaluation to manage access to services
US11212338B1 (en) 2018-01-23 2021-12-28 Amazon Technologies, Inc. Managed scaling of a processing service
CN108446172B (en) * 2018-02-26 2021-03-23 平安普惠企业管理有限公司 Data calling method and device, computer equipment and storage medium
CN108600372B (en) * 2018-04-26 2021-01-05 国网山东省电力公司泗水县供电公司 Information interaction system based on multiple power transmission equipment inspection devices and control terminal
WO2020041324A1 (en) 2018-08-20 2020-02-27 Shure Acquisition Holdings, Inc. Systems and methods for large scale ota firmware update
US11184414B2 (en) * 2018-12-07 2021-11-23 Slack Technologies, Llc Reservation management for client-initiated polling requests in a communication system
US10938699B1 (en) * 2019-10-01 2021-03-02 Cisco Technology, Inc. Systems and methods for monitoring and addressing network performance issues

Family Cites Families (1108)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US222458A (en) 1879-12-09 Improvement in automatic telephone-exchanges
US447918A (en) 1891-03-10 Automatic telephone-exchange
US1020881A (en) 1911-07-17 1912-03-19 William Brandon Berry-picker.
US4276597A (en) 1974-01-17 1981-06-30 Volt Delta Resources, Inc. Method and apparatus for information storage and retrieval
US4200770A (en) 1977-09-06 1980-04-29 Stanford University Cryptographic apparatus and method
US4255796A (en) 1978-02-14 1981-03-10 Bell Telephone Laboratories, Incorporated Associative information retrieval continuously guided by search status feedback
US4531020A (en) 1982-07-23 1985-07-23 Oak Industries Inc. Multi-layer encryption system for the broadcast of encrypted information
US4807182A (en) 1986-03-12 1989-02-21 Advanced Software, Inc. Apparatus and method for comparing data groups
US4831582A (en) 1986-11-07 1989-05-16 Allen-Bradley Company, Inc. Database access machine for factory automation network
US4897781A (en) 1987-02-13 1990-01-30 International Business Machines Corporation System and method for using cached data at a local node after re-opening a file at a remote node in a distributed networking environment
US5008853A (en) 1987-12-02 1991-04-16 Xerox Corporation Representation of collaborative multi-user activities relative to shared structured data objects in a networked workstation environment
US5220657A (en) 1987-12-02 1993-06-15 Xerox Corporation Updating local copy of shared data in a collaborative system
US4875159A (en) 1987-12-22 1989-10-17 Amdahl Corporation Version management system using plural control fields for synchronizing two versions of files in a multiprocessor system
US4972457A (en) 1989-01-19 1990-11-20 Spectrum Information Technologies, Inc. Portable hybrid communication system and methods
US7537167B1 (en) 1993-08-31 2009-05-26 Broadcom Corporation Modular, portable data processing terminal for use in a radio frequency communication network
JP2609473B2 (en) 1989-10-23 1997-05-14 シャープ株式会社 Communication device
US5263157A (en) 1990-02-15 1993-11-16 International Business Machines Corporation Method and system for providing user access control within a distributed data processing system by the exchange of access control profiles
JP3111468B2 (en) 1990-10-17 2000-11-20 富士通株式会社 Communication concealment method
US5438611A (en) 1991-05-20 1995-08-01 Ntp Incorporated Electronic mail system with RF communications to mobile processors originating from outside of the electronic mail system and method of operation thereof
US5479472A (en) 1991-05-20 1995-12-26 Ntp Incorporated System for interconnecting electronic mail systems by RF communications and method of operation thereof
US5436960A (en) 1991-05-20 1995-07-25 Campana, Jr.; Thomas J. Electronic mail system with RF communications to mobile processors and method of operation thereof
US5283856A (en) 1991-10-04 1994-02-01 Beyond, Inc. Event-driven rule-based messaging system
WO1993009501A1 (en) 1991-11-01 1993-05-13 Yeh Keming W Portable device having data storage capability for transferring data between a portable computer and a desktop computer
US5519606A (en) 1992-01-21 1996-05-21 Starfish Software, Inc. System and methods for appointment reconciliation
US5357431A (en) 1992-01-27 1994-10-18 Fujitsu Limited Character string retrieval system using index and unit for making the index
WO1993020641A1 (en) 1992-03-27 1993-10-14 Bell Atlantic Network Services, Inc. Improved data transmission public switched telephone network
US5392390A (en) 1992-04-10 1995-02-21 Intellilink Corp. Method for mapping, translating, and dynamically reconciling data between disparate computer platforms
US5689654A (en) 1992-06-29 1997-11-18 Elonex F.P. Holdings, Ltd. Digital assistant system including a host computer with a docking bay for the digital assistant wherein a heat sink is moved into contact with a docked digital assistant for cooling the digital assistant
GB9213821D0 (en) 1992-06-30 1992-08-12 Inmos Ltd Content addressable memory
ES2198407T3 (en) 1992-09-30 2004-02-01 Motorola, Inc. SYSTEM OF DISTRIBUTION OF EMAIL MESSAGES.
US5983179A (en) 1992-11-13 1999-11-09 Dragon Systems, Inc. Speech recognition system which turns its voice response on for confirmation when it has been turned off without confirmation
US5666530A (en) 1992-12-02 1997-09-09 Compaq Computer Corporation System for automatic synchronization of common file between portable computer and host computer via communication channel selected from a plurality of usable channels there between
US5581749A (en) 1992-12-21 1996-12-03 Thedow Chemical Company System and method for maintaining codes among distributed databases using a global database
US5384892A (en) 1992-12-31 1995-01-24 Apple Computer, Inc. Dynamic language model for speech recognition
JPH06216935A (en) 1993-01-18 1994-08-05 Fujitsu Ltd Electronic mail system
US5386564A (en) 1993-02-24 1995-01-31 Hewlett-Packard Company Conversion of data and objects across classes in an object management system
US5799318A (en) 1993-04-13 1998-08-25 Firstfloor Software Method and apparatus for collecting and displaying information from diverse computer resources
US7924783B1 (en) 1994-05-06 2011-04-12 Broadcom Corporation Hierarchical communications system
US5696903A (en) 1993-05-11 1997-12-09 Norand Corporation Hierarchical communications system using microlink, data rate switching, frequency hopping and vehicular local area networking
JPH06324928A (en) 1993-05-14 1994-11-25 Mitsubishi Electric Corp Log generating device, device for arbitrating versions different in file and device for arbitrating version different in computer file being at different places
JPH0828754B2 (en) 1993-06-30 1996-03-21 日本電気株式会社 Frame synchronization method
US5729704A (en) 1993-07-21 1998-03-17 Xerox Corporation User-directed method for operating on an object-based model data structure through a second contextual image
EP0647909B1 (en) 1993-10-08 2003-04-16 International Business Machines Corporation Information catalog system with object-dependent functionality
US5493692A (en) 1993-12-03 1996-02-20 Xerox Corporation Selective delivery of electronic messages in a multiple computer system based on context and environment of a user
US5555376A (en) 1993-12-03 1996-09-10 Xerox Corporation Method for granting a user request having locational and contextual attributes consistent with user policies for devices having locational attributes consistent with the user request
US5559800A (en) 1994-01-19 1996-09-24 Research In Motion Limited Remote control of gateway functions in a wireless data communication network
JPH07271699A (en) 1994-03-31 1995-10-20 Canon Inc Peripheral processor and information processor connected through network, and control method in peripheral processor and control method for peripheral processor
US5913032A (en) 1994-04-04 1999-06-15 Inprise Corporation System and methods for automatically distributing a particular shared data object through electronic mail
US5704029A (en) 1994-05-23 1997-12-30 Wright Strategies, Inc. System and method for completing an electronic form
US5434994A (en) 1994-05-23 1995-07-18 International Business Machines Corporation System and method for maintaining replicated data coherency in a data processing system
US5694546A (en) 1994-05-31 1997-12-02 Reisman; Richard R. System for automatic unattended electronic information transport between a server and a client by a vendor provided transport software with a manifest list
US5787430A (en) 1994-06-30 1998-07-28 International Business Machines Corporation Variable length data sequence backtracking a trie structure
US5742905A (en) 1994-09-19 1998-04-21 Bell Communications Research, Inc. Personal communications internetworking
US5802312A (en) 1994-09-27 1998-09-01 Research In Motion Limited System for transmitting data files between computers in a wireless environment utilizing a file transfer agent executing on host system
US5652884A (en) 1994-11-14 1997-07-29 Object Technology Licensing Corp. Method and apparatus for dynamic update of an existing object in an object editor
US5623601A (en) 1994-11-18 1997-04-22 Milkway Networks Corporation Apparatus and method for providing a secure gateway for communication and data exchanges between networks
US5715403A (en) 1994-11-23 1998-02-03 Xerox Corporation System for controlling the distribution and use of digital works having attached usage rights where the usage rights are defined by a usage rights grammar
US5613012A (en) 1994-11-28 1997-03-18 Smarttouch, Llc. Tokenless identification system for authorization of electronic transactions and electronic transmissions
US5758257A (en) 1994-11-29 1998-05-26 Herz; Frederick System and method for scheduling broadcast of and access to video programs and other data using customer profiles
US5619648A (en) 1994-11-30 1997-04-08 Lucent Technologies Inc. Message filtering techniques
US5758322A (en) 1994-12-09 1998-05-26 International Voice Register, Inc. Method and apparatus for conducting point-of-sale transactions using voice recognition
US5627658A (en) 1994-12-14 1997-05-06 Xerox Corporation Automatic networked facsimile queuing system
US5664207A (en) 1994-12-16 1997-09-02 Xcellenet, Inc. Systems and methods for automatically sharing information among remote/mobile nodes
US5572571A (en) 1994-12-30 1996-11-05 Sony Corporation Programmable cellular telephone and system
US5684990A (en) 1995-01-11 1997-11-04 Puma Technology, Inc. Synchronization of disparate databases
CA2167790A1 (en) 1995-01-23 1996-07-24 Donald S. Maier Relational database system and method with high data availability during table data restructuring
US5729735A (en) 1995-02-08 1998-03-17 Meyering; Samuel C. Remote database file synchronizer
US5706211A (en) 1995-03-02 1998-01-06 Motorola, Inc. Message communications system
US5822324A (en) 1995-03-16 1998-10-13 Bell Atlantic Network Services, Inc. Simulcasting digital video programs for broadcast and interactive services
US5604788A (en) 1995-03-16 1997-02-18 Motorola, Inc. Wireless messaging system with electronic mail replication
US5651010A (en) 1995-03-16 1997-07-22 Bell Atlantic Network Services, Inc. Simultaneous overlapping broadcasting of digital programs
US5819284A (en) 1995-03-24 1998-10-06 At&T Corp. Personalized real time information display as a portion of a screen saver
JPH08297528A (en) 1995-04-25 1996-11-12 Canon Inc Data communication device
US5758354A (en) 1995-04-28 1998-05-26 Intel Corporation Application independent e-mail synchronization
US5793413A (en) 1995-05-01 1998-08-11 Bell Atlantic Network Services, Inc. Wireless video distribution
CA2220345C (en) 1995-05-08 2001-09-04 Compuserve Incorporated System for electronic messaging via wireless devices
US5682524A (en) 1995-05-26 1997-10-28 Starfish Software, Inc. Databank system with methods for efficiently storing non-uniform data records
US5835061A (en) 1995-06-06 1998-11-10 Wayport, Inc. Method and apparatus for geographic-based communications service
US5752186A (en) 1995-06-07 1998-05-12 Jeman Technologies, Inc. Access free wireless telephony fulfillment service system
US5680542A (en) 1995-06-07 1997-10-21 Motorola, Inc. Method and apparatus for synchronizing data in a host memory with data in target MCU memory
US5701469A (en) 1995-06-07 1997-12-23 Microsoft Corporation Method and system for generating accurate search results using a content-index
US5721908A (en) 1995-06-07 1998-02-24 International Business Machines Corporation Computer network for WWW server data access over internet
US5710918A (en) 1995-06-07 1998-01-20 International Business Machines Corporation Method for distributed task fulfillment of web browser requests
US5752246A (en) 1995-06-07 1998-05-12 International Business Machines Corporation Service agent for fulfilling requests of a web browser
US5826269A (en) 1995-06-21 1998-10-20 Microsoft Corporation Electronic mail interface for a network server
US5706507A (en) 1995-07-05 1998-01-06 International Business Machines Corporation System and method for controlling access to data located on a content server
US6016520A (en) 1995-07-14 2000-01-18 Microsoft Corporation Method of viewing at a client viewing station a multiple media title stored at a server and containing a plurality of topics utilizing anticipatory caching
US5818437A (en) 1995-07-26 1998-10-06 Tegic Communications, Inc. Reduced keyboard disambiguating computer
US7051086B2 (en) 1995-07-27 2006-05-23 Digimarc Corporation Method of linking on-line data to printed documents
US5745360A (en) 1995-08-14 1998-04-28 International Business Machines Corp. Dynamic hypertext link converter system and process
US5634053A (en) 1995-08-29 1997-05-27 Hughes Aircraft Company Federated information management (FIM) system and method for providing data site filtering and translation for heterogeneous databases
US5647002A (en) 1995-09-01 1997-07-08 Lucent Technologies Inc. Synchronization of mailboxes of different types
US5630081A (en) 1995-09-07 1997-05-13 Puma Technology, Inc. Connection resource manager displaying link-status information using a traffic light iconic representation
US5721914A (en) 1995-09-14 1998-02-24 Mci Corporation System and method for hierarchical data distribution
US6185184B1 (en) 1995-09-25 2001-02-06 Netspeak Corporation Directory server for providing dynamically assigned network protocol addresses
US5778361A (en) 1995-09-29 1998-07-07 Microsoft Corporation Method and system for fast indexing and searching of text in compound-word languages
US5757916A (en) 1995-10-06 1998-05-26 International Series Research, Inc. Method and apparatus for authenticating the location of remote users of networked computing systems
US5758150A (en) 1995-10-06 1998-05-26 Tele-Communications, Inc. System and method for database synchronization
US5884323A (en) 1995-10-13 1999-03-16 3Com Corporation Extendible method and apparatus for synchronizing files on two different computer systems
US5727202A (en) 1995-10-18 1998-03-10 Palm Computing, Inc. Method and apparatus for synchronizing information on two different computer systems
US5572643A (en) 1995-10-19 1996-11-05 Judson; David H. Web browser with dynamic display of information objects during linking
US5713019A (en) 1995-10-26 1998-01-27 Keaten; Timothy M. Iconic access to remote electronic monochrome raster data format document repository
JP3459149B2 (en) 1995-11-06 2003-10-20 シャープ株式会社 Email transfer system
US5764639A (en) 1995-11-15 1998-06-09 Staples; Leven E. System and method for providing a remote user with a virtual presence to an office
US5920821A (en) 1995-12-04 1999-07-06 Bell Atlantic Network Services, Inc. Use of cellular digital packet data (CDPD) communications to convey system identification list data to roaming cellular subscriber stations
US5809415A (en) 1995-12-11 1998-09-15 Unwired Planet, Inc. Method and architecture for an interactive two-way data communication network
US5794210A (en) 1995-12-11 1998-08-11 Cybergold, Inc. Attention brokerage
US5831664A (en) 1995-12-15 1998-11-03 Mediaone Group, Inc. Method and system for synchronizing data between at least one mobile interface device and an interactive terminal
US5802454A (en) 1995-12-15 1998-09-01 Teletrac, Inc. Remotely distributed location and messaging system
US5832483A (en) 1995-12-15 1998-11-03 Novell, Inc. Distributed control interface for managing the interoperability and concurrency of agents and resources in a real-time environment
US6101531A (en) 1995-12-19 2000-08-08 Motorola, Inc. System for communicating user-selected criteria filter prepared at wireless client to communication server for filtering data transferred from host to said wireless client
US5781901A (en) 1995-12-21 1998-07-14 Intel Corporation Transmitting electronic mail attachment over a network using a e-mail page
US5903723A (en) 1995-12-21 1999-05-11 Intel Corporation Method and apparatus for transmitting electronic mail attachments with attachment references
US5765171A (en) 1995-12-29 1998-06-09 Lucent Technologies Inc. Maintaining consistency of database replicas
US5978933A (en) 1996-01-11 1999-11-02 Hewlett-Packard Company Generic fault tolerant platform
US5787441A (en) 1996-01-11 1998-07-28 International Business Machines Corporation Method of replicating data at a field level
US5781614A (en) 1996-01-19 1998-07-14 Lucent Technologies Inc. Message retrieval via alternative access
US5822523A (en) 1996-02-01 1998-10-13 Mpath Interactive, Inc. Server-group messaging system for interactive applications
US6198696B1 (en) 1999-06-16 2001-03-06 Siemens Information And Communication Networks, Inc. Device and method for tracking time zone changes in communications devices
US5841432A (en) 1996-02-09 1998-11-24 Carmel; Sharon Method and system of building and transmitting a data file for real time play of multimedia, particularly animation, and a data file for real time play of multimedia applications
US6047327A (en) 1996-02-16 2000-04-04 Intel Corporation System for distributing electronic information to a targeted group of users
US6513069B1 (en) 1996-03-08 2003-01-28 Actv, Inc. Enhanced video programming system and method for providing a distributed community network
US5806074A (en) 1996-03-19 1998-09-08 Oracle Corporation Configurable conflict resolution in a computer implemented distributed database
US5706502A (en) 1996-03-25 1998-01-06 Sun Microsystems, Inc. Internet-enabled portfolio manager system and method
US5937161A (en) 1996-04-12 1999-08-10 Usa.Net, Inc. Electronic message forwarding system
US6049671A (en) 1996-04-18 2000-04-11 Microsoft Corporation Method for identifying and obtaining computer software from a network computer
US5809242A (en) 1996-04-19 1998-09-15 Juno Online Services, L.P. Electronic mail system for displaying advertisement at local computer received from remote system while the local computer is off-line the remote system
US5751813A (en) 1996-04-29 1998-05-12 Motorola, Inc. Use of an encryption server for encrypting messages
US5790974A (en) 1996-04-29 1998-08-04 Sun Microsystems, Inc. Portable calendaring device having perceptual agent managing calendar entries
US5838973A (en) 1996-05-03 1998-11-17 Andersen Consulting Llp System and method for interactively transforming a system or process into a visual representation
US5898780A (en) 1996-05-21 1999-04-27 Gric Communications, Inc. Method and apparatus for authorizing remote internet access
US5802518A (en) 1996-06-04 1998-09-01 Multex Systems, Inc. Information delivery system and method
US5781906A (en) 1996-06-06 1998-07-14 International Business Machines Corporation System and method for construction of a data structure for indexing multidimensional objects
US5857201A (en) 1996-06-18 1999-01-05 Wright Strategies, Inc. Enterprise connectivity to handheld devices
US5835722A (en) 1996-06-27 1998-11-10 Logon Data Corporation System to control content and prohibit certain interactive attempts by a person using a personal computer
US6035104A (en) 1996-06-28 2000-03-07 Data Link Systems Corp. Method and apparatus for managing electronic documents by alerting a subscriber at a destination other than the primary destination
JP3224745B2 (en) 1996-07-09 2001-11-05 株式会社日立製作所 High reliability network system and server switching method
EP0912954B8 (en) 1996-07-22 2006-06-14 Cyva Research Corporation Personal information security and exchange tool
US5862223A (en) 1996-07-24 1999-01-19 Walker Asset Management Limited Partnership Method and apparatus for a cryptographically-assisted commercial network system designed to facilitate and support expert-based commerce
US5940813A (en) 1996-07-26 1999-08-17 Citibank, N.A. Process facility management matrix and system and method for performing batch, processing in an on-line environment
US5802524A (en) 1996-07-29 1998-09-01 International Business Machines Corporation Method and product for integrating an object-based search engine with a parametrically archived database
EP0822502A1 (en) 1996-07-31 1998-02-04 BRITISH TELECOMMUNICATIONS public limited company Data access system
US6543695B1 (en) 1996-08-02 2003-04-08 Symbol Technologies, Inc. Housing for hand held scanner
US5974238A (en) 1996-08-07 1999-10-26 Compaq Computer Corporation Automatic data synchronization between a handheld and a host computer using pseudo cache including tags and logical data elements
US5758355A (en) 1996-08-07 1998-05-26 Aurum Software, Inc. Synchronization of server database with client database using distribution tables
US5832500A (en) 1996-08-09 1998-11-03 Digital Equipment Corporation Method for searching an index
US5852820A (en) 1996-08-09 1998-12-22 Digital Equipment Corporation Method for optimizing entries for searching an index
US6016478A (en) 1996-08-13 2000-01-18 Starfish Software, Inc. Scheduling system with methods for peer-to-peer scheduling of remote users
US5867817A (en) 1996-08-19 1999-02-02 Virtual Vision, Inc. Speech recognition manager
US5822747A (en) 1996-08-23 1998-10-13 Tandem Computers, Inc. System and method for optimizing database queries
US5898917A (en) 1996-08-27 1999-04-27 Ag Communication Systems Corporation System for providing enhanced services in cellular radio telecommunication systems using #CCSC based triggers
FI111428B (en) 1996-08-29 2003-07-15 Nokia Corp Gallup that utilizes a wireless data communication connection
US5838768A (en) 1996-10-03 1998-11-17 Telefonaktiebolaget L M Ericsson System and method for controlled media conversion in an intelligent network
US5838252A (en) 1996-09-09 1998-11-17 Datalink Systems, Inc. Interactive two-way pager systems
US5852775A (en) 1996-09-12 1998-12-22 Earthweb, Inc. Cellular telephone advertising system
US5892909A (en) 1996-09-27 1999-04-06 Diffusion, Inc. Intranet-based system with methods for co-active delivery of information to multiple users
US6181935B1 (en) 1996-09-27 2001-01-30 Software.Com, Inc. Mobility extended telephone application programming interface and method of use
US7359720B2 (en) 1996-09-27 2008-04-15 Openwave Systems Inc. Mobility extended telephone application programming interface and method of use
US6018343A (en) 1996-09-27 2000-01-25 Timecruiser Computing Corp. Web calendar architecture and uses thereof
US5978837A (en) 1996-09-27 1999-11-02 At&T Corp. Intelligent pager for remotely managing E-Mail messages
TW347498B (en) 1996-09-30 1998-12-11 Casio Computer Co Ltd Information supply system
US5870759A (en) 1996-10-09 1999-02-09 Oracle Corporation System for synchronizing data between computers using a before-image of data
US5790790A (en) 1996-10-24 1998-08-04 Tumbleweed Software Corporation Electronic document delivery system in which notification of said electronic document is sent to a recipient thereof
FI113224B (en) 1996-11-11 2004-03-15 Nokia Corp Implementation of invoicing in a data communication system
US6044381A (en) 1997-09-11 2000-03-28 Puma Technology, Inc. Using distributed history files in synchronizing databases
US6212529B1 (en) 1996-11-13 2001-04-03 Puma Technology, Inc. Synchronization of databases using filters
US6405218B1 (en) 1996-11-13 2002-06-11 Pumatech, Inc. Synchronizing databases
US5943676A (en) 1996-11-13 1999-08-24 Puma Technology, Inc. Synchronization of recurring records in incompatible databases
US6141664A (en) 1996-11-13 2000-10-31 Puma Technology, Inc. Synchronization of databases with date range
FI104139B1 (en) 1996-11-27 1999-11-15 Nokia Telecommunications Oy Use two SIM cards with the same MSISDN number
US6202085B1 (en) 1996-12-06 2001-03-13 Microsoft Corportion System and method for incremental change synchronization between multiple copies of data
US6131116A (en) 1996-12-13 2000-10-10 Visto Corporation System and method for globally accessing computer services
US6085192A (en) 1997-04-11 2000-07-04 Roampage, Inc. System and method for securely synchronizing multiple copies of a workspace element in a network
US6023708A (en) 1997-05-29 2000-02-08 Visto Corporation System and method for using a global translator to synchronize workspace elements across a network
US6708221B1 (en) 1996-12-13 2004-03-16 Visto Corporation System and method for globally and securely accessing unified information in a computer network
JP3244166B2 (en) 1996-12-25 2002-01-07 ユニデン株式会社 Information reservation transmission method, information reservation transmission method, and transmission server
US5963642A (en) 1996-12-30 1999-10-05 Goldstein; Benjamin D. Method and apparatus for secure storage of data
US6411696B1 (en) 1996-12-31 2002-06-25 Intel Corporation System for finding a user with a preferred communication mechanism
US5907618A (en) 1997-01-03 1999-05-25 International Business Machines Corporation Method and apparatus for verifiably providing key recovery information in a cryptographic system
US6175831B1 (en) 1997-01-17 2001-01-16 Six Degrees, Inc. Method and apparatus for constructing a networking database and system
US6097383A (en) 1997-01-23 2000-08-01 Zenith Electronics Corporation Video and audio functions in a web television
US6401112B1 (en) 1997-01-29 2002-06-04 Palm, Inc. Method and apparatus for synchronizing an Email client on a portable computer system with an Email client on a desktop computer
US6006274A (en) 1997-01-30 1999-12-21 3Com Corporation Method and apparatus using a pass through personal computer connected to both a local communication link and a computer network for indentifying and synchronizing a preferred computer with a portable computer
US5964833A (en) 1997-02-07 1999-10-12 Datalink Systems Corp. Pager enhanced keyboard and system
US5790425A (en) 1997-02-19 1998-08-04 Sun Microsystems, Inc. Generic server benchmarking framework in a client-server environment
US5928325A (en) 1997-02-24 1999-07-27 Motorola, Inc. Method of dynamically establishing communication of incoming messages to one or more user devices presently available to an intended recipient
US6003070A (en) 1997-02-25 1999-12-14 Intervvoice Limited Partnership E-mail system and interface for equipment monitoring and control
US5890147A (en) 1997-03-07 1999-03-30 Microsoft Corporation Scope testing of documents in a search engine using document to folder mapping
US5948066A (en) 1997-03-13 1999-09-07 Motorola, Inc. System and method for delivery of information over narrow-band communications links
US5867665A (en) 1997-03-24 1999-02-02 Pfn, Inc Domain communications server
US6546005B1 (en) 1997-03-25 2003-04-08 At&T Corp. Active user registry
US6138128A (en) 1997-04-02 2000-10-24 Microsoft Corp. Sharing and organizing world wide web references using distinctive characters
US5961590A (en) 1997-04-11 1999-10-05 Roampage, Inc. System and method for synchronizing electronic mail between a client site and a central site
US5890129A (en) 1997-05-30 1999-03-30 Spurgeon; Loren J. System for exchanging health care insurance information
JPH10336372A (en) 1997-05-30 1998-12-18 Ricoh Co Ltd Transfer method for scan data
US6320943B1 (en) 1997-06-12 2001-11-20 Legerity, Inc. Electronic directory system and method
US6023700A (en) 1997-06-17 2000-02-08 Cranberry Properties, Llc Electronic mail distribution system for integrated electronic communication
US6134432A (en) 1997-06-17 2000-10-17 Bulletin.Net, Inc. System and process for allowing wireless messaging
JP2002504293A (en) 1997-06-19 2002-02-05 マーチャント,ブライアン,イー. Security device for data transmission using dynamic random encryption
US6073142A (en) 1997-06-23 2000-06-06 Park City Group Automated post office based rule analysis of e-mail messages and other data objects for controlled distribution in network environments
US6057855A (en) 1997-07-02 2000-05-02 Hewlett-Packard Company Method and apparatus for providing polygon pixel sub-sample information using incremental means
US6044372A (en) 1997-07-18 2000-03-28 Dazel Corporation Method and apparatus for publishing information to a communications network and enabling subscriptions to such information
US6073165A (en) 1997-07-29 2000-06-06 Jfax Communications, Inc. Filtering computer network messages directed to a user's e-mail box based on user defined filters, and forwarding a filtered message to the user's receiver
US6101320A (en) 1997-08-01 2000-08-08 Aurora Communications Exchange Ltd. Electronic mail communication system and method
US7088801B1 (en) 1997-09-08 2006-08-08 Mci, Inc. Single telephone number access to multiple communications services
US20010010046A1 (en) 1997-09-11 2001-07-26 Muyres Matthew R. Client content management and distribution system
US5845278A (en) 1997-09-12 1998-12-01 Inioseek Corporation Method for automatically selecting collections to search in full text searches
US5909689A (en) 1997-09-18 1999-06-01 Sony Corporation Automatic update of file versions for files shared by several computers which record in respective file directories temporal information for indicating when the files have been created
US6138146A (en) 1997-09-29 2000-10-24 Ericsson Inc. Electronic mail forwarding system and method
US6125369A (en) 1997-10-02 2000-09-26 Microsoft Corporation Continuous object sychronization between object stores on different computers
US5924096A (en) 1997-10-15 1999-07-13 Novell, Inc. Distributed database using indexed into tags to tracks events according to type, update cache, create virtual update log on demand
US5907681A (en) 1997-10-20 1999-05-25 International Business Machines Corporation Intelligent method, apparatus and computer program product for automated refreshing of internet web pages
US5974327A (en) 1997-10-21 1999-10-26 At&T Corp. Adaptive frequency channel assignment based on battery power level in wireless access protocols
US6272545B1 (en) 1997-10-24 2001-08-07 Microsoft Corporation System and method for interaction between one or more desktop computers and one or more mobile devices
US6370566B2 (en) 1998-04-10 2002-04-09 Microsoft Corporation Generating meeting requests and group scheduling from a mobile device
US6052735A (en) 1997-10-24 2000-04-18 Microsoft Corporation Electronic mail object synchronization between a desktop computer and mobile device
US6269369B1 (en) 1997-11-02 2001-07-31 Amazon.Com Holdings, Inc. Networked personal contact manager
FR2771875B1 (en) 1997-11-04 2000-04-14 Gilles Jean Antoine Kremer METHOD FOR TRANSMITTING INFORMATION AND COMPUTER SERVER IMPLEMENTING IT
US6112181A (en) 1997-11-06 2000-08-29 Intertrust Technologies Corporation Systems and methods for matching, selecting, narrowcasting, and/or classifying based on rights management and/or other information
US6034621A (en) 1997-11-18 2000-03-07 Lucent Technologies, Inc. Wireless remote synchronization of data between PC and PDA
US5951636A (en) 1997-12-04 1999-09-14 International Business Machines Corp. Accessing a post office system from a client computer using applets
US6052563A (en) 1997-12-10 2000-04-18 Motorola Communication device controlled by appointment information stored therein, and method therefor
US6295541B1 (en) 1997-12-16 2001-09-25 Starfish Software, Inc. System and methods for synchronizing two or more datasets
US6324587B1 (en) 1997-12-23 2001-11-27 Microsoft Corporation Method, computer program product, and data structure for publishing a data object over a store and forward transport
EP0926591B1 (en) 1997-12-26 2005-08-24 Casio Computer Co., Ltd. Network-access management system and method
US6151606A (en) 1998-01-16 2000-11-21 Visto Corporation System and method for using a workspace data manager to access, manipulate and synchronize network data
US5960406A (en) 1998-01-22 1999-09-28 Ecal, Corp. Scheduling system for use between users on the web
US6157630A (en) 1998-01-26 2000-12-05 Motorola, Inc. Communications system with radio device and server
JP3561139B2 (en) 1998-01-27 2004-09-02 シャープ株式会社 File object relay method, computer-readable recording medium storing program of file object relay method, and gateway computer
US6119171A (en) 1998-01-29 2000-09-12 Ip Dynamics, Inc. Domain name routing
US6205448B1 (en) 1998-01-30 2001-03-20 3Com Corporation Method and apparatus of synchronizing two computer systems supporting multiple synchronization techniques
US6138013A (en) 1998-02-12 2000-10-24 Motorola, Inc. Method for location based intercept in a communication system
US7080371B1 (en) 1998-03-03 2006-07-18 Siebel Systems, Inc. Method, system, apparatus and program product for distribution and instantiation of software upgrades
US6304881B1 (en) 1998-03-03 2001-10-16 Pumatech, Inc. Remote data access and synchronization
US7032242B1 (en) 1998-03-05 2006-04-18 3Com Corporation Method and system for distributed network address translation with network security features
US20010037453A1 (en) 1998-03-06 2001-11-01 Mitty Todd Jay Secure electronic transactions using a trusted intermediary with non-repudiation of receipt and contents of message
US6167379A (en) 1998-03-24 2000-12-26 Siemens Information And Communication Networks, Inc. System for user to accept or decline updating a calendar remotely with a proposed schedule update that may have schedule confliction
US6170014B1 (en) 1998-03-25 2001-01-02 Community Learning And Information Network Computer architecture for managing courseware in a shared use operating environment
US6925477B1 (en) 1998-03-31 2005-08-02 Intellisync Corporation Transferring records between two databases
US6018762A (en) 1998-03-31 2000-01-25 Lucent Technologies Inc. Rules-based synchronization of mailboxes in a data network
US6119014A (en) 1998-04-01 2000-09-12 Ericsson Inc. System and method for displaying short messages depending upon location, priority, and user-defined indicators
US6128627A (en) 1998-04-15 2000-10-03 Inktomi Corporation Consistent data storage in an object cache
US6065055A (en) 1998-04-20 2000-05-16 Hughes; Patrick Alan Inappropriate site management software
US6421781B1 (en) 1998-04-30 2002-07-16 Openwave Systems Inc. Method and apparatus for maintaining security in a push server
US6233341B1 (en) 1998-05-19 2001-05-15 Visto Corporation System and method for installing and using a temporary certificate at a remote site
US6816849B1 (en) 1998-05-26 2004-11-09 Gerald B. Halt, Jr. Advanced internet interface
FI105743B (en) 1998-05-27 2000-09-29 Nokia Mobile Phones Ltd Method for multimedia messaging and multimedia messaging system
US6327586B1 (en) 1998-05-27 2001-12-04 Wisdombuilder, L.L.C. System method and computer program product to automate the management and analysis of heterogeneous data
US6195533B1 (en) 1998-05-27 2001-02-27 Glenayre Electronics, Inc. Method for storing an application's transaction data in a wireless messaging system
US6529908B1 (en) 1998-05-28 2003-03-04 Netspan Corporation Web-updated database with record distribution by email
US6779019B1 (en) 1998-05-29 2004-08-17 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device
US6289214B1 (en) 1998-05-29 2001-09-11 Ericsson Inc. Systems and methods for deactivating a cellular radiotelephone system using an ANSI-41 short message service email
US6438585B2 (en) 1998-05-29 2002-08-20 Research In Motion Limited System and method for redirecting message attachments between a host system and a mobile data communication device
US6463463B1 (en) 1998-05-29 2002-10-08 Research In Motion Limited System and method for pushing calendar event messages from a host system to a mobile data communication device
US7025209B2 (en) 1998-05-29 2006-04-11 Palmsource, Inc. Method and apparatus for wireless internet access
US6219694B1 (en) 1998-05-29 2001-04-17 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device having a shared electronic address
WO1999063458A1 (en) 1998-05-29 1999-12-09 Sony Corporation Experience favorite information providing system
NL1009376C1 (en) 1998-06-11 1998-07-06 Boardwalk Ag Data system for providing relationship patterns between people.
EP1086435A1 (en) 1998-06-11 2001-03-28 Boardwalk AG System, method, and computer program product for providing relational patterns between entities
US6085166A (en) 1998-06-19 2000-07-04 International Business Machines Electronic calendar with group scheduling and asynchronous fan out method
US6101480A (en) 1998-06-19 2000-08-08 International Business Machines Electronic calendar with group scheduling and automated scheduling techniques for coordinating conflicting schedules
CA2336387A1 (en) 1998-06-30 2000-01-06 Paragon Software (Developments) Ltd. Telephone directory management system having wireless telephone interface capability
US6363051B1 (en) 1998-06-30 2002-03-26 At&T Corp. Method and apparatus for achieving fast reconnection of permanent virtal channels in a frame relay network
SE523335C2 (en) 1998-07-03 2004-04-13 Sendit Ab Method and apparatus for accessing and retrieving information
JP4170448B2 (en) 1998-07-03 2008-10-22 富士通株式会社 Group contact system and recording medium recording program for executing contact system
US6300947B1 (en) 1998-07-06 2001-10-09 International Business Machines Corporation Display screen and window size related web page adaptation system
US6256666B1 (en) 1998-07-14 2001-07-03 International Business Machines Corp. Method and system for remotely managing electronic mail attachments
US6275850B1 (en) 1998-07-24 2001-08-14 Siemens Information And Communication Networks, Inc. Method and system for management of message attachments
US6886030B1 (en) 1998-08-18 2005-04-26 United Video Properties, Inc. Electronic mail system employing a low bandwidth link for e-mail notifications
US6336138B1 (en) 1998-08-25 2002-01-01 Hewlett-Packard Company Template-driven approach for generating models on network services
US6438612B1 (en) 1998-09-11 2002-08-20 Ssh Communications Security, Ltd. Method and arrangement for secure tunneling of data between virtual routers
US6289212B1 (en) 1998-09-16 2001-09-11 Openwave Systems Inc. Method and apparatus for providing electronic mail services during network unavailability
US6253202B1 (en) 1998-09-18 2001-06-26 Tacit Knowledge Systems, Inc. Method, system and apparatus for authorizing access by a first user to a knowledge profile of a second user responsive to an access request from the first user
US6115709A (en) 1998-09-18 2000-09-05 Tacit Knowledge Systems, Inc. Method and system for constructing a knowledge profile of a user having unrestricted and restricted access portions according to respective levels of confidence of content of the portions
US6389455B1 (en) 1998-09-22 2002-05-14 Richard C. Fuisz Method and apparatus for bouncing electronic messages
US6198922B1 (en) 1998-09-22 2001-03-06 Iridium Ip Llc Method and system for locating subscribers in a global telecommunications network
US6718740B2 (en) 1998-09-24 2004-04-13 Bell & Howell Mail And Messaging Technologies Company Inserting apparatus and method with controlled, master cycle speed-dependent actuator operations
US7509349B2 (en) 1998-10-01 2009-03-24 Onepin, Inc. Method and apparatus for storing and retrieving business contact information in a computer system
US6131096A (en) 1998-10-05 2000-10-10 Visto Corporation System and method for updating a remote database in a network
US6546425B1 (en) 1998-10-09 2003-04-08 Netmotion Wireless, Inc. Method and apparatus for providing mobile and other intermittent connectivity in a computing environment
US7136645B2 (en) 1998-10-09 2006-11-14 Netmotion Wireless, Inc. Method and apparatus for providing mobile and other intermittent connectivity in a computing environment
US7293107B1 (en) 1998-10-09 2007-11-06 Netmotion Wireless, Inc. Method and apparatus for providing mobile and other intermittent connectivity in a computing environment
US6263340B1 (en) 1998-10-20 2001-07-17 International Business Machines Corp. User registration in file review systems
US6324544B1 (en) 1998-10-21 2001-11-27 Microsoft Corporation File object synchronization between a desktop computer and a mobile device
US6449622B1 (en) 1999-03-08 2002-09-10 Starfish Software, Inc. System and methods for synchronizing datasets when dataset changes may be received out of order
US6871220B1 (en) 1998-10-28 2005-03-22 Yodlee, Inc. System and method for distributed storage and retrieval of personal information
US6502135B1 (en) 1998-10-30 2002-12-31 Science Applications International Corporation Agile network protocol for secure communications with assured system availability
US6167435A (en) 1998-10-30 2000-12-26 Netcreations, Inc. Double opt-in™ method and system for verifying subscriptions to information distribution services
US6363352B1 (en) 1998-11-13 2002-03-26 Microsoft Corporation Automatic scheduling and formation of a virtual meeting over a computer network
FI982490A0 (en) 1998-11-18 1998-11-18 Nokia Corp Procedures and systems for communication
US6490353B1 (en) 1998-11-23 2002-12-03 Tan Daniel Tiong Hok Data encrypting and decrypting apparatus and method
US6859212B2 (en) 1998-12-08 2005-02-22 Yodlee.Com, Inc. Interactive transaction center interface
US20010023414A1 (en) 1998-12-08 2001-09-20 Srihari Kumar Interactive calculation and presentation of financial data results through a single interface on a data-packet-network
US6249808B1 (en) 1998-12-15 2001-06-19 At&T Corp Wireless delivery of message using combination of text and voice
US6292904B1 (en) 1998-12-16 2001-09-18 International Business Machines Corporation Client account generation and authentication system for a network server
US6760916B2 (en) 2000-01-14 2004-07-06 Parkervision, Inc. Method, system and computer program product for producing and distributing enhanced media downstreams
US6516327B1 (en) 1998-12-24 2003-02-04 International Business Machines Corporation System and method for synchronizing data in multiple databases
US20010013069A1 (en) 1999-01-11 2001-08-09 Infospace, Inc. Data messaging aggregation
ES2296381T3 (en) 1999-01-14 2008-04-16 Nokia Corporation METHOD AND SYSTEM OF INTERCEPTATION.
US6442589B1 (en) 1999-01-14 2002-08-27 Fujitsu Limited Method and system for sorting and forwarding electronic messages and other data
FR2788914B1 (en) 1999-01-22 2001-03-23 Sfr Sa AUTHENTICATION METHOD, WITH ESTABLISHMENT OF A SECURE CHANNEL, BETWEEN A SUBSCRIBER AND A SERVICE PROVIDER ACCESSIBLE VIA A TELECOMMUNICATION OPERATOR
US6351767B1 (en) 1999-01-25 2002-02-26 International Business Machines Corporation Method and system for automatically caching dynamic content based on a cacheability determination
US6735591B2 (en) 1999-01-26 2004-05-11 Joseph M. Khan Universal information warehouse system and method
US6173446B1 (en) 1999-02-02 2001-01-09 Ultimus, Inc. Apparatus for licensing software applications
US6201469B1 (en) 1999-02-12 2001-03-13 Sensormatic Electronics Corporation Wireless synchronization of pulsed magnetic EAS systems
US6526506B1 (en) 1999-02-25 2003-02-25 Telxon Corporation Multi-level encryption access point for wireless network
US6247135B1 (en) 1999-03-03 2001-06-12 Starfish Software, Inc. Synchronization process negotiation for computing devices
US6535892B1 (en) 1999-03-08 2003-03-18 Starfish Software, Inc. System and methods for exchanging messages between a client and a server for synchronizing datasets
US6415031B1 (en) 1999-03-12 2002-07-02 Diva Systems Corporation Selective and renewable encryption for secure distribution of video on-demand
JP4299911B2 (en) 1999-03-24 2009-07-22 株式会社東芝 Information transfer system
US7062532B1 (en) 1999-03-25 2006-06-13 Autodesk, Inc. Method and apparatus for drawing collaboration on a network
US6820204B1 (en) 1999-03-31 2004-11-16 Nimesh Desai System and method for selective information exchange
US6308201B1 (en) 1999-04-08 2001-10-23 Palm, Inc. System and method for sharing data among a plurality of personal digital assistants
US6336117B1 (en) 1999-04-30 2002-01-01 International Business Machines Corporation Content-indexing search system and method providing search results consistent with content filtering and blocking policies implemented in a blocking engine
US8050964B2 (en) 1999-05-06 2011-11-01 Etagz, Inc. Computer-readable medium product label apparatus and method
AU4839300A (en) 1999-05-11 2000-11-21 Webvan Group, Inc. Electronic commerce enabled delivery system and method
US6668046B1 (en) 1999-05-18 2003-12-23 Motorola, Inc. Method and system for generating a user's telecommunications bill
US6560456B1 (en) 1999-05-24 2003-05-06 Openwave Systems, Inc. System and method for providing subscriber-initiated information over the short message service (SMS) or a microbrowser
US6996627B1 (en) 1999-05-25 2006-02-07 Realnetworks, Inc. System and method for providing update information
US6377810B1 (en) 1999-06-11 2002-04-23 Motorola, Inc. Method of operation of mobile wireless communication system with location information
US7882247B2 (en) 1999-06-11 2011-02-01 Netmotion Wireless, Inc. Method and apparatus for providing secure connectivity in mobile and other intermittent computing environments
US6782252B1 (en) 1999-06-26 2004-08-24 Lg Information & Communications, Ltd. Apparatus and method for transmitting call holding message in mobile communication terminal
JP2003503907A (en) 1999-06-28 2003-01-28 ユナイテッド ビデオ プロパティーズ, インコーポレイテッド Interactive television program guide system and method with niche hub
US6704278B1 (en) 1999-07-02 2004-03-09 Cisco Technology, Inc. Stateful failover of service managers
US6401104B1 (en) 1999-07-03 2002-06-04 Starfish Software, Inc. System and methods for synchronizing datasets using cooperation among multiple synchronization engines
US6356937B1 (en) 1999-07-06 2002-03-12 David Montville Interoperable full-featured web-based and client-side e-mail system
US6618710B1 (en) 1999-07-07 2003-09-09 International Business Machines Corporation Apparatus and method for intelligent routing of electronic messages to pagers and computers
US6721410B1 (en) 1999-08-10 2004-04-13 Nortel Networks Limited Recursive identification of individuals for casual collaborative conferencing
US6442637B1 (en) 1999-08-12 2002-08-27 Handspring, Inc. Expandable mobile computer system
KR100565040B1 (en) 1999-08-20 2006-03-30 삼성전자주식회사 User interface method using 3-dimensional user input device in 3-dimensional graphic display and computer readable medium therefor
US6549939B1 (en) 1999-08-31 2003-04-15 International Business Machines Corporation Proactive calendar notification agent
US7289964B1 (en) 1999-08-31 2007-10-30 Accenture Llp System and method for transaction services patterns in a netcentric environment
US6640249B1 (en) 1999-08-31 2003-10-28 Accenture Llp Presentation services patterns in a netcentric environment
US6615253B1 (en) 1999-08-31 2003-09-02 Accenture Llp Efficient server side data retrieval for execution of client side applications
US6742015B1 (en) 1999-08-31 2004-05-25 Accenture Llp Base services patterns in a netcentric environment
US6640244B1 (en) 1999-08-31 2003-10-28 Accenture Llp Request batcher in a transaction services patterns environment
US6965917B1 (en) 1999-09-07 2005-11-15 Comverse Ltd. System and method for notification of an event
US7079499B1 (en) 1999-09-08 2006-07-18 Nortel Networks Limited Internet protocol mobility architecture framework
US6601026B2 (en) 1999-09-17 2003-07-29 Discern Communications, Inc. Information retrieval by natural language querying
WO2001022310A1 (en) 1999-09-22 2001-03-29 Oleg Kharisovich Zommers Interactive personal information system and method
US6505214B1 (en) 1999-09-28 2003-01-07 Microsoft Corporation Selective information synchronization based on implicit user designation
US6873688B1 (en) 1999-09-30 2005-03-29 Oy Riddes Ltd. Method for carrying out questionnaire based survey in cellular radio system, a cellular radio system and a base station
US20030078880A1 (en) 1999-10-08 2003-04-24 Nancy Alley Method and system for electronically signing and processing digital documents
US7020685B1 (en) 1999-10-08 2006-03-28 Openwave Systems Inc. Method and apparatus for providing internet content to SMS-based wireless devices
EP1234246B1 (en) 1999-10-22 2015-08-12 Nomadix, Inc. System and method for network access without reconfiguration
US7630986B1 (en) 1999-10-27 2009-12-08 Pinpoint, Incorporated Secure data interchange
US7167839B1 (en) 1999-11-05 2007-01-23 Commercial Recovery Corporation Collection agency data access method
US6721780B1 (en) 1999-11-09 2004-04-13 Fireclick, Inc. Predictive pre-download of network objects
US20020055351A1 (en) 1999-11-12 2002-05-09 Elsey Nicholas J. Technique for providing personalized information and communications services
US8032409B1 (en) 1999-11-22 2011-10-04 Accenture Global Services Limited Enhanced visibility during installation management in a network-based supply chain environment
US6532446B1 (en) 1999-11-24 2003-03-11 Openwave Systems Inc. Server based speech recognition user interface for wireless devices
US6499054B1 (en) 1999-12-02 2002-12-24 Senvid, Inc. Control and observation of physical devices, equipment and processes by multiple users over computer networks
US7120692B2 (en) 1999-12-02 2006-10-10 Senvid, Inc. Access and control system for network-enabled devices
DE19958707A1 (en) 1999-12-06 2001-06-07 Siemens Ag Method of transmitting a text message
IE20001001A1 (en) 1999-12-13 2001-07-11 Markport Ltd A service management access node for mobile internet
US6526433B1 (en) 1999-12-15 2003-02-25 International Business Machines Corporation Adaptive timeout value setting for distributed computing environment (DCE) applications
AU2909401A (en) 1999-12-20 2001-07-03 Planetid, Inc. Information exchange engine providing a critical infrastructure layer and methods of use thereof
US6892196B1 (en) 1999-12-22 2005-05-10 Accenture Llp System, method and article of manufacture for a user programmable diary interface link
US6728530B1 (en) 1999-12-28 2004-04-27 Nokia Corporation Calendar-display apparatus, and associated method, for a mobile terminal
US6898427B1 (en) 1999-12-29 2005-05-24 Bellsouth Intellectual Property Corporation Method of coupling portable communications device to first network by way of second network
US6771294B1 (en) 1999-12-29 2004-08-03 Petri Pulli User interface
US7146645B1 (en) 1999-12-30 2006-12-05 Nokia Mobile Phones Ltd. Dedicated applications for user stations and methods for downloading dedicated applications to user stations
US6625621B2 (en) 2000-01-04 2003-09-23 Starfish Software, Inc. System and methods for a fast and scalable synchronization server
US6664991B1 (en) 2000-01-06 2003-12-16 Microsoft Corporation Method and apparatus for providing context menus on a pen-based device
US6727917B1 (en) 2000-01-06 2004-04-27 Microsoft Corporation User interface for palm-sized computing devices and method and apparatus for displaying the same
US6496802B1 (en) 2000-01-07 2002-12-17 Mp3.Com, Inc. System and method for providing access to electronic works
US6745024B1 (en) 2000-01-10 2004-06-01 Qualcomm Incorporated System and method for preparing and sending an electronic mail communication using a wireless communications device
GB2364477B (en) 2000-01-18 2003-11-05 Ericsson Telefon Ab L M Virtual private networks
US6922721B1 (en) 2000-10-17 2005-07-26 The Phonepages Of Sweden Ab Exchange of information in a communication system
US6694336B1 (en) 2000-01-25 2004-02-17 Fusionone, Inc. Data transfer and synchronization system
US8156074B1 (en) 2000-01-26 2012-04-10 Synchronoss Technologies, Inc. Data transfer and synchronization system
US6671757B1 (en) 2000-01-26 2003-12-30 Fusionone, Inc. Data transfer and synchronization system
US6816944B2 (en) 2000-02-02 2004-11-09 Innopath Software Apparatus and methods for providing coordinated and personalized application and data management for resource-limited mobile devices
US6738766B2 (en) 2000-02-02 2004-05-18 Doongo Technologies, Inc. Apparatus and methods for providing personalized application search results for wireless devices based on user profiles
JP2001218185A (en) 2000-02-03 2001-08-10 Matsushita Electric Ind Co Ltd Device and system for transferring data and program recording medium
US6742059B1 (en) 2000-02-04 2004-05-25 Emc Corporation Primary and secondary management commands for a peripheral connected to multiple agents
US7240067B2 (en) 2000-02-08 2007-07-03 Sybase, Inc. System and methodology for extraction and aggregation of data from dynamic content
US6721787B1 (en) 2000-02-10 2004-04-13 3Com Corporation System and method for wireless hot-synchronization of a personal digital assistant
US20010034225A1 (en) 2000-02-11 2001-10-25 Ash Gupte One-touch method and system for providing email to a wireless communication device
US6895558B1 (en) 2000-02-11 2005-05-17 Microsoft Corporation Multi-access mode electronic personal assistant
US20040117387A1 (en) 2000-02-25 2004-06-17 Vincent Civetta Database sizing and diagnostic utility
US6446118B1 (en) 2000-02-29 2002-09-03 Designtech International, Inc. E-mail notification device
EP1132844A3 (en) 2000-03-02 2002-06-05 Telseon IP Services Inc. E-commerce system facilitating service networks including broadband communication service networks
US6757708B1 (en) 2000-03-03 2004-06-29 International Business Machines Corporation Caching dynamic content
US6757362B1 (en) 2000-03-06 2004-06-29 Avaya Technology Corp. Personal virtual assistant
US6785641B1 (en) 2000-10-11 2004-08-31 Smith International, Inc. Simulating the dynamic response of a drilling tool assembly and its application to drilling tool assembly design optimization and drilling performance optimization
FI108828B (en) 2000-03-14 2002-03-28 Sonera Oyj Providing billing in a telecommunications system
US7634528B2 (en) 2000-03-16 2009-12-15 Microsoft Corporation Harnessing information about the timing of a user's client-server interactions to enhance messaging and collaboration services
US7319847B2 (en) 2000-03-20 2008-01-15 Nielsen Mobile, Inc. Bitwise monitoring of network performance
US6741855B1 (en) 2000-03-24 2004-05-25 Sun Microsystems, Inc. Method and apparatus for remotely managing data via a mobile device
AU2001253161A1 (en) 2000-04-04 2001-10-15 Stick Networks, Inc. Method and apparatus for scheduling presentation of digital content on a personal communication device
US6820088B1 (en) 2000-04-10 2004-11-16 Research In Motion Limited System and method for synchronizing data records between multiple databases
US6221877B1 (en) 2000-04-12 2001-04-24 Regents Of The University Of California Substituted 4-phthalimidocarboxanilides as inhibitors of purine salvage phosphoribosyltransferases
US6981041B2 (en) 2000-04-13 2005-12-27 Aep Networks, Inc. Apparatus and accompanying methods for providing, through a centralized server site, an integrated virtual office environment, remotely accessible via a network-connected web browser, with remote network monitoring and management capabilities
JP2001306463A (en) 2000-04-20 2001-11-02 Matsushita Graphic Communication Systems Inc Mail report device and portable telephone system
WO2001084433A1 (en) 2000-05-01 2001-11-08 Mobliss, Inc. System for conducting electronic surveys
JP2002024020A (en) 2000-05-01 2002-01-25 Toshiba Corp Screen control program, dynamic display information acquisition program, screen display transaction program, screen component interface program and screen program preparing method
US6662016B1 (en) 2000-05-05 2003-12-09 Openwave Systems, Inc. Providing graphical location information for mobile resources using a data-enabled network
US6928481B1 (en) 2000-05-05 2005-08-09 International Business Machines Corporation Method, apparatus and program to optimize the network distribution of digital information based on hierarchical grouping of server topology and code distribution
FI20001078A (en) 2000-05-08 2001-11-09 Nokia Corp Shared application access to data services for wireless communication systems
US7353274B1 (en) 2000-05-09 2008-04-01 Medisys/Rjb Consulting, Inc. Method, apparatus, and system for determining whether a computer is within a particular location
US7725525B2 (en) 2000-05-09 2010-05-25 James Duncan Work Method and apparatus for internet-based human network brokering
US6643650B1 (en) 2000-05-09 2003-11-04 Sun Microsystems, Inc. Mechanism and apparatus for using messages to look up documents stored in spaces in a distributed computing environment
US6868447B1 (en) 2000-05-09 2005-03-15 Sun Microsystems, Inc. Mechanism and apparatus for returning results of services in a distributed computing environment
KR20010105705A (en) 2000-05-17 2001-11-29 정문술 Method for providing integrated user management environment to multi-internet service and system for the same
US6593944B1 (en) 2000-05-18 2003-07-15 Palm, Inc. Displaying a web page on an electronic display device having a limited display area
GB0012195D0 (en) 2000-05-19 2000-07-12 Nokia Networks Oy Location information services
US6671700B1 (en) 2000-05-23 2003-12-30 Palm Source, Inc. Method and apparatus for parallel execution of conduits during simultaneous synchronization of databases
US6985933B1 (en) 2000-05-30 2006-01-10 International Business Machines Corporation Method and system for increasing ease-of-use and bandwidth utilization in wireless devices
US6785868B1 (en) 2000-05-31 2004-08-31 Palm Source, Inc. Method and apparatus for managing calendar information from a shared database and managing calendar information from multiple users
US6556217B1 (en) 2000-06-01 2003-04-29 Nokia Corporation System and method for content adaptation and pagination based on terminal capabilities
US8060389B2 (en) 2000-06-07 2011-11-15 Apple Inc. System and method for anonymous location based services
US8073565B2 (en) 2000-06-07 2011-12-06 Apple Inc. System and method for alerting a first mobile data processing system nearby a second mobile data processing system
JP3526435B2 (en) 2000-06-08 2004-05-17 株式会社東芝 Network system
EP1292884A2 (en) 2000-06-12 2003-03-19 Preworx ( Proprietary) Limited System for controlling a display of the user interface of a software application
US7058691B1 (en) 2000-06-12 2006-06-06 Trustees Of Princeton University System for wireless push and pull based services
JP2001356973A (en) 2000-06-13 2001-12-26 Century Systems Kk Network system
US20020095328A1 (en) 2000-06-14 2002-07-18 Garret Swart Method and apparatus for profiling clients of a database-driven transaction system and marketing according to profile data
US6732101B1 (en) 2000-06-15 2004-05-04 Zix Corporation Secure message forwarding system detecting user's preferences including security preferences
WO2001097088A1 (en) 2000-06-15 2001-12-20 Orion's Belt, Inc. Method of and system for determining connections between parties over a network
US20020019812A1 (en) 2000-06-16 2002-02-14 Board Karen Eleanor System and service for receiving, customizing, and re-broadcasting high-speed financial data to users operating wireless network-capable devices
FI111899B (en) 2000-06-16 2003-09-30 Nokia Corp Method for allocating billing in message delivery system, delivery system, server and terminal
US6738808B1 (en) 2000-06-30 2004-05-18 Bell South Intellectual Property Corporation Anonymous location service for wireless networks
FI110400B (en) 2000-07-03 2003-01-15 Nokia Corp A method, terminal, and system for managing multiple mailboxes
AU2001278873A1 (en) 2000-07-06 2002-01-21 Broadbeam Corporation System and method for the remote creation of notification agents for wireless devices
EP1354263A2 (en) 2000-07-07 2003-10-22 Openwave Systems Inc. Graphical user interface features of a browser in a hand-held wireless communication device
IL153841A0 (en) 2000-07-10 2003-07-31 Viven Ltd Broadcast content over cellular telephones
US7047202B2 (en) 2000-07-13 2006-05-16 Amit Jaipuria Method and apparatus for optimizing networking potential using a secured system for an online community
US6621892B1 (en) 2000-07-14 2003-09-16 America Online, Inc. System and method for converting electronic mail text to audio for telephonic delivery
US6968179B1 (en) 2000-07-27 2005-11-22 Microsoft Corporation Place specific buddy list services
KR20010007743A (en) 2000-07-27 2001-02-05 이승열 WAP connecting method using guidecode inserted an advertisement
ATE266296T1 (en) 2000-08-02 2004-05-15 Aepona Ltd GATEWAY FOR ACCESSING NETWORK RESOURCES
US6944662B2 (en) 2000-08-04 2005-09-13 Vinestone Corporation System and methods providing automatic distributed data retrieval, analysis and reporting services
EP1360620A2 (en) 2000-08-04 2003-11-12 Mobileaware Technologies Limited An e-business mobility platform
JP2002057807A (en) 2000-08-08 2002-02-22 Nec Corp Telephone directory management system for portable telephone
US7146404B2 (en) 2000-08-22 2006-12-05 Colloquis, Inc. Method for performing authenticated access to a service on behalf of a user
US6430602B1 (en) 2000-08-22 2002-08-06 Active Buddy, Inc. Method and system for interactively responding to instant messaging requests
TW512640B (en) 2000-08-25 2002-12-01 Phone Inc W Mobile opinion polling system and method
EP1187481B1 (en) 2000-09-11 2008-04-02 Handmark Europe AB A method for dynamic caching
US6938079B1 (en) 2000-09-19 2005-08-30 3Com Corporation System and method for automatically configuring a client device
US7225231B2 (en) 2000-09-20 2007-05-29 Visto Corporation System and method for transmitting workspace elements across a network
AU2001296932A1 (en) 2000-09-28 2002-04-08 Accessline Communications Corporation User configurable system for handling incoming calls to users having multiple destinations adresses
US6650890B1 (en) 2000-09-29 2003-11-18 Postini, Inc. Value-added electronic messaging services and transparent implementation thereof using intermediate server
US6901437B1 (en) 2000-10-06 2005-05-31 Verizon Laboratories Inc. Mobile cache for dynamically composing user-specific information
WO2002031702A1 (en) 2000-10-09 2002-04-18 Enic Corporation Registering and using multilingual domain names
US20020161928A1 (en) 2000-10-10 2002-10-31 Awele Ndili Smart agent for providing network content to wireless devices
US20020042875A1 (en) 2000-10-11 2002-04-11 Jayant Shukla Method and apparatus for end-to-end secure data communication
US8321459B2 (en) 2000-10-11 2012-11-27 Peter Pekarek-Kostka Method and system for facilitating access to always current contact information
JP3851944B2 (en) 2000-10-17 2006-11-29 株式会社メキキ Human network relationship registration system, human network relationship registration method and server, human network relationship registration program, and computer-readable recording medium recording the program
US6804707B1 (en) 2000-10-20 2004-10-12 Eric Ronning Method and system for delivering wireless messages and information to personal computing devices
US6990472B2 (en) 2000-10-23 2006-01-24 Starpound Corporation Telecommunications initiated data fulfillment system
US20020156839A1 (en) 2000-10-26 2002-10-24 Scott Peterson System for providing localized content information via wireless personal communication devices
AU2002228739A1 (en) 2000-10-27 2002-05-06 Entigen Corporation Integrating heterogeneous data and tools
US7117262B2 (en) 2000-11-01 2006-10-03 Inktomi Corporation Cooperative management of distributed network caches
US20020087883A1 (en) 2000-11-06 2002-07-04 Curt Wohlgemuth Anti-piracy system for remotely served computer applications
US7870196B2 (en) 2000-11-08 2011-01-11 Nokia Corporation System and methods for using an application layer control protocol transporting spatial location information pertaining to devices connected to wired and wireless internet protocol networks
AU2002226886A1 (en) 2000-11-09 2002-05-21 Change Tools, Inc. A user definable interface system, method and computer program product
US20020146129A1 (en) 2000-11-09 2002-10-10 Kaplan Ari D. Method and system for secure wireless database management
US20020120779A1 (en) 2000-11-14 2002-08-29 Douglas Teeple Mediation software for delivery of interactive mobile messaging and personalized content to mobile devices
US20030054810A1 (en) 2000-11-15 2003-03-20 Chen Yih-Farn Robin Enterprise mobile server platform
US6986061B1 (en) 2000-11-20 2006-01-10 International Business Machines Corporation Integrated system for network layer security and fine-grained identity-based access control
FI114364B (en) 2000-11-22 2004-09-30 Nokia Corp Data transfer
US7039391B2 (en) 2000-11-28 2006-05-02 Xanboo, Inc. Method and system for communicating with a wireless device
US20050278641A1 (en) 2000-11-30 2005-12-15 Steve Mansour Javascript Calendar Application Delivered to a Web Browser
US6766165B2 (en) 2000-12-05 2004-07-20 Nortel Networks Limited Method and system for remote and local mobile network management
US7260590B1 (en) 2000-12-06 2007-08-21 Cisco Technology, Inc. Streamed database archival process with background synchronization
US6976075B2 (en) 2000-12-08 2005-12-13 Clarinet Systems, Inc. System uses communication interface for configuring a simplified single header packet received from a PDA into multiple headers packet before transmitting to destination device
US7085555B2 (en) 2000-12-19 2006-08-01 Bellsouth Intellectual Property Corporation Location blocking service from a web advertiser
US7596791B2 (en) 2000-12-19 2009-09-29 Emc Corporation Methods and techniques for delivering rich Java applications over thin-wire connections with high performance and scalability
US6944679B2 (en) 2000-12-22 2005-09-13 Microsoft Corp. Context-aware systems and methods, location-aware systems and methods, context-aware vehicles and methods of operating the same, and location-aware vehicles and methods of operating the same
FI110560B (en) 2000-12-27 2003-02-14 Nokia Corp Grouping of wireless communication terminals
JP2002215582A (en) 2000-12-28 2002-08-02 Morgan Stanley Dean Witter Japan Ltd Method and device for authentication
US7310350B1 (en) 2000-12-29 2007-12-18 Oracle International Corporation Mobile surveys and polling
US20020087679A1 (en) 2001-01-04 2002-07-04 Visual Insights Systems and methods for monitoring website activity in real time
US6931529B2 (en) 2001-01-05 2005-08-16 International Business Machines Corporation Establishing consistent, end-to-end protection for a user datagram
US7257639B1 (en) 2001-01-19 2007-08-14 Microsoft Corporation Enhanced email—distributed attachment storage
US6871236B2 (en) 2001-01-26 2005-03-22 Microsoft Corporation Caching transformed content in a mobile gateway
US6845153B2 (en) 2001-01-31 2005-01-18 Telefonaktiebolaget Lm Ericsson (Publ) Network independent party addressing using a unique identifier linked to network specific addresses
WO2002065286A2 (en) 2001-02-12 2002-08-22 Lto Limited Client software enabling a client to run a network based application
US7013350B2 (en) 2001-02-16 2006-03-14 Microsoft Corporation System setting flags based on address types in destination address field of a message to indicate different transports to deliver the message
US7225259B2 (en) 2001-02-21 2007-05-29 Nokia Inc. Service tunnel over a connectionless network
WO2002071287A2 (en) 2001-02-23 2002-09-12 Mobilitec Inc. System and method for charging for directed provisioning of user applications on limited-resource devices
US7085824B2 (en) 2001-02-23 2006-08-01 Power Measurement Ltd. Systems for in the field configuration of intelligent electronic devices
US6463382B1 (en) 2001-02-26 2002-10-08 Motorola, Inc. Method of optimizing traffic content
JP3782671B2 (en) 2001-02-28 2006-06-07 株式会社エヌ・ティ・ティ・ドコモ Link manager and link management method
US6985983B2 (en) 2001-03-01 2006-01-10 Hewlett-Packard Development Company, L.P. Translating device adapter having a common command set for interfacing multiple types of redundant storage devices to a host processor
US20030023975A1 (en) 2001-03-02 2003-01-30 Microsoft Corporation Enhanced music services for television
US20030223554A1 (en) 2001-03-06 2003-12-04 Zhang Jack K. Communication systems and methods
US6636482B2 (en) 2001-03-08 2003-10-21 Arris International, Inc. Method and apparatus for controlling traffic loading of different service levels in a cable data system
JP2002271400A (en) 2001-03-09 2002-09-20 Matsushita Electric Ind Co Ltd Method of data transmission
US20030125023A1 (en) 2001-03-15 2003-07-03 Eyal Fishler Method and system for providing a wireless terminal communication session integrated with data and voice services
US7233795B1 (en) 2001-03-19 2007-06-19 Ryden Michael V Location based communications system
US7242680B2 (en) 2001-03-20 2007-07-10 Verizon Business Global Llc Selective feature blocking in a communications network
US7043637B2 (en) 2001-03-21 2006-05-09 Microsoft Corporation On-disk file format for a serverless distributed file system
US6847974B2 (en) 2001-03-26 2005-01-25 Us Search.Com Inc Method and apparatus for intelligent data assimilation
US6707801B2 (en) 2001-03-28 2004-03-16 Qualcomm Incorporated Method and apparatus for data transport in a wireless communication system
US20020144109A1 (en) 2001-03-29 2002-10-03 International Business Machines Corporation Method and system for facilitating public key credentials acquisition
US6993326B2 (en) 2001-04-02 2006-01-31 Bellsouth Intellectual Property Corporation System and method for providing short message targeted advertisements over a wireless communications network
FI20010761A (en) 2001-04-11 2002-10-12 Suomen Posti Oyj Method, system and device for voting
DE60226714D1 (en) 2001-04-12 2008-07-03 Research In Motion Ltd System and method for dynamically shifting information to wireless data communication devices
US7398271B1 (en) 2001-04-16 2008-07-08 Yahoo! Inc. Using network traffic logs for search enhancement
US7921290B2 (en) 2001-04-18 2011-04-05 Ipass Inc. Method and system for securely authenticating network access credentials for users
US6987734B2 (en) 2001-04-20 2006-01-17 Clear Channel Wireless, Inc. Provision of digital data via multiple broadcasts
US6981062B2 (en) 2001-04-20 2005-12-27 Sbc Technology Resources, Inc. World wide web content synchronization between wireless devices
US20020174189A1 (en) 2001-04-23 2002-11-21 Luosheng Peng Apparatus and methods for intelligently caching applications and data on a mobile device
US6885388B2 (en) 2001-04-25 2005-04-26 Probaris Technologies Inc. Method for automatically generating list of meeting participants and delegation permission
US6944447B2 (en) 2001-04-27 2005-09-13 Accenture Llp Location-based services
US7437295B2 (en) 2001-04-27 2008-10-14 Accenture Llp Natural language processing for a location-based services system
US7698228B2 (en) 2001-04-27 2010-04-13 Accenture Llp Tracking purchases in a location-based services system
AUPR464601A0 (en) 2001-04-30 2001-05-24 Commonwealth Of Australia, The Shapes vector
US20020158908A1 (en) 2001-04-30 2002-10-31 Kristian Vaajala Web browser user interface for low-resolution displays
US7430609B2 (en) 2001-04-30 2008-09-30 Aol Llc, A Delaware Limited Liability Company Managing access to streams hosted on duplicating switches
TW550961B (en) 2001-05-03 2003-09-01 Far Eastone Telecomm Co Ltd Mobile phone Internet access utilizing short message services apparatus and method
US7088821B2 (en) 2001-05-03 2006-08-08 Cheman Shaik Absolute public key cryptographic system and method surviving private-key compromise with other advantages
JP2002335518A (en) 2001-05-09 2002-11-22 Fujitsu Ltd Control unit for controlling display, server and program
ATE350868T1 (en) 2001-05-10 2007-01-15 Nortel Networks Ltd SYSTEM AND METHOD FOR DIRECTING COMMUNICATIONS BETWEEN MOBILE TELECOMMUNICATIONS NETWORKS USING DIFFERENT RADIO ACCESS TECHNOLOGIES
FI112906B (en) 2001-05-10 2004-01-30 Nokia Corp Method and apparatus for forming a communication group
EP1388107A1 (en) 2001-05-11 2004-02-11 Swisscom Mobile AG Method for transmitting an anonymous request from a consumer to a content or service provider through a telecommunication network
US7433922B2 (en) 2001-05-11 2008-10-07 Varia Llc Method and system for collecting and displaying aggregate presence information for mobile media players
US20030051142A1 (en) 2001-05-16 2003-03-13 Hidalgo Lluis Mora Firewalls for providing security in HTTP networks and applications
US20040024892A1 (en) 2001-05-21 2004-02-05 Creswell Carroll W. System for providing sequenced communications within a group
US7024491B1 (en) 2001-05-23 2006-04-04 Western Digital Ventures, Inc. Remotely synchronizing a mobile terminal by adapting ordering and filtering synchronization rules based on a user's operation of the mobile terminal
KR100417407B1 (en) 2001-05-25 2004-02-05 엘지전자 주식회사 Power saving method of mobile communication terminal
US7130839B2 (en) 2001-05-29 2006-10-31 Sun Microsystems, Inc. Method and system for grouping entries in a directory server by group memberships defined by roles
US7206806B2 (en) 2001-05-30 2007-04-17 Pineau Richard A Method and system for remote utilizing a mobile device to share data objects
EP1402388A4 (en) 2001-06-04 2005-03-16 Nct Group Inc System and method for modifying a data stream using element parsing
US7827055B1 (en) 2001-06-07 2010-11-02 Amazon.Com, Inc. Identifying and providing targeted content to users having common interests
US7155710B2 (en) 2001-06-08 2006-12-26 Igt Method and apparatus for gaming device software configuration
US7296155B1 (en) 2001-06-08 2007-11-13 Cisco Technology, Inc. Process and system providing internet protocol security without secure domain resolution
US6957397B1 (en) 2001-06-11 2005-10-18 Palm, Inc. Navigating through a menu of a handheld computer using a keyboard
JP3926792B2 (en) 2001-06-12 2007-06-06 リサーチ イン モーション リミテッド System and method for compressing secure email for exchange with mobile data communication devices
US7120928B2 (en) 2001-06-15 2006-10-10 Dinesh Sheth Secure selective sharing of account information on an internet information aggregation system
US20020193094A1 (en) 2001-06-15 2002-12-19 Lawless John P. Method and system for downloading software products directly to wireless phones
US6671695B2 (en) 2001-06-18 2003-12-30 The Procter & Gamble Company Dynamic group generation and management
US6947770B2 (en) 2001-06-22 2005-09-20 Ericsson, Inc. Convenient dialing of names and numbers from a phone without alpha keypad
WO2003003756A2 (en) 2001-06-27 2003-01-09 Flarion Technologies, Inc. Methods and apparatus for supporting group communications
US7409423B2 (en) 2001-06-28 2008-08-05 Horvitz Eric J Methods for and applications of learning and inferring the periods of time until people are available or unavailable for different forms of communication, collaboration, and information access
ATE464753T1 (en) 2001-06-29 2010-04-15 Motorola Inc METHOD FOR UPDATING A LIST OF MEMBERS OF A PARTICIPANT GROUP
US7219139B2 (en) 2001-06-29 2007-05-15 Claria Corporation System and method for using continuous messaging units in a network architecture
US6798358B2 (en) 2001-07-03 2004-09-28 Nortel Networks Limited Location-based content delivery
US20040205248A1 (en) 2001-07-10 2004-10-14 Herbert A Little System and method for secure message key caching in a mobile communication device
US20030153338A1 (en) 2001-07-24 2003-08-14 Herz Frederick S. M. Autoband
US20030046433A1 (en) 2001-07-25 2003-03-06 Omer Luzzatti Method to synchronize information between online devices
JP2003046576A (en) 2001-07-27 2003-02-14 Fujitsu Ltd Message delivery system, message delivery management server, message distribution management program, and computer-readable recording medium with the program recorded thereon
US7809364B2 (en) 2001-07-30 2010-10-05 Nokia Mobile Phones Limited Apparatus, and associated method, for providing an operation parameter to a mobile station of a radio communication station
US20030028430A1 (en) 2001-08-01 2003-02-06 Zimmerman Stephen M. System, computer product and method for providing billboards with pull technology
US20030028441A1 (en) 2001-08-02 2003-02-06 International Business Machines Corporation Answer fulfillment-based marketing
US7962622B2 (en) 2001-08-07 2011-06-14 Motorola Mobility, Inc. System and method for providing provisioning and upgrade services for a wireless device
US7596565B2 (en) 2001-08-07 2009-09-29 Good Technology System and method for maintaining wireless file folders at a wireless device
US7743119B2 (en) 2001-08-07 2010-06-22 Motorola, Inc. System and method for mapping identification codes
EP1283648A1 (en) 2001-08-07 2003-02-12 Siemens Aktiengesellschaft Method, Terminal and radiocommunications system for transmission of group messages
US7389412B2 (en) 2001-08-10 2008-06-17 Interactive Technology Limited Of Hk System and method for secure network roaming
US7133862B2 (en) 2001-08-13 2006-11-07 Xerox Corporation System with user directed enrichment and import/export control
US7185362B2 (en) 2001-08-20 2007-02-27 Qualcomm, Incorporated Method and apparatus for security in a data processing system
DE10141858B4 (en) 2001-08-27 2010-06-17 Kraussmaffei Technologies Gmbh Method and device for producing sheet-like plastic molded parts, in particular plastic discs
US6996393B2 (en) 2001-08-31 2006-02-07 Nokia Corporation Mobile content delivery system
US20030046587A1 (en) 2001-09-05 2003-03-06 Satyam Bheemarasetti Secure remote access using enterprise peer networks
US20030046586A1 (en) 2001-09-05 2003-03-06 Satyam Bheemarasetti Secure remote access to data between peers
US8583430B2 (en) 2001-09-06 2013-11-12 J. Albert Avila Semi-automated intermodal voice to data transcription method and apparatus
US20030050041A1 (en) 2001-09-07 2003-03-13 Robert Wu Network system for providing prepaid wireless remote access service
US7567575B2 (en) 2001-09-07 2009-07-28 At&T Corp. Personalized multimedia services using a mobile service platform
CA2356823C (en) 2001-09-10 2010-05-11 Research In Motion Limited System and method for real time self-provisioning for a mobile communication device
US20030065802A1 (en) 2001-09-28 2003-04-03 Nokia Corporation System and method for dynamically producing a multimedia content sample for mobile terminal preview
US7392483B2 (en) 2001-09-28 2008-06-24 Ntt Docomo, Inc, Transformation of platform specific graphical user interface widgets migrated between heterogeneous device platforms
US20030063120A1 (en) 2001-09-28 2003-04-03 Wong Hoi Lee Candy Scalable graphical user interface architecture
US7234111B2 (en) 2001-09-28 2007-06-19 Ntt Docomo, Inc. Dynamic adaptation of GUI presentations to heterogeneous device platforms
US8500556B2 (en) * 2001-09-28 2013-08-06 Bally Gaming, Inc. Two-wire exchange system
US20030065738A1 (en) 2001-10-01 2003-04-03 Thumb Logic, Inc. Wireless information systems and methods
US20030065739A1 (en) 2001-10-01 2003-04-03 J. Mitchell Shnier Methods for independently generating a reference to desired information available from a remote source
US20030084165A1 (en) 2001-10-12 2003-05-01 Openwave Systems Inc. User-centric session management for client-server interaction using multiple applications and devices
US20030072451A1 (en) 2001-10-16 2003-04-17 Pimentel Roberto J. Method and apparatus for securely transferring wireless data
US7007107B1 (en) 2001-10-22 2006-02-28 United Electronic Industries Methods and apparatus for performing data acquisition and control
WO2003036520A1 (en) 2001-10-23 2003-05-01 Visto Corporation System and method for merging remote and local data in a single user interface
US6993327B2 (en) 2001-10-29 2006-01-31 Motorola, Inc. Multicast distribution of presence information for an instant messaging system
US7917394B2 (en) 2001-11-19 2011-03-29 Csg Systems, Inc. System and method for providing access to network services
US6892070B2 (en) 2001-11-05 2005-05-10 Unnikrishnan S. Warrier Communication system and method for minimizing international roaming costs
US7127477B2 (en) 2001-11-06 2006-10-24 Everyware Solutions Inc. Method and system for access to automatically synchronized remote files
US20030088629A1 (en) 2001-11-08 2003-05-08 Martin Berkowitz Email management system and method
US7028183B2 (en) 2001-11-13 2006-04-11 Symantec Corporation Enabling secure communication in a clustered or distributed architecture
US20040103147A1 (en) 2001-11-13 2004-05-27 Flesher Kevin E. System for enabling collaboration and protecting sensitive data
JP2005509979A (en) 2001-11-15 2005-04-14 ヴィスト・コーポレーション Asynchronous synchronization system and method
US7373362B2 (en) 2001-11-19 2008-05-13 Extended Systems, Inc. Coordinated synchronization
US6885874B2 (en) 2001-11-27 2005-04-26 Motorola, Inc. Group location and route sharing system for communication units in a trunked communication system
US20080301231A1 (en) 2001-11-28 2008-12-04 Samir Narendra Mehta Method and System for Maintaining and Distributing Wireless Applications
US20050144219A1 (en) 2001-12-05 2005-06-30 Shinji Terada Communication information sharing system, communication information sharing method, communication information sharing program
WO2003049357A2 (en) 2001-12-07 2003-06-12 Telefonaktiebolaget Lm Ericsson (Publ) Lawful interception of end-to-end encrypted data traffic
WO2003050771A1 (en) 2001-12-12 2003-06-19 Scytl Online World Security, Sa Secure electronic voting method and the cryptographic protocols and computer programs used
US7149780B2 (en) 2001-12-14 2006-12-12 Pitney Bowes Inc. Method for determining e-mail address format rules
US7062024B2 (en) 2001-12-19 2006-06-13 Ameritech Communications, Inc. Telecommunication services reporting system
US7313766B2 (en) 2001-12-20 2007-12-25 Nokia Corporation Method, system and apparatus for constructing fully personalized and contextualized user interfaces for terminals in mobile use
JP4386732B2 (en) 2002-01-08 2009-12-16 セブン ネットワークス, インコーポレイテッド Mobile network connection architecture
WO2003063103A1 (en) 2002-01-18 2003-07-31 Georgia Tech Research Corporation Monitoring and tracking of assets by utilizing wireless communications
US7219222B1 (en) 2002-01-18 2007-05-15 Ge Medical Technology Services, Inc. Method and system to grant access to software options resident on a medical imaging device
US6741232B1 (en) 2002-01-23 2004-05-25 Good Technology, Inc. User interface for a data processing apparatus
US6907501B2 (en) 2002-01-25 2005-06-14 Ntt Docomo Inc. System for management of cacheable streaming content in a packet based communication network with mobile hosts
US20030154212A1 (en) 2002-01-28 2003-08-14 International Business Machines Corporation Method and apparatus for determining attributes among objects
GB0202370D0 (en) 2002-02-01 2002-03-20 Symbian Ltd Pinging
US7392348B2 (en) 2003-08-06 2008-06-24 International Business Machines Corporation Method for validating remotely cached dynamic content web pages
US7257776B2 (en) 2002-02-05 2007-08-14 Microsoft Corporation Systems and methods for scaling a graphical user interface according to display dimensions and using a tiered sizing schema to define display objects
US7711854B2 (en) 2002-02-07 2010-05-04 Accenture Global Services Gmbh Retrieving documents over a network with a wireless communication device
US7007242B2 (en) 2002-02-20 2006-02-28 Nokia Corporation Graphical user interface for a mobile device
US6910159B2 (en) 2002-02-20 2005-06-21 Microsoft Corporation System and method for gathering and automatically processing user and debug data for mobile devices
US7240095B1 (en) 2002-02-22 2007-07-03 Bellsouth Intellectual Property Corporation Electronic mail notification
US6775362B1 (en) 2002-03-06 2004-08-10 Alcatel Graphical telephone system
GB0205130D0 (en) 2002-03-06 2002-04-17 Symbian Ltd A method of enabling a wireless information device to access data services
JP4366040B2 (en) 2002-03-07 2009-11-18 インターナショナル・ビジネス・マシーンズ・コーポレーション Network service system, server and program
US20050108322A1 (en) 2002-03-11 2005-05-19 Robert Kline System and method for pushing data to a mobile device
US6806883B2 (en) 2002-03-11 2004-10-19 Sun Microsystems, Inc. System and method for handling display device requests for display data from a frame buffer
US7257391B2 (en) 2002-03-26 2007-08-14 Zoove Corp. Wireless data system
US8516114B2 (en) 2002-03-29 2013-08-20 International Business Machines Corporation Method and apparatus for content pre-fetching and preparation
US20040078814A1 (en) 2002-03-29 2004-04-22 Digeo, Inc. Module-based interactive television ticker
US7184790B2 (en) 2002-04-02 2007-02-27 Dorenbosch Jheroen P Method and apparatus for establishing a talk group
US9137324B2 (en) 2002-04-10 2015-09-15 International Business Machines Corporation Capacity on-demand in distributed computing environments
US20030204602A1 (en) 2002-04-26 2003-10-30 Hudson Michael D. Mediated multi-source peer content delivery network architecture
US7272122B2 (en) 2002-04-26 2007-09-18 Nokia Corporation Relocation of application-specific functionality during seamless network layer-level handoffs
US7376701B2 (en) 2002-04-29 2008-05-20 Cisco Technology, Inc. System and methodology for control of, and access and response to internet email from a wireless device
US7016978B2 (en) 2002-04-29 2006-03-21 Bellsouth Intellectual Property Corporation Instant messaging architecture and system for interoperability and presence management
US7818365B2 (en) 2002-05-01 2010-10-19 Sybase, Inc. System, method, and computer program product for online and offline interactive applications on mobile devices
US20030208529A1 (en) 2002-05-03 2003-11-06 Sreenath Pendyala System for and method of real-time remote access and manipulation of data
US7395329B1 (en) 2002-05-13 2008-07-01 At&T Delaware Intellectual Property., Inc. Real-time notification of presence availability changes
US20030217142A1 (en) 2002-05-15 2003-11-20 Microsoft Corporation Method and system for supporting the communication of presence information regarding one or more telephony devices
US20030217098A1 (en) 2002-05-15 2003-11-20 Microsoft Corporation Method and system for supporting the communication of presence information regarding one or more telephony devices
KR100871118B1 (en) 2002-05-18 2008-11-28 엘지전자 주식회사 Management method for multicast group
GB0211736D0 (en) 2002-05-21 2002-07-03 Commtag Ltd Data communications systems
CN100478943C (en) 2002-05-31 2009-04-15 国际商业机器公司 System and method for accessing different types of back end data stores
US20030227487A1 (en) 2002-06-01 2003-12-11 Hugh Harlan M. Method and apparatus for creating and accessing associative data structures under a shared model of categories, rules, triggers and data relationship permissions
US7016909B2 (en) 2002-06-04 2006-03-21 Microsoft Corporation Method and system for expansion of recurring calendar events
EP1514382A2 (en) 2002-06-07 2005-03-16 Koninklijke Philips Electronics N.V. Wireless technology co-existence
US6867965B2 (en) 2002-06-10 2005-03-15 Soon Huat Khoo Compound portable computing device with dual portion keyboard coupled over a wireless link
US6966058B2 (en) 2002-06-12 2005-11-15 Agami Systems, Inc. System and method for managing software upgrades in a distributed computing system
US7353394B2 (en) 2002-06-20 2008-04-01 International Business Machine Corporation System and method for digital signature authentication of SMS messages
US7096030B2 (en) 2002-06-28 2006-08-22 Nokia Corporation System and method for initiating location-dependent applications on mobile devices
US8924484B2 (en) 2002-07-16 2014-12-30 Sonicwall, Inc. Active e-mail filter with challenge-response
US6941310B2 (en) 2002-07-17 2005-09-06 Oracle International Corp. System and method for caching data for a mobile application
US7085787B2 (en) 2002-07-19 2006-08-01 International Business Machines Corporation Capturing data changes utilizing data-space tracking
US20040027378A1 (en) 2002-08-06 2004-02-12 Hays Grace L. Creation of user interfaces for multiple devices
US20040027326A1 (en) 2002-08-06 2004-02-12 Grace Hays System for and method of developing a common user interface for mobile applications
US7349871B2 (en) 2002-08-08 2008-03-25 Fujitsu Limited Methods for purchasing of goods and services
CN1221898C (en) 2002-08-13 2005-10-05 国际商业机器公司 System and method for updating network proxy cache server object
US6968175B2 (en) 2002-08-13 2005-11-22 Nokia Corporation Method and system for sharing transmission revenue between mobile operators and content providers
CA2495639C (en) 2002-08-16 2011-03-08 Research In Motion Limited System and method for triggering a provisioning event
AU2003270139A1 (en) 2002-08-30 2004-03-19 Koninklijke Kpn N.V. Method and system for the phased retrieval of data
US20050038724A1 (en) 2002-08-30 2005-02-17 Navio Systems, Inc. Methods and apparatus for enabling transaction relating to digital assets
US20050234860A1 (en) 2002-08-30 2005-10-20 Navio Systems, Inc. User agent for facilitating transactions in networks
US20050038707A1 (en) 2002-08-30 2005-02-17 Navio Systems, Inc. Methods and apparatus for enabling transactions in networks
US6756882B2 (en) 2002-09-09 2004-06-29 Motorola, Inc. Method and controller for providing a location-based game associated with a plurality of mobile stations
US20080313282A1 (en) 2002-09-10 2008-12-18 Warila Bruce W User interface, operating system and architecture
US7209137B2 (en) 2002-09-12 2007-04-24 International Business Machines Corporation Efficient triangular shaped meshes
US10373420B2 (en) 2002-09-16 2019-08-06 Touchtunes Music Corporation Digital downloading jukebox with enhanced communication features
KR100486713B1 (en) 2002-09-17 2005-05-03 삼성전자주식회사 Apparatus and method for streaming multimedia data
US7725542B2 (en) 2003-02-10 2010-05-25 At&T Intellectual Property I, L.P. Forwarding IM messages to E-mail
US20060190984A1 (en) 2002-09-23 2006-08-24 Credant Technologies, Inc. Gatekeeper architecture/features to support security policy maintenance and distribution
US7051053B2 (en) 2002-09-30 2006-05-23 Dinesh Sinha Method of lazily replicating files and monitoring log in backup file system
US20040064445A1 (en) 2002-09-30 2004-04-01 Pfleging Gerald W. Wireless access to a database by a short message system query
US7016673B2 (en) 2002-10-01 2006-03-21 Interdigital Technology Corporation Wireless communication method and system with controlled WTRU peer-to-peer communications
US7366981B2 (en) 2002-10-04 2008-04-29 Fuji Xerox Co., Ltd. Image forming device and method
CN1489332A (en) 2002-10-10 2004-04-14 �Ҵ���˾ Safety system and method for providing service device of identifying long-distance callin user's service-charge
US20040073476A1 (en) 2002-10-10 2004-04-15 Prolink Services Llc Method and system for identifying key opinion leaders
CN1527232A (en) 2002-10-16 2004-09-08 �ֹ��� Method ad apparatus for realizing distribution preset service, automatic supply maintenance and irrelevant service implementation with equipment
US20040075675A1 (en) 2002-10-17 2004-04-22 Tommi Raivisto Apparatus and method for accessing services via a mobile terminal
US6999092B2 (en) 2002-10-25 2006-02-14 Fujitsu Limited Image display apparatus in which a specific area display attribute is modifiable
SE0203188D0 (en) 2002-10-29 2002-10-29 Ericsson Telefon Ab L M Automatic provisioning including MMS greeting
US7650416B2 (en) 2003-08-12 2010-01-19 Riverbed Technology Content delivery for client-server protocols with user affinities using connection end-point proxies
MXPA05004765A (en) 2002-11-04 2005-08-02 Research In Motion Ltd Method and system for maintaining a wireless data connection.
US7809384B2 (en) 2002-11-05 2010-10-05 Microsoft Corporation User-input scheduling of synchronization operation on a mobile device based on user activity
US7263086B2 (en) 2002-11-12 2007-08-28 Nokia Corporation Method and system for providing location-based services in multiple coverage area environments
GB0226596D0 (en) 2002-11-14 2002-12-24 Commtag Ltd Data communication systems
CA2506585A1 (en) 2002-11-18 2004-06-03 Valerie Kucharewski People lists
ATE369684T1 (en) 2002-11-25 2007-08-15 T Mobile Deutschland Gmbh METHOD AND SYSTEM FOR SIMPLIFYING ACCESS TO AN EMAIL ACCOUNT VIA A MOBILE NETWORK
US6867774B1 (en) 2002-12-02 2005-03-15 Ngrain (Canada) Corporation Method and apparatus for transforming polygon data to voxel data for general purpose applications
US20040107319A1 (en) 2002-12-03 2004-06-03 D'orto David M. Cache management system and method
US7797064B2 (en) 2002-12-13 2010-09-14 Stephen Loomis Apparatus and method for skipping songs without delay
US7526800B2 (en) 2003-02-28 2009-04-28 Novell, Inc. Administration of protection of data accessible by a mobile device
US7308689B2 (en) 2002-12-18 2007-12-11 International Business Machines Corporation Method, apparatus, and program for associating related heterogeneous events in an event handler
DE10259755A1 (en) 2002-12-19 2004-07-08 Bt Ingnite Gmbh & Co Automatic terminal or user identification in networks
US7130424B2 (en) 2002-12-19 2006-10-31 Qualcomm, Inc. Systems and methods for utilizing an application from a native portable device within a non-native communications network
US7949759B2 (en) 2003-04-02 2011-05-24 AOL, Inc. Degrees of separation for handling communications
US7917468B2 (en) 2005-08-01 2011-03-29 Seven Networks, Inc. Linking of personal information management data
US7853563B2 (en) 2005-08-01 2010-12-14 Seven Networks, Inc. Universal data aggregation
US8468126B2 (en) 2005-08-01 2013-06-18 Seven Networks, Inc. Publishing data in an information community
US7272830B2 (en) 2003-01-16 2007-09-18 Sun Microsystems, Inc. Ordering program data for loading on a device
US7752301B1 (en) 2003-01-23 2010-07-06 Gomez Acquisition Corporation System and interface for monitoring information technology assets
US20040176128A1 (en) 2003-01-30 2004-09-09 3Com Corporation System, mobile communications unit, and softswitch method and apparatus for establishing an Internet Protocol communication link
US7210121B2 (en) 2003-02-07 2007-04-24 Sun Microsystems, Inc. Method and system for generating first class citizen application implementing native software application wrapper
US20040167966A1 (en) 2003-02-21 2004-08-26 Simon Lee Method and system for directing communications in a communications network
AU2003900772A0 (en) 2003-02-21 2003-03-13 Canon Kabushiki Kaisha Reducing the number of compositing operations performed in a pixel sequential rendering system
GB2398968B (en) 2003-02-27 2005-07-27 Motorola Inc Reduction in signalling load in a wireless communication system
US7672439B2 (en) 2003-04-02 2010-03-02 Aol Inc. Concatenated audio messages
US7644166B2 (en) 2003-03-03 2010-01-05 Aol Llc Source audio identifiers for digital communications
US20040177369A1 (en) 2003-03-06 2004-09-09 Akins Glendon L. Conditional access personal video recorder
US7881745B1 (en) 2003-03-10 2011-02-01 Hewlett-Packard Development Company, L.P. Electronic device network employing provisioning techniques to update firmware and/or software in electronic devices
US7310729B2 (en) 2003-03-12 2007-12-18 Limelight Networks, Inc. Digital rights management license delivery system and method
US20040181550A1 (en) 2003-03-13 2004-09-16 Ville Warsta System and method for efficient adaptation of multimedia message content
US7388947B2 (en) 2003-03-14 2008-06-17 Federal Bureau Of Investigation, The United States Of America As Represented By The Office Of The General Counsel Controllable telecommunications switch reporting compatible with voice grade lines
CA2519360A1 (en) 2003-03-17 2004-09-30 Spector & Associates, Inc Apparatus and method for broadcasting messages to selected group(s) of users
US7801092B2 (en) 2003-03-21 2010-09-21 Cisco Technology, Inc. Method for a simple 802.11e HCF implementation
US7613776B1 (en) 2003-03-26 2009-11-03 Aol Llc Identifying and using identities deemed to be known to a user
US6995749B2 (en) 2003-03-28 2006-02-07 Good Technology, Inc. Auto font magnification mechanism
EP2811679A1 (en) 2003-03-31 2014-12-10 Apple Inc. A radio telecommunications system and method of operating the same with polling
WO2004092956A1 (en) 2003-04-02 2004-10-28 Pathfire, Inc. Cascading key encryption
JP2004312413A (en) 2003-04-08 2004-11-04 Sony Corp Content providing server, information processing device and method, and computer program
TWI254564B (en) 2003-04-11 2006-05-01 Far Eastone Telecomm Co Ltd Multimedia message servicing method capable of inquiring downloading information and structure thereof
KR20040094275A (en) 2003-04-30 2004-11-09 삼성전자주식회사 Call setup method for push-to-talk service in cellular mobile telecommunications system
WO2004107099A2 (en) 2003-04-30 2004-12-09 Disney Enterprises, Inc. Cell phone multimedia controller
US20050015432A1 (en) 2003-05-13 2005-01-20 Cohen Hunter C. Deriving contact information from emails
US7100821B2 (en) 2003-05-15 2006-09-05 Mehran Randall Rasti Charge card and debit transactions using a variable charge number
GB2402297B (en) 2003-05-15 2005-08-17 Sun Microsystems Inc Update dependency control for multi-master replication
EP1664990A2 (en) 2003-05-19 2006-06-07 Modular Computing & Communications Corporation Apparatus and method for mobile personal computing and communications
DE60314601T2 (en) 2003-05-30 2008-02-28 Research In Motion Ltd., Waterloo System and method for providing service for a communication device
US7447909B2 (en) 2003-06-05 2008-11-04 Nortel Networks Limited Method and system for lawful interception of packet switched network services
US20040252816A1 (en) 2003-06-13 2004-12-16 Christophe Nicolas Mobile phone sample survey method
JP2006527439A (en) 2003-06-13 2006-11-30 ユニヴァーシティ オブ ランカスター User interface
US7069308B2 (en) 2003-06-16 2006-06-27 Friendster, Inc. System, method and apparatus for connecting users in an online computer system based on their relationships within social networks
US20040260948A1 (en) 2003-06-23 2004-12-23 Tatsuhiko Miyata Server and control method for managing permission setting of personal information disclosure
US7937091B2 (en) 2003-06-25 2011-05-03 Ntt Docomo, Inc. Method and apparatus for resource sharing over handset terminals
US20040266364A1 (en) 2003-06-27 2004-12-30 Nguyen Bach L. Method and apparatus for customization of a user interface
US7532571B1 (en) 2003-06-27 2009-05-12 Microsoft Corporation Providing online connectivity across a range of electronic communications systems
US20040264396A1 (en) 2003-06-30 2004-12-30 Boris Ginzburg Method for power saving in a wireless LAN
US7448080B2 (en) 2003-06-30 2008-11-04 Nokia, Inc. Method for implementing secure corporate communication
US7392249B1 (en) 2003-07-01 2008-06-24 Microsoft Corporation Methods, systems, and computer-readable mediums for providing persisting and continuously updating search folders
NL1023861C2 (en) 2003-07-08 2005-03-14 Pieter Gerard Maclaine Pont System and method for an electronic election.
EP1652368B1 (en) 2003-07-14 2018-04-04 Cisco Technology, Inc. System and method for active mobile collaboration
GB0316531D0 (en) 2003-07-15 2003-08-20 Transitive Ltd Method and apparatus for performing native binding
WO2005010715A2 (en) 2003-07-21 2005-02-03 Fusionone, Inc. Device message management system
US7382879B1 (en) 2003-07-23 2008-06-03 Sprint Communications Company, L.P. Digital rights management negotiation for streaming media over a network
US7676802B2 (en) 2003-07-23 2010-03-09 Nokia Corporation System, and associated method, for downloading an application
JP2005044277A (en) 2003-07-25 2005-02-17 Fuji Xerox Co Ltd Unauthorized communication detection device
US7349968B2 (en) 2003-07-31 2008-03-25 International Business Machines Corporation Method, system and program product for asynchronously processing requests
EP1652395A2 (en) 2003-07-31 2006-05-03 Koninklijke KPN N.V. A method and system to enable email services for mobile devices
US6973299B2 (en) 2003-08-01 2005-12-06 Microsoft Corporation Unified contact list
US8200775B2 (en) 2005-02-01 2012-06-12 Newsilike Media Group, Inc Enhanced syndication
US7111047B2 (en) 2003-08-08 2006-09-19 Teamon Systems, Inc. Communications system providing message aggregation features and related methods
US7373386B2 (en) 2003-08-11 2008-05-13 Research In Motion Limited System and method for configuring access to electronic mailboxes
US20050037741A1 (en) 2003-08-12 2005-02-17 Siemens Information And Communication Networks, Inc. System and method for telephonic presence via e-mail and short message service
WO2005027485A1 (en) 2003-09-12 2005-03-24 Nokia Corporation Method and device for handling missed calls in a mobile communications environment
US7519042B2 (en) 2003-09-12 2009-04-14 Motorola, Inc. Apparatus and method for mixed-media call formatting
EP1517566B1 (en) 2003-09-16 2006-07-19 Research In Motion Limited Demand-based update provisioning for a mobile communication device
GB0321674D0 (en) 2003-09-16 2003-10-15 Cognima Ltd Catching content on phones
US7634558B1 (en) 2003-09-22 2009-12-15 Sprint Spectrum L.P. Method and system for updating network presence records at a rate dependent on network load
WO2005033872A2 (en) 2003-09-29 2005-04-14 Multilogic Systems, Llc System and method for overcoming decision making and communicattons errors to produce expedited and accurate group choices
US7346168B2 (en) 2003-09-29 2008-03-18 Avaya Technology Corp. Method and apparatus for secure wireless delivery of converged services
AU2004281059A1 (en) 2003-10-03 2005-04-21 Limelight Networks, Inc. Rich content download
US7324473B2 (en) 2003-10-07 2008-01-29 Accenture Global Services Gmbh Connector gateway
US7239877B2 (en) 2003-10-07 2007-07-03 Accenture Global Services Gmbh Mobile provisioning tool system
US7457872B2 (en) 2003-10-15 2008-11-25 Microsoft Corporation On-line service/application monitoring and reporting system
KR100625338B1 (en) 2003-10-16 2006-09-20 주식회사 모빌리언스 Method for approving electric payment using the short message service including url call back and system for implementing the same
US7792988B2 (en) 2003-10-20 2010-09-07 Sony Computer Entertainment America, LLC Peer-to-peer data relay
US20050120084A1 (en) 2003-10-28 2005-06-02 Yu Hu Method of and system for creating, maintaining, and utilizing an online universal address book
EP1528824A1 (en) 2003-10-30 2005-05-04 Hewlett-Packard Development Company, L.P. Improvements in or relating to the establishment of packet-based communications
US8185838B2 (en) 2003-11-03 2012-05-22 Bomers Florian U Universal computer input event translator
US7962575B2 (en) 2003-11-03 2011-06-14 Grape Technology Group, Inc. System and method for data synchronization between devices
WO2005046272A1 (en) 2003-11-06 2005-05-19 Intuwave Limited Secure multi-entity access to resources on mobile telephones
US7634509B2 (en) 2003-11-07 2009-12-15 Fusionone, Inc. Personal information space management system and method
US7080104B2 (en) 2003-11-07 2006-07-18 Plaxo, Inc. Synchronization and merge engines
EP1530169A1 (en) 2003-11-10 2005-05-11 Alcatel Method for performing a voting by mobile terminals
US7356572B2 (en) 2003-11-10 2008-04-08 Yahoo! Inc. Method, apparatus and system for providing a server agent for a mobile device
WO2005050625A2 (en) 2003-11-14 2005-06-02 Senvid, Inc. Managed peer-to-peer applications in a secure network
US7760744B1 (en) 2003-11-20 2010-07-20 Juniper Networks, Inc. Media path optimization for multimedia over internet protocol
US7072678B2 (en) 2003-11-20 2006-07-04 Tekelec Methods and systems for triggerless mobile group dialing
KR100585748B1 (en) 2003-11-27 2006-06-07 엘지전자 주식회사 Synchronization method and system for telephone number
US7076608B2 (en) 2003-12-02 2006-07-11 Oracle International Corp. Invalidating cached data using secondary keys
US7119810B2 (en) 2003-12-05 2006-10-10 Siemens Medical Solutions Usa, Inc. Graphics processing unit for simulation or medical diagnostic imaging
US20050124332A1 (en) 2003-12-08 2005-06-09 Clark David R. Mobile device programming system and method
US7305252B2 (en) 2003-12-09 2007-12-04 Nokia Corporation System and method for service naming and related directory structure in a mobile data network
US7774411B2 (en) 2003-12-12 2010-08-10 Wisys Technology Foundation, Inc. Secure electronic message transport protocol
US20050165909A1 (en) 2003-12-19 2005-07-28 Cromer Daryl C. Data processing system and method for permitting a server to remotely access asset information of a mobile client
US20050147130A1 (en) 2003-12-23 2005-07-07 Intel Corporation Priority based synchronization of data in a personal area network
US8010670B2 (en) 2003-12-23 2011-08-30 Slipstream Data Inc. Meta-data based method for local cache utilization
GB2409787B (en) 2003-12-29 2007-10-03 Nokia Corp A communications system
US7181228B2 (en) 2003-12-31 2007-02-20 Corporation For National Research Initiatives System and method for establishing and monitoring the relative location of group members
US7707573B1 (en) 2003-12-31 2010-04-27 Google Inc. Systems and methods for providing and installing software
US7614052B2 (en) 2004-01-09 2009-11-03 Nexaweb Technologies Inc. System and method for developing and deploying computer applications over a network
JP2005196600A (en) 2004-01-09 2005-07-21 Hitachi Ltd Presence data management method
US8281079B2 (en) 2004-01-13 2012-10-02 Hewlett-Packard Development Company, L.P. Multi-processor system receiving input from a pre-fetch buffer
US8112103B2 (en) 2004-01-16 2012-02-07 Kuang-Chao Eric Yeh Methods and systems for mobile device messaging
US7184753B2 (en) 2004-01-22 2007-02-27 Research In Motion Limited Mailbox pooling pre-empting criteria
JP2005209106A (en) 2004-01-26 2005-08-04 Nec Corp Portable communication terminal, received e-mail management method, program and recording medium
US7526768B2 (en) 2004-02-04 2009-04-28 Microsoft Corporation Cross-pollination of multiple sync sources
US7877605B2 (en) 2004-02-06 2011-01-25 Fujitsu Limited Opinion registering application for a universal pervasive transaction framework
US7194273B2 (en) 2004-02-12 2007-03-20 Lucent Technologies Inc. Location based service restrictions for mobile applications
US20050183143A1 (en) 2004-02-13 2005-08-18 Anderholm Eric J. Methods and systems for monitoring user, application or device activity
US7374099B2 (en) 2004-02-24 2008-05-20 Sun Microsystems, Inc. Method and apparatus for processing an application identifier from a smart card
US7140549B2 (en) 2004-02-24 2006-11-28 Sun Microsystems, Inc. Method and apparatus for selecting a desired application on a smart card
US7165727B2 (en) 2004-02-24 2007-01-23 Sun Microsystems, Inc. Method and apparatus for installing an application onto a smart card
US20050210104A1 (en) 2004-03-19 2005-09-22 Marko Torvinen Method and system for presence enhanced group management and communication
CA2562352C (en) 2004-04-09 2014-03-25 Telecom Italia S.P.A. Method, apparatus and communications network for managing electronic mail services
JP2005301908A (en) 2004-04-15 2005-10-27 Toshiba Corp Information apparatus remote control system
FI20045138A0 (en) 2004-04-16 2004-04-16 Nokia Corp Group information management
US7664814B2 (en) 2004-04-20 2010-02-16 Microsoft Corporation Presence-based seamless messaging
US7830832B2 (en) 2004-04-20 2010-11-09 Pine Valley Investments, Inc. Distributed voting system and method for land mobile radio system
US7259666B1 (en) 2004-04-30 2007-08-21 Sprint Communications Company L.P. Method and system for displaying status indications from communications network
US7372450B2 (en) 2004-05-05 2008-05-13 Inventec Appliances Corporation Analog input mapping for hand-held computing devices
EP1759521B1 (en) 2004-05-12 2016-06-29 Synchronoss Technologies, Inc. Advanced contact identification system
US20050273804A1 (en) 2004-05-12 2005-12-08 Showtime Networks Inc. Animated interactive polling system, method, and computer program product
US9356712B2 (en) 2004-05-14 2016-05-31 Vibes Media Llc Method and system for displaying data
US7465231B2 (en) 2004-05-20 2008-12-16 Gametap Llc Systems and methods for delivering content over a network
US7558799B2 (en) 2004-06-01 2009-07-07 Microsoft Corporation Method, system, and apparatus for discovering and connecting to data sources
US7103432B2 (en) 2004-06-02 2006-09-05 Research In Motion Limited Auto-configuration of hardware on a portable computing device
US7469125B2 (en) 2004-06-17 2008-12-23 Nokia Corporation Enhanced method of transferring data from a data originating device to a mobile terminal
TWI260137B (en) 2004-06-23 2006-08-11 High Tech Comp Corp Method for wireless network establishment between devices and apparatus thereof
US7295853B2 (en) 2004-06-30 2007-11-13 Research In Motion Limited Methods and apparatus for the immediate acceptance and queuing of voice data for PTT communications
US8073960B2 (en) 2004-07-01 2011-12-06 Nokia Corporation Arranging management operations in management system
NO323527B1 (en) 2004-07-01 2007-06-04 Tandberg Telecom As Monitoring and control of management systems
US7809381B2 (en) 2004-07-16 2010-10-05 Bridgeport Networks, Inc. Presence detection for cellular and internet protocol telephony
US7734927B2 (en) 2004-07-21 2010-06-08 International Business Machines Corporation Real-time voting based authorization in an autonomic workflow process using an electronic messaging system
US8341172B2 (en) 2004-07-22 2012-12-25 International Business Machines Corporation Method and system for providing aggregate data access
CN101199187A (en) 2004-07-23 2008-06-11 茨特里克斯系统公司 A method and systems for securing remote access to private networks
EP1622009A1 (en) 2004-07-27 2006-02-01 Texas Instruments Incorporated JSM architecture and systems
US9143380B2 (en) 2004-08-06 2015-09-22 Nokia Technologies Oy System and method for third party specified generation of web server content
US7412657B2 (en) 2004-08-26 2008-08-12 International Business Machines Corporation Systems, methods, and media for updating an instant messaging system
US20060047844A1 (en) 2004-08-30 2006-03-02 Li Deng One step approach to deliver multimedia from local PC to mobile devices
US7422115B2 (en) 2004-09-07 2008-09-09 Iconix, Inc. Techniques for to defeat phishing
US7962569B2 (en) 2004-09-08 2011-06-14 Cradlepoint, Inc. Embedded DNS
US20060069746A1 (en) 2004-09-08 2006-03-30 Davis Franklin A System and method for smart persistent cache
US7587482B2 (en) 2004-09-08 2009-09-08 Yahoo! Inc. Multimodal interface for mobile messaging
US7599347B2 (en) 2004-09-16 2009-10-06 Research In Motion Limited System and method for allocating session initiation protocol (SIP) identifications (IDs) to user agents
US7657277B2 (en) 2004-09-24 2010-02-02 Qualcomm Incorporated Method and system for power control in a communication system
US8112548B2 (en) 2004-09-28 2012-02-07 Yahoo! Inc. Method for providing a clip for viewing at a remote device
US7437509B2 (en) 2004-09-29 2008-10-14 Sap Ag Mobile adaptive cache
US9307577B2 (en) 2005-01-21 2016-04-05 The Invention Science Fund I, Llc User assistance
US9049212B2 (en) 2004-09-30 2015-06-02 International Business Machines Corporation Method, system, and computer program product for prefetching sync data and for edge caching sync data on a cellular device
US20060069686A1 (en) 2004-09-30 2006-03-30 Siemens Information And Communication Networks, Inc. System and method for predicting availability
US8010082B2 (en) 2004-10-20 2011-08-30 Seven Networks, Inc. Flexible billing architecture
US7441271B2 (en) 2004-10-20 2008-10-21 Seven Networks Method and apparatus for intercepting events in a communication system
US8090880B2 (en) 2006-11-09 2012-01-03 Microsoft Corporation Data consistency within a federation infrastructure
US7317927B2 (en) 2004-11-05 2008-01-08 Wirelesswerx International, Inc. Method and system to monitor persons utilizing wireless media
US7464136B2 (en) 2004-11-05 2008-12-09 Microsoft Corporation Integrated messaging domain name setup
US7026984B1 (en) 2004-11-08 2006-04-11 Cingular Wireless Ii, L.L.C. Intelligent utilization of resources in mobile devices
US20060099970A1 (en) 2004-11-10 2006-05-11 Morgan Scott D Method and system for providing a log of mobile station location requests
FI118288B (en) 2005-01-26 2007-09-14 Seven Networks Internat Oy Electronic mail conveyance method to mobile terminal, involves generating service activation code having identifier of mobile terminal, encryption and checksum information, and conveying it through secure channel to host system
FI119581B (en) 2004-11-22 2008-12-31 Seven Networks Internat Oy E-mail traffic to and from a mobile terminal
US7643818B2 (en) 2004-11-22 2010-01-05 Seven Networks, Inc. E-mail messaging to/from a mobile terminal
EP1815634B1 (en) 2004-11-22 2015-01-07 Seven Networks, Inc. Data security in a mobile e-mail service
US7706781B2 (en) 2004-11-22 2010-04-27 Seven Networks International Oy Data security in a mobile e-mail service
US20060112177A1 (en) 2004-11-24 2006-05-25 Microsoft Corporation Method and system for controlling access to presence information on a peer-to-peer basis
US7587608B2 (en) 2004-11-30 2009-09-08 Sap Ag Method and apparatus for storing data on the application layer in mobile devices
WO2006058967A1 (en) 2004-12-03 2006-06-08 Seven Networks International Oy Provisioning of e-mail settings for a mobile terminal
FI117152B (en) 2004-12-03 2006-06-30 Seven Networks Internat Oy E-mail service provisioning method for mobile terminal, involves using domain part and further parameters to generate new parameter set in list of setting parameter sets, if provisioning of e-mail service is successful
US20060123042A1 (en) 2004-12-07 2006-06-08 Micrsoft Corporation Block importance analysis to enhance browsing of web page search results
KR100638587B1 (en) 2004-12-16 2006-10-26 주식회사 팬택 Mobile phone and method for auto setting traffic data rate considering application attribute
US7362325B2 (en) 2004-12-21 2008-04-22 Qualcomm Incorporated 2D/3D line rendering using 3D rasterization algorithms
US7849031B2 (en) 2004-12-22 2010-12-07 Hntb Holdings Ltd. Optimizing traffic predictions and enhancing notifications
US20060141962A1 (en) 2004-12-23 2006-06-29 Sony Ericsson Mobile Communications Ab Selecting/acquiring desired multimedia content
US8561126B2 (en) 2004-12-29 2013-10-15 International Business Machines Corporation Automatic enforcement of obligations according to a data-handling policy
US7200390B1 (en) 2004-12-30 2007-04-03 Cellco Partnership Device software update transport and download
US20060253605A1 (en) 2004-12-30 2006-11-09 Prabakar Sundarrajan Systems and methods for providing integrated client-side acceleration techniques to access remote applications
US8799006B2 (en) 2004-12-30 2014-08-05 Cerner Innovation, Inc. System and methods for distributed analysis of patient records
GB2421827B (en) 2004-12-31 2010-04-14 Ibm Methods apparatus and computer programs for dynamic generation of forms
US8306831B2 (en) 2005-01-10 2012-11-06 International Business Machines Corporation Systems with message integration for data exchange, collection, monitoring and/or alerting
TWI293844B (en) 2005-01-11 2008-02-21 Ind Tech Res Inst A system and method for performing application layer service authentication and providing secure access to an application server
US20060161621A1 (en) 2005-01-15 2006-07-20 Outland Research, Llc System, method and computer program product for collaboration and synchronization of media content on a plurality of media players
US7716306B2 (en) 2005-01-25 2010-05-11 International Business Machines Corporation Data caching based on data contents
US20060184625A1 (en) 2005-01-31 2006-08-17 Nordvik Markus A Short query-based system and method for content searching
US20060179410A1 (en) 2005-02-07 2006-08-10 Nokia Corporation Terminal, method, server, and computer program product for switching buddy lists based on user profile
BRPI0500426A (en) 2005-02-11 2006-09-26 Ricardo Capucio Borges ptec - technological process for creating and conducting collaborative events
US20060190569A1 (en) 2005-02-22 2006-08-24 Nextair Corporation Facilitating mobile device awareness of the availability of new or updated server-side applications
US8260852B1 (en) 2005-03-02 2012-09-04 Google Inc. Methods and apparatuses for polls
US7957271B2 (en) 2005-03-09 2011-06-07 International Business Machines Corporation Using mobile traffic history to minimize transmission time
US7752633B1 (en) 2005-03-14 2010-07-06 Seven Networks, Inc. Cross-platform event engine
US20060252435A1 (en) 2005-03-18 2006-11-09 Yahoo! Inc. Enabling application wakeup on a mobile device with a hybrid client
US7596608B2 (en) 2005-03-18 2009-09-29 Liveprocess Corporation Networked emergency management system
US20060223593A1 (en) 2005-04-01 2006-10-05 Ixi Mobile (R&D) Ltd. Content delivery system and method for a mobile communication device
MX2007011984A (en) 2005-04-01 2008-04-10 Multiplied Media Corp Multi-mode location based e-directory service enabling method, system, and apparatus.
US7461071B2 (en) 2005-04-04 2008-12-02 Younite, Inc. Distributed management framework for personal attributes
US20060242320A1 (en) 2005-04-21 2006-10-26 Paul Nettle Method and apparatus for polling
US20060242137A1 (en) 2005-04-21 2006-10-26 Microsoft Corporation Full text search of schematized data
US7796742B1 (en) 2005-04-21 2010-09-14 Seven Networks, Inc. Systems and methods for simplified provisioning
US7694008B2 (en) 2005-05-04 2010-04-06 Venturi Wireless Method and apparatus for increasing performance of HTTP over long-latency links
US7653648B2 (en) 2005-05-06 2010-01-26 Microsoft Corporation Permissions using a namespace
US20060259923A1 (en) 2005-05-12 2006-11-16 Fu-Sheng Chiu Interactive multimedia interface display
US8020110B2 (en) 2005-05-26 2011-09-13 Weisermazars Llp Methods for defining queries, generating query results and displaying same
US20060277271A1 (en) 2005-06-07 2006-12-07 Yahoo! Inc. Prefetching content based on a mobile user profile
NZ540853A (en) 2005-06-17 2006-12-22 Eftol Internat Ltd Online payment system for merchants using a virtual terminal in the form of a pin pad
WO2006136660A1 (en) 2005-06-21 2006-12-28 Seven Networks International Oy Maintaining an ip connection in a mobile network
US7673055B2 (en) 2005-06-23 2010-03-02 Research In Motion Limited System and method for automatically responding to a received communication
US7593714B2 (en) 2005-06-24 2009-09-22 Motorola, Inc. Communication services payment method and system
US20060294223A1 (en) 2005-06-24 2006-12-28 Microsoft Corporation Pre-fetching and DNS resolution of hyperlinked content
US7933395B1 (en) 2005-06-27 2011-04-26 Google Inc. Virtual tour of user-defined paths in a geographic information system
US20060294071A1 (en) 2005-06-28 2006-12-28 Microsoft Corporation Facet extraction and user feedback for ranking improvement and personalization
US20070005738A1 (en) 2005-06-29 2007-01-04 Microsoft Corporation Automated remote scanning of a network for managed and unmanaged devices
US8688790B2 (en) 2005-07-01 2014-04-01 Email2 Scp Solutions Inc. Secure electronic mail system with for your eyes only features
JP4371272B2 (en) 2005-07-04 2009-11-25 ソニー・エリクソン・モバイルコミュニケーションズ株式会社 Portable terminal device, content distribution system, and content reproduction program
CA2513018A1 (en) 2005-07-22 2007-01-22 Research In Motion Limited Method for training a proxy server for content delivery based on communication of state information from a mobile device browser
US7548969B2 (en) 2005-07-27 2009-06-16 Hewlett-Packard Development Company, L.P. Computer system polling with adjustable intervals based on rules and server states
US8214450B2 (en) 2005-08-01 2012-07-03 Limelight Networks, Inc. Dynamic bandwidth allocation
US8069166B2 (en) 2005-08-01 2011-11-29 Seven Networks, Inc. Managing user-to-user contact with inferred presence information
US9286388B2 (en) 2005-08-04 2016-03-15 Time Warner Cable Enterprises Llc Method and apparatus for context-specific content delivery
US8731542B2 (en) 2005-08-11 2014-05-20 Seven Networks International Oy Dynamic adjustment of keep-alive message intervals in a mobile network
US7925973B2 (en) 2005-08-12 2011-04-12 Brightcove, Inc. Distribution of content
US20070049258A1 (en) 2005-08-30 2007-03-01 Jason Thibeault System and method of mobile to desktop document interaction using really simple syndication
GB0517585D0 (en) 2005-08-30 2005-10-05 Ramakrishna Madhusudana Intuitive search which delivers fast results on the mobile phone
CA2517526A1 (en) 2005-08-30 2007-02-28 Oz Communications Method and system for communicating message notifications to mobile devices
GB2445688A (en) 2005-09-01 2008-07-16 Zvi Haim Lev System and method for reliable content access using a cellular/wireless device with imaging capabilities
US20080214148A1 (en) 2005-11-05 2008-09-04 Jorey Ramer Targeting mobile sponsored content within a social network
US20070060196A1 (en) 2005-09-14 2007-03-15 Lucent Technologies Inc. Call delivery between networks serving a dual mode wireless communication device
US20070067381A1 (en) 2005-09-19 2007-03-22 The Sco Group, Inc. Systems and methods for providing distributed applications and services for intelligent mobile devices
US8121069B2 (en) 2005-09-27 2012-02-21 Research In Motion Limited Adaptive data delivery
US7715825B2 (en) 2005-09-28 2010-05-11 Research In Motion Limited Pushback methods and apparatus for use in communicating messages to mobile communication devices
US20070078857A1 (en) 2005-09-30 2007-04-05 Nokia Corporation Method and a device for browsing information feeds
US20070264993A1 (en) 2005-10-04 2007-11-15 Hughes Bryan G Method, apparatus and article for opinion polling
US20070130217A1 (en) 2005-10-13 2007-06-07 Unwired Software, Inc. Many to many data synchronization
US20070088852A1 (en) 2005-10-17 2007-04-19 Zohar Levkovitz Device, system and method of presentation of advertisements on a wireless device
US7693555B2 (en) 2005-10-21 2010-04-06 Intel Corporation Sleep-mode wireless cell reselection apparatus, systems, and methods
US20070116223A1 (en) 2005-10-28 2007-05-24 Burke Paul M Telephony and web services coordination
GB0522079D0 (en) 2005-10-29 2005-12-07 Griffin Ian Mobile game or program distribution
US7853590B2 (en) 2005-12-02 2010-12-14 Microsoft Corporation Remote read-write access to disparate data stores
GB0526029D0 (en) 2005-12-21 2006-02-01 Nokia Corp Managing connections in a wireless communications network
US20070150881A1 (en) 2005-12-22 2007-06-28 Motorola, Inc. Method and system for run-time cache logging
US7889732B2 (en) 2005-12-22 2011-02-15 Alcatel-Lucent Usa, Inc. Method for converting between unicast sessions and a multicast session
US20070147317A1 (en) 2005-12-23 2007-06-28 Motorola, Inc. Method and system for providing differentiated network service in WLAN
US7716180B2 (en) 2005-12-29 2010-05-11 Amazon Technologies, Inc. Distributed storage system with web services client interface
KR20070071858A (en) 2005-12-30 2007-07-04 브이케이 주식회사 Submenu display method of mobile phone
GB0602523D0 (en) 2006-01-05 2006-03-22 Redburn Consulting Ltd Community messaging system
KR20070078238A (en) 2006-01-26 2007-07-31 에스케이 텔레콤주식회사 Multimedia contents transmitting method and system in communication network
US9479604B2 (en) 2006-01-30 2016-10-25 Qualcomm Incorporated System and method for dynamic phone book and network content links in a mobile device
US7925243B2 (en) 2006-02-14 2011-04-12 Mcgary Faith System and method for providing mobile device services using SMS communications
US8620994B2 (en) 2006-02-23 2013-12-31 Qualcomm Incorporated System and method for scheduling content updates in a content-based application
US7769395B2 (en) 2006-06-20 2010-08-03 Seven Networks, Inc. Location-based operations and messaging
US20070220080A1 (en) 2006-03-01 2007-09-20 Sean Humphrey Method, system, and computer program product for downloading medical awareness objects on communication devices
BRPI0708569B1 (en) 2006-03-07 2019-08-20 Thomson Licensing PORTABLE COMMUNICATION DEVICE AND ADAPTED BASE TO COMMUNICATE WITH A PORTABLE COMMUNICATION DEVICE
US20090248794A1 (en) 2008-03-26 2009-10-01 Time Warner Cable Inc System and method for content sharing
US20070245010A1 (en) 2006-03-24 2007-10-18 Robert Arn Systems and methods for multi-perspective optimization of data transfers in heterogeneous networks such as the internet
US7769805B1 (en) 2006-03-31 2010-08-03 Spring Communications Company L.P. Mobile device catalog and caching and architecture
US20080242370A1 (en) 2006-03-31 2008-10-02 Ixi Mobile (R&D) Ltd. Efficient server polling system and method
US20070233855A1 (en) 2006-04-03 2007-10-04 International Business Machines Corporation Adaptible keepalive for enterprise extenders
KR101166272B1 (en) 2006-04-13 2012-07-17 엘지전자 주식회사 The apparatus and method for channel management of mobile communication terminal
US9028329B2 (en) 2006-04-13 2015-05-12 Igt Integrating remotely-hosted and locally rendered content on a gaming device
US20080201751A1 (en) 2006-04-18 2008-08-21 Sherjil Ahmed Wireless Media Transmission Systems and Methods
US20070249365A1 (en) 2006-04-20 2007-10-25 Sony Ericsson Mobile Communications Ab Device, method and computer program for connecting a mobile device to a wireless network
US8015245B2 (en) 2006-04-24 2011-09-06 Microsoft Corporation Personalized information communications
US7937361B2 (en) 2006-04-28 2011-05-03 Research In Motion Limited Method of reflecting on another device a change to a browser cache on a handheld electronic device, and associated device
US8280982B2 (en) 2006-05-24 2012-10-02 Time Warner Cable Inc. Personal content server apparatus and methods
US9386327B2 (en) 2006-05-24 2016-07-05 Time Warner Cable Enterprises Llc Secondary content insertion apparatus and methods
KR100791628B1 (en) 2006-06-09 2008-01-04 고려대학교 산학협력단 Method for active controlling cache in mobile network system, Recording medium and System thereof
US20070288469A1 (en) 2006-06-12 2007-12-13 Research In Motion Limited System and method for mixed mode delivery of dynamic content to a mobile device
US7921116B2 (en) 2006-06-16 2011-04-05 Microsoft Corporation Highly meaningful multimedia metadata creation and associations
US8028335B2 (en) 2006-06-19 2011-09-27 Microsoft Corporation Protected environments for protecting users against undesirable activities
WO2007149526A2 (en) 2006-06-20 2007-12-27 Seven Networks, Inc. Group management and messaging
US20080001717A1 (en) 2006-06-20 2008-01-03 Trevor Fiatal System and method for group management
US20070290787A1 (en) 2006-06-20 2007-12-20 Trevor Fiatal Systems and methods for group messaging
US7995034B2 (en) 2006-06-22 2011-08-09 Microsoft Corporation Input device having a presence sensor
US7805489B2 (en) 2006-06-27 2010-09-28 Research In Motion Limited Electronic mail communications system with client email internet service provider (ISP) polling application and related methods
US7760641B2 (en) 2006-07-10 2010-07-20 International Business Machines Corporation Distributed traffic shaping across a cluster
US7720082B2 (en) 2006-07-13 2010-05-18 Neustar, Inc. System and method for short message service and instant messaging continuity
US8874780B2 (en) 2006-07-17 2014-10-28 Qualcomm Incorporated Data buffering and notification system and methods thereof
US20080077506A1 (en) 2006-07-28 2008-03-27 Alastair Rampell Methods and systems for providing a user interface for an alternative payment platform
US8295862B2 (en) 2006-08-03 2012-10-23 Telibrahma Convergent Communications Pvt Ltd Method and system to enable communication through SMS communication channel
US9336323B2 (en) 2006-08-04 2016-05-10 Flash Networks, Inc. Method and system for accelerating surfing the internet
US7689664B2 (en) 2006-08-10 2010-03-30 Sony Ericsson Mobile Communications Ab System and method for installing and configuring software applications on a mobile networked terminal
US7996487B2 (en) 2006-08-23 2011-08-09 Oracle International Corporation Managing searches on mobile devices
KR100765238B1 (en) 2006-08-24 2007-10-09 엘지전자 주식회사 Method for obtaining dns information of mobile terminal and mobile terminal thereof
US8261256B1 (en) 2006-08-24 2012-09-04 Bby Solutions, Inc. System and method for automatically updating the software of a networked personal audiovisual device
US20080059308A1 (en) 2006-09-02 2008-03-06 David Gerken Methods and apparatus for using poll results to target and/or select advertisements
US20080103877A1 (en) 2006-09-02 2008-05-01 David Gerken Methods and apparatus for soliciting, tracking, aggregating, reporting opinions and/or poll results
JP2008065546A (en) 2006-09-06 2008-03-21 Sony Computer Entertainment Inc Data transfer system, data transfer device, file format conversion device and data transfer method
GB0617732D0 (en) 2006-09-08 2006-10-18 Supercom Resources Ltd Intelligent message receiving method and apparatus
US7789305B2 (en) 2006-09-08 2010-09-07 At&T Intellectual Property I, L.P. System and method of voting via an interactive television system
US8467775B2 (en) 2006-09-12 2013-06-18 Ubiquity Holdings Digital data compression in a cellular phone
US8682340B2 (en) 2006-10-05 2014-03-25 Blackberry Limited Data retrieval method for location based services on a wireless device
US8126475B2 (en) 2006-10-09 2012-02-28 Motorola Mobility, Inc. Apparatus and method for uplink scheduling on shared channels
US8849896B2 (en) 2006-10-16 2014-09-30 Nokia Corporation Dynamic polling control for content distribution
US8555335B2 (en) 2006-11-01 2013-10-08 Microsoft Corporation Securing distributed application information delivery
US20080108298A1 (en) 2006-11-07 2008-05-08 Selen Mats A Certified two way source initiated transfer
WO2008061042A2 (en) 2006-11-10 2008-05-22 Pelago, Inc. Managing aggregation and sending of communications
KR20080043134A (en) 2006-11-13 2008-05-16 삼성전자주식회사 Method and system for setting a session between converged ip messaging service client and short messaging service client
WO2008060573A2 (en) 2006-11-14 2008-05-22 Grape Technology Group Inc. System and method for providing a search portal with enhanced results
WO2008067335A2 (en) 2006-11-27 2008-06-05 Smobile Systems, Inc. Wireless intrusion prevention system and method
US20080125225A1 (en) 2006-11-28 2008-05-29 Giannis Anastasios Lazaridis Multiplayer voting game and method for conducting a multiplayer voting game
US7778792B2 (en) 2006-12-08 2010-08-17 Chumby Industries, Inc. Systems and methods for location, motion, and contact detection and tracking in a networked audiovisual device
US8671021B2 (en) 2006-12-13 2014-03-11 Quickplay Media Inc. Consumption profile for mobile media
US8537659B2 (en) 2006-12-20 2013-09-17 Apple Inc. Method and system for reducing service interruptions to mobile communication devices
US8938765B2 (en) 2006-12-22 2015-01-20 Time Warner Cable Enterprises Llc Methods, apparatus and user interface for providing content on demand
US20080154870A1 (en) 2006-12-26 2008-06-26 Voice Signal Technologies, Inc. Collection and use of side information in voice-mediated mobile search
US7684346B2 (en) 2006-12-29 2010-03-23 Nokia Corporation Communications control for extending the period over which a terminal is able to have an open connection with a host accessible via a packet data network
US20090012841A1 (en) 2007-01-05 2009-01-08 Yahoo! Inc. Event communication platform for mobile device users
US20070167178A1 (en) 2007-01-07 2007-07-19 Al-Harbi Mansour A Short Message Service (SMS) Parser
US9100500B2 (en) 2007-01-08 2015-08-04 Qualcomm Incorporated Methods and systems of providing local access number calling features
US7987471B2 (en) 2007-01-26 2011-07-26 Microsoft Corporation Mobile device management proxy system
US20100118190A1 (en) 2007-02-06 2010-05-13 Mobixell Networks Converting images to moving picture format
US9270944B2 (en) 2007-02-14 2016-02-23 Time Warner Cable Enterprises Llc Methods and apparatus for content delivery notification and management
US8181206B2 (en) 2007-02-28 2012-05-15 Time Warner Cable Inc. Personal content server apparatus and methods
US8543141B2 (en) 2007-03-09 2013-09-24 Sony Corporation Portable communication device and method for media-enhanced messaging
US7584294B2 (en) * 2007-03-12 2009-09-01 Citrix Systems, Inc. Systems and methods for prefetching objects for caching using QOS
US7783757B2 (en) * 2007-03-12 2010-08-24 Citrix Systems, Inc. Systems and methods of revalidating cached objects in parallel with request for object
US7809818B2 (en) * 2007-03-12 2010-10-05 Citrix Systems, Inc. Systems and method of using HTTP head command for prefetching
KR20080085513A (en) 2007-03-20 2008-09-24 삼성전자주식회사 Home network control apparatus, home network system using it and control method thereof
US7916676B2 (en) 2007-03-23 2011-03-29 Broadcom Corporation Method and system for holistic energy management in ethernet networks
US20100228863A1 (en) 2007-03-28 2010-09-09 Pioneer Corporation Content distribution system and its control method
US7809841B1 (en) 2007-03-29 2010-10-05 Trading Technologies International, Inc. System and method for communicating with an electronic exchange in an electronic trading environment
US8451809B2 (en) 2007-04-13 2013-05-28 Hart Communication Foundation Wireless gateway in a process control environment supporting a wireless communication protocol
US7908656B1 (en) 2007-04-23 2011-03-15 Network Appliance, Inc. Customized data generating data storage system filter for data security
US8134970B2 (en) 2007-05-04 2012-03-13 Wichorus Inc. Method and system for transmitting content in a wireless communication network
US8060486B2 (en) 2007-05-07 2011-11-15 Hewlett-Packard Development Company, L.P. Automatic conversion schema for cached web requests
US8805425B2 (en) 2007-06-01 2014-08-12 Seven Networks, Inc. Integrated messaging
US20080301300A1 (en) 2007-06-01 2008-12-04 Microsoft Corporation Predictive asynchronous web pre-fetch
US8693494B2 (en) 2007-06-01 2014-04-08 Seven Networks, Inc. Polling
WO2008149337A2 (en) 2007-06-05 2008-12-11 Dcf Technologies Ltd. Devices for providing distributable middleware data proxy between application servers and database servers
CA2687883C (en) 2007-06-19 2014-07-08 Qualcomm Incorporated Methods and apparatus for dataset synchronization in a wireless environment
US20090010259A1 (en) 2007-07-08 2009-01-08 Alexander Sirotkin Device, system, and method of classification of communication traffic
US8065484B2 (en) 2007-07-19 2011-11-22 Oracle International Corporation Enhanced access to data available in a cache
CN100591020C (en) 2007-08-22 2010-02-17 华为技术有限公司 Multimedia business implementing system, method and relevant device
US7957335B2 (en) 2007-08-23 2011-06-07 Cisco Technology, Inc. Dynamic power usage management based on historical traffic pattern data for network devices
CN101378544B (en) 2007-08-31 2011-12-07 国际商业机器公司 Method, device and system for polling information
US7979645B2 (en) 2007-09-14 2011-07-12 Ricoh Company, Limited Multiprocessor system for memory mapping of processing nodes
SE532199C2 (en) 2007-09-21 2009-11-10 Sreg Internat Ab Procedure and system for backup and recovery of computer and user information
US9071859B2 (en) 2007-09-26 2015-06-30 Time Warner Cable Enterprises Llc Methods and apparatus for user-based targeted content delivery
US7729366B2 (en) 2007-10-03 2010-06-01 General Instrument Corporation Method, apparatus and system for network mobility of a mobile communication device
US8364181B2 (en) 2007-12-10 2013-01-29 Seven Networks, Inc. Electronic-mail filtering for mobile devices
US8149241B2 (en) 2007-12-10 2012-04-03 International Business Machines Corporation Arrangements for controlling activities of an avatar
US8793305B2 (en) 2007-12-13 2014-07-29 Seven Networks, Inc. Content delivery to a mobile device from a content service
US9002828B2 (en) 2007-12-13 2015-04-07 Seven Networks, Inc. Predictive content delivery
WO2009085586A1 (en) 2007-12-20 2009-07-09 Motorola, Inc. Method and system for managing search results in a communication network
US7921167B2 (en) 2007-12-21 2011-04-05 Kaushal Shroff Virtual electronic card based networking
US20090172565A1 (en) 2007-12-26 2009-07-02 John Clarke Jackson Systems, Devices, and Methods for Sharing Content
US7899996B1 (en) 2007-12-31 2011-03-01 Emc Corporation Full track read for adaptive pre-fetching of data
US8107921B2 (en) 2008-01-11 2012-01-31 Seven Networks, Inc. Mobile virtual network operator
KR101510099B1 (en) 2008-01-11 2015-04-08 삼성전자주식회사 Method for displaying three dimension menu haiving multiple layer in digital image processing apparatus
US9354068B2 (en) 2008-01-14 2016-05-31 Blackberry Limited System and method for dynamically downloading and displaying map data
US8862657B2 (en) 2008-01-25 2014-10-14 Seven Networks, Inc. Policy based content service
US20090193338A1 (en) 2008-01-28 2009-07-30 Trevor Fiatal Reducing network and battery consumption during content delivery and playback
US20090228545A1 (en) 2008-03-07 2009-09-10 Mendez Jose A Online mobile applications capable of dealing with occasional disconnects
US8099505B2 (en) 2008-03-26 2012-01-17 Microsoft Corporation Aggregating connection maintenance to optimize resource consumption
US8019863B2 (en) 2008-03-28 2011-09-13 Ianywhere Solutions, Inc. Synchronizing events between mobile devices and servers
US20090248670A1 (en) 2008-03-31 2009-10-01 Trevor Fiatal Content search engine
US20090248696A1 (en) 2008-03-31 2009-10-01 David Rowles Method and system for detecting restricted content associated with retrieved content
US8725679B2 (en) * 2008-04-07 2014-05-13 International Business Machines Corporation Client side caching of synchronized data
US8520589B2 (en) 2008-05-19 2013-08-27 Motorola Mobility Llc Mobile device and method for intelligently communicating data generated thereby over short-range, unlicensed wireless networks and wide area wireless networks
US20090299817A1 (en) 2008-06-03 2009-12-03 Qualcomm Incorporated Marketing and advertising framework for a wireless device
US8787947B2 (en) 2008-06-18 2014-07-22 Seven Networks, Inc. Application discovery on mobile devices
US8078158B2 (en) 2008-06-26 2011-12-13 Seven Networks, Inc. Provisioning applications for a mobile device
US8112475B2 (en) 2008-06-27 2012-02-07 Microsoft Corporation Managing data delivery based on device state
US8677018B2 (en) 2008-08-25 2014-03-18 Google Inc. Parallel, side-effect based DNS pre-caching
US20100057924A1 (en) 2008-09-02 2010-03-04 Qualcomm Incorporated Access point for improved content delivery system
US9521625B2 (en) 2008-09-15 2016-12-13 Apple Inc. Electronic devices for receiving pushed data
US20100077035A1 (en) 2008-09-23 2010-03-25 Nokia Corporation Optimized Polling in Low Resource Devices
US7966410B2 (en) 2008-09-25 2011-06-21 Microsoft Corporation Coordinating data delivery using time suggestions
US20100083255A1 (en) 2008-09-26 2010-04-01 Microsoft Corporation Notification batching based on user state
US8594627B2 (en) 2008-10-06 2013-11-26 Telecommunications Systems, Inc. Remotely provisioned wirelessly proxy
EP2175627A1 (en) 2008-10-09 2010-04-14 Sony Corporation Wireless transfer of data from a mobile device to a server
US8909759B2 (en) 2008-10-10 2014-12-09 Seven Networks, Inc. Bandwidth measurement
US9235704B2 (en) 2008-10-21 2016-01-12 Lookout, Inc. System and method for a scanning API
US9407694B2 (en) 2008-10-30 2016-08-02 Dell Products, Lp System and method of polling with an information handling system
US8694492B2 (en) 2008-11-03 2014-04-08 Telefonaktiebolaget Lm Ericsson (Publ) Pre-fetching of data in a mobile communications environment
US20100131617A1 (en) 2008-11-25 2010-05-27 John Osborne Method and system for differential transmission of web page structures
JP5168107B2 (en) 2008-11-26 2013-03-21 富士通株式会社 Relay server, information browsing system and program
KR20100064605A (en) * 2008-12-05 2010-06-15 에스케이커뮤니케이션즈 주식회사 Method and web server for managing connection
US7974194B2 (en) 2008-12-12 2011-07-05 Microsoft Corporation Optimizing data traffic and power consumption in mobile unified communication applications
US20100211651A1 (en) 2009-01-18 2010-08-19 Iskoot, Inc. Method and system for multimedia file transfer to a mobile device
US8769206B2 (en) 2009-01-20 2014-07-01 Oracle International Corporation Methods and systems for implementing transcendent page caching
KR101308679B1 (en) 2009-02-19 2013-09-13 주식회사 팬택 Special character input apparatus and method for a device had a touch screen
KR20100096347A (en) 2009-02-24 2010-09-02 주식회사 팬택 Method for random access process in mobile communication
US8194680B1 (en) 2009-03-11 2012-06-05 Amazon Technologies, Inc. Managing communications for modified computer networks
US20100250986A1 (en) 2009-03-27 2010-09-30 Motorola, Inc. Method and Device for Improving Battery Life of a Mobile Computing Device
US8275859B2 (en) 2009-03-31 2012-09-25 International Business Machines Corporation Selective partial updates of web content
US20100268757A1 (en) * 2009-04-17 2010-10-21 Google Inc. Pseudo Pipelining of Client Requests
US8769049B2 (en) 2009-04-24 2014-07-01 Microsoft Corporation Intelligent tiers of backup data
US8086803B2 (en) 2009-05-13 2011-12-27 International Business Machines Corporation Managing cache elements
JP4849351B2 (en) 2009-06-08 2012-01-11 ソニー株式会社 Image display control apparatus and method
US8549101B2 (en) 2009-06-16 2013-10-01 Oracle International Corporation Portable embedded local server for write-through cache
US9313800B2 (en) 2009-06-23 2016-04-12 Nokia Technologies Oy Method and apparatus for optimizing energy consumption for wireless connectivity
US8065419B2 (en) 2009-06-23 2011-11-22 Core Wireless Licensing S.A.R.L. Method and apparatus for a keep alive probe service
US8364611B2 (en) 2009-08-13 2013-01-29 Yahoo! Inc. System and method for precaching information on a mobile device
CN101998682A (en) 2009-08-27 2011-03-30 中兴通讯股份有限公司 Device and method for acquiring service content by personal network equipment and related device thereof
US8175584B2 (en) 2009-09-14 2012-05-08 Texas Instruments Incorporated System and method to facilitate downloading data at a mobile wireless device
US8549044B2 (en) 2009-09-17 2013-10-01 Ydreams—Informatica, S.A. Edificio Ydreams Range-centric contextual information systems and methods
US20110028129A1 (en) 2009-10-13 2011-02-03 Hutchison James W Proximity Triggered Profile-Based Wireless Matching
WO2011056557A2 (en) * 2009-10-26 2011-05-12 View2Gether Inc. System and method for providing a user terminal with supplemental information to a search result
US8782323B2 (en) 2009-10-30 2014-07-15 International Business Machines Corporation Data storage management using a distributed cache scheme
US8688907B2 (en) 2009-11-25 2014-04-01 Cleversafe, Inc. Large scale subscription based dispersed storage network
US8769156B2 (en) 2009-12-23 2014-07-01 Citrix Systems, Inc. Systems and methods for maintaining transparent end to end cache redirection
US8228832B2 (en) 2010-01-25 2012-07-24 Motorola Mobility, Inc. USSD transport method and device
US9477531B2 (en) 2010-01-27 2016-10-25 Vmware, Inc. Accessing virtual disk content of a virtual machine without running a virtual desktop
US8949988B2 (en) 2010-02-26 2015-02-03 Juniper Networks, Inc. Methods for proactively securing a web application and apparatuses thereof
TW201209697A (en) 2010-03-30 2012-03-01 Michael Luna 3D mobile user interface with configurable workspace management
US10002202B2 (en) * 2010-05-28 2018-06-19 Microsoft Technology Licensing, Llc Realtime websites with publication and subscription
US8527993B2 (en) 2010-06-01 2013-09-03 Qualcomm Incorporated Tasking system interface methods and apparatuses for use in wireless devices
US8725915B2 (en) 2010-06-01 2014-05-13 Qualcomm Incorporated Virtual buffer interface methods and apparatuses for use in wireless devices
US20130086228A1 (en) * 2010-06-11 2013-04-04 Hewlett-Packard Development Company, L.P. Http-based client-server communication system and method
US8954515B2 (en) 2010-06-30 2015-02-10 Alcatel Lucent Method and apparatus for reducing application update traffic in cellular networks
US9183590B2 (en) * 2010-07-20 2015-11-10 Neopost Technologies System and method for managing postal accounting data using transient data collectors
CA2806549C (en) 2010-07-26 2014-10-28 Seven Networks, Inc. Context aware traffic management for resource conservation in a wireless network
US9077630B2 (en) 2010-07-26 2015-07-07 Seven Networks, Inc. Distributed implementation of dynamic wireless traffic policy
US8838783B2 (en) 2010-07-26 2014-09-16 Seven Networks, Inc. Distributed caching for resource and mobile network traffic management
US9043433B2 (en) 2010-07-26 2015-05-26 Seven Networks, Inc. Mobile network traffic coordination across multiple applications
CA2857458A1 (en) 2010-07-26 2012-02-09 Michael Luna Mobile application traffic optimization
CA2806529C (en) 2010-07-26 2014-12-09 Seven Networks, Inc. Prediction of activity session for mobile network use optimization and user experience enhancement
US8762450B2 (en) 2010-07-27 2014-06-24 Qualcomm Incorporated Apparatus and method for reducing frequent server messages
US8938800B2 (en) 2010-07-28 2015-01-20 Mcafee, Inc. System and method for network level protection against malicious software
US9413558B2 (en) 2010-08-31 2016-08-09 Hewlett-Packard Development Company, L.P. Communicating between electronic devices using a portable storage device
US8806486B2 (en) * 2010-09-03 2014-08-12 Time Warner Cable Enterprises, Llc. Methods and systems for managing a virtual data center with embedded roles based access control
US8510374B2 (en) 2010-09-24 2013-08-13 Microsoft Corporation Polling protocol for automatic load limiting
US9521174B2 (en) * 2010-10-19 2016-12-13 Paul Matthew Davidge Video script interpreter platform with cooperating client and server
US8458413B2 (en) 2010-10-27 2013-06-04 International Business Machines Corporation Supporting virtual input/output (I/O) server (VIOS) active memory sharing in a cluster environment
US8190701B2 (en) 2010-11-01 2012-05-29 Seven Networks, Inc. Cache defeat detection and caching of content addressed by identifiers intended to defeat cache
US8843153B2 (en) 2010-11-01 2014-09-23 Seven Networks, Inc. Mobile traffic categorization and policy for network use optimization while preserving user experience
WO2012060995A2 (en) 2010-11-01 2012-05-10 Michael Luna Distributed caching in a wireless network of content delivered for a mobile application over a long-held request
US8484314B2 (en) 2010-11-01 2013-07-09 Seven Networks, Inc. Distributed caching in a wireless network of content delivered for a mobile application over a long-held request
US8166164B1 (en) 2010-11-01 2012-04-24 Seven Networks, Inc. Application and network-based long poll request detection and cacheability assessment therefor
GB2499534B (en) 2010-11-01 2018-09-19 Seven Networks Llc Caching adapted for mobile application behavior and network conditions
WO2012061430A2 (en) 2010-11-01 2012-05-10 Michael Luna Distributed management of keep-alive message signaling for mobile network resource conservation and optimization
US8819060B2 (en) 2010-11-19 2014-08-26 Salesforce.Com, Inc. Virtual objects in an on-demand database environment
GB2500327B (en) 2010-11-22 2019-11-06 Seven Networks Llc Optimization of resource polling intervals to satisfy mobile device requests
CN103404193B (en) 2010-11-22 2018-06-05 七网络有限责任公司 The connection that adjustment data transmission is established with the transmission being optimized for through wireless network
US20120158837A1 (en) 2010-12-15 2012-06-21 Research In Motion Limited Method and system for establishing a notification service for a device
KR20120076859A (en) 2010-12-30 2012-07-10 삼성전자주식회사 Method and apparatus for synchronizing keep alive packet in a portable terminal
US20120174220A1 (en) 2010-12-31 2012-07-05 Verisign, Inc. Detecting and mitigating denial of service attacks
US9325662B2 (en) 2011-01-07 2016-04-26 Seven Networks, Llc System and method for reduction of mobile network traffic used for domain name system (DNS) queries
US8634809B1 (en) * 2011-05-02 2014-01-21 Time Warner Cable Enterprises Llc Methods and apparatus for communicating messages between mobile communications devices and internet enabled devices

Cited By (90)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8811952B2 (en) 2002-01-08 2014-08-19 Seven Networks, Inc. Mobile device power management in data synchronization over a mobile network with or without a trigger notification
US8549587B2 (en) 2002-01-08 2013-10-01 Seven Networks, Inc. Secure end-to-end transport through intermediary nodes
US9251193B2 (en) 2003-01-08 2016-02-02 Seven Networks, Llc Extending user relationships
USRE45348E1 (en) 2004-10-20 2015-01-20 Seven Networks, Inc. Method and apparatus for intercepting events in a communication system
US8805334B2 (en) 2004-11-22 2014-08-12 Seven Networks, Inc. Maintaining mobile terminal information for secure communications
US8873411B2 (en) 2004-12-03 2014-10-28 Seven Networks, Inc. Provisioning of e-mail settings for a mobile terminal
US8561086B2 (en) 2005-03-14 2013-10-15 Seven Networks, Inc. System and method for executing commands that are non-native to the native environment of a mobile device
US8839412B1 (en) 2005-04-21 2014-09-16 Seven Networks, Inc. Flexible real-time inbox access
US8438633B1 (en) 2005-04-21 2013-05-07 Seven Networks, Inc. Flexible real-time inbox access
US8761756B2 (en) 2005-06-21 2014-06-24 Seven Networks International Oy Maintaining an IP connection in a mobile network
US8412675B2 (en) 2005-08-01 2013-04-02 Seven Networks, Inc. Context aware data presentation
US8468126B2 (en) 2005-08-01 2013-06-18 Seven Networks, Inc. Publishing data in an information community
US9055102B2 (en) 2006-02-27 2015-06-09 Seven Networks, Inc. Location-based operations and messaging
US8693494B2 (en) 2007-06-01 2014-04-08 Seven Networks, Inc. Polling
US8805425B2 (en) 2007-06-01 2014-08-12 Seven Networks, Inc. Integrated messaging
US8774844B2 (en) 2007-06-01 2014-07-08 Seven Networks, Inc. Integrated messaging
US8364181B2 (en) 2007-12-10 2013-01-29 Seven Networks, Inc. Electronic-mail filtering for mobile devices
US8738050B2 (en) 2007-12-10 2014-05-27 Seven Networks, Inc. Electronic-mail filtering for mobile devices
US9002828B2 (en) 2007-12-13 2015-04-07 Seven Networks, Inc. Predictive content delivery
US8862657B2 (en) 2008-01-25 2014-10-14 Seven Networks, Inc. Policy based content service
US8849902B2 (en) 2008-01-25 2014-09-30 Seven Networks, Inc. System for providing policy based content service in a mobile network
US8799410B2 (en) 2008-01-28 2014-08-05 Seven Networks, Inc. System and method of a relay server for managing communications and notification between a mobile device and a web access server
US8838744B2 (en) 2008-01-28 2014-09-16 Seven Networks, Inc. Web-based access to data objects
US8787947B2 (en) 2008-06-18 2014-07-22 Seven Networks, Inc. Application discovery on mobile devices
US8494510B2 (en) 2008-06-26 2013-07-23 Seven Networks, Inc. Provisioning applications for a mobile device
US8909759B2 (en) 2008-10-10 2014-12-09 Seven Networks, Inc. Bandwidth measurement
US9049179B2 (en) 2010-07-26 2015-06-02 Seven Networks, Inc. Mobile network traffic coordination across multiple applications
US9043433B2 (en) 2010-07-26 2015-05-26 Seven Networks, Inc. Mobile network traffic coordination across multiple applications
US9077630B2 (en) 2010-07-26 2015-07-07 Seven Networks, Inc. Distributed implementation of dynamic wireless traffic policy
US9407713B2 (en) 2010-07-26 2016-08-02 Seven Networks, Llc Mobile application traffic optimization
US8838783B2 (en) 2010-07-26 2014-09-16 Seven Networks, Inc. Distributed caching for resource and mobile network traffic management
US8886176B2 (en) 2010-07-26 2014-11-11 Seven Networks, Inc. Mobile application traffic optimization
US8484314B2 (en) 2010-11-01 2013-07-09 Seven Networks, Inc. Distributed caching in a wireless network of content delivered for a mobile application over a long-held request
US9021048B2 (en) 2010-11-01 2015-04-28 Seven Networks, Inc. Caching adapted for mobile application behavior and network conditions
US8782222B2 (en) 2010-11-01 2014-07-15 Seven Networks Timing of keep-alive messages used in a system for mobile network resource conservation and optimization
US8843153B2 (en) 2010-11-01 2014-09-23 Seven Networks, Inc. Mobile traffic categorization and policy for network use optimization while preserving user experience
US8700728B2 (en) 2010-11-01 2014-04-15 Seven Networks, Inc. Cache defeat detection and caching of content addressed by identifiers intended to defeat cache
US9060032B2 (en) 2010-11-01 2015-06-16 Seven Networks, Inc. Selective data compression by a distributed traffic management system to reduce mobile data traffic and signaling traffic
US8966066B2 (en) 2010-11-01 2015-02-24 Seven Networks, Inc. Application and network-based long poll request detection and cacheability assessment therefor
US9275163B2 (en) 2010-11-01 2016-03-01 Seven Networks, Llc Request and response characteristics based adaptation of distributed caching in a mobile network
US9330196B2 (en) 2010-11-01 2016-05-03 Seven Networks, Llc Wireless traffic management system cache optimization using http headers
US8326985B2 (en) 2010-11-01 2012-12-04 Seven Networks, Inc. Distributed management of keep-alive message signaling for mobile network resource conservation and optimization
US8903954B2 (en) 2010-11-22 2014-12-02 Seven Networks, Inc. Optimization of resource polling intervals to satisfy mobile device requests
US8539040B2 (en) 2010-11-22 2013-09-17 Seven Networks, Inc. Mobile network background traffic data management with optimized polling intervals
US8417823B2 (en) 2010-11-22 2013-04-09 Seven Network, Inc. Aligning data transfer to optimize connections established for transmission over a wireless network
US9100873B2 (en) 2010-11-22 2015-08-04 Seven Networks, Inc. Mobile network background traffic data management
US9325662B2 (en) 2011-01-07 2016-04-26 Seven Networks, Llc System and method for reduction of mobile network traffic used for domain name system (DNS) queries
US8316098B2 (en) 2011-04-19 2012-11-20 Seven Networks Inc. Social caching for device resource sharing and management
US9300719B2 (en) 2011-04-19 2016-03-29 Seven Networks, Inc. System and method for a mobile device to use physical storage of another device for caching
US8356080B2 (en) 2011-04-19 2013-01-15 Seven Networks, Inc. System and method for a mobile device to use physical storage of another device for caching
US9084105B2 (en) 2011-04-19 2015-07-14 Seven Networks, Inc. Device resources sharing for network resource conservation
US8832228B2 (en) 2011-04-27 2014-09-09 Seven Networks, Inc. System and method for making requests on behalf of a mobile device based on atomic processes for mobile network traffic relief
US8635339B2 (en) * 2011-04-27 2014-01-21 Seven Networks, Inc. Cache state management on a mobile device to preserve user experience
US20120317370A1 (en) * 2011-04-27 2012-12-13 Seven Networks, Inc. Cache state management on a mobile device to preserve user experience
US20120290717A1 (en) * 2011-04-27 2012-11-15 Michael Luna Detecting and preserving state for satisfying application requests in a distributed proxy and cache system
US8621075B2 (en) * 2011-04-27 2013-12-31 Seven Metworks, Inc. Detecting and preserving state for satisfying application requests in a distributed proxy and cache system
US9239800B2 (en) 2011-07-27 2016-01-19 Seven Networks, Llc Automatic generation and distribution of policy information regarding malicious mobile traffic in a wireless network
US8984581B2 (en) 2011-07-27 2015-03-17 Seven Networks, Inc. Monitoring mobile application activities for malicious traffic on a mobile device
US10154153B2 (en) * 2011-11-10 2018-12-11 Microsoft Technology Licensing, Llc Application resource usage information
US20170289363A1 (en) * 2011-11-10 2017-10-05 Microsoft Technology Licensing, Llc Application resource usage information
US8977755B2 (en) 2011-12-06 2015-03-10 Seven Networks, Inc. Mobile device and method to utilize the failover mechanism for fault tolerance provided for mobile traffic management and network/device resource conservation
US8918503B2 (en) 2011-12-06 2014-12-23 Seven Networks, Inc. Optimization of mobile traffic directed to private networks and operator configurability thereof
US8868753B2 (en) 2011-12-06 2014-10-21 Seven Networks, Inc. System of redundantly clustered machines to provide failover mechanisms for mobile traffic management and network resource conservation
US9208123B2 (en) 2011-12-07 2015-12-08 Seven Networks, Llc Mobile device having content caching mechanisms integrated with a network operator for traffic alleviation in a wireless network and methods therefor
US9277443B2 (en) 2011-12-07 2016-03-01 Seven Networks, Llc Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol
US9009250B2 (en) 2011-12-07 2015-04-14 Seven Networks, Inc. Flexible and dynamic integration schemas of a traffic management system with various network operators for network traffic alleviation
US9173128B2 (en) 2011-12-07 2015-10-27 Seven Networks, Llc Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol
US9832095B2 (en) 2011-12-14 2017-11-28 Seven Networks, Llc Operation modes for mobile traffic optimization and concurrent management of optimized and non-optimized traffic
US9021021B2 (en) 2011-12-14 2015-04-28 Seven Networks, Inc. Mobile network reporting and usage analytics system and method aggregated using a distributed traffic optimization system
US8861354B2 (en) 2011-12-14 2014-10-14 Seven Networks, Inc. Hierarchies and categories for management and deployment of policies for distributed wireless traffic optimization
US9131397B2 (en) 2012-01-05 2015-09-08 Seven Networks, Inc. Managing cache to prevent overloading of a wireless network due to user activity
US8909202B2 (en) 2012-01-05 2014-12-09 Seven Networks, Inc. Detection and management of user interactions with foreground applications on a mobile device in distributed caching
US20140365576A1 (en) * 2012-01-26 2014-12-11 Ofer Eliassaf Identifying a push communication pattern
US11082510B2 (en) * 2012-01-26 2021-08-03 Micro Focus Llc Identifying a push communication pattern
US9203864B2 (en) 2012-02-02 2015-12-01 Seven Networks, Llc Dynamic categorization of applications for network access in a mobile network
US9326189B2 (en) 2012-02-03 2016-04-26 Seven Networks, Llc User as an end point for profiling and optimizing the delivery of content and data in a wireless network
US8812695B2 (en) 2012-04-09 2014-08-19 Seven Networks, Inc. Method and system for management of a virtual network connection without heartbeat messages
US10263899B2 (en) 2012-04-10 2019-04-16 Seven Networks, Llc 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
US8775631B2 (en) 2012-07-13 2014-07-08 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
US9161258B2 (en) 2012-10-24 2015-10-13 Seven Networks, Llc Optimized and selective management of policy deployment to mobile clients in a congested network to prevent further aggravation of network congestion
US9307493B2 (en) 2012-12-20 2016-04-05 Seven Networks, Llc Systems and methods for application management of mobile device radio state promotion and demotion
US9271238B2 (en) 2013-01-23 2016-02-23 Seven Networks, Llc Application or context aware fast dormancy
US9241314B2 (en) 2013-01-23 2016-01-19 Seven Networks, Llc Mobile device with application or context aware fast dormancy
US8874761B2 (en) 2013-01-25 2014-10-28 Seven Networks, Inc. Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols
US8750123B1 (en) 2013-03-11 2014-06-10 Seven Networks, Inc. Mobile device equipped with mobile network congestion recognition to make intelligent decisions regarding connecting to an operator network
US9065765B2 (en) 2013-07-22 2015-06-23 Seven Networks, Inc. Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network
US20170034211A1 (en) * 2015-07-27 2017-02-02 Swisscom Ag Systems and methods for identifying phishing websites
US10708302B2 (en) * 2015-07-27 2020-07-07 Swisscom Ag Systems and methods for identifying phishing web sites
US10735307B1 (en) * 2019-01-10 2020-08-04 Ebay Inc. Network latency measurement and analysis system
US11611502B2 (en) 2019-01-10 2023-03-21 Ebay Inc. Network latency measurement and analysis system

Also Published As

Publication number Publication date
US8166164B1 (en) 2012-04-24
US8291076B2 (en) 2012-10-16
US20120173616A1 (en) 2012-07-05
US8966066B2 (en) 2015-02-24
US20130041974A1 (en) 2013-02-14
WO2012060997A2 (en) 2012-05-10
WO2012060997A3 (en) 2012-07-19

Similar Documents

Publication Publication Date Title
US8966066B2 (en) Application and network-based long poll request detection and cacheability assessment therefor
US8484314B2 (en) Distributed caching in a wireless network of content delivered for a mobile application over a long-held request
US8965392B2 (en) Mobile traffic categorization and policy for network use optimization while preserving user experience
US9100873B2 (en) Mobile network background traffic data management
US9084105B2 (en) Device resources sharing for network resource conservation
US8782222B2 (en) Timing of keep-alive messages used in a system for mobile network resource conservation and optimization
US9275163B2 (en) Request and response characteristics based adaptation of distributed caching in a mobile network
US9208123B2 (en) Mobile device having content caching mechanisms integrated with a network operator for traffic alleviation in a wireless network and methods therefor
US8326985B2 (en) Distributed management of keep-alive message signaling for mobile network resource conservation and optimization
US8903954B2 (en) Optimization of resource polling intervals to satisfy mobile device requests
US8635339B2 (en) Cache state management on a mobile device to preserve user experience
US8832228B2 (en) System and method for making requests on behalf of a mobile device based on atomic processes for mobile network traffic relief

Legal Events

Date Code Title Description
AS Assignment

Owner name: SEVEN NETWORKS, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LUNA, MICHAEL;TSOMBALJUK, ANDREI;SIGNING DATES FROM 20111007 TO 20111009;REEL/FRAME:027067/0886

STCF Information on status: patent grant

Free format text: PATENTED CASE

FEPP Fee payment procedure

Free format text: PAT HOLDER NO LONGER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: STOL); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

AS Assignment

Owner name: SEVEN NETWORKS, LLC, CALIFORNIA

Free format text: ENTITY CONVERSION;ASSIGNOR:SEVEN NETWORKS, INC.;REEL/FRAME:036485/0059

Effective date: 20150714

FPAY Fee payment

Year of fee payment: 4

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

LAPS Lapse for failure to pay maintenance fees

Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20200424