US20140177497A1 - Management of mobile device radio state promotion and demotion - Google PatentsManagement of mobile device radio state promotion and demotion Download PDF
- Publication number
- US20140177497A1 US20140177497A1 US13/844,682 US201313844682A US2014177497A1 US 20140177497 A1 US20140177497 A1 US 20140177497A1 US 201313844682 A US201313844682 A US 201313844682A US 2014177497 A1 US2014177497 A1 US 2014177497A1
- United States
- Prior art keywords
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- 230000004044 response Effects 0.000 claims description 295
- 230000000694 effects Effects 0.000 claims description 111
- 230000005540 biological transmission Effects 0.000 claims description 21
- 230000003044 adaptive Effects 0.000 claims description 7
- 241000760358 Enodes Species 0.000 abstract 1
- 230000006399 behavior Effects 0.000 description 66
- 238000010586 diagram Methods 0.000 description 38
- 230000015654 memory Effects 0.000 description 29
- 238000000034 method Methods 0.000 description 27
- 230000001413 cellular Effects 0.000 description 24
- 238000004891 communication Methods 0.000 description 23
- 239000000203 mixture Substances 0.000 description 19
- 238000007493 shaping process Methods 0.000 description 17
- 206010046306 Upper respiratory tract infection Diseases 0.000 description 16
- 230000002452 interceptive Effects 0.000 description 16
- 238000001514 detection method Methods 0.000 description 14
- 238000005516 engineering process Methods 0.000 description 13
- 230000001965 increased Effects 0.000 description 12
- 230000002085 persistent Effects 0.000 description 12
- 230000003993 interaction Effects 0.000 description 10
- 230000000670 limiting Effects 0.000 description 10
- 239000000969 carrier Substances 0.000 description 9
- 230000003247 decreasing Effects 0.000 description 8
- 230000001737 promoting Effects 0.000 description 8
- 230000011664 signaling Effects 0.000 description 8
- 230000001934 delay Effects 0.000 description 7
- 230000001419 dependent Effects 0.000 description 7
- 230000035945 sensitivity Effects 0.000 description 7
- 230000000875 corresponding Effects 0.000 description 5
- 238000005457 optimization Methods 0.000 description 5
- 235000010384 tocopherol Nutrition 0.000 description 5
- 235000019731 tricalcium phosphate Nutrition 0.000 description 5
- 230000003466 anti-cipated Effects 0.000 description 4
- 230000001808 coupling Effects 0.000 description 4
- 238000010168 coupling process Methods 0.000 description 4
- 238000005859 coupling reaction Methods 0.000 description 4
- 230000003068 static Effects 0.000 description 4
- 241001067407 Cometes Species 0.000 description 3
- 230000005059 dormancy Effects 0.000 description 3
- 238000011068 load Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000006011 modification reaction Methods 0.000 description 3
- 230000003287 optical Effects 0.000 description 3
- 230000001629 suppression Effects 0.000 description 3
- 230000001960 triggered Effects 0.000 description 3
- 230000001955 cumulated Effects 0.000 description 2
- 230000003111 delayed Effects 0.000 description 2
- 230000002708 enhancing Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 230000035755 proliferation Effects 0.000 description 2
- 230000002104 routine Effects 0.000 description 2
- 238000004088 simulation Methods 0.000 description 2
- 230000007958 sleep Effects 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 241001071864 Lethrinus laticaudis Species 0.000 description 1
- 235000009074 Phytolacca americana Nutrition 0.000 description 1
- 240000007643 Phytolacca americana Species 0.000 description 1
- 230000002411 adverse Effects 0.000 description 1
- 230000003542 behavioural Effects 0.000 description 1
- 230000001010 compromised Effects 0.000 description 1
- 230000001276 controlling effect Effects 0.000 description 1
- 230000001809 detectable Effects 0.000 description 1
- 230000001627 detrimental Effects 0.000 description 1
- 238000003379 elimination reaction Methods 0.000 description 1
- 230000000977 initiatory Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000000051 modifying Effects 0.000 description 1
- 230000000737 periodic Effects 0.000 description 1
- 230000036316 preload Effects 0.000 description 1
- 238000004321 preservation Methods 0.000 description 1
- 230000002829 reduced Effects 0.000 description 1
- 230000003252 repetitive Effects 0.000 description 1
- 238000001228 spectrum Methods 0.000 description 1
- 238000007619 statistical method Methods 0.000 description 1
- 239000000126 substance Substances 0.000 description 1
- 230000001360 synchronised Effects 0.000 description 1
- 230000002123 temporal effect Effects 0.000 description 1
- 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
- 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/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
- H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
- H04W52/0232—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal according to average transmission signal activity
- 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
Embodiments of the present disclosure include systems and methods for management of mobile device radio state. In some embodiments, a method, which can be implemented on a system, allows a network component (e.g., the policy and charging rules function in a UMTS network) to determine whether a mobile device is idle or active. Based on this determination, the network component may modify the behavior of a network element (e.g., a base station, eNode B or Node B) in relation to promotion or demotion of the mobile device's radio state. In some embodiments, the disclosed system can include a client side component on the mobile device which can determine criteria to be used by the network component to govern and optimize changes in mobile device radio state in a manner that conserves device and network resources.
- This application claims priority to and the benefit of the U.S. Provisional Application 61/740,392, entitled MANAGEMENT OF MOBILE DEVICE RADIO STATE PROMOTION AND DEMOTION BY BUFFER AND/OR ACTIVITY MONITORING, (Attorney Docket No. 76443-8152.US00) filed on Dec. 20, 2012, the contents of which are all incorporated by reference herein.
- This application is related to U.S. patent application Ser. No. ______ entitled “SYSTEMS AND METHODS FOR APPLICATION MANAGEMENT OF MOBILE DEVICE RADIO STATE PROMOTION AND DEMOTION,” (Attorney Docket No. 76443-8152.US02), filed on Mar. 15, 2013, the contents of which are all incorporated by reference herein.
- Multiple factors may contribute to the proliferation of data on a mobile network: the end-user, mobile devices, wireless devices, mobile applications, and the network. As mobile devices evolve, so may the various elements associated with the network, such as, availability, applications, user behavior, location thus changing the way the network interacts with the device and the application.
- Some mobile devices may have applications or other clients that create data (e.g., background data, background activity) that appear active to the network when it is in fact idle or in a background state when the user is not using the device. This background data or signaling may cause the network to unnecessarily promote the mobile device from a lower powered radio state to a higher powered one, causing unneeded or non-optimal battery consumption and network resource consumption.
FIG. 1A-1depicts diagrams showing radio states and transitions in a 3G network.
FIG. 1A-2depicts a diagram showing radio states and transitions in a 4G/LTE network.
FIG. 1Billustrates an example diagram of a system where a host server facilitates management of traffic, content caching, and/or resource conservation between mobile devices (e.g., wireless devices), an application server or content provider, or other servers such as an ad server, promotional content server, or an e-coupon server in a wireless network (or broadband network) for resource conservation. The host server can further manage mobile device radio state promotion and demotion by buffer and/or activity monitoring.
FIG. 1Cillustrates an example diagram of a proxy and cache system distributed between the host server and device which facilitates network traffic management between a device, an application server or content provider, or other servers such as an ad server, promotional content server, or an e-coupon server for resource conservation and content caching. In some embodiments, the proxy system distributed among the host server and the device can further manage mobile device radio state promotion and demotion by buffer and/or activity monitoring.
FIG. 2Adepicts a block diagram illustrating an example of client-side components in a distributed proxy and cache system, further including a radio state management engine.
FIG. 2Bdepicts a block diagram illustrating additional components in the radio state management engine shown in the example of FIG. 2A.
FIG. 3Adepicts a block diagram illustrating an example of server-side components in a distributed proxy and cache system, further including a radio state management engine.
FIG. 3Bdepicts a block diagram illustrating additional components in the radio state management engine shown in the example of FIG. 3A.
FIG. 4Adepicts a block diagram illustrating an example of client-side components in a distributed proxy and cache system residing on a mobile device (e.g., wireless device) that manages traffic in a wireless network (or broadband network) for resource conservation, content caching, and/or traffic management. The client-side proxy (or local proxy) can further categorize mobile traffic and/or implement delivery policies based on application behavior, content priority, user activity, and/or user expectations.
FIG. 4Bdepicts a block diagram illustrating a further example of components in the cache system shown in the example of FIG. 4Awhich in some embodiments is capable of caching and adapting caching strategies for mobile application behavior and/or network conditions. Components capable of detecting long poll requests and managing caching of long polls are also illustrated.
FIG. 4Cdepicts a block diagram illustrating examples of additional components in the local cache shown in the example of FIG. 4Awhich is further capable of performing mobile traffic categorization and policy implementation based on application behavior and/or user activity.
FIG. 5Adepicts a block diagram illustrating an example of server-side components, in certain embodiments of a distributed proxy and cache system that manages traffic in a wireless network (or broadband network) for resource conservation, content caching, and/or traffic management. In some embodiments, the server-side proxy (or proxy server) can further categorize mobile traffic and/or implement delivery policies based on application behavior, content priority, user activity, and/or user expectations.
FIG. 5Bdepicts a block diagram illustrating a further example of components in the caching policy manager in the cache system shown in the example of FIG. 5Awhich is capable of caching and adapting caching strategies for mobile application behavior and/or network conditions. Components capable in some embodiments of detecting long poll requests and managing caching of long polls are also illustrated.
FIG. 5Cdepicts a block diagram illustrating examples of additional components in certain embodiments in the proxy server shown in the example of FIG. 5Awhich is further capable of performing mobile traffic categorization and policy implementation based on application behavior and/or traffic priority.
FIG. 6is a flow diagram depicting certain steps in a process for assessing background data and performing a radio status transition as implemented in certain embodiments.
FIG. 7is a flow diagram depicting a process for assessing background data and performing a radio status transition based on power state transition criteria as implemented in certain embodiments.
FIG. 8is a flow diagram generally depicting a process for monitoring applications which transmit background data and performing a radio status transition based on radio state transition criteria as implemented in certain embodiments.
FIG. 9depicts a table showing examples of different traffic or application category types which can be used in implementing network access and content delivery policies.
FIG. 10depicts a table showing examples of different content category types which can be used in implementing network access and content delivery policies.
FIG. 11shows 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 following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding of the disclosure. However, in certain instances, well-known or conventional details are not described in order to avoid obscuring the description. References to “one embodiment” or “an embodiment” in the present disclosure can be, but not necessarily are, references to the same embodiment and such references mean at least one of the embodiments.
- Reference in this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “In some embodiments” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not other embodiments.
- The terms used in this specification generally have their ordinary meanings in the art, within the context of the disclosure, and in the specific context where each term is used. Certain terms that are used to describe the disclosure are discussed below, or elsewhere in the specification, to provide additional guidance to the practitioner regarding the description of the disclosure. For convenience, certain terms may be highlighted, for example using italics and/or quotation marks. The use of highlighting has no influence on the scope and meaning of a term; the scope and meaning of a term is the same, in the same context, whether or not it is highlighted. It will be appreciated that same thing can be said in more than one way.
- Consequently, alternative language and synonyms may be used for any one or more of the terms discussed herein, nor is any special significance to be placed upon whether or not a term is elaborated or discussed herein. Synonyms for certain terms are provided. A recital of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification, including examples of any terms discussed herein, is illustrative only, and is not intended to further limit the scope and meaning of the disclosure or of any exemplified term. Likewise, the disclosure is not limited to various embodiments given in this specification.
- Without intent to limit the scope of the disclosure, examples of instruments, apparatus, methods and their related results according to the embodiments of the present disclosure are given below. Note that titles or subtitles may be used in the examples for convenience of a reader, which in no way should limit the scope of the disclosure. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. In the case of conflict, the present document, including definitions, will control.
- As used herein, a “module,” “a manager,” a “handler,” a “detector,” an “interface,” a “controller,” a “normalizer,” a “generator,” an “invalidator,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module, manager, handler, detector, interface, controller, normalizer, generator, invalidator, or engine can be centralized or its functionality distributed. The module, manager, handler, detector, interface, controller, normalizer, generator, invalidator, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor.
- As used herein, a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid. Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.
- Certain of the embodiments disclose a comprehensive and end-to-end solution that is able to address each element for operators and devices manufacturers to support both the shift in mobile or wireless devices and the surge in data by leveraging the premise that mobile content has a definable or relevant “freshness” value. The “freshness” of mobile content can be determined, either with certainty, or with some heuristics having a tolerance within which the user experience is enhanced, or not negatively impacted, or negatively impacted but is either not perceptible to the user or within a tolerable threshold level.
- Certain of the embodiments transparently determine such “freshness” by monitoring, analyzing, and applying rules (which may be heuristically determined) the transactions (requests/responses) between applications (e.g., mobile applications) and the peers (corresponding server or other clients). Moreover, the technology is further able to effectively cache content which may be marked by its originating/host server as being “non-cacheable” and identify some “freshness” value which can then be used in implementing application-specific caching. In general, the “freshness” value has an approximate minimum value which is typically determined using the update interval (e.g., interval with which requests are sent) between the application and its corresponding server/host.
- 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 3.5G, Long Term Evolution (LTE), 4G, and WiMax, are focused on providing increased bandwidth. Although partially addressed by the standards, a key problem that remains is lack of bandwidth on the signaling channel more so than the data channel and the standard does not address battery life very well.
- Certain 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 applying specific heuristics associated with device, user behavioral patterns (how often they interact with the device/application) and/or network parameters.
- Certain of the disclosed embodiments can further include, moving recurring Hypertext Transfer Protocol (HTTP) polls performed by various widgets, RSS readers, etc., to remote network node (e.g., Network Operation Center (NOC)), thus considerably lowering device battery/power consumption, radio channel signaling and bandwidth usage. Additionally, the offloading can be performed transparently so that existing applications do not need to be changed.
- In some embodiments, this can be implemented using a local proxy on the mobile device (e.g., any wireless device) which automatically detects recurring requests for the same content (RSS feed, Widget data set) that matches a specific rule (e.g., happens every 15 minutes). The local proxy can automatically cache the content on the mobile device while delegating the polling to the server (e.g., a proxy server operated as an element of a communications network). The server can then notify the mobile/client proxy if the content changes, and if content has not changed (or not changed sufficiently, or in an identified manner or amount) the mobile proxy provides the latest version in its cache to the user (without need to utilize the radio at all). This way the mobile or wireless device (e.g., a mobile phone, smart phone, M2M module/MODEM, or any other wireless devices, etc.) does not need to open (e.g., thus powering on the radio) or use a data connection if the request is for content that is monitored and that has been not flagged as new/changed.
- The logic for automatically adding content sources/application servers (e.g., including URLs/content) to be monitored can also check for various factors like how often the content is the same, how often the same request is made (is there a fixed interval/pattern?), which application is requesting the data, etc. Similar rules to decide between using the cache and request the data from the original source may also be implemented and executed by the local proxy and/or server in certain embodiments.
- For example, when the request comes at an unscheduled/unexpected time (user initiated check), or after every (n) consecutive times the response has been provided from the cache, etc., or if the application is running in the background vs. in a more interactive mode of the foreground. As more and more mobile applications or wireless enabled applications base their features on resources available in the network, this becomes increasingly important. In addition, the disclosed technology allows elimination of unnecessary chatter from the network, benefiting the operators trying to optimize the wireless spectrum usage.
- In some embodiments, the disclosed proxy system is able to establish policies for choosing traffic (data, content, messages, updates, etc.) to cache and/or shape. Additionally, by combining information from observing the application making the network requests, getting explicit information from the application, or knowing the network destination the application is reaching, the disclosed technology can determine or infer what category the transmitted traffic belongs to.
- For example, In some embodiments, mobile or wireless traffic can be categorized as: (a1) interactive traffic or (a2) background traffic. The difference is that in (a1) a user is actively waiting for a response, while in (a2) a user is not expecting a response. This categorization can be used in conjunction with or in lieu of a second type of categorization of traffic: (b1) immediate, (b2) low priority, (b3) immediate if the requesting application is in the foreground and active.
- For example, a new update, message or email may be in the (b1) category to be delivered immediately, but it still is (a2) background traffic—a user is not actively waiting for it. A similar categorization applies to instant messages when they come outside of an active chat session. During an active chat session a user is expecting a response faster. Such user expectations are determined or inferred and factored into when optimizing network use and device resources in performing traffic categorization and policy implementation.
- Some examples of the applications of the described categorization scheme, include the following: (a1) interactive traffic can be categorized as (b1) immediate—but (a2) background traffic may also be (b2) or (b3). An example of a low priority transfer is email or message maintenance transaction such as deleting email or other messages or marking email as read at the mail or application server. Such a transfer can typically occur at the earlier of (a) timer exceeding a timeout value (for example, 2 minutes), and (b) data being sent for other purposes.
- An example of (b3) is IM presence updates, stock ticker updates, weather updates, status updates, news feeds. When the UI of the application is in the foreground and/or active (for example, as indicated by the backlight of the device/phone being lit or as determined or inferred from the status of other sensors), updates can be considered immediate whenever the server has something to push to the device. When the application is not in the foreground or not active, such updates can be suppressed until the application comes to foreground and is active.
- With some embodiments, networks can be selected or optimized simultaneously for (a1) interactive traffic and (a2) background traffic.
- In some embodiments, as the wireless device or mobile device proxy (separately or in conjunction with the server proxy) is able to categorize the traffic as (for example) (a1) interactive traffic or (a2) background traffic, it can apply different policies to different types of traffic. This means that it can internally operate differently for (a1) and (a2) traffic (for example, by allowing interactive traffic to go through to the network in whole or in part, and apply stricter traffic control to background traffic; or the device side only allows a request to activate the radio if it has received information from the server that the content at the host has been updated, etc.).
- When the request does require access over the wireless network, the disclosed technology can request the radio layer to apply different network configurations to different traffic. Depending on the type of traffic and network this may be achieved by different means:
- (1) Using 3G/4G for (a1) and 2G/2.5G for (a2);
- (3) Utilizing different network access points for different data sets (access points which would be configured to use network resources differently similar to (1) and (2) above).
- Additionally, 3GPP Fast Dormancy calls for improvements so that applications, operating systems or the mobile device would have awareness of the traffic type to be more efficient in the future. Certain embodiments of the disclosed system, having the knowledge of the traffic category and being able to utilize Fast Dormancy appropriately may solve the problem identified in Fast Dormancy. In this manner, the mobile or broadband network does not need to be configured with a compromised configuration that adversely impacts both battery consumption and network signaling resources.
- Detecting (or determining) a polling schedule allows the proxy server (server-side of the distributed cache system) to be as close as possible with its polls to the application polls. Many applications employ scheduled interval polling (e.g., every 4 hours or every 30 seconds, at another time interval). The client side proxy can detect automatic polls based on time measurements and create an automatic polling profile for an application. As an example, the local proxy attempts to detect the time interval between requests and after 2, 3, 4, or more polls, determines an automatic rate if the time intervals are all within 1 second (or another measure of relative closeness) of each other. If not, the client may collect data from a greater number of polling events (e.g., 10-12 polls) and apply a statistical analysis to determine, compute, or estimate a value for the average interval that is used. The polling profile is delivered to the server where it is used. If it is a frequent manual request, the locally proxy can substitute it with a default interval for this application taken from a profile for non-critical applications.
- In some embodiments, the local proxy (e.g., device side proxy) may keep monitoring the application/client polls and update the polling interval. If it changes by more than 30% (or another predetermined/dynamic/conditional value) from the current value, it is communicated to the proxy server (e.g., server-side proxy). This approach can be referred to as the scenario of “lost interest.” In some instances, the local proxy can recognize requests made outside of this schedule, consider them “manual,” and treat them accordingly.
- In some embodiments, applications can be organized into three groups or modes of caching. Each mobile client/application can be categorized to be treated as one of these modes, or treated using multiple modes, depending on one or more conditions.
- A) Fully cached—local proxy updates (e.g., sends application requests directly over the network to be serviced by the application server/content host) only when the proxy server tells the local proxy to update. In this mode, the local proxy can ignore manual requests and the proxy server uses the detected automatic profile (e.g., sports score applets, Facebook, every 10, 15, 30, or more polls) to poll the application server/content provider.
- B) Partially cached—the local proxy uses the local or internal cache for automatic requests (e.g., application automatic refreshes), other scheduled requests but passes through some manual requests (e.g., email download, EBay or some Facebook requests); and
- C) Never cached (e.g., real-time stock ticker, sports scores/statuses; however, in some instances, 15 minutes delayed quotes can be safely placed on 30 seconds schedules—B or even A).
- The actual application or caching mode classification can be determined based on the rate of content change and critical character of data. Unclassified applications by default can be set as class C.
- In some embodiments, the local proxy starts by detecting the device backlight status. Requests made with the screen light ‘off’ can be allowed to use the local cache if a request with identical signature is registered with the proxy server, which is polling the original host server/content server(s) to which the requests are directed. If the screen light is ‘on’, further detection can be made to determine whether it is a background application or for other indicators that local cache entries can or cannot be used to satisfy the request. When identified, the requests for which local entries can be used may be processed identically to the screen light off situation. Foreground requests can use the aforementioned application classification to assess when cached data is safe to use to process requests.
FIG. 1A-1depicts diagrams showing radio states 4000 and transitions in a 3G network. A 3G device can be in one of the following Radio Resource Control (RRC) connection states (the Idle state may not technically be considered a “connected state” in some instances). A high state may include, e.g. DCH, Cell DCH or High Speed Packet Access (HSPA) 4004. In the state 4004, the device may communicate with the network in a dedicated fashion, which may require the most network resources and the highest device power (compared with the other states). The low state may include, e.g., FACH or Cell FACH 4003. In this state 4003, the device may communicate with the network, but doing so may require some network resources (e.g., supporting data throughput at low rates) and some device power. Low state 4003 may generally impose a lesser burden than the High state 4004.
- A standby state may include, e.g., URA, URA PCH or Cell PCH 4002. In this state 4002, the network may be aware of the device, but there may be no requirement for network resources to be consumed. In an idle state 4001, the network may be aware of the device, but the device may be in sleep mode. In sleep mode, the device may not really communicate with the network and may therefore require the least amount of network resources and consume the least power (compared with the other states).
FIG. 1A-2depicts a diagram showing radio states and transitions in a 4G/LTE network. Particularly, mobility states 4100 may be the status conditions of a mobile device as the mobile device relates to a communication network. Mobility states may include detached 4101 (unknown to the network), active 4102 (communicating with the network), and idle 4103 (awaiting actions). In some embodiments, the Universal Mobile Telecommunications System (UMTS) LTE device may starts in the detached 4101 (unknown status) state when it is turned on. After the mobile device registers with the network, it may change into the active state 4102. If the device is inactive for a period of time (does not transfer information), it may be moved into the idle mode 4103. If there is data to be transferred, the mode may be changed back to the active 4102. When a device is powered off, it may inform the system (deregisters) and may detach from the network.
- The mobile device may have applications or other clients that create data (e.g., background data, background activity) that appear active to the network when it is in fact idle or in a background state when the user is not using the device. This background data or signaling may cause the network to unnecessarily promote the mobile device from a lower powered radio state to a higher powered one, causing unneeded or non-optimal battery consumption and network resource consumption.
- Various of the disclosed embodiments include one or more of client-side components (in the local proxy 275 as shown in the examples of
FIG. 2A-FIG. 2B) and/or server-side components (in the proxy server 325 as shown in the examples of FIG. 3A-FIG. 3B) which can derive information from the mobile device (150, 250) about device usage to implicitly control radio state (as dictated on the network side via network-side throttling. For example, the disclosed technology, in the case of the 3 or 4 state Wideband Code Division Multiple Access (WCDMA)/3G model (IDLE/(PCH)/FACH/DCH)) can take advantage of knowing or determining the FACH consumption rate and byte buffers by keeping the radio in FACH for e.g. background data transfer until the buffer crosses a threshold (predetermined or dynamically adjusted, device dependent, carrier dependent, network condition dependent), or when the device's backlight is off, or until user activity/lack thereof is determined/detected or some other similar criteria.
- The client side components in the local proxy 275 can, alone or in combination with the server side components in the proxy server 325, more intelligently determine what user activity and/or data activity should justify a radio state promotion and communicate the information to the network to be implemented as a single session, multi-session, or global policy (e.g., via a policy manager on the network side such as the Policy and Charging Rules Function (PCRF) node). This policy can be used to execute the appropriate level of throttling to prevent the radio from going to higher powered states when unjustified based on dynamic conditions (e.g., network status, traffic, congestion, user expectations and/or user behavior/other activity).
- In some embodiments, buffer size can be used as a trigger or indication of when to trigger radio state changes. The parameters related to the buffer (e.g., threshold, timer, buffer sensitivity) which are configured by the network to cause radio state changes may be dynamic based on the network conditions, hardware/software configuration and can differ based on network operator/carrier.
- Due to the predominantly dynamic nature of buffer parameters, to use the buffer size in the disclosed technology for optimizing situations for radio state promotions and/or demotions, in some embodiments the client side components and/or the server side components can be configured to include dynamic adaptive logic to discover network specific or condition specific values and adjust accordingly. In some instances, static values for the buffer parameters can also be used. Some example of implementations include as follows:
- The client side and/or the server side can include components (e.g., the components shown in
FIG. 2A-FIG. 3B) which handle the traffic over a common channel, to handle specific types of traffic.
- The client side components can include logic (e.g., the components shown in the example of
FIG. 2A-FIG. 2B) to load and adjust itself with related values for the buffer parameters by communicating with the server-side components. The server-side components can then learn about those values while the client side determines or computes them.
- The server-side components (e.g., the components shown in
FIG. 3A-FIG. 3B), can be ready to use and apply the parameter values (transfer instructions) (e.g., there can be different values for each client).
- The client side and/or the server side can include components (e.g., the components shown in
- The client side and server side components can be transparent and can receive a normal junk of bytes. In general, the implementation may include logic which would keep the device radio in lower powered states such as PCH or FACH, or inactive state, for as long as possible to avoid over consumption of device and network resources, so long as the user experience is not negatively impacted or noticeable by the user. This technology can provide signaling optimization in both WCDMA/3G networks as well as 4G/LTE networks.
- In some embodiments, the disclosed system including the client side and/or server side components (e.g., the components shown in
FIG. 2A-FIG. 3B) can be integrated with policy management nodes/components of wireless networks (e.g., the PCRF node in the RNS (radio network system) of an UMTS network)). In some embodiments, the PCRF, through interoperation with the disclosed system, can determine whether a given mobile device (150, 250) is in “idle” or “active” at a given moment. The PCRF can then govern or dictate the Radio Network Controller (RNC) (in WCDMA 3G), NodeB or eNodeB (in LTE 4G) policies that would, for example allow or forbid a radio channel status upgrade into a higher powered state, or lower the radio channel status to a lower powered state in a more intelligent and resource efficient manner. Note that UMTS networks (via the PCRF) can perform throttling and the disclosed system including client side and/or server side components can provide the information to the network regarding what level of throttling should occur to trigger radio state changes to higher powered or lower powered states.
- In a further embodiment, the client-side components (e.g., as illustrated in
FIG. 2A-FIG. 2B) can be configured to rate-limit data transmission upon request for data, to avoid triggering transition to higher powered radio states (e.g., DCH in the 3/4 state model) for that particular transaction. In this example, such data can be transmitted through or using a rate-limiting proxy (e.g., a rate limiting proxy 520 as shown in the example of FIG. 3B) which can limit or adjust the rate of the response as requested/specified by the client side components. The rate limiting proxy 520 can be a component of the server-side components (e.g., internal to), or it can be a separate entity (external to the server-side components). Note that the ‘rate limit’ can include the speed of transmission, or the buffer size after which the server will accumulate data for the client side components to acknowledge the transmission. The client side components can utilize various parameters including request and/or anticipated response characteristics, application, device state (e.g., screen off, backlight status), user activity, user preferences/behavior, to determine/specify whether to rate-limit the response data and/or the degree to which to rate-limit the response data.
FIG. 1Billustrates an example diagram of a system where a host server 100 facilitates management of traffic, content caching, and/or resource conservation between mobile devices (e.g., wireless devices 150), and an application server or content provider 110, or other servers such as an ad server 120A, promotional content server 120B, or an e-coupon server 120C in a wireless network (or broadband network) for resource conservation. The host server can further manage mobile device radio state promotion and demotion by buffer and/or activity monitoring.
- The client devices 150 can be any system and/or device, and/or any combination of devices/systems that is able to establish a connection, including wired, wireless, cellular connections with another device, a server and/or other systems such as host server 100 and/or application server/content provider 110. Client devices 150 will typically include a display and/or other output functionalities to present information and data exchanged between among the devices 150 and/or the host server 100 and/or application server/content provider 110. The application server/content provider 110 can by any server including third party servers or service/content providers further including advertisement, promotional content, publication, or electronic coupon servers or services. Similarly, separate advertisement servers 120A, promotional content servers 120B, and/or e-Coupon servers 120C as application servers or content providers are illustrated by way of example.
- For example, the client devices 150 can include mobile, hand held or portable devices, wireless devices, or non-portable devices and can be any of, but not limited to, a server desktop, a desktop computer, a computer cluster, or portable devices, including a notebook, a laptop computer, a handheld computer, a palmtop computer, a mobile phone, a cell phone, a smart phone, a PDA, a Blackberry device, a Palm device, a handheld tablet (e.g., an iPad or any other tablet), a hand held console, a hand held gaming device or console, any SuperPhone such as the iPhone, and/or any other portable, mobile, hand held devices, or fixed wireless interface such as a M2M device, etc. In some embodiments, the client devices 150, host server 100, and application server 110 are coupled via a network 106 and/or a network 108. In some embodiments, the devices 150 and host server 100 may be directly connected to one another.
- The input mechanism on client devices 150 can include touch screen keypad (including single touch, multi-touch, gesture sensing in 2D or 3D, etc.), a physical keypad, a mouse, a pointer, a track pad, motion detector (e.g., including 1-axis, 2-axis, 3-axis accelerometer, etc.), a light sensor, capacitance sensor, resistance sensor, temperature sensor, proximity sensor, a piezoelectric device, device orientation detector (e.g., electronic compass, tilt sensor, rotation sensor, gyroscope, accelerometer), or a combination of the above.
- Signals received or detected indicating user activity at client devices 150 through one or more of the above input mechanism, or others, can be used in the disclosed technology in acquiring context awareness at the client device 150. Context awareness at client devices 150 generally may include, by way of example but not limitation, client device 150 operation or state acknowledgement, management, user activity/behavior/interaction awareness, detection, sensing, tracking, trending, and/or application (e.g., mobile applications) type, behavior, activity, operating state, etc.
- Context awareness in the present disclosure may also include knowledge and detection of network side contextual data and can include network information such as network capacity, bandwidth, traffic, type of network/connectivity, and/or any other operational state data. Network side contextual data can be received from and/or queried from network service providers (e.g., cell provider 112 and/or Internet service providers) of the network 106 and/or network 108 (e.g., by the host server and/or devices 150). In addition to application context awareness as determined from the client 150 side, the application context awareness may also be received from or obtained/queried from the respective application/service providers 110 (by the host 100 and/or client devices 150).
- The host server 100 can use, for example, contextual information obtained for client devices 150, networks 106/108, applications (e.g., mobile applications), application server/provider 110, or any combination of the above, to manage the traffic in the system to satisfy data needs of the client devices 150 (e.g., to satisfy application or any other request including HTTP request). In some embodiments, the traffic is managed by the host server 100 to satisfy data requests made in response to explicit or non-explicit user 103 requests and/or device/application maintenance tasks. The traffic can be managed such that network consumption, for example, use of the cellular network is conserved for effective and efficient bandwidth utilization. In addition, the host server 100 can manage and coordinate such traffic in the system such that use of device 150 side resources (e.g., including but not limited to battery power consumption, radio use, processor/memory use) are optimized with a general philosophy for resource conservation while still optimizing performance and user experience.
- For example, in context of battery conservation, the device 150 can observe user activity (for example, by observing user keystrokes, backlight status, or other signals via one or more input mechanisms, etc.) and may alter device 150's behaviors in response. The device 150 can also request that host server 100 alter the behavior for network resource consumption based upon user activity or behavior.
- In some embodiments, the traffic management for resource conservation may be performed using a distributed system between the host server 100 and client device 150. The distributed system can include proxy server and cache components on the server side 100 and on the device/client side, for example, as shown by the server cache 135 on the server 100 side and the local cache 185 on the client 150 side.
- Functions and techniques disclosed for context aware traffic management for resource conservation in networks (e.g., network 106 and/or 108) and devices 150, reside in a distributed proxy and cache system. The proxy and cache system can be distributed between, and reside on, a given client device 150 in part or in whole and/or host server 100 in part or in whole. The distributed proxy and cache system are illustrated with further reference to the example diagram shown in
FIG. 1C. Functions and techniques performed by the proxy and cache components in the client device 150, the host server 100, and the related components therein are described, respectively, in detail with further reference to the examples of FIG. 2A-5C.
- In some embodiments, client devices 150 may communicate with the host server 100 and/or the application server 110 over network 106, which can be a cellular network and/or a broadband network. To facilitate overall traffic management between devices 150 and various application servers/content providers 110 to implement network (bandwidth utilization) and device resource (e.g., battery consumption), the host server 100 can communicate with the application server/providers 110 over the network 108, which can include the Internet (e.g., a broadband network).
- In some embodiments, the networks 106 and/or 108, over which the client devices 150, the host server 100, and/or application server 110 communicate, may be a cellular network, a broadband network, a telephonic network, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet, or any combination thereof. For example, the Internet can provide file transfer, remote log in, email, news, RSS, cloud-based services, instant messaging, visual voicemail, push mail, VoIP, and other services through any known or convenient protocol, such as, but is not limited to the TCP/IP protocol, UDP, HTTP, DNS, FTP, UPnP, NSF, ISDN, PDH, RS-232, SDH, SONET, etc.
- The networks 106 and/or 108 can be any collection of distinct networks operating wholly or partially in conjunction to provide connectivity to the client devices 150 and the host server 100 and may appear as one or more networks to the serviced systems and devices. In some embodiments, communications to and from the client devices 150 can be achieved by, an open network, such as the Internet, or a private network, broadband network, such as an intranet and/or the extranet. In some embodiments, communications can be achieved by a secure communications protocol, such as secure sockets layer (SSL), or transport layer security (TLS).
- In addition, communications can be achieved via one or more networks, such as, but are not limited to, one or more of WiMax, a Local Area Network (LAN), Wireless Local Area Network (WLAN), a Personal area network (PAN), a Campus area network (CAN), a Metropolitan area network (MAN), a Wide area network (WAN), a Wireless wide area network (WWAN), or any broadband network, and further enabled with technologies such as, by way of example, Global System for Mobile Communications (GSM), Personal Communications Service (PCS), Bluetooth, WiFi, Fixed Wireless Data, 2G, 2.5G, 3G, 4G, IMT-Advanced, pre-4G, LTE Advanced, mobile WiMax, WiMax 2, WirelessMAN-Advanced networks, enhanced data rates for GSM evolution (EDGE), General packet radio service (GPRS), enhanced GPRS, iBurst, UMTS, HSPDA, HSUPA, HSPA, UMTS-TDD, 1xRTT, EV-DO, messaging protocols such as, TCP/IP, SMS, MMS, extensible messaging and presence protocol (XMPP), real time messaging protocol (RTMP), instant messaging and presence protocol (IMPP), instant messaging, USSD, IRC, or any other wireless data networks, broadband networks, or messaging protocols.
FIG. 1Cillustrates 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 or content provider 110, or other servers such as an ad server 120A, promotional content server 120B, or an e-coupon server 120C for resource conservation and content caching. The proxy system distributed among the host server 100 and the device 150 can further manage mobile device radio state promotion and demotion by buffer and/or activity monitoring.
- The distributed proxy and cache system can include, for example, the proxy server 125 (e.g., remote proxy) and the server cache, 135 components on the server side. The server-side proxy 125 and cache 135 can, as illustrated, reside internal to the host server 100. In addition, the proxy server 125 and cache 135 on the server-side can be partially or wholly external to the host server 100 and in communication via one or more of the networks 106 and 108. For example, the proxy server 125 may be external to the host server and the server cache 135 may be maintained at the host server 100. Alternatively, the proxy server 125 may be within the host server 100 while the server cache is external to the host server 100. In addition, each of the proxy server 125 and the cache 135 may be partially internal to the host server 100 and partially external to the host server 100. The application server/content provider 110 can by any server including third party servers or service/content providers further including advertisement, promotional content, publication, or electronic coupon servers or services. Similarly, separate advertisement servers 120A, promotional content servers 120B, and/or e-Coupon servers 120C as application servers or content providers are illustrated by way of example.
- The distributed system can also, include, in some embodiments, client-side components, including by way of example but not limitation, a local proxy 175 (e.g., a mobile client on a mobile device) and/or a local cache 185, which can, as illustrated, reside internal to the device 150 (e.g., a mobile device).
- In addition, the client-side proxy 175 and local cache 185 can be partially or wholly external to the device 150 and in communication via one or more of the networks 106 and 108. For example, the local proxy 175 may be external to the device 150 and the local cache 185 may be maintained at the device 150. Alternatively, the local proxy 175 may be within the device 150 while the local cache 185 is external to the device 150. In addition, each of the proxy 175 and the cache 185 may be partially internal to the host server 100 and partially external to the host server 100.
- In some embodiments, the distributed system can include an optional caching proxy server 199. The caching proxy server 199 can be a component which is operated by the application server/content provider 110, the host server 100, or a network service provider 112, and or any combination of the above to facilitate network traffic management for network and device resource conservation. Proxy server 199 can be used, for example, for caching content to be provided to the device 150, for example, from one or more of, the application server/provider 110, host server 100, and/or a network service provider 112. Content caching can also be entirely or partially performed by the remote proxy 125 to satisfy application requests or other data requests at the device 150.
- In context aware traffic management and optimization for resource conservation in a network (e.g., cellular or other wireless networks), characteristics of user activity/behavior and/or application behavior at a mobile device (e.g., any wireless device) 150 can be tracked by the local proxy 175 and communicated, over the network 106 to the proxy server 125 component in the host server 100, for example, as connection metadata. The proxy server 125 which in turn is coupled to the application server/provider 110 may provide content and data to satisfy requests made at the device 150.
- In addition, the local proxy 175 can identify and retrieve mobile device properties, including one or more of, battery level, network that the device is registered on, radio state, or whether the mobile device is being used (e.g., interacted with by a user). In some instances, the local proxy 175 can delay, expedite (prefetch), and/or modify data prior to transmission to the proxy server 125, when appropriate, as will be further detailed with references to the description associated with the examples of
- The local database 185 can be included in the local proxy 175 or coupled to the local proxy 175 and can be queried for a locally stored response to the data request prior to the data request being forwarded on to the proxy server 125. Locally cached responses can be used by the local proxy 175 to satisfy certain application requests of the mobile device 150, by retrieving cached content stored in the cache storage 185, when the cached content is still valid.
- Similarly, the proxy server 125 of the host server 100 can also delay, expedite, or modify data from the local proxy prior to transmission to the content sources (e.g., the application server/content provider 110). In addition, the proxy server 125 uses device properties and connection metadata to generate rules for satisfying request of applications on the mobile device 150. The proxy server 125 can gather real time traffic information about requests of applications for later use in optimizing similar connections with the mobile device 150 or other mobile devices.
- In some embodiments, the local proxy 175 and the proxy server 125 are transparent to the multiple applications executing on the mobile device. The local proxy 175 may be transparent to the operating system or platform of the mobile device and may or may not be specific to device manufacturers. In some instances, the local proxy 175 may be optionally customizable in part or in whole to be device specific. In some embodiments, the local proxy 175 may be bundled into a wireless model, a firewall, and/or a router.
- In some embodiments, the host server 100 can in some instances, utilize the store and forward functions of a short message service center (SMSC) 112, such as that provided by the network service provider, in communicating with the device 150 in achieving network traffic management. Note that 112 can also utilize any other type of alternative channel including USSD or other network control mechanisms. As will be further described with reference to the example of
FIG. 3, the host server 100 can forward content or HTTP responses to the SMSC 112 such that it is automatically forwarded to the device 150 if available, and for subsequent forwarding if the device 150 is not currently available.
- In general, the disclosed distributed proxy and cache system allows optimization of network usage, for example, by serving requests from the local cache 185, the local proxy 175 reduces the number of requests that need to be satisfied over the network 106. Further, the local proxy 175 and the proxy server 125 may filter irrelevant data from the communicated data. In addition, the local proxy 175 and the proxy server 125 can also accumulate low priority data and send it in batches to avoid the protocol overhead of sending individual data fragments. The local proxy 175 and the proxy server 125 can also compress or transcode the traffic, reducing the amount of data sent over the network 106 and/or 108. The signaling traffic in the network 106 and/or 108 can be reduced, as the networks are now used less often and the network traffic can be synchronized among individual applications.
- With respect to the battery life of the mobile device 150, by serving application or content requests from the local cache 185, the local proxy 175 can reduce the number of times the radio module is powered up. The local proxy 175 and the proxy server 125 can work in conjunction to accumulate low priority data and send it in batches to reduce the number of times and/or amount of time when the radio is powered up. The local proxy 175 can synchronize the network use by performing the batched data transfer for all connections simultaneously.
FIG. 2Adepicts a block diagram illustrating another example of client-side components in a distributed proxy and cache system, further including a radio state management engine 401. FIG. 2Bdepicts a block diagram illustrating additional components in the radio state management engine 401 shown in the example of FIG. 2A.
- The radio state management engine 401 can include a response rate configuration engine 402 having a data rate configurator 403, a buffer size configurator 404 and/or a PCRF policy recommendation engine 405. The engine 401 may also include a radio state change criteria manager 411 having an FACH consumption rate and/or buffer tracker 412, a state change threshold configuration engine 439, and/or a state change trigger detector 413. Additional or less modules/engines can be included.
FIG. 3Adepicts a block diagram illustrating an example of server-side components in a distributed proxy and cache system, further including a radio state management engine 501. FIG. 3Bdepicts a block diagram illustrating additional components in the radio state management engine 501 shown in the example of FIG. 3A.
- The radio state management engine 501 can include a rate limiting engine 502 having a data rate configurator 503 and/or a buffer size configurator 504, a PCRF interface engine 505, a radio state change criteria manager 511 having a 3 or 4 state CDMA radio state compatibility module, a 2 state LTE/4G radio state compatibility module, and/or a radio state change trigger detector and processing engine 539. The radio state management engine 501 can include or be coupled to a rate-limiting proxy 520 (as illustrated). Additional or less modules/engines can be included.
- The various components of the radio state management engine 401 and the radio state management engine 501 can singularly or in any combination perform the management and/or policy management of mobile device radio state promotion or demotion based on buffer, activity, or device (e.g., idle or active) state monitoring as described in conjunction with
FIG. 1A-1and FIG. 1A-2. For example, the radio state management engine 401/501 can implicitly manage the radio state transition since the radio state is controlled by the network (i.e., the network orders the device to a specific state). In one implementation, the radio state transition is by managed by throttling the actual data flow through the network, such that the device is able to affect how the network will order it to change its state.
- In one embodiment, for example, the radio state management engine 401 can gather and/or determine information concerning the current state of the device and provide such information to the PCRF node to allow the PCRF node to understand the current state of the device in the network and control the radio state of the device by signaling the radio access network nodes such as RNC and eNodeB. In another embodiment, for example, the radio state management engine 501 can determine whether the PCRF node can signal or control the radio access network nodes to change the radio state of the device. In one implementation, if the PCRF to radio access network node communication or control is not feasible, the radio state management engine 501 can detect such condition and can obtain information from the PCRF node to control the radio state of the mobile device. For example, in one implementation, the radio state management engine 501 can provide policy information and/or the level of throttling needed to keep the radio on the mobile device from going to the higher powered states.
- Referring to
FIG. 2B, the radio state management engine 401 can manage the radio state of a mobile device is a mobile network by monitoring a criteria associated with the mobile and determining whether to perform a radio status transition of the mobile device in the mobile network from a first state to a second state based at least in part upon the criteria. In one implementation, the first state and the second state are distinguished from a higher powered state or a lower powered state. In one implementation the radio status transition includes one of a promotion or demotion.
- The response rate configuration engine 402 can include various options for configuring response rates such as data/transmission rates, buffer size, PCRF policy recommendations, and the like. In one implementation, the response rates may be configured for various purposes such as to avoid triggering transition to higher powered radio states.
- The data rate configurator 403, in one implementation, can be used to configure the data transmission rate. In one implementation, data rate can be specified or configured for traffic based on, or when one or more of the following is detected, the application is not interacting with the user, the application is running in the background on the mobile device, or the data contained in the traffic is not time critical, and the like. The buffer size configurator 404, in one implementation, can be used to configure the size or capacity of a buffer on the mobile device, which can cause the server to accumulate data for the client to acknowledge the transmission. The PCRF policy recommendation engine 405, in one implementation, can communicate a plurality of rules to a network component such as a radio access network node (e.g., RNC, eNodeB, and the like). In one implementation, the rules determine a level of throttling.
- The radio state change criteria manager 411, in one implementation, can monitor, configure and/or manage criteria for changing radio state. In one implementation, the criteria can include, but are not limited to: a capacity of a buffer, the buffer located on a mobile device, a Forward Access Channel (FACH) consumption rate, a backlight status of the mobile device, one or more of behavior of applications running on the mobile device, user activity at the mobile device, and user preferences at the mobile device. In one implementation, the radio state change criteria manager 411 can monitor the criteria by applying logic to discover network specific or condition specific values associated with the buffer capacity. In one implementation, the logic can be adaptive to network conditions and is dynamically adjustable. In some implementations, the radio state change criteria manager 411 can leverage other modules of the local proxy 275 (e.g., application behavior detector 236, user activity module 215) to manage criteria for radio state change. In one implementation, the radio state change criteria manager 411 can determine whether to perform radio channel status transition from a first state to a second state based on various information such as one or more of the criteria, application, and the like.
- The FACH consumption rate and/or buffer tracker 412 can, in one implementation, can know, track and/or determine the FACH consumption rate and byte buffers by keeping the radio in FACH for e.g. background data transfer until the buffer crosses a threshold or when the device's backlight is off, or until user activity/lack thereof is determined/detected or some other similar criteria. In one implementation, the tracking of the buffer can be used to determine if the buffer exceeds a threshold. If the buffer exceeds the threshold, the criteria for radio state change is determined as being met, such that the radio state is promoted from a first state to the second state. In one implementation, the second state can be a higher powered state than the first state.
- The state change threshold configuration engine 439, in one implementation, can be used to configure the thresholds for causing or triggering radio state changes. For example, buffer size can be configured for use as a trigger or indication of when to trigger radio state changes.
- The state change trigger detector 413 can detect the change of radio state, such as promotion or a demotion. In one implementation, the state change detector 413 can also effect the change by changing the radio state. In another implementation, the state change trigger detector 413 can perform the radio status transition by adjusting a level of throttling.
- In one embodiment, the radio state management engine 401 may also include a module for determining whether an application transmits a background data or foreground data over a wireless network. In one implementation, background data can include, but is not limited to: data transmitted or generated by an application without a user interaction or a user request, data transmitted or generated by the application for application maintenance or updating, and the like. The foreground data can include, but is not limited to: data transmitted or generated as a result of a user interaction or a user request.
- Referring to
FIG. 3B, some of the components of the radio state management engine 501 may perform functions similar to the components of the radio state management engine 401.
- In one implementation, the rate limiting proxy 520 can limit or adjust the rate of the response as requested/specified by the client side components. The rate limiting proxy 520 can be a component of the radio state management engine 501 or it can be a separate entity (external to engine 501). The rate limiting proxy 520 can, for example, be responsive to various parameters specified or requested by the client-side, including request and/or anticipated response characteristics, application, device state (e.g., screen off, backlight status), user activity, user preferences/behavior, to determine/specify whether to rate-limit the response data and/or the degree to which to rate-limit the response data.
- The rate limiting engine 502, in one implementation, can perform some or all of the functions of the rate limiting proxy 520. The rate limiting engine 502 can, for example, limit the speed of transmission, or the buffer size after which the server will accumulate data for the client side components to acknowledge the transmission.
- The PCRF interface engine 505 can, in one implementation, interface with the PCRF node. The interface engine can obtain policies from the PCRF node, and/or provide policies or enhanced policies to the PCRF node. For example, via the interface engine, the radio state management engine 501 can provide information concerning when or what level of throttling should happen to keep the radio from transitioning to the higher powered states. The components in the UMTS network (through PCRF) can then perform the throttling and thereby manage the radio states.
- The radio state change criteria manager 511 can receive, access, obtain, configure, and/or apply various criteria for managing radio state change in mobile devices. In one implementation, for example, the manager 511 can monitor criteria associated with the mobile device, network, and/or the like. In a further implementation, such criteria may be specific to WCDMA or LTE/4G networks. The 3 or 4 state WCDMA radio state compatibility module 512 may, for example, have its own set of criteria for when to trigger radio state change, or the state to which the change can be triggered, and the like. In one implementation, in the case of 3 or 4 state WCDMA, the module 512 can take advantage of knowing or determining the FACH consumption rate and byte buffers by keeping the radio in FACH for e.g. background data transfer until the buffer crosses a threshold (predetermined or dynamically adjusted, device dependent, carrier dependent, network condition dependent), or when the device's backlight is off, or until user activity/lack thereof is determined/detected or some other similar criteria. The 2 state LTE/4G radio state compatibility module 513 can similarly monitor criteria associated with LTE/4G network and the two states specific to the network to determine whether to perform a radio status transition, and which state to transition to.
- The radio state change trigger detector and processing engine 539, in one implementation, can detect a trigger to change the radio state of a mobile device (e.g., from the radio state change criteria manager), and can determine whether to perform a radio channel status transition based on the criteria and upon the application, such as upon the application's behavior. In one implementation, to perform the transition or cause the transition to be performed, the radio state change trigger detector and processing engine can modify or provide rules to a PCRF network component via the PCRF interface engine. In one implementation, PCRF can cause the transition at the appropriate time. In some implementation, the radio state change trigger detector and processing engine can determine that rules which avoid a transition and maintain the current state as appropriate.
FIG. 4Adepicts a block diagram illustrating an example of client-side components in a distributed proxy and cache system residing on a mobile device (e.g., wireless device) 250 that manages traffic in a wireless network (or broadband network) for resource conservation, content caching, and/or traffic management. The client-side proxy (or local proxy 275) can further categorize mobile traffic and/or implement delivery policies based on application behavior, content priority, user activity, and/or user expectations.
- The device 250, which can be a portable or mobile device (e.g., any wireless device), such as a portable phone, generally includes, for example, a network interface 208 an operating system 204, a context Application Programming Interface (API) 206, and mobile applications which may be proxy-unaware 210 or proxy-aware 220. Note that the device 250 is specifically illustrated in the example of
FIG. 2Aas a mobile device, such is not a limitation and that device 250 may be any wireless, broadband, 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, LAN, WAN, etc.).
- The network interface 208 can be a networking module that enables the device 250 to mediate data in a network with an entity that is external to the host server 250, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface 208 can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 2G, 3G, 3.5G, 4G, LTE, etc.,), Bluetooth, or whether or not the connection is via a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, a bridge router, a hub, a digital media receiver, and/or a repeater.
- Device 250 can further include, client-side components of the distributed proxy and cache system which can include, a local proxy 275 (e.g., a mobile client of a mobile device) and a cache 285. In some embodiments, the local proxy 275 includes a user activity module 215, a proxy API 225, a request/transaction manager 235, a caching policy manager 245 having an application protocol module 248, a traffic shaping engine 255, and/or a connection manager 265. The traffic shaping engine 255 may further include an alignment module 256 and/or a batching module 257, the connection manager 265 may further include a radio controller 266. The request/transaction manager 235 can further include an application behavior detector 236 and/or a prioritization engine 241, the application behavior detector 236 may further include a pattern detector 237 and/or and application profile generator 239. Additional or less components/modules/engines can be included in the local proxy 275 and each illustrated component.
- In some embodiments, a portion of the distributed proxy and cache system for network traffic management resides in or is in communication with device 250, including local proxy 275 (mobile client) and/or cache 285. The local proxy 275 can provide an interface on the device 250 for users to access device applications and services including email, IM, voice mail, visual voicemail, feeds, Internet, games, productivity tools, or other applications, etc.
- The proxy 275 is generally application independent and can be used by applications (e.g., both proxy-aware and proxy-unaware applications 210 and 220 and other mobile applications) to open TCP connections to a remote server (e.g., the server 100 in the examples of
FIG. 1B-1Cand/or server proxy 125/325 shown in the examples of FIG. 1Band FIG. 5A). In some instances, the local proxy 275 includes a proxy API 225 which can be optionally used to interface with proxy-aware applications 220 (or applications (e.g., mobile applications) on a mobile device (e.g., any wireless device)).
- The applications 210 and 220 can generally include any user application, widgets, software, HTTP-based application, web browsers, video or other multimedia streaming or downloading application, video games, social network applications, email clients, RSS management applications, application stores, document management applications, productivity enhancement applications, etc. The applications can be provided with the device OS, by the device manufacturer, by the network service provider, downloaded by the user, or provided by others.
- One embodiment of the local proxy 275 includes or is coupled to a context API 206, as shown. The context API 206 may be a part of the operating system 204 or device platform or independent of the operating system 204, as illustrated. The operating system 204 can include any operating system including but not limited to, any previous, current, and/or future versions/releases of, Windows Mobile, iOS, Android, Symbian, Palm OS, Brew MP, Java 2 Micro Edition (J2ME), Blackberry, etc.
- The context API 206 may be a plug-in to the operating system 204 or a particular client/application on the device 250. The context API 206 can detect signals indicative of user or device activity, for example, sensing motion, gesture, device location, changes in device location, device backlight, keystrokes, clicks, activated touch screen, mouse click or detection of other pointer devices. The context API 206 can be coupled to input devices or sensors on the device 250 to identify these signals. Such signals can generally include input received in response to explicit user input at an input device/mechanism at the device 250 and/or collected from ambient signals/contextual cues detected at or in the vicinity of the device 250 (e.g., light, motion, piezoelectric, etc.).
- In some embodiments, the user activity module 215 interacts with the context API 206 to identify, determine, infer, detect, compute, predict, and/or anticipate, characteristics of user activity on the device 250. Various inputs collected by the context API 206 can be aggregated by the user activity module 215 to generate a profile for characteristics of user activity. Such a profile can be generated by the user activity module 215 with various temporal characteristics. For instance, user activity profile can be generated in real-time for a given instant to provide a view of what the user is doing or not doing at a given time (e.g., defined by a time window, in the last minute, in the last 30 seconds, etc.), a user activity profile can also be generated for a ‘session’ defined by an application or web page that describes the characteristics of user behavior with respect to a specific task they are engaged in on the device 250, or for a specific time period (e.g., for the last 2 hours, for the last 5 hours).
- Additionally, characteristic profiles can be generated by the user activity module 215 to depict a historical trend for user activity and behavior (e.g., 1 week, 1 mo., 2 mo., etc.). Such historical profiles can also be used to deduce trends of user behavior, for example, access frequency at different times of day, trends for certain days of the week (weekends or week days), user activity trends based on location data (e.g., IP address, GPS, or cell tower coordinate data) or changes in location data (e.g., user activity based on user location, or user activity based on whether the user is on the go, or traveling outside a home region, etc.) to obtain user activity characteristics.
- In some embodiments, user activity module 215 can detect and track user activity with respect to applications, documents, files, windows, icons, and folders on the device 250. For example, the user activity module 215 can detect when an application or window (e.g., a web browser or any other type of application) has been exited, closed, minimized, maximized, opened, moved into the foreground, or into the background, multimedia content playback, etc.
- In some embodiments, characteristics of the user activity on the device 250 can be used to locally adjust behavior of the device (e.g., mobile device or any wireless device) to optimize its resource consumption such as battery/power consumption and more generally, consumption of other device resources including memory, storage, and processing power. In some embodiments, the use of a radio on a device can be adjusted based on characteristics of user behavior (e.g., by the radio controller 266 of the connection manager 265) coupled to the user activity module 215. For example, the radio controller 266 can turn the radio on or off, based on characteristics of the user activity on the device 250. In addition, the radio controller 266 can adjust the power mode of the radio (e.g., to be in a higher power mode or lower power mode) depending on characteristics of user activity.
- In some embodiments, characteristics of the user activity on device 250 can also be used to cause another device (e.g., other computers, a mobile device, a wireless device, or a non-portable device) or server (e.g., host server 100 and 300 in the examples of
FIG. 1B-1Cand FIG. 5A) which can communicate (e.g., via a cellular or other network) with the device 250 to modify its communication frequency with the mobile device 250. The local proxy 275 can use the characteristics information of user behavior determined by the user activity module 215 to instruct the remote device as to how to modulate its communication frequency (e.g., decreasing communication frequency, such as data push frequency if the user is idle, requesting that the remote device notify the device 250 if new data, changed, data, or data of a certain level of importance becomes available, etc.).
- In some embodiments, 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. 1B-1Cand FIG. 3A) send the data that was buffered as a result of the previously decreased communication frequency.
- In addition, or in alternative, the local proxy 275 can communicate the characteristics of user activity at the device 250 to the remote device (e.g., host server 100 and 300 in the examples of
FIG. 1B-1Cand FIG. 5A) and the remote device may determine how to alter its own communication frequency with the device 250 for network resource conservation and conservation of device 250 resources.
- In some embodiments, 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.
- In some embodiments, the request/transaction manager 235 can prioritize requests or transactions made by applications and/or users at the device 250, for example by the prioritization engine 241. Importance or priority of requests/transactions can be determined by the request/transaction manager 235 by applying a rule set, for example, according to time sensitivity of the transaction, time sensitivity of the content in the transaction, time criticality of the transaction, time criticality of the data transmitted in the transaction, and/or time criticality or importance of an application making the request.
- In addition, transaction characteristics can also depend on whether the transaction was a result of user-interaction or other user-initiated action on the device (e.g., user interaction with an application (e.g., a mobile application)). In general, a time critical transaction can include a transaction resulting from a user-initiated data transfer, and can be prioritized as such. Transaction characteristics can also depend on the amount of data that will be transferred or is anticipated to be transferred as a result of the requested transaction. For example, the connection manager 265, can adjust the radio mode (e.g., high power or low power mode via the radio controller 266) based on the amount of data that will need to be transferred.
- In addition, the radio controller 266/connection manager 265 can adjust the radio power mode (high or low) based on time criticality/sensitivity of the transaction. The radio controller 266 can trigger the use of high power radio mode when a time-critical transaction (e.g., a transaction resulting from a user-initiated data transfer, an application running in the foreground, any other event meeting a certain criteria) is initiated or detected.
- In some embodiments, the priorities can be set by default, for example, based on device platform, device manufacturer, operating system, etc. Priorities can alternatively or in additionally be set by the particular application; for example, the Facebook application (e.g., a mobile application) can set its own priorities for various transactions (e.g., a status update can be of higher priority than an add friend request or a poke request, a message send request can be of higher priority than a message delete request, for example), an email client or IM chat client may have its own configurations for priority. The prioritization engine 241 may include a set of rules for assigning priority.
- In some embodiments, 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 LinkedIn-related transactions), for specific transaction types (e.g., for all send message requests across all applications to have higher priority than message delete requests, for all calendar-related events to have a high priority, etc.), and/or for specific folders.
- In some embodiments, the prioritization engine 241 can track and resolve conflicts in priorities set by different entities. For example, manual settings specified by the user may take precedence over device OS settings, network provider parameters/limitations (e.g., set in default for a network service area, geographic locale, set for a specific time of day, or set based on service/fee type) may limit any user-specified settings and/or application-set priorities. In some instances, a manual synchronization request received from a user can override some, most, or all priority settings in that the requested synchronization is performed when requested, regardless of the individually assigned priority or an overall priority ranking for the requested action.
- Priority can be specified and tracked internally in any known and/or convenient manner, including but not limited to, a binary representation, a multi-valued representation, a graded representation and all are considered to be within the scope of the disclosed technology.
TABLE I Change Change (initiated on device) Priority (initiated on server) Priority Send email High Receive email High Delete email Low Edit email Often not (Un)read email Low possible to Move message Low sync (Low if Read more High possible) Download High New email in deleted Low attachment items New Calendar event High Delete an email Low Edit/change High (Un)Read an email Low Calendar event Move messages Low Add a contact High Any calendar change High Edit a contact High Any contact change High Search contacts High Wipe/lock device High Change a setting High Settings change High Manual send/receive High Any folder change High IM status change Medium Connector restart High (if no Auction outbid or High changes nothing change notification is sent) Weather Updates Low Social Network Medium Status Updates Severe Weather Alerts High News Updates Low
- Table I above shows, for illustration purposes, some examples of transactions with examples of assigned priorities in a binary representation scheme. Additional assignments are possible for additional types of events, requests, transactions, and as previously described, priority assignments can be made at more or less granular levels, e.g., at the session level or at the application level, etc.
- As shown by way of example in the above table, in general, lower priority requests/transactions can include, updating message status as being read, unread, deleting of messages, deletion of contacts; higher priority requests/transactions, can in some instances include, status updates, new IM chat message, new email, calendar event update/cancellation/deletion, an event in a mobile gaming session, or other entertainment related events, a purchase confirmation through a web purchase or online, request to load additional or download content, contact book related events, a transaction to change a device setting, location-aware or location-based events/transactions, or any other events/request/transactions initiated by a user or where the user is known to be, expected to be, or suspected to be waiting for a response, etc.
- Inbox pruning events (e.g., email, or any other types of messages), are generally considered low priority and absent other impending events, generally will not trigger use of the radio on the device 250. Specifically, pruning events to remove old email or other content can be ‘piggy backed’ with other communications if the radio is not otherwise on, at the time of a scheduled pruning event. For example, if the user has preferences set to ‘keep messages for 7 days old,’ then instead of powering on the device radio to initiate a message delete from the device 250 the moment that the message has exceeded 7 days old, the message is deleted when the radio is powered on next. If the radio is already on, then pruning may occur as regularly scheduled.
- The request/transaction manager 235, can use the priorities for requests (e.g., by the prioritization engine 241) to manage outgoing traffic from the device 250 for resource optimization (e.g., to utilize the device radio more efficiently for battery conservation). For example, transactions/requests below a certain priority ranking may not trigger use of the radio on the device 250 if the radio is not already switched on, as controlled by the connection manager 265. In contrast, the radio controller 266 can turn on the radio such a request can be sent when a request for a transaction is detected to be over a certain priority level.
- In some embodiments, priority assignments (such as that determined by the local proxy 275 or another device/entity) can be used cause a remote device to modify its communication with the frequency with the mobile device or wireless device. For example, the remote device can be configured to send notifications to the device 250 when data of higher importance is available to be sent to the mobile device or wireless device.
- In some embodiments, transaction priority can be used in conjunction with characteristics of user activity in shaping or managing traffic, for example, by the traffic shaping engine 255. For example, the traffic shaping engine 255 can, in response to detecting that a user is dormant or inactive, wait to send low priority transactions from the device 250, for a period of time. In addition, the traffic shaping engine 255 can allow multiple low priority transactions to accumulate for batch transferring from the device 250 (e.g., via the batching module 257). In some embodiments, 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.
- In some embodiments, 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 some embodiments, an impending pruning event (pruning of an inbox), or any other low priority events, can be executed when a batch transfer occurs.
- In general, the batching capability can be disabled or enabled at the event/transaction level, application level, or session level, based on any one or combination of the following: user configuration, device limitations/settings, manufacturer specification, network provider parameters/limitations, platform-specific limitations/settings, device OS settings, etc. In some embodiments, batch transfer can be initiated when an application/window/file is closed out, exited, or moved into the background; users can optionally be prompted before initiating a batch transfer; users can also manually trigger batch transfers.
- In some embodiments, the local proxy 275 locally adjusts radio use on the device 250 by caching data in the cache 285. When requests or transactions from the device 250 can be satisfied by content stored in the cache 285, the radio controller 266 need not activate the radio to send the request to a remote entity (e.g., the host server 100, 300, as shown in
FIG. 1Band FIG. 5Aor a content provider/application server such as the server/provider 110 shown in the examples of FIG. 1Band FIG. 1C). As such, the local proxy 275 can use the local cache 285 and the cache policy manager 245 to locally store data for satisfying data requests to eliminate or reduce the use of the device radio for conservation of network resources and device battery consumption.
- In leveraging the local cache, once the request/transaction manager 225 intercepts a data request by an application on the device 250, the local repository 285 can be queried to determine if there is any locally stored response, and also determine whether the response is valid. When a valid response is available in the local cache 285, the response can be provided to the application on the device 250 without the device 250 needing to access the cellular network or wireless broadband network.
- If a valid response is not available, the local proxy 275 can query a remote proxy (e.g., the server proxy 325 of
FIG. 5A) 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. 1C) can be provided to the mobile device, possibly without the mobile device 250 needing to access the cellular network, thus relieving consumption of network resources.
- If a valid cache response is not available, or if cache responses are unavailable for the intercepted data request, the local proxy 275, for example, the caching policy manager 245, can send the data request to a remote proxy (e.g., server proxy 325 of
FIG. 5A) which forwards the data request to a content source (e.g., application server/content provider 110 of FIG. 1B) 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. 5A. The cache policy manager 245 can manage or process requests that use a variety of protocols, including but not limited to HTTP, HTTPS, IMAP, POP, SMTP, XMPP, and/or ActiveSync. The caching policy manager 245 can locally store responses for data requests in the local database 285 as cache entries, for subsequent use in satisfying same or similar data requests.
- The caching policy manager 245 can request that the remote proxy monitor responses for the data request and the remote proxy can notify the device 250 when an unexpected response to the data request is detected. In such an event, the cache policy manager 245 can erase or replace the locally stored response(s) on the device 250 when notified of the unexpected response (e.g., new data, changed data, additional data, etc.) to the data request. In some embodiments, the caching policy manager 245 is able to detect or identify the protocol used for a specific request, including but not limited to HTTP, HTTPS, IMAP, POP, SMTP, XMPP, and/or ActiveSync. In some embodiments, application specific handlers (e.g., via the application protocol module 246 of the caching policy manager 245) on the local proxy 275 allows for optimization of any protocol that can be port mapped to a handler in the distributed proxy (e.g., port mapped on the proxy server 325 in the example of
- In some embodiments, the local proxy 275 notifies the remote proxy such that the remote proxy can monitor responses received for the data request from the content source for changed results prior to returning the result to the device 250, for example, when the data request to the content source has yielded same results to be returned to the mobile device. In general, the local proxy 275 can simulate application server responses for applications on the device 250, using locally cached content. This can prevent utilization of the cellular network for transactions where new/changed data is not available, thus freeing up network resources and preventing network congestion.
- In some embodiments, the local proxy 275 includes an application behavior detector 236 to track, detect, observe, monitor, applications (e.g., proxy-aware and/or unaware applications 210 and 220) accessed or installed on the device 250. Application behaviors, or patterns in detected behaviors (e.g., via the pattern detector 237) of one or more applications accessed on the device 250 can be used by the local proxy 275 to optimize traffic in a wireless network needed to satisfy the data needs of these applications.
- For example, based on detected behavior of multiple applications, the traffic shaping engine 255 can align content requests made by at least some of the applications over the network (wireless network) (e.g., via the alignment module 256). The alignment module 256 can delay or expedite some earlier received requests to achieve alignment. When requests are aligned, the traffic shaping engine 255 can utilize the connection manager to poll over the network to satisfy application data requests. Content requests for multiple applications can be aligned based on behavior patterns or rules/settings including, for example, content types requested by the multiple applications (audio, video, text, etc.), device (e.g., mobile or wireless device) parameters, and/or network parameters/traffic conditions, network service provider constraints/specifications, etc.
- In some embodiments, the pattern detector 237 can detect recurrences in application requests made by the multiple applications, for example, by tracking patterns in application behavior. A tracked pattern can include, detecting that certain applications, as a background process, poll an application server regularly, at certain times of day, on certain days of the week, periodically in a predictable fashion, with a certain frequency, with a certain frequency in response to a certain type of event, in response to a certain type user query, frequency that requested content is the same, frequency with which a same request is made, interval between requests, applications making a request, or any combination of the above, for example.
- Such recurrences can be used by traffic shaping engine 255 to offload polling of content from a content source (e.g., from an application server/content provider 110 of
FIG. 1A) that would result from the application requests that would be performed at the mobile device or wireless device 250 to be performed instead, by a proxy server (e.g., proxy server 125 of FIG. 1Cor proxy server 325 of FIG. 5A) remote from the device 250. Traffic shaping engine 255 can decide to offload the polling when the recurrences match a rule. For example, there are multiple occurrences or requests for the same resource that have exactly the same content, or returned value, or based on detection of repeatable time periods between requests and responses such as a resource that is requested at specific times during the day. The offloading of the polling can decrease the amount of bandwidth consumption needed by the mobile device 250 to establish a wireless (cellular or other wireless broadband) connection with the content source for repetitive content polls.
- As a result of the offloading of the polling, locally cached content stored in the local cache 285 can be provided to satisfy data requests at the device 250, when content change is not detected in the polling of the content sources. As such, when data has not changed, application data needs can be satisfied without needing to enable radio use or occupying cellular bandwidth in a wireless network. When data has changed and/or new data has been received, the remote entity to which polling is offloaded, can notify the device 250. The remote entity may be the host server 300 as shown in the example of
- In some embodiments, 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. 1C) to generate and send the heartbeat messages to maintain a connection with the backend (e.g., application server/provider 110 in the example of FIG. 1A).
- The local proxy 275 generally represents any one or a portion of the functions described for the individual managers, modules, and/or engines. The local proxy 275 and device 250 can include additional or less components; more or less functions can be included, in whole or in part, without deviating from the novel art of the disclosure.
FIG. 4Bdepicts a block diagram illustrating a further example of components in the cache system shown in the example of FIG. 4Awhich is capable of caching and adapting caching strategies for mobile application behavior and/or network conditions.
- In some embodiments, the caching policy manager 245 includes a metadata generator 203, a cache look-up engine 205, a cache appropriateness decision engine 246, a poll schedule generator 247, an application protocol module 248, a cache or connect selection engine 249 and/or a local cache invalidator 244. The cache appropriateness decision engine 246 can further include a timing predictor 246 a,a content predictor 246 b, a request analyzer 246 c, and/or a response analyzer 246 d, and the cache or connect selection engine 249 includes a response scheduler 249 a. The metadata generator 203 and/or the cache look-up engine 205 are coupled to the cache 285 (or local cache) for modification or addition to cache entries or querying thereof.
- The cache look-up engine 205 may further include an ID or URI filter 205 a, the local cache invalidator 244 may further include a TTL manager 244 a, and the poll schedule generator 247 may further include a schedule update engine 247 a and/or a time adjustment engine 247 b. One embodiment of caching policy manager 245 includes an application cache policy repository 243. In some embodiments, the application behavior detector 236 includes a pattern detector 237, a poll interval detector 238, an application profile generator 239, and/or a priority engine 241. The poll interval detector 238 may further include a long poll detector 238 a having a response/request tracking engine 238 b. The poll interval detector 238 may further include a long poll hunting detector 238 c. The application profile generator 239 can further include a response delay interval tracker 239 a.
- The pattern detector 237, application profile generator 239, and the priority engine 241 were also described in association with the description of the pattern detector shown in the example of
FIG. 4A. One embodiment further includes an application profile repository 242 which can be used by the local proxy 275 to store information or metadata regarding application profiles (e.g., behavior, patterns, type of HTTP requests, etc.)
- The cache appropriateness decision engine 246 can detect, assess, or determine whether content from a content source (e.g., application server/content provider 110 in the example of
FIG. 1B) with which a mobile device 250 interacts and has content that may be suitable for caching. For example, the decision engine 246 can use information about a request and/or a response received for the request initiated at the mobile device 250 to determine cacheability, potential cacheability, or non-cacheability. In some instances, the decision engine 246 can initially verify whether a request is directed to a blacklisted destination or whether the request itself originates from a blacklisted client or application. If so, additional processing and analysis may not be performed by the decision engine 246 and the request may be allowed to be sent over the air to the server to satisfy the request. The black listed destinations or applications/clients (e.g., mobile applications) can be maintained locally in the local proxy (e.g., in the application profile repository 242) or remotely (e.g., in the proxy server 325 or another entity).
- In some embodiments, the decision engine 246, for example, via the request analyzer 246 c, collects information about an application or client request generated at the mobile device 250. The request information can include request characteristics information including, for example, request method. For example, the request method can indicate the type of HTTP request generated by the mobile application or client. In some embodiments, response to a request can be identified as cacheable or potentially cacheable if the request method is a GET request or POST request. Other types of requests (e.g., OPTIONS, HEAD, PUT, DELETE, TRACE, or CONNECT) may or may not be cached. In general, HTTP requests with uncacheable request methods will not be cached.
- Request characteristics information can further include information regarding request size, for example. Responses to requests (e.g., HTTP requests) with body size exceeding a certain size will not be cached. For example, cacheability can be determined if the information about the request indicates that a request body size of the request does not exceed a certain size. In some instances, the maximum cacheable request body size can be set to 8092 bytes. In other instances, different values may be used, dependent on network capacity or network operator specific settings, for example.
- In some instances, content from a given application server/content provider (e.g., the server/content provider 110 of
FIG. 1C) is determined to be suitable for caching based on a set of criteria, for example, criteria specifying time criticality of the content that is being requested from the content source. In some embodiments, the local proxy (e.g., the local proxy 175 or 275 of FIG. 1Cand FIG. 4A) applies a selection criteria to store the content from the host server which is requested by an application as cached elements in a local cache on the mobile device to satisfy subsequent requests made by the application.
- The cache appropriateness decision engine 246, further based on detected patterns of requests sent from the mobile device 250 (e.g., by a mobile application or other types of clients on the device 250) and/or patterns of received responses, can detect predictability in requests and/or responses. For example, the request characteristics information collected by the decision engine 246, (e.g., the request analyzer 246 c) can further include periodicity information between a request and other requests generated by a same client on the mobile device or other requests directed to the same host (e.g., with similar or same identifier parameters).
- Periodicity can be detected, by the decision engine 246 or the request analyzer 246 c, when the request and the other requests generated by the same client occur at a fixed rate or nearly fixed rate, or at a dynamic rate with some identifiable or partially or wholly reproducible changing pattern. If the requests are made with some identifiable pattern (e.g., regular intervals, intervals having a detectable pattern, or trend (e.g., increasing, decreasing, constant, etc.) the timing predictor 246 a can determine that the requests made by a given application on a device is predictable and identify it to be potentially appropriate for caching, at least from a timing standpoint.
- An identifiable pattern or trend can generally include any application or client behavior which may be simulated either locally, for example, on the local proxy 275 on the mobile device 250 or simulated remotely, for example, by the proxy server 325 on the host 300, or a combination of local and remote simulation to emulate application behavior.
- In some embodiments, the decision engine 246, for example, via the response analyzer 246 d, can collect information about a response to an application or client request generated at the mobile device 250. The response is typically received from a server or the host of the application (e.g., mobile application) or client which sent the request at the mobile device 250. In some instances, the mobile client or application can be the mobile version of an application (e.g., social networking, search, travel management, voicemail, contact manager, email) or a web site accessed via a web browser or via a desktop client.
- For example, response characteristics information can include an indication of whether transfer encoding or chunked transfer encoding is used in sending the response. In some instances, responses to HTTP requests with transfer encoding or chunked transfer encoding are not cached, and therefore are also removed from further analysis. The rationale here is that chunked responses are usually large and non-optimal for caching, since the processing of these transactions may likely slow down the overall performance. Therefore, In some embodiments, cacheability or potential for cacheability can be determined when transfer encoding is not used in sending the response.
- In addition, the response characteristics information can include an associated status code of the response which can be identified by the response analyzer 246 d. In some instances, HTTP responses with uncacheable status codes are typically not cached. The response analyzer 246 d can extract the status code from the response and determine whether it matches a status code which is cacheable or uncacheable. Some cacheable status codes include by way of example: 200—OK, 301—Redirect, 302—Found, 303—See other, 304—Not Modified, 307 Temporary Redirect, or 500—Internal server error. Some uncacheable status codes can include, for example, 403—Forbidden or 404—Not found.
- In some embodiments, cacheability or potential for cacheability can be determined if the information about the response does not indicate an uncacheable status code or indicates a cacheable status code. If the response analyzer 246 d detects an uncacheable status code associated with a given response, the specific transaction (request/response pair) may be eliminated from further processing and determined to be uncacheable on a temporary basis, a semi-permanent, or a permanent basis. If the status code indicates cacheability, the transaction (e.g., request and/or response pair) may be subject to further processing and analysis to confirm cacheability.
- Response characteristics information can also include response size information. In general, responses can be cached locally at the mobile device 250 if the responses do not exceed a certain size. In some instances, the default maximum cached response size is set to 115 KB. In other instances, the max cacheable response size may be different and/or dynamically adjusted based on operating conditions, network conditions, network capacity, user preferences, network operator requirements, or other application-specific, user specific, and/or device-specific reasons. In some embodiments, the response analyzer 246 d can identify the size of the response, and cacheability or potential for cacheability can be determined if a given threshold or max value is not exceeded by the response size.
- Furthermore, response characteristics information can include response body information for the response to the request and other response to other requests generated by a same client on the mobile device, or directed to a same content host or application server. The response body information for the response and the other responses can be compared, for example, by the response analyzer 246 d, to prevent the caching of dynamic content (or responses with content that changes frequently and cannot be efficiently served with cache entries, such as financial data, stock quotes, news feeds, real-time sporting event activities, etc.), such as content that would no longer be relevant or up-to-date if served from cached entries.
- The cache appropriateness decision engine 246 (e.g., the content predictor 246 b) can definitively identify repeatability or identify indications of repeatability, potential repeatability, or predictability in responses received from a content source (e.g., the content host/application server 110 shown in the example of
FIG. 1C). Repeatability can be detected by, for example, tracking at least two responses received from the content source and determines if the two responses are the same. For example, cacheability can be determined, by the response analyzer 246 d, if the response body information for the response and the other responses sent by the same mobile client or directed to the same host/server are same or substantially the same. The two responses may or may not be responses sent in response to consecutive requests. In some embodiments, hash values of the responses received for requests from a given application are used to determine repeatability of content (with or without heuristics) for the application in general and/or for the specific request. Additional same responses may be required for some applications or under certain circumstances.
- Repeatability in received content need not be 100% ascertained. For example, responses can be determined to be repeatable if a certain number or a certain percentage of responses are the same, or similar. The certain number or certain percentage of same/similar responses can be tracked over a select period of time, set by default or set based on the application generating the requests (e.g., whether the application is highly dynamic with constant updates or less dynamic with infrequent updates). Any indicated predictability or repeatability, or possible repeatability, can be utilized by the distributed system in caching content to be provided to a requesting application or client on the mobile device 250.
- In some embodiments, for a long poll type request, the local proxy 175 can begin to cache responses on a third request when the response delay times for the first two responses are the same, substantially the same, or detected to be increasing in intervals. In general, the received responses for the first two responses should be the same, and upon verifying that the third response received for the third request is the same (e.g., if R0=R1=R2), the third response can be locally cached on the mobile device. Less or more same responses may be required to begin caching, depending on the type of application, type of data, type of content, user preferences, or carrier/network operator specifications.
- Increasing response delays with same responses for long polls can indicate a hunting period (e.g., a period in which the application/client on the mobile device is seeking the longest time between a request and response that a given network will allow), as detected by the long poll hunting detector 238 c of the application behavior detector 236.
- An example can be described below using T0, T1, T2, where T indicates the delay time between when a request is sent and when a response (e.g., the response header) is detected/received for consecutive requests:
- T0=Response0(t)−Request0(t)=180 s. (+/−tolerance)
- T1=Response1(t)−Request1(t)=240 s. (+/−tolerance)
- T2=Response2(t)−Request2(t)=500 s. (+/−tolerance)
- In the example timing sequence shown above, T0<T1<T2, this may indicate a hunting pattern for a long poll when network timeout has not yet been reached or exceeded. Furthermore, if the responses R0, R1, and R2 received for the three requests are the same, R2 can be cached. In this example, R2 is cached during the long poll hunting period without waiting for the long poll to settle, thus expediting response caching (e.g., this is optional accelerated caching behavior which can be implemented for all or select applications).
- As such, the local proxy 275 can specify information that can be extracted from the timing sequence shown above (e.g., polling schedule, polling interval, polling type) to the proxy server and begin caching and to request the proxy server to begin polling and monitoring the source (e.g., using any of T0, T1, T2 as polling intervals but typically T2, or the largest detected interval without timing out, and for which responses from the source is received will be sent to the proxy server 325 of
FIG. 5Afor use in polling the content source (e.g., application server/service provider 310)).
- However, if the time intervals are detected to be getting shorter, the application (e.g., mobile application)/client may still be hunting for a time interval for which a response can be reliably received from the content source (e.g., application/server server/provider 110 or 310), and as such caching typically should not begin until the request/response intervals indicate the same time interval or an increasing time interval, for example, for a long poll type request.
- An example of handling a detected decreasing delay can be described below using T0, T1, T2, T3, and T4 where T indicates the delay time between when a request is sent and when a response (e.g., the response header) is detected/received for consecutive requests:
- T0=Response0(t)−Request0(t)=160 s. (+/−tolerance)
- T1=Response1(t)−Request1(t)=240 s. (+/−tolerance)
- T2=Response2(t)−Request2(t)=500 s. (+/−tolerance)
- T3=Time out at 700 s. (+/−tolerance)
- T4=Response4(t)−Request4(t)=600 (+/−tolerance)
- If a pattern for response delays T1<T2<T3>T4 is detected, as shown in the above timing sequence (e.g., detected by the long poll hunting detector 238 c of the application behavior detector 236), it can be determined that T3 likely exceeded the network time out during a long poll hunting period. In Request 3, a response likely was not received since the connection was terminated by the network, application, server, or other reason before a response was sent or available. On Request 4 (after T4), if a response (e.g., Response 4) is detected or received, the local proxy 275 can then use the response for caching (if the content repeatability condition is met). The local proxy can also use T4 as the poll interval in the polling schedule set for the proxy server to monitor/poll the content source.
- Note that the above description shows that caching can begin while long polls are in hunting mode in the event of detecting increasing response delays, as long as responses are received and not timed out for a given request. This can be referred to as the optional accelerated caching during long poll hunting. Caching can also begin after the hunting mode (e.g., after the poll requests have settled to a constant or near constant delay value) has completed. Note that hunting may or may not occur for long polls and when hunting occurs; the proxy 275 can generally detect this and determine whether to begin to cache during the hunting period (increasing intervals with same responses) or wait until the hunt settles to a stable value.
- In some embodiments, the timing predictor 246 a of the cache appropriateness decision engine 246 can track timing of responses received from outgoing requests from an application (e.g., mobile application) or client to detect any identifiable patterns which can be partially wholly reproducible, such that locally cached responses can be provided to the requesting client on the mobile device 250 in a manner that simulates content source (e.g., application server/content provider 110 or 310) behavior. For example, the manner in which (e.g., from a timing standpoint) responses or content would be delivered to the requesting application/client on the device 250. This ensures preservation of user experience when responses to application or mobile client requests are served from a local and/or remote cache instead of being retrieved/received directly from the content source (e.g., application, content provider 110 or 310).
- In some embodiments, the decision engine 246 or the timing predictor 246 a determines the timing characteristics a given application (e.g., mobile application) or client from, for example, the request/response tracking engine 238 b and/or the application profile generator 239 (e.g., the response delay interval tracker 239 a). Using the timing characteristics, the timing predictor 246 a determines whether the content received in response to the requests are suitable or are potentially suitable for caching. For example, poll request intervals between two consecutive requests from a given application can be used to determine whether request intervals are repeatable (e.g., constant, near constant, increasing with a pattern, decreasing with a pattern, etc.) and can be predicted and thus reproduced at least some of the times either exactly or approximated within a tolerance level.
- In some instances, the timing characteristics of a given request type for a specific application, for multiple requests of an application, or for multiple applications can be stored in the application profile repository 242. The application profile repository 242 can generally store any type of information or metadata regarding application request/response characteristics including timing patterns, timing repeatability, content repeatability, etc.
- The application profile repository 242 can also store metadata indicating the type of request used by a given application (e.g., long polls, long-held HTTP requests, HTTP streaming, push, COMET push, etc.) Application profiles indicating request type by applications can be used when subsequent same/similar requests are detected, or when requests are detected from an application which has already been categorized. In this manner, timing characteristics for the given request type or for requests of a specific application which has been tracked and/or analyzed, need not be reanalyzed.
- Application profiles can be associated with a time-to-live (e.g., or a default expiration time). The use of an expiration time for application profiles, or for various aspects of an application or request's profile can be used on a case by case basis. The time-to-live or actual expiration time of application profile entries can be set to a default value or determined individually, or a combination thereof. Application profiles can also be specific to wireless networks, physical networks, network operators, or specific carriers.
- One embodiment includes an application blacklist manager 201. The application blacklist manager 201 can be coupled to the application cache policy repository 243 and can be partially or wholly internal to local proxy or the caching policy manager 245. Similarly, the blacklist manager 201 can be partially or wholly internal to local proxy or the application behavior detector 236. The blacklist manager 201 can aggregate, track, update, manage, adjust, or dynamically monitor a list of destinations of servers/host that are ‘blacklisted,’ or identified as not cached, on a permanent or temporary basis. The blacklist of destinations, when identified in a request, can potentially be used to allow the request to be sent over the (cellular) network for servicing. Additional processing on the request may not be performed since it is detected to be directed to a blacklisted destination.
- Blacklisted destinations can be identified in the application cache policy repository 243 by address identifiers including specific URIs or patterns of identifiers including URI patterns. In general, blacklisted destinations can be set by or modified for any reason by any party including the user (owner/user of mobile device 250), operating system/mobile platform of device 250, the destination itself, network operator (of cellular network), Internet service provider, other third parties, or according to a list of destinations for applications known to be uncacheable/not suited for caching. Some entries in the blacklisted destinations may include destinations aggregated based on the analysis or processing performed by the local proxy (e.g., cache appropriateness decision engine 246).
- For example, applications or mobile clients on the mobile device for which responses have been identified as non-suitable for caching can be added to the blacklist. Their corresponding hosts/servers may be added in addition to or in lieu of an identification of the requesting application/client on the mobile device 250. Some or all of such clients identified by the proxy system can be added to the blacklist. For example, for all application clients or applications that are temporarily identified as not being suitable for caching, only those with certain detected characteristics (based on timing, periodicity, frequency of response content change, content predictability, size, etc.) can be blacklisted.
- The blacklisted entries may include a list of requesting applications or requesting clients on the mobile device (rather than destinations) such that, when a request is detected from a given application or given client, it may be sent through the network for a response, since responses for blacklisted clients/applications are in most circumstances not cached.
- A given application profile may also be treated or processed differently (e.g., different behavior of the local proxy 275 and the remote proxy 325) depending on the mobile account associated with a mobile device from which the application is being accessed. For example, a higher paying account, or a premier account may allow more frequent access of the wireless network or higher bandwidth allowance thus affecting the caching policies implemented between the local proxy 275 and proxy server 325 with an emphasis on better performance compared to conservation of resources. A given application profile may also be treated or processed differently under different wireless network conditions (e.g., based on congestion or network outage, etc.).
- Note that cache appropriateness can be determined, tracked, and managed for multiple clients or applications on the mobile device 250. Cache appropriateness can also be determined for different requests or request types initiated by a given client or application on the mobile device 250. The caching policy manager 245, along with the timing predictor 246 a and/or the content predictor 246 b which heuristically determines or estimates predictability or potential predictability, can track, manage and store cacheability information for various application or various requests for a given application. Cacheability information may also include conditions (e.g., an application can be cached at certain times of the day, or certain days of the week, or certain requests of a given application can be cached, or all requests with a given destination address can be cached) under which caching is appropriate which can be determined and/or tracked by the cache appropriateness decision engine 246 and stored and/or updated when appropriate in the application cache policy repository 243 coupled to the cache appropriateness decision engine 246.
- The information in the application cache policy repository 243 regarding cacheability of requests, applications, and/or associated conditions can be used later on when same requests are detected. In this manner, the decision engine 246 and/or the timing and content predictors 246 a/b need not track and reanalyze request/response timing and content characteristics to make an assessment regarding cacheability. In addition, the cacheability information can in some instances be shared with local proxies of other mobile devices by way of direct communication or via the host server (e.g., proxy server 325 of host server 300).
- For example, cacheability information detected by the local proxy 275 on various mobile devices can be sent to a remote host server or a proxy server 325 on the host server (e.g., host server 300 or proxy server 325 shown in the example of
FIG. 5A, host 100 and proxy server 125 in the example of FIG. 1B-1C). The remote host or proxy server can then distribute the information regarding application-specific, request-specific cacheability information and/or any associated conditions to various mobile devices or their local proxies in a wireless network or across multiple wireless networks (same service provider or multiple wireless service providers) for their use.
- In general, the selection criteria for caching can further include, by way of example but not limitation, the state of the mobile device indicating whether the mobile device is active or inactive, network conditions, and/or radio coverage statistics. The cache appropriateness decision engine 246 can in any one or any combination of the criteria, and in any order, identifying sources for which caching may be suitable.
- Once application servers/content providers having identified or detected content that is potentially suitable for local caching on the mobile device 250, the cache policy manager 245 can proceed to cache the associated content received from the identified sources by storing content received from the content source as cache elements in a local cache (e.g., local cache 185 or 285 shown in the examples of
FIG. 1B-1Cand FIG. 4A, respectively) on the mobile device 250.
- The response can be stored in the cache 285 (e.g., also referred as the local cache) as a cache entry. In addition to the response to a request, the cached entry can include response metadata having additional information regarding caching of the response. The metadata may be generated by the metadata generator 203 and can include, for example, timing data such as the access time of the cache entry or creation time of the cache entry. Metadata can include additional information, such as any information suited for use in determining whether the response stored as the cached entry is used to satisfy the subsequent response. For example, metadata information can further include, request timing history (e.g., including request time, request start time, request end time), hash of the request and/or response, time intervals or changes in time intervals, etc.
- In some embodiments, the cache entry is stored in the cache 285 in association with a time-to-live (TTL), which for example may be assigned or determined by the TTL manager 244 a of the cache invalidator 244. The time-to-live of a cache entry is the amount of time the entry is persisted in the cache 285 regardless of whether the response is still valid or relevant for a given request or client/application on the mobile device 250. For example, if the time-to-live of a given cache entry is set to 12 hours, the cache entry is purged, removed, or otherwise indicated as having exceeded the time-to-live, even if the response body contained in the cache entry is still current and applicable for the associated request.
- A default time-to-live can be automatically used for all entries unless otherwise specified (e.g., by the TTL manager 244 a), or each cache entry can be created with its individual TTL (e.g., determined by the TTL manager 244 a based on various dynamic or static criteria). Note that each entry can have a single time-to-live associated with both the response data and any associated metadata. In some instances, the associated metadata may have a different time-to-live (e.g., a longer time-to-live) than the response data.
- The content source having content for caching can, in addition or in alternate, be identified to a proxy server (e.g., proxy server 125 or 325 shown in the examples of
FIG. 1B-1Cand FIG. 5A, respectively) remote from and in wireless communication with the mobile device 250 such that the proxy server can monitor the content source (e.g., application server/content provider 110) for new or changed data. Similarly, the local proxy (e.g., the local proxy 175 or 275 of FIG. 1B-1Cand FIG. 4A, respectively) can identify to the proxy server that content received from a specific application server/content provider is being stored as cached elements in the local cache 285.
- Once content has been locally cached, the cache policy manager 245, upon receiving future polling requests to contact the application server/content host (e.g., 110 or 310), can retrieve the cached elements from the local cache to respond to the polling request made at the mobile device 250 such that a radio of the mobile device is not activated to service the polling request. For example, the cache look-up engine 205 can query the cache 285 to identify the response to be served to a response. The response can be served from the cache in response to identifying a matching cache entry and also using any metadata stored with the response in the cache entry. The cache entries can be queried by the cache look-up engine using a URI of the request or another type of identifier (e.g., via the ID or URI filter 205 a). The cache-lookup engine 205 can further use the metadata (e.g., extract any timing information or other relevant information) stored with the matching cache entry to determine whether response is still suited for use in being served to a current request.
- Note that the cache-look-up can be performed by the engine 205 using one or more of various multiple strategies. In some embodiments, multiple cook-up strategies can be executed sequentially on each entry store din the cache 285, until at least one strategy identifies a matching cache entry. The strategy employed to performing cache look-up can include a strict matching criteria or a matching criteria which allows for non-matching parameters.
- For example, the look-up engine 205 can perform a strict matching strategy which searches for an exact match between an identifier (e.g., a URI for a host or resource) referenced in a present request for which the proxy is attempting to identify a cache entry and an identifier stored with the cache entries. In the case where identifiers include URIs or URLs, the matching algorithm for strict matching will search for a cache entry where all the parameters in the URLs match. For example:
- 1. Cache contains entry for http://test.com/products/
- 2. Request is being made to URI http://test.com/products/
- Strict strategy will find a match, since both URIs are same.
- 1. Cache contains entry for http://test.com/products/?query=all
- 2. Request is being made to URI http://test.com/products/?query=sub
- Under the strict strategy outlined above, a match will not be found since the URIs differ in the query parameter.
- In another example strategy, the look-up engine 205 looks for a cache entry with an identifier that partially matches the identifier references in a present request for which the proxy is attempting to identify a matching cache entry. For example, the look-up engine 205 may look for a cache entry with an identifier which differs from the request identifier by a query parameter value. In utilizing this strategy, the look-up engine 205 can collect information collected for multiple previous requests (e.g., a list of arbitrary parameters in an identifier) to be later checked with the detected arbitrary parameter in the current request. For example, in the case where cache entries are stored with URI or URL identifiers, the look-up engine may search for a cache entry with a URI differing by a query parameter. If found, the engine 205 can examine the cache entry for information collected during previous requests (e.g. a list of arbitrary parameters) and checked whether the arbitrary parameter detected in or extracted from the current URI/URL belongs to the arbitrary parameters list.
- 1. Cache contains entry for http://test.com/products/?query=all, where query is marked as arbitrary.
- 2. Request is being made to URI http://text.com/products/?query=sub
- Match will be found, since query parameter is marked as arbitrary.
- 1. Cache contains entry for http://test.com/products/?query=all, where query is marked as arbitrary.
- 2. Request is being made to URI http://test.com/products/?query=sub&sort=asc
- Match will not be found, since current request contains sort parameter which is not marked as arbitrary in the cache entry.
- Additional strategies for detecting cache hit may be employed. These strategies can be implemented singly or in any combination thereof. A cache-hit can be determined when any one of these strategies determines a match. A cache miss may be indicated when the look-up engine 205 determines that the requested data cannot be served from the cache 285, for any reason. For example, a cache miss may be determined when no cache entries are identified for any or all utilized look-up strategies.
- Cache miss may also be determined when a matching cache entry exists but determined to be invalid or irrelevant for the current request. For example, the look-up engine 205 may further analyze metadata (e.g., which may include timing data of the cache entry) associated with the matching cache entry to determine whether it is still suitable for use in responding to the present request.
- When the look-up engine 205 has identified a cache hit (e.g., an event indicating that the requested data can be served from the cache), the stored response in the matching cache entry can be served from the cache to satisfy the request of an application/client.
- By servicing requests using cache entries stored in cache 285, network bandwidth and other resources need not be used to request/receive poll responses which may have not changed from a response that has already been received at the mobile device 250. Such servicing and fulfilling application (e.g., mobile application) requests locally via cache entries in the local cache 285 allows for more efficient resource and mobile network traffic utilization and management since the request need not be sent over the wireless network further consuming bandwidth. In general, the cache 285 can be persisted between power on/off of the mobile device 250, and persisted across application/client refreshes and restarts.
- For example, the local proxy 275, upon receipt of an outgoing request from its mobile device 250 or from an application or other type of client on the mobile device 250, can intercept the request and determine whether a cached response is available in the local cache 285 of the mobile device 250. If so, the outgoing request is responded to by the local proxy 275 using the cached response on the cache of the mobile device. As such, the outgoing request can be filled or satisfied without a need to send the outgoing request over the wireless network, thus conserving network resources and battery consumption.
- In some embodiments, the responding to the requesting application/client on the device 250 is timed to correspond to a manner in which the content server would have responded to the outgoing request over a persistent connection (e.g., over the persistent connection, or long-held HTTP connection, long poll type connection, that would have been established absent interception by the local proxy). The timing of the response can be emulated or simulated by the local proxy 275 to preserve application behavior such that end user experience is not affected, or minimally affected by serving stored content from the local cache 285 rather than fresh content received from the intended content source (e.g., content host/application server 110 of
FIG. 1B-FIG. 1C). The timing can be replicated exactly or estimated within a tolerance parameter, which may go unnoticed by the user or treated similarly by the application so as to not cause operation issues.
- For example, the outgoing request can be a request for a persistent connection intended for the content server (e.g., application server/content provider of examples of
FIG. 1B-1C). In a persistent connection (e.g., long poll, COMET-style push or any other push simulation in asynchronous HTTP requests, long-held HTTP request, HTTP streaming, or others) with a content source (server), the connection is held for some time after a request is sent. The connection can typically be persisted between the mobile device and the server until content is available at the server to be sent to the mobile device. Thus, there typically can be some delay in time between when a long poll request is sent and when a response is received from the content source. If a response is not provided by the content source for a certain amount of time, the connection may also terminate due to network reasons (e.g., socket closure) if a response is not sent.
- Thus, to emulate a response from a content server sent over a persistent connection (e.g., a long poll style connection), the manner of response of the content server can be simulated by allowing a time interval to elapse before responding to the outgoing request with the cached response. The length of the time interval can be determined on a request by request basis or on an application by application (client by client basis), for example.
- In some embodiments, the time interval is determined based on request characteristics (e.g., timing characteristics) of an application on the mobile device from which the outgoing request originates. For example, poll request intervals (e.g., which can be tracked, detected, and determined by the long poll detector 238 a of the poll interval detector 238) can be used to determine the time interval to wait before responding to a request with a local cache entry and managed by the response scheduler 249 a.
- Some embodiments of the cache policy manager 245 includes a poll schedule generator 247 which can generate a polling schedule for one or more applications on the mobile device 250. The polling schedule can specify a polling interval that can be employed by an entity which is physically distinct and/or separate from the mobile device 250 in monitoring the content source for one or more applications (such that cached responses can be verified periodically by polling a host server (host server 110 or 310) to which the request is directed) on behalf of the mobile device. One example of such an external entity which can monitor the content at the source for the mobile device 250 is a proxy server (e.g., proxy server 125 or 325 shown in the examples of
FIG. 1B-1Cand FIG. 5A-C).
- The polling schedule (e.g., including a rate/frequency of polling) can be determined, for example, based on the interval between the polling requests directed to the content source from the mobile device. The polling schedule or rate of polling may be determined at the mobile device 250 (by the local proxy). In some embodiments, the poll interval detector 238 of the application behavior detector 236 can monitor polling requests directed to a content source from the mobile device 250 in order to determine an interval between the polling requests made from any or all application (e.g., mobile application).
- For example, the poll interval detector 238 can track requests and responses for applications or clients on the device 250. In some embodiments, consecutive requests are tracked prior to detection of an outgoing request initiated from the application (e.g., mobile application) on the mobile device 250 by the same mobile client or application (e.g., mobile application). The polling rate can be determined using request information collected for the request for which the response is cached. In some embodiments, the rate is determined from averages of time intervals between previous requests generated by the same client which generated the request. For example, a first interval may be computed between the current request and a previous request, and a second interval can be computed between the two previous requests. The polling rate can be set from the average of the first interval and the second interval and sent to the proxy server in setting up the caching strategy.
- Alternate intervals may be computed in generating an average; for example, multiple previous requests in addition to two previous requests may be used, and more than two intervals may be used in computing an average. In general, in computing intervals, a given request need not have resulted in a response to be received from the host server/content source in order to use it for interval computation. In other words, the timing characteristics of a given request may be used in interval computation, as long as the request has been detected, even if the request failed in sending, or if the response retrieval failed.
- Some embodiments of the poll schedule generator 247 includes a schedule update engine 247 a and/or a time adjustment engine 247 b. The schedule update engine 247 a can determine a need to update a rate or polling interval with which a given application server/content host from a previously set value, based on a detected interval change in the actual requests generated from a client or application (e.g., mobile application) on the mobile device 250.
- For example, a request for which a monitoring rate was determined may now be sent from the application (e.g., mobile application) or client at a different request interval. The scheduled update engine 247 a can determine the updated polling interval of the actual requests and generate a new rate, different from the previously set rate to poll the host at on behalf of the mobile device 250. The updated polling rate can be communicated to the remote proxy (proxy server 325) over the cellular network for the remote proxy to monitor the given host. In some instances, the updated polling rate may be determined at the remote proxy or remote entity which monitors the host.
- In some embodiments, the time adjustment engine 247 b can further optimize the poll schedule generated to monitor the application server/content source (110 or 310). For example, the time adjustment engine 247 b can optionally specify a time to start polling to the proxy server. For example, in addition to setting the polling interval at which the proxy server is to monitor the application, server/content host can also specify the time at which an actual request was generated at the mobile client/application.
- However, in some cases, due to inherent transmission delay or added network delays or other types of latencies, the remote proxy server receives the poll setup from the local proxy with some delay (e.g., a few minutes, or a few seconds). This has the effect of detecting response change at the source after a request is generated by the mobile client/application causing the invalidate of the cached response to occur after it has once again been served to the application after the response is no longer current or valid.
- To resolve this non-optimal result of serving the out-dated content once again before invalidating it, the time adjustment engine 247 b can specify the time (t0) at which polling should begin in addition to the rate, where the specified initial time t0 can be specified to the proxy server 325 as a time that is less than the actual time when the request was generated by the mobile app/client. This way, the server polls the resource slightly before the generation of an actual request by the mobile client such that any content change can be detected prior to an actual application request. This prevents invalid or irrelevant out-dated content/response from being served once again before fresh content is served.
- In some embodiments, an outgoing request from a mobile device 250 is detected to be for a persistent connection (e.g., a long poll, COMET style push, and long-held (HTTP) request) based on timing characteristics of prior requests from the same application or client on the mobile device 250. For example, requests and/or corresponding responses can be tracked by the request/response tracking engine 238 b of the long poll detector 238 a of the poll interval detector 238.
- The timing characteristics of the consecutive requests can be determined to set up a polling schedule for the application or client. The polling schedule can be used to monitor the content source (content source/application server) for content changes such that cached content stored on the local cache in the mobile device 250 can be appropriately managed (e.g., updated or discarded). In some embodiments, the timing characteristics can include, for example, a response delay time (‘D’) and/or an idle time (‘IT’).
- In some embodiments, the response/request tracking engine 238 b can track requests and responses to determine, compute, and/or estimate, the timing diagrams for applicant or client requests.
- For example, the response/request tracking engine 238 b detects a first request (Request 0) initiated by a client on the mobile device and a second request (Request 1) initiated by the client on the mobile device after a response is received at the mobile device responsive to the first request. The second request is one that is subsequent to the first request.
- In some embodiments, the response/request tracking engine 238 b can track requests and responses to determine, compute, and/or estimate the timing diagrams for applicant or client requests. The response/request tracking engine 238 b can detect a first request initiated by a client on the mobile device and a second request initiated by the client on the mobile device after a response is received at the mobile device responsive to the first request. The second request is one that is subsequent to the first request.
- The response/request tracking engine 238 b further determines relative timings between the first, second requests, and the response received in response to the first request. In general, the relative timings can be used by the long poll detector 238 a to determine whether requests generated by the application are long poll requests.
- Note that in general, the first and second requests that are used by the response/request tracking engine 238 b in computing the relative timings are selected for use after a long poll hunting period has settled or in the event when long poll hunting does not occur. Timing characteristics that are typical of a long poll hunting period can be, for example, detected by the long poll hunting detector 238 c. In other words, the requests tracked by the response/request tracking engine 238 b and used for determining whether a given request is a long poll occurs after the long poll has settled.
- In some embodiments, the long poll hunting detector 238 c can identify or detect hunting mode, by identifying increasing request intervals (e.g., increasing delays). The long poll hunting detector 238 a can also detect hunting mode by detecting increasing request intervals, followed by a request with no response (e.g., connection timed out), or by detecting increasing request intervals followed by a decrease in the interval. In addition, the long poll hunting detector 238 c can apply a filter value or a threshold value to request-response time delay value (e.g., an absolute value) above which the detected delay can be considered to be a long poll request-response delay. The filter value can be any suitable value characteristic of long polls and/or network conditions (e.g., 2 s, 5 s, 10 s, 15 s, 20 s., etc.) and can be used as a filter or threshold value.
- The response delay time (‘D’) refers to the start time to receive a response after a request has been sent and the idle refers to time to send a subsequent request after the response has been received. In some embodiments, the outgoing request is detected to be for a persistent connection based on a comparison (e.g., performed by the tracking engine 238 b) of the response delay time relative (‘D’) or average of (‘D’) (e.g., any average over any period of time) to the idle time (‘IT’), for example, by the long poll detector 238 a. The number of averages used can be fixed, dynamically adjusted, or changed over a longer period of time. For example, the requests initiated by the client are determined to be long poll requests if the response delay time interval is greater than the idle time interval (D>IT or D>>IT). In some embodiments, the tracking engine 238 b of the long poll detector computes, determines, or estimates the response delay time interval as the amount of time elapsed between time of the first request and initial detection or full receipt of the response.
- In some embodiments, a request is detected to be for a persistent connection when the idle time (‘IT’) is short since persistent connections, established in response to long poll requests or long poll HTTP requests for example, can also be characterized in detecting immediate or near-immediate issuance of a subsequent request after receipt of a response to a previous request (e.g., IT ˜0). As such, the idle time (‘IT’) can also be used to detect such immediate or near-immediate re-request to identify long poll requests. The absolute or relative timings determined by the tracking engine 238 b are used to determine whether the second request is immediately or near-immediately re-requested after the response to the first request is received. For example, a request may be categorized as a long poll request if D+RT+IT˜D+RT since IT is small for this to hold true. IT may be determined to be small if it is less than a threshold value. Note that the threshold value could be fixed or calculated over a limited time period (a session, a day, a month, etc.), or calculated over a longer time period (e.g., several months or the life of the analysis). For example, for every request, the average IT can be determined, and the threshold can be determined using this average IT (e.g., the average IT less a certain percentage may be used as the threshold). This can allow the threshold to automatically adapt over time to network conditions and changes in server capability, resource availability or server response. A fixed threshold can take upon any value including by way of example but not limitation (e.g., 1 s. 2 s. 3 s. . . . etc.).
- In some embodiments, the long poll detector 238 a can compare the relative timings (e.g., determined by the tracker engine 238 b) to request-response timing characteristics for other applications to determine whether the requests of the application are long poll requests. For example, the requests initiated by a client or application can be determined to be long poll requests if the response delay interval time (‘D’) or the average response delay interval time (e.g., averaged over×number of requests or any number of delay interval times averaged over×amount of time) is greater than a threshold value.
- The threshold value can be determined using response delay interval times for requests generated by other clients, for example by the request/response tracking engine 238 b and/or by the application profile generator 239 (e.g., the response delay interval tracker 239 a). The other clients may reside on the same mobile device and the threshold value is determined locally by components on the mobile device. The threshold value can be determined for all requests over all resources server over all networks, for example. The threshold value can be set to a specific constant value (e.g., 30 seconds, for example) to be used for all requests, or any request which does not have an applicable threshold value (e.g., long poll is detected if D>30 seconds).
- In some instances, the other clients reside on different mobile devices and the threshold can be determined by a proxy server (e.g., proxy server 325 of the host 300 shown in the example of
FIG. 5A-B) which is external to the mobile device and able to communicate over a wireless network with the multiple different mobile devices, as will be further described with reference to FIG. 5B.
- In some embodiments, the cache policy manager 245 sends the polling schedule to the proxy server (e.g., proxy server 125 or 325 shown in the examples of
FIG. 1B-1Cand FIG. 5A) and can be used by the proxy server in monitoring the content source, for example, for changed or new content (updated response different from the cached response associated with a request or application). A polling schedule sent to the proxy can include multiple timing parameters including but not limited to interval (time from request 1 to request 2) or a time out interval (time to wait for response, used in long polls, for example). Referring to the timing diagram of a request/response timing sequence timing intervals ‘RI’, ‘D’, ‘RT’, and/or ‘IT’, or some statistical manipulation of the above values (e.g., average, standard deviation, etc.) may all or in part be sent to the proxy server.
- For example, in the case when the local proxy 275 detects a long poll, the various timing intervals in a request/response timing sequence (e.g., ‘D’, ‘RT’, and/or ‘IT’) can be sent to the proxy server 325 for use in polling the content source (e.g., application server/content host 110). The local proxy 275 can also identify to the proxy server 325 that a given application or request to be monitored is a long poll request (e.g., instructing the proxy server to set a ‘long poll flag’, for example). In addition, the proxy server uses the various timing intervals to determine when to send keep-alive indications on behalf of mobile devices.
- The local cache invalidator 244 of the caching policy manager 245 can invalidate cache elements in the local cache (e.g., cache 185 or 285) when new or changed data (e.g., updated response) is detected from the application server/content source for a given request. The cached response can be determined to be invalid for the outgoing request based on a notification received from the proxy server (e.g., proxy 325 or the host server 300). The source which provides responses to requests of the mobile client can be monitored to determine relevancy of the cached response stored in the cache of the mobile device 250 for the request. For example, the cache invalidator 244 can further remove/delete the cached response from the cache of the mobile device when the cached response is no longer valid for a given request or a given application.
- In some embodiments, the cached response is removed from the cache after it is provided once again to an application which generated the outgoing request after determining that the cached response is no longer valid. The cached response can be provided again without waiting for the time interval or provided again after waiting for a time interval (e.g., the time interval determined to be specific to emulate the response delay in a long poll). In some embodiments, the time interval is the response delay ‘D’ or an average value of the response delay ‘D’ over two or more values.
- The new or changed data can be, for example, detected by the proxy server (e.g., proxy server 125 or 325 shown in the examples of
FIG. 1B-1C, FIG. 3A-3B, and FIG. 5A-5C). When a cache entry for a given request/poll has been invalidated, the use of the radio on the mobile device 250 can be enabled (e.g., by the local proxy 275 or the cache policy manager 245) to satisfy the subsequent polling requests.
- Some embodiments of the cache policy manager 245 include a cache or connect selection engine 249 which can decide whether to use a locally cached entry to satisfy a poll/content request generated at the mobile device 250 by an application or widget. For example, the local proxy 275 or the cache policy manger 245 can intercept a polling request, made by an application (e.g., mobile application) on the mobile device, to contact the application server/content provider. The selection engine 249 can determine whether the content received for the intercepted request has been locally stored as cache elements for deciding whether the radio of the mobile device needs to be activated to satisfy the request made by the application (e.g., mobile application) and also determine whether the cached response is still valid for the outgoing request prior to responding to the outgoing request using the cached response.
- In some embodiments, the local proxy 275, in response to determining that relevant cached content exists and is still valid, can retrieve the cached elements from the local cache to provide a response to the application (e.g., mobile application) which made the polling request such that a radio of the mobile device is not activated to provide the response to the application (e.g., mobile application). In general, the local proxy 275 continues to provide the cached response each time the outgoing request is received until the updated response different from the cached response is detected.
- When it is determined that the cached response is no longer valid, a new request for a given request is transmitted over the wireless network for an updated response. The request can be transmitted to the application server/content provider (e.g., server/host 110) or the proxy server on the host server (e.g., proxy 325 on the host 300) for a new and updated response. In some embodiments the cached response can be provided again as a response to the outgoing request if a new response is not received within the time interval, prior to removal of the cached response from the cache on the mobile device.
FIG. 4Cdepicts a block diagram illustrating examples of additional components in the local proxy 275 shown in the example of FIG. 4Awhich is further capable of performing mobile traffic categorization and policy implementation based on application behavior and/or user activity.
- In this embodiment of the local proxy 275, the user activity module 215 further includes one or more of, a user activity tracker 215 a, a user activity prediction engine 215 b, and/or a user expectation manager 215 c. The application behavior detect 236 can further include a prioritization engine 241 a, a time criticality detection engine 241 b, an application state categorizer 241 c, and/or an application traffic categorizer 241 d. The local proxy 275 can further include a backlight detector 219 and/or a network configuration selection engine 251. The network configuration selection engine 251 can further include, one or more of, a wireless generation standard selector 251 a, a data rate specifier 251 b, an access channel selection engine 251 c, and/or an access point selector.
- In some embodiments, the application behavior detector 236 is able to detect, determined, identify, or infer, the activity state of an application on the mobile device 250 to which traffic has originated from or is directed to, for example, via the application state categorizer 241 c and/or the traffic categorizer 241 d. The activity state can be determined by whether the application is in a foreground or background state on the mobile device (via the application state categorizer 241 c) since the traffic for a foreground application vs. a background application may be handled differently.
- In some embodiments, the activity state can be determined, detected, identified, or inferred with a level of certainty of heuristics, based on the backlight status of the mobile device 250 (e.g., by the backlight detector 219) or other software agents or hardware sensors on the mobile device, including but not limited to, resistive sensors, capacitive sensors, ambient light sensors, motion sensors, touch sensors, etc. In general, if the backlight is on, the traffic can be treated as being or determined to be generated from an application that is active or in the foreground, or the traffic is interactive. In addition, if the backlight is on, the traffic can be treated as being or determined to be traffic from user interaction or user activity, or traffic containing data that the user is expecting within some time frame.
- In some embodiments, the activity state is determined based on whether the traffic is interactive traffic or maintenance traffic. Interactive traffic can include transactions from responses and requests generated directly from user activity/interaction with an application and can include content or data that a user is waiting or expecting to receive. Maintenance traffic may be used to support the functionality of an application which is not directly detected by a user. Maintenance traffic can also include actions or transactions that may take place in response to a user action, but the user is not actively waiting for or expecting a response.
- For example, a mail or message delete action at a mobile device 250 generates a request to delete the corresponding mail or message at the server, but the user typically is not waiting for a response. Thus, such a request may be categorized as maintenance traffic, or traffic having a lower priority (e.g., by the prioritization engine 241 a) and/or is not time-critical (e.g., by the time criticality detection engine 214 b).
- Contrastingly, a mail ‘read’ or message ‘read’ request initiated by a user a the mobile device 250, can be categorized as ‘interactive traffic’ since the user generally is waiting to access content or data when they request to read a message or mail. Similarly, such a request can be categorized as having higher priority (e.g., by the prioritization engine 241 a) and/or as being time critical/time sensitive (e.g., by the time criticality detection engine 241 b).
- The time criticality detection engine 241 b can generally determine, identify, infer the time sensitivity of data contained in traffic sent from the mobile device 250 or to the mobile device from a host server (e.g., host 300) or application server (e.g., app server/content source 110). For example, time sensitive data can include, status updates, stock information updates, IM presence information, email messages or other messages, actions generated from mobile gaming applications, webpage requests, location updates, etc. Data that is not time sensitive or time critical, by nature of the content or request, can include requests to delete messages, mark-as-read or edited actions, application-specific actions such as an add-friend or delete-friend request, certain types of messages, or other information which does not frequently changing by nature, etc. In some instances when the data is not time critical, the timing with which to allow the traffic to pass through is set based on when additional data needs to be sent from the mobile device 250. For example, traffic shaping engine 255 can align the traffic with one or more subsequent transactions to be sent together in a single power-on event of the mobile device radio (e.g., using the alignment module 256 and/or the batching module 257). The alignment module 256 can also align polling requests occurring close in time directed to the same host server, since these request are likely to be responded to with the same data.
- In the alternate or in combination, the activity state can be determined from assessing, determining, evaluating, inferring, identifying user activity at the mobile device 250 (e.g., via the user activity module 215). For example, user activity can be directly detected and tracked using the user activity tracker 215 a. The traffic resulting therefrom can then be categorized appropriately for subsequent processing to determine the policy for handling. Furthermore, user activity can be predicted or anticipated by the user activity prediction engine 215 b. By predicting user activity or anticipating user activity, the traffic thus occurring after the prediction can be treated as resulting from user activity and categorized appropriately to determine the transmission policy.
- In addition, the user activity module 215 can also manage user expectations (e.g., via the user expectation manager 215 c and/or in conjunction with the activity tracker 215 and/or the prediction engine 215 b) to ensure that traffic is categorized appropriately such that user expectations are generally met. For example, a user-initiated action should be analyzed (e.g., by the expectation manager 215) to determine or infer whether the user would be waiting for a response. If so, such traffic should be handled under a policy such that the user does not experience an unpleasant delay in receiving such a response or action.
- In some embodiments, an advanced generation wireless standard network is selected for use in sending traffic between a mobile device and a host server in the wireless network based on the activity state of the application on the mobile device for which traffic is originated from or directed to. An advanced technology standards such as the 3G, 3.5G, 3G+, 4G, or LTE network can be selected for handling traffic generated as a result of user interaction, user activity, or traffic containing data that the user is expecting or waiting for. Advanced generation wireless standard network can also be selected for to transmit data contained in traffic directed to the mobile device which responds to foreground activities.
- In categorizing traffic and defining a transmission policy for mobile traffic, a network configuration can be selected for use (e.g., by the network configuration selection engine 251) on the mobile device 250 in sending traffic between the mobile device and a proxy server (325) and/or an application server (e.g., app server/host 110). The network configuration that is selected can be determined based on information gathered by the application behavior module 236 regarding application activity state (e.g., background or foreground traffic), application traffic category (e.g., interactive or maintenance traffic), any priorities of the data/content, time sensitivity/criticality.
- The network configuration selection engine 2510 can select or specify one or more of, a generation standard (e.g., via wireless generation standard selector 251 a), a data rate (e.g., via data rate specifier 251 b), an access channel (e.g., access channel selection engine 251 c), and/or an access point (e.g., via the access point selector 251 d), in any combination.
- For example, a more advanced generation (e.g., 3G, LTE, or 4G or later) can be selected or specified for traffic when the activity state is in interaction with a user or in a foreground on the mobile device. Contrastingly, an older generation standard (e.g., 2G, 2.5G, or 3G or older) can be specified for traffic when one or more of the following is detected, the application is not interacting with the user, the application is running in the background on the mobile device, or the data contained in the traffic is not time critical, or is otherwise determined to have lower priority.
- Similarly, a network configuration with a slower data rate can be specified for traffic when one or more of the following is detected, the application is not interacting with the user, the application is running in the background on the mobile device, or the data contained in the traffic is not time critical. The access channel (e.g., Forward access channel or dedicated channel) can be specified.
FIG. 5Adepicts 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 server-side proxy (or proxy server 325) can further categorize mobile traffic and/or implement delivery policies based on application behavior, content priority, user activity, and/or user expectations.
- The host server 300 generally includes, for example, a network interface 308 and/or one or more repositories 312, 314, and 316. Note that server 300 may be any portable/mobile or non-portable device, server, cluster of computers and/or other types of processing units (e.g., any number of a machine shown in the example of
FIG. 1B) able to receive or transmit signals to satisfy data requests over a network including any wired or wireless networks (e.g., WiFi, cellular, Bluetooth, etc.).
- The network interface 308 can include networking module(s) or devices(s) that enable the server 300 to mediate data in a network with an entity that is external to the host server 300, through any known and/or convenient communications protocol supported by the host and the external entity. Specifically, the network interface 308 allows the server 300 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 the repository 312. The host server 300 can store information about devices (e.g., hardware capability, properties, device settings, device language, network capability, manufacturer, device model, OS, OS version, etc.) in the device information repository 314. Additionally, the host server 300 can store information about network providers and the various network service areas in the network service provider repository 316.
- The communication enabled by network interface 308 allows for simultaneous connections (e.g., including cellular connections) with devices 350 and/or connections (e.g., including wired/wireless, HTTP, Internet connections, LAN, WiFi, etc.) with content servers/providers 310 to manage the traffic between devices 350 and content providers 310, for optimizing network resource utilization and/or to conserver power (battery) consumption on the serviced devices 350. The host server 300 can communicate with mobile devices 350 serviced by different network service providers and/or in the same/different network service areas. The host server 300 can operate and is compatible with devices 350 with varying types or levels of mobile capabilities, including by way of example but not limitation, 1G, 2G, 2G transitional (2.5G, 2.75G), 3G (IMT-2000), 3G transitional (3.5G, 3.75G, 3.9G), 4G (IMT-advanced), etc.
- In general, the network interface 308 can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G type networks such as LTE, WiMAX, etc.), Bluetooth, WiFi, or any other network whether or not connected via a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, a bridge router, a hub, a digital media receiver, and/or a repeater.
- The host server 300 can further include server-side components of the distributed proxy and cache system which can include a proxy server 325 and a server cache 335. In some embodiments, the proxy server 325 can include an HTTP access engine 345, a caching policy manager 355, a proxy controller 365, a traffic shaping engine 375, a new data detector 347 and/or a connection manager 395.
- The HTTP access engine 345 may further include a heartbeat manager 398; the proxy controller 365 may further include a data invalidator module 368; the traffic shaping engine 375 may further include a control protocol 376 and a batching module 377. Additional or less components/modules/engines can be included in the proxy server 325 and each illustrated component.
- As used herein, a “module,” a “manager,” a “handler,” a “detector,” an “interface,” a “controller,” a “normalizer,” a “generator,” an “invalidator,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module, manager, handler, detector, interface, controller, normalizer, generator, invalidator, or engine can be centralized or its functionality distributed. The module, manager, handler, detector, interface, controller, normalizer, generator, invalidator, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor. As used herein, a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid. Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.
- In the example of a device (e.g., mobile device 350) making an application or content request to an application server or content provider 310, the request may be intercepted and routed to the proxy server 325 which is coupled to the device 350 and the application server/content provider 310. Specifically, the proxy server is able to communicate with the local proxy (e.g., proxy 175 and 275 of the examples of
FIG. 1Cand FIG. 4Arespectively) of the mobile device 350, the local proxy forwards the data request to the proxy server 325 in some instances for further processing and, if needed, for transmission to the application server/content server 310 for a response to the data request.
- In such a configuration, the host 300, or the proxy server 325 in the host server 300 can utilize intelligent information provided by the local proxy in adjusting its communication with the device in such a manner that optimizes use of network and device resources. For example, the proxy server 325 can identify characteristics of user activity on the device 350 to modify its communication frequency. The characteristics of user activity can be determined by, for example, the activity/behavior awareness module 366 in the proxy controller 365 via information collected by the local proxy on the device 350.
- In some embodiments, communication frequency can be controlled by the connection manager 395 of the proxy server 325, for example, to adjust push frequency of content or updates to the device 350. For instance, push frequency can be decreased by the connection manager 395 when characteristics of the user activity indicate that the user is inactive. In some embodiments, when the characteristics of the user activity indicate that the user is subsequently active after a period of inactivity, the connection manager 395 can adjust the communication frequency with the device 350 to send data that was buffered as a result of decreased communication frequency to the device 350.
- In addition, the proxy server 325 includes priority awareness of various requests, transactions, sessions, applications, and/or specific events. Such awareness can be determined by the local proxy on the device 350 and provided to the proxy server 325. The priority awareness module 367 of the proxy server 325 can generally assess the priority (e.g., including time-criticality, time-sensitivity, etc.) of various events or applications; additionally, the priority awareness module 367 can track priorities determined by local proxies of devices 350.
- In some embodiments, through priority awareness, the connection manager 395 can further modify communication frequency (e.g., use or radio as controlled by the radio controller 396) of the server 300 with the devices 350. For example, the server 300 can notify the device 350, thus requesting use of the radio if it is not already in use when data or updates of an importance/priority level which meets a criteria becomes available to be sent.
- In some embodiments, 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 367 and/or 366. 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 some embodiments, the proxy server 325 can order the each messages/packets in a batch for transmission based on event/transaction priority such that higher priority content can be sent first in case connection is lost or the battery dies, etc.
- In some embodiments, 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. 5Ait 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. 1C), such as being managed by an application server/content provider 310, a network service provider, or another third party.
- In some embodiments, content caching is performed locally on the device 350 with the assistance of host server 300. For example, proxy server 325 in the host server 300 can query the application server/provider 310 with requests and monitor changes in responses. When changed or new responses are detected (e.g., by the new data detector 347), the proxy server 325 can notify the mobile device 350 such that the local proxy on the device 350 can make the decision to invalidate (e.g., indicated as out-dated) the relevant cache entries stored as any responses in its local cache. Alternatively, the data invalidator module 368 can automatically instruct the local proxy of the device 350 to invalidate certain cached data, based on received responses from the application server/provider 310. The cached data is marked as invalid, and can get replaced or deleted when new content is received from the content server 310.
- Note that data change can be detected by the detector 347 in one or more ways. For example, the server/provider 310 can notify the host server 300 upon a change. The change can also be detected at the host server 300 in response to a direct poll of the source server/provider 310. In some instances, the proxy server 325 can in addition, pre-load the local cache on the device 350 with the new/updated data. This can be performed when the host server 300 detects that the radio on the mobile device is already in use, or when the server 300 has additional content/data to be sent to the device 350.
- One or more the above mechanisms can be implemented simultaneously or adjusted/configured based on application (e.g., different policies for different servers/providers 310). In some instances, the source provider/server 310 may notify the host 300 for certain types of events (e.g., events meeting a priority threshold level). In addition, the provider/server 310 may be configured to notify the host 300 at specific time intervals, regardless of event priority.
- In some embodiments, the proxy server 325 of the host 300 can monitor/track responses received for the data request from the content source for changed results prior to returning the result to the mobile device, such monitoring may be suitable when data request to the content source has yielded same results to be returned to the mobile device, thus preventing network/power consumption from being used when no new changes are made to a particular requested. The local proxy of the device 350 can instruct the proxy server 325 to perform such monitoring or the proxy server 325 can automatically initiate such a process upon receiving a certain number of the same responses (e.g., or a number of the same responses in a period of time) for a particular request.
- In some embodiments, the server 300, through the activity/behavior awareness module 366, is able to identify or detect user activity at a device that is separate from the mobile device 350. For example, the module 366 may detect that a user's message inbox (e.g., email or types of inbox) is being accessed. This can indicate that the user is interacting with his/her application using a device other than the mobile device 350 and may not need frequent updates, if at all.
- The server 300, in this instance, can thus decrease the frequency with which new or updated content is sent to the mobile device 350, or eliminate all communication for as long as the user is detected to be using another device for access. Such frequency decrease may be application specific (e.g., for the application with which the user is interacting with on another device), or it may be a general frequency decrease (E.g., since the user is detected to be interacting with one server or one application via another device, he/she could also use it to access other services.) to the mobile device 350.
- In some embodiments, the host server 300 is able to poll content sources 310 on behalf of devices 350 to conserve power or battery consumption on devices 350. For example, certain applications on the mobile device 350 can poll its respective server 310 in a predictable recurring fashion. Such recurrence or other types of application behaviors can be tracked by the activity/behavior module 366 in the proxy controller 365. The host server 300 can thus poll content sources 310 for applications on the mobile device 350 that would otherwise be performed by the device 350 through a wireless (e.g., including cellular connectivity). The host server can poll the sources 310 for new or changed data by way of the HTTP access engine 345 to establish HTTP connection or by way of radio controller 396 to connect to the source 310 over the cellular network. When new or changed data is detected, the new data detector 347 can notify the device 350 that such data is available and/or provide the new/changed data to the device 350.
- In some embodiments, 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. 1C. SMS is used to transmit invalidation messages, batches of invalidation messages, or even content in the case where the content is small enough to fit into just a few (usually one or two) SMS messages. This avoids the need to access the radio channel to send overhead information. The host server 300 can use SMS for certain transactions or responses having a priority level above a threshold or otherwise meeting a criteria. The server 300 can also utilize SMS as an out-of-band trigger to maintain or wake-up an IP connection as an alternative to maintaining an always-on IP connection.
- In some embodiments, the connection manager 395 in the proxy server 325 (e.g., the heartbeat manager 398) can generate and/or transmit heartbeat messages on behalf of connected devices 350 to maintain a backend connection with a provider 310 for applications running on devices 350.
- For example, in the distributed proxy system, local cache on the device 350 can prevent any or all heartbeat messages needed to maintain TCP/IP connections required for applications from being sent over the cellular, or other, network and instead rely on the proxy server 325 on the host server 300 to generate and/or send the heartbeat messages to maintain a connection with the backend (e.g., application server/provider 110 in the example of
FIG. 1A). The proxy server can generate the keep-alive (heartbeat) messages independent of the operations of the local proxy on the mobile device.
- The repositories 312, 314, and/or 316 can additionally store software, descriptive data, images, system information, drivers, and/or any other data item utilized by other components of the host server 300 and/or any other servers for operation. The repositories may be managed by a database management system (DBMS), for example, which may be but is not limited to Oracle, DB2, Microsoft Access, Microsoft SQL Server, PostgreSQL, MySQL, FileMaker, etc.
- The repositories can be implemented via object-oriented technology and/or via text files and can be managed by a distributed database management system, an object-oriented database management system (OODBMS) (e.g., ConceptBase, FastDB Main Memory Database Management System, JDOlnstruments, ObjectDB, etc.), an object-relational database management system (ORDBMS) (e.g., Informix, OpenLink Virtuoso, VMDS, etc.), a file system, and/or any other convenient or known database management package.
FIG. 5Bdepicts a block diagram illustrating a further example of components in the caching policy manager 355 in the cache system shown in the example of FIG. 5Awhich is capable of caching and adapting caching strategies for application (e.g., mobile application) behavior and/or network conditions.
- The caching policy manager 355, In some embodiments, can further include a metadata generator 303, a cache look-up engine 305, an application protocol module 356, a content source monitoring engine 357 having a poll schedule manager 358, a response analyzer 361, and/or an updated or new content detector 359. In some embodiments, the poll schedule manager 358 further includes a host timing simulator 358 a, a long poll request detector/manager 358 b, a schedule update engine 358 c, and/or a time adjustment engine 358 d. The metadata generator 303 and/or the cache look-up engine 305 can be coupled to the cache 335 (or, server cache) for modification or addition to cache entries or querying thereof.
- In some embodiments, the proxy server (e.g., the proxy server 125 or 325 of the examples of
FIG. 1B-1Cand FIG. 5A) can monitor a content source for new or changed data via the monitoring engine 357. The proxy server, as shown, is an entity external to the mobile device 250 of FIG. 4A-4B. The content source (e.g., application server/content provider 110 of FIG. 1B-1C) can be one that has been identified to the proxy server (e.g., by the local proxy) as having content that is being locally cached on a mobile device (e.g., mobile device 150 or 250). The content source can be monitored, for example, by the monitoring engine 357 at a frequency that is based on polling frequency of the content source at the mobile device. The poll schedule can be generated, for example, by the local proxy and sent to the proxy server. The poll frequency can be tracked and/or managed by the poll schedule manager 358.
- For example, the proxy server can poll the host (e.g., content provider/application server) on behalf of the mobile device and simulate the polling behavior of the client to the host via the host timing simulator 358 a. The polling behavior can be simulated to include characteristics of a long poll request-response sequences experienced in a persistent connection with the host (e.g., by the long poll request detector/manager 358 b). Note that once a polling interval/behavior is set, the local proxy 275 on the device-side and/or the proxy server 325 on the server-side can verify whether application and application server/content host behavior match or can be represented by this predicted pattern. In general, the local proxy and/or the proxy server can detect deviations and, when appropriate, re-evaluate and compute, determine, or estimate another polling interval.
- In some embodiments, the caching policy manager 355 on the server-side of the distribute proxy can, in conjunction with or independent of the proxy server 275 on the mobile device, identify or detect long poll requests. For example, the caching policy manager 355 can determine a threshold value to be used in comparison with a response delay interval time in a request-response sequence for an application request to identify or detect long poll requests, possible long poll requests (e.g., requests for a persistent connection with a host with which the client communicates including, but not limited to, a long-held HTTP request, a persistent connection enabling COMET style push, request for HTTP streaming, etc.), or other requests which can otherwise be treated as a long poll request.
- For example, the threshold value can be determined by the proxy 325 using response delay interval times for requests generated by clients/applications across mobile devices which may be serviced by multiple different cellular or wireless networks. Since the proxy 325 resides on host 300 is able to communicate with multiple mobile devices via multiple networks, the caching policy manager 355 has access to application/client information at a global level which can be used in setting threshold values to categorize and detect long polls.
- By tracking response delay interval times across applications across devices over different or same networks, the caching policy manager 355 can set one or more threshold values to be used in comparison with response delay interval times for long poll detection. Threshold values set by the proxy server 325 can be static or dynamic, and can be associated with conditions and/or a time-to-live (an expiration time/date in relative or absolute terms).
- In addition, the caching policy manager 355 of the proxy 325 can further determine the threshold value, in whole or in part, based on network delays of a given wireless network, networks serviced by a given carrier (service provider), or multiple wireless networks. The proxy 325 can also determine the threshold value for identification of long poll requests based on delays of one or more application server/content provider (e.g., 110) to which application (e.g., mobile application) or mobile client requests are directed.
- The proxy server can detect new or changed data at a monitored content source and transmits a message to the mobile device notifying it of such a change such that the mobile device (or the local proxy on the mobile device) can take appropriate action (e.g., to invalidate the cache elements in the local cache). In some instances, the proxy server (e.g., the caching policy manager 355) upon detecting new or changed data can also store the new or changed data in its cache (e.g., the server cache 135 or 335 of the examples of
FIG. 1Cand FIG. 5A, respectively). The new/updated data stored in the server cache 335 can be used in some instances to satisfy content requests at the mobile device; for example, it can be used after the proxy server has notified the mobile device of the new/changed content and that the locally cached content has been invalidated.
- The metadata generator 303, similar to the metadata generator 203 shown in the example of
FIG. 4B, can generate metadata for responses cached for requests at the mobile device 250. The metadata generator 303 can generate metadata for cache entries stored in the server cache 335. Similarly, the cache look-up engine 305 can include the same or similar functions are those described for the cache look-up engine 205 shown in the example of FIG. 4B.
- The response analyzer 361 can perform any or all of the functionalities related to analyzing responses received for requests generated at the mobile device 250 in the same or similar fashion to the response analyzer 246 d of the local proxy shown in the example of
FIG. 4B. Since the proxy server 325 is able to receive responses from the application server/content source 310 directed to the mobile device 250, the proxy server 325 (e.g., the response analyzer 361) can perform similar response analysis steps to determine cacheability, as described for the response analyzer of the local proxy. The responses can be analyzed in addition to or in lieu of the analysis that can be performed at the local proxy 275 on the mobile device 250.
- Furthermore, the schedule update engine 358 c can update the polling interval of a given application server/content host based on application request interval changes of the application at the mobile device 250 as described for the schedule update engine in the local proxy 275. The time adjustment engine 358 d can set an initial time at which polls of the application server/content host is to begin to prevent the serving of out of date content once again before serving fresh content as described for the schedule update engine in the local proxy 275. Both the schedule updating and the time adjustment algorithms can be performed in conjunction with or in lieu of the similar processes performed at the local proxy 275 on the mobile device 250.
FIG. 5Cdepicts a block diagram illustrating examples of additional components in proxy server 325 shown in the example of FIG. 5Awhich is further capable of performing mobile traffic categorization and policy implementation based on application behavior and/or traffic priority.
- In some embodiments of the proxy server 325, the traffic shaping engine 375 is further coupled to a traffic analyzer 336 for categorizing mobile traffic for policy definition and implementation for mobile traffic and transactions directed to one or more mobile devices (e.g., mobile device 250 of
FIG. 4A-4C) or to an application server/content host (e.g., 110 of FIG. 1B-1C). In general, the proxy server 325 is remote from the mobile devices and remote from the host server, as shown in the examples of FIG. 1B-1C. The proxy server 325 or the host server 300 can monitor the traffic for multiple mobile devices and is capable of categorizing traffic and devising traffic policies for different mobile devices.
- In addition, the proxy server 325 or host server 300 can operate with multiple carriers or network operators and can implement carrier-specific policies relating to categorization of traffic and implementation of traffic policies for the various categories. For example, the traffic analyzer 336 of the proxy server 325 or host server 300 can include one or more of, a prioritization engine 341 a, a time criticality detection engine 341 b, an application state categorizer 341 c, and/or an application traffic categorizer 341 d.
- Each of these engines or modules can track different criterion for what is considered priority, time critical, background/foreground, or interactive/maintenance based on different wireless carriers. Different criterion may also exist for different mobile device types (e.g., device model, manufacturer, operating system, etc.). In some instances, the user of the mobile devices can adjust the settings or criterion regarding traffic category and the proxy server 325 is able to track and implement these user adjusted/configured settings.
- In some embodiments, the traffic analyzer 336 is able to detect, determined, identify, or infer, the activity state of an application on one or more mobile devices (e.g., mobile device 150 or 250) which traffic has originated from or is directed to, for example, via the application state categorizer 341 c and/or the traffic categorizer 341 d. The activity state can be determined based on whether the application is in a foreground or background state on one or more of the mobile devices (via the application state categorizer 341 c) since the traffic for a foreground application vs. a background application may be handled differently to optimize network use.
- In the alternate or in combination, the activity state of an application can be determined by the wirelessly connected mobile devices (e.g., via the application behavior detectors in the local proxies) and communicated to the proxy server 325. For example, the activity state can be determined, detected, identified, or inferred with a level of certainty of heuristics, based on the backlight status at mobile devices (e.g., by a backlight detector) or other software agents or hardware sensors on the mobile device, including but not limited to, resistive sensors, capacitive sensors, ambient light sensors, motion sensors, touch sensors, etc. In general, if the backlight is on, the traffic can be treated as being or determined to be generated from an application that is active or in the foreground, or the traffic is interactive. In addition, if the backlight is on, the traffic can be treated as being or determined to be traffic from user interaction or user activity, or traffic containing data that the user is expecting within some time frame.
- The activity state can be determined from assessing, determining, evaluating, inferring, identifying user activity at the mobile device 250 (e.g., via the user activity module 215) and communicated to the proxy server 325. In some embodiments, the activity state is determined based on whether the traffic is interactive traffic or maintenance traffic. Interactive traffic can include transactions from responses and requests generated directly from user activity/interaction with an application and can include content or data that a user is waiting or expecting to receive. Maintenance traffic may be used to support the functionality of an application which is not directly detected by a user. Maintenance traffic can also include actions or transactions that may take place in response to a user action, but the user is not actively waiting for or expecting a response.
- The time criticality detection engine 341 b can generally determine, identify, infer the time sensitivity of data contained in traffic sent from the mobile device 250 or to the mobile device from the host server 300 or proxy server 325, or the application server (e.g., app server/content source 110). For example, time sensitive data can include, status updates, stock information updates, IM presence information, email messages or other messages, actions generated from mobile gaming applications, webpage requests, location updates, etc.
- Data that is not time sensitive or time critical, by nature of the content or request, can include requests to delete messages, mark-as-read or edited actions, application-specific actions such as an add-friend or delete-friend request, certain types of messages, or other information which does not frequently changing by nature, etc. In some instances when the data is not time critical, the timing with which to allow the traffic to be sent to a mobile device is based on when there is additional data that needs to the sent to the same mobile device. For example, traffic shaping engine 375 can align the traffic with one or more subsequent transactions to be sent together in a single power-on event of the mobile device radio (e.g., using the alignment module 378 and/or the batching module 377). The alignment module 378 can also align polling requests occurring close in time directed to the same host server, since these request are likely to be responded to with the same data.
- In general, whether new or changed data is sent from a host server to a mobile device can be determined based on whether an application on the mobile device to which the new or changed data is relevant, is running in a foreground (e.g., by the application state categorizer 341 c), or the priority or time criticality of the new or changed data. The proxy server 325 can send the new or changed data to the mobile device if the application is in the foreground on the mobile device, or if the application is in the foreground and in an active state interacting with a user on the mobile device, and/or whether a user is waiting for a response that would be provided in the new or changed data. The proxy server 325 (or traffic shaping engine 375) can send the new or changed data that is of a high priority or is time critical.
- Similarly, the proxy server 325 (or the traffic shaping engine 375) can suppressing the sending of the new or changed data if the application is in the background on the mobile device. The proxy server 325 can also suppress the sending of the new or changed data if the user is not waiting for the response provided in the new or changed data; wherein the suppressing is performed by a proxy server coupled to the host server and able to wirelessly connect to the mobile device.
- In general, if data, including new or change data is of a low priority or is not time critical, the proxy server can waiting to transfer the data until after a time period, or until there is additional data to be sent (e.g. via the alignment module 378 and/or the batching module 377).
FIG. 6is a flow diagram depicting steps in a process 2000 for assessing background data and performing a radio status transition as implemented in some embodiments. At step 2001, the system can monitor criteria associated with a mobile device, e.g., using a local proxy. As discussed above, the criteria may include a capacity of a buffer, the state of a backlight on the device, a FACH consumption rate, user activity at the device, user preferences, or other criteria indicative of the mobile device's status. In some embodiments, the buffer may not be monitored directly, but may instead be modeled to avoid the need for heavy computations. Certain of the criteria may be combined into a “group” of criteria. For example, the system may determine that data transmitted/received is background data based on the buffer exceeding a threshold when the backlight is off.
- In some embodiments, the monitored criteria may not be a size of the data sent, but rather the speed with which the data is sent. For example, data sent or received at a rate exceeding a threshold during an inactive state of the mobile device, may be indicative of background data. In some embodiments, the system may apply dynamic adaptive logic to discover network specific or condition specific values associated with the criteria. In some embodiments, the system may detect background data transmissions by monitoring the draw on a battery at the mobile device.
- At step 2002 the system may determine whether to perform a radio status transition based at least in part on the criteria. As discussed above, in some embodiments, the radio status transition may be performed by communicating rules to a PCRF component in a network. A local proxy on the mobile device may determine a plurality of rules, e.g., rules used at a PCRF, based on the monitoring and may communicate the rules to a network component so as to adjust a level of throttling. In one implementation, the PCRF may request the network component to change the radio status.
FIG. 7is a flow diagram generally depicting a process 2100 for assessing background data and performing a radio status transition accordingly as implemented in certain embodiments. At step 2101 the system may monitor an application on a mobile device. At step 2102 the system may determine whether data transmitted or received because of the monitored application meets power state transition criteria. In some embodiments, the power state transition criteria may be used to determine if the data transmitted or received is background data. If the data meets the criteria, at step 2103 the system may perform a radio status transition from a first state to a second state. For example, if the system may determine that the data is background data, and demote to the system a lower radio status state in a 3G or LTE network. In some embodiments, if the state does not meet the criteria, the system may take action to preserve the existing state. For example, the system may adjust rules at a PCRF component, so that the current state is not promoted or demoted based on the current configuration of the monitored criteria.
FIG. 8is a flow diagram generally depicting a process 2200 for assessing background data and performing a radio status transition accordingly as implemented in certain embodiments. At step 2201 the system may determine if an application intends to transmit or receive background data. If the system determines that the application may transmit or receive background data, at step 2202 the system may monitor the application. At step 2203 the system may determine if the criteria to transition the radio state have been met. At step 2204, the system may determine whether to perform a radio channel status transition based on the criteria and upon the application, such as upon the application's behavior. If the system determines that the transition is to occur, at step 2205, the system may perform the transition or cause the transition to be performed. For example, the system may modify or provide rules to a PCRF network component, such that the PCRF will cause the transition at the appropriate time. Note that in some embodiments, based upon the monitoring, the system may determine that rules which avoid a transition and maintain the current state are appropriate.
FIG. 9depicts a table 700 showing examples of different traffic or application category types which can be used in implementing network access and content delivery policies. For example, traffic/application categories can include interactive or background, whether a user is waiting for the response, foreground/background application, and whether the backlight is on or off.
FIG. 10depicts a table 800 showing examples of different content category types which can be used in implementing network access and content delivery policies. For example, content category types can include content of high or low priority, and time critical or non-time critical content/data.
FIG. 11shows a diagrammatic representation of a machine in the example form of a computer system within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.
- In the example of
FIG. 11, the computer system 1100 includes a processor, memory, non-volatile memory, and an interface device. Various common components (e.g., cache memory) are omitted for illustrative simplicity. The computer system 1100 is intended to illustrate a hardware device on which any of the components depicted in the example of FIGS. 2A-2B, 3A-3B, 4A-4D and 5A-C (and any other components described in this specification) can be implemented. The computer system 1100 can be of any applicable known or convenient type. The components of the computer system 1100 can be coupled together via a bus or through some other known or convenient device.
- The processor may be, for example, a conventional microprocessor such as an Intel Pentium microprocessor or Motorola power PC microprocessor. One of skill in the relevant art will recognize that the terms “machine-readable (storage) medium” or “computer-readable (storage) medium” include any type of device that is accessible by the processor.
- The memory is coupled to the processor by, for example, a bus. The memory can include, by way of example but not limitation, random access memory (RAM), such as dynamic RAM (DRAM) and static RAM (SRAM). The memory can be local, remote, or distributed.
- The bus also couples the processor to the non-volatile memory and drive unit. The non-volatile memory is often a magnetic floppy or hard disk, a magnetic-optical disk, an optical disk, a read-only memory (ROM), such as a CD-ROM, EPROM, or EEPROM, a magnetic or optical card, or another form of storage for large amounts of data. Some of this data is often written, by a direct memory access process, into memory during execution of software in the computer 1100. The non-volatile storage can be local, remote, or distributed. The non-volatile memory is optional because systems can be created with all applicable data available in memory. A typical computer system will usually include at least a processor, memory, and a device (e.g., a bus) coupling the memory to the processor.
- Software is typically stored in the non-volatile memory and/or the drive unit. Indeed, for large programs, it may not even be possible to store the entire program in the memory. Nevertheless, it should be understood that for software to run, if necessary, it is moved to a computer readable location appropriate for processing, and for illustrative purposes, that location is referred to as the memory in this paper. Even when software is moved to the memory for execution, the processor will typically make use of hardware registers to store values associated with the software, and local cache that, ideally, serves to speed up execution. As used herein, a software program is assumed to be stored at any known or convenient location (from non-volatile storage to hardware registers) when the software program is referred to as “implemented in a computer-readable medium.” A processor is considered to be “configured to execute a program” when at least one value associated with the program is stored in a register readable by the processor.
- The bus also couples the processor to the network interface device. The interface can include one or more of a modem or network interface. It will be appreciated that a modem or network interface can be considered to be part of the computer system. The interface can include an analog modem, isdn modem, cable modem, token ring interface, satellite transmission interface (e.g. “direct PC”), or other interfaces for coupling a computer system to other computer systems. The interface can include one or more input and/or output devices. The I/O devices can include, by way of example but not limitation, a keyboard, a mouse or other pointing device, disk drives, printers, a scanner, and other input and/or output devices, including a display device. The display device can include, by way of example but not limitation, a cathode ray tube (CRT), liquid crystal display (LCD), or some other applicable known or convenient display device. For simplicity, it is assumed that controllers of any devices not depicted in the example of
FIG. 8reside in the interface.
- In operation, the computer system 1100 can be controlled by operating system software that includes a file management system, such as a disk operating system. One example of operating system software with associated file management system software is the family of operating systems known as Windows® from Microsoft Corporation of Redmond, Wash., and their associated file management systems. Another example of operating system software with its associated file management system software is the Linux operating system and its associated file management system. The file management system is typically stored in the non-volatile memory and/or drive unit and causes the processor to execute the various acts required by the operating system to input and output data and to store data in the memory, including storing files on the non-volatile memory and/or drive unit.
- Some portions of the detailed description may be presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
- It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
- The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the methods of some embodiments. The required structure for a variety of these systems will appear from the description below. In addition, the techniques are not described with reference to any particular programming language, and various embodiments may thus be implemented using a variety of programming languages.
- In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.
- The machine may be a server computer, a client computer, a personal computer (PC), a user device, a tablet PC, a laptop computer, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, an iPhone, an iPad, a Blackberry, a processor, a telephone, a web appliance, a network router, switch or bridge, a console, a hand-held console, a (hand-held) gaming device, a music player, any portable, mobile, hand-held device, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.
- While the machine-readable medium or machine-readable storage medium is shown in an exemplary embodiment to be a single medium, the term “machine-readable medium” and “machine-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” and “machine-readable storage medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the presently disclosed technique and innovation.
- In general, the routines executed to implement the embodiments of the disclosure may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically comprise one or more instructions set at various times in various memory and storage devices in a computer that, when read and executed by one or more processing units or processors in a computer, cause the computer to perform operations to execute elements involving the various aspects of the disclosure.
- Moreover, while embodiments have been described in the context of fully functioning computers and computer systems, those skilled in the art will appreciate that the various embodiments are capable of being distributed as a program product in a variety of forms, and that the disclosure applies equally regardless of the particular type of machine or computer-readable media used to actually effect the distribution.
- Further examples of machine-readable storage media, machine-readable media, or computer-readable (storage) media include but are not limited to recordable type media such as volatile and non-volatile memory devices, floppy and other removable disks, hard disk drives, optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), among others, and transmission type media such as digital and analog communication links.
- Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof, means any connection or coupling, either direct or indirect, between two or more elements; the coupling of connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.
- The above detailed description of embodiments of the disclosure is not intended to be exhaustive or to limit the teachings to the precise form disclosed above. While specific embodiments of, and examples for, the disclosure are described above for illustrative purposes, various equivalent modifications are possible within the scope of the disclosure, as those skilled in the relevant art will recognize For example, while processes or blocks are presented in a given order, alternative embodiments may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or sub-combinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed in parallel, or may be performed at different times. Further any specific numbers noted herein are only examples: alternative implementations may employ differing values or ranges.
- The teachings of the disclosure provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various embodiments described above can be combined to provide further embodiments.
- Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the disclosure can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further embodiments of the disclosure.
- These and other changes can be made to the disclosure in light of the above Detailed Description. While the above description describes certain embodiments of the disclosure, and describes the best mode contemplated, no matter how detailed the above appears in text, the teachings can be practiced in many ways. Details of the system may vary considerably in its implementation details, while still being encompassed by the subject matter disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the disclosure should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the disclosure with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the disclosure to the specific embodiments disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the disclosure encompasses not only the disclosed embodiments, but also all equivalent ways of practicing or implementing the disclosure under the claims.
- While certain aspects of the disclosure are presented below in certain claim forms, the inventors contemplate the various aspects of the disclosure in any number of claim forms. For example, while only one aspect of the disclosure is recited as a means-plus-function claim under 35 U.S.C. §112, ¶6, other aspects may likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. (Any claims intended to be treated under 35 U.S.C. §112, ¶6 will begin with the words “means for.”) Accordingly, the applicant reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the disclosure.
1. A method for radio state management of a mobile device in a mobile network, the method, comprising:
monitoring a criteria associated with the mobile device; and
determining whether to perform a radio status transition of the mobile device in the mobile network from a first state to a second state based at least in part upon the criteria, the first state and the second state being distinguished from a higher powered state or a lower powered state.
2. The method of
claim 1, wherein the radio status transition includes one of a promotion or a demotion.
3. The method of
claim 1, wherein the criteria includes a capacity of a buffer, the buffer located on a mobile device.
4. The method of
claim 3, wherein monitoring the criteria comprises applying logic to discover network specific or condition specific values associated with the buffer capacity.
5. The method of
claim 4, wherein, the logic is adaptive to network conditions and is dynamically adjustable.
6. The method of
claim 1, wherein, the criteria includes a Forward Access Channel (FACH) consumption rate.
7. The method of
claim 1, wherein, the criteria includes a backlight status of the mobile device.
8. The method of
claim 1, wherein the criteria comprises one or more of behavior of applications running on the mobile device, user activity at the mobile device, and user preferences at the mobile device.
9. The method of
claim 1, wherein determining whether to perform a radio status transition comprises communicating rules to a Policy and Charging Rules Function (PCRF) component of a network component in a mobile network.
10. The method of
claim 1, wherein whether the criteria is met is determined by a local proxy on the mobile device.
11. The method of
claim 10, wherein the method further comprises:
determining, using the local proxy, rules based on monitoring the criteria and monitoring the one or more applications; and
communicating the rules to a network component in the mobile network, the rules configured to determine a level of throttling.
12. The method of
claim 1, wherein, the criteria is monitored by a proxy server remote from the mobile device.
13. The method of
claim 12, the method further comprising:
determining, using the proxy server, rules based on the monitoring a criteria and monitoring the one or more mobile applications on or accessed via the mobile device; and
communicating the rules to a network component in the mobile network, the rules configured to determine a level of throttling.
14. The method of
claim 1, further comprising, performing the radio status transition includes adjusting a level of throttling.
15. The method of
claim 1, wherein the mobile network is a 3G network and the first state comprises one of three states in the 3G network.
16. The method of
claim 1, wherein, the mobile network is a 4G/LTE network and first state is one of two states in the 4G/LTE network.
17. The method of
claim 1, further comprising communicating a plurality of rules to a network component, the plurality of rules configured to determine a level of throttling
35. A mobile device able to manage radio state change, the mobile device, comprising:
a radio to connect to a mobile network;
a local proxy configured to:
monitor a mobile application accessed on or via the mobile device to determine whether data transmission or data receipt caused by the application meets criteria to transition a power state of the radio; and
transition or maintain the power state of the radio based on the criteria and based on an amount of data in the data transmission or the amount of data in the data receipt.
36. The mobile device of
claim 35, wherein the criteria includes a capacity of a buffer located on the mobile device.
37. The mobile device of
claim 36, wherein monitoring the application comprises applying dynamic adaptive logic to discover network specific values associated with the buffer capacity.
38. The mobile device of
claim 36, wherein monitoring the application comprises applying dynamic adaptive logic to discover condition specific values associated with the buffer capacity.
39. The mobile device of
claim 35, wherein the criteria comprises one of a Forward Access Channel (FACH) consumption rate.
40. The mobile device of
claim 39, wherein the criteria comprises a buffer capacity during a background data transfer while the radio is kept in a FACH consumption rate.
41. The mobile device of
claim 35, wherein determining whether to perform a radio channel status transition comprises communicating rules to a PCRF component in a network.
42. The mobile device of
claim 35, wherein the local proxy is further configured to:
determine a plurality of rules based on monitoring a criteria and monitoring the one or more applications; and
communicate the rules to a network component, the rules configured to determine a level of throttling.
43. The mobile device of
claim 35, wherein preventing a radio status channel transition comprises adjusting a level of throttling.
44. The mobile device of
claim 35, wherein the power state comprises a state in a 3G network or a state in an LTE network.
80. A machine readable storage medium comprising instructions which when executed by a processor cause a computer system to perform a method comprising:
monitoring a criteria associated with a mobile device; and
determining whether to perform a radio status transition from a first state to a second state based at least in part upon the criteria.
81. The machine readable storage medium of
claim 80, wherein the radio status transition includes one of a promotion or a demotion.
82. The machine readable storage medium of
claim 80, wherein the criteria includes a capacity of a buffer, the buffer located on a mobile device.
83. The method of
claim 82, wherein monitoring the criteria comprises applying dynamic adaptive logic to discover network specific or condition specific values associated with the buffer capacity.
84. The machine readable storage medium of
claim 80, wherein the criteria comprises one of request characteristics, response characteristics, a FACH consumption rate, applications running on a mobile device, mobile device state, mobile device backlight status, user activity at a mobile device, user preferences at a mobile device.
85. The machine readable storage medium of
claim 80, wherein determining whether to perform a radio status transition comprises communicating rules to a PCRF component in a network.
86. The machine readable storage medium of
claim 80, wherein the criteria is monitored by a local proxy on the mobile device.
87. The machine readable storage medium of
claim 86, wherein the method further comprises:
determining, using the local proxy, a plurality of rules based on the monitoring a criteria and monitoring the one or more applications; and
communicating the rules to a network component, the rules configured to determine a level of throttling.
88. The machine readable storage medium of
claim 80, wherein, the criteria is monitored by a proxy server remote from the mobile device.
89. The machine readable storage medium of
claim 88, the method further comprising:
determining, using the proxy server, a plurality of rules based on the monitoring a criteria and monitoring the one or more applications; and
communicating the rules to a network component, the rules configured to determine a level of throttling.
90. The machine readable storage medium of
claim 80, wherein preventing a radio status transition comprises adjusting a level of throttling.
91. The machine readable storage medium of
claim 80, wherein the first state comprises a state in a 3G network or a state in an LTE network.
Priority Applications (2)
|Application Number||Priority Date||Filing Date||Title|
|US13/844,682 US20140177497A1 (en)||2012-12-20||2013-03-15||Management of mobile device radio state promotion and demotion|
Applications Claiming Priority (1)
|Application Number||Priority Date||Filing Date||Title|
|US13/844,682 US20140177497A1 (en)||2012-12-20||2013-03-15||Management of mobile device radio state promotion and demotion|
|Publication Number||Publication Date|
|US20140177497A1 true US20140177497A1 (en)||2014-06-26|
Family Applications (2)
|Application Number||Title||Priority Date||Filing Date|
|US13/844,675 Expired - Fee Related US9307493B2 (en)||2012-12-20||2013-03-15||Systems and methods for application management of mobile device radio state promotion and demotion|
|US13/844,682 Abandoned US20140177497A1 (en)||2012-12-20||2013-03-15||Management of mobile device radio state promotion and demotion|
Family Applications Before (1)
|Application Number||Title||Priority Date||Filing Date|
|US13/844,675 Expired - Fee Related US9307493B2 (en)||2012-12-20||2013-03-15||Systems and methods for application management of mobile device radio state promotion and demotion|
Country Status (1)
|US (2)||US9307493B2 (en)|
Cited By (16)
|Publication number||Priority date||Publication date||Assignee||Title|
|US20140195645A1 (en) *||2013-01-04||2014-07-10||Netflix, Inc.||Proxy application with dynamic filter updating|
|US20140229952A1 (en) *||2013-02-12||2014-08-14||Qualcomm Incorporated||Intelligent task manager using onboard sensors|
|US20140344289A1 (en) *||2013-05-20||2014-11-20||United Video Properties, Inc.||Energy-saving systems and methods for updating media information|
|US20140365599A1 (en) *||2013-06-11||2014-12-11||Samsung Electronics Co., Ltd.||Communication method of node overhearing content in content centric network and node|
|US20150160976A1 (en) *||2013-12-06||2015-06-11||Samsung Electronics Co., Ltd.||Multitasking method and electronic device therefor|
|US20170006130A1 (en) *||2013-12-20||2017-01-05||Intel Corporation||Crowd sourced online application cache management|
|WO2017035261A1 (en) *||2015-08-25||2017-03-02||Alibaba Group Holding Limited||Method and system for network access request control|
|WO2017160425A1 (en) *||2016-03-18||2017-09-21||T-Mobile Usa, Inc.||Preference-aware content streaming|
|US10187281B2 (en)||2015-04-30||2019-01-22||Alibaba Group Holding Limited||Method and system of monitoring a service object|
|US10193943B2 (en)||2015-11-09||2019-01-29||T-Mobile Usa, Inc.||Data-plan-based quality setting suggestions and use thereof to manage content provider services|
|US10305952B2 (en) *||2015-11-09||2019-05-28||T-Mobile Usa, Inc.||Preference-aware content streaming|
|US20190253445A1 (en) *||2018-02-09||2019-08-15||Extrahop Networks, Inc.||Detection of denial of service attacks|
|US10423450B2 (en)||2015-04-23||2019-09-24||Alibaba Group Holding Limited||Method and system for scheduling input/output resources of a virtual machine|
|US10728152B2 (en)||2016-02-08||2020-07-28||T-Mobile Usa, Inc.||Dynamic network rate control|
|US11055223B2 (en)||2015-07-17||2021-07-06||Alibaba Group Holding Limited||Efficient cache warm up based on user requests|
|US11068586B2 (en)||2015-05-06||2021-07-20||Alibaba Group Holding Limited||Virtual host isolation|
Families Citing this family (7)
|Publication number||Priority date||Publication date||Assignee||Title|
|US7356567B2 (en) *||2004-12-30||2008-04-08||Aol Llc, A Delaware Limited Liability Company||Managing instant messaging sessions on multiple devices|
|US9445452B2 (en) *||2014-12-05||2016-09-13||T-Mobile U.S.A. Inc.||Directed application control of user device radio|
|CN106227589B (en) *||2016-07-25||2019-11-26||维沃移动通信有限公司||A kind of application program scheduling method and mobile terminal|
|US10650621B1 (en)||2016-09-13||2020-05-12||Iocurrents, Inc.||Interfacing with a vehicular controller area network|
|CN106535231B (en) *||2016-12-08||2019-12-13||北京邮电大学||Content transmission method for 5G user-oriented central network Cache deployment|
|DE112017006689T5 (en) *||2016-12-30||2019-09-12||Intel Corporation||PROCESS AND DEVICES FOR RADIO COMMUNICATION|
|CN109151194B (en) *||2018-08-14||2021-03-02||Oppo广东移动通信有限公司||Data transmission method, device, electronic equipment and storage medium|
|Publication number||Priority date||Publication date||Assignee||Title|
|US20120173901A1 (en) *||2011-01-03||2012-07-05||Qualcomm Incorporated||Performance improvements in a wireless client terminal using assistance from a proxy device|
|US20130083713A1 (en) *||2011-10-03||2013-04-04||Mediatek, Inc.||Enhancement for Scheduling Request Triggering Based on Traffic Condition|
Family Cites Families (1336)
|Publication number||Priority date||Publication date||Assignee||Title|
|US447918A (en)||1891-03-10||Automatic telephone-exchange|
|US222458A (en)||1879-12-09||Improvement in automatic telephone-exchanges|
|US4276597A (en)||1974-01-17||1981-06-30||Volt Delta Resources, Inc.||Method and apparatus for information storage and retrieval|
|US4200770A (en)||1977-09-06||1980-04-29||Stanford University||Cryptographic apparatus and method|
|US4255796A (en)||1978-02-14||1981-03-10||Bell Telephone Laboratories, Incorporated||Associative information retrieval continuously guided by search status feedback|
|US4531020A (en)||1982-07-23||1985-07-23||Oak Industries Inc.||Multi-layer encryption system for the broadcast of encrypted information|
|US4807182A (en)||1986-03-12||1989-02-21||Advanced Software, Inc.||Apparatus and method for comparing data groups|
|US4831582A (en)||1986-11-07||1989-05-16||Allen-Bradley Company, Inc.||Database access machine for factory automation network|
|US4897781A (en)||1987-02-13||1990-01-30||International Business Machines Corporation||System and method for using cached data at a local node after re-opening a file at a remote node in a distributed networking environment|
|US5008853A (en)||1987-12-02||1991-04-16||Xerox Corporation||Representation of collaborative multi-user activities relative to shared structured data objects in a networked workstation environment|
|US5220657A (en)||1987-12-02||1993-06-15||Xerox Corporation||Updating local copy of shared data in a collaborative system|
|US4875159A (en)||1987-12-22||1989-10-17||Amdahl Corporation||Version management system using plural control fields for synchronizing two versions of files in a multiprocessor system|
|US4972457A (en)||1989-01-19||1990-11-20||Spectrum Information Technologies, Inc.||Portable hybrid communication system and methods|
|JP2609473B2 (en)||1989-10-23||1997-05-14||シャープ株式会社||Communication device|
|US7537167B1 (en)||1993-08-31||2009-05-26||Broadcom Corporation||Modular, portable data processing terminal for use in a radio frequency communication network|
|US7924783B1 (en)||1994-05-06||2011-04-12||Broadcom Corporation||Hierarchical communications system|
|US5263157A (en)||1990-02-15||1993-11-16||International Business Machines Corporation||Method and system for providing user access control within a distributed data processing system by the exchange of access control profiles|
|US5479472A (en)||1991-05-20||1995-12-26||Ntp Incorporated||System for interconnecting electronic mail systems by RF communications and method of operation thereof|
|US5436960A (en)||1991-05-20||1995-07-25||Campana, Jr.; Thomas J.||Electronic mail system with RF communications to mobile processors and method of operation thereof|
|US5438611A (en)||1991-05-20||1995-08-01||Ntp Incorporated||Electronic mail system with RF communications to mobile processors originating from outside of the electronic mail system and method of operation thereof|
|US5283856A (en)||1991-10-04||1994-02-01||Beyond, Inc.||Event-driven rule-based messaging system|
|WO1993009501A1 (en)||1991-11-01||1993-05-13||Yeh Keming W||Portable device having data storage capability for transferring data between a portable computer and a desktop computer|
|US5519606A (en)||1992-01-21||1996-05-21||Starfish Software, Inc.||System and methods for appointment reconciliation|
|US5357431A (en)||1992-01-27||1994-10-18||Fujitsu Limited||Character string retrieval system using index and unit for making the index|
|WO1993020641A1 (en)||1992-03-27||1993-10-14||Bell Atlantic Network Services, Inc.||Improved data transmission public switched telephone network|
|US5392390A (en)||1992-04-10||1995-02-21||Intellilink Corp.||Method for mapping, translating, and dynamically reconciling data between disparate computer platforms|
|US5689654A (en)||1992-06-29||1997-11-18||Elonex F.P. Holdings, Ltd.||Digital assistant system including a host computer with a docking bay for the digital assistant wherein a heat sink is moved into contact with a docked digital assistant for cooling the digital assistant|
|GB9213821D0 (en)||1992-06-30||1992-08-12||Inmos Ltd||Content addressable memory|
|AT239337T (en)||1992-09-30||2003-05-15||Motorola Inc||Electronic message delivery system|
|US5850627A (en)||1992-11-13||1998-12-15||Dragon Systems, Inc.||Apparatuses and methods for training and operating speech recognition systems|
|US5666530A (en)||1992-12-02||1997-09-09||Compaq Computer Corporation||System for automatic synchronization of common file between portable computer and host computer via communication channel selected from a plurality of usable channels there between|
|US5581749A (en)||1992-12-21||1996-12-03||Thedow Chemical Company||System and method for maintaining codes among distributed databases using a global database|
|US5384892A (en)||1992-12-31||1995-01-24||Apple Computer, Inc.||Dynamic language model for speech recognition|
|JPH06216935A (en)||1993-01-18||1994-08-05||Fujitsu Ltd||Electronic mail system|
|US5386564A (en)||1993-02-24||1995-01-31||Hewlett-Packard Company||Conversion of data and objects across classes in an object management system|
|US5799318A (en)||1993-04-13||1998-08-25||Firstfloor Software||Method and apparatus for collecting and displaying information from diverse computer resources|
|US5696903A (en)||1993-05-11||1997-12-09||Norand Corporation||Hierarchical communications system using microlink, data rate switching, frequency hopping and vehicular local area networking|
|JPH06324928A (en)||1993-05-14||1994-11-25||Mitsubishi Electric Corp||Log generating device, device for arbitrating versions different in file and device for arbitrating version different in computer file being at different places|
|JPH0828754B2 (en)||1993-06-30||1996-03-21||日本電気株式会社||Frame synchronization method|
|US5729704A (en)||1993-07-21||1998-03-17||Xerox Corporation||User-directed method for operating on an object-based model data structure through a second contextual image|
|EP0647909B1 (en)||1993-10-08||2003-04-16||International Business Machines Corporation||Information catalog system with object-dependent functionality|
|US5537464A (en)||1993-11-02||1996-07-16||Lewis; C. Alan||Method and apparatus for the billing of value-added communication calls|
|US7051086B2 (en)||1995-07-27||2006-05-23||Digimarc Corporation||Method of linking on-line data to printed documents|
|US5493692A (en)||1993-12-03||1996-02-20||Xerox Corporation||Selective delivery of electronic messages in a multiple computer system based on context and environment of a user|
|US5555376A (en)||1993-12-03||1996-09-10||Xerox Corporation||Method for granting a user request having locational and contextual attributes consistent with user policies for devices having locational attributes consistent with the user request|
|US5559800A (en)||1994-01-19||1996-09-24||Research In Motion Limited||Remote control of gateway functions in a wireless data communication network|
|JPH07271699A (en)||1994-03-31||1995-10-20||Canon Inc||Peripheral processor and information processor connected through network, and control method in peripheral processor and control method for peripheral processor|
|US5913032A (en)||1994-04-04||1999-06-15||Inprise Corporation||System and methods for automatically distributing a particular shared data object through electronic mail|
|US5704029A (en)||1994-05-23||1997-12-30||Wright Strategies, Inc.||System and method for completing an electronic form|
|US5434994A (en)||1994-05-23||1995-07-18||International Business Machines Corporation||System and method for maintaining replicated data coherency in a data processing system|
|US5694546A (en)||1994-05-31||1997-12-02||Reisman; Richard R.||System for automatic unattended electronic information transport between a server and a client by a vendor provided transport software with a manifest list|
|EP0804769B1 (en)||1994-06-30||2000-02-02||International Business Machines Corporation||Variable length data sequence matching method and apparatus|
|US5742905A (en)||1994-09-19||1998-04-21||Bell Communications Research, Inc.||Personal communications internetworking|
|US5802312A (en)||1994-09-27||1998-09-01||Research In Motion Limited||System for transmitting data files between computers in a wireless environment utilizing a file transfer agent executing on host system|
|US5644788A (en)||1994-10-28||1997-07-01||Cyrix Corporation||Burst transfers using an ascending or descending only burst ordering|
|US5652884A (en)||1994-11-14||1997-07-29||Object Technology Licensing Corp.||Method and apparatus for dynamic update of an existing object in an object editor|
|US5623601A (en)||1994-11-18||1997-04-22||Milkway Networks Corporation||Apparatus and method for providing a secure gateway for communication and data exchanges between networks|
|US5715403A (en)||1994-11-23||1998-02-03||Xerox Corporation||System for controlling the distribution and use of digital works having attached usage rights where the usage rights are defined by a usage rights grammar|
|US5613012A (en)||1994-11-28||1997-03-18||Smarttouch, Llc.||Tokenless identification system for authorization of electronic transactions and electronic transmissions|
|US5758257A (en)||1994-11-29||1998-05-26||Herz; Frederick||System and method for scheduling broadcast of and access to video programs and other data using customer profiles|
|US5619648A (en)||1994-11-30||1997-04-08||Lucent Technologies Inc.||Message filtering techniques|
|US5758322A (en)||1994-12-09||1998-05-26||International Voice Register, Inc.||Method and apparatus for conducting point-of-sale transactions using voice recognition|
|US5627658A (en)||1994-12-14||1997-05-06||Xerox Corporation||Automatic networked facsimile queuing system|
|US5664207A (en)||1994-12-16||1997-09-02||Xcellenet, Inc.||Systems and methods for automatically sharing information among remote/mobile nodes|
|US5572571A (en)||1994-12-30||1996-11-05||Sony Corporation||Programmable cellular telephone and system|
|US5684990A (en)||1995-01-11||1997-11-04||Puma Technology, Inc.||Synchronization of disparate databases|
|CA2167790A1 (en)||1995-01-23||1996-07-24||Donald S. Maier||Relational database system and method with high data availability during table data restructuring|
|US5729735A (en)||1995-02-08||1998-03-17||Meyering; Samuel C.||Remote database file synchronizer|
|US5706211A (en)||1995-03-02||1998-01-06||Motorola, Inc.||Message communications system|
|US5604788A (en)||1995-03-16||1997-02-18||Motorola, Inc.||Wireless messaging system with electronic mail replication|
|US5651010A (en)||1995-03-16||1997-07-22||Bell Atlantic Network Services, Inc.||Simultaneous overlapping broadcasting of digital programs|
|US5822324A (en)||1995-03-16||1998-10-13||Bell Atlantic Network Services, Inc.||Simulcasting digital video programs for broadcast and interactive services|
|US5819284A (en)||1995-03-24||1998-10-06||At&T Corp.||Personalized real time information display as a portion of a screen saver|
|JPH08297528A (en)||1995-04-25||1996-11-12||Canon Inc||Data communication device|
|US5758354A (en)||1995-04-28||1998-05-26||Intel Corporation||Application independent e-mail synchronization|
|US5793413A (en)||1995-05-01||1998-08-11||Bell Atlantic Network Services, Inc.||Wireless video distribution|
|GB2315200B (en)||1995-05-08||2000-06-21||Compuserve Inc||System for electronic messaging via wireless devices|
|US5682524A (en)||1995-05-26||1997-10-28||Starfish Software, Inc.||Databank system with methods for efficiently storing non-uniform data records|
|US5835061A (en)||1995-06-06||1998-11-10||Wayport, Inc.||Method and apparatus for geographic-based communications service|
|US5701469A (en)||1995-06-07||1997-12-23||Microsoft Corporation||Method and system for generating accurate search results using a content-index|
|US5710918A (en)||1995-06-07||1998-01-20||International Business Machines Corporation||Method for distributed task fulfillment of web browser requests|
|US5752246A (en)||1995-06-07||1998-05-12||International Business Machines Corporation||Service agent for fulfilling requests of a web browser|
|US5752186A (en)||1995-06-07||1998-05-12||Jeman Technologies, Inc.||Access free wireless telephony fulfillment service system|
|US5680542A (en)||1995-06-07||1997-10-21||Motorola, Inc.||Method and apparatus for synchronizing data in a host memory with data in target MCU memory|
|US5721908A (en)||1995-06-07||1998-02-24||International Business Machines Corporation||Computer network for WWW server data access over internet|
|US5826269A (en)||1995-06-21||1998-10-20||Microsoft Corporation||Electronic mail interface for a network server|
|US5706507A (en)||1995-07-05||1998-01-06||International Business Machines Corporation||System and method for controlling access to data located on a content server|
|US6016520A (en)||1995-07-14||2000-01-18||Microsoft Corporation||Method of viewing at a client viewing station a multiple media title stored at a server and containing a plurality of topics utilizing anticipatory caching|
|US5818437A (en)||1995-07-26||1998-10-06||Tegic Communications, Inc.||Reduced keyboard disambiguating computer|
|US5745360A (en)||1995-08-14||1998-04-28||International Business Machines Corp.||Dynamic hypertext link converter system and process|
|US5634053A (en)||1995-08-29||1997-05-27||Hughes Aircraft Company||Federated information management (FIM) system and method for providing data site filtering and translation for heterogeneous databases|
|US5647002A (en)||1995-09-01||1997-07-08||Lucent Technologies Inc.||Synchronization of mailboxes of different types|
|US5630081A (en)||1995-09-07||1997-05-13||Puma Technology, Inc.||Connection resource manager displaying link-status information using a traffic light iconic representation|
|US5721914A (en)||1995-09-14||1998-02-24||Mci Corporation||System and method for hierarchical data distribution|
|US6185184B1 (en)||1995-09-25||2001-02-06||Netspeak Corporation||Directory server for providing dynamically assigned network protocol addresses|
|US5778361A (en)||1995-09-29||1998-07-07||Microsoft Corporation||Method and system for fast indexing and searching of text in compound-word languages|
|US5758150A (en)||1995-10-06||1998-05-26||Tele-Communications, Inc.||System and method for database synchronization|
|US5757916A (en)||1995-10-06||1998-05-26||International Series Research, Inc.||Method and apparatus for authenticating the location of remote users of networked computing systems|
|US5884323A (en)||1995-10-13||1999-03-16||3Com Corporation||Extendible method and apparatus for synchronizing files on two different computer systems|
|US5727202A (en)||1995-10-18||1998-03-10||Palm Computing, Inc.||Method and apparatus for synchronizing information on two different computer systems|
|US5572643A (en)||1995-10-19||1996-11-05||Judson; David H.||Web browser with dynamic display of information objects during linking|
|US5713019A (en)||1995-10-26||1998-01-27||Keaten; Timothy M.||Iconic access to remote electronic monochrome raster data format document repository|
|JP3459149B2 (en)||1995-11-06||2003-10-20||シャープ株式会社||Email transfer system|
|US5764639A (en)||1995-11-15||1998-06-09||Staples; Leven E.||System and method for providing a remote user with a virtual presence to an office|
|US5920821A (en)||1995-12-04||1999-07-06||Bell Atlantic Network Services, Inc.||Use of cellular digital packet data (CDPD) communications to convey system identification list data to roaming cellular subscriber stations|
|US5809415A (en)||1995-12-11||1998-09-15||Unwired Planet, Inc.||Method and architecture for an interactive two-way data communication network|
|US5794210A (en)||1995-12-11||1998-08-11||Cybergold, Inc.||Attention brokerage|
|US5831664A (en)||1995-12-15||1998-11-03||Mediaone Group, Inc.||Method and system for synchronizing data between at least one mobile interface device and an interactive terminal|
|US5832483A (en)||1995-12-15||1998-11-03||Novell, Inc.||Distributed control interface for managing the interoperability and concurrency of agents and resources in a real-time environment|
|US5802454A (en)||1995-12-15||1998-09-01||Teletrac, Inc.||Remotely distributed location and messaging system|
|US6101531A (en)||1995-12-19||2000-08-08||Motorola, Inc.||System for communicating user-selected criteria filter prepared at wireless client to communication server for filtering data transferred from host to said wireless client|
|US5781901A (en)||1995-12-21||1998-07-14||Intel Corporation||Transmitting electronic mail attachment over a network using a e-mail page|
|US5903723A (en)||1995-12-21||1999-05-11||Intel Corporation||Method and apparatus for transmitting electronic mail attachments with attachment references|
|US5765171A (en)||1995-12-29||1998-06-09||Lucent Technologies Inc.||Maintaining consistency of database replicas|
|US5978933A (en)||1996-01-11||1999-11-02||Hewlett-Packard Company||Generic fault tolerant platform|
|US5787441A (en)||1996-01-11||1998-07-28||International Business Machines Corporation||Method of replicating data at a field level|
|US5781614A (en)||1996-01-19||1998-07-14||Lucent Technologies Inc.||Message retrieval via alternative access|
|US5822523A (en)||1996-02-01||1998-10-13||Mpath Interactive, Inc.||Server-group messaging system for interactive applications|
|US5841432A (en)||1996-02-09||1998-11-24||Carmel; Sharon||Method and system of building and transmitting a data file for real time play of multimedia, particularly animation, and a data file for real time play of multimedia applications|
|US6047327A (en)||1996-02-16||2000-04-04||Intel Corporation||System for distributing electronic information to a targeted group of users|
|US6513069B1 (en)||1996-03-08||2003-01-28||Actv, Inc.||Enhanced video programming system and method for providing a distributed community network|
|US5806074A (en)||1996-03-19||1998-09-08||Oracle Corporation||Configurable conflict resolution in a computer implemented distributed database|
|US5673322A (en)||1996-03-22||1997-09-30||Bell Communications Research, Inc.||System and method for providing protocol translation and filtering to access the world wide web from wireless or low-bandwidth networks|
|US5706502A (en)||1996-03-25||1998-01-06||Sun Microsystems, Inc.||Internet-enabled portfolio manager system and method|
|US5937161A (en)||1996-04-12||1999-08-10||Usa.Net, Inc.||Electronic message forwarding system|
|US6049671A (en)||1996-04-18||2000-04-11||Microsoft Corporation||Method for identifying and obtaining computer software from a network computer|
|US5809242A (en)||1996-04-19||1998-09-15||Juno Online Services, L.P.||Electronic mail system for displaying advertisement at local computer received from remote system while the local computer is off-line the remote system|
|US5751813A (en)||1996-04-29||1998-05-12||Motorola, Inc.||Use of an encryption server for encrypting messages|
|US5790974A (en)||1996-04-29||1998-08-04||Sun Microsystems, Inc.||Portable calendaring device having perceptual agent managing calendar entries|
|US5838973A (en)||1996-05-03||1998-11-17||Andersen Consulting Llp||System and method for interactively transforming a system or process into a visual representation|
|US5898780A (en)||1996-05-21||1999-04-27||Gric Communications, Inc.||Method and apparatus for authorizing remote internet access|
|US5802518A (en)||1996-06-04||1998-09-01||Multex Systems, Inc.||Information delivery system and method|
|US5781906A (en)||1996-06-06||1998-07-14||International Business Machines Corporation||System and method for construction of a data structure for indexing multidimensional objects|
|US5857201A (en)||1996-06-18||1999-01-05||Wright Strategies, Inc.||Enterprise connectivity to handheld devices|
|US5835722A (en)||1996-06-27||1998-11-10||Logon Data Corporation||System to control content and prohibit certain interactive attempts by a person using a personal computer|
|US6035104A (en)||1996-06-28||2000-03-07||Data Link Systems Corp.||Method and apparatus for managing electronic documents by alerting a subscriber at a destination other than the primary destination|
|JP3224745B2 (en)||1996-07-09||2001-11-05||株式会社日立製作所||High reliability network system and server switching method|
|CA2261262C (en)||1996-07-22||2007-08-21||Cyva Research Corporation||Personal information security and exchange tool|
|US5862223A (en)||1996-07-24||1999-01-19||Walker Asset Management Limited Partnership||Method and apparatus for a cryptographically-assisted commercial network system designed to facilitate and support expert-based commerce|
|US5940813A (en)||1996-07-26||1999-08-17||Citibank, N.A.||Process facility management matrix and system and method for performing batch, processing in an on-line environment|
|US5802524A (en)||1996-07-29||1998-09-01||International Business Machines Corporation||Method and product for integrating an object-based search engine with a parametrically archived database|
|EP0822502A1 (en)||1996-07-31||1998-02-04||BRITISH TELECOMMUNICATIONS public limited company||Data access system|
|US6543695B1 (en)||1996-08-02||2003-04-08||Symbol Technologies, Inc.||Housing for hand held scanner|
|US5974238A (en)||1996-08-07||1999-10-26||Compaq Computer Corporation||Automatic data synchronization between a handheld and a host computer using pseudo cache including tags and logical data elements|
|US5758355A (en)||1996-08-07||1998-05-26||Aurum Software, Inc.||Synchronization of server database with client database using distribution tables|
|US5852820A (en)||1996-08-09||1998-12-22||Digital Equipment Corporation||Method for optimizing entries for searching an index|
|US5832500A (en)||1996-08-09||1998-11-03||Digital Equipment Corporation||Method for searching an index|
|US6016478A (en)||1996-08-13||2000-01-18||Starfish Software, Inc.||Scheduling system with methods for peer-to-peer scheduling of remote users|
|US5867817A (en)||1996-08-19||1999-02-02||Virtual Vision, Inc.||Speech recognition manager|
|US5822747A (en)||1996-08-23||1998-10-13||Tandem Computers, Inc.||System and method for optimizing database queries|
|US5898917A (en)||1996-08-27||1999-04-27||Ag Communication Systems Corporation||System for providing enhanced services in cellular radio telecommunication systems using #CCSC based triggers|
|FI111428B (en)||1996-08-29||2003-07-15||Nokia Corp||Gallup utilizing wireless data|
|US5838252A (en)||1996-09-09||1998-11-17||Datalink Systems, Inc.||Interactive two-way pager systems|
|US5852775A (en)||1996-09-12||1998-12-22||Earthweb, Inc.||Cellular telephone advertising system|
|US7359720B2 (en)||1996-09-27||2008-04-15||Openwave Systems Inc.||Mobility extended telephone application programming interface and method of use|
|US6018343A (en)||1996-09-27||2000-01-25||Timecruiser Computing Corp.||Web calendar architecture and uses thereof|
|US5978837A (en)||1996-09-27||1999-11-02||At&T Corp.||Intelligent pager for remotely managing E-Mail messages|
|US6181935B1 (en)||1996-09-27||2001-01-30||Software.Com, Inc.||Mobility extended telephone application programming interface and method of use|
|US5892909A (en)||1996-09-27||1999-04-06||Diffusion, Inc.||Intranet-based system with methods for co-active delivery of information to multiple users|
|TW347498B (en)||1996-09-30||1998-12-11||Casio Computer Co Ltd||Information supply system|
|US5838768A (en)||1996-10-03||1998-11-17||Telefonaktiebolaget L M Ericsson||System and method for controlled media conversion in an intelligent network|
|US5870759A (en)||1996-10-09||1999-02-09||Oracle Corporation||System for synchronizing data between computers using a before-image of data|
|US5790790A (en)||1996-10-24||1998-08-04||Tumbleweed Software Corporation||Electronic document delivery system in which notification of said electronic document is sent to a recipient thereof|
|FI113224B (en)||1996-11-11||2004-03-15||Nokia Corp||Implementation of invoicing in a data communication system|
|US5943676A (en)||1996-11-13||1999-08-24||Puma Technology, Inc.||Synchronization of recurring records in incompatible databases|
|US6141664A (en)||1996-11-13||2000-10-31||Puma Technology, Inc.||Synchronization of databases with date range|
|US6212529B1 (en)||1996-11-13||2001-04-03||Puma Technology, Inc.||Synchronization of databases using filters|
|US6405218B1 (en)||1996-11-13||2002-06-11||Pumatech, Inc.||Synchronizing databases|
|US6148377A (en)||1996-11-22||2000-11-14||Mangosoft Corporation||Shared memory computer networks|
|FI104139B1 (en)||1996-11-27||1999-11-15||Nokia Telecommunications Oy||Use two SIM cards with the same MSISDN number|
|US6202085B1 (en)||1996-12-06||2001-03-13||Microsoft Corportion||System and method for incremental change synchronization between multiple copies of data|
|US6131116A (en)||1996-12-13||2000-10-10||Visto Corporation||System and method for globally accessing computer services|
|US6708221B1 (en)||1996-12-13||2004-03-16||Visto Corporation||System and method for globally and securely accessing unified information in a computer network|
|US7225231B2 (en)||2000-09-20||2007-05-29||Visto Corporation||System and method for transmitting workspace elements across a network|
|JP3244166B2 (en)||1996-12-25||2002-01-07||ユニデン株式会社||Information reservation transmission method, information reservation transmission method, and transmission server|
|US5963642A (en)||1996-12-30||1999-10-05||Goldstein; Benjamin D.||Method and apparatus for secure storage of data|
|US6411696B1 (en)||1996-12-31||2002-06-25||Intel Corporation||System for finding a user with a preferred communication mechanism|
|US5907618A (en)||1997-01-03||1999-05-25||International Business Machines Corporation||Method and apparatus for verifiably providing key recovery information in a cryptographic system|
|US6175831B1 (en)||1997-01-17||2001-01-16||Six Degrees, Inc.||Method and apparatus for constructing a networking database and system|
|US6097383A (en)||1997-01-23||2000-08-01||Zenith Electronics Corporation||Video and audio functions in a web television|
|US6401112B1 (en)||1997-01-29||2002-06-04||Palm, Inc.||Method and apparatus for synchronizing an Email client on a portable computer system with an Email client on a desktop computer|
|US6006274A (en)||1997-01-30||1999-12-21||3Com Corporation||Method and apparatus using a pass through personal computer connected to both a local communication link and a computer network for indentifying and synchronizing a preferred computer with a portable computer|
|US5964833A (en)||1997-02-07||1999-10-12||Datalink Systems Corp.||Pager enhanced keyboard and system|
|US5790425A (en)||1997-02-19||1998-08-04||Sun Microsystems, Inc.||Generic server benchmarking framework in a client-server environment|
|US5928325A (en)||1997-02-24||1999-07-27||Motorola, Inc.||Method of dynamically establishing communication of incoming messages to one or more user devices presently available to an intended recipient|
|US6003070A (en)||1997-02-25||1999-12-14||Intervvoice Limited Partnership||E-mail system and interface for equipment monitoring and control|
|US5890147A (en)||1997-03-07||1999-03-30||Microsoft Corporation||Scope testing of documents in a search engine using document to folder mapping|
|US5948066A (en)||1997-03-13||1999-09-07||Motorola, Inc.||System and method for delivery of information over narrow-band communications links|
|US5867665A (en)||1997-03-24||1999-02-02||Pfn, Inc||Domain communications server|
|US6546005B1 (en)||1997-03-25||2003-04-08||At&T Corp.||Active user registry|
|US6138128A (en)||1997-04-02||2000-10-24||Microsoft Corp.||Sharing and organizing world wide web references using distinctive characters|
|US6085192A (en)||1997-04-11||2000-07-04||Roampage, Inc.||System and method for securely synchronizing multiple copies of a workspace element in a network|
|US5961590A (en)||1997-04-11||1999-10-05||Roampage, Inc.||System and method for synchronizing electronic mail between a client site and a central site|
|US6023708A (en)||1997-05-29||2000-02-08||Visto Corporation||System and method for using a global translator to synchronize workspace elements across a network|
|JPH10336372A (en)||1997-05-30||1998-12-18||Ricoh Co Ltd||Transfer method for scan data|
|US5890129A (en)||1997-05-30||1999-03-30||Spurgeon; Loren J.||System for exchanging health care insurance information|
|US6320943B1 (en)||1997-06-12||2001-11-20||Legerity, Inc.||Electronic directory system and method|
|US6023700A (en)||1997-06-17||2000-02-08||Cranberry Properties, Llc||Electronic mail distribution system for integrated electronic communication|
|NZ330703A (en)||1997-06-17||2000-03-27||Telecom Wireless Solutions Inc||Electronic mail system for interconnecting computer networks with digital mobile phone network|
|EP0992002A2 (en)||1997-06-19||2000-04-12||Brian E. Marchant||Security apparatus for data transmission with dynamic random encryption|
|US6073142A (en)||1997-06-23||2000-06-06||Park City Group||Automated post office based rule analysis of e-mail messages and other data objects for controlled distribution in network environments|
|US6057855A (en)||1997-07-02||2000-05-02||Hewlett-Packard Company||Method and apparatus for providing polygon pixel sub-sample information using incremental means|
|US6044372A (en)||1997-07-18||2000-03-28||Dazel Corporation||Method and apparatus for publishing information to a communications network and enabling subscriptions to such information|
|US6073165A (en)||1997-07-29||2000-06-06||Jfax Communications, Inc.||Filtering computer network messages directed to a user's e-mail box based on user defined filters, and forwarding a filtered message to the user's receiver|
|US6101320A (en)||1997-08-01||2000-08-08||Aurora Communications Exchange Ltd.||Electronic mail communication system and method|
|US7088801B1 (en)||1997-09-08||2006-08-08||Mci, Inc.||Single telephone number access to multiple communications services|
|US20010010046A1 (en)||1997-09-11||2001-07-26||Muyres Matthew R.||Client content management and distribution system|
|US6044381A (en)||1997-09-11||2000-03-28||Puma Technology, Inc.||Using distributed history files in synchronizing databases|
|US5845278A (en)||1997-09-12||1998-12-01||Inioseek Corporation||Method for automatically selecting collections to search in full text searches|
|US6098172A (en)||1997-09-12||2000-08-01||Lucent Technologies Inc.||Methods and apparatus for a computer network firewall with proxy reflection|
|US5909689A (en)||1997-09-18||1999-06-01||Sony Corporation||Automatic update of file versions for files shared by several computers which record in respective file directories temporal information for indicating when the files have been created|
|US6138146A (en)||1997-09-29||2000-10-24||Ericsson Inc.||Electronic mail forwarding system and method|
|US6125369A (en)||1997-10-02||2000-09-26||Microsoft Corporation||Continuous object sychronization between object stores on different computers|
|US5924096A (en)||1997-10-15||1999-07-13||Novell, Inc.||Distributed database using indexed into tags to tracks events according to type, update cache, create virtual update log on demand|
|US5907681A (en)||1997-10-20||1999-05-25||International Business Machines Corporation||Intelligent method, apparatus and computer program product for automated refreshing of internet web pages|
|US5974327A (en)||1997-10-21||1999-10-26||At&T Corp.||Adaptive frequency channel assignment based on battery power level in wireless access protocols|
|US6052735A (en)||1997-10-24||2000-04-18||Microsoft Corporation||Electronic mail object synchronization between a desktop computer and mobile device|
|US6272545B1 (en)||1997-10-24||2001-08-07||Microsoft Corporation||System and method for interaction between one or more desktop computers and one or more mobile devices|
|US6269369B1 (en)||1997-11-02||2001-07-31||Amazon.Com Holdings, Inc.||Networked personal contact manager|
|FR2771875B1 (en)||1997-11-04||2000-04-14||Gilles Jean Antoine Kremer||Method for transmitting information and computer server implementing it|
|US6112181A (en)||1997-11-06||2000-08-29||Intertrust Technologies Corporation||Systems and methods for matching, selecting, narrowcasting, and/or classifying based on rights management and/or other information|
|US6034621A (en)||1997-11-18||2000-03-07||Lucent Technologies, Inc.||Wireless remote synchronization of data between PC and PDA|
|US5951636A (en)||1997-12-04||1999-09-14||International Business Machines Corp.||Accessing a post office system from a client computer using applets|
|US6052563A (en)||1997-12-10||2000-04-18||Motorola||Communication device controlled by appointment information stored therein, and method therefor|
|US6295541B1 (en)||1997-12-16||2001-09-25||Starfish Software, Inc.||System and methods for synchronizing two or more datasets|
|US6324587B1 (en)||1997-12-23||2001-11-27||Microsoft Corporation||Method, computer program product, and data structure for publishing a data object over a store and forward transport|
|US6487557B1 (en)||1997-12-26||2002-11-26||Casio Computer Co., Ltd.||Network-access management system and method applied to network and computer program product including computer program recorded on storage medium for creating display data|
|US6151606A (en)||1998-01-16||2000-11-21||Visto Corporation||System and method for using a workspace data manager to access, manipulate and synchronize network data|
|US5960406A (en)||1998-01-22||1999-09-28||Ecal, Corp.||Scheduling system for use between users on the web|
|US6157630A (en)||1998-01-26||2000-12-05||Motorola, Inc.||Communications system with radio device and server|
|JP3561139B2 (en)||1998-01-27||2004-09-02||シャープ株式会社||File object relay method, computer-readable recording medium storing program of file object relay method, and gateway computer|
|US6119171A (en)||1998-01-29||2000-09-12||Ip Dynamics, Inc.||Domain name routing|
|US6205448B1 (en)||1998-01-30||2001-03-20||3Com Corporation||Method and apparatus of synchronizing two computer systems supporting multiple synchronization techniques|
|US6185598B1 (en)||1998-02-10||2001-02-06||Digital Island, Inc.||Optimized network resource location|
|US6138013A (en)||1998-02-12||2000-10-24||Motorola, Inc.||Method for location based intercept in a communication system|
|US7080371B1 (en)||1998-03-03||2006-07-18||Siebel Systems, Inc.||Method, system, apparatus and program product for distribution and instantiation of software upgrades|
|US6304881B1 (en)||1998-03-03||2001-10-16||Pumatech, Inc.||Remote data access and synchronization|
|US7032242B1 (en)||1998-03-05||2006-04-18||3Com Corporation||Method and system for distributed network address translation with network security features|
|US20010037453A1 (en)||1998-03-06||2001-11-01||Mitty Todd Jay||Secure electronic transactions using a trusted intermediary with non-repudiation of receipt and contents of message|
|US6167379A (en)||1998-03-24||2000-12-26||Siemens Information And Communication Networks, Inc.||System for user to accept or decline updating a calendar remotely with a proposed schedule update that may have schedule confliction|
|US6170014B1 (en)||1998-03-25||2001-01-02||Community Learning And Information Network||Computer architecture for managing courseware in a shared use operating environment|
|US6018762A (en)||1998-03-31||2000-01-25||Lucent Technologies Inc.||Rules-based synchronization of mailboxes in a data network|
|US6925477B1 (en)||1998-03-31||2005-08-02||Intellisync Corporation||Transferring records between two databases|
|US6119014A (en)||1998-04-01||2000-09-12||Ericsson Inc.||System and method for displaying short messages depending upon location, priority, and user-defined indicators|
|US6370566B2 (en)||1998-04-10||2002-04-09||Microsoft Corporation||Generating meeting requests and group scheduling from a mobile device|
|US6128627A (en)||1998-04-15||2000-10-03||Inktomi Corporation||Consistent data storage in an object cache|
|US6065055A (en)||1998-04-20||2000-05-16||Hughes; Patrick Alan||Inappropriate site management software|
|US6006197A (en)||1998-04-20||1999-12-21||Straightup Software, Inc.||System and method for assessing effectiveness of internet marketing campaign|
|US6421781B1 (en)||1998-04-30||2002-07-16||Openwave Systems Inc.||Method and apparatus for maintaining security in a push server|
|US6233341B1 (en)||1998-05-19||2001-05-15||Visto Corporation||System and method for installing and using a temporary certificate at a remote site|
|US6816849B1 (en)||1998-05-26||2004-11-09||Gerald B. Halt, Jr.||Advanced internet interface|
|US6195533B1 (en)||1998-05-27||2001-02-27||Glenayre Electronics, Inc.||Method for storing an application's transaction data in a wireless messaging system|
|FI105743B (en)||1998-05-27||2000-09-29||Nokia Mobile Phones Ltd||Method for multimedia messaging and multimedia messaging system|
|US6327586B1 (en)||1998-05-27||2001-12-04||Wisdombuilder, L.L.C.||System method and computer program product to automate the management and analysis of heterogeneous data|
|US6529908B1 (en)||1998-05-28||2003-03-04||Netspan Corporation||Web-updated database with record distribution by email|
|US6463463B1 (en)||1998-05-29||2002-10-08||Research In Motion Limited||System and method for pushing calendar event messages from a host system to a mobile data communication device|
|US6219694B1 (en)||1998-05-29||2001-04-17||Research In Motion Limited||System and method for pushing information from a host system to a mobile data communication device having a shared electronic address|
|US6377991B1 (en)||1998-05-29||2002-04-23||Microsoft Corporation||Method, computer program product, and system for migrating URLs within a dynamically changing distributed cache of URLs|
|US6438585B2 (en)||1998-05-29||2002-08-20||Research In Motion Limited||System and method for redirecting message attachments between a host system and a mobile data communication device|
|US7025209B2 (en)||1998-05-29||2006-04-11||Palmsource, Inc.||Method and apparatus for wireless internet access|
|US6289214B1 (en)||1998-05-29||2001-09-11||Ericsson Inc.||Systems and methods for deactivating a cellular radiotelephone system using an ANSI-41 short message service email|
|US6782409B1 (en)||1998-05-29||2004-08-24||Sony Corporation||Experience/sympathy information providing system|
|US6779019B1 (en)||1998-05-29||2004-08-17||Research In Motion Limited||System and method for pushing information from a host system to a mobile data communication device|
|US6311216B1 (en)||1998-05-29||2001-10-30||Microsoft Corporation||Method, computer program product, and system for client-side deterministic routing and URL lookup into a distributed cache of URLS|
|US6341311B1 (en)||1998-05-29||2002-01-22||Microsoft Corporation||Directing data object access requests in a distributed cache|
|CA2334880A1 (en)||1998-06-11||1999-12-16||Boardwalk Ltd.||System, method, and computer program product for providing relational patterns between entities|
|NL1009376C1 (en)||1998-06-11||1998-07-06||Boardwalk Ag||Data system for providing relationship patterns between people.|
|US6085166A (en)||1998-06-19||2000-07-04||International Business Machines||Electronic calendar with group scheduling and asynchronous fan out method|
|US6101480A (en)||1998-06-19||2000-08-08||International Business Machines||Electronic calendar with group scheduling and automated scheduling techniques for coordinating conflicting schedules|
|WO2000001132A1 (en)||1998-06-30||2000-01-06||Paragon Software (Developments) Ltd.||Telephone directory management system having wireless telephone interface capability|
|US6363051B1 (en)||1998-06-30||2002-03-26||At&T Corp.||Method and apparatus for achieving fast reconnection of permanent virtal channels in a frame relay network|
|SE523335C2 (en)||1998-07-03||2004-04-13||Sendit Ab||Method and apparatus for accessing and retrieving information|
|JP4170448B2 (en)||1998-07-03||2008-10-22||富士通株式会社||Group contact system and recording medium recording program for executing contact system|
|US6300947B1 (en)||1998-07-06||2001-10-09||International Business Machines Corporation||Display screen and window size related web page adaptation system|
|US6256666B1 (en)||1998-07-14||2001-07-03||International Business Machines Corp.||Method and system for remotely managing electronic mail attachments|
|US6275850B1 (en)||1998-07-24||2001-08-14||Siemens Information And Communication Networks, Inc.||Method and system for management of message attachments|
|US6886030B1 (en)||1998-08-18||2005-04-26||United Video Properties, Inc.||Electronic mail system employing a low bandwidth link for e-mail notifications|
|US6336138B1 (en)||1998-08-25||2002-01-01||Hewlett-Packard Company||Template-driven approach for generating models on network services|
|US6438612B1 (en)||1998-09-11||2002-08-20||Ssh Communications Security, Ltd.||Method and arrangement for secure tunneling of data between virtual routers|
|US6721288B1 (en)||1998-09-16||2004-04-13||Openwave Systems Inc.||Wireless mobile devices having improved operation during network unavailability|
|US6289212B1 (en)||1998-09-16||2001-09-11||Openwave Systems Inc.||Method and apparatus for providing electronic mail services during network unavailability|
|US6115709A (en)||1998-09-18||2000-09-05||Tacit Knowledge Systems, Inc.||Method and system for constructing a knowledge profile of a user having unrestricted and restricted access portions according to respective levels of confidence of content of the portions|
|US6253202B1 (en)||1998-09-18||2001-06-26||Tacit Knowledge Systems, Inc.||Method, system and apparatus for authorizing access by a first user to a knowledge profile of a second user responsive to an access request from the first user|
|US6198922B1 (en)||1998-09-22||2001-03-06||Iridium Ip Llc||Method and system for locating subscribers in a global telecommunications network|
|US6389455B1 (en)||1998-09-22||2002-05-14||Richard C. Fuisz||Method and apparatus for bouncing electronic messages|
|US6718740B2 (en)||1998-09-24||2004-04-13||Bell & Howell Mail And Messaging Technologies Company||Inserting apparatus and method with controlled, master cycle speed-dependent actuator operations|
|US6622157B1 (en)||1998-09-28||2003-09-16||Certeon, Inc.||Extending network services using mobile agents|
|US7509349B2 (en)||1998-10-01||2009-03-24||Onepin, Inc.||Method and apparatus for storing and retrieving business contact information in a computer system|
|US6131096A (en)||1998-10-05||2000-10-10||Visto Corporation||System and method for updating a remote database in a network|
|US6546425B1 (en)||1998-10-09||2003-04-08||Netmotion Wireless, Inc.||Method and apparatus for providing mobile and other intermittent connectivity in a computing environment|
|US7136645B2 (en)||1998-10-09||2006-11-14||Netmotion Wireless, Inc.||Method and apparatus for providing mobile and other intermittent connectivity in a computing environment|
|US7882247B2 (en)||1999-06-11||2011-02-01||Netmotion Wireless, Inc.||Method and apparatus for providing secure connectivity in mobile and other intermittent computing environments|
|US7293107B1 (en)||1998-10-09||2007-11-06||Netmotion Wireless, Inc.||Method and apparatus for providing mobile and other intermittent connectivity in a computing environment|
|US6263340B1 (en)||1998-10-20||2001-07-17||International Business Machines Corp.||User registration in file review systems|
|US6324544B1 (en)||1998-10-21||2001-11-27||Microsoft Corporation||File object synchronization between a desktop computer and a mobile device|
|US6871220B1 (en)||1998-10-28||2005-03-22||Yodlee, Inc.||System and method for distributed storage and retrieval of personal information|
|US6535892B1 (en)||1999-03-08||2003-03-18||Starfish Software, Inc.||System and methods for exchanging messages between a client and a server for synchronizing datasets|
|US6502135B1 (en)||1998-10-30||2002-12-31||Science Applications International Corporation||Agile network protocol for secure communications with assured system availability|
|US6167435A (en)||1998-10-30||2000-12-26||Netcreations, Inc.||Double opt-in™ method and system for verifying subscriptions to information distribution services|
|US6321338B1 (en)||1998-11-09||2001-11-20||Sri International||Network surveillance|
|US6363352B1 (en)||1998-11-13||2002-03-26||Microsoft Corporation||Automatic scheduling and formation of a virtual meeting over a computer network|
|FI982490A0 (en)||1998-11-18||1998-11-18||Nokia Corp||Procedures and systems for communication|
|US6490353B1 (en)||1998-11-23||2002-12-03||Tan Daniel Tiong Hok||Data encrypting and decrypting apparatus and method|
|AU759014B2 (en)||1998-11-30||2003-04-03||Rovi Guides, Inc.||Smart agent based on habit, statistical inference and psycho-demographic profiling|
|US6859212B2 (en)||1998-12-08||2005-02-22||Yodlee.Com, Inc.||Interactive transaction center interface|
|US20010023414A1 (en)||1998-12-08||2001-09-20||Srihari Kumar||Interactive calculation and presentation of financial data results through a single interface on a data-packet-network|
|US6249808B1 (en)||1998-12-15||2001-06-19||At&T Corp||Wireless delivery of message using combination of text and voice|
|US6292904B1 (en)||1998-12-16||2001-09-18||International Business Machines Corporation||Client account generation and authentication system for a network server|
|US6760916B2 (en)||2000-01-14||2004-07-06||Parkervision, Inc.||Method, system and computer program product for producing and distributing enhanced media downstreams|
|US6516327B1 (en)||1998-12-24||2003-02-04||International Business Machines Corporation||System and method for synchronizing data in multiple databases|
|US20010013069A1 (en)||1999-01-11||2001-08-09||Infospace, Inc.||Data messaging aggregation|
|US6209038B1 (en)||1999-01-13||2001-03-27||International Business Machines Corporation||Technique for aggregate transaction scope across multiple independent web requests|
|EP1142218B1 (en)||1999-01-14||2007-10-31||Nokia Corporation||Interception method and system|
|US6442589B1 (en)||1999-01-14||2002-08-27||Fujitsu Limited||Method and system for sorting and forwarding electronic messages and other data|
|FR2788914B1 (en)||1999-01-22||2001-03-23||Sfr Sa||AUTHENTICATION METHOD, WITH ESTABLISHMENT OF A SECURE CHANNEL, BETWEEN A SUBSCRIBER AND A SERVICE PROVIDER ACCESSIBLE VIA A TELECOMMUNICATION OPERATOR|
|US6351767B1 (en)||1999-01-25||2002-02-26||International Business Machines Corporation||Method and system for automatically caching dynamic content based on a cacheability determination|
|US6735591B2 (en)||1999-01-26||2004-05-11||Joseph M. Khan||Universal information warehouse system and method|
|US6173446B1 (en)||1999-02-02||2001-01-09||Ultimus, Inc.||Apparatus for licensing software applications|
|US6201469B1 (en)||1999-02-12||2001-03-13||Sensormatic Electronics Corporation||Wireless synchronization of pulsed magnetic EAS systems|
|US6526506B1 (en)||1999-02-25||2003-02-25||Telxon Corporation||Multi-level encryption access point for wireless network|
|US6247135B1 (en)||1999-03-03||2001-06-12||Starfish Software, Inc.||Synchronization process negotiation for computing devices|
|US6449622B1 (en)||1999-03-08||2002-09-10||Starfish Software, Inc.||System and methods for synchronizing datasets when dataset changes may be received out of order|
|US6377790B1 (en)||1999-03-08||2002-04-23||Sharp Laboratories Of America, Inc.||Mobile-initiated, packet switched communications method|
|US6415031B1 (en)||1999-03-12||2002-07-02||Diva Systems Corporation||Selective and renewable encryption for secure distribution of video on-demand|
|JP4299911B2 (en)||1999-03-24||2009-07-22||株式会社東芝||Information transfer system|
|US7062532B1 (en)||1999-03-25||2006-06-13||Autodesk, Inc.||Method and apparatus for drawing collaboration on a network|
|US6820204B1 (en)||1999-03-31||2004-11-16||Nimesh Desai||System and method for selective information exchange|
|US6308201B1 (en)||1999-04-08||2001-10-23||Palm, Inc.||System and method for sharing data among a plurality of personal digital assistants|
|US6336117B1 (en)||1999-04-30||2002-01-01||International Business Machines Corporation||Content-indexing search system and method providing search results consistent with content filtering and blocking policies implemented in a blocking engine|
|US8050964B2 (en)||1999-05-06||2011-11-01||Etagz, Inc.||Computer-readable medium product label apparatus and method|
|US6622127B1 (en)||1999-05-11||2003-09-16||Kaiser Foundation Hospitals||Order allocation to select from inventory locations stocking few units of inventory|
|US6668046B1 (en)||1999-05-18||2003-12-23||Motorola, Inc.||Method and system for generating a user's telecommunications bill|
|US6560456B1 (en)||1999-05-24||2003-05-06||Openwave Systems, Inc.||System and method for providing subscriber-initiated information over the short message service (SMS) or a microbrowser|
|US6996627B1 (en)||1999-05-25||2006-02-07||Realnetworks, Inc.||System and method for providing update information|
|US6377810B1 (en)||1999-06-11||2002-04-23||Motorola, Inc.||Method of operation of mobile wireless communication system with location information|
|US6198696B1 (en)||1999-06-16||2001-03-06||Siemens Information And Communication Networks, Inc.||Device and method for tracking time zone changes in communications devices|
|US6782252B1 (en)||1999-06-26||2004-08-24||Lg Information & Communications, Ltd.||Apparatus and method for transmitting call holding message in mobile communication terminal|
|EP1197075A1 (en)||1999-06-28||2002-04-17||United Video Properties, Inc.||Interactive television program guide system and method with niche hubs|
|US6704278B1 (en)||1999-07-02||2004-03-09||Cisco Technology, Inc.||Stateful failover of service managers|
|US6401104B1 (en)||1999-07-03||2002-06-04||Starfish Software, Inc.||System and methods for synchronizing datasets using cooperation among multiple synchronization engines|
|US6356937B1 (en)||1999-07-06||2002-03-12||David Montville||Interoperable full-featured web-based and client-side e-mail system|
|US6618710B1 (en)||1999-07-07||2003-09-09||International Business Machines Corporation||Apparatus and method for intelligent routing of electronic messages to pagers and computers|
|US6721410B1 (en)||1999-08-10||2004-04-13||Nortel Networks Limited||Recursive identification of individuals for casual collaborative conferencing|
|US6442637B1 (en)||1999-08-12||2002-08-27||Handspring, Inc.||Expandable mobile computer system|
|KR100565040B1 (en)||1999-08-20||2006-03-30||삼성전자주식회사||User interface method using 3-dimensional user input device in 3-dimensional graphic display and computer readable medium therefor|
|US6640249B1 (en)||1999-08-31||2003-10-28||Accenture Llp||Presentation services patterns in a netcentric environment|
|US6742015B1 (en)||1999-08-31||2004-05-25||Accenture Llp||Base services patterns in a netcentric environment|
|US6640244B1 (en)||1999-08-31||2003-10-28||Accenture Llp||Request batcher in a transaction services patterns environment|
|US7289964B1 (en)||1999-08-31||2007-10-30||Accenture Llp||System and method for transaction services patterns in a netcentric environment|
|US6615253B1 (en)||1999-08-31||2003-09-02||Accenture Llp||Efficient server side data retrieval for execution of client side applications|
|US6549939B1 (en)||1999-08-31||2003-04-15||International Business Machines Corporation||Proactive calendar notification agent|
|US6965917B1 (en)||1999-09-07||2005-11-15||Comverse Ltd.||System and method for notification of an event|
|US7079499B1 (en)||1999-09-08||2006-07-18||Nortel Networks Limited||Internet protocol mobility architecture framework|
|US6601026B2 (en)||1999-09-17||2003-07-29||Discern Communications, Inc.||Information retrieval by natural language querying|
|AU7564200A (en)||1999-09-22||2001-04-24||Oleg Kharisovich Zommers||Interactive personal information system and method|
|US6505214B1 (en)||1999-09-28||2003-01-07||Microsoft Corporation||Selective information synchronization based on implicit user designation|
|EP1236138A1 (en)||1999-09-30||2002-09-04||Oy Riddes Ltd||A method for carrying out questionnaire based survey in cellular radio system, a cellular radio system and a base station|
|US7020685B1 (en)||1999-10-08||2006-03-28||Openwave Systems Inc.||Method and apparatus for providing internet content to SMS-based wireless devices|
|US20030078880A1 (en)||1999-10-08||2003-04-24||Nancy Alley||Method and system for electronically signing and processing digital documents|
|EP1234246B1 (en)||1999-10-22||2015-08-12||Nomadix, Inc.||System and method for network access without reconfiguration|
|US7630986B1 (en)||1999-10-27||2009-12-08||Pinpoint, Incorporated||Secure data interchange|
|US7167839B1 (en)||1999-11-05||2007-01-23||Commercial Recovery Corporation||Collection agency data access method|
|US6721780B1 (en)||1999-11-09||2004-04-13||Fireclick, Inc.||Predictive pre-download of network objects|
|US20020055351A1 (en)||1999-11-12||2002-05-09||Elsey Nicholas J.||Technique for providing personalized information and communications services|
|US8032409B1 (en)||1999-11-22||2011-10-04||Accenture Global Services Limited||Enhanced visibility during installation management in a network-based supply chain environment|
|US6532446B1 (en)||1999-11-24||2003-03-11||Openwave Systems Inc.||Server based speech recognition user interface for wireless devices|
|US7120692B2 (en)||1999-12-02||2006-10-10||Senvid, Inc.||Access and control system for network-enabled devices|
|US6499054B1 (en)||1999-12-02||2002-12-24||Senvid, Inc.||Control and observation of physical devices, equipment and processes by multiple users over computer networks|
|DE19958707A1 (en)||1999-12-06||2001-06-07||Siemens Ag||Method of transmitting a text message|
|ES2253276T3 (en)||1999-12-13||2006-06-01||Markport Limited||ACCESS NODE FOR SERVICE MANAGEMENT.|
|US6526433B1 (en)||1999-12-15||2003-02-25||International Business Machines Corporation||Adaptive timeout value setting for distributed computing environment (DCE) applications|
|WO2001046825A1 (en)||1999-12-20||2001-06-28||Planetid, Inc.||Information exchange engine providing a critical infrastructure layer and methods of use thereof|
|US6834195B2 (en)||2000-04-04||2004-12-21||Carl Brock Brandenberg||Method and apparatus for scheduling presentation of digital content on a personal communication device|
|US6892196B1 (en)||1999-12-22||2005-05-10||Accenture Llp||System, method and article of manufacture for a user programmable diary interface link|
|US6728530B1 (en)||1999-12-28||2004-04-27||Nokia Corporation||Calendar-display apparatus, and associated method, for a mobile terminal|
|US6898427B1 (en)||1999-12-29||2005-05-24||Bellsouth Intellectual Property Corporation||Method of coupling portable communications device to first network by way of second network|
|US6771294B1 (en)||1999-12-29||2004-08-03||Petri Pulli||User interface|
|US7146645B1 (en)||1999-12-30||2006-12-05||Nokia Mobile Phones Ltd.||Dedicated applications for user stations and methods for downloading dedicated applications to user stations|
|US6625621B2 (en)||2000-01-04||2003-09-23||Starfish Software, Inc.||System and methods for a fast and scalable synchronization server|
|US7050079B1 (en)||2000-01-04||2006-05-23||International Business Machines Corporation||System and method for dynamically generating viewable graphics|
|US6727917B1 (en)||2000-01-06||2004-04-27||Microsoft Corporation||User interface for palm-sized computing devices and method and apparatus for displaying the same|
|US6664991B1 (en)||2000-01-06||2003-12-16||Microsoft Corporation||Method and apparatus for providing context menus on a pen-based device|
|US6496802B1 (en)||2000-01-07||2002-12-17||Mp3.Com, Inc.||System and method for providing access to electronic works|
|US6745024B1 (en)||2000-01-10||2004-06-01||Qualcomm Incorporated||System and method for preparing and sending an electronic mail communication using a wireless communications device|
|GB2364477B (en)||2000-01-18||2003-11-05||Ericsson Telefon Ab L M||Virtual private networks|
|US6694336B1 (en)||2000-01-25||2004-02-17||Fusionone, Inc.||Data transfer and synchronization system|
|US8156074B1 (en)||2000-01-26||2012-04-10||Synchronoss Technologies, Inc.||Data transfer and synchronization system|
|US6671757B1 (en)||2000-01-26||2003-12-30||Fusionone, Inc.||Data transfer and synchronization system|
|US20010042099A1 (en)||2000-02-02||2001-11-15||Doongo Technologies, Inc.||Apparatus and methods for optimizing traffic volume in wireless email communications|
|US6816944B2 (en)||2000-02-02||2004-11-09||Innopath Software||Apparatus and methods for providing coordinated and personalized application and data management for resource-limited mobile devices|
|JP2001218185A (en)||2000-02-03||2001-08-10||Matsushita Electric Ind Co Ltd||Device and system for transferring data and program recording medium|
|US6742059B1 (en)||2000-02-04||2004-05-25||Emc Corporation||Primary and secondary management commands for a peripheral connected to multiple agents|
|US7240067B2 (en)||2000-02-08||2007-07-03||Sybase, Inc.||System and methodology for extraction and aggregation of data from dynamic content|
|US6721787B1 (en)||2000-02-10||2004-04-13||3Com Corporation||System and method for wireless hot-synchronization of a personal digital assistant|
|AU3693301A (en)||2000-02-11||2001-08-20||Etrieve Inc||One-touch method and system for providing email to a wireless communication device|
|US6895558B1 (en)||2000-02-11||2005-05-17||Microsoft Corporation||Multi-access mode electronic personal assistant|
|US6421674B1 (en)||2000-02-15||2002-07-16||Nortel Networks Limited||Methods and systems for implementing a real-time, distributed, hierarchical database using a proxiable protocol|
|FI110352B (en)||2000-02-24||2002-12-31||Nokia Corp||Method and Arrangement for Optimizing Reconnection in a Cellular Radio System Supporting Real-Time and Non-Real-Time Data Transmission|
|US20040117387A1 (en)||2000-02-25||2004-06-17||Vincent Civetta||Database sizing and diagnostic utility|
|US6446118B1 (en)||2000-02-29||2002-09-03||Designtech International, Inc.||E-mail notification device|
|EP1132844A3 (en)||2000-03-02||2002-06-05||Telseon IP Services Inc.||E-commerce system facilitating service networks including broadband communication service networks|
|US6757708B1 (en)||2000-03-03||2004-06-29||International Business Machines Corporation||Caching dynamic content|
|US6757362B1 (en)||2000-03-06||2004-06-29||Avaya Technology Corp.||Personal virtual assistant|
|US20030223554A1 (en)||2001-03-06||2003-12-04||Zhang Jack K.||Communication systems and methods|
|FI108828B (en)||2000-03-14||2002-03-28||Sonera Oyj||Providing billing in a telecommunications system|
|US7634528B2 (en)||2000-03-16||2009-12-15||Microsoft Corporation||Harnessing information about the timing of a user's client-server interactions to enhance messaging and collaboration services|
|US7319847B2 (en)||2000-03-20||2008-01-15||Nielsen Mobile, Inc.||Bitwise monitoring of network performance|
|US6741855B1 (en)||2000-03-24||2004-05-25||Sun Microsystems, Inc.||Method and apparatus for remotely managing data via a mobile device|
|US6820088B1 (en)||2000-04-10||2004-11-16||Research In Motion Limited||System and method for synchronizing data records between multiple databases|
|US6221877B1 (en)||2000-04-12||2001-04-24||Regents Of The University Of California||Substituted 4-phthalimidocarboxanilides as inhibitors of purine salvage phosphoribosyltransferases|
|US6981041B2 (en)||2000-04-13||2005-12-27||Aep Networks, Inc.||Apparatus and accompanying methods for providing, through a centralized server site, an integrated virtual office environment, remotely accessible via a network-connected web browser, with remote network monitoring and management capabilities|
|US20020004746A1 (en)||2000-04-17||2002-01-10||Ferber John B.||E-coupon channel and method for delivery of e-coupons to wireless devices|
|US8898340B2 (en)||2000-04-17||2014-11-25||Circadence Corporation||Dynamic network link acceleration for network including wireless communication devices|
|JP2001306463A (en)||2000-04-20||2001-11-02||Matsushita Graphic Communication Systems Inc||Mail report device and portable telephone system|
|JP2002024020A (en)||2000-05-01||2002-01-25||Toshiba Corp||Screen control program, dynamic display information acquisition program, screen display transaction program, screen component interface program and screen program preparing method|
|WO2001084433A1 (en)||2000-05-01||2001-11-08||Mobliss, Inc.||System for conducting electronic surveys|
|AU9087401A (en)||2000-09-15||2002-03-26||Mobliss Inc||System for conducting user-specific promotional campaigns using multiple communications device platforms|
|US6662016B1 (en)||2000-05-05||2003-12-09||Openwave Systems, Inc.||Providing graphical location information for mobile resources using a data-enabled network|
|US6928481B1 (en)||2000-05-05||2005-08-09||International Business Machines Corporation||Method, apparatus and program to optimize the network distribution of digital information based on hierarchical grouping of server topology and code distribution|
|FI20001078A (en)||2000-05-08||2001-11-09||Nokia Corp||Shared application access to data services for wireless communication systems|
|US7725525B2 (en)||2000-05-09||2010-05-25||James Duncan Work||Method and apparatus for internet-based human network brokering|
|US7353274B1 (en)||2000-05-09||2008-04-01||Medisys/Rjb Consulting, Inc.||Method, apparatus, and system for determining whether a computer is within a particular location|
|US6868447B1 (en)||2000-05-09||2005-03-15||Sun Microsystems, Inc.||Mechanism and apparatus for returning results of services in a distributed computing environment|
|US6643650B1 (en)||2000-05-09||2003-11-04||Sun Microsystems, Inc.||Mechanism and apparatus for using messages to look up documents stored in spaces in a distributed computing environment|
|KR20010105705A (en)||2000-05-17||2001-11-29||정문술||Method for providing integrated user management environment to multi-internet service and system for the same|
|US6593944B1 (en)||2000-05-18||2003-07-15||Palm, Inc.||Displaying a web page on an electronic display device having a limited display area|
|GB0012195D0 (en)||2000-05-19||2000-07-12||Nokia Networks Oy||Location information services|
|US6671700B1 (en)||2000-05-23||2003-12-30||Palm Source, Inc.||Method and apparatus for parallel execution of conduits during simultaneous synchronization of databases|
|US6985933B1 (en)||2000-05-30||2006-01-10||International Business Machines Corporation||Method and system for increasing ease-of-use and bandwidth utilization in wireless devices|
|US6785868B1 (en)||2000-05-31||2004-08-31||Palm Source, Inc.||Method and apparatus for managing calendar information from a shared database and managing calendar information from multiple users|
|US6556217B1 (en)||2000-06-01||2003-04-29||Nokia Corporation||System and method for content adaptation and pagination based on terminal capabilities|
|US8489669B2 (en)||2000-06-07||2013-07-16||Apple Inc.||Mobile data processing system moving interest radius|
|US8060389B2 (en)||2000-06-07||2011-11-15||Apple Inc.||System and method for anonymous location based services|
|JP3526435B2 (en)||2000-06-08||2004-05-17||株式会社東芝||Network system|
|CN1197001C (en)||2000-06-12||2005-04-13||普里沃克斯(控股)有限公司||System for controlling display of user interface of software application|
|US7058691B1 (en)||2000-06-12||2006-06-06||Trustees Of Princeton University||System for wireless push and pull based services|
|JP2001356973A (en)||2000-06-13||2001-12-26||Century Systems Kk||Network system|
|US20020095391A1 (en)||2000-06-14||2002-07-18||Garret Swart||Methods and apparatus for providing variable price structures for time-based services available through a transaction system|
|US6732101B1 (en)||2000-06-15||2004-05-04||Zix Corporation||Secure message forwarding system detecting user's preferences including security preferences|
|MXPA02012364A (en)||2000-06-15||2004-04-02||Orion S Belt Inc||Method of and system for determining connections between parties over a network.|
|FI111899B (en)||2000-06-16||2003-09-30||Nokia Corp||Method for allocating billing in message delivery system, delivery system, server and terminal|
|US20020019812A1 (en)||2000-06-16||2002-02-14||Board Karen Eleanor||System and service for receiving, customizing, and re-broadcasting high-speed financial data to users operating wireless network-capable devices|
|AU6865201A (en)||2000-06-24||2002-01-08||Motorola Inc||A communication system that provides access queuing for communication services|
|US7024464B1 (en)||2000-06-29||2006-04-04||3Com Corporation||Dynamic content management for wireless communication systems|
|US6738808B1 (en)||2000-06-30||2004-05-18||Bell South Intellectual Property Corporation||Anonymous location service for wireless networks|
|FI110400B (en)||2000-07-03||2003-01-15||Nokia Corp||A method, terminal, and system for managing multiple mailboxes|
|US20020059457A1 (en)||2000-07-06||2002-05-16||Ballard Glenn Wesley||System and method for the remote creation of notification agents for wireless devices|
|AU6989101A (en)||2000-07-07||2002-01-21||Openwave Sys Inc||Graphical user interface features of a browser in a hand-held wireless communication device|
|GB0016835D0 (en)||2000-07-07||2000-08-30||Messagelabs Limited||Method of, and system for, processing email|
|WO2002005517A2 (en)||2000-07-10||2002-01-17||Viven Ltd.||Broadcast content over cellular telephones|
|US6941351B2 (en)||2000-07-11||2005-09-06||Microsoft Corporation||Application program caching|
|US7047202B2 (en)||2000-07-13||2006-05-16||Amit Jaipuria||Method and apparatus for optimizing networking potential using a secured system for an online community|
|US6621892B1 (en)||2000-07-14||2003-09-16||America Online, Inc.||System and method for converting electronic mail text to audio for telephonic delivery|
|US6968179B1 (en)||2000-07-27||2005-11-22||Microsoft Corporation||Place specific buddy list services|
|KR20010007743A (en)||2000-07-27||2001-02-05||이승열||WAP connecting method using guidecode inserted an advertisement|
|US6618717B1 (en)||2000-07-31||2003-09-09||Eliyon Technologies Corporation||Computer method and apparatus for determining content owner of a website|
|DE60103163T2 (en)||2000-08-02||2005-05-04||Aepona Ltd.||GATEWAY TO ACCESS NET RESOURCES|
|WO2002013077A2 (en)||2000-08-04||2002-02-14||Mobileaware Technologies Limited||An e-business mobility platform|
|US6944662B2 (en)||2000-08-04||2005-09-13||Vinestone Corporation||System and methods providing automatic distributed data retrieval, analysis and reporting services|
|JP2002057807A (en)||2000-08-08||2002-02-22||Nec Corp||Telephone directory management system for portable telephone|
|US6430602B1 (en)||2000-08-22||2002-08-06||Active Buddy, Inc.||Method and system for interactively responding to instant messaging requests|
|US7146404B2 (en)||2000-08-22||2006-12-05||Colloquis, Inc.||Method for performing authenticated access to a service on behalf of a user|
|TW512640B (en)||2000-08-25||2002-12-01||Phone Inc W||Mobile opinion polling system and method|
|US6754470B2 (en)||2000-09-01||2004-06-22||Telephia, Inc.||System and method for measuring wireless device and network usage and performance metrics|
|US6745011B1 (en)||2000-09-01||2004-06-01||Telephia, Inc.||System and method for measuring wireless device and network usage and performance metrics|
|EP1187481B1 (en)||2000-09-11||2008-04-02||Handmark Europe AB||A method for dynamic caching|
|JP3612271B2 (en)||2000-09-12||2005-01-19||株式会社東芝||File system|
|US6938079B1 (en)||2000-09-19||2005-08-30||3Com Corporation||System and method for automatically configuring a client device|
|AU9693201A (en)||2000-09-28||2002-04-08||Accessline Comm Corp||Communication management system for managing multiple incoming communications, such as from one graphical user interface|
|US6650890B1 (en)||2000-09-29||2003-11-18||Postini, Inc.||Value-added electronic messaging services and transparent implementation thereof using intermediate server|
|US7190976B2 (en)||2000-10-02||2007-03-13||Microsoft Corporation||Customizing the display of a mobile computing device|
|US6901437B1 (en)||2000-10-06||2005-05-31||Verizon Laboratories Inc.||Mobile cache for dynamically composing user-specific information|
|AU9677401A (en)||2000-10-09||2002-04-22||Enic Corp||Registering and using multilingual domain names|
|US20020161928A1 (en)||2000-10-10||2002-10-31||Awele Ndili||Smart agent for providing network content to wireless devices|
|US8321459B2 (en)||2000-10-11||2012-11-27||Peter Pekarek-Kostka||Method and system for facilitating access to always current contact information|
|US6785641B1 (en)||2000-10-11||2004-08-31||Smith International, Inc.||Simulating the dynamic response of a drilling tool assembly and its application to drilling tool assembly design optimization and drilling performance optimization|
|US20020042875A1 (en)||2000-10-11||2002-04-11||Jayant Shukla||Method and apparatus for end-to-end secure data communication|
|JP3851944B2 (en)||2000-10-17||2006-11-29||株式会社メキキ||Human network relationship registration system, human network relationship registration method and server, human network relationship registration program, and computer-readable recording medium recording the program|
|US6922721B1 (en)||2000-10-17||2005-07-26||The Phonepages Of Sweden Ab||Exchange of information in a communication system|
|US6804707B1 (en)||2000-10-20||2004-10-12||Eric Ronning||Method and system for delivering wireless messages and information to personal computing devices|
|US6990472B2 (en)||2000-10-23||2006-01-24||Starpound Corporation||Telecommunications initiated data fulfillment system|
|US20020156839A1 (en)||2000-10-26||2002-10-24||Scott Peterson||System for providing localized content information via wireless personal communication devices|
|US6901429B2 (en)||2000-10-27||2005-05-31||Eric Morgan Dowling||Negotiated wireless peripheral security systems|
|US20020133504A1 (en)||2000-10-27||2002-09-19||Harry Vlahos||Integrating heterogeneous data and tools|
|US6847892B2 (en)||2001-10-29||2005-01-25||Digital Angel Corporation||System for localizing and sensing objects and providing alerts|
|US7127492B1 (en)||2000-10-31||2006-10-24||International Business Machines Corporation||Method and apparatus for distributed application acceleration|
|US7117262B2 (en)||2000-11-01||2006-10-03||Inktomi Corporation||Cooperative management of distributed network caches|
|US20020087883A1 (en)||2000-11-06||2002-07-04||Curt Wohlgemuth||Anti-piracy system for remotely served computer applications|
|US7870196B2 (en)||2000-11-08||2011-01-11||Nokia Corporation||System and methods for using an application layer control protocol transporting spatial location information pertaining to devices connected to wired and wireless internet protocol networks|
|US6918091B2 (en)||2000-11-09||2005-07-12||Change Tools, Inc.||User definable interface system, method and computer program product|
|US20020146129A1 (en)||2000-11-09||2002-10-10||Kaplan Ari D.||Method and system for secure wireless database management|
|US20020120779A1 (en)||2000-11-14||2002-08-29||Douglas Teeple||Mediation software for delivery of interactive mobile messaging and personalized content to mobile devices|
|US20030054810A1 (en)||2000-11-15||2003-03-20||Chen Yih-Farn Robin||Enterprise mobile server platform|
|US6986061B1 (en)||2000-11-20||2006-01-10||International Business Machines Corporation||Integrated system for network layer security and fine-grained identity-based access control|
|FI114364B (en)||2000-11-22||2004-09-30||Nokia Corp||Data transfer|
|US20080301231A1 (en)||2001-11-28||2008-12-04||Samir Narendra Mehta||Method and System for Maintaining and Distributing Wireless Applications|
|US7039391B2 (en)||2000-11-28||2006-05-02||Xanboo, Inc.||Method and system for communicating with a wireless device|
|US6766165B2 (en)||2000-12-05||2004-07-20||Nortel Networks Limited||Method and system for remote and local mobile network management|
|US7260590B1 (en)||2000-12-06||2007-08-21||Cisco Technology, Inc.||Streamed database archival process with background synchronization|
|US6976075B2 (en)||2000-12-08||2005-12-13||Clarinet Systems, Inc.||System uses communication interface for configuring a simplified single header packet received from a PDA into multiple headers packet before transmitting to destination device|
|US7596791B2 (en)||2000-12-19||2009-09-29||Emc Corporation||Methods and techniques for delivering rich Java applications over thin-wire connections with high performance and scalability|
|US7085555B2 (en)||2000-12-19||2006-08-01||Bellsouth Intellectual Property Corporation||Location blocking service from a web advertiser|
|US6944679B2 (en)||2000-12-22||2005-09-13||Microsoft Corp.||Context-aware systems and methods, location-aware systems and methods, context-aware vehicles and methods of operating the same, and location-aware vehicles and methods of operating the same|
|FI110560B (en)||2000-12-27||2003-02-14||Nokia Corp||Grouping of wireless communication terminals|
|JP2002215582A (en)||2000-12-28||2002-08-02||Morgan Stanley Dean Witter Japan Ltd||Method and device for authentication|
|US7310350B1 (en)||2000-12-29||2007-12-18||Oracle International Corporation||Mobile surveys and polling|
|US20020087679A1 (en)||2001-01-04||2002-07-04||Visual Insights||Systems and methods for monitoring website activity in real time|
|US6931529B2 (en)||2001-01-05||2005-08-16||International Business Machines Corporation||Establishing consistent, end-to-end protection for a user datagram|
|US7257639B1 (en)||2001-01-19||2007-08-14||Microsoft Corporation||Enhanced email—distributed attachment storage|
|US6871236B2 (en)||2001-01-26||2005-03-22||Microsoft Corporation||Caching transformed content in a mobile gateway|
|US6845153B2 (en)||2001-01-31||2005-01-18||Telefonaktiebolaget Lm Ericsson (Publ)||Network independent party addressing using a unique identifier linked to network specific addresses|
|US7627658B2 (en)||2001-02-12||2009-12-01||Integra Sp Limited||Presentation service which enables client device to run a network based application|
|US7013350B2 (en)||2001-02-16||2006-03-14||Microsoft Corporation||System setting flags based on address types in destination address field of a message to indicate different transports to deliver the message|
|US7225259B2 (en)||2001-02-21||2007-05-29||Nokia Inc.||Service tunnel over a connectionless network|
|WO2002071287A2 (en)||2001-02-23||2002-09-12||Mobilitec Inc.||System and method for charging for directed provisioning of user applications on limited-resource devices|
|US7085824B2 (en)||2001-02-23||2006-08-01||Power Measurement Ltd.||Systems for in the field configuration of intelligent electronic devices|
|US6463382B1 (en)||2001-02-26||2002-10-08||Motorola, Inc.||Method of optimizing traffic content|
|JP3782671B2 (en)||2001-02-28||2006-06-07||株式会社エヌ・ティ・ティ・ドコモ||Link manager and link management method|
|US6985983B2 (en)||2001-03-01||2006-01-10||Hewlett-Packard Development Company, L.P.||Translating device adapter having a common command set for interfacing multiple types of redundant storage devices to a host processor|
|US20030023975A1 (en)||2001-03-02||2003-01-30||Microsoft Corporation||Enhanced music services for television|
|US6636482B2 (en)||2001-03-08||2003-10-21||Arris International, Inc.||Method and apparatus for controlling traffic loading of different service levels in a cable data system|
|JP2002271400A (en)||2001-03-09||2002-09-20||Matsushita Electric Ind Co Ltd||Method of data transmission|
|US20030125023A1 (en)||2001-03-15||2003-07-03||Eyal Fishler||Method and system for providing a wireless terminal communication session integrated with data and voice services|
|US7233795B1 (en)||2001-03-19||2007-06-19||Ryden Michael V||Location based communications system|
|US7242680B2 (en)||2001-03-20||2007-07-10||Verizon Business Global Llc||Selective feature blocking in a communications network|
|US7043637B2 (en)||2001-03-21||2006-05-09||Microsoft Corporation||On-disk file format for a serverless distributed file system|
|US6847974B2 (en)||2001-03-26||2005-01-25||Us Search.Com Inc||Method and apparatus for intelligent data assimilation|
|US6707801B2 (en)||2001-03-28||2004-03-16||Qualcomm Incorporated||Method and apparatus for data transport in a wireless communication system|
|US7185362B2 (en)||2001-08-20||2007-02-27||Qualcomm, Incorporated||Method and apparatus for security in a data processing system|
|US20020144109A1 (en)||2001-03-29||2002-10-03||International Business Machines Corporation||Method and system for facilitating public key credentials acquisition|
|US6993326B2 (en)||2001-04-02||2006-01-31||Bellsouth Intellectual Property Corporation||System and method for providing short message targeted advertisements over a wireless communications network|
|FI20010761A (en)||2001-04-11||2002-10-12||Suomen Posti Oyj||Method, system and device for voting|
|EP1378105B1 (en)||2001-04-12||2008-05-21||Research In Motion Limited||System and method for dynamically pushing information on wireless data communication devices|
|US7770223B2 (en)||2001-04-12||2010-08-03||Computer Associates Think, Inc.||Method and apparatus for security management via vicarious network devices|
|US7398271B1 (en)||2001-04-16||2008-07-08||Yahoo! Inc.||Using network traffic logs for search enhancement|
|US6954754B2 (en)||2001-04-16||2005-10-11||Innopath Software, Inc.||Apparatus and methods for managing caches on a mobile device|
|US7921290B2 (en)||2001-04-18||2011-04-05||Ipass Inc.||Method and system for securely authenticating network access credentials for users|
|US6987734B2 (en)||2001-04-20||2006-01-17||Clear Channel Wireless, Inc.||Provision of digital data via multiple broadcasts|
|US6981062B2 (en)||2001-04-20||2005-12-27||Sbc Technology Resources, Inc.||World wide web content synchronization between wireless devices|
|US20020174189A1 (en)||2001-04-23||2002-11-21||Luosheng Peng||Apparatus and methods for intelligently caching applications and data on a mobile device|
|US6885388B2 (en)||2001-04-25||2005-04-26||Probaris Technologies Inc.||Method for automatically generating list of meeting participants and delegation permission|
|US6839564B2 (en)||2001-04-25||2005-01-04||Nokia Corporation||Synchronization of database data|
|US7437295B2 (en)||2001-04-27||2008-10-14||Accenture Llp||Natural language processing for a location-based services system|
|US7698228B2 (en)||2001-04-27||2010-04-13||Accenture Llp||Tracking purchases in a location-based services system|
|US6944447B2 (en)||2001-04-27||2005-09-13||Accenture Llp||Location-based services|
|EP1391105A4 (en)||2001-04-30||2005-07-06||Polycom Inc||Audio conferencing system and method|
|AUPR464601A0 (en)||2001-04-30||2001-05-24||Commonwealth Of Australia, The||Shapes vector|
|US7430609B2 (en)||2001-04-30||2008-09-30||Aol Llc, A Delaware Limited Liability Company||Managing access to streams hosted on duplicating switches|
|US20020158908A1 (en)||2001-04-30||2002-10-31||Kristian Vaajala||Web browser user interface for low-resolution displays|
|US7088821B2 (en)||2001-05-03||2006-08-08||Cheman Shaik||Absolute public key cryptographic system and method surviving private-key compromise with other advantages|
|TW550961B (en)||2001-05-03||2003-09-01||Far Eastone Telecomm Co Ltd||Mobile phone Internet access utilizing short message services apparatus and method|
|JP2002335518A (en)||2001-05-09||2002-11-22||Fujitsu Ltd||Control unit for controlling display, server and program|
|AT350868T (en)||2001-05-10||2007-01-15||Nortel Networks Ltd||SYSTEM AND METHOD FOR TRANSMITTING COMMUNICATION BETWEEN MOBILE TELECOMMUNICATIONS NETWORKS USING DIFFERENT RADIO ACCESS TECHNOLOGIES|
|FI112906B (en)||2001-05-10||2004-01-30||Nokia Corp||Method and apparatus for forming a communication group|
|EP1388107A1 (en)||2001-05-11||2004-02-11||Swisscom Mobile AG||Method for transmitting an anonymous request from a consumer to a content or service provider through a telecommunication network|
|US7433922B2 (en)||2001-05-11||2008-10-07||Varia Llc||Method and system for collecting and displaying aggregate presence information for mobile media players|
|US20030051142A1 (en)||2001-05-16||2003-03-13||Hidalgo Lluis Mora||Firewalls for providing security in HTTP networks and applications|
|US20030182420A1 (en)||2001-05-21||2003-09-25||Kent Jones||Method, system and apparatus for monitoring and controlling internet site content access|
|US20040024892A1 (en)||2001-05-21||2004-02-05||Creswell Carroll W.||System for providing sequenced communications within a group|
|US7024491B1 (en)||2001-05-23||2006-04-04||Western Digital Ventures, Inc.||Remotely synchronizing a mobile terminal by adapting ordering and filtering synchronization rules based on a user's operation of the mobile terminal|
|KR100417407B1 (en)||2001-05-25||2004-02-05||엘지전자 주식회사||Power saving method of mobile communication terminal|
|US7130839B2 (en)||2001-05-29||2006-10-31||Sun Microsystems, Inc.||Method and system for grouping entries in a directory server by group memberships defined by roles|
|US7206806B2 (en)||2001-05-30||2007-04-17||Pineau Richard A||Method and system for remote utilizing a mobile device to share data objects|
|EP1402692A4 (en)||2001-06-04||2005-06-15||Nct Group Inc||System and method for increasing the effective bandwidth of a communications network|
|US7827055B1 (en)||2001-06-07||2010-11-02||Amazon.Com, Inc.||Identifying and providing targeted content to users having common interests|
|US7155710B2 (en)||2001-06-08||2006-12-26||Igt||Method and apparatus for gaming device software configuration|
|US7296155B1 (en)||2001-06-08||2007-11-13||Cisco Technology, Inc.||Process and system providing internet protocol security without secure domain resolution|
|US6957397B1 (en)||2001-06-11||2005-10-18||Palm, Inc.||Navigating through a menu of a handheld computer using a keyboard|
|KR100565916B1 (en)||2001-06-12||2006-03-30||리서치 인 모션 리미티드||System and method for compressing secure e-mail for exchange with a mobile data communication device|
|US20020193094A1 (en)||2001-06-15||2002-12-19||Lawless John P.||Method and system for downloading software products directly to wireless phones|
|US7120928B2 (en)||2001-06-15||2006-10-10||Dinesh Sheth||Secure selective sharing of account information on an internet information aggregation system|
|US6671695B2 (en)||2001-06-18||2003-12-30||The Procter & Gamble Company||Dynamic group generation and management|
|US6947770B2 (en)||2001-06-22||2005-09-20||Ericsson, Inc.||Convenient dialing of names and numbers from a phone without alpha keypad|
|WO2003003756A2 (en)||2001-06-27||2003-01-09||Flarion Technologies, Inc.||Methods and apparatus for supporting group communications|
|US7409423B2 (en)||2001-06-28||2008-08-05||Horvitz Eric J||Methods for and applications of learning and inferring the periods of time until people are available or unavailable for different forms of communication, collaboration, and information access|
|AT464753T (en)||2001-06-29||2010-04-15||Motorola Inc||Process for updating a list of members of a participant group|
|US7219139B2 (en)||2001-06-29||2007-05-15||Claria Corporation||System and method for using continuous messaging units in a network architecture|
|US6798358B2 (en)||2001-07-03||2004-09-28||Nortel Networks Limited||Location-based content delivery|
|US7305492B2 (en)||2001-07-06||2007-12-04||Juniper Networks, Inc.||Content service aggregation system|
|US20040205248A1 (en)||2001-07-10||2004-10-14||Herbert A Little||System and method for secure message key caching in a mobile communication device|
|US7076244B2 (en)||2001-07-23||2006-07-11||Research In Motion Limited||System and method for pushing information to a mobile device|
|US20030153338A1 (en)||2001-07-24||2003-08-14||Herz Frederick S. M.||Autoband|
|US20030046433A1 (en)||2001-07-25||2003-03-06||Omer Luzzatti||Method to synchronize information between online devices|
|JP2003046576A (en)||2001-07-27||2003-02-14||Fujitsu Ltd||Message delivery system, message delivery management server, message distribution management program, and computer-readable recording medium with the program recorded thereon|
|US7809364B2 (en)||2001-07-30||2010-10-05||Nokia Mobile Phones Limited||Apparatus, and associated method, for providing an operation parameter to a mobile station of a radio communication station|
|US20030028430A1 (en)||2001-08-01||2003-02-06||Zimmerman Stephen M.||System, computer product and method for providing billboards with pull technology|
|US20030028441A1 (en)||2001-08-02||2003-02-06||International Business Machines Corporation||Answer fulfillment-based marketing|
|US7962622B2 (en)||2001-08-07||2011-06-14||Motorola Mobility, Inc.||System and method for providing provisioning and upgrade services for a wireless device|
|US7743119B2 (en)||2001-08-07||2010-06-22||Motorola, Inc.||System and method for mapping identification codes|
|EP1283648A1 (en)||2001-08-07||2003-02-12||Siemens Aktiengesellschaft||Method, Terminal and radiocommunications system for transmission of group messages|
|US7596565B2 (en)||2001-08-07||2009-09-29||Good Technology||System and method for maintaining wireless file folders at a wireless device|
|WO2003015356A1 (en)||2001-08-08||2003-02-20||Fujitsu Limited||Server, mobile communication terminal, radio device, communication method for communication system, and communication system|
|US7389412B2 (en)||2001-08-10||2008-06-17||Interactive Technology Limited Of Hk||System and method for secure network roaming|
|US7133862B2 (en)||2001-08-13||2006-11-07||Xerox Corporation||System with user directed enrichment and import/export control|
|US6996393B2 (en)||2001-08-31||2006-02-07||Nokia Corporation||Mobile content delivery system|
|US20030046586A1 (en)||2001-09-05||2003-03-06||Satyam Bheemarasetti||Secure remote access to data between peers|
|US20030046587A1 (en)||2001-09-05||2003-03-06||Satyam Bheemarasetti||Secure remote access using enterprise peer networks|
|US8713107B2 (en)||2001-09-06||2014-04-29||J. Albert Avila||Method and system for remote delivery of email|
|US7567575B2 (en)||2001-09-07||2009-07-28||At&T Corp.||Personalized multimedia services using a mobile service platform|
|US20030050041A1 (en)||2001-09-07||2003-03-13||Robert Wu||Network system for providing prepaid wireless remote access service|
|CA2356823C (en)||2001-09-10||2010-05-11||Research In Motion Limited||System and method for real time self-provisioning for a mobile communication device|
|US20030063120A1 (en)||2001-09-28||2003-04-03||Wong Hoi Lee Candy||Scalable graphical user interface architecture|
|US7392483B2 (en)||2001-09-28||2008-06-24||Ntt Docomo, Inc,||Transformation of platform specific graphical user interface widgets migrated between heterogeneous device platforms|
|US7234111B2 (en)||2001-09-28||2007-06-19||Ntt Docomo, Inc.||Dynamic adaptation of GUI presentations to heterogeneous device platforms|
|US20030065802A1 (en)||2001-09-28||2003-04-03||Nokia Corporation||System and method for dynamically producing a multimedia content sample for mobile terminal preview|
|US20030065738A1 (en)||2001-10-01||2003-04-03||Thumb Logic, Inc.||Wireless information systems and methods|
|US20030065739A1 (en)||2001-10-01||2003-04-03||J. Mitchell Shnier||Methods for independently generating a reference to desired information available from a remote source|
|US20030084165A1 (en)||2001-10-12||2003-05-01||Openwave Systems Inc.||User-centric session management for client-server interaction using multiple applications and devices|
|US20030072451A1 (en)||2001-10-16||2003-04-17||Pimentel Roberto J.||Method and apparatus for securely transferring wireless data|
|US7007107B1 (en)||2001-10-22||2006-02-28||United Electronic Industries||Methods and apparatus for performing data acquisition and control|
|WO2003036520A1 (en)||2001-10-23||2003-05-01||Visto Corporation||System and method for merging remote and local data in a single user interface|
|US6993327B2 (en)||2001-10-29||2006-01-31||Motorola, Inc.||Multicast distribution of presence information for an instant messaging system|
|US6892070B2 (en)||2001-11-05||2005-05-10||Unnikrishnan S. Warrier||Communication system and method for minimizing international roaming costs|
|US7127477B2 (en)||2001-11-06||2006-10-24||Everyware Solutions Inc.||Method and system for access to automatically synchronized remote files|
|US20030088629A1 (en)||2001-11-08||2003-05-08||Martin Berkowitz||Email management system and method|
|US7028183B2 (en)||2001-11-13||2006-04-11||Symantec Corporation||Enabling secure communication in a clustered or distributed architecture|
|US20040103147A1 (en)||2001-11-13||2004-05-27||Flesher Kevin E.||System for enabling collaboration and protecting sensitive data|
|AU2002357731A1 (en)||2001-11-15||2003-06-10||Visto Corporation||System and methods for asychronous synchronization|
|EP1313244B1 (en)||2001-11-16||2016-11-02||Google, Inc.||Communication device and method for communicating over a digital mobile network|
|US7373362B2 (en)||2001-11-19||2008-05-13||Extended Systems, Inc.||Coordinated synchronization|
|US7917394B2 (en)||2001-11-19||2011-03-29||Csg Systems, Inc.||System and method for providing access to network services|
|US6885874B2 (en)||2001-11-27||2005-04-26||Motorola, Inc.||Group location and route sharing system for communication units in a trunked communication system|
|US20030105837A1 (en)||2001-11-30||2003-06-05||Yury Kamen||Interception for optimal caching of distributed applications|
|WO2003048945A1 (en)||2001-12-05||2003-06-12||Cybird Co., Ltd.||Communication information sharing system, communication information sharing method, communication information sharing program|
|WO2003050743A1 (en)||2001-12-06||2003-06-19||Access Co., Ltd.||System and method for providing subscription content services to mobile devices|
|WO2003049357A2 (en)||2001-12-07||2003-06-12||Telefonaktiebolaget Lm Ericsson (Publ)||Lawful interception of end-to-end encrypted data traffic|
|AT424593T (en)||2001-12-12||2009-03-15||Scytl Secure Electronic Voting||Process for safe electronic choosing and cryptographic protocols and computer programs therefor|
|US7149780B2 (en)||2001-12-14||2006-12-12||Pitney Bowes Inc.||Method for determining e-mail address format rules|
|US7062024B2 (en)||2001-12-19||2006-06-13||Ameritech Communications, Inc.||Telecommunication services reporting system|
|US7313766B2 (en)||2001-12-20||2007-12-25||Nokia Corporation||Method, system and apparatus for constructing fully personalized and contextualized user interfaces for terminals in mobile use|
|EP1466261B1 (en)||2002-01-08||2018-03-07||Seven Networks, LLC||Connection architecture for a mobile network|
|EP1469694A4 (en)||2002-01-17||2006-12-13||Fujitsu Ltd||Mobile networ system|
|US7219222B1 (en)||2002-01-18||2007-05-15||Ge Medical Technology Services, Inc.||Method and system to grant access to software options resident on a medical imaging device|
|US6972682B2 (en)||2002-01-18||2005-12-06||Georgia Tech Research Corporation||Monitoring and tracking of assets by utilizing wireless communications|
|US6741232B1 (en)||2002-01-23||2004-05-25||Good Technology, Inc.||User interface for a data processing apparatus|
|US7996517B2 (en)||2002-01-23||2011-08-09||Novell, Inc.||Transparent network connection takeover|
|US6907501B2 (en)||2002-01-25||2005-06-14||Ntt Docomo Inc.||System for management of cacheable streaming content in a packet based communication network with mobile hosts|
|US20030154212A1 (en)||2002-01-28||2003-08-14||International Business Machines Corporation||Method and apparatus for determining attributes among objects|
|GB0202370D0 (en)||2002-02-01||2002-03-20||Symbian Ltd||Pinging|
|US7257776B2 (en)||2002-02-05||2007-08-14||Microsoft Corporation||Systems and methods for scaling a graphical user interface according to display dimensions and using a tiered sizing schema to define display objects|
|US7711854B2 (en)||2002-02-07||2010-05-04||Accenture Global Services Gmbh||Retrieving documents over a network with a wireless communication device|
|US7007242B2 (en)||2002-02-20||2006-02-28||Nokia Corporation||Graphical user interface for a mobile device|
|US6910159B2 (en)||2002-02-20||2005-06-21||Microsoft Corporation||System and method for gathering and automatically processing user and debug data for mobile devices|
|US7240095B1 (en)||2002-02-22||2007-07-03||Bellsouth Intellectual Property Corporation||Electronic mail notification|
|FR2837042B1 (en)||2002-03-05||2005-04-08||Cegetel Groupe||METHOD FOR OPTIMIZING NETWORK TRAFFIC AND DEVICE FOR IMPLEMENTING SAID METHOD|
|US6775362B1 (en)||2002-03-06||2004-08-10||Alcatel||Graphical telephone system|
|GB0205130D0 (en)||2002-03-06||2002-04-17||Symbian Ltd||A method of enabling a wireless information device to access data services|
|JP4366040B2 (en)||2002-03-07||2009-11-18||インターナショナル・ビジネス・マシーンズ・コーポレーション||Network service system, server and program|
|US6806883B2 (en)||2002-03-11||2004-10-19||Sun Microsystems, Inc.||System and method for handling display device requests for display data from a frame buffer|
|DE60334529D1 (en)||2002-03-11||2010-11-25||Research In Motion Ltd||SYSTEM AND METHOD FOR MOVING DATA TO A MOBILE DEVICE|
|US7257391B2 (en)||2002-03-26||2007-08-14||Zoove Corp.||Wireless data system|
|US8516114B2 (en)||2002-03-29||2013-08-20||International Business Machines Corporation||Method and apparatus for content pre-fetching and preparation|
|US20040078814A1 (en)||2002-03-29||2004-04-22||Digeo, Inc.||Module-based interactive television ticker|
|US7184790B2 (en)||2002-04-02||2007-02-27||Dorenbosch Jheroen P||Method and apparatus for establishing a talk group|
|US9137324B2 (en)||2002-04-10||2015-09-15||International Business Machines Corporation||Capacity on-demand in distributed computing environments|
|US7272122B2 (en)||2002-04-26||2007-09-18||Nokia Corporation||Relocation of application-specific functionality during seamless network layer-level handoffs|
|US20030204602A1 (en)||2002-04-26||2003-10-30||Hudson Michael D.||Mediated multi-source peer content delivery network architecture|
|US7016978B2 (en)||2002-04-29||2006-03-21||Bellsouth Intellectual Property Corporation||Instant messaging architecture and system for interoperability and presence management|
|US7376701B2 (en)||2002-04-29||2008-05-20||Cisco Technology, Inc.||System and methodology for control of, and access and response to internet email from a wireless device|
|US7818365B2 (en)||2002-05-01||2010-10-19||Sybase, Inc.||System, method, and computer program product for online and offline interactive applications on mobile devices|
|US20030208529A1 (en)||2002-05-03||2003-11-06||Sreenath Pendyala||System for and method of real-time remote access and manipulation of data|
|US7395329B1 (en)||2002-05-13||2008-07-01||At&T Delaware Intellectual Property., Inc.||Real-time notification of presence availability changes|
|US20050234860A1 (en)||2002-08-30||2005-10-20||Navio Systems, Inc.||User agent for facilitating transactions in networks|
|US20050038707A1 (en)||2002-08-30||2005-02-17||Navio Systems, Inc.||Methods and apparatus for enabling transactions in networks|
|US20050038724A1 (en)||2002-08-30||2005-02-17||Navio Systems, Inc.||Methods and apparatus for enabling transaction relating to digital assets|
|US20030217142A1 (en)||2002-05-15||2003-11-20||Microsoft Corporation||Method and system for supporting the communication of presence information regarding one or more telephony devices|
|US20030217098A1 (en)||2002-05-15||2003-11-20||Microsoft Corporation||Method and system for supporting the communication of presence information regarding one or more telephony devices|
|KR100871118B1 (en)||2002-05-18||2008-11-28||엘지전자 주식회사||Management method for multicast group|
|GB0211736D0 (en)||2002-05-21||2002-07-03||Commtag Ltd||Data communications systems|
|JP2005535947A (en)||2002-05-31||2005-11-24||インターナショナル・ビジネス・マシーンズ・コーポレーション||System and method for accessing different types of back-end data stores|
|US20030227487A1 (en)||2002-06-01||2003-12-11||Hugh Harlan M.||Method and apparatus for creating and accessing associative data structures under a shared model of categories, rules, triggers and data relationship permissions|
|US7016909B2 (en)||2002-06-04||2006-03-21||Microsoft Corporation||Method and system for expansion of recurring calendar events|
|AU2003259388A1 (en)||2002-06-07||2003-12-22||Koninklijke Philips Electronics N.V.||Wireless technology co-existence|
|US6867965B2 (en)||2002-06-10||2005-03-15||Soon Huat Khoo||Compound portable computing device with dual portion keyboard coupled over a wireless link|
|US6966058B2 (en)||2002-06-12||2005-11-15||Agami Systems, Inc.||System and method for managing software upgrades in a distributed computing system|
|US7343396B2 (en)||2002-06-20||2008-03-11||Fineground Networks||Precomputation of web documents|
|US7353394B2 (en)||2002-06-20||2008-04-01||International Business Machine Corporation||System and method for digital signature authentication of SMS messages|
|US7933945B2 (en)||2002-06-27||2011-04-26||Openpeak Inc.||Method, system, and computer program product for managing controlled residential or non-residential environments|
|US7096030B2 (en)||2002-06-28||2006-08-22||Nokia Corporation||System and method for initiating location-dependent applications on mobile devices|
|US7614059B2 (en)||2002-07-11||2009-11-03||Topia Technology||System and method for the discovery and usage of local resources by a mobile agent object|
|US8924484B2 (en)||2002-07-16||2014-12-30||Sonicwall, Inc.||Active e-mail filter with challenge-response|
|US6941310B2 (en)||2002-07-17||2005-09-06||Oracle International Corp.||System and method for caching data for a mobile application|
|US7085787B2 (en)||2002-07-19||2006-08-01||International Business Machines Corporation||Capturing data changes utilizing data-space tracking|
|US7383339B1 (en)||2002-07-31||2008-06-03||Aol Llc, A Delaware Limited Liability Company||Local proxy server for establishing device controls|
|US7124320B1 (en)||2002-08-06||2006-10-17||Novell, Inc.||Cluster failover via distributed configuration repository|
|US20040027378A1 (en)||2002-08-06||2004-02-12||Hays Grace L.||Creation of user interfaces for multiple devices|
|US20040027326A1 (en)||2002-08-06||2004-02-12||Grace Hays||System for and method of developing a common user interface for mobile applications|
|US7349871B2 (en)||2002-08-08||2008-03-25||Fujitsu Limited||Methods for purchasing of goods and services|
|US6968175B2 (en)||2002-08-13||2005-11-22||Nokia Corporation||Method and system for sharing transmission revenue between mobile operators and content providers|
|CN1221898C (en)||2002-08-13||2005-10-05||国际商业机器公司||System and method for updating network proxy cache server object|
|CN1689300B (en)||2002-08-16||2010-04-28||捷讯研究有限公司||System and method for triggering a provisioning event|
|AU2003270139A1 (en)||2002-08-30||2004-03-19||Koninklijke Kpn N.V.||Method and system for the phased retrieval of data|
|US20040047356A1 (en)||2002-09-06||2004-03-11||Bauer Blaine D.||Network traffic monitoring|
|US6756882B2 (en)||2002-09-09||2004-06-29||Motorola, Inc.||Method and controller for providing a location-based game associated with a plurality of mobile stations|
|US20080313282A1 (en)||2002-09-10||2008-12-18||Warila Bruce W||User interface, operating system and architecture|
|US7209137B2 (en)||2002-09-12||2007-04-24||International Business Machines Corporation||Efficient triangular shaped meshes|
|US10373420B2 (en)||2002-09-16||2019-08-06||Touchtunes Music Corporation||Digital downloading jukebox with enhanced communication features|
|KR100486713B1 (en)||2002-09-17||2005-05-03||삼성전자주식회사||Apparatus and method for streaming multimedia data|
|US20060190984A1 (en)||2002-09-23||2006-08-24||Credant Technologies, Inc.||Gatekeeper architecture/features to support security policy maintenance and distribution|
|US20040064445A1 (en)||2002-09-30||2004-04-01||Pfleging Gerald W.||Wireless access to a database by a short message system query|
|US7051053B2 (en)||2002-09-30||2006-05-23||Dinesh Sinha||Method of lazily replicating files and monitoring log in backup file system|
|US7231220B2 (en)||2002-10-01||2007-06-12||Interdigital Technology Corporation||Location based method and system for wireless mobile unit communication|
|US7366981B2 (en)||2002-10-04||2008-04-29||Fuji Xerox Co., Ltd.||Image forming device and method|
|CN1489332A (en)||2002-10-10||2004-04-14||国际商业机器公司||Safety system and method for providing service device of identifying long-distance callin user's service-charge|
|KR100485974B1 (en)||2002-10-10||2005-05-03||엔에이치엔(주)||Method and System for Providing Contents|
|US20040073476A1 (en)||2002-10-10||2004-04-15||Prolink Services Llc||Method and system for identifying key opinion leaders|
|BR0304946A (en)||2002-10-16||2004-08-31||Xerox Corp||Method and apparatus for enabling distributed subscription services, automated supply maintenance implementation of device independent service, including device model agent, add-on component, method and apparatus for low-cost side device embedded platform, distributed service enablement, and platform server interface for standalone provision of device services|
|US20040075675A1 (en)||2002-10-17||2004-04-22||Tommi Raivisto||Apparatus and method for accessing services via a mobile terminal|
|CA2503343A1 (en)||2002-10-22||2004-05-06||Unho Choi||Integrated emergency response system in information infrastructure and operating method therefor|
|US6999092B2 (en)||2002-10-25||2006-02-14||Fujitsu Limited||Image display apparatus in which a specific area display attribute is modifiable|
|SE0203188D0 (en)||2002-10-29||2002-10-29||Ericsson Telefon Ab L M||Automatic provisioning including MMS greeting|
|CA2504800C (en)||2002-11-04||2011-09-20||Research In Motion Limited||Method and system for maintaining a wireless data connection|
|US7809384B2 (en)||2002-11-05||2010-10-05||Microsoft Corporation||User-input scheduling of synchronization operation on a mobile device based on user activity|
|US7269433B2 (en)||2002-11-05||2007-09-11||Microsoft Corporation||Scheduling of synchronization operation on a mobile device based on predetermined subset of user actions|
|US7263086B2 (en)||2002-11-12||2007-08-28||Nokia Corporation||Method and system for providing location-based services in multiple coverage area environments|
|GB0226596D0 (en)||2002-11-14||2002-12-24||Commtag Ltd||Data communication systems|
|EP1565830A4 (en)||2002-11-18||2008-03-12||America Online Inc||People lists|
|US20040095913A1 (en)||2002-11-20||2004-05-20||Nokia, Inc.||Routing optimization proxy in IP networks|
|EP1422899B1 (en)||2002-11-25||2007-08-08||T-Mobile Deutschland GmbH||Method and system for providing easy access to an e-mail account via a mobile communication network|
|US6867774B1 (en)||2002-12-02||2005-03-15||Ngrain (Canada) Corporation||Method and apparatus for transforming polygon data to voxel data for general purpose applications|
|US20040107319A1 (en)||2002-12-03||2004-06-03||D'orto David M.||Cache management system and method|
|US6912562B1 (en)||2002-12-04||2005-06-28||At&T Corp.||Cache invalidation technique with spurious resource change indications|
|US7797064B2 (en)||2002-12-13||2010-09-14||Stephen Loomis||Apparatus and method for skipping songs without delay|
|US7526800B2 (en)||2003-02-28||2009-04-28||Novell, Inc.||Administration of protection of data accessible by a mobile device|
|US7308689B2 (en)||2002-12-18||2007-12-11||International Business Machines Corporation||Method, apparatus, and program for associating related heterogeneous events in an event handler|
|US7043264B2 (en)||2002-12-18||2006-05-09||America Online, Inc.||Message transmission system in a GPRS environment|
|DE10259755A1 (en)||2002-12-19||2004-07-08||Bt Ingnite Gmbh & Co||Automatic terminal or user identification in networks|
|US7130424B2 (en)||2002-12-19||2006-10-31||Qualcomm, Inc.||Systems and methods for utilizing an application from a native portable device within a non-native communications network|
|US7925717B2 (en)||2002-12-20||2011-04-12||Avaya Inc.||Secure interaction between a mobile client device and an enterprise application in a communication system|
|US7614052B2 (en)||2004-01-09||2009-11-03||Nexaweb Technologies Inc.||System and method for developing and deploying computer applications over a network|
|US7272830B2 (en)||2003-01-16||2007-09-18||Sun Microsystems, Inc.||Ordering program data for loading on a device|
|US7752301B1 (en)||2003-01-23||2010-07-06||Gomez Acquisition Corporation||System and interface for monitoring information technology assets|
|US20040176128A1 (en)||2003-01-30||2004-09-09||3Com Corporation||System, mobile communications unit, and softswitch method and apparatus for establishing an Internet Protocol communication link|
|US7210121B2 (en)||2003-02-07||2007-04-24||Sun Microsystems, Inc.||Method and system for generating first class citizen application implementing native software application wrapper|
|US7725542B2 (en)||2003-02-10||2010-05-25||At&T Intellectual Property I, L.P.||Forwarding IM messages to E-mail|
|US20040162890A1 (en)||2003-02-18||2004-08-19||Yasutoshi Ohta||Imaging apparatus help system|
|AU2003900772A0 (en)||2003-02-21||2003-03-13||Canon Kabushiki Kaisha||Reducing the number of compositing operations performed in a pixel sequential rendering system|
|US20040167966A1 (en)||2003-02-21||2004-08-26||Simon Lee||Method and system for directing communications in a communications network|
|FR2851710B1 (en)||2003-02-25||2005-06-24||Cit Alcatel||METHOD FOR MAKING A MOBILE USER PASSING FROM A PUBLIC TELECOMMUNICATION NETWORK TO ANOTHER RECEIVE CALLS VIA THE NETWORK MOST SUITABLE FOR ITS LOCATION; AND DEVICES FOR IMPLEMENTING SAID METHOD|
|GB2398968B (en)||2003-02-27||2005-07-27||Motorola Inc||Reduction in signalling load in a wireless communication system|
|US6965968B1 (en)||2003-02-27||2005-11-15||Finjan Software Ltd.||Policy-based caching|
|US7644166B2 (en)||2003-03-03||2010-01-05||Aol Llc||Source audio identifiers for digital communications|
|US20040177369A1 (en)||2003-03-06||2004-09-09||Akins Glendon L.||Conditional access personal video recorder|
|US7881745B1 (en)||2003-03-10||2011-02-01||Hewlett-Packard Development Company, L.P.||Electronic device network employing provisioning techniques to update firmware and/or software in electronic devices|
|US7310729B2 (en)||2003-03-12||2007-12-18||Limelight Networks, Inc.||Digital rights management license delivery system and method|
|US20040181550A1 (en)||2003-03-13||2004-09-16||Ville Warsta||System and method for efficient adaptation of multimedia message content|
|US7388947B2 (en)||2003-03-14||2008-06-17||Federal Bureau Of Investigation, The United States Of America As Represented By The Office Of The General Counsel||Controllable telecommunications switch reporting compatible with voice grade lines|
|CA2519360A1 (en)||2003-03-17||2004-09-30||Spector & Associates, Inc||Apparatus and method for broadcasting messages to selected group(s) of users|
|US7801092B2 (en)||2003-03-21||2010-09-21||Cisco Technology, Inc.||Method for a simple 802.11e HCF implementation|
|US8117265B2 (en)||2003-03-26||2012-02-14||Aol Inc.||Identifying and using identities deemed to be known to a user|
|US6995749B2 (en)||2003-03-28||2006-02-07||Good Technology, Inc.||Auto font magnification mechanism|
|EP2811679A1 (en)||2003-03-31||2014-12-10||Apple Inc.||A radio telecommunications system and method of operating the same with polling|
|US7672439B2 (en)||2003-04-02||2010-03-02||Aol Inc.||Concatenated audio messages|
|WO2004092956A1 (en)||2003-04-02||2004-10-28||Pathfire, Inc.||Cascading key encryption|
|US7949759B2 (en)||2003-04-02||2011-05-24||AOL, Inc.||Degrees of separation for handling communications|
|JP2004312413A (en)||2003-04-08||2004-11-04||Sony Corp||Content providing server, information processing device and method, and computer program|
|TWI254564B (en)||2003-04-11||2006-05-01||Far Eastone Telecomm Co Ltd||Multimedia message servicing method capable of inquiring downloading information and structure thereof|
|US7394761B2 (en)||2003-04-29||2008-07-01||Avocent Huntsville Corporation||System and method for delivering messages using alternate modes of communication|
|EP1625474A4 (en)||2003-04-30||2012-03-07||Disney Entpr Inc||Cell phone multimedia controller|