Patent Description:
Lack of proper support has prompted a number of vendors to provide documents to guide their operator partners and independent software vendors to configure their networks and applications to perform better in WCDMA networks. This guidance focuses on: configuring networks to go to stay on high-power radio mode as short as possible and making periodic keep alive messages that are used to maintain an always-on TCP/IP connection as infrequent as possible. Such solutions typically assume lack of coordination between the user, the application and the network.

Furthermore, application protocols may provide long-lived connections that allow servers to push updated data to a mobile device without the need of the client to periodically re-establish the connection or to periodically query for changes. However, the mobile device needs to be sure that the connection remains usable by periodically sending some data, often called a keep-alive message, to the server and making sure the server is receiving this data. While the amount of data sent for a single keep-alive is not a lot and the keep-alive interval for an individual application is not too short, the cumulative effect of multiple applications performing this individually will amount to small pieces of data being sent very frequently. Frequently sending bursts of data in a wireless network also result in high battery consumption due to the constant need of powering/re-powering the radio module.

<CIT> describes managing power-consuming resources on a first computing device by time-based and condition-based scheduling of data delivery from a plurality of second computing devices. A scheduler executing on the first computing device has knowledge of recurrent schedules for activation by the second computing devices. The first computing device determines availability of the power-consuming resources and adjusts an activation time for the schedules to use the power-consuming resources when the resources are available. Managing the schedules associated with the second computing devices preserves battery life of the first computing device.

<CIT> describes a configurable interface for controlling data sent from a mobile device. This interface can include multiple, configurable options that permit a mobile device user to control how often outgoing data is sent from the device. These options can include: a push on schedule option, a push within a time counted from when outgoing data was queued for delivery option, a push on volume option, a push immediately option, an auto-adjusting push option, and a customized push option based upon a user-adjustable sliding scale between two competing considerations.

<CIT> describes a method of preloading data on a cache in a local machine. The cache is operably coupled to a data store, in a remote host machine. The method includes the steps of determining a user behaviour profile for the local machine; retrieving data relating to the user behaviour profile from the data store; and preloading the retrieved data in the cache, such that the data is made available to the cache user when desired. A local machine, a host machine, a cache, a communication system and preloading functions are also described. In this manner, data within the cache is maintained and replaced in a substantially optimal manner, and configured to be available to a cache user when it is predicted that the user wishes to access the data.

The invention relates to a mobile device, as further defined in claim <NUM>, and a method, as further defined in claim <NUM>, for efficiently managing application-based priorities by a user of a mobile device.

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. Similarly, various requirements are described which may be requirements for some embodiments but not other embodiments.

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. 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.

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.

Embodiments of the present disclosure include systems and methods for context aware traffic management for network and device resource conservation.

One embodiment of the disclosed technology includes, a system that optimizes multiple aspects of the connection with wired and wireless 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 <NUM>, namely LTE, <NUM>, 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. 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 which automatically detects recurring requests for the same content (RSS feed, Widget data set) that matches a specific rule (e.g. happens every <NUM> 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 device (e.g., a mobile phone, smart phone, etc.) does not need to open up (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, or otherwise different.

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 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.

<FIG> illustrates an example diagram of a system where a host server <NUM> facilitates management of traffic between client devices <NUM> and an application server or content provider <NUM> in a wireless network for resource conservation.

The client devices 102A-D 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 <NUM> and/or application server/content provider <NUM>. Client devices <NUM> will typically include a display and/or other output functionalities to present information and data exchanged between among the devices <NUM> and/or the host server <NUM> and/or application server/content provider <NUM>.

For example, the client devices <NUM> can include mobile, hand held or portable 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, etc. In one embodiment, the client devices <NUM>, host server <NUM>, and app server <NUM> are coupled via a network <NUM> and/or a network <NUM>. In some embodiments, the devices <NUM> and host server <NUM> may be directly connected to one another.

The input mechanism on client devices <NUM> 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 <NUM>-axis, <NUM>-axis, <NUM>-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 <NUM> 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 <NUM>. Context awareness at client devices <NUM> generally includes, by way of example but not limitation, client device <NUM> 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 <NUM> and/or Internet service providers) of the network <NUM> and/or network <NUM> (e.g., by the host server and/or devices <NUM>). In addition to application context awareness as determined from the client <NUM> side, the application context awareness may also be received from or obtained/queried from the respective application/service providers <NUM> (by the host <NUM> and/or client devices <NUM>).

The host server <NUM> can use, for example, contextual information obtained for client devices <NUM>, networks <NUM>/<NUM>, applications (e.g., mobile applications), application server/provider <NUM>, or any combination of the above, to manage the traffic in the system to satisfy data needs of the client devices <NUM> (e.g., to satisfy application or any other request including HTTP request). In one embodiment, the traffic is managed by the host server <NUM> to satisfy data requests made in response to explicit or non-explicit user <NUM> 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 <NUM> can manage and coordinate such traffic in the system such that use of device <NUM> 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 <NUM> 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 <NUM> behaviors. The device <NUM> can also request the host server <NUM> 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 <NUM> and client device <NUM>. The distributed system can include proxy server and cache components on the server <NUM> side and on the client <NUM> side, for example, as shown by the server cache <NUM> on the server <NUM> side and the local cache <NUM> on the client <NUM> side.

Functions and techniques disclosed for context aware traffic management for resource conservation in networks (e.g., network <NUM> and/or <NUM>) and devices <NUM>, reside in a distributed proxy and cache system. The proxy and cache system can be distributed between, and reside on, a given client device <NUM> in part or in whole and/or host server <NUM> in part or in whole. The distributed proxy and cache system are illustrated with further reference to the example diagram shown in <FIG>. Functions and techniques performed by the proxy and cache components in the client device <NUM>, the host server <NUM>, and the related components therein are described, respectively, in detail with further reference to the examples of <FIG><NUM>.

In one embodiment, client devices <NUM> communicate with the host server <NUM> and/or the application server <NUM> over network <NUM>, which can be a cellular network. To facilitate overall traffic management between devices <NUM> and various application servers/content providers <NUM> to implement network (bandwidth utilization) and device resource (e.g., battery consumption), the host server <NUM> can communicate with the application server/providers <NUM> over the network <NUM>, which can include the Internet.

In general, the networks <NUM> and/or <NUM>, over which the client devices <NUM>, the host server <NUM>, and/or application server <NUM> communicate, may be a cellular 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, Open System Interconnections (OSI), FTP, UPnP, iSCSI, NSF, ISDN, PDH, RS-<NUM>, SDH, SONET, etc. Open System Interconnections (OSI), FTP, UPnP, iSCSI, NSF, ISDN, PDH, RS-<NUM>, SDH, SONET, etc..

The networks <NUM> and/or <NUM> can be any collection of distinct networks operating wholly or partially in conjunction to provide connectivity to the client devices <NUM> and the host server <NUM> and may appear as one or more networks to the serviced systems and devices. In one embodiment, communications to and from the client devices <NUM> can be achieved by, an open network, such as the Internet, or a private 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), enabled with technologies such as, by way of example, Global System for Mobile Communications (GSM), Personal Communications Service (PCS), Digital Advanced Mobile Phone Service (D-Amps), Bluetooth, Wi-Fi, Fixed Wireless Data, <NUM>, <NUM>, <NUM>, <NUM>, IMT-Advanced, pre-<NUM>, <NUM> LTE, 3GPP LTE, LTE Advanced, mobile WiMax, WiMax <NUM>, 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, USSD, IRC, or any other wireless data networks or messaging protocols.

