WO2012161751A1 - Coordination de trafic de réseau mobile entre de multiples applications - Google Patents
Coordination de trafic de réseau mobile entre de multiples applications Download PDFInfo
- Publication number
- WO2012161751A1 WO2012161751A1 PCT/US2012/022121 US2012022121W WO2012161751A1 WO 2012161751 A1 WO2012161751 A1 WO 2012161751A1 US 2012022121 W US2012022121 W US 2012022121W WO 2012161751 A1 WO2012161751 A1 WO 2012161751A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- application
- request
- data
- network
- mobile device
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0251—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/25—Maintenance of established connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/535—Tracking the activity of the user
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- WCDMA Wideband Code Division Multiple Access
- applications whose functions are based on actions initiated by the network, in contrast to functions initiated by the user or by the device.
- Such applications include, for example, push email, instant messaging, visual voicemail and voice and video telephony, and others.
- Such applications typically require an always-on IP connection and frequent transmit of small bits of data.
- WCDMA networks are designed and optimized for high- throughput of large amounts of data, not for applications that require frequent, but low- throughput and/or small amounts of data.
- Each transaction puts the mobile device radio in a high power mode for considerable length of time - typically between 15-30 seconds.
- 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.
- 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.
- FIG. 1A illustrates an example diagram of a system where a host server facilitates management of traffic between client devices and an application server or content provider in a wireless network for resource conservation.
- FIG. IB illustrates an example diagram of a proxy and cache system distributed between the host server and device which facilitates network traffic management between a device and an application server/content provider for resource conservation.
- FIG. 2A depicts a block diagram illustrating an example of client-side components in a distributed proxy and cache system residing on a mobile device that manages traffic in a wireless network for resource conservation.
- FIG. 2B depicts a block diagram illustrating another example of components in the application behavior detector and the traffic shaping engine in the local proxy on the client-side of the distributed proxy system shown in the example of FIG. 2 A.
- FIG. 3 depicts a block diagram illustrating an example of server-side components in a distributed proxy and cache system that manages traffic in a wireless network for resource conservation.
- FIG. 4A depicts a timing diagram showing how data requests from a mobile device to an application server/content provider in a wireless network can be coordinated by a distributed proxy system in a manner such that network and battery resources are conserved through using content caching and monitoring performed by the distributed proxy system.
- FIG. 4B depicts a timing diagram showing how data requests from a mobile device to an application server/content provider in a wireless network can be aligned at the local proxy in the distributed proxy system to optimize network and radio use.
- FIG. 5 depicts a diagram showing one example process for implementing a hybrid IP and SMS power saving mode on a mobile device using a distributed proxy and cache system (e.g., such as the distributed system shown in the example of FIG. IB).
- a distributed proxy and cache system e.g., such as the distributed system shown in the example of FIG. IB.
- FIG. 6 depicts a flow chart illustrating example selection processes through which data transfer requests of multiple applications can be coordinated into a single transfer operation.
- FIG. 7 depicts an example of triggering events that would cause a data request to be transferred without alignment with another data request.
- FIG. 8 depicts a flow chart illustrating an example process for using timing characteristics of data requests made by individual applications to delay transfer of one or more of the data requests made by one of the individual applications.
- FIG. 9 depicts a flow chart illustrating an example process for using application behavior of multiple applications to align their content requests made over the network.
- FIG. 10 depicts an example of processes through which the time of delay for content requests can be determined to align content requests over the wireless network.
- FIG. 11 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.
- references in this specification to "one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure.
- the appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments.
- various features are described which may be exhibited by some embodiments and not by others.
- various requirements are described which may be requirements for some embodiments but not other embodiments.
- Embodiments of the present disclosure include systems and methods for mobile network traffic coordination across multiple applications.
- 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 4G, namely LTE, 4G, and WiMAX are focused on providing increased bandwidth. Although partially addressed by the standards a key problem that remains is lack of bandwidth on the signaling channel more so than the data channel.
- 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.
- remote network node e.g., Network operation center (NOC)
- NOC Network operation center
- 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 15 minutes).
- the local proxy can automatically cache the content on the mobile device while delegating the polling to the server (e.g., a proxy server operated as an element of a communications network).
- the server can then notify the mobile/client proxy if the content changes, and if content has not changed (or not changed sufficiently, or in an identified manner or amount) the mobile proxy provides the latest version in its cache to the user (without need to utilize the radio at all).
- the mobile device e.g., a mobile phone, smart phone, etc.
- the mobile device 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.
- the logic for automatically adding content sources/application servers (e.g., including URLs/content) to be monitored can also check for various factors like how often the content is the same, how often the same request is made (is there a fixed interval/pattern?), which application is requesting the data, etc. Similar rules to decide between using the cache and request the data from the original source may also be implemented and executed by the local proxy and/or server.
- content sources/application servers e.g., including URLs/content
- a group of applications [A, B, C, ...] may have a timeline of transfers of data from the mobile device (or client (e.g., mobile application, software agent, widget) on the mobile device) to the network, or from the network to the mobile device (for receipt by the client).
- client e.g., mobile application, software agent, widget
- the time of the transfers can be represented as:
- Application A tAl, tA2, tA3, ...
- Application B tBl, tB2, tB3, ...
- Application C tCl, tC2, tC3, ...
- Each of the times 't' can have a natural point of occurring based upon the independent activity of the corresponding application as operations are executed at the application server/provider and/or on the software client on the mobile device.
- an application can transfer a message, an event, or other types of data to the network (or vice versa) at a regular or semi-regular series of times as part of polling, satisfying a device, application, or user request, application maintenance, or other operation.
- an application can transfer a message, event, or other types data via the network (or vice versa) at a regular, semi-regular, or irregular series of times to perform its inherent functions or operations, such as synchronizing two data stores, determining the contents of a data store, accessing new data from the application server/service provider, communicating with a peer device (e.g., another device with the same application or another application with which the requesting application interacts), exchanging control messages, etc.
- a peer device e.g., another device with the same application or another application with which the requesting application interacts
- the second application may be the same application as the first application and that correlations can be tracked and determined for multiple requests sent by one application in a similar fashion.
- a distributed proxy system including a local proxy and/or proxy server can operate to intercept the events or transactions (or requests for transfer) of information.
- the local proxy and/or the proxy server can delay (or expedite) the time at which one or more of these transfers would normally occur in order to perform multiple transfers together as part of a single transfer operation (i.e., instead of performing multiple, individual transfers).
- the local and/or proxy server can pre-retrieve data for a non-priority application or less important/time sensitive application whose polls are typically expected to happen before another application having higher priority, for example.
- a delay could be negative resulting in content pre-retrieval for alignment with an anticipated data request which typically happens before the request of the lesser priority application.
- the delay time (D) can represent a maximum time delay value (or in some instances, expedited time value) after receipt of a request to make such a transfer, with the value of D determined so as to enable the collection of as many of the transfers as feasible in a single, optimized data transfer.
- the delay times or expedited times of one or more transfers are determined so as to factor in any potential impact on performance and user experience.
- the system determines D to prevent undesired penalties or inefficiencies, and to prevent undesired impact on the user experience.
- the delay 'D' could be negative or positive for alignment purposes (e.g., to implement a delayed or an expedited transfer).
- delay time 'D' (use to represent both positive and negative delays (effectively and expedited transfer)) can be determined based on consideration of one or more of the following factors: the priority of the application (or the relative priority of one application in comparison to another), the nature or amount of data involved in the transfer (e.g., whether it represents fresh data, a housekeeping function, a control instruction, etc.), the status of the application (e.g., active, inactive, background, foreground, etc.), a useable lifetime of the data to be transferred (a period before it becomes stale), the interval between the transfer times of multiple data requests for a single application, the interval between the transfer times across more than one application (e.g., the largest transfer time interval based on consideration of all active applications), network characteristics (available bandwidth, network latency, etc.), or another relevant factor.
- the priority of the application or the relative priority of one application in comparison to another
- the nature or amount of data involved in the transfer e.g., whether it represents fresh data, a housekeeping function,
- the delay time 'D' of specific events/transactions can be controlled by the mobile device (e.g., platform, device settings, or OS specifications), network service provider, and/or the user as part of optimizing the battery life to align data transfer requests across multiple applications or the same application, as opposed to performing each data transfer individually.
- the user can manually configure a setting specifying that requests across multiple applications or the same application are to be batched. The user can enable the setting, and allow the system to configure the details.
- the user can specify preferences, priorities, or any other constraints related to alignment of data request transfer of the mobile network.
- FIG. 1A illustrates an example diagram of a system where a host server 100 facilitates management of traffic between client devices 102 and an application server or content provider 110 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 100 and/or application server/content provider 110.
- Client devices 102 will typically include a display and/or other output functionalities to present information and data exchanged between among the devices 102 and/or the host server 100 and/or application server/content provider 110.
- the client devices 102 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.
- the client devices 102, host server 100, and app server 110 are coupled via a network 106 and/or a network 108.
- the devices 102 and host server 100 may be directly connected to one another. .
- the input mechanism on client devices 102 can include touch screen keypad (including single touch, multi-touch, gesture sensing in 2D or 3D, etc.), a physical keypad, a mouse, a pointer, a track pad, motion detector (e.g., including 1-axis, 2-axis, 3-axis accelerometer, etc.), a light sensor, capacitance sensor, resistance sensor, temperature sensor, proximity sensor, a piezoelectric device, device orientation detector (e.g., electronic compass, tilt sensor, rotation sensor, gyroscope, accelerometer), or a combination of the above.
- touch screen keypad including single touch, multi-touch, gesture sensing in 2D or 3D, etc.
- a physical keypad e.g., a mouse, a pointer, a track pad
- motion detector e.g., including 1-axis, 2-axis, 3-axis accelerometer, etc.
- a light sensor e.g., including 1-axis, 2-axis, 3-axis accelerometer, etc
- Context awareness at client devices 102 generally includes, by way of example but not limitation, client device 102 operation or state acknowledgement, management, user activity/behavior/interaction awareness, detection, sensing, tracking, trending, and/or application (e.g., mobile applications) type, behavior, activity, operating state, etc.
- Context awareness in the present disclosure also includes knowledge and detection of network side contextual data and can include network information such as network capacity, bandwidth, traffic, type of network/connectivity, and/or any other operational state data.
- Network side contextual data can be received from and/or queried from network service providers (e.g., cell provider 112 and/or Internet service providers) of the network 106 and/or network 108 (e.g., by the host server and/or devices 102).
- network service providers e.g., cell provider 112 and/or Internet service providers
- the application context awareness may also be received from or obtained/queried from the respective application/service providers 110 (by the host 100 and/or client devices 102).
- the host server 100 can use, for example, contextual information obtained for client devices 102, networks 106/108, applications (e.g., mobile applications), application server/provider 110, or any combination of the above, to manage the traffic in the system to satisfy data needs of the client devices 102 (e.g., to satisfy application or any other request including HTTP request).
- the traffic is managed by the host server 100 to satisfy data requests made in response to explicit or non-explicit user 103 requests and/or device/application maintenance tasks.
- the traffic can be managed such that network consumption, for example, use of the cellular network is conserved for effective and efficient bandwidth utilization.
- the host server 100 can manage and coordinate such traffic in the system such that use of device 102 side resources (e.g., including but not limited to battery power consumption, radio use, processor/memory use) are optimized with a general philosophy for resource conservation while still optimizing performance and user experience.
- device 102 side resources e.g., including but not limited to battery power consumption, radio use, processor/memory use
- the device 150 can observe user activity (for example, by observing user keystrokes, backlight status, or other signals via one or more input mechanisms, etc.) and alters device 102 behaviors.
- the device 150 can also request the host server 100 to alter the behavior for network resource consumption based on user activity or behavior.
- the traffic management for resource conservation is performed using a distributed system between the host server 100 and client device 102.
- the distributed system can include proxy server and cache components on the server 100 side and on the client 102 side, for example, as shown by the server cache 135 on the server 100 side and the local cache 150 on the client 102 side.
- Functions and techniques disclosed for context aware traffic management for resource conservation in networks reside in a distributed proxy and cache system.
- the proxy and cache system can be distributed between, and reside on, a given client device 102 in part or in whole and/or host server 100 in part or in whole.
- the distributed proxy and cache system are illustrated with further reference to the example diagram shown in FIG. IB. Functions and techniques performed by the proxy and cache components in the client device 102, the host server 100, and the related components therein are described, respectively, in detail with further reference to the examples of FIG. 2-3.
- client devices 102 communicate with the host server 100 and/or the application server 110 over network 106, which can be a cellular network.
- network 106 can be a cellular network.
- the host server 100 can communicate with the application server/providers 110 over the network 108, which can include the Internet.
- the networks 106 and/or 108, over which the client devices 102, the host server 100, and/or application server 110 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.
- 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-232, SDH, SONET, etc.
- the networks 106 and/or 108 can be any collection of distinct networks operating wholly or partially in conjunction to provide connectivity to the client devices 102 and the host server 100 and may appear as one or more networks to the serviced systems and devices.
- communications to and from the client devices 102 can be achieved by, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet.
- communications can be achieved by a secure communications protocol, such as secure sockets layer (SSL), or transport layer security (TLS).
- SSL secure sockets layer
- TLS transport layer security
- communications can be achieved via one or more networks, such as, but are not limited to, one or more of WiMax, a Local Area Network (LAN), Wireless Local Area Network (WLAN), a Personal area network (PAN), a Campus area network (CAN), a Metropolitan area network (MAN), a Wide area network (WAN), a Wireless wide area network (WW AN), 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, 2G, 2.5G, 3G, 4G, IMT-Advanced, pre-4G, 3G LTE, 3 GPP LTE, LTE Advanced, mobile WiMax, WiMax 2, WirelessMAN-Advanced networks, enhanced data rates for GSM evolution (EDGE), General packet radio service (GPRS), enhanced GPRS, iBurst, UMTS, HSPDA, HSUPA, HSPA, UMTS-TDD, IxRTT, EV
- FIG. IB illustrates an example diagram of a proxy and cache system distributed between the host server 100 and device 150 which facilitates network traffic management between the device 150 and an application server/content provider 100 (e.g., a source server) for resource conservation.
- an application server/content provider 100 e.g., a source server
- the distributed proxy and cache system can include, for example, the proxy server 125 (e.g., remote proxy) and the server cache, 135 components on the server side.
- the server-side proxy 125 and cache 135 can, as illustrated, reside internal to the host server 100.
- the proxy server 125 and cache 135 on the server-side can be partially or wholly external to the host server 100 and in communication via one or more of the networks 106 and 108.
- the proxy server 125 may be external to the host server and the server cache 135 may be maintained at the host server 100.
- the proxy server 125 may be within the host server 100 while the server cache is external to the host server 100.
- each of the proxy server 125 and the cache 135 may be partially internal to the host server 100 and partially external to the host server 100.
- the distributed system can also, include, in one embodiment, client-side components, including by way of example but not limitation, a local proxy 175 (e.g., a mobile client on a mobile device) and/or a local cache 185, which can, as illustrated, reside internal to the device 150 (e.g., a mobile device).
- client-side components including by way of example but not limitation, a local proxy 175 (e.g., a mobile client on a mobile device) and/or a local cache 185, which can, as illustrated, reside internal to the device 150 (e.g., a mobile device).
- the client-side proxy 175 and local cache 185 can be partially or wholly external to the device 150 and in communication via one or more of the networks 106 and 108.
- the local proxy 175 may be external to the device 150 and the local cache 185 may be maintained at the device 150.
- the local proxy 175 may be within the device 150 while the local cache 185 is external to the device 150.
- each of the proxy 175 and the cache 185 may be partially internal to the host server 100 and partially external to the host server 100.
- the distributed system can include an optional caching proxy server 199.
- the caching proxy server 199 can be a component which is operated by the application server/content provider 110, the host server 100, or a network service provider 112, and or any combination of the above to facilitate network traffic management for network and device resource conservation.
- Proxy server 199 can be used, for example, for caching content to be provided to the device 150, for example, from one or more of, the application server/provider 110, host server 100, and/or a network service provider 112. Content caching can also be entirely or partially performed by the remote proxy 125 to satisfy application requests or other data requests at the device 150.
- characteristics of user activity/behavior and/or application behavior at a mobile device 150 can be tracked by the local proxy 175 and communicated, over the network 106 to the proxy server 125 component in the host server 100, for example, as connection metadata.
- the proxy server 125 which in turn is coupled to the application server/provider 110 provides content and data to satisfy requests made at the device 150.
- the local proxy 175 can identify and retrieve mobile device properties including, one or more of, battery level, network that the device is registered on, radio state, whether the mobile device is being used (e.g., interacted with by a user). In some instances, the local proxy 175 can delay, expedite (prefetch) and/or modify data prior to transmission to the proxy server 125, when appropriate, as will be further detailed with references to the description associated with the examples of FIG. 2-3.
- the local database 185 can be included in the local proxy 175 or coupled to the proxy 175 and can be queried for a locally stored response to the data request prior to the data request being forwarded on to the proxy server 125.
- Locally cached responses can be used by the local proxy 175 to satisfy certain application requests of the mobile device 150, by retrieving cached content stored in the cache storage 185, when the cached content is still valid.
- the proxy server 125 of the host server 100 can also delay, expedite, or modify data from the local proxy prior to transmission to the content sources (e.g., the app server/content provider 110).
- the proxy server 125 uses device properties and connection metadata to generate rules for satisfying request of applications on the mobile device 150.
- the proxy server 125 can gather real time traffic information about requests of applications for later use in optimizing similar connections with the mobile device 150 or other mobile devices.
- the local proxy 175 and the proxy server 125 are transparent to the multiple applications executing on the mobile device.
- the local proxy 175 is generally transparent to the operating system or platform of the mobile device and may or may not be specific to device manufacturers.
- the local proxy 175 is optionally customizable in part or in whole to be device specific.
- the local proxy 175 may be bundled into a wireless model, into a firewall, and/or a router.
- the host server 100 can in some instances, utilize the store and forward functions of a short message service center (SMSC) 112, such as that provided by the network service provider 112, in communicating with the device 150 in achieving network traffic management.
- SMSC short message service center
- the host server 100 can forward content or HTTP responses to the SMSC 112 such that it is automatically forwarded to the device 150 if available, and for subsequent forwarding if the device 150 is not currently available.
- the disclosed distributed proxy and cache system allows optimization of network usage, for example, by serving requests from the local cache 185, the local proxy 175 reduces the number of requests that need to be satisfied over the network 106. Further, the local proxy 175 and the proxy server 125 may filter irrelevant data from the communicated data. In addition, the local proxy 175 and the proxy server 125 can also accumulate low priority data and send it in batches to avoid the protocol overhead of sending individual data fragments. The local proxy 175 and the proxy server 125 can also compress or transcode the traffic, reducing the amount of data sent over the network 106 and/or 108. The signaling traffic in the network 106 and/or 108 can be reduced, as the networks are now used less often and the network traffic can be synchronized among individual applications.
- FIG. 2A depicts a block diagram illustrating an example of client-side components in a distributed proxy and cache system residing on a device 250 that manages traffic in a wireless network for resource conservation.
- the device 250 which can be a portable or mobile device, such as a portable phone, generally includes, for example, a network interface 208, an operating system 204, a context API 206, and mobile applications which may be proxy unaware 210 or proxy aware 220.
- the device 250 is specifically illustrated in the example of FIG. 2 as a mobile device, such is not a limitation and that device 250 may be any portable/mobile or non-portable device able to receive, transmit signals to satisfy data requests over a network including wired or wireless networks (e.g., WiFi, cellular, Bluetooth, etc.).
- wired or wireless networks e.g., WiFi, cellular, Bluetooth, etc.
- the network interface 202 can be a networking module that enables the device 250 to mediate data in a network with an entity that is external to the host server 250, through any known and/or convenient communications protocol supported by the host and the external entity.
- the network interface 208 can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G, LTE, etc.,), Bluetooth, or whether or not the connection is via a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.
- a network adaptor card e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G, LTE, etc.,
- Device 250 can further include, client-side components of the distributed proxy and cache system which can include, a local proxy 275 (e.g., a mobile client of a mobile device) and a cache 285.
- the local proxy 275 includes a user activity module 215, a proxy API 225, a request/transaction manager 235, a caching policy manager 245, a traffic shaping engine 255, and/or a connection manager 265.
- the traffic shaping engine 255 may further include an alignment module 256 and/or a batching module 257
- the connection manager 265 may further include a radio controller 266.
- the request/transaction manager 235 can further include an application behavior detector 236 and/or a prioritization engine 241, the application behavior detector 236 may further include a pattern detector 237 and/or and application profile generator 239. Additional or less components/modules/engines can be included in the local proxy 275 and each illustrated component.
- a "module,” “a manager,” a “handler,” a “detector,” an “interface,” 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.
- a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid.
- Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.
- a portion of the distributed proxy and cache system for network traffic management resides in or is in communication with device 250, including local proxy 275 (mobile client) and/or cache 285.
- the local proxy 275 can provide an interface on the device 250 for users to access device applications and services including email, IM, voice mail, visual voicemail, feeds, Internet, other applications, etc.
- the proxy 275 is generally application independent and can be used by applications (e.g., both proxy aware and proxy-unaware mobile applications 210 and 220) to open TCP connections to a remote server (e.g., the server 100 in the examples of FIG. 1A-1B and/or server proxy 125/325 shown in the examples of FIG. IB and FIG. 3).
- a remote server e.g., the server 100 in the examples of FIG. 1A-1B and/or server proxy 125/325 shown in the examples of FIG. IB and FIG. 3.
- the local proxy 275 includes a proxy API 225 which can be optionally used to interface with proxy-aware applications 220 (or mobile applications on a mobile device).
- the applications 210 and 220 can generally include any user application, widgets, software, HTTP-based application, web browsers, video or other multimedia streaming or downloading application, video games, social network applications, email clients, RSS management applications, application stores, document management applications, productivity enhancement applications, etc.
- the applications can be provided with the device OS, by the device manufacturer, by the network service provider, downloaded by the user, or provided by others.
- the local proxy 275 includes or is coupled to a context API 206, as shown.
- the context API 206 may be a part of the operating system 204 or device platform or independent of the operating system 204, as illustrated.
- the operating system 204 can include any operating system including but not limited to, any previous, current, and/or future versions/releases of, Windows Mobile, iOS, Android, Symbian, Palm OS, Brew MP, Java 2 Micro Edition (J2ME), Blackberry, etc.
- the context API 206 may be a plug-in to the operating system 204 or a particular client application on the device 250.
- the context API 206 can detect signals indicative of user or device activity, for example, sensing motion, gesture, device location, changes in device location, device backlight, keystrokes, clicks,, activated touch screen, mouse click or detection of other pointer devices.
- the context API 206 can be coupled to input devices or sensors on the device 250 to identify these signals. Such signals can generally include input received in response to explicit user input at an input device/mechanism at the device 250 and/or collected from ambient signals/contextual cues detected at or in the vicinity of the device 250 (e.g., light, motion, piezoelectric, etc.).
- the user activity module 215 interacts with the context API 206 to identify, determine, infer, detect, compute, predict, and/or anticipate, characteristics of user activity on the device 250.
- Various inputs collected by the context API 206 can be aggregated by the user activity module 215 to generate a profile for characteristics of user activity.
- Such a profile can be generated by the module 215 with various temporal characteristics.
- user activity profile can be generated in real-time for a given instant to provide a view of what the user is doing or not doing at a given time (e.g., defined by a time window, in the last minute, in the last 30 seconds, etc.), a user activity profile can also be generated for a 'session' defined by an application or web page that describes the characteristics of user behavior with respect to a specific task they are engaged in on the device 250, or for a specific time period (e.g., for the last 2 hours, for the last 5 hours).
- characteristic profiles can be generated by the user activity module 215 to depict a historical trend for user activity and behavior (e.g. 1 week, 1 mo, 2 mo, etc.). Such historical profiles can also be used to deduce trends of user behavior, for example, access frequency at different times of day, trends for certain days of the week (weekends or week days), user activity trends based on location data (e.g., IP address, GPS, or cell tower coordinate data) or changes in location data (e.g., user activity based on user location, or user activity based on whether the user is on the go, or traveling outside a home region, etc.) to obtain user activity characteristics.
- location data e.g., IP address, GPS, or cell tower coordinate data
- changes in location data e.g., user activity based on user location, or user activity based on whether the user is on the go, or traveling outside a home region, etc.
- user activity module 215 can detect and track user activity with respect to applications, documents, files, windows, icons, and folders on the device 250. For example, the user activity module 215 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.
- an application or window e.g., a web browser
- characteristics of the user activity on the device 250 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.
- the use of a radio on a device can be adjusted based on characteristics of user behavior (e.g., by the radio controller 266 of the connection manager 265) coupled to the user activity module 215.
- the radio controller 266 can turn the radio on or off, based on characteristics of the user activity on the device 250.
- the radio controller 266 can adjust the power mode of the radio (e.g., to be in a higher power mode or lower power mode) depending on characteristics of user activity.
- characteristics of the user activity on device 250 can also be used to cause another device (e.g., other computers, a mobile device, or a non-portable device) or server (e.g., host server 100 and 300 in the examples of FIG. 1A-B and FIG. 3) which can communicate (e.g., via a cellular or other network) with the device 250 to modify its communication frequency with the device 250.
- another device e.g., other computers, a mobile device, or a non-portable device
- server e.g., host server 100 and 300 in the examples of FIG. 1A-B and FIG. 3
- the local proxy 275 can use the characteristics information of user behavior determined by the user activity module 215 to instruct the remote device as to how to modulate its communication frequency (e.g., decreasing communication frequency, such as data push frequency if the user is idle, requesting that the remote device notify the device 250 if new data, changed, data, or data of a certain level of importance becomes available, etc.).
- decreasing communication frequency such as data push frequency if the user is idle
- the user activity module 215 can, in response to determining that user activity characteristics indicate that a user is active after a period of inactivity, request that a remote device (e.g., server host server 100 and 300 in the examples of FIG. 1A-B and FIG. 3) send the data that was buffered as a result of the previously decreased communication frequency.
- a remote device e.g., server host server 100 and 300 in the examples of FIG. 1A-B and FIG. 3
- the local proxy 275 can communicate the characteristics of user activity at the device 250 to the remove device (e.g., e.g., host server 100 and 300 in the examples of FIG. 1A-B and FIG. 3) and the remote device determines how to alter its own communication frequency with the device 250 for network resource conservation and conservation of device 250 resources.
- the remove device e.g., host server 100 and 300 in the examples of FIG. 1A-B and FIG. 3
- the remote device determines how to alter its own communication frequency with the device 250 for network resource conservation and conservation of device 250 resources.
- One embodiment of the local proxy 275 further includes a request/transaction manager 235, which can detect, identify, intercept, process, manage, data requests initiated on the device 250, for example, by applications 210 and/or 220, and/or directly/indirectly by a user request.
- the request/transaction manager 235 can determine how and when to process a given request or transaction, or a set of requests/transactions, based on transaction characteristics.
- the request/transaction manager 235 can prioritize requests or transactions made by applications and/or users at the device 250, for example by the prioritization engine 241. Importance or priority of requests/transactions can be determined by the manager 235 by applying a rule set, for example, according to time sensitivity of the transaction, time sensitivity of the content in the transaction, time criticality of the transaction, time criticality of the data transmitted in the transaction, and/or time criticality or importance of an application making the request.
- transaction characteristics can also depend on whether the transaction was a result of user-interaction or other user initiated action on the device (e.g., user interaction with a mobile application).
- a time critical transaction can include a transaction resulting from a user-initiated data transfer, and can be prioritized as such.
- Transaction characteristics can also depend on the amount of data that will be transferred or is anticipated to be transferred as a result of the request/requested transaction.
- the connection manager 265 can adjust the radio mode (e.g., high power or low power mode via the radio controller 266) based on the amount of data that will need to be transferred.
- the radio controller 266/connection manager 265 can adjust the radio power mode (high or low) based on time criticality/sensitivity of the transaction.
- the radio controller 266 can trigger the use of high power radio mode when a time-critical transaction (e.g., a transaction resulting from a user-initiated data transfer, an application running in the foreground, any other event meeting a certain criteria) is initiated or detected.
- a time-critical transaction e.g., a transaction resulting from a user-initiated data transfer, an application running in the foreground, any other event meeting a certain criteria
- the priorities can be determined set by in 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 241 may include set of rules for assigning priority.
- the prioritization engine 241 can also track network provider limitations or specifications on application or transaction priority in determining an overall priority status for a request/transaction. Furthermore, priority can in part or in whole be determined by user preferences, either explicit or implicit. A user, can in general, set priorities at different tiers, such as, specific priorities for sessions, or types, or applications (e.g., a browsing session, a gaming session, versus an IM chat session, the user may set a gaming session to always have higher priority than an IM chat session, which may have higher priority than web-browsing session).
- a user can set application-specific priorities, (e.g., a user may set Facebook related transactions to have a higher priority than Linkedln related transactions), for specific transaction types (e.g., for all send message requests across all applications to have higher priority than message delete requests, for all calendar-related events to have a high priority, etc.), and/or for specific folders.
- application-specific priorities e.g., a user may set Facebook related transactions to have a higher priority than Linkedln related transactions
- specific transaction types e.g., for all send message requests across all applications to have higher priority than message delete requests, for all calendar-related events to have a high priority, etc.
- the prioritization engine 241 can track and resolve conflicts in priorities set by different entities. For example, manual settings specified by the user may take precedence over device OS settings, network provider parameters/limitations (e.g., set in default for a network service area, geographic locale, set for a specific time of day, or set based on service/fee type) may limit any user-specified settings and/or application-set priorities. In some instances, a manual 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.
- network provider parameters/limitations e.g., set in default for a network service area, geographic locale, set for a specific time of day, or set based on service/fee type
- a manual 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 shows, for illustration purposes, some examples of transactions with examples of assigned priorities in a binary representation scheme. Additional assignments are possible for additional types of events, requests, transactions, and as previously described, priority assignments can be made at more or less granular levels, e.g., at the session level or at the application level, etc.
- lower priority requests/transactions can include, updating message status as being read, unread, deleting of messages, deletion of contacts; higher priority requests/transactions, can in some instances include, status updates, new IM chat message, new email, calendar event update/cancellation/deletion, an event in a mobile gaming session, or other entertainment related events, a purchase confirmation through a web purchase or online, request to load additional or download content, contact book related events, a transaction to change a device setting, location-aware or location-based events/transactions, or any other events/request/transactions initiated by a user or where the user is known to be, expected to be, or suspected to be waiting for a response, etc.
- Inbox pruning events are generally considered low priority and absent other impending events, generally will not trigger use of the radio on the device 250.
- pruning events to remove old email or other content can be 'piggy backed' with other communications if the radio is not otherwise on, at the time of a scheduled pruning event. For example, if the user has preferences set to 'keep messages for 7 days old,' then instead of powering on the device radio to initiate a message delete from the device 250 the moment that the message has exceeded 7 days old, the message is deleted when the radio is powered on next. If the radio is already on, then pruning may occur as regularly scheduled.
- the requesl/transaction manager 235 can use the priorities for requests (e.g., by the prioritization engine 241) to manage outgoing traffic from the device 250 for resource optimization (e.g., to utilize the device radio more efficiently for battery conservation). For example, transactions/requests below a certain priority ranking may not trigger use of the radio on the device 250 if the radio is not already switched on, as controlled by the connection manager 265. In contrast, the radio controller 266 can turn on the radio such a request can be sent when a request for a transaction is detected to be over a certain priority level.
- priority assignments (such as that determined by the local proxy 275 or another device/entity) can be used cause a remote device to modify its communication with the frequency with the mobile device.
- the remote device can be configured to send notifications to the device 250 when data of higher importance is available to be sent to the mobile device.
- transaction priority can be used in conjunction with characteristics of user activity in shaping or managing traffic, for example, by the traffic shaping engine 255.
- the traffic shaping engine 255 can, in response to detecting that a user is dormant or inactive, wait to send low priority transactions from the device 250, for a period of time.
- the traffic shaping engine 255 can allow multiple low priority transactions to accumulate for batch transferring from the device 250 (e.g., via the batching module 257).
- the priorities can be set, configured, or readjusted by a user. For example, content depicted in Table I in the same or similar form can be accessible in a user interface on the device 250 and for example , used by the user to adjust or view the priorities.
- the batching module 257 can initiate batch transfer based on certain criteria. For example, batch transfer (e.g., of multiple occurrences of events, some of which occurred at different instances in time) may occur after a certain number of low priority events have been detected, or after an amount of time elapsed after the first of the low priority event was initiated. In addition, the batching module 257 can initiate batch transfer of the cumulated low priority events when a higher priority event is initiated or detected at the device 250. Batch transfer can otherwise be initiated when radio use is triggered for another reason (e.g., to receive data from a remote device such as host server 100 or 300). In one embodiment, an impending pruning event (pruning of an inbox), or any other low priority events, can be executed when a batch transfer occurs.
- an impending pruning event pruning of an inbox
- the batching capability can be disabled or enabled at the event/transaction level, application level, or session level, based on any one or combination of the following: user configuration, device limitations/settings, manufacturer specification, network provider parameters/limitations, platform specific limitations/settings, device OS settings, etc.
- batch transfer can be initiated when an application/window/file is closed out, exited, or moved into the background; users can optionally be prompted before initiating a batch transfer; users can also manually trigger batch transfers.
- the local proxy 275 locally adjusts radio use on the device 250 by caching data in the cache 285.
- the radio controller 266 need not activate the radio to send the request to a remote entity (e.g., the host server 100, 300, as shown in FIG. 1 and FIG. 3 or a content provider/application server such as the server/provider 110 shown in the examples of FIG. 1A and FIG. IB).
- a remote entity e.g., the host server 100, 300, as shown in FIG. 1 and FIG. 3 or a content provider/application server such as the server/provider 110 shown in the examples of FIG. 1A and FIG. IB.
- the local proxy 275 can use the local cache 285 and the cache policy manager 245 to locally store data for satisfying data requests to eliminate or reduce the use of the device radio for conservation of network resources and device battery consumption.
- the local repository 285 can be queried to determine if there is any locally stored response, and also determine whether the response is valid. When a valid response is available in the local cache 285, the response can be provided to the application on the device 250 without the device 250 needing to access the cellular network.
- the local proxy 275 can query a remote proxy (e.g., the server proxy 325 of FIG. 3) to determine whether a remotely stored response is valid. If so, the remotely stored response (e.g., which may be stored on the server cache 135 or optional caching server 199 shown in the example of FIG. IB) can be provided to the mobile device, possibly without the mobile device 250 needing to access the cellular network, thus relieving consumption of network resources.
- a remote proxy e.g., the server proxy 325 of FIG. 3
- the local proxy 275 can send the data request to a remote proxy (e.g., server proxy 325 of FIG. 3) which forwards the data request to a content source (e.g., application server/content provider 110 of FIG. 1) and a response from the content source can be provided through the remote proxy, as will be further described in the description associated with the example host server 300 of FIG. 3.
- the cache policy manager 245 can manage or process requests that use a variety of protocols, including but not limited to HTTP, HTTPS, IMAP, POP, SMTP and/or ActiveSync.
- the caching policy manager 245 can locally store responses for data requests in the local database 285 as cache entries, for subsequent use in satisfying same or similar data requests. [00106] The manager 245 can request that the remote proxy monitor responses for the data request, and the remote proxy can notify the device 250 when an unexpected response to the data request is detected. In such an event, the cache policy manager 245 can erase or replace the locally stored response(s) on the device 250 when notified of the unexpected response (e.g., new data, changed data, additional data, etc.) to the data request. In one embodiment, the caching policy manager 245 is able to detect or identify the protocol used for a specific request, including but not limited to HTTP, HTTPS, IMAP, POP, SMTP and/or ActiveSync.
- application specific handlers e.g., via the application protocol module 246 of the manager 245 on the local proxy 275 allows for optimization of any protocol that can be port mapped to a handler in the distributed proxy (e.g., port mapped on the proxy server 325 in the example of FIG. 3).
- the local proxy 275 notifies the remote proxy such that the remote proxy can monitor responses received for the data request from the content source for changed results prior to returning the result to the device 250, for example, when the data request to the content source has yielded same results to be returned to the mobile device.
- the local proxy 275 can simulate application server responses for applications on the device 250, using locally cached content. This can prevent utilization of the cellular network for transactions where new/changed data is not available, thus freeing up network resources and preventing network congestion.
- the local proxy 275 includes an application behavior detector 236 to track, detect, observe, monitor, applications (e.g., proxy aware and/or unaware applications 210 and 220) accessed or installed on the device 250.
- application behaviors, or patterns in detected behaviors e.g., via the pattern detector 237) of one or more applications accessed on the device 250 can be used by the local proxy 275 to optimize traffic in a wireless network needed to satisfy the data needs of these applications.
- the traffic shaping engine 255 can align content requests made by at least some of the applications over the network (wireless network) (e.g., via the alignment module 256).
- the alignment module can delay or expedite some earlier received requests to achieve alignment.
- the traffic shaping engine 255 can utilize the connection manager to poll over the network to satisfy application data requests.
- Content requests for multiple applications can be aligned based on behavior patterns or rules/settings including, for example, content types requested by the multiple applications (audio, video, text, etc.), mobile device parameters, and/or network parameters/traffic conditions, network service provider constraints/specifications, etc.
- the pattern detector 237 can detect recurrences in application requests made by the multiple applications, for example, by tracking patterns in application behavior.
- a tracked pattern can include, detecting that certain applications, as a background process, poll an application server regularly, at certain times of day, on certain days of the week, periodically in a predictable fashion, with a certain frequency, with a certain frequency in response to a certain type of event, in response to a certain type user query, frequency that requested content is the same, frequency with which a same request is made, interval between requests, applications making a request, or any combination of the above, for example.
- Such recurrences can be used by traffic shaping engine 255 to offload polling of content from a content source (e.g., from an application server/content provider 110 of FIG. 1) that would result from the application requests that would be performed at the mobile device 250 to be performed instead, by a proxy server (e.g., proxy server 125 of FIG. IB or proxy server 325 of FIG. 3) remote from the device 250.
- Traffic engine 255 can decide to offload the polling when the recurrences match a rule. For example, there are multiple occurrences or requests for the same resource that have exactly the same content, or returned value, or based on detection of repeatable time periods between requests and responses such as a resource that is requested at specific times during the day.
- the offloading of the polling can decrease the amount of bandwidth consumption needed by the mobile device 250 to establish a wireless (cellular) connection with the content source for repetitive content polls.
- the remote entity to which polling is offloaded can notify the device 250.
- the remote entity may be the host server 300 as shown in the example of FIG. 3.
- the local proxy 275 can mitigate the need/use of periodic keep alive messages (heartbeat messages) to maintain TCP/IP connections, which can consume significant amounts of power thus having detrimental impacts on mobile device battery life.
- the connection manager 265 in the local proxy e.g., the heartbeat manager 267) can detect, identify, and intercept any or all heartbeat (keep-alive) messages being sent from applications.
- the heartbeat manager 267 can prevent any or all of these heartbeat messages from being sent over the cellular, or other network, and instead rely on the server component of the distributed proxy system (e.g., shown in FIG. IB) to generate the and send the heartbeat messages to maintain a connection with the backend (e.g., app server/provider 110 in the example of FIG. 1).
- the server component of the distributed proxy system e.g., shown in FIG. IB
- the backend e.g., app server/provider 110 in the example of FIG. 1
- the local proxy 275 generally represents any one or a portion of the functions described for the individual managers, modules, and/or engines.
- the local proxy 275 and device 250 can include additional or less components; more or less functions can be included, in whole or in part, without deviating from the novel art of the disclosure.
- FIG. 2B depicts a block diagram illustrating another example of components in the application behavior detector 236 and the traffic shaping engine 255 in the local proxy 275 on the client-side of the distributed proxy system shown in the example of FIG. 2A.
- the pattern detector 237 of the application behavior detector 236 further includes a correlation detector 238 and the application profile generator 239 further includes an application status detector 240.
- the correlation detector 238, in one embodiment, can detect, determine, identify, compute, track, any correlations in the timing of data transfer requests made by applications, agents, and/or widgets accessed via (e.g., application streaming or accessed through a cloud) or running on the device 250.
- correlation types include event-level correlations and application- level correlations, and can include system/application.
- the correlation detector 238 can track and monitor system/application triggered events and/or user-triggered events/transactions. In addition, the correlation detector 238 can identify or track correlations between events for a given application or across different applications.
- a correlation can be detected, for example, when a first event/transaction type of a first application triggers the initiation of a second event/transaction type of the same application.
- the triggering can be detected by the correlation detector 238 through identifying patterns in the timing characteristics of such events occurring within the first application.
- a correlation can include, an identification of the ordering of the first and second event/transaction types (e.g., the second event type always occurs after the first event type).
- a correlation can also include, determining that the first and second event/transaction types occur within a timeframe of one another (e.g., the first event type occurs within a 10 ms. time window of the second event type), etc.
- a correlation can also be detected, for example, when a specific event type of one application triggers a specific event type of another application (or has a timing or ordering relationship thereof).
- the correlation detector 238 can detect that operation of one application (e.g., such as the launching of one application or any other activity) is related to the operation of another application. For example, the detector can determine that if one application is launched, the other application is also launched.
- the detector can also detect that one application is always launched within a certain time window of another application being launched/accessed, or the activity status of one application is linked to the application status of the activity status of another application (e.g., when one application moves into the foreground ackground, the other application moves into the foreground/background, or when one application becomes active/inactive, the other application also changes state and becomes either active or inactive, etc.).
- events/transactions detected and tracked for correlation can include system or application-initiated events, or user-triggered events (e.g., including explicit user requests or implicit user requests).
- the correlation detector 238 uses user activity module 215 and can also detect application or application event correlations in relation to and/or in conjunction with user activity. For example, the correlation detector 238 can determine that an occurrence of a first event type frequently causes the user to perform an action which triggers a second event (of the same application or different application). While examples are described herein for two events and examples given for two applications, note that the correlation detector 238 can track, detect, and identify correlations in occurrences of events/transactions, correlations for multiple events (e.g., 2, 3, 4, 5, etc.) that can be detected and identified.
- the correlation detector 238 tracks the timing characteristics of requests made by applications to detect correlations.
- the correlations can be incorporated into an application's profile by the profile generator 239.
- the profile generator includes an application status detector 240.
- the application status detector 240 can detect an activity state of an application on the device 250.
- An activity state can indicate, by way of example but not limitation, whether a specific application is operating in the background or foreground on the mobile device 250, whether the application is active or inactive, whether the application is being interacted with (e.g., by a user, or another application or device).
- the activity state or status of an application on the device 250 can also be included in an application's profile (e.g., by the profile generator 239) along with any correlation with other events or applications and used for data request alignment.
- one embodiment of the alignment module 256 of the traffic shaping engine 255 which is able to use the application behavior (e.g., as determined by the application behavior detector 236) of one or multiple applications on a device 250 to align some of the content requests (e.g., aligned by the alignment module 256) made by the same application or at least a portion the multiple applications from the mobile device over the network.
- the application behaviors can be indicated in application profiles generated by the application profile generator 239, for example.
- the content requests (made by the same application or different applications) are aligned by delaying or expediting a time at which some of the content requests would occur without alignment and the traffic shaping engine 256 can transfer the content requests that are delayed or expedited in a single transfer operation over the network (cellular or other wireless network).
- the amount of time that a request can be delayed (time 'D') is generally determined (e.g. by the delay module 258) to optimize a number of content requests able to be aligned in the single transfer operation.
- delay module 258 can utilize the correlations in event/transaction occurrences within an application or across multiple applications as identified by the correlation detector 238 in determining delay time for aligning multiple requests.
- the delay time 'D' (e.g., refers to the time by which a request is expedited or delayed) is generally determined based on application behavior (e.g., as determined by the application behavior detector 236 and/or indicated in an application profile). More specifically, the time that is delayed in transfer of a given content request can be determined based on priority of a specific application (e.g., as determined by the prioritization engine 241 of the application behavior detector 236) making the given content request, or based on the priority of the specific application relative to other applications on the mobile device 250.
- application behavior e.g., as determined by the application behavior detector 236 and/or indicated in an application profile. More specifically, the time that is delayed in transfer of a given content request can be determined based on priority of a specific application (e.g., as determined by the prioritization engine 241 of the application behavior detector 236) making the given content request, or based on the priority of the specific application relative to other applications on the mobile device 250.
- the delay module 258 can determine delays in transfer further based on, one or more of amount of data involved in the given content request, a nature of data involved in the given content request, usable lifetime of data to be transferred in the given content request, and/or network characteristics including available bandwidth or network latency.
- the local proxy 275 of the device 250 detects a first data request made via a first application and a second data request made via a second application, or where first and second data requests are made by the same application.
- the alignment module 256 of the traffic shaping engine 255 in the local proxy 275 on the device 250 can delay the transfer of the first data transfer request made via the first application to the proxy server (e.g., proxy server 125 or 325 in the examples of FIG. IB and FIG.
- the delay of the first data transfer request can be determined by the delay module 258 and the decision can be made when, for example, the second application is of a higher priority relative to the first application, or that the second application is running in the foreground, or that a user is interacting with the second application and the second data request is initiated in response to the user interaction, or that the second application is more data intensive than the first application.
- FIG. 3 depicts a block diagram illustrating an example of server-side components in a distributed proxy and cache system residing on a host server 300 that manages traffic in a wireless network for resource conservation.
- the host server 300 generally includes, for example, a network interface 308 and/or one or more repositories 312, 314, 316.
- server 300 may be any portable/mobile or non-portable device, server, cluster of computers and/or other types of processing units (e.g., any number of a machine shown in the example of FIG. 11) able to receive, transmit signals to satisfy data requests over a network including any wired or wireless networks (e.g., WiFi, cellular, Bluetooth, etc.).
- wired or wireless networks e.g., WiFi, cellular, Bluetooth, etc.
- the network interface 308 can include networking module(s) or devices(s) that enable the server 300 to mediate data in a network with an entity that is external to the host server 300, through any known and/or convenient communications protocol supported by the host and the external entity. Specifically, the network interface 308 allows the server 308 to communicate with multiple devices including mobile phone devices 350, and/or one or more application servers/content providers 310.
- the host server 300 can store information about connections (e.g., network characteristics, conditions, types of connections, etc.) with devices in the connection metadata repository 312. Additionally, any information about third party application or content providers can also be stored in 312. The host server 300 can store information about devices (e.g., hardware capability, properties, device settings, device language, network capability, manufacturer, device model, OS, OS version, etc.) in the device information repository 314. Additionally, the host server 300 can store information about network providers and the various network service areas in the network service provider repository 316.
- connections e.g., network characteristics, conditions, types of connections, etc.
- devices e.g., hardware capability, properties, device settings, device language, network capability, manufacturer, device model, OS, OS version, etc.
- the host server 300 can store information about network providers and the various network service areas in the network service provider repository 316.
- the communication enabled by 308 allows for simultaneous connections (e.g., including cellular connections) with devices 350 and/or connections (e.g., including wired/wireless, HTTP, Internet connections, LAN, Wifi, etc.) with content servers/providers 310, to manage the traffic between devices 350 and content providers 310, for optimizing network resource utilization and/or to conserver power (battery) consumption on the serviced devices 350.
- the host server 300 can communicate with mobile devices 350 serviced by different network service providers and/or in the same/different network service areas.
- the host server 300 can operate and is compatible with devices 350 with varying types or levels of mobile capabilities, including by way of example but not limitation, 1G, 2G, 2G transitional (2.5G, 2.75G), 3G (IMT-2000), 3G transitional (3.5G, 3.75G, 3.9G), 4G (IMT-advanced), etc.
- the network interface 308 can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G type networks such as , LTE, WiMAX, etc.,), Bluetooth, WiFi, or any other network whether or not connected via a 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.
- a network adaptor card e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G type networks such as , LTE, WiMAX, etc.,
- Bluetooth WiFi
- the host server 300 can further include, server-side components of the distributed proxy and cache system which can include, a proxy server 325 and a server cache 335.
- the server proxy 325 can include an HTTP access engine 345, a caching policy manager 355, a proxy controller 365, a traffic shaping engine 375, a new data detector 386, and/or a connection manager 395.
- the HTTP access engine 345 may further include a heartbeat manager 346, the proxy controller 365 may further include a data invalidator module 366, the traffic shaping engine 375 may further include a control protocol 276 and a batching module 377. Additional or less components/modules/engines can be included in the proxy server 325 and each illustrated component.
- a "module,” “a manager,” a “handler,” a “detector,” an “interface,” a “controller,” 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.
- a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer- readable (storage) medium to be valid.
- Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.
- the request may be intercepted and routed to the proxy server 325, which is coupled to the device 350 and the provider 310.
- the proxy server is able to communicate with the local proxy (e.g., proxy 175 and 275 of the examples of FIG. 1 and FIG. 2 respectively) of the device 350, the local proxy forwards the data request to the proxy server 325 for, in some instances, further processing, and if needed, for transmission to the content server 310 for a response to the data request.
- the local proxy e.g., proxy 175 and 275 of the examples of FIG. 1 and FIG. 2 respectively
- the host 300, or the proxy server 325 in the host server 300 can utilize intelligent information provided by the local proxy in adjusting its communication with the device in such a manner that optimizes use of network and device resources.
- the proxy server 325 can identify characteristics of user activity on the device 350 to modify its communication frequency. The characteristics of user activity can be determined by, for example, the activity/behavior awareness module 366 in the proxy controller 365, via information collected by the local proxy on the device 350.
- communication frequency can be controlled by the connection manager 396 of the proxy server 325, for example, to adjust push frequency of content or updates to the device 350.
- push frequency can be decreased by the connection manager 396 when characteristics of the user activity indicate that the user is inactive.
- the connection manager 396 can adjust the communication frequency with the device 350 to send data that was buffered as a result of decreased communication frequency, to the device 350.
- the proxy server 325 includes priority awareness of various requests, transactions, sessions, applications, and/or specific events. Such awareness can be determined by the local proxy on the device 350 and provided to the proxy server 325.
- the priority awareness module 367 of the proxy server 325 can generally assess the priority (e.g., including time-criticality, time-sensitivity, etc.) of various events or applications; additionally, the priority awareness module 367 can track priorities determined by local proxies of devices 350.
- the connection manager 395 can further modify communication frequency (e.g., use or radio as controlled by the radio controller 396) of the server 300 with the devices 350. For example, the server 300 can notify the device 350, thus requesting use of the radio if it is not already in use, when data or updates of an importance/priority level which meets a criteria becomes available to be sent.
- the proxy server 325 can detect multiple occurrences of events (e.g., transactions, content, data received from server/provider 310) and allow the events to accumulate for batch transfer to device 350. Batch transfer can be cumulated and transfer of events can be delayed based on priority awareness and/or user activity/application behavior awareness, as tracked by modules 366 and/or 367. For example, batch transfer of multiple events (of a lower priority) to the device 350 can be initiated by the batching module 377 when an event of a higher priority (meeting a threshold or criteria) is detected at the server 300. In addition, batch transfer from the server 300 can be triggered when the server receives data from the device 350, indicating that the device radio is already in use and is thus on. In one embodiment, the proxy server 324 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.
- events e.g., transactions, content, data received from server/
- the server 300 caches data (e.g., as managed by the caching policy manager 355) such that communication frequency over a network (e.g., cellular network) with the device 350 can be modified (e.g., decreased).
- the data can be cached, for example in the server cache 335, for subsequent retrieval or batch sending to the device 350 to potentially decrease the need to turn on the device 350 radio.
- the server cache 335 can be partially or wholly internal to the host server 300, although in the example of FIG. 3, it is shown as being external to the host 300. In some instances, the server cache 335 may be the same as and/or integrated in part or in whole with another cache managed by another entity (e.g., the optional caching proxy server 199 shown in the example of FIG. IB), such as being managed by an application server/content provider 110, a network service provider, or another third party.
- another entity e.g., the optional caching proxy server 199 shown in the example of FIG. IB
- content caching is performed locally on the device 350 with the assistance of host server 300.
- proxy server 325 in the host server 300 can query the application server/provider 310 with requests and monitor changes in responses. When changed or new responses are detected (e.g., by the new data detector 347), the proxy server 325 can notify the mobile device 350, such that the local proxy on the device 350 can make the decision to invalidate (e.g., indicated as out-dated) the relevant cache entries stored as any responses in its local cache.
- the data invalidator module 368 can automatically instruct the local proxy of the device 350 to invalidate certain cached data, based on received responses from the application server/provider 310. The cached data is marked as invalid, and can get replaced or deleted when new content is received from the content server 310.
- data change can be detected by the detector 347 in one or more ways.
- the server/provider 310 can notify the host server 300 upon a change.
- the change can also be detected at the host server 300 in response to a direct poll of the source server/provider 310.
- the proxy server 325 can in addition, preload the local cache on the device 350 with the new/updated data. This can be performed when the host server 300 detects that the radio on the mobile device is already in use, or when the server 300 has additional content/data to be sent to the device 350.
- One or more the above mechanisms can be implemented simultaneously or adjusted/configured based on application (e.g., different policies for different servers/providers 310).
- the source provider/server 310 may notify the host 300 for certain types of events (e.g., events meeting a priority threshold level).
- the provider/server 310 may be configured to notify the host 300 at specific time intervals, regardless of event priority.
- the proxy server 325 of the host 300 can monitor/track responses received for the data request from the content source for changed results prior to returning the result to the mobile device, such monitoring may be suitable when data request to the content source has yielded same results to be returned to the mobile device, thus preventing network/power consumption from being used when no new/changes are made to a particular requested.
- the local proxy of the device 350 can instruct the proxy server 325 to perform such monitoring or the proxy server 325 can automatically initiate such a process upon receiving a certain number of the same responses (e.g., or a number of the same responses in a period of time) for a particular request.
- the server 300 for example, through the activity/behavior awareness module 366, is able to identify or detect user activity, at a device that is separate from the mobile device 350.
- the module 366 may detect that a user's message inbox (e.g., email or types of inbox) is being accessed. This can indicate that the user is interacting with his/her application using a device other than the mobile device 350 and may not need frequent updates, if at all.
- a user's message inbox e.g., email or types of inbox
- the server 300 can thus decrease the frequency with which new or updated content is sent to the mobile device 350, or eliminate all communication for as long as the user is detected to be using another device for access.
- Such frequency decrease may be application specific (e.g., for the application with which the user is interacting with on another device), or it may be a general frequency decrease (e.g., since the user is detected to be interacting with one server or one application via another device, he/she could also use it to access other services) to the mobile device 350.
- the host server 300 is able to poll content sources 310 on behalf of devices 350 to conserve power or battery consumption on devices 350. For example, certain applications on the mobile device 350 can poll its respective server 310 in a predictable recurring fashion. Such recurrence or other types of application behaviors can be tracked by the activity/behavior module 366 in the proxy controller 365.
- the host server 300 can thus poll content sources 310 for applications on the mobile device 350, that would otherwise be performed by the device 350 through a wireless (e.g., including cellular connectivity).
- the host server can poll the sources 310 for new or changed data by way of the HTTP access engine 345 to establish HTTP connection or by way of radio controller 396 to connect to the source 310 over the cellular network.
- the new data detector can notify the device 350 that such data is available and/or provide the new/changed data to the device 350.
- the connection manager 395 determines that the mobile device 350 is unavailable (e.g., the radio is turned off) and utilizes SMS to transmit content to the device 350, for instance via the SMSC shown in the example of FIG. IB. SMS is used to transmit invalidation messages, batches of invalidation messages, or even content in the case the content is small enough to fit into just a few (usually one or two) SMS messages. This avoids the need to access the radio channel to send overhead information.
- the host server 300 can use SMS for certain transactions or responses having a priority level above a threshold or otherwise meeting a criteria.
- the server 300 can also utilize SMS as an out-of-band trigger to maintain or wake-up an IP connection as an alternative to maintaining an always-on IP connection.
- connection manager 395 in the proxy server 325 can generate and/or transmit heartbeat messages on behalf of connected devices 350, to maintain a backend connection with a provider 310 for applications running on devices 350.
- local cache on the device 350 can prevent any or all heartbeat messages needed to maintain TCP/IP connections required for applications, from being sent over the cellular, or other network, and instead rely on the proxy server 325 on the host server 300 to generate and/or send the heartbeat messages to maintain a connection with the backend (e.g., app server/provider 110 in the example of FIG. 1).
- the proxy server can generate the keep-alive (heartbeat) messages independent of the operations of the local proxy on the mobile device.
- the repositories 312, 314, and/or 316 can additionally store software, descriptive data, images, system information, drivers, and/or any other data item utilized by other components of the host server 300 and/or any other servers for operation.
- the repositories may be managed by a database management system (DBMS), for example but not limited to, Oracle, DB2, Microsoft Access, Microsoft SQL Server, PostgreSQL, MySQL, FileMaker, etc.
- DBMS database management system
- the repositories can be implemented via object-oriented technology and/or via text files, and can be managed by a distributed database management system, an object- oriented database management system (OODBMS) (e.g., ConceptBase, FastDB Main Memory Database Management System, JDOInstruments, ObjectDB, etc.), an object- relational database management system (ORDBMS) (e.g., Informix, OpenLink Virtuoso, VMDS, etc.), a file system, and/or any other convenient or known database management package.
- OODBMS object- oriented database management system
- ORDBMS object- relational database management system
- FIG. 4A depicts a diagram showing how data requests from a mobile device 450 to an application server/content provider 496 in a wireless network can be coordinated by a distributed proxy system 460 in a manner such that network and battery resources are conserved through using content caching and monitoring performed by the distributed proxy system 460.
- the mobile device 450, or the software widget executing on the device 450 performs a data request 402 (e.g., an HTTP GET, POST, or other request) directly to the application server 495 and receives a response 404 directly from the server/provider 495. If the data has been updated, the widget on the mobile device 450 can refreshes itself to reflect the update and waits for small period of time and initiates another data request to the server/provider 495.
- a data request 402 e.g., an HTTP GET, POST, or other request
- the widget on the mobile device 450 can refreshes itself to reflect the update and waits for small period of time and initiates another data request to the server/provider 495.
- the requesting client or software widget 455 on the device 450 can utilize the distributed proxy system 460 in handling the data request made to server/provider 495.
- the distributed proxy system 460 can include a local proxy 465 (which is typically considered a client-side component of the system 460 and can reside on the mobile device 450), a caching proxy (475, considered a server-side component 470 of the system 460 and can reside on the host server 485 or be wholly or partially external to the host server 485), a host server 485.
- the local proxy 465 can be connected to the proxy 475 and host server 485 via any network or combination of networks.
- the widget 455 can perform the data request 406 via the local proxy 465.
- the local proxy 465 can intercept the requests made by device applications, and can identify the connection type of the request (e.g., an HTTP get request or other types of requests).
- the local proxy 465 can then query the local cache for any previous information about the request (e.g., to determine whether a locally stored response is available and/or still valid). If a locally stored response is not available or if there is an invalid response stored, the local proxy 465 can update or store information about the request, the time it was made, and any additional data, in the local cache. The information can be updated for use in potentially satisfying subsequent requests.
- the local proxy 465 can then send the request to the host server 485 and the server 485 can perform the request 406 and returns the results in response 408.
- the local proxy 465 can store the result and in addition, information about the result and returns the result to the requesting widget 455.
- the local proxy 465 can notify 410 the server 485 that the request should be monitored (e.g., steps 412 and 414) for result changes prior to returning a result to the local proxy 465 or requesting widget 455.
- the local proxy 465 can now store the results into the local cache. Now, when the data request 416, for which a locally response is available, is made by the widget 455 and intercepted at the local proxy 465, the proxy 465 can return the response 418 from the local cache without needing to establish a connection communication over the wireless network.
- the server proxy performs the requests marked for monitoring 420 to determine whether the response 422 for the given request has changed.
- the host server 485 can perform this monitoring independently of the widget 455 or local proxy 465 operations. Whenever an unexpected response 422 is received for a request, the server 485 can notify the local proxy 465 that the response has changed (e.g., the invalidate notification in step 424) and that the locally stored response on the client should be erased or replaced with a new response.
- a subsequent data request 426 by the widget 455 from the device 450 results in the data being returned from host server 485 (e.g., via the caching proxy 475).
- the wireless (cellular) network is intelligently used when the content/data for the widget or software application 455 on the mobile device 450 has actually changed.
- the traffic needed to check for the changes to application data is not performed over the wireless (cellular) network. This reduces the amount of generated network traffic and shortens the total time and the number of times the radio module is powered up on the mobile device 450, thus reducing battery consumption, and in addition, frees up network bandwidth.
- FIG. 4B depicts a timing diagram showing how data requests from a mobile device 450 to an application server/content provider 495 in a wireless network can be aligned at the local proxy 465 in the distributed proxy system 460 to optimize network and radio use.
- the local proxy 465 can determine that the radio on the mobile device 450 is currently off and decide to wait to transfer the request A 432 over the network.
- the proxy 465 can determine (e.g., based on conditions and/or processes illustrated in the flow charts in the examples of FIG. 6-10) whether to transfer the data request B 434 and/or whether also to transfer the impending data request A 432.
- the local proxy 465 does not transfer data requests A and B until data request C436 is detected at the device 450 by the proxy 465.
- the time 'Dl' 433 with which request A 432 and time T>2' 435 with which request B 434 are delayed, can be determined by the local proxy 465 (e.g., as described in conjunction with the traffic shaping module and delay module in the example of FIG. 2B).
- the radio can be turned on when request C 436 is received and data transfers for requests A, B, and C 438 can be aligned at this point to be transferred to the host server 480 on the server- side 470 of the distributed proxy 460 which can forward the request to the server/provider 495, immediately in transfer 440, or possibly with some delay, in transfer 442.
- the data requests A, B, and C can all originate from the same application or different applications on the mobile device 450.
- FIG. 5 depicts a diagram showing one example process for implementing a hybrid IP and SMS power saving mode on a mobile device 550 using a distributed proxy and cache system (e.g., such as the distributed system shown in the example of FIG. IB).
- a distributed proxy and cache system e.g., such as the distributed system shown in the example of FIG. IB.
- the local proxy (e.g., proxy 175 in the example of FIG. IB) monitors the device for user activity.
- server push is active. For example, always-on-push IP connection can be maintained and if available, SMS triggers can be immediately sent to the mobile device 550 as it becomes available.
- the local proxy can adjust the device to go into the power saving mode.
- the local proxy receives a message or a correspondence from a remote proxy (e.g., the server proxy 135 in the example of FIG. IB) on the server-side of the distributed proxy and cache system
- the local proxy can respond with a call indicating that the device 550 is currently in power save mode (e.g., via a power save remote procedure call).
- the local proxy take the opportunity to notify multiple accounts or providers (e.g., 51 OA, and 51 OB) of the current power save status (e.g., timed to use the same radio power-on event).
- the response from the local proxy can include a time (e.g., the power save period) indicating to the remote proxy (e.g., server proxy 135) and/or the app server/providers 510A/B when the device 550 is next able to receive changes or additional data.
- a default power savings period can be set by the local proxy. Consecutive power saving periods can increase in duration. For example, if a first power saving period has elapsed without an activity occurring, the device 550 can continue into a second power saving mode with a longer time period (e.g., see periods one 503 and period two 505). In general, any activity on the device takes the client out of power saving mode and ends that particular power save event.
- the wait period communicated to the servers 510A/B can be the existing period, rather than an incremented time period.
- the next wait period communicated in step 508 to servers 510A/B is again the same time saving period.
- the remote proxy server upon receipt of power save notification from the device 550, can stop sending changes (data or SMS's) for the period of time requested (the wait period). At the end of the wait period, any notifications received can be acted upon and changes sent to the device 550 as a single batched event.
- the proxy server can start the poll or data collect event earlier (before the end of a power save period) in order to increase the chance that the client will receive data at the next radio power on event.
- the device 550 whenever new data or content comes into the device 550 while it is in a power saving mode, it can respond with the power saving remote procedure call to all end points currently registered (e.g., server/providers 510A/B).
- the wait period can be updated in operation in real time to accommodate operating conditions. For example, as the mobile device 550 sends additional power saving calls (e.g., with updated wait times) if multiple servers 510A/B or others, respond to the end of a wait period with different delays, the local proxy can adjust the wait period on the fly to accommodate the different delays.
- Detection of user activity 512 at the device 550 causes the power save mode to be exited.
- the device 550 When the device 550 exits power save mode, it can send power save cancel call to the proxy server and immediately receives any changes associated with any pending notifications. This may require a poll to be run by the proxy server after receiving the power saving cancel call. If the latest power saving period has expired, then no power save cancel call may be needed as the proxy server will already be in traditional push operation mode.
- power save mode is not applied when the device 550 is plugged into a charger.
- This setting can be reconfigured or adjusted by the user or another party.
- the power save mode can be turned on and off, for example, by the user via a user interface on device 550.
- timing of power events to receive data can be synced with any power save calls to optimize radio use.
- FIG. 6 depicts a flow chart illustrating example selection processes through which data transfer requests of multiple applications can be coordinated into a single transfer operation.
- a first data transfer request initiated by a first application on a device or mobile device is received.
- One or more selection processes can be performed to determine whether to delay transfer of the first data transfer request, as shown in steps 604-608, including, determining whether the user is interacting with the first application, whether the first application is in the foreground, or whether the radio of the mobile device on which the request is initiated is already on. Note that although the selection processes are illustrated and identified in a specific order, the order in which the system checks for applicability is not limited to such, any of the above conditions can be checked in any ordering or any combination with one of the other conditions.
- process 610 in general, a decision can be made to transfer the data request over the wireless (cellular or others) network, or to power on the radio (e.g., via the radio controller 256 shown in the example of FIG. 2A) to perform the transfer without or with minimal delay. Additional conditions that are not shown here which may cause the transfer of the data request to occur immediately or upon receipt may be included. [00182] If none of the conditions in 604-608 applies (or other suitable conditions depending on the specific implementation), in process 612, the transfer of the first data transfer request can be delayed. In process 614, it is determined whether another data transfer request has been initiated. If not, the process continues at flow 'A' in FIG. 7.
- the system performs one or more of several condition checks shown in decision flows 616-624 including determining whether the second application is of higher priority than the first application, whether the second application running in the foreground, whether the user interacting with the second application, whether the other data request initiated in response to user interaction, and/or whether the second application is more data intensive than the first application.
- condition checks shown in decision flows 616-624 including determining whether the second application is of higher priority than the first application, whether the second application running in the foreground, whether the user interacting with the second application, whether the other data request initiated in response to user interaction, and/or whether the second application is more data intensive than the first application.
- the flow chart continues at ' ⁇ ' in FIG. 7 if none of the above conditions apply.
- process 626 the first data transfer request of the first application and the other data transfer request of the second application are transferred in a single transfer operation over the network. Note that the conditions shown in 616-624 can be applied in any order or any combination with one another, although illustrated in the example flow chart as having a particular order.
- FIG. 7 depicts an example of triggering events that would cause a data request to be transferred without alignment with another data request.
- processes 702-710 can occur independently or in conjunction with one another and cause the data request to be transferred over the wireless network without or with minimal delay upon occurrences of these events.
- the mobile device radio is turned on due to another event.
- a certain time period has elapsed, in process 706, a user trigger is detected, and/or the first application exits in process 708 and/or moves into the background in process 710.
- n process 721 the data request is transferred over the wireless (cellular or others) network.
- FIG. 8 depicts a flow chart illustrating an example process for using timing characteristics of data requests made by individual applications to delay transfer of one or more of the data requests made by one of the individual applications.
- processes 802 and 804 data transfer requests made by first and second application on the mobile device are tracked.
- the transaction/request manager 235 of the local proxy 275 shown in the example of FIG. 2A can detect the occurrence of the data transfer requests and request that the application behavior detector 236 begin to track correlations or other types of behaviors of the requesting applications.
- a first timing characteristic of data transfer requests made by the first application is determined and in process 808, a second timing characteristic of data transfer requests made by the second application is determined, and can be used, for example, by the correlation detector 238 to identify any correlations in the requests.
- the transfer of the first data request can be delayed using the first and second timing characteristics or in process 812, the transfer of the second data request can be delayed using the first and second timing characteristics.
- Such delay e.g., determined by the delay module 258 of the local proxy shown in the example of FIG. 2B
- the delays can be until another event occurs, until a manual (user) trigger is detected, or after a certain amount of time, or when another triggering event (e.g., user interaction) occurs.
- the delays are user-configurable and can be tracked and factored into consideration by the delay module 258.
- FIG. 9 depicts a flow chart illustrating an example process for using application behavior of multiple applications to align their content requests made over the network.
- process 902 application behavior of multiple applications are detected on a mobile device.
- the behaviors of any number of applications on the mobile device that are detected can be tracked. Any or all mobile applications on a device can be monitored for the potential for its requests to be aligned for traffic coordination.
- the user can select the applications to be aligned, or specify applications not to be tracked for traffic coordination.
- the device platform, manufacturer, OS settings, and/or network provider may have additional specifications or conditions for aligning traffic requests and selection of applications for traffic coordination.
- process 904 some of the content requests made by at least a portion the multiple applications from the mobile device over the network, are aligned.
- Process flow continues to step 'B' as shown in the example of FIG. 10 which depicts an example of processes through which the time of delay 'D' for content requests can be determined to align content requests over the wireless network.
- process 906 some of the content requests that are delayed in a single transfer operation are transferred over the network.
- Example processes applied to determine delay time 'D' include, by way of example but not limitation: Determine priority of a specific application or priority of the application relative to other applications in process 1002, Determine an amount of data involved in a given content request in step 1004, Determine the useable lifetime of data to be transferred in the content request in step 1006, Determine a nature of data involved in a given content request in step 1008, Determine a status of the application making the content request in step 1010, and/or Determine the network characteristics when the request is made in step 1012. Any number of the above conditions can be applied in any order. Additional conditions which can be used may not be illustrated in the example above. In process 1014, any u ser configuration or overriding settings can be factored into consideration in determining delay to align content request, in process 1016.
- FIG. 11 shows a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.
- the machine operates as a standalone device or may be connected (e.g., networked) to other machines.
- the machine may operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.
- the machine may be a server computer, a client computer, a personal computer (PC), a user device, a tablet PC, a laptop computer, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, an iPhone, an iPad, a Blackberry, a processor, a telephone, a web appliance, a network router, switch or bridge, a console, a hand-held console, a (hand-held) gaming device, a music player, any portable, mobile, hand-held device, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.
- PC personal computer
- PDA personal digital assistant
- machine-readable medium or machine-readable storage medium is shown in an exemplary embodiment to be a single medium, the term “machine-readable medium” and “machine-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions.
- the term “machine- readable medium” and “machine-readable storage medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the presently disclosed technique and innovation.
- routines executed to implement the embodiments of the disclosure may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as "computer programs.”
- the computer programs typically comprise one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processing units or processors in a computer, cause the computer to perform operations to execute elements involving the various aspects of the disclosure.
- machine-readable storage media machine-readable media, or computer-readable (storage) media
- recordable type media such as volatile and non-volatile memory devices, floppy and other removable disks, hard disk drives, optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), among others, and transmission type media such as digital and analog communication links.
- CD ROMS Compact Disk Read-Only Memory
- DVDs Digital Versatile Disks
- transmission type media such as digital and analog communication links.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Mobile Radio Communication Systems (AREA)
- Information Transfer Between Computers (AREA)
Abstract
L'invention porte sur des systèmes et sur des procédés pour une coordination de trafic de réseau mobile entre de multiples applications. Selon un aspect, des modes de réalisation de la présente invention comprennent un système de mandataire et de cache distribué, comprenant un mandataire local sur un dispositif mobile pour intercepter une requête de données effectuée par l'intermédiaire d'un dispositif mobile, et un serveur de mandataire couplé au dispositif mobile et à un serveur de contenu vers lequel la requête de données est dirigée. Un mode de réalisation consiste à retarder le transfert d'une première requête de transfert de données, initiée par une première application, jusqu'à ce qu'une autre requête de transfert de données initiée par une seconde application soit détectée sur le dispositif mobile et à transférer la première requête de transfert de données de la première application et l'autre requête de transfert de données de la seconde application en une seule opération de transfert sur le réseau.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
FI20125102A FI20125102L (fi) | 2010-07-26 | 2012-01-31 | Matkaviestinverkon liikenteen koordinointi usean sovelluksen ylitse |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/115,631 US9043433B2 (en) | 2010-07-26 | 2011-05-25 | Mobile network traffic coordination across multiple applications |
US13/115,631 | 2011-05-25 | ||
US13/355,443 US9049179B2 (en) | 2010-07-26 | 2012-01-20 | Mobile network traffic coordination across multiple applications |
US13/355,443 | 2012-01-20 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012161751A1 true WO2012161751A1 (fr) | 2012-11-29 |
Family
ID=47222390
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2012/022121 WO2012161751A1 (fr) | 2010-07-26 | 2012-01-20 | Coordination de trafic de réseau mobile entre de multiples applications |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2012161751A1 (fr) |
Cited By (50)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8412675B2 (en) | 2005-08-01 | 2013-04-02 | Seven Networks, Inc. | Context aware data presentation |
US8417823B2 (en) | 2010-11-22 | 2013-04-09 | Seven Network, Inc. | Aligning data transfer to optimize connections established for transmission over a wireless network |
US8438633B1 (en) | 2005-04-21 | 2013-05-07 | Seven Networks, Inc. | Flexible real-time inbox access |
US8468126B2 (en) | 2005-08-01 | 2013-06-18 | Seven Networks, Inc. | Publishing data in an information community |
US8484314B2 (en) | 2010-11-01 | 2013-07-09 | Seven Networks, Inc. | Distributed caching in a wireless network of content delivered for a mobile application over a long-held request |
US8494510B2 (en) | 2008-06-26 | 2013-07-23 | Seven Networks, Inc. | Provisioning applications for a mobile device |
US8561086B2 (en) | 2005-03-14 | 2013-10-15 | Seven Networks, Inc. | System and method for executing commands that are non-native to the native environment of a mobile device |
US8621075B2 (en) | 2011-04-27 | 2013-12-31 | Seven Metworks, Inc. | Detecting and preserving state for satisfying application requests in a distributed proxy and cache system |
US8693494B2 (en) | 2007-06-01 | 2014-04-08 | Seven Networks, Inc. | Polling |
US8700728B2 (en) | 2010-11-01 | 2014-04-15 | Seven Networks, Inc. | Cache defeat detection and caching of content addressed by identifiers intended to defeat cache |
US8738050B2 (en) | 2007-12-10 | 2014-05-27 | Seven Networks, Inc. | Electronic-mail filtering for mobile devices |
US8750123B1 (en) | 2013-03-11 | 2014-06-10 | Seven Networks, Inc. | Mobile device equipped with mobile network congestion recognition to make intelligent decisions regarding connecting to an operator network |
US8761756B2 (en) | 2005-06-21 | 2014-06-24 | Seven Networks International Oy | Maintaining an IP connection in a mobile network |
US8775631B2 (en) | 2012-07-13 | 2014-07-08 | Seven Networks, Inc. | Dynamic bandwidth adjustment for browsing or streaming activity in a wireless network based on prediction of user behavior when interacting with mobile applications |
US8774844B2 (en) | 2007-06-01 | 2014-07-08 | Seven Networks, Inc. | Integrated messaging |
US8787947B2 (en) | 2008-06-18 | 2014-07-22 | Seven Networks, Inc. | Application discovery on mobile devices |
US8799410B2 (en) | 2008-01-28 | 2014-08-05 | Seven Networks, Inc. | System and method of a relay server for managing communications and notification between a mobile device and a web access server |
US8811952B2 (en) | 2002-01-08 | 2014-08-19 | Seven Networks, Inc. | Mobile device power management in data synchronization over a mobile network with or without a trigger notification |
US8812695B2 (en) | 2012-04-09 | 2014-08-19 | Seven Networks, Inc. | Method and system for management of a virtual network connection without heartbeat messages |
US8832228B2 (en) | 2011-04-27 | 2014-09-09 | Seven Networks, Inc. | System and method for making requests on behalf of a mobile device based on atomic processes for mobile network traffic relief |
US8838783B2 (en) | 2010-07-26 | 2014-09-16 | Seven Networks, Inc. | Distributed caching for resource and mobile network traffic management |
US8843153B2 (en) | 2010-11-01 | 2014-09-23 | Seven Networks, Inc. | Mobile traffic categorization and policy for network use optimization while preserving user experience |
US8862657B2 (en) | 2008-01-25 | 2014-10-14 | Seven Networks, Inc. | Policy based content service |
US8861354B2 (en) | 2011-12-14 | 2014-10-14 | Seven Networks, Inc. | Hierarchies and categories for management and deployment of policies for distributed wireless traffic optimization |
US8868753B2 (en) | 2011-12-06 | 2014-10-21 | Seven Networks, Inc. | System of redundantly clustered machines to provide failover mechanisms for mobile traffic management and network resource conservation |
US8874761B2 (en) | 2013-01-25 | 2014-10-28 | Seven Networks, Inc. | Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols |
US8903954B2 (en) | 2010-11-22 | 2014-12-02 | Seven Networks, Inc. | Optimization of resource polling intervals to satisfy mobile device requests |
US8909759B2 (en) | 2008-10-10 | 2014-12-09 | Seven Networks, Inc. | Bandwidth measurement |
US8909202B2 (en) | 2012-01-05 | 2014-12-09 | Seven Networks, Inc. | Detection and management of user interactions with foreground applications on a mobile device in distributed caching |
US8934414B2 (en) | 2011-12-06 | 2015-01-13 | Seven Networks, Inc. | Cellular or WiFi mobile traffic optimization based on public or private network destination |
US8984581B2 (en) | 2011-07-27 | 2015-03-17 | Seven Networks, Inc. | Monitoring mobile application activities for malicious traffic on a mobile device |
US9002828B2 (en) | 2007-12-13 | 2015-04-07 | Seven Networks, Inc. | Predictive content delivery |
US9009250B2 (en) | 2011-12-07 | 2015-04-14 | Seven Networks, Inc. | Flexible and dynamic integration schemas of a traffic management system with various network operators for network traffic alleviation |
US9021021B2 (en) | 2011-12-14 | 2015-04-28 | Seven Networks, Inc. | Mobile network reporting and usage analytics system and method aggregated using a distributed traffic optimization system |
US9043433B2 (en) | 2010-07-26 | 2015-05-26 | Seven Networks, Inc. | Mobile network traffic coordination across multiple applications |
US9055102B2 (en) | 2006-02-27 | 2015-06-09 | Seven Networks, Inc. | Location-based operations and messaging |
US9065765B2 (en) | 2013-07-22 | 2015-06-23 | Seven Networks, Inc. | Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network |
US9084105B2 (en) | 2011-04-19 | 2015-07-14 | Seven Networks, Inc. | Device resources sharing for network resource conservation |
US9161258B2 (en) | 2012-10-24 | 2015-10-13 | Seven Networks, Llc | Optimized and selective management of policy deployment to mobile clients in a congested network to prevent further aggravation of network congestion |
US9173128B2 (en) | 2011-12-07 | 2015-10-27 | Seven Networks, Llc | Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol |
US9203864B2 (en) | 2012-02-02 | 2015-12-01 | Seven Networks, Llc | Dynamic categorization of applications for network access in a mobile network |
US9251193B2 (en) | 2003-01-08 | 2016-02-02 | Seven Networks, Llc | Extending user relationships |
US9271238B2 (en) | 2013-01-23 | 2016-02-23 | Seven Networks, Llc | Application or context aware fast dormancy |
US9307493B2 (en) | 2012-12-20 | 2016-04-05 | Seven Networks, Llc | Systems and methods for application management of mobile device radio state promotion and demotion |
US9325662B2 (en) | 2011-01-07 | 2016-04-26 | Seven Networks, Llc | System and method for reduction of mobile network traffic used for domain name system (DNS) queries |
US9326189B2 (en) | 2012-02-03 | 2016-04-26 | Seven Networks, Llc | User as an end point for profiling and optimizing the delivery of content and data in a wireless network |
US9832095B2 (en) | 2011-12-14 | 2017-11-28 | Seven Networks, Llc | Operation modes for mobile traffic optimization and concurrent management of optimized and non-optimized traffic |
EP3235337A4 (fr) * | 2014-12-19 | 2018-07-18 | Intel Corporation | Mandataire de réseau pour une diffusion en continu de vidéo écoénergétique sur des dispositifs mobiles |
US10263899B2 (en) | 2012-04-10 | 2019-04-16 | Seven Networks, Llc | Enhanced customer service for mobile carriers using real-time and historical mobile application and traffic or optimization data associated with mobile devices in a mobile network |
US10803317B2 (en) | 2017-03-21 | 2020-10-13 | Nokia Technologies Oy | Media rendering |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050170776A1 (en) * | 2002-06-07 | 2005-08-04 | David Siorpaes | Wireless technology co-existence |
KR20060068186A (ko) * | 2004-12-16 | 2006-06-21 | 주식회사 팬택 | 어플리케이션 속성에 따른 트래픽 데이터 전송속도의 자동설정을 위한 이동통신 단말기 및 방법 |
KR20070102091A (ko) * | 2006-04-13 | 2007-10-18 | 엘지전자 주식회사 | 이동통신 단말기의 채널 관리 장치 및 방법 |
US20080104666A1 (en) * | 2006-11-01 | 2008-05-01 | Microsoft Corporation | Securing Distributed Application Information Delivery |
-
2012
- 2012-01-20 WO PCT/US2012/022121 patent/WO2012161751A1/fr active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050170776A1 (en) * | 2002-06-07 | 2005-08-04 | David Siorpaes | Wireless technology co-existence |
KR20060068186A (ko) * | 2004-12-16 | 2006-06-21 | 주식회사 팬택 | 어플리케이션 속성에 따른 트래픽 데이터 전송속도의 자동설정을 위한 이동통신 단말기 및 방법 |
KR20070102091A (ko) * | 2006-04-13 | 2007-10-18 | 엘지전자 주식회사 | 이동통신 단말기의 채널 관리 장치 및 방법 |
US20080104666A1 (en) * | 2006-11-01 | 2008-05-01 | Microsoft Corporation | Securing Distributed Application Information Delivery |
Cited By (65)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8811952B2 (en) | 2002-01-08 | 2014-08-19 | Seven Networks, Inc. | Mobile device power management in data synchronization over a mobile network with or without a trigger notification |
US9251193B2 (en) | 2003-01-08 | 2016-02-02 | Seven Networks, Llc | Extending user relationships |
US8561086B2 (en) | 2005-03-14 | 2013-10-15 | Seven Networks, Inc. | System and method for executing commands that are non-native to the native environment of a mobile device |
US8438633B1 (en) | 2005-04-21 | 2013-05-07 | Seven Networks, Inc. | Flexible real-time inbox access |
US8839412B1 (en) | 2005-04-21 | 2014-09-16 | Seven Networks, Inc. | Flexible real-time inbox access |
US8761756B2 (en) | 2005-06-21 | 2014-06-24 | Seven Networks International Oy | Maintaining an IP connection in a mobile network |
US8468126B2 (en) | 2005-08-01 | 2013-06-18 | Seven Networks, Inc. | Publishing data in an information community |
US8412675B2 (en) | 2005-08-01 | 2013-04-02 | Seven Networks, Inc. | Context aware data presentation |
US9055102B2 (en) | 2006-02-27 | 2015-06-09 | Seven Networks, Inc. | Location-based operations and messaging |
US8693494B2 (en) | 2007-06-01 | 2014-04-08 | Seven Networks, Inc. | Polling |
US8805425B2 (en) | 2007-06-01 | 2014-08-12 | Seven Networks, Inc. | Integrated messaging |
US8774844B2 (en) | 2007-06-01 | 2014-07-08 | Seven Networks, Inc. | Integrated messaging |
US8738050B2 (en) | 2007-12-10 | 2014-05-27 | Seven Networks, Inc. | Electronic-mail filtering for mobile devices |
US9002828B2 (en) | 2007-12-13 | 2015-04-07 | Seven Networks, Inc. | Predictive content delivery |
US8862657B2 (en) | 2008-01-25 | 2014-10-14 | Seven Networks, Inc. | Policy based content service |
US8799410B2 (en) | 2008-01-28 | 2014-08-05 | Seven Networks, Inc. | System and method of a relay server for managing communications and notification between a mobile device and a web access server |
US8838744B2 (en) | 2008-01-28 | 2014-09-16 | Seven Networks, Inc. | Web-based access to data objects |
US8787947B2 (en) | 2008-06-18 | 2014-07-22 | Seven Networks, Inc. | Application discovery on mobile devices |
US8494510B2 (en) | 2008-06-26 | 2013-07-23 | Seven Networks, Inc. | Provisioning applications for a mobile device |
US8909759B2 (en) | 2008-10-10 | 2014-12-09 | Seven Networks, Inc. | Bandwidth measurement |
US9043433B2 (en) | 2010-07-26 | 2015-05-26 | Seven Networks, Inc. | Mobile network traffic coordination across multiple applications |
US9049179B2 (en) | 2010-07-26 | 2015-06-02 | Seven Networks, Inc. | Mobile network traffic coordination across multiple applications |
US8838783B2 (en) | 2010-07-26 | 2014-09-16 | Seven Networks, Inc. | Distributed caching for resource and mobile network traffic management |
US8782222B2 (en) | 2010-11-01 | 2014-07-15 | Seven Networks | Timing of keep-alive messages used in a system for mobile network resource conservation and optimization |
US8700728B2 (en) | 2010-11-01 | 2014-04-15 | Seven Networks, Inc. | Cache defeat detection and caching of content addressed by identifiers intended to defeat cache |
US8484314B2 (en) | 2010-11-01 | 2013-07-09 | Seven Networks, Inc. | Distributed caching in a wireless network of content delivered for a mobile application over a long-held request |
US8843153B2 (en) | 2010-11-01 | 2014-09-23 | Seven Networks, Inc. | Mobile traffic categorization and policy for network use optimization while preserving user experience |
US8903954B2 (en) | 2010-11-22 | 2014-12-02 | Seven Networks, Inc. | Optimization of resource polling intervals to satisfy mobile device requests |
US9100873B2 (en) | 2010-11-22 | 2015-08-04 | Seven Networks, Inc. | Mobile network background traffic data management |
US8417823B2 (en) | 2010-11-22 | 2013-04-09 | Seven Network, Inc. | Aligning data transfer to optimize connections established for transmission over a wireless network |
US8539040B2 (en) | 2010-11-22 | 2013-09-17 | Seven Networks, Inc. | Mobile network background traffic data management with optimized polling intervals |
US9325662B2 (en) | 2011-01-07 | 2016-04-26 | Seven Networks, Llc | System and method for reduction of mobile network traffic used for domain name system (DNS) queries |
US9084105B2 (en) | 2011-04-19 | 2015-07-14 | Seven Networks, Inc. | Device resources sharing for network resource conservation |
US9300719B2 (en) | 2011-04-19 | 2016-03-29 | Seven Networks, Inc. | System and method for a mobile device to use physical storage of another device for caching |
US8832228B2 (en) | 2011-04-27 | 2014-09-09 | Seven Networks, Inc. | System and method for making requests on behalf of a mobile device based on atomic processes for mobile network traffic relief |
US8621075B2 (en) | 2011-04-27 | 2013-12-31 | Seven Metworks, Inc. | Detecting and preserving state for satisfying application requests in a distributed proxy and cache system |
US8984581B2 (en) | 2011-07-27 | 2015-03-17 | Seven Networks, Inc. | Monitoring mobile application activities for malicious traffic on a mobile device |
US8977755B2 (en) | 2011-12-06 | 2015-03-10 | Seven Networks, Inc. | Mobile device and method to utilize the failover mechanism for fault tolerance provided for mobile traffic management and network/device resource conservation |
US8934414B2 (en) | 2011-12-06 | 2015-01-13 | Seven Networks, Inc. | Cellular or WiFi mobile traffic optimization based on public or private network destination |
US8868753B2 (en) | 2011-12-06 | 2014-10-21 | Seven Networks, Inc. | System of redundantly clustered machines to provide failover mechanisms for mobile traffic management and network resource conservation |
US9173128B2 (en) | 2011-12-07 | 2015-10-27 | Seven Networks, Llc | Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol |
US9009250B2 (en) | 2011-12-07 | 2015-04-14 | Seven Networks, Inc. | Flexible and dynamic integration schemas of a traffic management system with various network operators for network traffic alleviation |
US9277443B2 (en) | 2011-12-07 | 2016-03-01 | Seven Networks, Llc | Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol |
US9208123B2 (en) | 2011-12-07 | 2015-12-08 | Seven Networks, Llc | Mobile device having content caching mechanisms integrated with a network operator for traffic alleviation in a wireless network and methods therefor |
US9832095B2 (en) | 2011-12-14 | 2017-11-28 | Seven Networks, Llc | Operation modes for mobile traffic optimization and concurrent management of optimized and non-optimized traffic |
US9021021B2 (en) | 2011-12-14 | 2015-04-28 | Seven Networks, Inc. | Mobile network reporting and usage analytics system and method aggregated using a distributed traffic optimization system |
US8861354B2 (en) | 2011-12-14 | 2014-10-14 | Seven Networks, Inc. | Hierarchies and categories for management and deployment of policies for distributed wireless traffic optimization |
US9131397B2 (en) | 2012-01-05 | 2015-09-08 | Seven Networks, Inc. | Managing cache to prevent overloading of a wireless network due to user activity |
US8909202B2 (en) | 2012-01-05 | 2014-12-09 | Seven Networks, Inc. | Detection and management of user interactions with foreground applications on a mobile device in distributed caching |
US9203864B2 (en) | 2012-02-02 | 2015-12-01 | Seven Networks, Llc | Dynamic categorization of applications for network access in a mobile network |
US9326189B2 (en) | 2012-02-03 | 2016-04-26 | Seven Networks, Llc | User as an end point for profiling and optimizing the delivery of content and data in a wireless network |
US8812695B2 (en) | 2012-04-09 | 2014-08-19 | Seven Networks, Inc. | Method and system for management of a virtual network connection without heartbeat messages |
US10263899B2 (en) | 2012-04-10 | 2019-04-16 | Seven Networks, Llc | Enhanced customer service for mobile carriers using real-time and historical mobile application and traffic or optimization data associated with mobile devices in a mobile network |
US8775631B2 (en) | 2012-07-13 | 2014-07-08 | Seven Networks, Inc. | Dynamic bandwidth adjustment for browsing or streaming activity in a wireless network based on prediction of user behavior when interacting with mobile applications |
US9161258B2 (en) | 2012-10-24 | 2015-10-13 | Seven Networks, Llc | Optimized and selective management of policy deployment to mobile clients in a congested network to prevent further aggravation of network congestion |
US9307493B2 (en) | 2012-12-20 | 2016-04-05 | Seven Networks, Llc | Systems and methods for application management of mobile device radio state promotion and demotion |
US9271238B2 (en) | 2013-01-23 | 2016-02-23 | Seven Networks, Llc | Application or context aware fast dormancy |
US8874761B2 (en) | 2013-01-25 | 2014-10-28 | Seven Networks, Inc. | Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols |
US8750123B1 (en) | 2013-03-11 | 2014-06-10 | Seven Networks, Inc. | Mobile device equipped with mobile network congestion recognition to make intelligent decisions regarding connecting to an operator network |
US9065765B2 (en) | 2013-07-22 | 2015-06-23 | Seven Networks, Inc. | Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network |
EP3235337A4 (fr) * | 2014-12-19 | 2018-07-18 | Intel Corporation | Mandataire de réseau pour une diffusion en continu de vidéo écoénergétique sur des dispositifs mobiles |
US10673914B2 (en) | 2014-12-19 | 2020-06-02 | Intel Corporation | Network proxy for energy efficient video streaming on mobile devices |
US11252208B2 (en) | 2014-12-19 | 2022-02-15 | Intel Corporation | Network proxy for energy efficient video streaming on mobile devices |
US11770428B2 (en) | 2014-12-19 | 2023-09-26 | Intel Corporation | Network proxy for energy efficient video streaming on mobile devices |
US10803317B2 (en) | 2017-03-21 | 2020-10-13 | Nokia Technologies Oy | Media rendering |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9049179B2 (en) | Mobile network traffic coordination across multiple applications | |
US9503544B2 (en) | Mobile application traffic optimization | |
US9681387B2 (en) | Mobile traffic optimization and coordination and user experience enhancement | |
CA2806557C (fr) | Optimisation du trafic d'applications mobiles | |
CA2806550C (fr) | Mise en memoire cache distribuee pour la gestion des ressources et du trafic sur un reseau mobile | |
WO2012161751A1 (fr) | Coordination de trafic de réseau mobile entre de multiples applications |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 20125102 Country of ref document: FI |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12789296 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 12789296 Country of ref document: EP Kind code of ref document: A1 |