<FIG> illustrates an example diagram of a proxy and cache system distributed between the host server <NUM> and device <NUM> which facilitates network traffic management between the device <NUM> and an application server/content provider <NUM> (e.g., a source server) for resource conservation.

The distributed proxy and cache system can include, for example, the proxy server <NUM> (e.g., remote proxy) and the server cache, <NUM> components on the server side. The server-side proxy <NUM> and cache <NUM> can, as illustrated, reside internal to the host server <NUM>. In addition, the proxy server <NUM> and cache <NUM> on the server-side can be partially or wholly external to the host server <NUM> and in communication via one or more of the networks <NUM> and <NUM>. For example, the proxy server <NUM> may be external to the host server and the server cache <NUM> may be maintained at the host server <NUM>. Alternatively, the proxy server <NUM> may be within the host server <NUM> while the server cache is external to the host server <NUM>. In addition, each of the proxy server <NUM> and the cache <NUM> may be partially internal to the host server <NUM> and partially external to the host server <NUM>.

The distributed system can also, include, in one embodiment, client-side components, including by way of example but not limitation, a local proxy <NUM> (e.g., a mobile client on a mobile device) and/or a local cache <NUM>, which can, as illustrated, reside internal to the device <NUM> (e.g., a mobile device).

In addition, the client-side proxy <NUM> and local cache <NUM> can be partially or wholly external to the device <NUM> and in communication via one or more of the networks <NUM> and <NUM>. For example, the local proxy <NUM> may be external to the device <NUM> and the local cache <NUM> may be maintained at the device <NUM>. Alternatively, the local proxy <NUM> may be within the device <NUM> while the local cache <NUM> is external to the device <NUM>. In addition, each of the proxy <NUM> and the cache <NUM> may be partially internal to the host server <NUM> and partially external to the host server <NUM>.

In one embodiment, the distributed system can include an optional caching proxy server <NUM>. The caching proxy server <NUM> can be a component which is operated by the application server/content provider <NUM>, the host server <NUM>, or a network service provider <NUM>, and or any combination of the above to facilitate network traffic management for network and device resource conservation. Proxy server <NUM> can be used, for example, for caching content to be provided to the device <NUM>, for example, from one or more of, the application server/provider <NUM>, host server <NUM>, and/or a network service provider <NUM>. Content caching can also be entirely or partially performed by the remote proxy <NUM> to satisfy application requests or other data requests at the device <NUM>.

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 <NUM> can be tracked by the local proxy <NUM> and communicated, over the network <NUM> to the proxy server <NUM> component in the host server <NUM>, for example, as connection metadata. The proxy server <NUM> which in turn is coupled to the application server/provider <NUM> provides content and data to satisfy requests made at the device <NUM>.

In addition, the local proxy <NUM> can identify and retrieve mobile device properties including, one or more of, battery level, network that the device is registered on, radio state, whether the mobile device is being used (e.g., interacted with by a user). In some instances, the local proxy <NUM> can delay, expedite (prefetch), and/or modify data prior to transmission to the proxy server <NUM>, when appropriate, as will be further detailed with references to the description associated with the examples of <FIG>.

The local database <NUM> can be included in the local proxy <NUM> or coupled to the proxy <NUM> 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 <NUM>. Locally cached responses can be used by the local proxy <NUM> to satisfy certain application requests of the mobile device <NUM>, by retrieving cached content stored in the cache storage <NUM>, when the cached content is still valid.

Similarly, the proxy server <NUM> of the host server <NUM> can also delay, expedite, or modify data from the local proxy prior to transmission to the content sources (e.g., the app server/content provider <NUM>). In addition, the proxy server <NUM> uses device properties and connection metadata to generate rules for satisfying request of applications on the mobile device <NUM>. The proxy server <NUM> can gather real time traffic information about requests of applications for later use in optimizing similar connections with the mobile device <NUM> or other mobile devices.

In general, the local proxy <NUM> and the proxy server <NUM> are transparent to the multiple applications executing on the mobile device. The local proxy <NUM> is generally transparent to the operating system or platform of the mobile device and may or may not be specific to device manufacturers. For example, he local proxy can be implemented without adding a TCP stack and thus act transparently to both the US and the mobile applications. In some instances, the local proxy <NUM> is optionally customizable in part or in whole to be device specific. In some embodiments, the local proxy <NUM> may be bundled into a wireless model, into a firewall, and/or a router.

In one embodiment, the host server <NUM> can in some instances, utilize the store and forward functions of a short message service center (SMSC) <NUM>, such as that provided by the network service provider <NUM>, in communicating with the device <NUM> in achieving network traffic management. As will be further described with reference to the example of <FIG>, the host server <NUM> can forward content or HTTP responses to the SMSC <NUM> such that it is automatically forwarded to the device <NUM> if available, and for subsequent forwarding if the device <NUM> 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 <NUM>, the local proxy <NUM> reduces the number of requests that need to be satisfied over the network <NUM>. Further, the local proxy <NUM> and the proxy server <NUM> may filter irrelevant data from the communicated data. In addition, the local proxy <NUM> and the proxy server <NUM> can also accumulate low priority data and send it in batches to avoid the protocol overhead of sending individual data fragments. The local proxy <NUM> and the proxy server <NUM> can also compress or transcode the traffic, reducing the amount of data sent over the network <NUM> and/or <NUM>. The signaling traffic in the network <NUM> and/or <NUM> 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 <NUM>, by serving application or content requests from the local cache <NUM>, the local proxy <NUM> can reduce the number of times the radio module is powered up. The local proxy <NUM> and the proxy server <NUM> 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 <NUM> can synchronize the network use by performing the batched data transfer for all connections simultaneously.

<FIG> depicts a block diagram illustrating an example of client-side components in a distributed proxy and cache system residing on a device <NUM> that manages traffic in a wireless network for resource conservation.

The device <NUM>, which can be a portable or mobile device, such as a portable phone, generally includes, for example, a network interface <NUM>, an operating system <NUM>, a context API <NUM>, and mobile applications which may be proxy unaware <NUM> or proxy aware <NUM>. Note that the device <NUM> is specifically illustrated in the example of <FIG> as a mobile device, such is not a limitation and that device <NUM> 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 <NUM> can be a networking module that enables the device <NUM> to mediate data in a network with an entity that is external to the host server <NUM>, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface <NUM> 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 <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, 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, bridge router, a hub, a digital media receiver, and/or a repeater.

Device <NUM> can further include, client-side components of the distributed proxy and cache system which can include, a local proxy <NUM> (e.g., a mobile client of a mobile device) and a cache <NUM>. In one embodiment, the local proxy <NUM> includes a user activity module <NUM>, a proxy API <NUM>, a request/transaction manager <NUM>, a caching policy manager <NUM>, a traffic shaping engine <NUM>, and/or a connection manager <NUM>. The traffic shaping engine <NUM> may further include an alignment module <NUM> and/or a batching module <NUM>, the connection manager <NUM> may further include a radio controller <NUM>. The request/transaction manager <NUM> can further include an application behavior detector <NUM> and/or a prioritization engine <NUM>, the application behavior detector <NUM> may further include a pattern detector <NUM> and/or and application profile generator <NUM>. Additional or less components/modules/engines can be included in the local proxy <NUM> and each illustrated component.

As used herein, a "module," "a manager," a "handler," a "detector," an "interface," 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, hander, or engine can be centralized or its functionality distributed. The module, manager, hander, 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 <NUM> U. <NUM>), 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 <NUM>, including local proxy <NUM> (mobile client) and/or cache <NUM>. The local proxy <NUM> can provide an interface on the device <NUM> for users to access device applications and services including email, IM, voice mail, visual voicemail, feeds, Internet, other applications, etc..

The proxy <NUM> is generally application independent and can be used by applications (e.g., both proxy aware and proxy-unaware mobile applications <NUM> and <NUM>) to open TCP connections to a remote server (e.g., the server <NUM> in the examples of <FIG> and/or server proxy <NUM>/<NUM> shown in the examples of <FIG> and <FIG>). In some instances, the local proxy <NUM> includes a proxy API <NUM> which can be optionally used to interface with proxy-aware applications <NUM> (or mobile applications on a mobile device).

The applications <NUM> and <NUM> 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 <NUM> includes or is coupled to a context API <NUM>, as shown. The context API <NUM> may be a part of the operating system <NUM> or device platform or independent of the operating system <NUM>, as illustrated. The operating system <NUM> 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 <NUM> Micro Edition (J2ME), Blackberry, etc..

The context API <NUM> may be a plug-in to the operating system <NUM> or a particular client application on the device <NUM>. The context API <NUM> 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 <NUM> can be coupled to input devices or sensors on the device <NUM> 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 <NUM> and/or collected from ambient signals/contextual cues detected at or in the vicinity of the device <NUM> (e.g., light, motion, piezoelectric, etc.).

In one embodiment, the user activity module <NUM> interacts with the context API <NUM> to identify, determine, infer, detect, compute, predict, and/or anticipate, characteristics of user activity on the device <NUM>. Various inputs collected by the context API <NUM> can be aggregated by the user activity module <NUM> to generate a profile for characteristics of user activity. Such a profile can be generated by the module <NUM> 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 <NUM> 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 <NUM>, or for a specific time period (e.g., for the last <NUM> hours, for the last <NUM> hours).

Additionally, characteristic profiles can be generated by the user activity module <NUM> to depict a historical trend for user activity and behavior (e.g. <NUM> week, <NUM> mo, <NUM> 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 <NUM> can detect and track user activity with respect to applications, documents, files, windows, icons, and folders on the device <NUM>. For example, the user activity module <NUM> can detect when an application or window (e.g., a web browser) 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 <NUM> can be used to locally adjust behavior of the device (e.g., mobile 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 <NUM> of the connection manager <NUM>) coupled to the user activity module <NUM>. For example, the radio controller <NUM> can turn the radio on or off, based on characteristics of the user activity on the device <NUM>. In addition, the radio controller <NUM> 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 <NUM> can also be used to cause another device (e.g., other computers, a mobile device, or a non-portable device) or server (e.g., host server <NUM> and <NUM> in the examples of <FIG> and <FIG>) which can communicate (e.g., via a cellular or other network) with the device <NUM> to modify its communication frequency with the device <NUM>. The local proxy <NUM> can use the characteristics information of user behavior determined by the user activity module <NUM> 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 <NUM> if new data, changed data, different data, or data of a certain level of importance becomes available, etc.).

In one embodiment, the user activity module <NUM> 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 <NUM> and <NUM> in the examples of <FIG> and <FIG>) send the data that was buffered as a result of the previously decreased communication frequency.

In addition, or in alternative, the local proxy <NUM> can communicate the characteristics of user activity at the device <NUM> to the remote device (e.g., host server <NUM> and <NUM> in the examples of <FIG> and <FIG>) and the remote device determines how to alter its own communication frequency with the device <NUM> for network resource conservation and conservation of device <NUM> resources.

One embodiment of the local proxy <NUM> further includes a request/transaction manager <NUM>, which can detect, identify, intercept, process, manage, data requests initiated on the device <NUM>, for example, by applications <NUM> and/or <NUM>, and/or directly/indirectly by a user request. The request/transaction manager <NUM> 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 <NUM> can prioritize requests or transactions made by applications and/or users at the device <NUM>, for example by the prioritization engine <NUM>. Importance or priority of requests/transactions can be determined by the manager <NUM> 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 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 request/requested transaction. For example, the connection manager <NUM>, can adjust the radio mode (e.g., high power or low power mode via the radio controller <NUM>) based on the amount of data that will need to be transferred.

In addition, the radio controller <NUM>/connection manager <NUM> can adjust the radio power mode (high or low) based on time criticality/sensitivity of the transaction. The radio controller <NUM> 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 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 <NUM> may include set of rules for assigning priority.

The priority engine <NUM> 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 LinkedIn 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 priority engine <NUM> 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 sync 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 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 <NUM>. 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 <NUM> days old,' then instead of powering on the device radio to initiate a message delete from the device <NUM> the moment that the message has exceeded <NUM> 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 <NUM>, can use the priorities for requests (e.g., by the prioritization engine <NUM>) to manage outgoing traffic from the device <NUM> 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 <NUM> if the radio is not already switched on, as controlled by the connection manager <NUM>. In contrast, the radio controller <NUM> 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 <NUM> or another device/entity) can be used cause a remote device to modify its communication with the frequency with the mobile device. For example, the remote device can be configured to send notifications to the device <NUM> when data of higher importance is available to be sent to the mobile 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 <NUM>. For example, the traffic shaping engine <NUM> can, in response to detecting that a user is dormant or inactive, wait to send low priority transactions from the device <NUM>, for a period of time. In addition, the traffic shaping engine <NUM> can allow multiple low priority transactions to accumulate for batch transferring from the device <NUM> (e.g., via the batching module <NUM>). 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 <NUM> and for example , used by the user to adjust or view the priorities.

The batching module <NUM> 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 <NUM> can initiate batch transfer of the cumulated low priority events when a higher priority event is initiated or detected at the device <NUM>. 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 <NUM> or <NUM>). 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 <NUM> locally adjusts radio use on the device <NUM> by caching data in the cache <NUM>. When requests or transactions from the device <NUM> can be satisfied by content stored in the cache <NUM>, the radio controller <NUM> need not activate the radio to send the request to a remote entity (e.g., the host server <NUM>, <NUM>, as shown in <FIG> and <FIG> or a content provider/application server such as the server/provider <NUM> shown in the examples of <FIG> and <FIG>). As such, the local proxy <NUM> can use the local cache <NUM> and the cache policy manager <NUM> 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 <NUM> intercepts a data request by an application on the device <NUM>, the local repository <NUM> 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 <NUM>, the response can be provided to the application on the device <NUM> without the device <NUM> needing to access the cellular network.

If a valid response is not available, the local proxy <NUM> can query a remote proxy (e.g., the server proxy <NUM> of <FIG>) 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 <NUM> or optional caching server <NUM> shown in the example of <FIG>) can be provided to the mobile device, possibly without the mobile device <NUM> 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 <NUM>, for example, the caching policy manager <NUM>, can send the data request to a remote proxy (e.g., server proxy <NUM> of <FIG>) which forwards the data request to a content source (e.g., application server/content provider <NUM> of <FIG>) 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 <NUM> of <FIG>. The cache policy manager <NUM> can manage or process requests that use a variety of protocols, including but not limited to HTTP, HTTPS, IMAP, POP, SMTP and/or ActiveSync. The caching policy manager <NUM> can locally store responses for data requests in the local database <NUM> as cache entries, for subsequent use in satisfying same or similar data requests. The manager <NUM> can request that the remote proxy monitor responses for the data request, and the remote proxy can notify the device <NUM> when an unexpected response to the data request is detected. In such an event, the cache policy manager <NUM> can erase or replace the locally stored response(s) on the device <NUM> when notified of the unexpected response (e.g., new data, changed data, additional data, different response, etc.) to the data request. In one embodiment, the caching policy manager <NUM> is able to detect or identify the protocol used for a specific request, including but not limited to HTTP, HTTPS, IMAP, POP, SMTP and/or ActiveSync. In one embodiment, application specific handlers (e.g., via the application protocol module <NUM> of the manager <NUM>) on the local proxy <NUM> 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 <NUM> in the example of <FIG>).

In one embodiment, the local proxy <NUM> 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 <NUM>, 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 <NUM> can simulate application server responses for applications on the device <NUM>, using locally cached content. This can prevent utilization of the cellular network for transactions where new/changed/different data is not available, thus freeing up network resources and preventing network congestion.

In one embodiment, the local proxy <NUM> includes an application behavior detector <NUM> to track, detect, observe, monitor, applications (e.g., proxy aware and/or unaware applications <NUM> and <NUM>) accessed or installed on the device <NUM>. Application behaviors, or patterns in detected behaviors (e.g., via the pattern detector <NUM>) of one or more applications accessed on the device <NUM> can be used by the local proxy <NUM> 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 <NUM> can align content requests made by at least some of the applications over the network (wireless network) (e.g., via the alignment module <NUM>). The alignment module can delay or expedite some earlier received requests to achieve alignment. When requests are aligned, the traffic shaping engine <NUM> 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.), mobile device parameters, and/or network parameters/traffic conditions, network service provider constraints/specifications, etc..

In one embodiment, the pattern detector <NUM> 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 <NUM> to offload polling of content from a content source (e.g., from an application server/content provider <NUM> of <FIG>) that would result from the application requests that would be performed at the mobile device <NUM> to be performed instead, by a proxy server (e.g., proxy server <NUM> of <FIG> or proxy server <NUM> of <FIG>) remote from the device <NUM>. Traffic engine <NUM> 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 <NUM> to establish a wireless (cellular) 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 <NUM> can be provided to satisfy data requests at the device <NUM>, 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, or when data is different, and/or new data has been received, the remote entity to which polling is offloaded, can notify the device <NUM>. The remote entity may be the host server <NUM> as shown in the example of <FIG>.

In one embodiment, the local proxy <NUM> 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 <NUM> in the local proxy (e.g., the heartbeat manager <NUM>) can detect, identify, and intercept any or all heartbeat (keep-alive) messages being sent from applications.

The heartbeat manager <NUM> 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>) to generate the and send the heartbeat messages to maintain a connection with the backend (e.g., app server/provider <NUM> in the example of <FIG>).

The local proxy <NUM> generally represents any one or a portion of the functions described for the individual managers, modules, and/or engines. The local proxy <NUM> and device <NUM> 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> depicts a block diagram illustrating an example of server-side components in a distributed proxy and cache system residing on a host server <NUM> that manages traffic in a wireless network for resource conservation.

The host server <NUM> generally includes, for example, a network interface <NUM> and/or one or more repositories <NUM>, <NUM>, <NUM>. Note that server <NUM> 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>) 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 <NUM> can include networking module(s) or devices(s) that enable the server <NUM> to mediate data in a network with an entity that is external to the host server <NUM>, through any known and/or convenient communications protocol supported by the host and the external entity. Specifically, the network interface <NUM> allows the server <NUM> to communicate with multiple devices including mobile phone devices <NUM>, and/or one or more application servers/content providers <NUM>.

The host server <NUM> can store information about connections (e.g., network characteristics, conditions, types of connections, etc.) with devices in the connection metadata repository <NUM>. Additionally, any information about third party application or content providers can also be stored in <NUM>. The host server <NUM> 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 <NUM>. Additionally, the host server <NUM> can store information about network providers and the various network service areas in the network service provider repository <NUM>.

The communication enabled by <NUM> allows for simultaneous connections (e.g., including cellular connections) with devices <NUM> and/or connections (e.g., including wired/wireless, HTTP, Internet connections, LAN, Wifi, etc.) with content servers/providers <NUM>, to manage the traffic between devices <NUM> and content providers <NUM>, for optimizing network resource utilization and/or to conserver power (battery) consumption on the serviced devices <NUM>. The host server <NUM> can communicate with mobile devices <NUM> serviced by different network service providers and/or in the same/different network service areas. The host server <NUM> can operate and is compatible with devices <NUM> with varying types or levels of mobile capabilities, including by way of example but not limitation, <NUM>, <NUM>, <NUM> transitional (<NUM>, <NUM>), <NUM> (IMT-<NUM>), <NUM> transitional (<NUM>, <NUM>, <NUM>), <NUM> (IMT-advanced), etc..

In general, the network interface <NUM> 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 <NUM>, <NUM>, <NUM>, <NUM>, <NUM> type networks such as , LTE, WiMAX, etc.,), Bluetooth, WiFi, or any other network whether or not connected via a a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.

The host server <NUM> can further include, server-side components of the distributed proxy and cache system which can include, a proxy server <NUM> and a server cache <NUM>. In one embodiment, the server proxy <NUM> can include an HTTP access engine <NUM>, a caching policy manager <NUM>, a proxy controller <NUM>, a traffic shaping engine <NUM>, a new data detector <NUM>, and/or a connection manager <NUM>.

The HTTP access engine <NUM> may further include a heartbeat manager <NUM>, the proxy controller <NUM> may further include a data invalidator module <NUM>, the traffic shaping engine <NUM> may further include a control protocol <NUM> and a batching module <NUM>. Additional or less components/modules/engines can be included in the proxy server <NUM> and each illustrated component.

As used herein, a "module," "a manager," a "handler," a "detector," an "interface," a "controller," 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, or engine can be centralized or its functionality distributed. The module, manager, handler, 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 <NUM> U. <NUM>), 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 <NUM>) making an application or content request to an app server or content provider <NUM>, the request may be intercepted and routed to the proxy server <NUM>, which is coupled to the device <NUM> and the provider <NUM>. Specifically, the proxy server is able to communicate with the local proxy (e.g., proxy <NUM> and <NUM> of the examples of <FIG> and <FIG> respectively) of the device <NUM>, the local proxy forwards the data request to the proxy server <NUM> for, in some instances, further processing, and if needed, for transmission to the content server <NUM> for a response to the data request.

In such a configuration, the host <NUM>, or the proxy server <NUM> in the host server <NUM> 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 <NUM> can identify characteristics of user activity on the device <NUM> to modify its communication frequency. The characteristics of user activity can be determined by, for example, the activity/behavior awareness module <NUM> in the proxy controller <NUM>, via information collected by the local proxy on the device <NUM>.

In one embodiment, communication frequency can be controlled by the connection manager <NUM> of the proxy server <NUM>, for example, to adjust push frequency of content or updates to the device <NUM>. For instance, push frequency can be decreased by the connection manager <NUM> 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 <NUM> can adjust the communication frequency with the device <NUM> to send data that was buffered as a result of decreased communication frequency, to the device <NUM>.

In addition, the proxy server <NUM> 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 <NUM> and provided to the proxy server <NUM>. The priority awareness module <NUM> of the proxy server <NUM> can generally assess the priority (e.g., including time-criticality, time-sensitivity, etc.) of various events or applications; additionally, the priority awareness module <NUM> can track priorities determined by local proxies of devices <NUM>.

In one embodiment, through priority awareness, the connection manager <NUM> can further modify communication frequency (e.g., use or radio as controlled by the radio controller <NUM>) of the server <NUM> with the devices <NUM>. For example, the server <NUM> can notify the device <NUM>, 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 <NUM> can detect multiple occurrences of events (e.g., transactions, content, data received from server/provider <NUM>) and allow the events to accumulate for batch transfer to device <NUM>. 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 <NUM> and/or <NUM>. For example, batch transfer of multiple events (of a lower priority) to the device <NUM> can be initiated by the batching module <NUM> when an event of a higher priority (meeting a threshold or criteria) is detected at the server <NUM>. In addition, batch transfer from the server <NUM> can be triggered when the server receives data from the device <NUM>, indicating that the device radio is already in use and is thus on. In one embodiment, the proxy server <NUM> 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 <NUM> caches data (e.g., as managed by the caching policy manager <NUM>) such that communication frequency over a network (e.g., cellular network) with the device <NUM> can be modified (e.g., decreased). The data can be cached, for example in the server cache <NUM>, for subsequent retrieval or batch sending to the device <NUM> to potentially decrease the need to turn on the device <NUM> radio. The server cache <NUM> can be partially or wholly internal to the host server <NUM>, although in the example of <FIG>, it is shown as being external to the host <NUM>. In some instances, the server cache <NUM> 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 <NUM> shown in the example of <FIG>), such as being managed by an application server/content provider <NUM>, a network service provider, or another third party.

In one embodiment, content caching is performed locally on the device <NUM> with the assistance of host server <NUM>. For example, proxy server <NUM> in the host server <NUM> can query the application server/provider <NUM> with requests and monitor changes in responses. When changed, different or new responses are detected (e.g., by the new data detector <NUM>), the proxy server <NUM> can notify the mobile device <NUM>, such that the local proxy on the device <NUM> 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 <NUM> can automatically instruct the local proxy of the device <NUM> to invalidate certain cached data, based on received responses from the app application server/provider <NUM>. The cached data is marked as invalid, and can get replaced or deleted when new content is received from the content server <NUM>.

Note that data change can be detected by the detector <NUM> in one or more ways. For example, the server/provider <NUM> can notify the host server <NUM> upon a change. The change can also be detected at the host server <NUM> in response to a direct poll of the source server/provider <NUM>. In some instances, the proxy server <NUM> can in addition, pre-load the local cache on the device <NUM> with the new/updated/changed/different data. This can be performed when the host server <NUM> detects that the radio on the mobile device is already in use, or when the server <NUM> has additional content/data to be sent to the device <NUM>.

One or more the above mechanisms can be implemented simultaneously or adjusted/configured based on application (e.g., different policies for different servers/providers <NUM>). In some instances, the source provider/server <NUM> may notify the host <NUM> for certain types of events (e.g., events meeting a priority threshold level). In addition, the provider/server <NUM> may be configured to notify the host <NUM> at specific time intervals, regardless of event priority.

In one embodiment, the proxy server <NUM> of the host <NUM> 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 <NUM> can instruct the proxy server <NUM> to perform such monitoring or the proxy server <NUM> 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 <NUM>, for example, through the activity/behavior awareness module <NUM>, is able to identify or detect user activity, at a device that is separate from the mobile device <NUM>. For example, the module <NUM> 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 <NUM> and may not need frequent updates, if at all.

The server <NUM>, in this instance, can thus decrease the frequency with which new, different, changed, or updated content is sent to the mobile device <NUM>, 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 <NUM>.

In one embodiment, the host server <NUM> is able to poll content sources <NUM> on behalf of devices <NUM> to conserve power or battery consumption on devices <NUM>. For example, certain applications on the mobile device <NUM> can poll its respective server <NUM> in a predictable recurring fashion. Such recurrence or other types of application behaviors can be tracked by the activity/behavior module <NUM> in the proxy controller <NUM>. The host server <NUM> can thus poll content sources <NUM> for applications on the mobile device <NUM>, that would otherwise be performed by the device <NUM> through a wireless (e.g., including cellular connectivity). The host server can poll the sources <NUM> for new, different, updated, or changed data by way of the HTTP access engine <NUM> to establish HTTP connection or by way of radio controller <NUM> to connect to the source <NUM> over the cellular network. When new, different, updated, or changed data is detected, the new data detector can notify the device <NUM> that such data is available and/or provide the new/changed data to the device <NUM>.

In one embodiment, the connection manager <NUM> determines that the mobile device <NUM> is unavailable (e.g., the radio is turned off) and utilizes SMS to transmit content to the device <NUM>, for instance via the SMSC shown in the example of <FIG>. 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 <NUM> can use SMS for certain transactions or responses having a priority level above a threshold or otherwise meeting a criteria. The server <NUM> 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 <NUM> in the proxy server <NUM> (e.g., the heartbeat manager <NUM>) can generate and/or transmit heartbeat messages on behalf of connected devices <NUM>, to maintain a backend connection with a provider <NUM> for applications running on devices <NUM>.

For example, in the distributed proxy system, local cache on the device <NUM> 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 <NUM> on the host server <NUM> to generate and/or send the heartbeat messages to maintain a connection with the backend (e.g., app server/provider <NUM> in the example of <FIG>). The proxy server can generate the keep-alive (heartbeat) messages independent of the operations of the local proxy on the mobile device.

The repositories <NUM>, <NUM>, and/or <NUM> can additionally store software, descriptive data, images, system information, drivers, and/or any other data item utilized by other components of the host server <NUM> 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> depicts a diagram showing how data requests from a mobile device <NUM> to an application server/content provider <NUM> in a wireless network can be coordinated by a distributed proxy system <NUM> in a manner such that network and battery resources are conserved through using content caching and monitoring performed by the distributed proxy system <NUM>.

In satisfying application or client requests on a mobile device <NUM> without the distributed proxy system <NUM>, the mobile device <NUM>, or the software widget executing on the device <NUM> performs a data request <NUM> (e.g., an HTTP GET, POST, or other request) directly to the application server <NUM> and receives a response <NUM> directly from the server/provider <NUM>. If the data has been updated, the widget on the mobile device <NUM> can refreshes itself to reflect the update and waits for small period of time and initiates another data request to the server/provider <NUM>.

In one embodiment, the requesting client or software widget <NUM> on the device <NUM> can utilize the distributed proxy system <NUM> in handling the data request made to server/provider <NUM>. In general, the distributed proxy system <NUM> can include a local proxy <NUM> (which is typically considered a client-side component of the system <NUM> and can reside on the mobile device <NUM>), a caching proxy (<NUM>, considered a server-side component <NUM> of the system <NUM> and can reside on the host server <NUM> or be wholly or partially external to the host server <NUM>), a host server <NUM>. The local proxy <NUM> can be connected to the proxy <NUM> and host server <NUM> via any network or combination of networks.

When the distributed proxy system <NUM> is used for data/application requests, the widget <NUM> can perform the data request <NUM> via the local proxy <NUM>. The local proxy <NUM>, 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 <NUM> 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 <NUM> 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 <NUM> can then send the request to the host server <NUM> and the server <NUM> can perform the request <NUM> and returns the results in response <NUM>. The local proxy <NUM> can store the result and in addition, information about the result and returns the result to the requesting widget <NUM>.

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 <NUM> can notify <NUM> the server <NUM> that the request should be monitored (e.g., steps <NUM> and <NUM>) for result changes prior to returning a result to the local proxy <NUM> or requesting widget <NUM>.

In one embodiment, if a request is marked for monitoring, the local proxy <NUM> can now store the results into the local cache. Now, when the data request <NUM>, for which a locally response is available, is made by the widget <NUM> and intercepted at the local proxy <NUM>, the proxy <NUM> can return the response <NUM> from the local cache without needing to establish a connection communication over the wireless network. In one embodiment, the response is stored at the server proxy in the server cache for subsequent use in satisfying same or similar data requests. The response can be stored in lieu of or in addition to storage on the local cache on the mobile device.

In addition, the server proxy performs the requests marked for monitoring <NUM> to determine whether the response <NUM> for the given request has changed. In general, the host server <NUM> can perform this monitoring independently of the widget <NUM> or local proxy <NUM> operations. Whenever an unexpected response <NUM> is received for a request, the server <NUM> can notify the local proxy <NUM> that the response has changed (e.g., the invalidate notification in step <NUM>) and that the locally stored response on the client should be erased or replaced with a new (e.g., changed or different) response.

In this case, a subsequent data request <NUM> by the widget <NUM> from the device <NUM> results in the data being returned from host server <NUM> (e.g., via the caching proxy <NUM>). Thus, through utilizing the distributed proxy system <NUM> the wireless (cellular) network is intelligently used when the content/data for the widget or software application <NUM> on the mobile device <NUM> 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 <NUM>, thus reducing battery consumption, and in addition, frees up network bandwidth.

<FIG> depicts a diagram showing one example process for implementing a hybrid IP and SMS power saving mode on a mobile device <NUM> using a distributed proxy and cache system (e.g., such as the distributed system shown in the example of <FIG>).

In step <NUM>, the local proxy (e.g., proxy <NUM> in the example of <FIG>) 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 <NUM> as it becomes available.

In process <NUM>, 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 <NUM>. ), 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 <NUM> in the example of <FIG>) on the server-side of the distributed proxy and cache system, the local proxy can respond with a call indicating that the device <NUM> 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 <NUM>) and/or the app server/providers 510A/B when the device <NUM> 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, change, 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 <NUM>, can stop sending changes (data or SMSs) 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 <NUM>, 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 <NUM>. The proxy server can time the poll or data collect event to optimize batch sending content to the mobile device <NUM> 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 <NUM> at the device <NUM> causes the power save mode to be exited. When the device <NUM> 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 <NUM> 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 <NUM>. In general, timing of power events to receive data can be synced with any power save calls to optimize radio use.

<FIG> depicts a flow chart illustrating example processes through which context awareness is used for traffic management.

In process <NUM>, characteristics of user activity on the mobile device are detected. In process <NUM>, behavior of the mobile device is adjusted to optimize battery consumption on the mobile device. The adjustment of the behavior of the mobile device can include, for example, adjusting the use of radio on the mobile device, as in process <NUM>. In addition, in process <NUM>, the radio can be switched on/off. Further, the radio can also be placed in low power or high power radio mode in process <NUM>.

In addition, data can be cached at the mobile device in process <NUM> to adjust radio use. Data may also be cached at the server in wireless communication with the mobile device to in order to modify communication frequency with the mobile device. In one embodiment, in response to detection of user activities on the mobile device, the characteristics of the user activity can be communicated from the mobile device to the server, in process <NUM>.

Similarly, based on the user activity characteristics, communication frequency of a server with the mobile device can be adjusted in process <NUM>. For example, data push frequency from the server to the mobile device is decreased, in process <NUM>. Similarly, data can be cached at the server in process <NUM> to adjust communication frequency.

In addition, characteristics of transactions occurring at the mobile device can also be used to locally adjust radio use on the mobile device. For example, characteristics of transactions include time criticality of the transactions and that a low power radio mode or a high power radio mode can be selected for use on the mobile device based on the time criticality of the transactions. Additionally, a low power radio mode or a high power radio mode is selected for use on the mobile device based on amount of data to be transferred in the transactions.

<FIG> depicts a flow chart illustrating an example process for managing traffic in a wireless network based on user interaction with a mobile device.

In process <NUM>, it is determined if the user actively interacting with the mobile device. If the user is actively interacting with the mobile device, the mobile device <NUM> can be notified, as in process <NUM>, of new data or changes in data.

If not, in process <NUM>, device can wait to send low priority transactions until after the user activity has been dormant for a period of time, for example, low priority transactions include, one or more of, updating message status as being read, unread, and deleting of messages. In addition, low priority transactions can be sent when a higher priority transaction needs to be sent, thus utilizing the same radio power-up event. Low priority transactions can generally include application maintenance events, events not requested by a user, events scheduled to be in the future, such as, by way of example but not limitation, one or more of, updating message status as being read, unread, and deleting of messages.

Similarly, if the user is not active, data push frequency from the server can be decreased in process <NUM>. In process <NUM>, if the user is detected to be subsequently active after being inactive, then data buffered as a result of decreased communication frequency can be sent to the mobile device, in process <NUM>.

Alternatively, even if the user is not actively interacting with the mobile device, an assessment can be made as to whether high importance data (e.g., data importance or priority meeting a threshold level) is pending to be sent to the mobile device, in process <NUM>. If so, the mobile device is notified, in process <NUM>. As a result of the notification, the mobile device radio can be enabled such that the high importance data can be sent to the mobile device. In general, the importance of data can be determined based on one or more of several criteria including but not limited to, application to which the data is relevant, time criticality, and time sensitivity, etc. An example of a time critical transaction includes a transaction resulting from a user-initiated data transfer.

<FIG> depicts a flow chart illustrating another example process for managing traffic in a wireless network based on user interaction with a mobile device.

In process <NUM>, user activity is detected at a device separate from a mobile device. In process <NUM>, it is determined whether the user activity at the device is able to access the same data, content, or application, which is also setup to be delivered to or accessed at the mobile device. For example, user activity at the device separate from the mobile device can include user access of an email inbox or other types applications via an interface other than that accessed from the mobile device (e.g., from a laptop or desktop computer). Since the user is now accessing the client from another device, the user now may not need content to be updated as frequently on the mobile device. Thus, in process <NUM>, communication frequency from a server to the mobile device is decreased.

<FIG> depicts a flow chart illustrating an example process for managing traffic initiated from a mobile device in a wireless network through batching of event transfer based on event priority.

In process <NUM>, multiple occurrences of events having a first priority type initiated on the mobile device are detected.

In process <NUM>, the mobile device cumulates multiple occurrences of events having a first priority type initiated on the mobile device, before transfer over the wireless network. The first priority type can be a generally low priority type indicating a request or update which is not time critical or time sensitive. Thus, if the device radio is currently off, the radio may not be immediately turned on to transmit individual events which are not time critical, until other triggering events occur or other criteria is met.

For example, in process <NUM>, occurrence of an event of a second priority type is detected, which can trigger batch transfer of the cumulated events to a server in wireless communication with the mobile device, in process <NUM>, where the second priority type is of a higher priority than the first priority type.

In another example, in process <NUM>, data transfer from the server can trigger the radio use on the mobile device, which can trigger batch transfer of the cumulated events to a server in wireless communication with the mobile device, in process <NUM>. Alternatively, in process <NUM>, after a period of time elapses, batch transfer of the cumulated events to a server in wireless communication with the mobile device can be triggered, in process <NUM>.

In one embodiment, in process <NUM>, a user trigger (e.g., a manual sync request) or in response to a user prompt, batch transfer of the cumulated events to a server in wireless communication with the mobile device can be triggered, in process <NUM>. In process <NUM>, when it is detected that an application is exited and/or moved into the background, batch transfer of the cumulated events to a server in wireless communication with the mobile device can be triggered, in process <NUM>.

<FIG> depicts a flow chart illustrating another example process for managing traffic initiated remotely from a mobile device in a wireless network through batching of event transfer based on event priority.

In process <NUM>, multiple occurrences of events having a first priority type are detected at a server wirelessly coupled to a mobile device. In process <NUM>, the server cumulates the multiple occurrences of events having a first priority type, before transfer over the wireless network. The first priority type may not be of a high priority type or having a priority exceeding a certain threshold level indicating a level or time criticality or urgency. Thus, such events, upon occurrence, may not be immediately transferred to the mobile device, until certain criterion is met, or until one or more triggering events occur.

For example, in process <NUM>, occurrence of an event of a second priority type is detected at the server, which can trigger batch transfer of the cumulated events to the mobile device, in process <NUM>, when the second priority type is of a higher priority than the first priority type. In another example, in process <NUM>, data transfer from the mobile device indicates the radio use on the mobile device, which can trigger batch transfer of the cumulated events to the mobile device, in process <NUM>.

Alternatively, in process <NUM>, after a period of time elapses, batch transfer of the cumulated events to the mobile device can be triggered, in process <NUM>. In process <NUM>, a user trigger or in response to a user prompt, batch transfer of the cumulated events to the mobile device can be triggered, in process <NUM>. In process <NUM>, when it is detected that an application is exited and/or moved into the background, batch transfer of the cumulated events to the mobile device can be triggered, in process <NUM>. In general, manual overrides or manual syncs can cause batch transfers to occur, either from the mobile device to the server or vice versa.

<FIG> 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, 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.

The network interface device enables the machine <NUM> to mediate data in a network with an entity that is external to the host server, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface device can include one or more of a network adaptor card, a wireless network interface card, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.

The network interface device can include a firewall which can, in some embodiments, govern and/or manage permission to access/proxy data in a computer network, and track varying levels of trust between different machines and/or applications. The firewall can be any number of modules having any combination of hardware and/or software components able to enforce a predetermined set of access rights between a particular set of machines and applications, machines and machines, and/or applications and applications, for example, to regulate the flow of traffic and resource sharing between these varying entities. The firewall may additionally manage and/or have access to an access control list which details permissions including for example, the access and operation rights of an object by an individual, a machine, and/or an application, and the circumstances under which the permission rights stand.

Other network security functions can be performed or included in the functions of the firewall, can be, for example, but are not limited to, intrusion-prevention, intrusion detection, next-generation firewall, personal firewall, etc. without deviating from the novel art of this disclosure.

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.

Claim 1:
A mobile device (<NUM>), comprising:
a local proxy (<NUM>) configured to:
determine a first application priority and a second application priority based on user preferences set at the mobile device, wherein the first application priority and second application priority are application-specific priorities set at the mobile device for respective first and second applications stored on the mobile device, wherein the user preferences are set by a user in a user interface of the mobile device;
provide the first application priority and the second application priority to a proxy server (<NUM>) so that the proxy server (<NUM>) modifies communication frequency with the mobile device (<NUM>, <NUM>) according to the received first application priority and second application priority;
receive data associated with the first application based on the first application priority; and
receive data associated with the second application based on the second application priority.