Patent Grant
9043433
When WCDMA was specified, there was little attention to requirements posed by applications whose functions are based on actions initiated by the network, in contrast to functions initiated by the user or by the device. Such applications include, for example, push email, instant messaging, visual voicemail and voice and video telephony, and others. Such applications typically require an always-on IP connection and frequent transmit of small bits of data. WCDMA networks are designed and optimized for high-throughput of large amounts of data, not for applications that require frequent, but low-throughput and/or small amounts of data. Each transaction puts the mobile device radio in a high power mode for considerable length of time—typically between 15-30 seconds. As the high power mode can consume as much as 100× the power as an idle mode, these network-initiated applications quickly drain battery in WCDMA networks. The issue has been exacerbated by the rapid increase of popularity of applications with network-initiated functionalities, such as push email.
Lack of proper support has prompted a number of vendors to provide documents to guide their operator partners and independent software vendors to configure their networks and applications to perform better in WCDMA networks. This guidance focuses on: configuring networks to go to stay on high-power radio mode as short as possible and making periodic keep alive messages that are used to maintain an always-on TCP/IP connection as infrequent as possible. Such solutions typically assume lack of coordination between the user, the application and the network.
Furthermore, application protocols may provide long-lived connections that allow servers to push updated data to a mobile device without the need of the client to periodically re-establish the connection or to periodically query for changes. However, the mobile device needs to be sure that the connection remains usable by periodically sending some data, often called a keep-alive message, to the server and making sure the server is receiving this data. While the amount of data sent for a single keep-alive is not a lot and the keep-alive interval for an individual application is not too short, the cumulative effect of multiple applications performing this individually will amount to small pieces of data being sent very frequently. Frequently sending bursts of data in a wireless network also result in high battery consumption due to the constant need of powering/re-powering the radio module.
The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding of the disclosure. However, in certain instances, well-known or conventional details are not described in order to avoid obscuring the description. References to one or an embodiment in the present disclosure can be, but not necessarily are, references to the same embodiment; and, such references mean at least one of the embodiments.
Reference in this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not other embodiments.
The terms used in this specification generally have their ordinary meanings in the art, within the context of the disclosure, and in the specific context where each term is used. Certain terms that are used to describe the disclosure are discussed below, or elsewhere in the specification, to provide additional guidance to the practitioner regarding the description of the disclosure. For convenience, certain terms may be highlighted, for example using italics and/or quotation marks. The use of highlighting has no influence on the scope and meaning of a term; the scope and meaning of a term is the same, in the same context, whether or not it is highlighted. It will be appreciated that same thing can be said in more than one way.
Consequently, alternative language and synonyms may be used for any one or more of the terms discussed herein, nor is any special significance to be placed upon whether or not a term is elaborated or discussed herein. Synonyms for certain terms are provided. A recital of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification including examples of any terms discussed herein is illustrative only, and is not intended to further limit the scope and meaning of the disclosure or of any exemplified term. Likewise, the disclosure is not limited to various embodiments given in this specification.
Without intent to limit the scope of the disclosure, examples of instruments, apparatus, methods and their related results according to the embodiments of the present disclosure are given below. Note that titles or subtitles may be used in the examples for convenience of a reader, which in no way should limit the scope of the disclosure. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. In the case of conflict, the present document, including definitions will control.
Embodiments of the present disclosure include systems and methods for mobile network traffic coordination across multiple applications.
One embodiment of the disclosed technology includes, a system that optimizes multiple aspects of the connection with wired and wireless networks and devices through a comprehensive view of device and application activity including: loading, current application needs on a device, controlling the type of access (push vs. pull or hybrid), location, concentration of users in a single area, time of day, how often the user interacts with the application, content or device, and using this information to shape traffic to a cooperative client/server or simultaneously mobile devices without a cooperative client. Because the disclosed server is not tied to any specific network provider it has visibility into the network performance across all service providers. This enables optimizations to be applied to devices regardless of the operator or service provider, thereby enhancing the user experience and managing network utilization while roaming. Bandwidth has been considered a major issue in wireless networks today. More and more research has been done related to the need for additional bandwidth to solve access problems—many of the performance enhancing solutions and next generation standards, such as those commonly referred to as 4G, namely LTE, 4G, and WiMAX are focused on providing increased bandwidth. Although partially addressed by the standards a key problem that remains is lack of bandwidth on the signaling channel more so than the data channel.
Embodiments of the disclosed technology includes, for example, alignment of requests from multiple applications to minimize the need for several polling requests; leverage specific content types to determine how to proxy/manage a connection/content; and apply specific heuristics associated with device, user behavioral patterns (how often they interact with the device/application) and/or network parameters.
Embodiments of the present technology can further include, moving recurring HTTP polls performed by various widgets, RSS readers, etc., to remote network node (e.g., Network operation center (NOC)), thus considerably lowering device battery/power consumption, radio channel signaling, and bandwidth usage. Additionally, the offloading can be performed transparently so that existing applications do not need to be changed.
In some embodiments, this can be implemented using a local proxy on the mobile device which automatically detects recurring requests for the same content (RSS feed, Widget data set) that matches a specific rule (e.g. happens every 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 device (e.g., a mobile phone, smart phone, etc.) does not need to open up (e.g., thus powering on the radio) or use a data connection if the request is for content that is monitored and that has been not flagged as new/changed.
The logic for automatically adding content sources/application servers (e.g., including URLs/content) to be monitored can also check for various factors like how often the content is the same, how often the same request is made (is there a fixed interval/pattern?), which application is requesting the data, etc. Similar rules to decide between using the cache and request the data from the original source may also be implemented and executed by the local proxy and/or server.
For example, when the request comes at an unscheduled/unexpected time (user initiated check), or after every (n) consecutive times the response has been provided from the cache, etc., or if the application is running in the background vs. in a more interactive mode of the foreground. As more and more mobile applications base their features on resources available in the network, this becomes increasingly important. In addition, the disclosed technology allows elimination of unnecessary chatter from the network, benefiting the operators trying to optimize the wireless spectrum usage.
Cross Application Traffic Coordination
In one embodiment of the present disclosure, a group of applications [A, B, C, . . . ] may have a timeline of transfers of data from the mobile device (or client (e.g., mobile application, software agent, widget) on the mobile device) to the network, or from the network to the mobile device (for receipt by the client). The time of the transfers can be represented as:
Application A: tA1, tA2, tA3, . . .
Application B: tB1, tB2, tB3, . . .
Application C: tC1, tC2, tC3, . . .
Each of the times ‘t’ can have a natural point of occurring based upon the independent activity of the corresponding application as operations are executed at the application server/provider and/or on the software client on the mobile device. For example, an application can transfer a message, an event, or other types of data to the network (or vice versa) at a regular or semi-regular series of times as part of polling, satisfying a device, application, or user request, application maintenance, or other operation.
Similarly, an application can transfer a message, event, or other types data via the network (or vice versa) at a regular, semi-regular, or irregular series of times to perform its inherent functions or operations, such as synchronizing two data stores, determining the contents of a data store, accessing new data from the application server/service provider, communicating with a peer device (e.g., another device with the same application or another application with which the requesting application interacts), exchanging control messages, etc.
In some instances, there is typically no correlation or weak correlation between the times at which data transfers or event transactions occur for one application as compared to a second application on a given mobile device, or for different data requests for the same application. In some cases, there may be a stronger correlation between the times at which a transfer occurs for one application as compared to a second application (e.g., where an operation of a first application is dependent upon or triggers an operation of a second application, or where a user typically executes an operation of one application in conjunction with an operation of a second application). Note that in some instances, the second application may be the same application as the first application and that correlations can be tracked and determined for multiple requests sent by one application in a similar fashion.
In some embodiments, in order to optimize (e.g., typically to minimize) the number of times that a device (e.g., a mobile device or smart phone) radio is turned on to decrease the consumption of power (and hence conserve its battery or other power source), a distributed proxy system including a local proxy and/or proxy server can operate to intercept the events or transactions (or requests for transfer) of information. When intercepted, the local proxy and/or the proxy server can delay (or expedite) the time at which one or more of these transfers would normally occur in order to perform multiple transfers together as part of a single transfer operation (i.e., instead of performing multiple, individual transfers). Alternatively, the local and/or proxy server can pre-retrieve data for a non-priority application or less important/time sensitive application whose polls are typically expected to happen before another application having higher priority, for example. In other words, a delay could be negative resulting in content pre-retrieval for alignment with an anticipated data request which typically happens before the request of the lesser priority application.
The delay time (D) can represent a maximum time delay value (or in some instances, expedited time value) after receipt of a request to make such a transfer, with the value of D determined so as to enable the collection of as many of the transfers as feasible in a single, optimized data transfer. The delay times or expedited times of one or more transfers are determined so as to factor in any potential impact on performance and user experience. Ideally, the system determines D to prevent undesired penalties or inefficiencies, and to prevent undesired impact on the user experience. Note that as described above, the delay ‘D’ could be negative or positive for alignment purposes (e.g., to implement a delayed or an expedited transfer).
In some embodiments, delay time ‘D’ (use to represent both positive and negative delays (effectively and expedited transfer)) can be determined based on consideration of one or more of the following factors: the priority of the application (or the relative priority of one application in comparison to another), the nature or amount of data involved in the transfer (e.g., whether it represents fresh data, a housekeeping function, a control instruction, etc.), the status of the application (e.g., active, inactive, background, foreground, etc.), a useable lifetime of the data to be transferred (a period before it becomes stale), the interval between the transfer times of multiple data requests for a single application, the interval between the transfer times across more than one application (e.g., the largest transfer time interval based on consideration of all active applications), network characteristics (available bandwidth, network latency, etc.), or another relevant factor.
In some embodiments, the delay time ‘D’ of specific events/transactions can be controlled by the mobile device (e.g., platform, device settings, or OS specifications), network service provider, and/or the user as part of optimizing the battery life to align data transfer requests across multiple applications or the same application, as opposed to performing each data transfer individually. In some instances, the user can manually configure a setting specifying that requests across multiple applications or the same application are to be batched. The user can enable the setting, and allow the system to configure the details. In addition, the user can specify preferences, priorities, or any other constraints related to alignment of data request transfer of the mobile network.
The client devices 102A-D can be any system and/or device, and/or any combination of devices/systems that is able to establish a connection, including wired, wireless, cellular connections with another device, a server and/or other systems such as host server 100 and/or application server/content provider 110. Client devices 102 will typically include a display and/or other output functionalities to present information and data exchanged between among the devices 102 and/or the host server 100 and/or application server/content provider 110.
For example, the client devices 102 can include mobile, hand held or portable devices or non-portable devices and can be any of, but not limited to, a server desktop, a desktop computer, a computer cluster, or portable devices including, a notebook, a laptop computer, a handheld computer, a palmtop computer, a mobile phone, a cell phone, a smart phone, a PDA, a Blackberry device, a Palm device, a handheld tablet (e.g. an iPad or any other tablet), a hand held console, a hand held gaming device or console, any SuperPhone such as the iPhone, and/or any other portable, mobile, hand held devices, etc. In one embodiment, the client devices 102, host server 100, and app server 110 are coupled via a network 106 and/or a network 108. In some embodiments, the devices 102 and host server 100 may be directly connected to one another.
The input mechanism on client devices 102 can include touch screen keypad (including single touch, multi-touch, gesture sensing in 2D or 3D, etc.), a physical keypad, a mouse, a pointer, a track pad, motion detector (e.g., including 1-axis, 2-axis, 3-axis accelerometer, etc.), a light sensor, capacitance sensor, resistance sensor, temperature sensor, proximity sensor, a piezoelectric device, device orientation detector (e.g., electronic compass, tilt sensor, rotation sensor, gyroscope, accelerometer), or a combination of the above.
Signals received or detected indicating user activity at client devices 102 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 102. Context awareness at client devices 102 generally includes, by way of example but not limitation, client device 102 operation or state acknowledgement, management, user activity/behavior/interaction awareness, detection, sensing, tracking, trending, and/or application (e.g., mobile applications) type, behavior, activity, operating state, etc.
Context awareness in the present disclosure also includes knowledge and detection of network side contextual data and can include network information such as network capacity, bandwidth, traffic, type of network/connectivity, and/or any other operational state data. Network side contextual data can be received from and/or queried from network service providers (e.g., cell provider 112 and/or Internet service providers) of the network 106 and/or network 108 (e.g., by the host server and/or devices 102). In addition to application context awareness as determined from the client 102 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 102).
The host server 100 can use, for example, contextual information obtained for client devices 102, networks 106/108, applications (e.g., mobile applications), application server/provider 110, or any combination of the above, to manage the traffic in the system to satisfy data needs of the client devices 102 (e.g., to satisfy application or any other request including HTTP request). In one embodiment, the traffic is managed by the host server 100 to satisfy data requests made in response to explicit or non-explicit user 103 requests and/or device/application maintenance tasks. The traffic can be managed such that network consumption, for example, use of the cellular network is conserved for effective and efficient bandwidth utilization. In addition, the host server 100 can manage and coordinate such traffic in the system such that use of device 102 side resources (e.g., including but not limited to battery power consumption, radio use, processor/memory use) are optimized with a general philosophy for resource conservation while still optimizing performance and user experience.
For example, in context of battery conservation, the device 150 can observe user activity (for example, by observing user keystrokes, backlight status, or other signals via one or more input mechanisms, etc.) and alters device 102 behaviors. The device 150 can also request the host server 100 to alter the behavior for network resource consumption based on user activity or behavior.
In one embodiment, the traffic management for resource conservation is performed using a distributed system between the host server 100 and client device 102. The distributed system can include proxy server and cache components on the server 100 side and on the client 102 side, for example, as shown by the server cache 135 on the server 100 side and the local cache 150 on the client 102 side.
Functions and techniques disclosed for context aware traffic management for resource conservation in networks (e.g., network 106 and/or 108) and devices 102, reside in a distributed proxy and cache system. The proxy and cache system can be distributed between, and reside on, a given client device 102 in part or in whole and/or host server 100 in part or in whole. The distributed proxy and cache system are illustrated with further reference to the example diagram shown in
In one embodiment, client devices 102 communicate with the host server 100 and/or the application server 110 over network 106, which can be a cellular network. To facilitate overall traffic management between devices 102 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.
In general, the networks 106 and/or 108, over which the client devices 102, the host server 100, and/or application server 110 communicate, may be a cellular network, a telephonic network, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet, or any combination thereof. For example, the Internet can provide file transfer, remote log in, email, news, RSS, cloud-based services, instant messaging, visual voicemail, push mail, VoIP, and other services through any known or convenient protocol, such as, but is not limited to the TCP/IP protocol, UDP, HTTP, DNS, Open System Interconnections (OSI), FTP, UPnP, iSCSI, NSF, ISDN, PDH, RS-232, SDH, SONET, etc.
The networks 106 and/or 108 can be any collection of distinct networks operating wholly or partially in conjunction to provide connectivity to the client devices 102 and the host server 100 and may appear as one or more networks to the serviced systems and devices. In one embodiment, communications to and from the client devices 102 can be achieved by, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet. In one embodiment, communications can be achieved by a secure communications protocol, such as secure sockets layer (SSL), or transport layer security (TLS).
In addition, communications can be achieved via one or more networks, such as, but are not limited to, one or more of WiMax, a Local Area Network (LAN), Wireless Local Area Network (WLAN), a Personal area network (PAN), a Campus area network (CAN), a Metropolitan area network (MAN), a Wide area network (WAN), a Wireless wide area network (WWAN), enabled with technologies such as, by way of example, Global System for Mobile Communications (GSM), Personal Communications Service (PCS), Digital Advanced Mobile Phone Service (D-Amps), Bluetooth, Wi-Fi, Fixed Wireless Data, 2G, 2.5G, 3G, 4G, IMT-Advanced, pre-4G, 3G LTE, 3GPP LTE, LTE Advanced, mobile WiMax, WiMax 2, WirelessMAN-Advanced networks, enhanced data rates for GSM evolution (EDGE), General packet radio service (GPRS), enhanced GPRS, iBurst, UMTS, HSPDA, HSUPA, HSPA, UMTS-TDD, 1xRTT, EV-DO, messaging protocols such as, TCP/IP, SMS, MMS, extensible messaging and presence protocol (XMPP), real time messaging protocol (RTMP), instant messaging and presence protocol (IMPP), instant messaging, USSD, IRC, or any other wireless data networks or messaging protocols.
The distributed proxy and cache system can include, for example, the proxy server 125 (e.g., remote proxy) and the server cache, 135 components on the server side. The server-side proxy 125 and cache 135 can, as illustrated, reside internal to the host server 100. In addition, the proxy server 125 and cache 135 on the server-side can be partially or wholly external to the host server 100 and in communication via one or more of the networks 106 and 108. For example, the proxy server 125 may be external to the host server and the server cache 135 may be maintained at the host server 100. Alternatively, the proxy server 125 may be within the host server 100 while the server cache is external to the host server 100. In addition, each of the proxy server 125 and the cache 135 may be partially internal to the host server 100 and partially external to the host server 100.
The distributed system can also, include, in one embodiment, client-side components, including by way of example but not limitation, a local proxy 175 (e.g., a mobile client on a mobile device) and/or a local cache 185, which can, as illustrated, reside internal to the device 150 (e.g., a mobile device).
In addition, the client-side proxy 175 and local cache 185 can be partially or wholly external to the device 150 and in communication via one or more of the networks 106 and 108. For example, the local proxy 175 may be external to the device 150 and the local cache 185 may be maintained at the device 150. Alternatively, the local proxy 175 may be within the device 150 while the local cache 185 is external to the device 150. In addition, each of the proxy 175 and the cache 185 may be partially internal to the host server 100 and partially external to the host server 100.
In one embodiment, the distributed system can include an optional caching proxy server 199. The caching proxy server 199 can be a component which is operated by the application server/content provider 110, the host server 100, or a network service provider 112, and or any combination of the above to facilitate network traffic management for network and device resource conservation. Proxy server 199 can be used, for example, for caching content to be provided to the device 150, for example, from one or more of, the application server/provider 110, host server 100, and/or a network service provider 112. Content caching can also be entirely or partially performed by the remote proxy 125 to satisfy application requests or other data requests at the device 150.
In context aware traffic management and optimization for resource conservation in a network (e.g., cellular or other wireless networks), characteristics of user activity/behavior and/or application behavior at a mobile device 150 can be tracked by the local proxy 175 and communicated, over the network 106 to the proxy server 125 component in the host server 100, for example, as connection metadata. The proxy server 125 which in turn is coupled to the application server/provider 110 provides content and data to satisfy requests made at the device 150.
In addition, the local proxy 175 can identify and retrieve mobile device properties including, one or more of, battery level, network that the device is registered on, radio state, 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 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 app server/content provider 110). In addition, the proxy server 125 uses device properties and connection metadata to generate rules for satisfying request of applications on the mobile device 150. The proxy server 125 can gather real time traffic information about requests of applications for later use in optimizing similar connections with the mobile device 150 or other mobile devices.
In general, the local proxy 175 and the proxy server 125 are transparent to the multiple applications executing on the mobile device. The local proxy 175 is generally transparent to the operating system or platform of the mobile device and may or may not be specific to device manufacturers. In some instances, the local proxy 175 is optionally customizable in part or in whole to be device specific. In some embodiments, the local proxy 175 may be bundled into a wireless model, into a firewall, and/or a router.
In one embodiment, the host server 100 can in some instances, utilize the store and forward functions of a short message service center (SMSC) 112, such as that provided by the network service provider 112, in communicating with the device 150 in achieving network traffic management. As will be further described with reference to the example of
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.
The device 250, which can be a portable or mobile device, such as a portable phone, generally includes, for example, a network interface 208, an operating system 204, a context API 206, and mobile applications which may be proxy unaware 210 or proxy aware 220. Note that the device 250 is specifically illustrated in the example of
The network interface 202 can be a networking module that enables the device 250 to mediate data in a network with an entity that is external to the host server 250, through any known and/or convenient communications protocol supported by the host and the external entity. The network interface 208 can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, WiFi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G, LTE, etc.,), Bluetooth, or whether or not the connection is via a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.
Device 250 can further include, client-side components of the distributed proxy and cache system which can include, a local proxy 275 (e.g., a mobile client of a mobile device) and a cache 285. In one embodiment, the local proxy 275 includes a user activity module 215, a proxy API 225, a request/transaction manager 235, a caching policy manager 245, a traffic shaping engine 255, and/or a connection manager 265. The traffic shaping engine 255 may further include an alignment module 256 and/or a batching module 257, the connection manager 265 may further include a radio controller 266. The request/transaction manager 235 can further include an application behavior detector 236 and/or a prioritization engine 241, the application behavior detector 236 may further include a pattern detector 237 and/or and application profile generator 239. Additional or less components/modules/engines can be included in the local proxy 275 and each illustrated component.
As used herein, a “module,” “a manager,” a “handler,” a “detector,” an “interface,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module, manager, hander, or engine can be centralized or its functionality distributed. The module, manager, hander, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor. As used herein, a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 35 U.S.C. 101), and to specifically exclude all mediums that are non-statutory in nature to the extent that the exclusion is necessary for a claim that includes the computer-readable (storage) medium to be valid. Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.
In one embodiment, a portion of the distributed proxy and cache system for network traffic management resides in or is in communication with device 250, including local proxy 275 (mobile client) and/or cache 285. The local proxy 275 can provide an interface on the device 250 for users to access device applications and services including email, IM, voice mail, visual voicemail, feeds, Internet, other applications, etc.
The proxy 275 is generally application independent and can be used by applications (e.g., both proxy aware and proxy-unaware mobile applications 210 and 220) to open TCP connections to a remote server (e.g., the server 100 in the examples of
The applications 210 and 220 can generally include any user application, widgets, software, HTTP-based application, web browsers, video or other multimedia streaming or downloading application, video games, social network applications, email clients, RSS management applications, application stores, document management applications, productivity enhancement applications, etc. The applications can be provided with the device OS, by the device manufacturer, by the network service provider, downloaded by the user, or provided by others.
One embodiment of the local proxy 275 includes or is coupled to a context API 206, as shown. The context API 206 may be a part of the operating system 204 or device platform or independent of the operating system 204, as illustrated. The operating system 204 can include any operating system including but not limited to, any previous, current, and/or future versions/releases of, Windows Mobile, iOS, Android, Symbian, Palm OS, Brew MP, Java 2 Micro Edition (J2ME), Blackberry, etc.
The context API 206 may be a plug-in to the operating system 204 or a particular client application on the device 250. The context API 206 can detect signals indicative of user or device activity, for example, sensing motion, gesture, device location, changes in device location, device backlight, keystrokes, clicks, activated touch screen, mouse click or detection of other pointer devices. The context API 206 can be coupled to input devices or sensors on the device 250 to identify these signals. Such signals can generally include input received in response to explicit user input at an input device/mechanism at the device 250 and/or collected from ambient signals/contextual cues detected at or in the vicinity of the device 250 (e.g., light, motion, piezoelectric, etc.).
In one embodiment, the user activity module 215 interacts with the context API 206 to identify, determine, infer, detect, compute, predict, and/or anticipate, characteristics of user activity on the device 250. Various inputs collected by the context API 206 can be aggregated by the user activity module 215 to generate a profile for characteristics of user activity. Such a profile can be generated by the module 215 with various temporal characteristics. For instance, user activity profile can be generated in real-time for a given instant to provide a view of what the user is doing or not doing at a given time (e.g., defined by a time window, in the last minute, in the last 30 seconds, etc.), a user activity profile can also be generated for a ‘session’ defined by an application or web page that describes the characteristics of user behavior with respect to a specific task they are engaged in on the device 250, or for a specific time period (e.g., for the last 2 hours, for the last 5 hours).
Additionally, characteristic profiles can be generated by the user activity module 215 to depict a historical trend for user activity and behavior (e.g. 1 week, 1 mo, 2 mo, etc.). Such historical profiles can also be used to deduce trends of user behavior, for example, access frequency at different times of day, trends for certain days of the week (weekends or week days), user activity trends based on location data (e.g., IP address, GPS, or cell tower coordinate data) or changes in location data (e.g., user activity based on user location, or user activity based on whether the user is on the go, or traveling outside a home region, etc.) to obtain user activity characteristics.
In one embodiment, user activity module 215 can detect and track user activity with respect to applications, documents, files, windows, icons, and folders on the device 250. For example, the user activity module 215 can detect when an application or window (e.g., a web browser) has been exited, closed, minimized, maximized, opened, moved into the foreground, or into the background, multimedia content playback, etc.
In one embodiment, characteristics of the user activity on the device 250 can be used to locally adjust behavior of the device (e.g., mobile device) to optimize its resource consumption such as battery/power consumption and more generally, consumption of other device resources including memory, storage, and processing power. In one embodiment, the use of a radio on a device can be adjusted based on characteristics of user behavior (e.g., by the radio controller 266 of the connection manager 265) coupled to the user activity module 215. For example, the radio controller 266 can turn the radio on or off, based on characteristics of the user activity on the device 250. In addition, the radio controller 266 can adjust the power mode of the radio (e.g., to be in a higher power mode or lower power mode) depending on characteristics of user activity.
In one embodiment, characteristics of the user activity on device 250 can also be used to cause another device (e.g., other computers, a mobile device, or a non-portable device) or server (e.g., host server 100 and 300 in the examples of
In one embodiment, the user activity module 215 can, in response to determining that user activity characteristics indicate that a user is active after a period of inactivity, request that a remote device (e.g., server host server 100 and 300 in the examples of
In addition, or in alternative, the local proxy 275 can communicate the characteristics of user activity at the device 250 to the remove device (e.g., e.g., host server 100 and 300 in the examples of
One embodiment of the local proxy 275 further includes a request/transaction manager 235, which can detect, identify, intercept, process, manage, data requests initiated on the device 250, for example, by applications 210 and/or 220, and/or directly/indirectly by a user request. The request/transaction manager 235 can determine how and when to process a given request or transaction, or a set of requests/transactions, based on transaction characteristics.
The request/transaction manager 235 can prioritize requests or transactions made by applications and/or users at the device 250, for example by the prioritization engine 241. Importance or priority of requests/transactions can be determined by the manager 235 by applying a rule set, for example, according to time sensitivity of the transaction, time sensitivity of the content in the transaction, time criticality of the transaction, time criticality of the data transmitted in the transaction, and/or time criticality or importance of an application making the request.
In addition, transaction characteristics can also depend on whether the transaction was a result of user-interaction or other user initiated action on the device (e.g., user interaction with a mobile application). In general, a time critical transaction can include a transaction resulting from a user-initiated data transfer, and can be prioritized as such. Transaction characteristics can also depend on the amount of data that will be transferred or is anticipated to be transferred as a result of the request/requested transaction. For example, the connection manager 265, can adjust the radio mode (e.g., high power or low power mode via the radio controller 266) based on the amount of data that will need to be transferred.
In addition, the radio controller 266/connection manager 265 can adjust the radio power mode (high or low) based on time criticality/sensitivity of the transaction. The radio controller 266 can trigger the use of high power radio mode when a time-critical transaction (e.g., a transaction resulting from a user-initiated data transfer, an application running in the foreground, any other event meeting a certain criteria) is initiated or detected.
In general, the priorities can be determined set by in default, for example, based on device platform, device manufacturer, operating system, etc. Priorities can alternatively or in additionally be set by the particular application; for example, the Facebook mobile application can set its own priorities for various transactions (e.g., a status update can be of higher priority than an add friend request or a poke request, a message send request can be of higher priority than a message delete request, for example), an email client or IM chat client may have its own configurations for priority. The prioritization engine 241 may include set of rules for assigning priority.
The prioritization engine 241 can also track network provider limitations or specifications on application or transaction priority in determining an overall priority status for a request/transaction. Furthermore, priority can in part or in whole be determined by user preferences, either explicit or implicit. A user, can in general, set priorities at different tiers, such as, specific priorities for sessions, or types, or applications (e.g., a browsing session, a gaming session, versus an IM chat session, the user may set a gaming session to always have higher priority than an IM chat session, which may have higher priority than web-browsing session). A user can set application-specific priorities, (e.g., a user may set Facebook related transactions to have a higher priority than LinkedIn related transactions), for specific transaction types (e.g., for all send message requests across all applications to have higher priority than message delete requests, for all calendar-related events to have a high priority, etc.), and/or for specific folders.
The prioritization engine 241 can track and resolve conflicts in priorities set by different entities. For example, manual settings specified by the user may take precedence over device OS settings, network provider parameters/limitations (e.g., set in default for a network service area, geographic locale, set for a specific time of day, or set based on service/fee type) may limit any user-specified settings and/or application-set priorities. In some instances, a manual sync request received from a user can override some, most, or all priority settings in that the requested synchronization is performed when requested, regardless of the individually assigned priority or an overall priority ranking for the requested action.
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 below shows, for illustration purposes, some examples of transactions with examples of assigned priorities in a binary representation scheme. Additional assignments are possible for additional types of events, requests, transactions, and as previously described, priority assignments can be made at more or less granular levels, e.g., at the session level or at the application level, etc.
As shown by way of example in the above table, in general, lower priority requests/transactions can include, updating message status as being read, unread, deleting of messages, deletion of contacts; higher priority requests/transactions, can in some instances include, status updates, new IM chat message, new email, calendar event update/cancellation/deletion, an event in a mobile gaming session, or other entertainment related events, a purchase confirmation through a web purchase or online, request to load additional or download content, contact book related events, a transaction to change a device setting, location-aware or location-based events/transactions, or any other events/request/transactions initiated by a user or where the user is known to be, expected to be, or suspected to be waiting for a response, etc.
Inbox pruning events (e.g., email, or any other types of messages), are generally considered low priority and absent other impending events, generally will not trigger use of the radio on the device 250. Specifically, pruning events to remove old email or other content can be ‘piggy backed’ with other communications if the radio is not otherwise on, at the time of a scheduled pruning event. For example, if the user has preferences set to ‘keep messages for 7 days old,’ then instead of powering on the device radio to initiate a message delete from the device 250 the moment that the message has exceeded 7 days old, the message is deleted when the radio is powered on next. If the radio is already on, then pruning may occur as regularly scheduled.
The request/transaction manager 235, can use the priorities for requests (e.g., by the prioritization engine 241) to manage outgoing traffic from the device 250 for resource optimization (e.g., to utilize the device radio more efficiently for battery conservation). For example, transactions/requests below a certain priority ranking may not trigger use of the radio on the device 250 if the radio is not already switched on, as controlled by the connection manager 265. In contrast, the radio controller 266 can turn on the radio such a request can be sent when a request for a transaction is detected to be over a certain priority level.
In one embodiment, priority assignments (such as that determined by the local proxy 275 or another device/entity) can be used cause a remote device to modify its communication with the frequency with the mobile device. 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.
In one embodiment, transaction priority can be used in conjunction with characteristics of user activity in shaping or managing traffic, for example, by the traffic shaping engine 255. For example, the traffic shaping engine 255 can, in response to detecting that a user is dormant or inactive, wait to send low priority transactions from the device 250, for a period of time. In addition, the traffic shaping engine 255 can allow multiple low priority transactions to accumulate for batch transferring from the device 250 (e.g., via the batching module 257). In one embodiment, the priorities can be set, configured, or readjusted by a user. For example, content depicted in Table I in the same or similar form can be accessible in a user interface on the device 250 and for example, used by the user to adjust or view the priorities.
The batching module 257 can initiate batch transfer based on certain criteria. For example, batch transfer (e.g., of multiple occurrences of events, some of which occurred at different instances in time) may occur after a certain number of low priority events have been detected, or after an amount of time elapsed after the first of the low priority event was initiated. In addition, the batching module 257 can initiate batch transfer of the cumulated low priority events when a higher priority event is initiated or detected at the device 250. Batch transfer can otherwise be initiated when radio use is triggered for another reason (e.g., to receive data from a remote device such as host server 100 or 300). In one embodiment, an impending pruning event (pruning of an inbox), or any other low priority events, can be executed when a batch transfer occurs.
In general, the batching capability can be disabled or enabled at the event/transaction level, application level, or session level, based on any one or combination of the following: user configuration, device limitations/settings, manufacturer specification, network provider parameters/limitations, platform specific limitations/settings, device OS settings, etc. In one embodiment, batch transfer can be initiated when an application/window/file is closed out, exited, or moved into the background; users can optionally be prompted before initiating a batch transfer; users can also manually trigger batch transfers.
In one embodiment, the local proxy 275 locally adjusts radio use on the device 250 by caching data in the cache 285. When requests or transactions from the device 250 can be satisfied by content stored in the cache 285, the radio controller 266 need not activate the radio to send the request to a remote entity (e.g., the host server 100, 300, as shown in
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.
If a valid response is not available, the local proxy 275 can query a remote proxy (e.g., the server proxy 325 of
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
The manager 245 can request that the remote proxy monitor responses for the data request, and the remote proxy can notify the device 250 when an unexpected response to the data request is detected. In such an event, the cache policy manager 245 can erase or replace the locally stored response(s) on the device 250 when notified of the unexpected response (e.g., new data, changed data, additional data, etc.) to the data request. In one embodiment, the caching policy manager 245 is able to detect or identify the protocol used for a specific request, including but not limited to HTTP, HTTPS, IMAP, POP, SMTP and/or ActiveSync. In one embodiment, application specific handlers (e.g., via the application protocol module 246 of the manager 245) on the local proxy 275 allows for optimization of any protocol that can be port mapped to a handler in the distributed proxy (e.g., port mapped on the proxy server 325 in the example of
In one embodiment, the local proxy 275 notifies the remote proxy such that the remote proxy can monitor responses received for the data request from the content source for changed results prior to returning the result to the device 250, for example, when the data request to the content source has yielded same results to be returned to the mobile device. In general, the local proxy 275 can simulate application server responses for applications on the device 250, using locally cached content. This can prevent utilization of the cellular network for transactions where new/changed data is not available, thus freeing up network resources and preventing network congestion.
In one embodiment, the local proxy 275 includes an application behavior detector 236 to track, detect, observe, monitor, applications (e.g., proxy aware and/or unaware applications 210 and 220) accessed or installed on the device 250. Application behaviors, or patterns in detected behaviors (e.g., via the pattern detector 237) of one or more applications accessed on the device 250 can be used by the local proxy 275 to optimize traffic in a wireless network needed to satisfy the data needs of these applications.
For example, based on detected behavior of multiple applications, the traffic shaping engine 255 can align content requests made by at least some of the applications over the network (wireless network) (e.g., via the alignment module 256). The alignment module 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.), mobile device parameters, and/or network parameters/traffic conditions, network service provider constraints/specifications, etc.
In one embodiment, the pattern detector 237 can detect recurrences in application requests made by the multiple applications, for example, by tracking patterns in application behavior. A tracked pattern can include, detecting that certain applications, as a background process, poll an application server regularly, at certain times of day, on certain days of the week, periodically in a predictable fashion, with a certain frequency, with a certain frequency in response to a certain type of event, in response to a certain type user query, frequency that requested content is the same, frequency with which a same request is made, interval between requests, applications making a request, or any combination of the above, for example.
Such recurrences can be used by traffic shaping engine 255 to offload polling of content from a content source (e.g., from an application server/content provider 110 of
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 one embodiment, the local proxy 275 can mitigate the need/use of periodic keep alive messages (heartbeat messages) to maintain TCP/IP connections, which can consume significant amounts of power thus having detrimental impacts on mobile device battery life. The connection manager 265 in the local proxy (e.g., the heartbeat manager 267) can detect, identify, and intercept any or all heartbeat (keep-alive) messages being sent from applications.
The heartbeat manager 267 can prevent any or all of these heartbeat messages from being sent over the cellular, or other network, and instead rely on the server component of the distributed proxy system (e.g., shown in
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.
In one embodiment, the pattern detector 237 of the application behavior detector 236 further includes a correlation detector 238 and the application profile generator 239 further includes an application status detector 240.
The correlation detector 238, in one embodiment, can detect, determine, identify, compute, track, any correlations in the timing of data transfer requests made by applications, agents, and/or widgets accessed via (e.g., application streaming or accessed through a cloud) or running on the device 250.
In general, correlation types include event-level correlations and application-level correlations, and can include system/application. The correlation detector 238 can track and monitor system/application triggered events and/or user-triggered events/transactions. In addition, the correlation detector 238 can identify or track correlations between events for a given application or across different applications.
A correlation can be detected, for example, when a first event/transaction type of a first application triggers the initiation of a second event/transaction type of the same application. The triggering can be detected by the correlation detector 238 through identifying patterns in the timing characteristics of such events occurring within the first application. For example, a correlation can include, an identification of the ordering of the first and second event/transaction types (e.g., the second event type always occurs after the first event type). A correlation can also include, determining that the first and second event/transaction types occur within a timeframe of one another (e.g., the first event type occurs within a 10 ms. time window of the second event type), etc.
A correlation can also be detected, for example, when a specific event type of one application triggers a specific event type of another application (or has a timing or ordering relationship thereof). Similarly, the correlation detector 238 can detect that operation of one application (e.g., such as the launching of one application or any other activity) is related to the operation of another application. For example, the detector can determine that if one application is launched, the other application is also launched.
The detector can also detect that one application is always launched within a certain time window of another application being launched/accessed, or the activity status of one application is linked to the application status of the activity status of another application (e.g., when one application moves into the foreground/background, the other application moves into the foreground/background, or when one application becomes active/inactive, the other application also changes state and becomes either active or inactive, etc.). Generally, such events/transactions detected and tracked for correlation can include system or application-initiated events, or user-triggered events (e.g., including explicit user requests or implicit user requests).
In some instances, the correlation detector 238 uses user activity module 215 and can also detect application or application event correlations in relation to and/or in conjunction with user activity. For example, the correlation detector 238 can determine that an occurrence of a first event type frequently causes the user to perform an action which triggers a second event (of the same application or different application). While examples are described herein for two events and examples given for two applications, note that the correlation detector 238 can track, detect, and identify correlations in occurrences of events/transactions, correlations for multiple events (e.g., 2, 3, 4, 5, etc.) that can be detected and identified.
In general, the correlation detector 238 tracks the timing characteristics of requests made by applications to detect correlations. The correlations can be incorporated into an application's profile by the profile generator 239.
In one embodiment, the profile generator includes an application status detector 240. The application status detector 240 can detect an activity state of an application on the device 250. An activity state can indicate, by way of example but not limitation, whether a specific application is operating in the background or foreground on the mobile device 250, whether the application is active or inactive, whether the application is being interacted with (e.g., by a user, or another application or device). The activity state or status of an application on the device 250 can also be included in an application's profile (e.g., by the profile generator 239) along with any correlation with other events or applications and used for data request alignment.
For example, one embodiment of the alignment module 256 of the traffic shaping engine 255 which is able to use the application behavior (e.g., as determined by the application behavior detector 236) of one or multiple applications on a device 250 to align some of the content requests (e.g., aligned by the alignment module 256) made by the same application or at least a portion the multiple applications from the mobile device over the network. The application behaviors can be indicated in application profiles generated by the application profile generator 239, for example.
In some instances the content requests (made by the same application or different applications) are aligned by delaying or expediting a time at which some of the content requests would occur without alignment and the traffic shaping engine 256 can transfer the content requests that are delayed or expedited in a single transfer operation over the network (cellular or other wireless network). The amount of time that a request can be delayed (time ‘D’) is generally determined (e.g. by the delay module 258) to optimize a number of content requests able to be aligned in the single transfer operation. Hence delay module 258 can utilize the correlations in event/transaction occurrences within an application or across multiple applications as identified by the correlation detector 238 in determining delay time for aligning multiple requests.
The delay time ‘D’ (e.g., refers to the time by which a request is expedited or delayed) is generally determined based on application behavior (e.g., as determined by the application behavior detector 236 and/or indicated in an application profile). More specifically, the time that is delayed in transfer of a given content request can be determined based on priority of a specific application (e.g., as determined by the prioritization engine 241 of the application behavior detector 236) making the given content request, or based on the priority of the specific application relative to other applications on the mobile device 250. In addition, the delay module 258 can determine delays in transfer further based on, one or more of amount of data involved in the given content request, a nature of data involved in the given content request, usable lifetime of data to be transferred in the given content request, and/or network characteristics including available bandwidth or network latency.
Thus in one example of a system level operation in aligning requests, the local proxy 275 of the device 250 detects a first data request made via a first application and a second data request made via a second application, or where first and second data requests are made by the same application. The alignment module 256 of the traffic shaping engine 255 in the local proxy 275 on the device 250 can delay the transfer of the first data transfer request made via the first application to the proxy server (e.g., proxy server 125 or 325 in the examples of
The delay of the first data transfer request can be determined by the delay module 258 and the decision can be made when, for example, the second application is of a higher priority relative to the first application, or that the second application is running in the foreground, or that a user is interacting with the second application and the second data request is initiated in response to the user interaction, or that the second application is more data intensive than the first application.
The host server 300 generally includes, for example, a network interface 308 and/or one or more repositories 312, 314, 316. Note that server 300 may be any portable/mobile or non-portable device, server, cluster of computers and/or other types of processing units (e.g., any number of a machine shown in the example of
The network interface 308 can include networking module(s) or devices(s) that enable the server 300 to mediate data in a network with an entity that is external to the host server 300, through any known and/or convenient communications protocol supported by the host and the external entity. Specifically, the network interface 308 allows the server 308 to communicate with multiple devices including mobile phone devices 350, and/or one or more application servers/content providers 310.
The host server 300 can store information about connections (e.g., network characteristics, conditions, types of connections, etc.) with devices in the connection metadata repository 312. Additionally, any information about third party application or content providers can also be stored in 312. The host server 300 can store information about devices (e.g., hardware capability, properties, device settings, device language, network capability, manufacturer, device model, OS, OS version, etc.) in the device information repository 314. Additionally, the host server 300 can store information about network providers and the various network service areas in the network service provider repository 316.
The communication enabled by 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, bridge router, a hub, a digital media receiver, and/or a repeater.
The host server 300 can further include, server-side components of the distributed proxy and cache system which can include, a proxy server 325 and a server cache 335. In one embodiment, the server proxy 325 can include an HTTP access engine 345, a caching policy manager 355, a proxy controller 365, a traffic shaping engine 375, a new data detector 386, and/or a connection manager 395.
The HTTP access engine 345 may further include a heartbeat manager 346, the proxy controller 365 may further include a data invalidator module 366, the traffic shaping engine 375 may further include a control protocol 276 and a batching module 377. Additional or less components/modules/engines can be included in the proxy server 325 and each illustrated component.
As used herein, a “module,” “a manager,” a “handler,” a “detector,” an “interface,” a “controller,” or an “engine” includes a general purpose, dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, the module, manager, handler, or engine can be centralized or its functionality distributed. The module, manager, handler, or engine can include general or special purpose hardware, firmware, or software embodied in a computer-readable (storage) medium for execution by the processor. As used herein, a computer-readable medium or computer-readable storage medium is intended to include all mediums that are statutory (e.g., in the United States, under 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 app 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 provider 310. Specifically, the proxy server is able to communicate with the local proxy (e.g., proxy 175 and 275 of the examples of
In such a configuration, the host 300, or the proxy server 325 in the host server 300 can utilize intelligent information provided by the local proxy in adjusting its communication with the device in such a manner that optimizes use of network and device resources. For example, the proxy server 325 can identify characteristics of user activity on the device 350 to modify its communication frequency. The characteristics of user activity can be determined by, for example, the activity/behavior awareness module 366 in the proxy controller 365, via information collected by the local proxy on the device 350.
In one embodiment, communication frequency can be controlled by the connection manager 396 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 396 when characteristics of the user activity indicate that the user is inactive. In one embodiment, when the characteristics of the user activity indicate that the user is subsequently active after a period of inactivity, the connection manager 396 can adjust the communication frequency with the device 350 to send data that was buffered as a result of decreased communication frequency, to the device 350.
In addition, the proxy server 325 includes priority awareness of various requests, transactions, sessions, applications, and/or specific events. Such awareness can be determined by the local proxy on the device 350 and provided to the proxy server 325. The priority awareness module 367 of the proxy server 325 can generally assess the priority (e.g., including time-criticality, time-sensitivity, etc.) of various events or applications; additionally, the priority awareness module 367 can track priorities determined by local proxies of devices 350.
In one embodiment, through priority awareness, the connection manager 395 can further modify communication frequency (e.g., use or radio as controlled by the radio controller 396) of the server 300 with the devices 350. For example, the server 300 can notify the device 350, thus requesting use of the radio if it is not already in use, when data or updates of an importance/priority level which meets a criteria becomes available to be sent.
In one embodiment, the proxy server 325 can detect multiple occurrences of events (e.g., transactions, content, data received from server/provider 310) and allow the events to accumulate for batch transfer to device 350. Batch transfer can be cumulated and transfer of events can be delayed based on priority awareness and/or user activity/application behavior awareness, as tracked by modules 366 and/or 367. For example, batch transfer of multiple events (of a lower priority) to the device 350 can be initiated by the batching module 377 when an event of a higher priority (meeting a threshold or criteria) is detected at the server 300. In addition, batch transfer from the server 300 can be triggered when the server receives data from the device 350, indicating that the device radio is already in use and is thus on. In one embodiment, the proxy server 324 can order the each messages/packets in a batch for transmission based on event/transaction priority, such that higher priority content can be sent first, in case connection is lost or the battery dies, etc.
In one embodiment, the server 300 caches data (e.g., as managed by the caching policy manager 355) such that communication frequency over a network (e.g., cellular network) with the device 350 can be modified (e.g., decreased). The data can be cached, for example in the server cache 335, for subsequent retrieval or batch sending to the device 350 to potentially decrease the need to turn on the device 350 radio. The server cache 335 can be partially or wholly internal to the host server 300, although in the example of
In one embodiment, content caching is performed locally on the device 350 with the assistance of host server 300. For example, proxy server 325 in the host server 300 can query the application server/provider 310 with requests and monitor changes in responses. When changed or new responses are detected (e.g., by the new data detector 347), the proxy server 325 can notify the mobile device 350, such that the local proxy on the device 350 can make the decision to invalidate (e.g., indicated as out-dated) the relevant cache entries stored as any responses in its local cache. Alternatively, the data invalidator module 368 can automatically instruct the local proxy of the device 350 to invalidate certain cached data, based on received responses from the application server/provider 310. The cached data is marked as invalid, and can get replaced or deleted when new content is received from the content server 310.
Note that data change can be detected by the detector 347 in one or more ways. For example, the server/provider 310 can notify the host server 300 upon a change. The change can also be detected at the host server 300 in response to a direct poll of the source server/provider 310. In some instances, the proxy server 325 can in addition, pre-load the local cache on the device 350 with the new/updated data. This can be performed when the host server 300 detects that the radio on the mobile device is already in use, or when the server 300 has additional content/data to be sent to the device 350.
One or more the above mechanisms can be implemented simultaneously or adjusted/configured based on application (e.g., different policies for different servers/providers 310). In some instances, the source provider/server 310 may notify the host 300 for certain types of events (e.g., events meeting a priority threshold level). In addition, the provider/server 310 may be configured to notify the host 300 at specific time intervals, regardless of event priority.
In one embodiment, the proxy server 325 of the host 300 can monitor/track responses received for the data request from the content source for changed results prior to returning the result to the mobile device, such monitoring may be suitable when data request to the content source has yielded same results to be returned to the mobile device, thus preventing network/power consumption from being used when no new/changes are made to a particular requested. The local proxy of the device 350 can instruct the proxy server 325 to perform such monitoring or the proxy server 325 can automatically initiate such a process upon receiving a certain number of the same responses (e.g., or a number of the same responses in a period of time) for a particular request.
In one embodiment, the server 300, for example, through the activity/behavior awareness module 366, is able to identify or detect user activity, at a device that is separate from the mobile device 350. For example, the module 366 may detect that a user's message inbox (e.g., email or types of inbox) is being accessed. This can indicate that the user is interacting with his/her application using a device other than the mobile device 350 and may not need frequent updates, if at all.
The server 300, in this instance, can thus decrease the frequency with which new or updated content is sent to the mobile device 350, or eliminate all communication for as long as the user is detected to be using another device for access. Such frequency decrease may be application specific (e.g., for the application with which the user is interacting with on another device), or it may be a general frequency decrease (e.g., since the user is detected to be interacting with one server or one application via another device, he/she could also use it to access other services) to the mobile device 350.
In one embodiment, the host server 300 is able to poll content sources 310 on behalf of devices 350 to conserve power or battery consumption on devices 350. For example, certain applications on the mobile device 350 can poll its respective server 310 in a predictable recurring fashion. Such recurrence or other types of application behaviors can be tracked by the activity/behavior module 366 in the proxy controller 365. The host server 300 can thus poll content sources 310 for applications on the mobile device 350, that would otherwise be performed by the device 350 through a wireless (e.g., including cellular connectivity). The host server can poll the sources 310 for new or changed data by way of the HTTP access engine 345 to establish HTTP connection or by way of radio controller 396 to connect to the source 310 over the cellular network. When new or changed data is detected, the new data detector can notify the device 350 that such data is available and/or provide the new/changed data to the device 350.
In one embodiment, the connection manager 395 determines that the mobile device 350 is unavailable (e.g., the radio is turned off) and utilizes SMS to transmit content to the device 350, for instance via the SMSC shown in the example of
In one embodiment, the connection manager 395 in the proxy server 325 (e.g., the heartbeat manager 398) can generate and/or transmit heartbeat messages on behalf of connected devices 350, to maintain a backend connection with a provider 310 for applications running on devices 350.
For example, in the distributed proxy system, local cache on the device 350 can prevent any or all heartbeat messages needed to maintain TCP/IP connections required for applications, from being sent over the cellular, or other network, and instead rely on the proxy server 325 on the host server 300 to generate and/or send the heartbeat messages to maintain a connection with the backend (e.g., app server/provider 110 in the example of
The repositories 312, 314, and/or 316 can additionally store software, descriptive data, images, system information, drivers, and/or any other data item utilized by other components of the host server 300 and/or any other servers for operation. The repositories may be managed by a database management system (DBMS), for example but not limited to, Oracle, DB2, Microsoft Access, Microsoft SQL Server, PostgreSQL, MySQL, FileMaker, etc.
The repositories can be implemented via object-oriented technology and/or via text files, and can be managed by a distributed database management system, an object-oriented database management system (OODBMS) (e.g., ConceptBase, FastDB Main Memory Database Management System, JDOInstruments, ObjectDB, etc.), an object-relational database management system (ORDBMS) (e.g., Informix, OpenLink Virtuoso, VMDS, etc.), a file system, and/or any other convenient or known database management package.
In satisfying application or client requests on a mobile device 450 without the distributed proxy system 460, the mobile device 450, or the software widget executing on the device 450 performs a data request 402 (e.g., an HTTP GET, POST, or other request) directly to the application server 495 and receives a response 404 directly from the server/provider 495. If the data has been updated, the widget on the mobile device 450 can refreshes itself to reflect the update and waits for small period of time and initiates another data request to the server/provider 495.
In one embodiment, the requesting client or software widget 455 on the device 450 can utilize the distributed proxy system 460 in handling the data request made to server/provider 495. In general, the distributed proxy system 460 can include a local proxy 465 (which is typically considered a client-side component of the system 460 and can reside on the mobile device 450), a caching proxy (475, considered a server-side component 470 of the system 460 and can reside on the host server 485 or be wholly or partially external to the host server 485), a host server 485. The local proxy 465 can be connected to the proxy 475 and host server 485 via any network or combination of networks.
When the distributed proxy system 460 is used for data/application requests, the widget 455 can perform the data request 406 via the local proxy 465. The local proxy 465, can intercept the requests made by device applications, and can identify the connection type of the request (e.g., an HTTP get request or other types of requests). The local proxy 465 can then query the local cache for any previous information about the request (e.g., to determine whether a locally stored response is available and/or still valid). If a locally stored response is not available or if there is an invalid response stored, the local proxy 465 can update or store information about the request, the time it was made, and any additional data, in the local cache. The information can be updated for use in potentially satisfying subsequent requests.
The local proxy 465 can then send the request to the host server 485 and the server 485 can perform the request 406 and returns the results in response 408. The local proxy 465 can store the result and in addition, information about the result and returns the result to the requesting widget 455.
In one embodiment, if the same request has occurred multiple times (within a certain time period) and it has often yielded same results, the local proxy 465 can notify 410 the server 485 that the request should be monitored (e.g., steps 412 and 414) for result changes prior to returning a result to the local proxy 465 or requesting widget 455.
In one embodiment, if a request is marked for monitoring, the local proxy 465 can now store the results into the local cache. Now, when the data request 416, for which a locally response is available, is made by the widget 455 and intercepted at the local proxy 465, the proxy 465 can return the response 418 from the local cache without needing to establish a connection communication over the wireless network.
In addition, the server proxy performs the requests marked for monitoring 420 to determine whether the response 422 for the given request has changed. In general, the host server 485 can perform this monitoring independently of the widget 455 or local proxy 465 operations. Whenever an unexpected response 422 is received for a request, the server 485 can notify the local proxy 465 that the response has changed (e.g., the invalidate notification in step 424) and that the locally stored response on the client should be erased or replaced with a new response.
In this case, a subsequent data request 426 by the widget 455 from the device 450 results in the data being returned from host server 485 (e.g., via the caching proxy 475). Thus, through utilizing the distributed proxy system 460 the wireless (cellular) network is intelligently used when the content/data for the widget or software application 455 on the mobile device 450 has actually changed. As such, the traffic needed to check for the changes to application data is not performed over the wireless (cellular) network. This reduces the amount of generated network traffic and shortens the total time and the number of times the radio module is powered up on the mobile device 450, thus reducing battery consumption, and in addition, frees up network bandwidth.
When a data request A 432 is detected at the local proxy 465 on the mobile device 450, the local proxy 465 can determine that the radio on the mobile device 450 is currently off and decide to wait to transfer the request A 432 over the network. When data request B 434 is detected, the proxy 465 can determine (e.g., based on conditions and/or processes illustrated in the flow charts in the examples of
In the example shown in
In step 502, the local proxy (e.g., proxy 175 in the example of
In process 504, after the user has been detected to be inactive or idle over a period of time (e.g., the example is shown for a period of inactivity of 20 min.), the local proxy can adjust the device to go into the power saving mode. In the power saving mode, when the local proxy receives a message or a correspondence from a remote proxy (e.g., the server proxy 135 in the example of
In one embodiment, the response from the local proxy can include a time (e.g., the power save period) indicating to the remote proxy (e.g., server proxy 135) and/or the app server/providers 510A/B when the device 550 is next able to receive changes or additional data. A default power savings period can be set by the local proxy. Consecutive power saving periods can increase in duration. For example, if a first power saving period has elapsed without an activity occurring, the device 550 can continue into a second power saving mode with a longer time period (e.g., see periods one 503 and period two 505). In general, any activity on the device takes the client out of power saving mode and ends that particular power save event.
In addition, if new data or event is received before the end of any one power saving period, then the wait period communicated to the servers 510A/B can be the existing period, rather than an incremented time period. For example, in step 506, since new content was received during the power saving mode, the next wait period communicated in step 508 to servers 510A/B is again the same time saving period. In response, the remote proxy server, upon receipt of power save notification from the device 550, can stop sending changes (data or SMS's) for the period of time requested (the wait period). At the end of the wait period, any notifications received can be acted upon and changes sent to the device 550 as a single batched event. If no notifications come in, then true push can be resumed with the data or an SMS being sent immediately to the device 550. To optimize batch sending content to the mobile device 550, the proxy server can start the poll or data collect event earlier (before the end of a power save period) in order to increase the chance that the client will receive data at the next radio power on event.
In one embodiment, whenever new data or content comes into the device 550 while it is in a power saving mode, it can respond with the power saving remote procedure call to all end points currently registered (e.g., server/providers 510A/B). Note that the wait period can be updated in operation in real time to accommodate operating conditions. For example, as the mobile device 550 sends additional power saving calls (e.g., with updated wait times) if multiple servers 510A/B or others, respond to the end of a wait period with different delays, the local proxy can adjust the wait period on the fly to accommodate the different delays.
Detection of user activity 512 at the device 550 causes the power save mode to be exited. When the device 550 exits power save mode, it can send power save cancel call to the proxy server and immediately receives any changes associated with any pending notifications. This may require a poll to be run by the proxy server after receiving the power saving cancel call. If the latest power saving period has expired, then no power save cancel call may be needed as the proxy server will already be in traditional push operation mode.
In one embodiment, power save mode is not applied when the device 550 is plugged into a charger. This setting can be reconfigured or adjusted by the user or another party. In general, the power save mode can be turned on and off, for example, by the user via a user interface on device 550. In general, timing of power events to receive data can be synced with any power save calls to optimize radio use.
In process 602, a first data transfer request initiated by a first application on a device or mobile device is received. One or more selection processes can be performed to determine whether to delay transfer of the first data transfer request, as shown in steps 604-608, including, determining whether the user is interacting with the first application, whether the first application is in the foreground, or whether the radio of the mobile device on which the request is initiated is already on. Note that although the selection processes are illustrated and identified in a specific order, the order in which the system checks for applicability is not limited to such, any of the above conditions can be checked in any ordering or any combination with one of the other conditions.
If one of the above applies, in process 610, in general, a decision can be made to transfer the data request over the wireless (cellular or others) network, or to power on the radio (e.g., via the radio controller 256 shown in the example of
If none of the conditions in 604-608 applies (or other suitable conditions depending on the specific implementation), in process 612, the transfer of the first data transfer request can be delayed. In process 614, it is determined whether another data transfer request has been initiated. If not, the process continues at flow ‘A’ in
If so, the system performs one or more of several condition checks shown in decision flows 616-624 including determining whether the second application is of higher priority than the first application, whether the second application running in the foreground, whether the user interacting with the second application, whether the other data request initiated in response to user interaction, and/or whether the second application is more data intensive than the first application. The flow chart continues at ‘A’ in
If any of the above conditions apply, then in process 626, the first data transfer request of the first application and the other data transfer request of the second application are transferred in a single transfer operation over the network. Note that the conditions shown in 616-624 can be applied in any order or any combination with one another, although illustrated in the example flow chart as having a particular order.
The events shown in processes 702-710 can occur independently or in conjunction with one another and cause the data request to be transferred over the wireless network without or with minimal delay upon occurrences of these events. For example, in process 702, the mobile device radio is turned on due to another event. In process 704, a certain time period has elapsed, in process 706, a user trigger is detected, and/or the first application exits in process 708 and/or moves into the background in process 710. When any of the above conditions are detected, n process 721, the data request is transferred over the wireless (cellular or others) network.
In processes 802 and 804, data transfer requests made by first and second application on the mobile device are tracked. For example, the transaction/request manager 235 of the local proxy 275 shown in the example of
In process 806, a first timing characteristic of data transfer requests made by the first application is determined and in process 808, a second timing characteristic of data transfer requests made by the second application is determined, and can be used, for example, by the correlation detector 238 to identify any correlations in the requests.
Based on the identified timing characteristics and any determined correlations or applicable priorities (e.g., As determined by the prioritization engine 241 in
While the example is illustrated and described for different applications (e.g., first and second applications are different applications), the process can similarly be applied to different requests within the same application (e.g., first and second applications may be the same application).
In process 902, application behavior of multiple applications are detected on a mobile device. In general, the behaviors of any number of applications on the mobile device that are detected can be tracked. Any or all mobile applications on a device can be monitored for the potential for its requests to be aligned for traffic coordination. In addition, the user can select the applications to be aligned, or specify applications not to be tracked for traffic coordination. Furthermore, the device platform, manufacturer, OS settings, and/or network provider may have additional specifications or conditions for aligning traffic requests and selection of applications for traffic coordination.
In process 904, some of the content requests made by at least a portion the multiple applications from the mobile device over the network, are aligned. Process flow continues to step ‘B’ as shown in the example of
Example processes applied to determine delay time ‘D’ include, by way of example but not limitation: Determine priority of a specific application or priority of the application relative to other applications in process 1002, Determine an amount of data involved in a given content request in step 1004, Determine the useable lifetime of data to be transferred in the content request in step 1006, Determine a nature of data involved in a given content request in step 1008, Determine a status of the application making the content request in step 1010, and/or Determine the network characteristics when the request is made in step 1012. Any number of the above conditions can be applied in any order. Additional conditions which can be used may not be illustrated in the example above. In process 1014, any user configuration or overriding settings can be factored into consideration in determining delay to align content request, in process 1016.
In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.
The machine may be a server computer, a client computer, a personal computer (PC), a user device, a tablet PC, a laptop computer, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, an iPhone, an iPad, a Blackberry, a processor, a telephone, a web appliance, a network router, switch or bridge, a console, a hand-held console, a (hand-held) gaming device, a music player, any portable, mobile, hand-held device, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.
While the machine-readable medium or machine-readable storage medium is shown in an exemplary embodiment to be a single medium, the term “machine-readable medium” and “machine-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” and “machine-readable storage medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the presently disclosed technique and innovation.
In general, the routines executed to implement the embodiments of the disclosure, may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically comprise one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processing units or processors in a computer, cause the computer to perform operations to execute elements involving the various aspects of the disclosure.
Moreover, while embodiments have been described in the context of fully functioning computers and computer systems, those skilled in the art will appreciate that the various embodiments are capable of being distributed as a program product in a variety of forms, and that the disclosure applies equally regardless of the particular type of machine or computer-readable media used to actually effect the distribution.
Further examples of machine-readable storage media, machine-readable media, or computer-readable (storage) media include but are not limited to recordable type media such as volatile and non-volatile memory devices, floppy and other removable disks, hard disk drives, optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), among others, and transmission type media such as digital and analog communication links.
Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof, means any connection or coupling, either direct or indirect, between two or more elements; the coupling of connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.
The above detailed description of embodiments of the disclosure is not intended to be exhaustive or to limit the teachings to the precise form disclosed above. While specific embodiments of, and examples for, the disclosure are described above for illustrative purposes, various equivalent modifications are possible within the scope of the disclosure, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative embodiments may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or subcombinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed in parallel, or may be performed at different times. Further any specific numbers noted herein are only examples: alternative implementations may employ differing values or ranges.
The teachings of the disclosure provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various embodiments described above can be combined to provide further embodiments.
Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the disclosure can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further embodiments of the disclosure.
These and other changes can be made to the disclosure in light of the above Detailed Description. While the above description describes certain embodiments of the disclosure, and describes the best mode contemplated, no matter how detailed the above appears in text, the teachings can be practiced in many ways. Details of the system may vary considerably in its implementation details, while still being encompassed by the subject matter disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the disclosure should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the disclosure with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the disclosure to the specific embodiments disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the disclosure encompasses not only the disclosed embodiments, but also all equivalent ways of practicing or implementing the disclosure under the claims.
While certain aspects of the disclosure are presented below in certain claim forms, the inventors contemplate the various aspects of the disclosure in any number of claim forms. For example, while only one aspect of the disclosure is recited as a means-plus-function claim under 35 U.S.C. §112, ¶6, other aspects may likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. (Any claims intended to be treated under 35 U.S.C. §112, ¶6 will begin with the words “means for”.) Accordingly, the applicant reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the disclosure.
This application claims the benefit of U.S. Provisional Patent Application No. 61/367,871 entitled “CONSERVING POWER CONSUMPTION IN APPLICATIONS WITH NETWORK INITIATED DATA TRANSFER FUNCTIONALITY”, which was filed on Jul. 26, 2010, U.S. Provisional Patent Application No. 61/367,870 entitled “MANAGING AND IMPROVING NETWORK RESOURCE UTILIZATION, PERFORMANCE AND OPTIMIZING TRAFFIC IN WIRE LINE AND WIRELESS NETWORKS WITH MOBILE CLIENTS”, which was filed on Jul. 26, 2010, U.S. Provisional Patent Application No. 61/408,858 entitled “CROSS APPLICATION TRAFFIC COORDINATION”, which was filed on Nov. 1, 2010, U.S. Provisional Patent Application No. 61/408,839 entitled “ACTIVITY SESSION AS METHOD OF OPTIMIZING NETWORK RESOURCE USE”, which was filed on Nov. 1, 2010, U.S. Provisional Patent Application No. 61/408,829 entitled “DISTRIBUTED POLICY MANAGEMENT”, which was filed on Nov. 1, 2010, U.S. Provisional Patent Application No. 61/408,846 entitled “INTELLIGENT CACHE MANAGEMENT IN CONGESTED WIRELESS NETWORKS”, which was filed on Nov. 1, 2010, U.S. Provisional Patent Application No. 61/408,854 entitled “INTELLIGENT MANAGEMENT OF NON-CACHABLE CONTENT IN WIRELESS NETWORKS”, which was filed on Nov. 1, 2010, U.S. Provisional Patent Application No. 61/408,826 entitled “ONE WAY INTELLIGENT HEARTBEAT”, which was filed on Nov. 1, 2010, U.S. Provisional Patent Application No. 61/408,820 entitled “TRAFFIC CATEGORIZATION AND POLICY DRIVING RADIO STATE”, which was filed on Nov. 1, 2010, U.S. Provisional Patent Application No. 61/416,020 entitled “ALIGNING BURSTS FROM SERVER TO CLIENT”, which was filed on Nov. 22, 2010, U.S. Provisional Patent Application No. 61/416,033 entitled “POLLING INTERVAL FUNCTIONS”, which was filed on Nov. 22, 2010, U.S. Provisional Patent Application No. 61/430,828 entitled “DOMAIN NAME SYSTEM WITH NETWORK TRAFFIC HARMONIZATION”, which was filed on Jan. 7, 2011, the contents of which are all incorporated by reference herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 222458 | Connolly et al. | Dec 1879 | A |
| 447918 | Strowger | Mar 1891 | A |
| 4200770 | Hellman et al. | Apr 1980 | A |
| 4255796 | Gabbe et al. | Mar 1981 | A |
| 4276597 | Dissly et al. | Jun 1981 | A |
| 4531020 | Wechselberger et al. | Jul 1985 | A |
| 4807182 | Queen | Feb 1989 | A |
| 4831582 | Miller et al. | May 1989 | A |
| 4875159 | Cary et al. | Oct 1989 | A |
| 4897781 | Chang et al. | Jan 1990 | A |
| 4972457 | O'Sullivan | Nov 1990 | A |
| 5008853 | Bly et al. | Apr 1991 | A |
| 5159624 | Makita | Oct 1992 | A |
| 5220657 | Bly et al. | Jun 1993 | A |
| 5263157 | Janis | Nov 1993 | A |
| 5283856 | Gross et al. | Feb 1994 | A |
| 5357431 | Nakada et al. | Oct 1994 | A |
| 5384892 | Strong | Jan 1995 | A |
| 5386564 | Shearer et al. | Jan 1995 | A |
| 5392390 | Crozier | Feb 1995 | A |
| 5434994 | Shaheen et al. | Jul 1995 | A |
| 5436960 | Campana, Jr. et al. | Jul 1995 | A |
| 5438611 | Campana, Jr. et al. | Aug 1995 | A |
| 5479472 | Campana, Jr. et al. | Dec 1995 | A |
| 5487100 | Kane | Jan 1996 | A |
| 5491703 | Barnaby et al. | Feb 1996 | A |
| 5493692 | Theimer et al. | Feb 1996 | A |
| 5519606 | Frid-Nielsen et al. | May 1996 | A |
| 5537464 | Lewis et al. | Jul 1996 | A |
| 5555376 | Theimer et al. | Sep 1996 | A |
| 5559800 | Mousseau et al. | Sep 1996 | A |
| 5572571 | Shirai | Nov 1996 | A |
| 5572643 | Judson | Nov 1996 | A |
| 5574859 | Yeh | Nov 1996 | A |
| 5581749 | Hossain et al. | Dec 1996 | A |
| 5600834 | Howard | Feb 1997 | A |
| 5603054 | Theimer et al. | Feb 1997 | A |
| 5604788 | Tett | Feb 1997 | A |
| 5613012 | Hoffman et al. | Mar 1997 | A |
| 5619507 | Tsuda | Apr 1997 | A |
| 5619648 | Canale et al. | Apr 1997 | A |
| 5623601 | Vu | Apr 1997 | A |
| 5625670 | Campana, Jr. et al. | Apr 1997 | A |
| 5625815 | Maier et al. | Apr 1997 | A |
| 5627658 | Connors et al. | May 1997 | A |
| 5630081 | Rybicki et al. | May 1997 | A |
| 5631946 | Campana, Jr. et al. | May 1997 | A |
| 5632018 | Otorii | May 1997 | A |
| 5634053 | Noble et al. | May 1997 | A |
| 5644788 | Courtright et al. | Jul 1997 | A |
| 5647002 | Brunson | Jul 1997 | A |
| 5652884 | Palevich | Jul 1997 | A |
| 5664207 | Crumpler et al. | Sep 1997 | A |
| 5666530 | Clark et al. | Sep 1997 | A |
| 5666553 | Crozier | Sep 1997 | A |
| 5673322 | Pepe et al. | Sep 1997 | A |
| 5680542 | Mulchandani et al. | Oct 1997 | A |
| 5682524 | Freund et al. | Oct 1997 | A |
| 5684990 | Boothby | Nov 1997 | A |
| 5689654 | Kikinis et al. | Nov 1997 | A |
| 5692039 | Brankley et al. | Nov 1997 | A |
| 5696903 | Mahany | Dec 1997 | A |
| 5701423 | Crozier | Dec 1997 | A |
| 5701469 | Brandli et al. | Dec 1997 | A |
| 5704029 | Wright, Jr. | Dec 1997 | A |
| 5706211 | Beletic et al. | Jan 1998 | A |
| 5706502 | Foley et al. | Jan 1998 | A |
| 5706507 | Schloss | Jan 1998 | A |
| 5710918 | Lagarde et al. | Jan 1998 | A |
| 5713019 | Keaten | Jan 1998 | A |
| 5715403 | Stefik | Feb 1998 | A |
| 5717925 | Harper et al. | Feb 1998 | A |
| 5721908 | Lagarde et al. | Feb 1998 | A |
| 5721914 | DeVries | Feb 1998 | A |
| 5727202 | Kucala | Mar 1998 | A |
| 5729549 | Kostreski et al. | Mar 1998 | A |
| 5729704 | Stone et al. | Mar 1998 | A |
| 5729735 | Meyering | Mar 1998 | A |
| 5742905 | Pepe et al. | Apr 1998 | A |
| 5745360 | Leone et al. | Apr 1998 | A |
| 5752186 | Malackowski et al. | May 1998 | A |
| 5752246 | Rogers et al. | May 1998 | A |
| 5754938 | Herz et al. | May 1998 | A |
| 5757916 | MacDoran et al. | May 1998 | A |
| 5758088 | Bezaire et al. | May 1998 | A |
| 5758150 | Bell et al. | May 1998 | A |
| 5758322 | Rongley | May 1998 | A |
| 5758354 | Huang et al. | May 1998 | A |
| 5758355 | Buchanan | May 1998 | A |
| 5765171 | Gehani et al. | Jun 1998 | A |
| 5778346 | Frid-Nielsen et al. | Jul 1998 | A |
| 5778361 | Nanjo et al. | Jul 1998 | A |
| 5781614 | Brunson | Jul 1998 | A |
| 5781901 | Kuzma | Jul 1998 | A |
| 5781906 | Aggarwal et al. | Jul 1998 | A |
| 5787430 | Doeringer et al. | Jul 1998 | A |
| 5787441 | Beckhardt | Jul 1998 | A |
| 5790425 | Wagle | Aug 1998 | A |
| 5790790 | Smith et al. | Aug 1998 | A |
| 5790974 | Tognazzini | Aug 1998 | A |
| 5793413 | Hylton et al. | Aug 1998 | A |
| 5794210 | Goldhaber et al. | Aug 1998 | A |
| 5799318 | Cardinal et al. | Aug 1998 | A |
| 5802312 | Lazaridis et al. | Sep 1998 | A |
| 5802454 | Goshay et al. | Sep 1998 | A |
| 5802518 | Karaev et al. | Sep 1998 | A |
| 5802524 | Flowers et al. | Sep 1998 | A |
| 5806074 | Souder et al. | Sep 1998 | A |
| 5809242 | Shaw et al. | Sep 1998 | A |
| 5809415 | Rossmann | Sep 1998 | A |
| 5818437 | Grover et al. | Oct 1998 | A |
| 5819172 | Campana, Jr. et al. | Oct 1998 | A |
| 5819274 | Jackson, Jr. | Oct 1998 | A |
| 5819284 | Farber et al. | Oct 1998 | A |
| 5822324 | Kostresti et al. | Oct 1998 | A |
| 5822747 | Graefe et al. | Oct 1998 | A |
| 5826269 | Hussey | Oct 1998 | A |
| 5831664 | Wharton et al. | Nov 1998 | A |
| 5832483 | Barker | Nov 1998 | A |
| 5832489 | Kucala | Nov 1998 | A |
| 5832500 | Burrows | Nov 1998 | A |
| 5835087 | Herz et al. | Nov 1998 | A |
| 5835722 | Bradshaw et al. | Nov 1998 | A |
| 5838252 | Kikinis | Nov 1998 | A |
| 5838768 | Sumar et al. | Nov 1998 | A |
| 5838973 | Carpenter-Smith et al. | Nov 1998 | A |
| 5845278 | Kirsch et al. | Dec 1998 | A |
| 5852775 | Hidary | Dec 1998 | A |
| 5852820 | Burrows | Dec 1998 | A |
| 5857201 | Wright, Jr. et al. | Jan 1999 | A |
| 5862223 | Walker et al. | Jan 1999 | A |
| 5867665 | Butman et al. | Feb 1999 | A |
| 5867817 | Catallo et al. | Feb 1999 | A |
| 5870759 | Bauer et al. | Feb 1999 | A |
| 5881231 | Takagi et al. | Mar 1999 | A |
| 5884323 | Hawkins et al. | Mar 1999 | A |
| 5889845 | Staples et al. | Mar 1999 | A |
| 5889953 | Thebaut et al. | Mar 1999 | A |
| 5890147 | Peltonen et al. | Mar 1999 | A |
| 5892909 | Grasso et al. | Apr 1999 | A |
| 5898780 | Liu et al. | Apr 1999 | A |
| 5898917 | Batni et al. | Apr 1999 | A |
| 5903723 | Beck et al. | May 1999 | A |
| 5907618 | Gennaro et al. | May 1999 | A |
| 5909689 | Van Ryzin | Jun 1999 | A |
| 5913032 | Schwartz et al. | Jun 1999 | A |
| 5924096 | Draper et al. | Jul 1999 | A |
| 5928325 | Shaughnessy et al. | Jul 1999 | A |
| 5928329 | Clark et al. | Jul 1999 | A |
| 5937161 | Mulligan et al. | Aug 1999 | A |
| 5940813 | Hutchings | Aug 1999 | A |
| 5943676 | Boothby | Aug 1999 | A |
| 5948066 | Whalen et al. | Sep 1999 | A |
| 5951636 | Zerber | Sep 1999 | A |
| 5960394 | Gould et al. | Sep 1999 | A |
| 5960406 | Rasansky et al. | Sep 1999 | A |
| 5961590 | Mendez et al. | Oct 1999 | A |
| 5963642 | Goldstein | Oct 1999 | A |
| 5964833 | Kikinis | Oct 1999 | A |
| 5968131 | Mendez et al. | Oct 1999 | A |
| 5974238 | Chase, Jr. | Oct 1999 | A |
| 5974327 | Agrawal et al. | Oct 1999 | A |
| 5978837 | Foladare et al. | Nov 1999 | A |
| 5978933 | Wyld et al. | Nov 1999 | A |
| 5987440 | O'Neil et al. | Nov 1999 | A |
| 6000000 | Hawkins et al. | Dec 1999 | A |
| 6003070 | Frantz | Dec 1999 | A |
| 6006197 | d'Eon et al. | Dec 1999 | A |
| 6006274 | Hawkins et al. | Dec 1999 | A |
| 6016478 | Zhang et al. | Jan 2000 | A |
| 6016520 | Facq et al. | Jan 2000 | A |
| 6018762 | Brunson et al. | Jan 2000 | A |
| 6023700 | Owens et al. | Feb 2000 | A |
| 6023708 | Mendez et al. | Feb 2000 | A |
| 6029238 | Furukawa | Feb 2000 | A |
| 6034621 | Kaufman | Mar 2000 | A |
| 6035104 | Zahariev | Mar 2000 | A |
| 6044205 | Reed et al. | Mar 2000 | A |
| 6044372 | Rothfus et al. | Mar 2000 | A |
| 6044381 | Boothby et al. | Mar 2000 | A |
| 6047051 | Ginzboorg et al. | Apr 2000 | A |
| 6047327 | Tso et al. | Apr 2000 | A |
| 6052563 | Macko | Apr 2000 | A |
| 6052735 | Ulrich et al. | Apr 2000 | A |
| 6057855 | Barkans | May 2000 | A |
| 6065055 | Hughes et al. | May 2000 | A |
| 6067477 | Wewalaarachchi et al. | May 2000 | A |
| 6073138 | de l'Etraz et al. | Jun 2000 | A |
| 6073142 | Geiger et al. | Jun 2000 | A |
| 6073165 | Narasimhan et al. | Jun 2000 | A |
| 6085166 | Beckhardt et al. | Jul 2000 | A |
| 6085192 | Mendez et al. | Jul 2000 | A |
| 6088677 | Spurgeon | Jul 2000 | A |
| 6098172 | Coss et al. | Aug 2000 | A |
| 6101320 | Schuetze et al. | Aug 2000 | A |
| 6101480 | Conmy et al. | Aug 2000 | A |
| 6101531 | Eggleston et al. | Aug 2000 | A |
| 6112181 | Shear et al. | Aug 2000 | A |
| 6119014 | Alperovich et al. | Sep 2000 | A |
| 6119171 | Alkhatib | Sep 2000 | A |
| 6125369 | Wu et al. | Sep 2000 | A |
| 6125388 | Reisman | Sep 2000 | A |
| 6125441 | Green | Sep 2000 | A |
| 6128627 | Mattis et al. | Oct 2000 | A |
| 6130898 | Kostreski et al. | Oct 2000 | A |
| 6131096 | Ng et al. | Oct 2000 | A |
| 6131116 | Riggins et al. | Oct 2000 | A |
| 6134432 | Holmes et al. | Oct 2000 | A |
| 6138013 | Blanchard et al. | Oct 2000 | A |
| 6138124 | Beckhardt | Oct 2000 | A |
| 6138128 | Perkowitz et al. | Oct 2000 | A |
| 6138146 | Moon et al. | Oct 2000 | A |
| 6141664 | Boothby | Oct 2000 | A |
| 6151606 | Mendez | Nov 2000 | A |
| 6157630 | Adler et al. | Dec 2000 | A |
| 6161008 | Lee et al. | Dec 2000 | A |
| 6161140 | Moriya | Dec 2000 | A |
| 6167379 | Dean et al. | Dec 2000 | A |
| 6167435 | Druckenmiller et al. | Dec 2000 | A |
| 6170014 | Darago et al. | Jan 2001 | B1 |
| 6173312 | Atarashi et al. | Jan 2001 | B1 |
| 6173446 | Khan et al. | Jan 2001 | B1 |
| 6175831 | Weinreich et al. | Jan 2001 | B1 |
| 6178419 | Legh-Smith et al. | Jan 2001 | B1 |
| 6181935 | Gossman et al. | Jan 2001 | B1 |
| 6185184 | Mattaway et al. | Feb 2001 | B1 |
| 6195533 | Tkatch et al. | Feb 2001 | B1 |
| 6198696 | Korpi et al. | Mar 2001 | B1 |
| 6198922 | Baynham | Mar 2001 | B1 |
| 6201469 | Balch et al. | Mar 2001 | B1 |
| 6202085 | Benson et al. | Mar 2001 | B1 |
| 6205448 | Kruglikov et al. | Mar 2001 | B1 |
| 6209038 | Bowen et al. | Mar 2001 | B1 |
| 6212529 | Boothby et al. | Apr 2001 | B1 |
| 6219694 | Lazaridis et al. | Apr 2001 | B1 |
| 6221877 | Aronov et al. | Apr 2001 | B1 |
| 6223187 | Boothby et al. | Apr 2001 | B1 |
| 6226686 | Rothschild et al. | May 2001 | B1 |
| 6233341 | Riggins | May 2001 | B1 |
| 6233606 | Dujari | May 2001 | B1 |
| 6243705 | Kucala | Jun 2001 | B1 |
| 6246875 | Seazholtz et al. | Jun 2001 | B1 |
| 6247135 | Feague | Jun 2001 | B1 |
| 6249808 | Seshadri | Jun 2001 | B1 |
| 6256666 | Singhal | Jul 2001 | B1 |
| 6263201 | Hashimoto et al. | Jul 2001 | B1 |
| 6263340 | Green | Jul 2001 | B1 |
| 6269369 | Robertson | Jul 2001 | B1 |
| 6272545 | Flanagin et al. | Aug 2001 | B1 |
| 6275850 | Beyda et al. | Aug 2001 | B1 |
| 6275858 | Bates et al. | Aug 2001 | B1 |
| 6289212 | Stein et al. | Sep 2001 | B1 |
| 6289214 | Backstrom | Sep 2001 | B1 |
| 6292904 | Broomhall et al. | Sep 2001 | B1 |
| 6295541 | Bodnar et al. | Sep 2001 | B1 |
| 6300947 | Kanevsky | Oct 2001 | B1 |
| 6304881 | Halim et al. | Oct 2001 | B1 |
| 6308201 | Pivowar et al. | Oct 2001 | B1 |
| 6311216 | Smith et al. | Oct 2001 | B1 |
| 6317594 | Gossman et al. | Nov 2001 | B1 |
| 6320943 | Borland | Nov 2001 | B1 |
| 6324541 | de l'Etraz et al. | Nov 2001 | B1 |
| 6324542 | Wright, Jr. et al. | Nov 2001 | B1 |
| 6324544 | Alam et al. | Nov 2001 | B1 |
| 6324587 | Trenbeath et al. | Nov 2001 | B1 |
| 6327586 | Kisiel | Dec 2001 | B1 |
| 6336117 | Massarani | Jan 2002 | B1 |
| 6336138 | Caswell et al. | Jan 2002 | B1 |
| 6341311 | Smith et al. | Jan 2002 | B1 |
| 6351767 | Batchelder et al. | Feb 2002 | B1 |
| 6356937 | Montville et al. | Mar 2002 | B1 |
| 6363051 | Eslambolchi et al. | Mar 2002 | B1 |
| 6363352 | Dailey et al. | Mar 2002 | B1 |
| 6370566 | Discolo et al. | Apr 2002 | B2 |
| 6377790 | Ishii | Apr 2002 | B1 |
| 6377810 | Geiger et al. | Apr 2002 | B1 |
| 6377991 | Smith et al. | Apr 2002 | B1 |
| 6380959 | Wang et al. | Apr 2002 | B1 |
| 6389422 | Doi et al. | May 2002 | B1 |
| 6389455 | Fuisz | May 2002 | B1 |
| 6389457 | Lazaridis et al. | May 2002 | B2 |
| 6397057 | Malackowski et al. | May 2002 | B1 |
| 6397230 | Carmel et al. | May 2002 | B1 |
| 6401104 | LaRue et al. | Jun 2002 | B1 |
| 6401112 | Boyer et al. | Jun 2002 | B1 |
| 6401113 | Lazaridis et al. | Jun 2002 | B2 |
| 6405197 | Gilmour | Jun 2002 | B2 |
| 6411696 | Iverson et al. | Jun 2002 | B1 |
| 6415031 | Colligan et al. | Jul 2002 | B1 |
| 6418308 | Heinonen et al. | Jul 2002 | B1 |
| 6421669 | Gilmour et al. | Jul 2002 | B1 |
| 6421674 | Yoakum et al. | Jul 2002 | B1 |
| 6421781 | Fox et al. | Jul 2002 | B1 |
| 6430602 | Kay et al. | Aug 2002 | B1 |
| 6438585 | Mousseau et al. | Aug 2002 | B2 |
| 6438612 | Ylonen et al. | Aug 2002 | B1 |
| 6442589 | Takahashi et al. | Aug 2002 | B1 |
| 6442637 | Hawkins et al. | Aug 2002 | B1 |
| 6446118 | Gottlieb | Sep 2002 | B1 |
| 6463463 | Godfrey et al. | Oct 2002 | B1 |
| 6463464 | Lazaridis et al. | Oct 2002 | B1 |
| 6484203 | Porras et al. | Nov 2002 | B1 |
| 6487557 | Nagatomo | Nov 2002 | B1 |
| 6487560 | LaRue et al. | Nov 2002 | B1 |
| 6490353 | Tan | Dec 2002 | B1 |
| 6496802 | van Zoest et al. | Dec 2002 | B1 |
| 6499054 | Hesselink et al. | Dec 2002 | B1 |
| 6505214 | Sherman et al. | Jan 2003 | B1 |
| 6516327 | Zondervan et al. | Feb 2003 | B1 |
| 6526433 | Chang et al. | Feb 2003 | B1 |
| 6526506 | Lewis | Feb 2003 | B1 |
| 6529908 | Piett et al. | Mar 2003 | B1 |
| 6532446 | King | Mar 2003 | B1 |
| 6535892 | LaRue et al. | Mar 2003 | B1 |
| 6546005 | Berkley et al. | Apr 2003 | B1 |
| 6549939 | Ford et al. | Apr 2003 | B1 |
| 6556217 | Mäkipää et al. | Apr 2003 | B1 |
| 6557026 | Stephens, Jr. | Apr 2003 | B1 |
| 6570890 | Keenan et al. | May 2003 | B1 |
| 6571140 | Wewalaarachchi et al. | May 2003 | B1 |
| 6593944 | Nicolas et al. | Jul 2003 | B1 |
| 6601026 | Appelt et al. | Jul 2003 | B2 |
| 6615253 | Bowman-Amuah | Sep 2003 | B1 |
| 6618710 | Zondervan et al. | Sep 2003 | B1 |
| 6621892 | Banister et al. | Sep 2003 | B1 |
| 6622157 | Heddaya et al. | Sep 2003 | B1 |
| 6625621 | Tan et al. | Sep 2003 | B2 |
| 6636482 | Cloonan et al. | Oct 2003 | B2 |
| 6639693 | Ejiri et al. | Oct 2003 | B1 |
| 6640097 | Corrigan et al. | Oct 2003 | B2 |
| 6640244 | Bowman-Amuah | Oct 2003 | B1 |
| 6640249 | Bowman-Amuah | Oct 2003 | B1 |
| 6643650 | Slaughter et al. | Nov 2003 | B1 |
| 6643688 | Fuisz | Nov 2003 | B1 |
| 6647384 | Gilmour | Nov 2003 | B2 |
| 6650890 | Irlam et al. | Nov 2003 | B1 |
| 6662016 | Buckham et al. | Dec 2003 | B1 |
| 6668046 | Albal | Dec 2003 | B1 |
| 6671695 | McFadden | Dec 2003 | B2 |
| 6671700 | Creemer et al. | Dec 2003 | B1 |
| 6671702 | Kruglikov et al. | Dec 2003 | B2 |
| 6671757 | Multer et al. | Dec 2003 | B1 |
| 6694336 | Multer et al. | Feb 2004 | B1 |
| 6697807 | McGeachie | Feb 2004 | B2 |
| 6701378 | Gilhuly et al. | Mar 2004 | B1 |
| 6707801 | Hsu | Mar 2004 | B2 |
| 6708221 | Mendez et al. | Mar 2004 | B1 |
| 6714965 | Kakuta et al. | Mar 2004 | B2 |
| 6721787 | Hiscock | Apr 2004 | B1 |
| 6727917 | Chew et al. | Apr 2004 | B1 |
| 6728530 | Heinonen et al. | Apr 2004 | B1 |
| 6728786 | Hawkins et al. | Apr 2004 | B2 |
| 6732101 | Cook | May 2004 | B1 |
| 6732158 | Hesselink et al. | May 2004 | B1 |
| 6735591 | Khan | May 2004 | B2 |
| 6741232 | Siedlikowski et al. | May 2004 | B1 |
| 6741855 | Martin et al. | May 2004 | B1 |
| 6742015 | Bowman-Amuah | May 2004 | B1 |
| 6742059 | Todd et al. | May 2004 | B1 |
| 6745024 | DeJaco et al. | Jun 2004 | B1 |
| 6745326 | Wary | Jun 2004 | B1 |
| 6756882 | Benes et al. | Jun 2004 | B2 |
| 6757362 | Cooper et al. | Jun 2004 | B1 |
| 6757696 | Multer et al. | Jun 2004 | B2 |
| 6757708 | Craig et al. | Jun 2004 | B1 |
| 6760916 | Holtz et al. | Jul 2004 | B2 |
| 6771294 | Pulli et al. | Aug 2004 | B1 |
| 6775362 | Ransom | Aug 2004 | B1 |
| 6779019 | Mousseau et al. | Aug 2004 | B1 |
| 6782409 | Yoshida | Aug 2004 | B1 |
| 6785868 | Raff | Aug 2004 | B1 |
| 6785906 | Gaughan et al. | Aug 2004 | B1 |
| 6799190 | Boothby | Sep 2004 | B1 |
| 6804707 | Ronning | Oct 2004 | B1 |
| 6810405 | LaRue et al. | Oct 2004 | B1 |
| 6816849 | Halt, Jr. | Nov 2004 | B1 |
| 6820088 | Hind et al. | Nov 2004 | B1 |
| 6820204 | Desai et al. | Nov 2004 | B1 |
| 6829487 | Eiden et al. | Dec 2004 | B2 |
| 6834195 | Brandenberg et al. | Dec 2004 | B2 |
| 6845383 | Kraenzel et al. | Jan 2005 | B1 |
| 6847974 | Wachtel | Jan 2005 | B2 |
| 6850757 | Watanabe et al. | Feb 2005 | B2 |
| 6859212 | Kumar et al. | Feb 2005 | B2 |
| 6867774 | Halmshaw et al. | Mar 2005 | B1 |
| 6868447 | Slaughter et al. | Mar 2005 | B1 |
| 6871220 | Rajan et al. | Mar 2005 | B1 |
| 6871236 | Fishman et al. | Mar 2005 | B2 |
| 6873688 | Aarnio | Mar 2005 | B1 |
| 6874017 | Inoue et al. | Mar 2005 | B1 |
| 6879985 | Deguchi et al. | Apr 2005 | B2 |
| 6886030 | Easterbrook et al. | Apr 2005 | B1 |
| 6892070 | Warrier et al. | May 2005 | B2 |
| 6892196 | Hughes | May 2005 | B1 |
| 6895394 | Kremer et al. | May 2005 | B1 |
| 6895558 | Loveland | May 2005 | B1 |
| 6898427 | Griffith et al. | May 2005 | B1 |
| 6912562 | Krishnamurthy et al. | Jun 2005 | B1 |
| 6922547 | O'Neill et al. | Jul 2005 | B2 |
| 6922721 | Minborg et al. | Jul 2005 | B1 |
| 6925477 | Champagne et al. | Aug 2005 | B1 |
| 6931529 | Kunzinger | Aug 2005 | B2 |
| 6938079 | Anderson et al. | Aug 2005 | B1 |
| 6938100 | Kang | Aug 2005 | B2 |
| 6941351 | Vetrivelkumaran et al. | Sep 2005 | B2 |
| 6944447 | Portman et al. | Sep 2005 | B2 |
| 6944662 | Devine et al. | Sep 2005 | B2 |
| 6947770 | Rydbeck | Sep 2005 | B2 |
| 6954754 | Peng | Oct 2005 | B2 |
| 6957397 | Hawkins et al. | Oct 2005 | B1 |
| 6965917 | Aloni et al. | Nov 2005 | B1 |
| 6965968 | Touboul | Nov 2005 | B1 |
| 6966058 | Earl et al. | Nov 2005 | B2 |
| 6968175 | Raivisto et al. | Nov 2005 | B2 |
| 6970879 | Gilmour | Nov 2005 | B1 |
| 6972682 | Lareau et al. | Dec 2005 | B2 |
| 6973299 | Apfel | Dec 2005 | B2 |
| 6981041 | Araujo et al. | Dec 2005 | B2 |
| 6981047 | Hanson et al. | Dec 2005 | B2 |
| 6985933 | Singhal et al. | Jan 2006 | B1 |
| 6985983 | Pellegrino et al. | Jan 2006 | B2 |
| 6986061 | Kunzinger | Jan 2006 | B1 |
| 6987734 | Hundemer | Jan 2006 | B2 |
| 6990472 | Rosenhaft et al. | Jan 2006 | B2 |
| 6993326 | Link, II et al. | Jan 2006 | B2 |
| 6993327 | Mathis | Jan 2006 | B2 |
| 6996627 | Carden | Feb 2006 | B1 |
| 6999753 | Beckmann et al. | Feb 2006 | B2 |
| 7016710 | Carmeli et al. | Mar 2006 | B2 |
| 7020685 | Chen et al. | Mar 2006 | B1 |
| 7024491 | Hanmann et al. | Apr 2006 | B1 |
| 7026984 | Thandu et al. | Apr 2006 | B1 |
| 7032242 | Grabelsky et al. | Apr 2006 | B1 |
| 7035630 | Knowles | Apr 2006 | B2 |
| 7046993 | Haaramo et al. | May 2006 | B2 |
| 7047202 | Jaipuria et al. | May 2006 | B2 |
| 7062024 | Kreckel et al. | Jun 2006 | B2 |
| 7069308 | Abrams | Jun 2006 | B2 |
| 7072678 | Allison | Jul 2006 | B2 |
| 7079499 | Akhtar et al. | Jul 2006 | B1 |
| 7080371 | Arnaiz et al. | Jul 2006 | B1 |
| 7082316 | Eiden et al. | Jul 2006 | B2 |
| 7085260 | Karaul et al. | Aug 2006 | B2 |
| 7085365 | Kauppinen | Aug 2006 | B2 |
| 7096030 | Huomo | Aug 2006 | B2 |
| 7100821 | Rasti | Sep 2006 | B2 |
| 7103432 | Drader et al. | Sep 2006 | B2 |
| 7116682 | Waclawsky et al. | Oct 2006 | B1 |
| 7120692 | Hesselink et al. | Oct 2006 | B2 |
| 7120928 | Sheth et al. | Oct 2006 | B2 |
| 7124320 | Wipfel | Oct 2006 | B1 |
| 7127492 | Calo et al. | Oct 2006 | B1 |
| 7130839 | Boreham et al. | Oct 2006 | B2 |
| 7136645 | Hanson et al. | Nov 2006 | B2 |
| 7139555 | Apfel | Nov 2006 | B2 |
| 7139565 | Fiatal et al. | Nov 2006 | B2 |
| 7140549 | de Jong | Nov 2006 | B2 |
| 7146645 | Hellsten et al. | Dec 2006 | B1 |
| 7149780 | Quine et al. | Dec 2006 | B2 |
| 7149789 | Slivka et al. | Dec 2006 | B2 |
| 7149959 | Jones et al. | Dec 2006 | B1 |
| 7162241 | Kim et al. | Jan 2007 | B2 |
| 7165727 | de Jong | Jan 2007 | B2 |
| 7172118 | Urken | Feb 2007 | B2 |
| 7177912 | Ignatoff et al. | Feb 2007 | B1 |
| 7181212 | Hogan et al. | Feb 2007 | B2 |
| 7181228 | Boesch | Feb 2007 | B2 |
| 7184790 | Dorenbosch et al. | Feb 2007 | B2 |
| 7185362 | Hawkes et al. | Feb 2007 | B2 |
| 7194273 | Vaudreuil | Mar 2007 | B2 |
| 7200390 | Henager et al. | Apr 2007 | B1 |
| 7203733 | Bern | Apr 2007 | B1 |
| 7206806 | Pineau | Apr 2007 | B2 |
| 7209757 | Naghian et al. | Apr 2007 | B2 |
| 7210121 | Xia et al. | Apr 2007 | B2 |
| 7219139 | Martin et al. | May 2007 | B2 |
| 7219222 | Durbin et al. | May 2007 | B1 |
| 7224957 | Spector | May 2007 | B2 |
| 7231206 | Cudak et al. | Jun 2007 | B2 |
| 7233795 | Ryden | Jun 2007 | B1 |
| 7234111 | Chu et al. | Jun 2007 | B2 |
| 7239877 | Corneille et al. | Jul 2007 | B2 |
| 7240095 | Lewis | Jul 2007 | B1 |
| 7242680 | Gallant | Jul 2007 | B2 |
| 7245926 | Liao et al. | Jul 2007 | B2 |
| 7249370 | Kodama et al. | Jul 2007 | B2 |
| 7257391 | Burgess et al. | Aug 2007 | B2 |
| 7257639 | Li et al. | Aug 2007 | B1 |
| 7259666 | Hermsmeyer et al. | Aug 2007 | B1 |
| 7260552 | Riera Jorba et al. | Aug 2007 | B2 |
| 7260590 | Williams | Aug 2007 | B1 |
| 7260651 | Parrella, Sr. et al. | Aug 2007 | B2 |
| 7272830 | de Jong | Sep 2007 | B2 |
| 7274783 | Yoakum et al. | Sep 2007 | B2 |
| 7277408 | Sorsa | Oct 2007 | B2 |
| 7284664 | Ivchenko et al. | Oct 2007 | B1 |
| 7289792 | Turunen | Oct 2007 | B1 |
| 7289964 | Bowman-Amuah | Oct 2007 | B1 |
| 7289971 | O'Neil et al. | Oct 2007 | B1 |
| 7293107 | Hanson et al. | Nov 2007 | B1 |
| 7295853 | Jin et al. | Nov 2007 | B2 |
| 7296155 | Trostle et al. | Nov 2007 | B1 |
| 7305252 | Britt et al. | Dec 2007 | B2 |
| 7305700 | Boynton et al. | Dec 2007 | B2 |
| 7310350 | Shao et al. | Dec 2007 | B1 |
| 7310729 | Gordon et al. | Dec 2007 | B2 |
| 7324473 | Corneille et al. | Jan 2008 | B2 |
| 7337219 | Meenan et al. | Feb 2008 | B1 |
| 7343396 | Kausik et al. | Mar 2008 | B2 |
| 7349871 | Labrou et al. | Mar 2008 | B2 |
| 7353258 | Washburn | Apr 2008 | B2 |
| 7353274 | Rouhi et al. | Apr 2008 | B1 |
| 7359720 | Hartmaier et al. | Apr 2008 | B2 |
| 7373386 | Gardner et al. | May 2008 | B2 |
| 7373661 | Smith et al. | May 2008 | B2 |
| 7374099 | de Jong | May 2008 | B2 |
| 7376701 | Bhargava et al. | May 2008 | B2 |
| 7382879 | Miller | Jun 2008 | B1 |
| 7383339 | Meenan et al. | Jun 2008 | B1 |
| 7388950 | Elsey et al. | Jun 2008 | B2 |
| 7389412 | Sharma et al. | Jun 2008 | B2 |
| 7392483 | Wong et al. | Jun 2008 | B2 |
| 7395329 | Holt et al. | Jul 2008 | B1 |
| 7398271 | Borkovsky et al. | Jul 2008 | B1 |
| 7430609 | Brown et al. | Sep 2008 | B2 |
| 7441271 | Fiatal et al. | Oct 2008 | B2 |
| 7443847 | Albert et al. | Oct 2008 | B1 |
| 7461071 | Fitzpatrick et al. | Dec 2008 | B2 |
| 7465231 | Lewin et al. | Dec 2008 | B2 |
| 7469125 | Nurmi | Dec 2008 | B2 |
| 7472424 | Evans et al. | Dec 2008 | B2 |
| 7483036 | Moore | Jan 2009 | B2 |
| 7499537 | Elsey et al. | Mar 2009 | B2 |
| 7502615 | Wilhoite et al. | Mar 2009 | B2 |
| 7519042 | Gorday et al. | Apr 2009 | B2 |
| 7532571 | Price et al. | May 2009 | B1 |
| 7539665 | Mendez | May 2009 | B2 |
| 7548947 | Kasriel et al. | Jun 2009 | B2 |
| 7548969 | Tripp et al. | Jun 2009 | B2 |
| 7551900 | Kang et al. | Jun 2009 | B2 |
| 7555291 | Wassingbo | Jun 2009 | B2 |
| 7567575 | Chen et al. | Jul 2009 | B2 |
| 7574208 | Hanson et al. | Aug 2009 | B2 |
| 7575171 | Lev | Aug 2009 | B2 |
| 7584294 | Plamondon | Sep 2009 | B2 |
| 7587482 | Henderson et al. | Sep 2009 | B2 |
| 7587510 | Klager et al. | Sep 2009 | B1 |
| 7587608 | Haller et al. | Sep 2009 | B2 |
| 7589223 | Bildstein et al. | Sep 2009 | B2 |
| 7593714 | Schultz et al. | Sep 2009 | B2 |
| 7596608 | Alexander et al. | Sep 2009 | B2 |
| 7596791 | Wei et al. | Sep 2009 | B2 |
| 7613792 | Zervas et al. | Nov 2009 | B2 |
| 7630986 | Herz et al. | Dec 2009 | B1 |
| 7634558 | Mangal et al. | Dec 2009 | B1 |
| 7636763 | Fein et al. | Dec 2009 | B1 |
| 7643818 | Backholm et al. | Jan 2010 | B2 |
| 7644166 | Appelman et al. | Jan 2010 | B2 |
| 7647047 | Moghaddam et al. | Jan 2010 | B2 |
| 7647561 | Zondervan et al. | Jan 2010 | B2 |
| 7650416 | Wu et al. | Jan 2010 | B2 |
| 7650432 | Bosworth et al. | Jan 2010 | B2 |
| 7672291 | Wang | Mar 2010 | B2 |
| 7672439 | Appelman et al. | Mar 2010 | B2 |
| 7680281 | Fiatal et al. | Mar 2010 | B2 |
| 7680520 | Ruuska et al. | Mar 2010 | B2 |
| 7684346 | Valli | Mar 2010 | B2 |
| 7689664 | Karlberg | Mar 2010 | B2 |
| 7693555 | Srinivasan et al. | Apr 2010 | B2 |
| 7693944 | Appelman et al. | Apr 2010 | B2 |
| 7694008 | Chang et al. | Apr 2010 | B2 |
| 7706781 | Backholm et al. | Apr 2010 | B2 |
| 7707573 | Marmaros et al. | Apr 2010 | B1 |
| 7716710 | Everson et al. | May 2010 | B1 |
| 7751803 | Vialen et al. | Jul 2010 | B2 |
| 7752633 | Fleming | Jul 2010 | B1 |
| 7757956 | Koenck et al. | Jul 2010 | B2 |
| 7769395 | Fiatal et al. | Aug 2010 | B2 |
| 7769400 | Backholm et al. | Aug 2010 | B2 |
| 7769805 | Barnes et al. | Aug 2010 | B1 |
| 7770223 | Shevenell et al. | Aug 2010 | B2 |
| 7778792 | Huang et al. | Aug 2010 | B2 |
| 7783757 | Plamondon | Aug 2010 | B2 |
| 7796742 | Sutaria et al. | Sep 2010 | B1 |
| 7797064 | Loomis et al. | Sep 2010 | B2 |
| 7809818 | Plamondon | Oct 2010 | B2 |
| 7827055 | Snodgrass et al. | Nov 2010 | B1 |
| 7827597 | Boynton et al. | Nov 2010 | B2 |
| 7849507 | Bloch et al. | Dec 2010 | B1 |
| 7853563 | Alvarado et al. | Dec 2010 | B2 |
| 7865618 | Howell et al. | Jan 2011 | B2 |
| 7873609 | Kim et al. | Jan 2011 | B2 |
| 7873705 | Kalish | Jan 2011 | B2 |
| 7877703 | Fleming | Jan 2011 | B1 |
| 7877807 | Shipp | Jan 2011 | B2 |
| 7881745 | Rao et al. | Feb 2011 | B1 |
| 7899996 | Levin-Michael | Mar 2011 | B1 |
| 7904548 | Shah et al. | Mar 2011 | B2 |
| 7908656 | Mu | Mar 2011 | B1 |
| 7917468 | Ariel et al. | Mar 2011 | B2 |
| 7917505 | van Gent et al. | Mar 2011 | B2 |
| 7921167 | Shroff et al. | Apr 2011 | B2 |
| 7930416 | Miller et al. | Apr 2011 | B2 |
| 7933929 | McClendon et al. | Apr 2011 | B1 |
| 7937091 | Roman et al. | May 2011 | B2 |
| 7941582 | Bushell et al. | May 2011 | B2 |
| 7958238 | Batz et al. | Jun 2011 | B1 |
| 7970860 | Kline et al. | Jun 2011 | B2 |
| 7970939 | Satish et al. | Jun 2011 | B1 |
| 7996487 | Snyder | Aug 2011 | B2 |
| 7996876 | Everson et al. | Aug 2011 | B1 |
| 8005891 | Knowles et al. | Aug 2011 | B2 |
| 8010082 | Sutaria et al. | Aug 2011 | B2 |
| 8032409 | Mikurak | Oct 2011 | B1 |
| 8056136 | Zaitsev | Nov 2011 | B1 |
| 8060154 | Bali et al. | Nov 2011 | B1 |
| 8064583 | Sutaria et al. | Nov 2011 | B1 |
| 8069166 | Alvarado et al. | Nov 2011 | B2 |
| 8074162 | Cohen | Dec 2011 | B1 |
| 8078158 | Backholm | Dec 2011 | B2 |
| 8087085 | Hu et al. | Dec 2011 | B2 |
| 8107921 | Fiatal | Jan 2012 | B2 |
| 8116214 | Backholm et al. | Feb 2012 | B2 |
| 8127342 | Boynton et al. | Feb 2012 | B2 |
| 8131763 | Tuscano et al. | Mar 2012 | B2 |
| 8160062 | Qian et al. | Apr 2012 | B2 |
| 8166164 | Luna et al. | Apr 2012 | B1 |
| 8190680 | Spilo et al. | May 2012 | B2 |
| 8190701 | Luna et al. | May 2012 | B2 |
| 8194680 | Brandwine et al. | Jun 2012 | B1 |
| 8195196 | Haran et al. | Jun 2012 | B2 |
| 8204953 | Luna et al. | Jun 2012 | B2 |
| 8209709 | Fleming | Jun 2012 | B2 |
| 8214813 | Harris et al. | Jul 2012 | B2 |
| 8239915 | Satish et al. | Aug 2012 | B1 |
| 8260852 | Cselle | Sep 2012 | B1 |
| 8291076 | Luna et al. | Oct 2012 | B2 |
| 8316098 | Luna et al. | Nov 2012 | B2 |
| 8326985 | Luna et al. | Dec 2012 | B2 |
| 8340633 | Rege et al. | Dec 2012 | B1 |
| 8356080 | Luna et al. | Jan 2013 | B2 |
| 8364181 | Backholm et al. | Jan 2013 | B2 |
| 8412675 | Alvarado et al. | Apr 2013 | B2 |
| 8417823 | Luna et al. | Apr 2013 | B2 |
| 8438633 | Backholm et al. | May 2013 | B1 |
| 8484314 | Luna et al. | Jul 2013 | B2 |
| 8522086 | Garrett | Aug 2013 | B1 |
| 8539040 | Luna et al. | Sep 2013 | B2 |
| 8547834 | Reeves et al. | Oct 2013 | B1 |
| 8606290 | Gerber et al. | Dec 2013 | B2 |
| 8621075 | Luna | Dec 2013 | B2 |
| 8635339 | Luna | Jan 2014 | B2 |
| 8831658 | Meylan et al. | Sep 2014 | B2 |
| 8943204 | Caldeira de Andrada et al. | Jan 2015 | B2 |
| 20010005364 | Kang | Jun 2001 | A1 |
| 20010009025 | Ahonen | Jul 2001 | A1 |
| 20010010046 | Muyres et al. | Jul 2001 | A1 |
| 20010013069 | Shah | Aug 2001 | A1 |
| 20010013088 | Matsumoto | Aug 2001 | A1 |
| 20010023414 | Kumar et al. | Sep 2001 | A1 |
| 20010032254 | Hawkins | Oct 2001 | A1 |
| 20010034225 | Gupte et al. | Oct 2001 | A1 |
| 20010034244 | Calder et al. | Oct 2001 | A1 |
| 20010037453 | Mitty et al. | Nov 2001 | A1 |
| 20010039191 | Maierhofer | Nov 2001 | A1 |
| 20010041566 | Xanthos et al. | Nov 2001 | A1 |
| 20010042009 | Montague | Nov 2001 | A1 |
| 20010042099 | Peng | Nov 2001 | A1 |
| 20010043148 | Stewart | Nov 2001 | A1 |
| 20010052052 | Peng | Dec 2001 | A1 |
| 20010053687 | Sivula | Dec 2001 | A1 |
| 20020002478 | Swart et al. | Jan 2002 | A1 |
| 20020002591 | Ketola | Jan 2002 | A1 |
| 20020004746 | Ferber et al. | Jan 2002 | A1 |
| 20020007303 | Brookler et al. | Jan 2002 | A1 |
| 20020013727 | Lee | Jan 2002 | A1 |
| 20020019225 | Miyashita | Feb 2002 | A1 |
| 20020019812 | Board et al. | Feb 2002 | A1 |
| 20020019830 | Hamberg et al. | Feb 2002 | A1 |
| 20020032671 | Iinuma | Mar 2002 | A1 |
| 20020035556 | Shah et al. | Mar 2002 | A1 |
| 20020035617 | Lynch et al. | Mar 2002 | A1 |
| 20020038253 | Seaman et al. | Mar 2002 | A1 |
| 20020042875 | Shukla | Apr 2002 | A1 |
| 20020049828 | Pekarek-Kostka | Apr 2002 | A1 |
| 20020049857 | Farber et al. | Apr 2002 | A1 |
| 20020052965 | Dowling | May 2002 | A1 |
| 20020053078 | Holtz et al. | May 2002 | A1 |
| 20020055351 | Elsey et al. | May 2002 | A1 |
| 20020059201 | Work | May 2002 | A1 |
| 20020059251 | Stern et al. | May 2002 | A1 |
| 20020059457 | Ballard et al. | May 2002 | A1 |
| 20020062467 | Hunzinger | May 2002 | A1 |
| 20020065110 | Enns et al. | May 2002 | A1 |
| 20020068559 | Sharma et al. | Jun 2002 | A1 |
| 20020069037 | Hendrickson et al. | Jun 2002 | A1 |
| 20020073207 | Widger et al. | Jun 2002 | A1 |
| 20020077077 | Rezvani et al. | Jun 2002 | A1 |
| 20020077084 | Zellner et al. | Jun 2002 | A1 |
| 20020078300 | Dharap | Jun 2002 | A1 |
| 20020078384 | Hippelainen | Jun 2002 | A1 |
| 20020087549 | Mostafa | Jul 2002 | A1 |
| 20020087679 | Pulley et al. | Jul 2002 | A1 |
| 20020087723 | Williams et al. | Jul 2002 | A1 |
| 20020087883 | Wohlgemuth et al. | Jul 2002 | A1 |
| 20020089542 | Imamura | Jul 2002 | A1 |
| 20020091921 | Kunzinger | Jul 2002 | A1 |
| 20020095319 | Swart et al. | Jul 2002 | A1 |
| 20020095328 | Swart et al. | Jul 2002 | A1 |
| 20020095391 | Swart et al. | Jul 2002 | A1 |
| 20020095399 | Devine et al. | Jul 2002 | A1 |
| 20020098855 | Hartmaier et al. | Jul 2002 | A1 |
| 20020099613 | Swart et al. | Jul 2002 | A1 |
| 20020099809 | Lee | Jul 2002 | A1 |
| 20020101975 | Tiburtius et al. | Aug 2002 | A1 |
| 20020103008 | Rahn et al. | Aug 2002 | A1 |
| 20020103934 | Fishman et al. | Aug 2002 | A1 |
| 20020107042 | Murnaghan et al. | Aug 2002 | A1 |
| 20020107944 | Bai et al. | Aug 2002 | A1 |
| 20020107985 | Hwang et al. | Aug 2002 | A1 |
| 20020108121 | Alao et al. | Aug 2002 | A1 |
| 20020116499 | Ennus et al. | Aug 2002 | A1 |
| 20020116501 | Ho et al. | Aug 2002 | A1 |
| 20020120388 | Bullock | Aug 2002 | A1 |
| 20020120766 | Okajima et al. | Aug 2002 | A1 |
| 20020120779 | Teeple et al. | Aug 2002 | A1 |
| 20020126701 | Requena | Sep 2002 | A1 |
| 20020128908 | Levin et al. | Sep 2002 | A1 |
| 20020129088 | Zhou et al. | Sep 2002 | A1 |
| 20020133504 | Vlahos et al. | Sep 2002 | A1 |
| 20020133598 | Strahm et al. | Sep 2002 | A1 |
| 20020138601 | Piponius et al. | Sep 2002 | A1 |
| 20020144109 | Benantar et al. | Oct 2002 | A1 |
| 20020146129 | Kaplan | Oct 2002 | A1 |
| 20020152379 | Gefwert et al. | Oct 2002 | A1 |
| 20020155848 | Suryanarayana | Oct 2002 | A1 |
| 20020156839 | Peterson et al. | Oct 2002 | A1 |
| 20020158908 | Vaajala et al. | Oct 2002 | A1 |
| 20020161587 | Pitts, III et al. | Oct 2002 | A1 |
| 20020161925 | Munger et al. | Oct 2002 | A1 |
| 20020161928 | Ndili | Oct 2002 | A1 |
| 20020164977 | Link, II et al. | Nov 2002 | A1 |
| 20020165988 | Khan et al. | Nov 2002 | A1 |
| 20020167484 | Hatanaka et al. | Nov 2002 | A1 |
| 20020174189 | Peng | Nov 2002 | A1 |
| 20020174208 | Morlitz | Nov 2002 | A1 |
| 20020186848 | Shaik | Dec 2002 | A1 |
| 20020188940 | Breckner et al. | Dec 2002 | A1 |
| 20020193094 | Lawless et al. | Dec 2002 | A1 |
| 20020194183 | Yoakum et al. | Dec 2002 | A1 |
| 20020194207 | Bartlett et al. | Dec 2002 | A1 |
| 20020194209 | Bolosky et al. | Dec 2002 | A1 |
| 20020198027 | Rydbeck | Dec 2002 | A1 |
| 20020198991 | Gopalakrishnan et al. | Dec 2002 | A1 |
| 20030005151 | Ullman et al. | Jan 2003 | A1 |
| 20030009571 | Bavadekar | Jan 2003 | A1 |
| 20030012147 | Buckman et al. | Jan 2003 | A1 |
| 20030014491 | Horvitz et al. | Jan 2003 | A1 |
| 20030021400 | Grandgent et al. | Jan 2003 | A1 |
| 20030022662 | Mittal | Jan 2003 | A1 |
| 20030023692 | Moroo | Jan 2003 | A1 |
| 20030023975 | Schrader et al. | Jan 2003 | A1 |
| 20030025599 | Monroe | Feb 2003 | A1 |
| 20030028430 | Zimmerman | Feb 2003 | A1 |
| 20030028441 | Barsness et al. | Feb 2003 | A1 |
| 20030037094 | Douceur et al. | Feb 2003 | A1 |
| 20030046433 | Luzzatti et al. | Mar 2003 | A1 |
| 20030046586 | Bheemarasetti et al. | Mar 2003 | A1 |
| 20030046587 | Bheemarasetti et al. | Mar 2003 | A1 |
| 20030050041 | Wu | Mar 2003 | A1 |
| 20030051142 | Hidalgo et al. | Mar 2003 | A1 |
| 20030054810 | Chen et al. | Mar 2003 | A1 |
| 20030055555 | Knockeart et al. | Mar 2003 | A1 |
| 20030056096 | Albert et al. | Mar 2003 | A1 |
| 20030060188 | Gidron et al. | Mar 2003 | A1 |
| 20030063120 | Wong et al. | Apr 2003 | A1 |
| 20030065738 | Yang et al. | Apr 2003 | A1 |
| 20030065739 | Shnier | Apr 2003 | A1 |
| 20030065802 | Vitikainen et al. | Apr 2003 | A1 |
| 20030069816 | Ung et al. | Apr 2003 | A1 |
| 20030070061 | Wong et al. | Apr 2003 | A1 |
| 20030072451 | Pimentel et al. | Apr 2003 | A1 |
| 20030078880 | Alley et al. | Apr 2003 | A1 |
| 20030084165 | Kjellberg et al. | May 2003 | A1 |
| 20030084361 | Lawrence et al. | May 2003 | A1 |
| 20030088629 | Berkowitz et al. | May 2003 | A1 |
| 20030093341 | Millard et al. | May 2003 | A1 |
| 20030093691 | Simon et al. | May 2003 | A1 |
| 20030096608 | Mortensen et al. | May 2003 | A1 |
| 20030097381 | Detweiler et al. | May 2003 | A1 |
| 20030100321 | Rao et al. | May 2003 | A1 |
| 20030100326 | Grube et al. | May 2003 | A1 |
| 20030105837 | Kamen et al. | Jun 2003 | A1 |
| 20030117432 | Kautto-Kiovula et al. | Jun 2003 | A1 |
| 20030120685 | Duncombe et al. | Jun 2003 | A1 |
| 20030125023 | Fishler | Jul 2003 | A1 |
| 20030126216 | Avila et al. | Jul 2003 | A1 |
| 20030126233 | Bryers et al. | Jul 2003 | A1 |
| 20030130984 | Quinlan et al. | Jul 2003 | A1 |
| 20030145038 | Bin Tariq et al. | Jul 2003 | A1 |
| 20030146934 | Bailey et al. | Aug 2003 | A1 |
| 20030153338 | Herz et al. | Aug 2003 | A1 |
| 20030154212 | Schirmer et al. | Aug 2003 | A1 |
| 20030156146 | Suomela et al. | Aug 2003 | A1 |
| 20030157947 | Fiatal et al. | Aug 2003 | A1 |
| 20030169262 | Lavelle et al. | Sep 2003 | A1 |
| 20030172112 | Vignaud | Sep 2003 | A1 |
| 20030177281 | McQuillan et al. | Sep 2003 | A1 |
| 20030182420 | Jones et al. | Sep 2003 | A1 |
| 20030182431 | Sturniolo et al. | Sep 2003 | A1 |
| 20030182441 | Andrew et al. | Sep 2003 | A1 |
| 20030187984 | Banavar et al. | Oct 2003 | A1 |
| 20030204605 | Hudson et al. | Oct 2003 | A1 |
| 20030204708 | Hulme et al. | Oct 2003 | A1 |
| 20030208529 | Pendyala et al. | Nov 2003 | A1 |
| 20030208559 | Velline et al. | Nov 2003 | A1 |
| 20030210666 | Trossen et al. | Nov 2003 | A1 |
| 20030211845 | Lohtia et al. | Nov 2003 | A1 |
| 20030217098 | Bobde et al. | Nov 2003 | A1 |
| 20030217142 | Bobde et al. | Nov 2003 | A1 |
| 20030223554 | Zhang | Dec 2003 | A1 |
| 20030227487 | Hugh | Dec 2003 | A1 |
| 20030227745 | Khoo | Dec 2003 | A1 |
| 20030229549 | Wolinsky et al. | Dec 2003 | A1 |
| 20030233329 | Laraki et al. | Dec 2003 | A1 |
| 20030235308 | Boynton et al. | Dec 2003 | A1 |
| 20030236857 | Takase et al. | Dec 2003 | A1 |
| 20030236981 | Marmigere et al. | Dec 2003 | A1 |
| 20040002324 | Juntunen et al. | Jan 2004 | A1 |
| 20040006630 | Friend et al. | Jan 2004 | A1 |
| 20040010590 | Manzano | Jan 2004 | A1 |
| 20040015504 | Ahad et al. | Jan 2004 | A1 |
| 20040024795 | Hind et al. | Feb 2004 | A1 |
| 20040024892 | Creswell et al. | Feb 2004 | A1 |
| 20040027326 | Hays et al. | Feb 2004 | A1 |
| 20040027375 | Ellis et al. | Feb 2004 | A1 |
| 20040027378 | Hays et al. | Feb 2004 | A1 |
| 20040030620 | Benjamin et al. | Feb 2004 | A1 |
| 20040030749 | Bowman-Amuah | Feb 2004 | A1 |
| 20040043770 | Amit et al. | Mar 2004 | A1 |
| 20040047356 | Bauer | Mar 2004 | A1 |
| 20040049579 | Ims et al. | Mar 2004 | A1 |
| 20040049599 | Friend et al. | Mar 2004 | A1 |
| 20040051715 | Brokenshire et al. | Mar 2004 | A1 |
| 20040054711 | Multer | Mar 2004 | A1 |
| 20040054739 | Friend et al. | Mar 2004 | A1 |
| 20040054854 | Thiyagaranjan et al. | Mar 2004 | A1 |
| 20040064445 | Pfleging et al. | Apr 2004 | A1 |
| 20040064488 | Sinha | Apr 2004 | A1 |
| 20040068579 | Marmigere et al. | Apr 2004 | A1 |
| 20040068698 | Wu et al. | Apr 2004 | A1 |
| 20040071146 | Belling | Apr 2004 | A1 |
| 20040072559 | Kakumaru et al. | Apr 2004 | A1 |
| 20040073476 | Donahue et al. | Apr 2004 | A1 |
| 20040073651 | Beaulieu et al. | Apr 2004 | A1 |
| 20040073707 | Dillon | Apr 2004 | A1 |
| 20040073867 | Kausik et al. | Apr 2004 | A1 |
| 20040075675 | Raivisto et al. | Apr 2004 | A1 |
| 20040075695 | Chew et al. | Apr 2004 | A1 |
| 20040078814 | Allen | Apr 2004 | A1 |
| 20040080515 | Hagiwara | Apr 2004 | A1 |
| 20040081088 | Schinner et al. | Apr 2004 | A1 |
| 20040082346 | Skytt et al. | Apr 2004 | A1 |
| 20040085909 | Soliman | May 2004 | A1 |
| 20040085980 | Lee | May 2004 | A1 |
| 20040098625 | Lagadec et al. | May 2004 | A1 |
| 20040103147 | Flesher et al. | May 2004 | A1 |
| 20040107319 | D'Orto et al. | Jun 2004 | A1 |
| 20040110497 | Little | Jun 2004 | A1 |
| 20040120262 | Hirose et al. | Jun 2004 | A1 |
| 20040120323 | Viikari et al. | Jun 2004 | A1 |
| 20040122907 | Chou et al. | Jun 2004 | A1 |
| 20040123095 | Marshall | Jun 2004 | A1 |
| 20040123304 | Black et al. | Jun 2004 | A1 |
| 20040127214 | Reddy et al. | Jul 2004 | A1 |
| 20040128375 | Rockwell | Jul 2004 | A1 |
| 20040133626 | Herrero et al. | Jul 2004 | A1 |
| 20040138931 | Hope et al. | Jul 2004 | A1 |
| 20040141011 | Smethers et al. | Jul 2004 | A1 |
| 20040147223 | Cho | Jul 2004 | A1 |
| 20040147248 | Will | Jul 2004 | A1 |
| 20040147262 | Lescuyer et al. | Jul 2004 | A1 |
| 20040148375 | Levett et al. | Jul 2004 | A1 |
| 20040151186 | Akama | Aug 2004 | A1 |
| 20040152450 | Kouznetsov et al. | Aug 2004 | A1 |
| 20040153537 | Rezvani et al. | Aug 2004 | A1 |
| 20040158611 | Daniell et al. | Aug 2004 | A1 |
| 20040162890 | Ohta | Aug 2004 | A1 |
| 20040167966 | Lee et al. | Aug 2004 | A1 |
| 20040170257 | Gross et al. | Sep 2004 | A1 |
| 20040172481 | Engstrom | Sep 2004 | A1 |
| 20040176128 | Grabelsky et al. | Sep 2004 | A1 |
| 20040177369 | Akins, III | Sep 2004 | A1 |
| 20040179513 | Smith et al. | Sep 2004 | A1 |
| 20040181550 | Warsta et al. | Sep 2004 | A1 |
| 20040184475 | Meier | Sep 2004 | A1 |
| 20040186889 | Washburn | Sep 2004 | A1 |
| 20040186902 | Stewart | Sep 2004 | A1 |
| 20040189610 | Friend | Sep 2004 | A1 |
| 20040198344 | Pitt et al. | Oct 2004 | A1 |
| 20040199497 | Timmons | Oct 2004 | A1 |
| 20040199582 | Kucharewski et al. | Oct 2004 | A1 |
| 20040199649 | Tarnanen et al. | Oct 2004 | A1 |
| 20040199663 | Horvitz et al. | Oct 2004 | A1 |
| 20040204085 | Vargas et al. | Oct 2004 | A1 |
| 20040205248 | Little et al. | Oct 2004 | A1 |
| 20040205330 | Godfrey et al. | Oct 2004 | A1 |
| 20040209602 | Joyce et al. | Oct 2004 | A1 |
| 20040210639 | Ben-Yoseph et al. | Oct 2004 | A1 |
| 20040218609 | Foster et al. | Nov 2004 | A1 |
| 20040219940 | Kong et al. | Nov 2004 | A1 |
| 20040229609 | Yamaguchi | Nov 2004 | A1 |
| 20040230619 | Blanco et al. | Nov 2004 | A1 |
| 20040230739 | Tsern et al. | Nov 2004 | A1 |
| 20040233930 | Colby, Jr. | Nov 2004 | A1 |
| 20040236792 | Celik | Nov 2004 | A1 |
| 20040242209 | Kruis et al. | Dec 2004 | A1 |
| 20040252816 | Nicolas | Dec 2004 | A1 |
| 20040255126 | Reith | Dec 2004 | A1 |
| 20040258231 | Elsey et al. | Dec 2004 | A1 |
| 20040259535 | Elsey et al. | Dec 2004 | A1 |
| 20040259537 | Ackley | Dec 2004 | A1 |
| 20040260948 | Miyata et al. | Dec 2004 | A1 |
| 20040264396 | Ginzburg et al. | Dec 2004 | A1 |
| 20040266364 | Nguyen et al. | Dec 2004 | A1 |
| 20040268148 | Karjala et al. | Dec 2004 | A1 |
| 20050002501 | Elsey et al. | Jan 2005 | A1 |
| 20050002508 | Elsey et al. | Jan 2005 | A1 |
| 20050002509 | Elsey et al. | Jan 2005 | A1 |
| 20050002510 | Elsey et al. | Jan 2005 | A1 |
| 20050010694 | Ma et al. | Jan 2005 | A1 |
| 20050015432 | Cohen | Jan 2005 | A1 |
| 20050021750 | Abrams | Jan 2005 | A1 |
| 20050022000 | Inomata et al. | Jan 2005 | A1 |
| 20050022182 | Mittal | Jan 2005 | A1 |
| 20050027591 | Gailey et al. | Feb 2005 | A9 |
| 20050027716 | Apfel | Feb 2005 | A1 |
| 20050027869 | Johnson | Feb 2005 | A1 |
| 20050030913 | Roy | Feb 2005 | A1 |
| 20050033657 | Herrington et al. | Feb 2005 | A1 |
| 20050033812 | McCarthy et al. | Feb 2005 | A1 |
| 20050033926 | Dumont | Feb 2005 | A1 |
| 20050037741 | Gilbert | Feb 2005 | A1 |
| 20050038707 | Roever et al. | Feb 2005 | A1 |
| 20050038724 | Roever et al. | Feb 2005 | A1 |
| 20050038863 | Onyon et al. | Feb 2005 | A1 |
| 20050041584 | Lau et al. | Feb 2005 | A1 |
| 20050041793 | Fulton et al. | Feb 2005 | A1 |
| 20050044144 | Malik et al. | Feb 2005 | A1 |
| 20050044235 | Balahura et al. | Feb 2005 | A1 |
| 20050050222 | Packer | Mar 2005 | A1 |
| 20050054381 | Lee et al. | Mar 2005 | A1 |
| 20050055578 | Wright et al. | Mar 2005 | A1 |
| 20050063544 | Uusitalo et al. | Mar 2005 | A1 |
| 20050071489 | Parupudi et al. | Mar 2005 | A1 |
| 20050071511 | Chen | Mar 2005 | A1 |
| 20050071674 | Chou et al. | Mar 2005 | A1 |
| 20050073982 | Corneille et al. | Apr 2005 | A1 |
| 20050075109 | Neyret et al. | Apr 2005 | A1 |
| 20050076085 | Budd et al. | Apr 2005 | A1 |
| 20050076136 | Cho et al. | Apr 2005 | A1 |
| 20050076241 | Appelman | Apr 2005 | A1 |
| 20050080928 | Beverly et al. | Apr 2005 | A1 |
| 20050086385 | Rouleau | Apr 2005 | A1 |
| 20050086540 | Gunter et al. | Apr 2005 | A1 |
| 20050094625 | Bouat | May 2005 | A1 |
| 20050097225 | Glatt et al. | May 2005 | A1 |
| 20050097570 | Bomers | May 2005 | A1 |
| 20050099963 | Multer et al. | May 2005 | A1 |
| 20050101307 | Brugge et al. | May 2005 | A1 |
| 20050102257 | Onyon et al. | May 2005 | A1 |
| 20050102328 | Ring et al. | May 2005 | A1 |
| 20050102351 | Jiang et al. | May 2005 | A1 |
| 20050108322 | Kline et al. | May 2005 | A1 |
| 20050108427 | Datta | May 2005 | A1 |
| 20050117606 | Kim | Jun 2005 | A1 |
| 20050120082 | Hesselink et al. | Jun 2005 | A1 |
| 20050120084 | Hu et al. | Jun 2005 | A1 |
| 20050120181 | Arunagirinathan et al. | Jun 2005 | A1 |
| 20050122333 | Sumanaweera et al. | Jun 2005 | A1 |
| 20050124332 | Clark et al. | Jun 2005 | A1 |
| 20050125459 | Sutinen et al. | Jun 2005 | A1 |
| 20050138111 | Aton et al. | Jun 2005 | A1 |
| 20050138176 | Singh et al. | Jun 2005 | A1 |
| 20050138198 | May | Jun 2005 | A1 |
| 20050144219 | Terada | Jun 2005 | A1 |
| 20050147130 | Hurwitz et al. | Jul 2005 | A1 |
| 20050154698 | Ikezawa et al. | Jul 2005 | A1 |
| 20050154796 | Forsyth | Jul 2005 | A1 |
| 20050154836 | Steeley et al. | Jul 2005 | A1 |
| 20050155027 | Wei | Jul 2005 | A1 |
| 20050163048 | Arora et al. | Jul 2005 | A1 |
| 20050164703 | Huynh | Jul 2005 | A1 |
| 20050164721 | Eric Yeh et al. | Jul 2005 | A1 |
| 20050165909 | Cromer et al. | Jul 2005 | A1 |
| 20050170776 | Siorpaes | Aug 2005 | A1 |
| 20050183143 | Anderholm et al. | Aug 2005 | A1 |
| 20050188038 | Yabe | Aug 2005 | A1 |
| 20050188048 | Yuan et al. | Aug 2005 | A1 |
| 20050193036 | Phillips et al. | Sep 2005 | A1 |
| 20050193096 | Yu et al. | Sep 2005 | A1 |
| 20050198170 | LeMay et al. | Sep 2005 | A1 |
| 20050203966 | Labrou et al. | Sep 2005 | A1 |
| 20050210104 | Torvinen | Sep 2005 | A1 |
| 20050210125 | Li | Sep 2005 | A1 |
| 20050210150 | Bahl | Sep 2005 | A1 |
| 20050213511 | Reece et al. | Sep 2005 | A1 |
| 20050216295 | Abrahamsohn | Sep 2005 | A1 |
| 20050222891 | Chan et al. | Oct 2005 | A1 |
| 20050228812 | Hansmann et al. | Oct 2005 | A1 |
| 20050232295 | Young | Oct 2005 | A1 |
| 20050234860 | Roever et al. | Oct 2005 | A1 |
| 20050235214 | Shimizu et al. | Oct 2005 | A1 |
| 20050245241 | Durand et al. | Nov 2005 | A1 |
| 20050246139 | Rivenbark et al. | Nov 2005 | A1 |
| 20050248526 | Twerdahl et al. | Nov 2005 | A1 |
| 20050250452 | Walton et al. | Nov 2005 | A1 |
| 20050251555 | Little, II | Nov 2005 | A1 |
| 20050254443 | Campbell et al. | Nov 2005 | A1 |
| 20050256880 | Nam Koong et al. | Nov 2005 | A1 |
| 20050262220 | Ecklund et al. | Nov 2005 | A1 |
| 20050273804 | Preisman | Dec 2005 | A1 |
| 20050278307 | Battagin et al. | Dec 2005 | A1 |
| 20050278641 | Mansour et al. | Dec 2005 | A1 |
| 20050278647 | Leavitt et al. | Dec 2005 | A1 |
| 20050288006 | Apfel | Dec 2005 | A1 |
| 20060012672 | Schrader et al. | Jan 2006 | A1 |
| 20060020525 | Borelli et al. | Jan 2006 | A1 |
| 20060020580 | Dettinger et al. | Jan 2006 | A1 |
| 20060020715 | Jungck | Jan 2006 | A1 |
| 20060020804 | Schleifer et al. | Jan 2006 | A1 |
| 20060020947 | Hallamaa et al. | Jan 2006 | A1 |
| 20060021023 | Stewart et al. | Jan 2006 | A1 |
| 20060022048 | Johnson | Feb 2006 | A1 |
| 20060025169 | Maciocco et al. | Feb 2006 | A1 |
| 20060026580 | Cabillic et al. | Feb 2006 | A1 |
| 20060029062 | Rao et al. | Feb 2006 | A1 |
| 20060029063 | Rao et al. | Feb 2006 | A1 |
| 20060029064 | Rao et al. | Feb 2006 | A1 |
| 20060031114 | Zommers | Feb 2006 | A1 |
| 20060031300 | Kock et al. | Feb 2006 | A1 |
| 20060031365 | Kay et al. | Feb 2006 | A1 |
| 20060031428 | Wikman | Feb 2006 | A1 |
| 20060031522 | Soulhi et al. | Feb 2006 | A1 |
| 20060031785 | Raciborski | Feb 2006 | A1 |
| 20060031938 | Choi | Feb 2006 | A1 |
| 20060037071 | Rao et al. | Feb 2006 | A1 |
| 20060041717 | Rosker et al. | Feb 2006 | A1 |
| 20060045121 | Monk | Mar 2006 | A1 |
| 20060046686 | Hawkins et al. | Mar 2006 | A1 |
| 20060047844 | Deng | Mar 2006 | A1 |
| 20060048061 | Forlenza et al. | Mar 2006 | A1 |
| 20060052091 | Onyon et al. | Mar 2006 | A1 |
| 20060052137 | Randall et al. | Mar 2006 | A1 |
| 20060059495 | Spector | Mar 2006 | A1 |
| 20060063544 | Zhao et al. | Mar 2006 | A1 |
| 20060065716 | Peters | Mar 2006 | A1 |
| 20060069686 | Beyda et al. | Mar 2006 | A1 |
| 20060069687 | Cui et al. | Mar 2006 | A1 |
| 20060069715 | Vayssiere | Mar 2006 | A1 |
| 20060069742 | Segre | Mar 2006 | A1 |
| 20060069746 | Davis et al. | Mar 2006 | A1 |
| 20060073810 | Pyhalammi et al. | Apr 2006 | A1 |
| 20060074951 | Beier et al. | Apr 2006 | A1 |
| 20060075028 | Zager et al. | Apr 2006 | A1 |
| 20060084410 | Sutaria et al. | Apr 2006 | A1 |
| 20060085503 | Stoye et al. | Apr 2006 | A1 |
| 20060093026 | Montojo et al. | May 2006 | A1 |
| 20060093135 | Fiatal et al. | May 2006 | A1 |
| 20060099969 | Staton et al. | May 2006 | A1 |
| 20060099970 | Morgan et al. | May 2006 | A1 |
| 20060112177 | Barkley et al. | May 2006 | A1 |
| 20060122976 | Baluja et al. | Jun 2006 | A1 |
| 20060123042 | Xie et al. | Jun 2006 | A1 |
| 20060129766 | Cassia et al. | Jun 2006 | A1 |
| 20060132495 | Anderson | Jun 2006 | A1 |
| 20060141962 | Forbes et al. | Jun 2006 | A1 |
| 20060142018 | Matz et al. | Jun 2006 | A1 |
| 20060143464 | Ananthanarayanan et al. | Jun 2006 | A1 |
| 20060143692 | Kodama et al. | Jun 2006 | A1 |
| 20060149591 | Hanf et al. | Jul 2006 | A1 |
| 20060149843 | Rhoads et al. | Jul 2006 | A1 |
| 20060149970 | Imazu | Jul 2006 | A1 |
| 20060155822 | Yang et al. | Jul 2006 | A1 |
| 20060161621 | Rosenberg | Jul 2006 | A1 |
| 20060165226 | Ernst et al. | Jul 2006 | A1 |
| 20060166663 | Haehnichen et al. | Jul 2006 | A1 |
| 20060167969 | Andreev et al. | Jul 2006 | A1 |
| 20060168043 | Eisenberger et al. | Jul 2006 | A1 |
| 20060168164 | Lemson | Jul 2006 | A1 |
| 20060179410 | Deeds | Aug 2006 | A1 |
| 20060182025 | Kim et al. | Aug 2006 | A1 |
| 20060184591 | Backholm et al. | Aug 2006 | A1 |
| 20060184613 | Stienessen et al. | Aug 2006 | A1 |
| 20060188864 | Shah | Aug 2006 | A1 |
| 20060190428 | Jung et al. | Aug 2006 | A1 |
| 20060190569 | Neil et al. | Aug 2006 | A1 |
| 20060190984 | Heard et al. | Aug 2006 | A1 |
| 20060192014 | Hamilton et al. | Aug 2006 | A1 |
| 20060195570 | Zellner et al. | Aug 2006 | A1 |
| 20060203765 | Laroia et al. | Sep 2006 | A1 |
| 20060209842 | Creamer et al. | Sep 2006 | A1 |
| 20060212531 | Kikkawa et al. | Sep 2006 | A1 |
| 20060224629 | Alexander et al. | Oct 2006 | A1 |
| 20060230058 | Morris | Oct 2006 | A1 |
| 20060230394 | Forth et al. | Oct 2006 | A1 |
| 20060234630 | Lai | Oct 2006 | A1 |
| 20060236392 | Thomas et al. | Oct 2006 | A1 |
| 20060240804 | Backholm et al. | Oct 2006 | A1 |
| 20060240805 | Backholm et al. | Oct 2006 | A1 |
| 20060242137 | Shah et al. | Oct 2006 | A1 |
| 20060242210 | Ring et al. | Oct 2006 | A1 |
| 20060242320 | Nettle et al. | Oct 2006 | A1 |
| 20060242607 | Hudson | Oct 2006 | A1 |
| 20060252435 | Henderson et al. | Nov 2006 | A1 |
| 20060253456 | Pacholec et al. | Nov 2006 | A1 |
| 20060253575 | Carter et al. | Nov 2006 | A1 |
| 20060253605 | Sundarrajan et al. | Nov 2006 | A1 |
| 20060259517 | Urscheler et al. | Nov 2006 | A1 |
| 20060259923 | Chiu | Nov 2006 | A1 |
| 20060265595 | Scottodiluzio | Nov 2006 | A1 |
| 20060271884 | Hurst | Nov 2006 | A1 |
| 20060274701 | Albertsson | Dec 2006 | A1 |
| 20060277265 | Backholm et al. | Dec 2006 | A1 |
| 20060277271 | Morse et al. | Dec 2006 | A1 |
| 20060282408 | Wisely et al. | Dec 2006 | A1 |
| 20060294071 | Weare et al. | Dec 2006 | A1 |
| 20060294223 | Glasgow et al. | Dec 2006 | A1 |
| 20060294388 | Abraham et al. | Dec 2006 | A1 |
| 20070002897 | Goshen et al. | Jan 2007 | A1 |
| 20070005738 | Alexion-Tiernan et al. | Jan 2007 | A1 |
| 20070006317 | Asami et al. | Jan 2007 | A1 |
| 20070011367 | Scott et al. | Jan 2007 | A1 |
| 20070019610 | Backholm et al. | Jan 2007 | A1 |
| 20070021065 | Sengupta et al. | Jan 2007 | A1 |
| 20070022118 | Layne | Jan 2007 | A1 |
| 20070027775 | Hwang | Feb 2007 | A1 |
| 20070027832 | Fiatal et al. | Feb 2007 | A1 |
| 20070027886 | Gent et al. | Feb 2007 | A1 |
| 20070027917 | Ariel et al. | Feb 2007 | A1 |
| 20070027920 | Alvarado et al. | Feb 2007 | A1 |
| 20070027921 | Alvarado et al. | Feb 2007 | A1 |
| 20070027930 | Alvarado et al. | Feb 2007 | A1 |
| 20070033531 | Marsh | Feb 2007 | A1 |
| 20070038567 | Allaire et al. | Feb 2007 | A1 |
| 20070038931 | Allaire et al. | Feb 2007 | A1 |
| 20070039049 | Kupferman et al. | Feb 2007 | A1 |
| 20070041393 | Westhead et al. | Feb 2007 | A1 |
| 20070044041 | Beynon et al. | Feb 2007 | A1 |
| 20070049258 | Thibeault | Mar 2007 | A1 |
| 20070050591 | Boyd et al. | Mar 2007 | A1 |
| 20070053345 | Hsu et al. | Mar 2007 | A1 |
| 20070060196 | Sharma | Mar 2007 | A1 |
| 20070061393 | Moore | Mar 2007 | A1 |
| 20070067147 | Huang | Mar 2007 | A1 |
| 20070067381 | Grant et al. | Mar 2007 | A1 |
| 20070067424 | Raciborski et al. | Mar 2007 | A1 |
| 20070070931 | Lewis et al. | Mar 2007 | A1 |
| 20070072617 | Lewis et al. | Mar 2007 | A1 |
| 20070076264 | Pierce et al. | Apr 2007 | A1 |
| 20070077949 | Henderson et al. | Apr 2007 | A1 |
| 20070078857 | Punaganti et al. | Apr 2007 | A1 |
| 20070078964 | East et al. | Apr 2007 | A1 |
| 20070083600 | Bakos et al. | Apr 2007 | A1 |
| 20070088801 | Levkovitz et al. | Apr 2007 | A1 |
| 20070088852 | Levkovitz | Apr 2007 | A1 |
| 20070100650 | Ramer et al. | May 2007 | A1 |
| 20070101061 | Baskaran et al. | May 2007 | A1 |
| 20070105627 | Campbell | May 2007 | A1 |
| 20070111764 | Park et al. | May 2007 | A1 |
| 20070116223 | Burke et al. | May 2007 | A1 |
| 20070118620 | Cartmell et al. | May 2007 | A1 |
| 20070118669 | Rand et al. | May 2007 | A1 |
| 20070123214 | Mock | May 2007 | A1 |
| 20070130108 | Simpson et al. | Jun 2007 | A1 |
| 20070130217 | Linyard et al. | Jun 2007 | A1 |
| 20070136533 | Church et al. | Jun 2007 | A1 |
| 20070140193 | Dosa et al. | Jun 2007 | A1 |
| 20070147317 | Smith et al. | Jun 2007 | A1 |
| 20070147411 | Bijwaard et al. | Jun 2007 | A1 |
| 20070150599 | Neogi et al. | Jun 2007 | A1 |
| 20070150881 | Khawand et al. | Jun 2007 | A1 |
| 20070153798 | Krstulich | Jul 2007 | A1 |
| 20070156824 | Thompson | Jul 2007 | A1 |
| 20070156842 | Vermeulen et al. | Jul 2007 | A1 |
| 20070161402 | Ng et al. | Jul 2007 | A1 |
| 20070161411 | Liao et al. | Jul 2007 | A1 |
| 20070162514 | Civetta et al. | Jul 2007 | A1 |
| 20070165516 | Xu et al. | Jul 2007 | A1 |
| 20070167178 | Al-Harbi | Jul 2007 | A1 |
| 20070174420 | Khusial et al. | Jul 2007 | A1 |
| 20070174433 | Mendez et al. | Jul 2007 | A1 |
| 20070174470 | Burgess et al. | Jul 2007 | A1 |
| 20070175998 | Lev | Aug 2007 | A1 |
| 20070192122 | Routson et al. | Aug 2007 | A1 |
| 20070194913 | Yokoshima et al. | Aug 2007 | A1 |
| 20070198698 | Boyd et al. | Aug 2007 | A1 |
| 20070202850 | Pantalone et al. | Aug 2007 | A1 |
| 20070204341 | Rand et al. | Aug 2007 | A1 |
| 20070214261 | Kikuchi et al. | Sep 2007 | A1 |
| 20070220080 | Humphrey | Sep 2007 | A1 |
| 20070220099 | Di Giorgio et al. | Sep 2007 | A1 |
| 20070226417 | Davis | Sep 2007 | A1 |
| 20070232263 | Chandhok et al. | Oct 2007 | A1 |
| 20070233855 | Brown et al. | Oct 2007 | A1 |
| 20070237318 | McGary | Oct 2007 | A1 |
| 20070240218 | Tuvell et al. | Oct 2007 | A1 |
| 20070245010 | Arn et al. | Oct 2007 | A1 |
| 20070245409 | Harris et al. | Oct 2007 | A1 |
| 20070249365 | Jendbro | Oct 2007 | A1 |
| 20070250591 | Milic-Frayling et al. | Oct 2007 | A1 |
| 20070254631 | Spooner | Nov 2007 | A1 |
| 20070255848 | Sewall et al. | Nov 2007 | A1 |
| 20070259673 | Willars et al. | Nov 2007 | A1 |
| 20070264993 | Hughes | Nov 2007 | A1 |
| 20070267492 | Maclaine Pont | Nov 2007 | A1 |
| 20070276925 | LaJoie et al. | Nov 2007 | A1 |
| 20070276926 | LaJoie et al. | Nov 2007 | A1 |
| 20070277231 | Medvinsky et al. | Nov 2007 | A1 |
| 20070288469 | Shenfield | Dec 2007 | A1 |
| 20070290787 | Fiatal et al. | Dec 2007 | A1 |
| 20070293207 | Guedalia et al. | Dec 2007 | A1 |
| 20070293238 | Fiatal et al. | Dec 2007 | A1 |
| 20070293958 | Stehle et al. | Dec 2007 | A1 |
| 20070294295 | Finkelstein et al. | Dec 2007 | A1 |
| 20070294373 | Harrison | Dec 2007 | A1 |
| 20070294395 | Strub et al. | Dec 2007 | A1 |
| 20070294763 | Udezue et al. | Dec 2007 | A1 |
| 20070296701 | Pope et al. | Dec 2007 | A1 |
| 20070299631 | Macbeth et al. | Dec 2007 | A1 |
| 20070299918 | Roberts | Dec 2007 | A1 |
| 20070300273 | Turner | Dec 2007 | A1 |
| 20080001717 | Fiatal | Jan 2008 | A1 |
| 20080005695 | Ozzie et al. | Jan 2008 | A1 |
| 20080008095 | Gilfix | Jan 2008 | A1 |
| 20080009344 | Graham et al. | Jan 2008 | A1 |
| 20080010365 | Schneider | Jan 2008 | A1 |
| 20080016236 | Beverly et al. | Jan 2008 | A1 |
| 20080020786 | Smith et al. | Jan 2008 | A1 |
| 20080026778 | Cai et al. | Jan 2008 | A1 |
| 20080032718 | Suresh | Feb 2008 | A1 |
| 20080034031 | Weisbrot et al. | Feb 2008 | A1 |
| 20080034034 | Agrawal | Feb 2008 | A1 |
| 20080037787 | Boynton et al. | Feb 2008 | A1 |
| 20080039032 | Haumont | Feb 2008 | A1 |
| 20080043692 | Morita | Feb 2008 | A1 |
| 20080045253 | Mousseau et al. | Feb 2008 | A1 |
| 20080052206 | Edwards et al. | Feb 2008 | A1 |
| 20080056225 | Brok | Mar 2008 | A1 |
| 20080059308 | Gerken | Mar 2008 | A1 |
| 20080059398 | Tsutsui | Mar 2008 | A1 |
| 20080059582 | Hartikainen et al. | Mar 2008 | A1 |
| 20080061142 | Howcroft et al. | Mar 2008 | A1 |
| 20080068519 | Adler et al. | Mar 2008 | A1 |
| 20080072324 | Repasi et al. | Mar 2008 | A1 |
| 20080077506 | Rampell et al. | Mar 2008 | A1 |
| 20080077571 | Harris et al. | Mar 2008 | A1 |
| 20080085719 | Kuchibhotla et al. | Apr 2008 | A1 |
| 20080085724 | Cormier et al. | Apr 2008 | A1 |
| 20080086379 | Dion et al. | Apr 2008 | A1 |
| 20080086556 | Ramalingam et al. | Apr 2008 | A1 |
| 20080086599 | Maron et al. | Apr 2008 | A1 |
| 20080091773 | Hameen-Anttila | Apr 2008 | A1 |
| 20080096526 | Miettinen et al. | Apr 2008 | A1 |
| 20080098062 | Balia | Apr 2008 | A1 |
| 20080098120 | Johnson et al. | Apr 2008 | A1 |
| 20080103877 | Gerken | May 2008 | A1 |
| 20080104666 | Dillaway | May 2008 | A1 |
| 20080108298 | Selen et al. | May 2008 | A1 |
| 20080114881 | Lee et al. | May 2008 | A1 |
| 20080117922 | Cockrell et al. | May 2008 | A1 |
| 20080125225 | Lazaridis et al. | May 2008 | A1 |
| 20080130663 | Fridman et al. | Jun 2008 | A1 |
| 20080133326 | Goncalves et al. | Jun 2008 | A1 |
| 20080133641 | Gent et al. | Jun 2008 | A1 |
| 20080133708 | Alvarado et al. | Jun 2008 | A1 |
| 20080134292 | Ariel et al. | Jun 2008 | A1 |
| 20080140665 | Ariel et al. | Jun 2008 | A1 |
| 20080140794 | Rybak | Jun 2008 | A1 |
| 20080146257 | Clegg | Jun 2008 | A1 |
| 20080148146 | Estrada et al. | Jun 2008 | A1 |
| 20080150704 | Igoe | Jun 2008 | A1 |
| 20080151817 | Fitchett et al. | Jun 2008 | A1 |
| 20080154870 | Evermann et al. | Jun 2008 | A1 |
| 20080155613 | Benya et al. | Jun 2008 | A1 |
| 20080163318 | Chen et al. | Jul 2008 | A1 |
| 20080166999 | Guedalia et al. | Jul 2008 | A1 |
| 20080167019 | Guedalia et al. | Jul 2008 | A1 |
| 20080168145 | Wilson | Jul 2008 | A1 |
| 20080172662 | Harris et al. | Jul 2008 | A1 |
| 20080177872 | Vengroff | Jul 2008 | A1 |
| 20080178294 | Hu et al. | Jul 2008 | A1 |
| 20080180228 | Wakefield et al. | Jul 2008 | A1 |
| 20080183800 | Herzog et al. | Jul 2008 | A1 |
| 20080184001 | Stager | Jul 2008 | A1 |
| 20080186166 | Zhou et al. | Aug 2008 | A1 |
| 20080189365 | Narayanaswami et al. | Aug 2008 | A1 |
| 20080192820 | Brooks et al. | Aug 2008 | A1 |
| 20080195819 | Dumont | Aug 2008 | A1 |
| 20080198995 | McGary et al. | Aug 2008 | A1 |
| 20080200161 | Morse et al. | Aug 2008 | A1 |
| 20080201225 | Maharajh et al. | Aug 2008 | A1 |
| 20080201362 | Multer et al. | Aug 2008 | A1 |
| 20080201751 | Ahmed et al. | Aug 2008 | A1 |
| 20080207182 | Maharajh et al. | Aug 2008 | A1 |
| 20080209491 | Hasek | Aug 2008 | A1 |
| 20080214148 | Ramer et al. | Sep 2008 | A1 |
| 20080214157 | Ramer et al. | Sep 2008 | A1 |
| 20080216094 | Anderson et al. | Sep 2008 | A1 |
| 20080220797 | Meiby et al. | Sep 2008 | A1 |
| 20080221715 | Krzyzanowski et al. | Sep 2008 | A1 |
| 20080222271 | Spires | Sep 2008 | A1 |
| 20080232290 | Elzur et al. | Sep 2008 | A1 |
| 20080233983 | Park et al. | Sep 2008 | A1 |
| 20080235351 | Banga et al. | Sep 2008 | A1 |
| 20080235383 | Schneider | Sep 2008 | A1 |
| 20080242370 | Lando et al. | Oct 2008 | A1 |
| 20080256090 | Dietterich et al. | Oct 2008 | A1 |
| 20080261663 | Park et al. | Oct 2008 | A1 |
| 20080263170 | Caron et al. | Oct 2008 | A1 |
| 20080270379 | Ramakrishna | Oct 2008 | A1 |
| 20080271123 | Ollis et al. | Oct 2008 | A1 |
| 20080273498 | Jalil et al. | Nov 2008 | A1 |
| 20080281798 | Chatterjee et al. | Nov 2008 | A1 |
| 20080288659 | Hasha et al. | Nov 2008 | A1 |
| 20080294769 | Doi et al. | Nov 2008 | A1 |
| 20080298386 | Fiatal | Dec 2008 | A1 |
| 20080299956 | Bailey et al. | Dec 2008 | A1 |
| 20080301231 | Mehta et al. | Dec 2008 | A1 |
| 20080301300 | Toub | Dec 2008 | A1 |
| 20080305819 | Chun et al. | Dec 2008 | A1 |
| 20080307035 | Burckart et al. | Dec 2008 | A1 |
| 20080313282 | Warila et al. | Dec 2008 | A1 |
| 20080320577 | Larduinat | Dec 2008 | A1 |
| 20090006116 | Baker et al. | Jan 2009 | A1 |
| 20090010204 | Pratt, Jr. et al. | Jan 2009 | A1 |
| 20090010259 | Sirotkin | Jan 2009 | A1 |
| 20090012841 | Saft et al. | Jan 2009 | A1 |
| 20090016526 | Fiatal et al. | Jan 2009 | A1 |
| 20090019105 | Sebastian | Jan 2009 | A1 |
| 20090019141 | Bush et al. | Jan 2009 | A1 |
| 20090019153 | Sebastian | Jan 2009 | A1 |
| 20090019485 | Ellis et al. | Jan 2009 | A1 |
| 20090019532 | Jacobsen et al. | Jan 2009 | A1 |
| 20090024794 | Iyer et al. | Jan 2009 | A1 |
| 20090027222 | Larsson et al. | Jan 2009 | A1 |
| 20090031006 | Johnson | Jan 2009 | A1 |
| 20090043741 | Kim | Feb 2009 | A1 |
| 20090049166 | Roman et al. | Feb 2009 | A1 |
| 20090049173 | Pulito et al. | Feb 2009 | A1 |
| 20090049482 | Auerbach et al. | Feb 2009 | A1 |
| 20090052372 | Durazzo et al. | Feb 2009 | A1 |
| 20090054034 | Backholm et al. | Feb 2009 | A1 |
| 20090055353 | Meema | Feb 2009 | A1 |
| 20090059950 | Gao et al. | Mar 2009 | A1 |
| 20090063647 | Backholm et al. | Mar 2009 | A1 |
| 20090064346 | Larsson et al. | Mar 2009 | A1 |
| 20090070526 | Tetrick et al. | Mar 2009 | A1 |
| 20090075683 | Backholm et al. | Mar 2009 | A1 |
| 20090077205 | Quinet et al. | Mar 2009 | A1 |
| 20090077263 | Koganti et al. | Mar 2009 | A1 |
| 20090077326 | Motohashi | Mar 2009 | A1 |
| 20090081944 | Yavuz et al. | Mar 2009 | A1 |
| 20090083602 | Sarkar et al. | Mar 2009 | A1 |
| 20090086651 | Luft et al. | Apr 2009 | A1 |
| 20090094317 | Venkitaraman | Apr 2009 | A1 |
| 20090100416 | Brown et al. | Apr 2009 | A1 |
| 20090100506 | Whang et al. | Apr 2009 | A1 |
| 20090109983 | Dixon et al. | Apr 2009 | A1 |
| 20090110179 | Elsey et al. | Apr 2009 | A1 |
| 20090112778 | Beck et al. | Apr 2009 | A1 |
| 20090119266 | Fitzpatrick et al. | May 2009 | A1 |
| 20090122772 | Jung | May 2009 | A1 |
| 20090125523 | Fitzpatrick et al. | May 2009 | A1 |
| 20090131045 | Feuer et al. | May 2009 | A1 |
| 20090138427 | Kalavade | May 2009 | A1 |
| 20090144632 | Mendez | Jun 2009 | A1 |
| 20090147008 | Do et al. | Jun 2009 | A1 |
| 20090149203 | Backholm et al. | Jun 2009 | A1 |
| 20090156178 | Elsey et al. | Jun 2009 | A1 |
| 20090157792 | Fiatal | Jun 2009 | A1 |
| 20090164433 | R et al. | Jun 2009 | A1 |
| 20090164560 | Fiatal | Jun 2009 | A1 |
| 20090164605 | Lusher et al. | Jun 2009 | A1 |
| 20090165115 | Toumura et al. | Jun 2009 | A1 |
| 20090172565 | Jackson et al. | Jul 2009 | A1 |
| 20090181641 | Fiatal | Jul 2009 | A1 |
| 20090182500 | Dicke | Jul 2009 | A1 |
| 20090187939 | Lajoie | Jul 2009 | A1 |
| 20090191903 | Fiatal | Jul 2009 | A1 |
| 20090193130 | Fiatal | Jul 2009 | A1 |
| 20090193338 | Fiatal | Jul 2009 | A1 |
| 20090204682 | Jeyaseelan et al. | Aug 2009 | A1 |
| 20090213837 | Ku et al. | Aug 2009 | A1 |
| 20090215504 | Lando | Aug 2009 | A1 |
| 20090216903 | Howell et al. | Aug 2009 | A1 |
| 20090221326 | Roussel et al. | Sep 2009 | A1 |
| 20090222584 | Josefsberg et al. | Sep 2009 | A1 |
| 20090225778 | Sharif-Ahmadi et al. | Sep 2009 | A1 |
| 20090228545 | Mendez et al. | Sep 2009 | A1 |
| 20090233595 | Harris et al. | Sep 2009 | A1 |
| 20090234861 | Ramer et al. | Sep 2009 | A1 |
| 20090241180 | Fiatal | Sep 2009 | A1 |
| 20090248670 | Fiatal | Oct 2009 | A1 |
| 20090248696 | Rowles et al. | Oct 2009 | A1 |
| 20090248794 | Helms et al. | Oct 2009 | A1 |
| 20090248878 | Tran et al. | Oct 2009 | A1 |
| 20090249480 | Osipkov et al. | Oct 2009 | A1 |
| 20090249482 | Sarathy | Oct 2009 | A1 |
| 20090252136 | Mahany et al. | Oct 2009 | A1 |
| 20090254589 | Nair et al. | Oct 2009 | A1 |
| 20090254663 | Alperovitch et al. | Oct 2009 | A1 |
| 20090254971 | Herz et al. | Oct 2009 | A1 |
| 20090264138 | Kang et al. | Oct 2009 | A1 |
| 20090265752 | Sharif-Ahmadi et al. | Oct 2009 | A1 |
| 20090268672 | Kline et al. | Oct 2009 | A1 |
| 20090271491 | Pan | Oct 2009 | A1 |
| 20090282125 | Jeide et al. | Nov 2009 | A1 |
| 20090282130 | Antoniou et al. | Nov 2009 | A1 |
| 20090286531 | Bhatt et al. | Nov 2009 | A1 |
| 20090287750 | Banavar et al. | Nov 2009 | A1 |
| 20090299817 | Fok et al. | Dec 2009 | A1 |
| 20090307133 | Holloway et al. | Dec 2009 | A1 |
| 20090307196 | Shuster | Dec 2009 | A1 |
| 20090307731 | Beyabani | Dec 2009 | A1 |
| 20090310501 | Catovic et al. | Dec 2009 | A1 |
| 20090318171 | Backholm et al. | Dec 2009 | A1 |
| 20090323678 | Wang | Dec 2009 | A1 |
| 20090325565 | Backholm | Dec 2009 | A1 |
| 20090327390 | Tran et al. | Dec 2009 | A1 |
| 20090327819 | Pan | Dec 2009 | A1 |
| 20100010993 | Hussey, Jr. et al. | Jan 2010 | A1 |
| 20100011031 | Huang et al. | Jan 2010 | A1 |
| 20100023582 | Pedersen et al. | Jan 2010 | A1 |
| 20100036885 | Shen et al. | Feb 2010 | A1 |
| 20100042691 | Maguire | Feb 2010 | A1 |
| 20100042718 | Morris | Feb 2010 | A1 |
| 20100049852 | Whitnah et al. | Feb 2010 | A1 |
| 20100049872 | Roskind | Feb 2010 | A1 |
| 20100057924 | Rauber et al. | Mar 2010 | A1 |
| 20100064341 | Aldera | Mar 2010 | A1 |
| 20100067413 | Schneider et al. | Mar 2010 | A1 |
| 20100069127 | Fiennes | Mar 2010 | A1 |
| 20100076994 | Soroca et al. | Mar 2010 | A1 |
| 20100077035 | Li et al. | Mar 2010 | A1 |
| 20100077083 | Tran et al. | Mar 2010 | A1 |
| 20100082811 | Van Der Merwe et al. | Apr 2010 | A1 |
| 20100083255 | Bane et al. | Apr 2010 | A1 |
| 20100087167 | Tsurutome et al. | Apr 2010 | A1 |
| 20100087179 | Makavy et al. | Apr 2010 | A1 |
| 20100088722 | Jiang | Apr 2010 | A1 |
| 20100093273 | Hohl | Apr 2010 | A1 |
| 20100095018 | Khemani et al. | Apr 2010 | A1 |
| 20100095065 | Gray et al. | Apr 2010 | A1 |
| 20100099421 | Patel et al. | Apr 2010 | A1 |
| 20100100952 | Sample et al. | Apr 2010 | A1 |
| 20100115050 | Sultenfuss et al. | May 2010 | A1 |
| 20100118190 | Salfati et al. | May 2010 | A1 |
| 20100121744 | Belz et al. | May 2010 | A1 |
| 20100131443 | Agarwal et al. | May 2010 | A1 |
| 20100131593 | Kihara et al. | May 2010 | A1 |
| 20100131617 | Osborne et al. | May 2010 | A1 |
| 20100146107 | Fiatal | Jun 2010 | A1 |
| 20100146607 | Piepenbrink et al. | Jun 2010 | A1 |
| 20100149975 | Tripathi et al. | Jun 2010 | A1 |
| 20100153652 | Thomas et al. | Jun 2010 | A1 |
| 20100154044 | Manku | Jun 2010 | A1 |
| 20100174735 | Fiatal | Jul 2010 | A1 |
| 20100174756 | Lazaridis et al. | Jul 2010 | A1 |
| 20100174861 | Katz et al. | Jul 2010 | A1 |
| 20100174939 | Vexler | Jul 2010 | A1 |
| 20100180005 | Sebastian et al. | Jul 2010 | A1 |
| 20100186011 | Magenheimer | Jul 2010 | A1 |
| 20100188994 | Raleigh | Jul 2010 | A1 |
| 20100192212 | Raleigh | Jul 2010 | A1 |
| 20100197282 | Uchida | Aug 2010 | A1 |
| 20100198752 | Digon et al. | Aug 2010 | A1 |
| 20100203876 | Krishnaswamy | Aug 2010 | A1 |
| 20100205148 | Leblanc et al. | Aug 2010 | A1 |
| 20100207870 | Cho | Aug 2010 | A1 |
| 20100211651 | Guedalia et al. | Aug 2010 | A1 |
| 20100212010 | Stringer et al. | Aug 2010 | A1 |
| 20100214942 | Du et al. | Aug 2010 | A1 |
| 20100214984 | Cho et al. | Aug 2010 | A1 |
| 20100220619 | Chikira et al. | Sep 2010 | A1 |
| 20100223364 | Wei | Sep 2010 | A1 |
| 20100227594 | DeVries | Sep 2010 | A1 |
| 20100228863 | Kawauchi | Sep 2010 | A1 |
| 20100229096 | Maiocco et al. | Sep 2010 | A1 |
| 20100235473 | Koren et al. | Sep 2010 | A1 |
| 20100238915 | Cayla et al. | Sep 2010 | A1 |
| 20100250695 | Shenfield et al. | Sep 2010 | A1 |
| 20100250706 | Burckart et al. | Sep 2010 | A1 |
| 20100250733 | Turanyi et al. | Sep 2010 | A1 |
| 20100250986 | Black et al. | Sep 2010 | A1 |
| 20100251366 | Baldry | Sep 2010 | A1 |
| 20100257580 | Zhao | Oct 2010 | A1 |
| 20100260038 | Dhodapkar et al. | Oct 2010 | A1 |
| 20100260173 | Johnson | Oct 2010 | A1 |
| 20100262487 | Edwards et al. | Oct 2010 | A1 |
| 20100262664 | Brown et al. | Oct 2010 | A1 |
| 20100268757 | Fisher | Oct 2010 | A1 |
| 20100274983 | Murphy et al. | Oct 2010 | A1 |
| 20100279662 | Kuusinen et al. | Nov 2010 | A1 |
| 20100281112 | Plamondon | Nov 2010 | A1 |
| 20100284327 | Miklos | Nov 2010 | A1 |
| 20100293335 | Muthiah et al. | Nov 2010 | A1 |
| 20100299223 | Crouch | Nov 2010 | A1 |
| 20100299455 | Master et al. | Nov 2010 | A1 |
| 20100299518 | Viswanathan et al. | Nov 2010 | A1 |
| 20100305983 | De Marcken | Dec 2010 | A1 |
| 20100312946 | Bold et al. | Dec 2010 | A1 |
| 20100313018 | Jorgensen | Dec 2010 | A1 |
| 20100315535 | Nurit et al. | Dec 2010 | A1 |
| 20100317340 | Lee et al. | Dec 2010 | A1 |
| 20100319054 | Mehta et al. | Dec 2010 | A1 |
| 20100322124 | Luoma et al. | Dec 2010 | A1 |
| 20100323664 | Sivaram et al. | Dec 2010 | A1 |
| 20100323730 | Karmarkar | Dec 2010 | A1 |
| 20100325306 | Vimpari et al. | Dec 2010 | A1 |
| 20100332513 | Azar et al. | Dec 2010 | A1 |
| 20100332680 | Anderson et al. | Dec 2010 | A1 |
| 20110019978 | Jagmag | Jan 2011 | A1 |
| 20110022812 | van der Linden et al. | Jan 2011 | A1 |
| 20110023084 | Kraemer | Jan 2011 | A1 |
| 20110028129 | Hutchison et al. | Feb 2011 | A1 |
| 20110029378 | Ramer et al. | Feb 2011 | A1 |
| 20110035799 | Handler | Feb 2011 | A1 |
| 20110040718 | Tendjoukian et al. | Feb 2011 | A1 |
| 20110040872 | Blackburn et al. | Feb 2011 | A1 |
| 20110044304 | Connelly et al. | Feb 2011 | A1 |
| 20110047594 | Mahaffey et al. | Feb 2011 | A1 |
| 20110065419 | Book et al. | Mar 2011 | A1 |
| 20110065424 | Estevez et al. | Mar 2011 | A1 |
| 20110066646 | Danado et al. | Mar 2011 | A1 |
| 20110066715 | Schieder et al. | Mar 2011 | A1 |
| 20110069663 | Shu et al. | Mar 2011 | A1 |
| 20110072306 | Racey et al. | Mar 2011 | A1 |
| 20110083186 | Niemela et al. | Apr 2011 | A1 |
| 20110093725 | Theocharous et al. | Apr 2011 | A1 |
| 20110093917 | Alcorn et al. | Apr 2011 | A1 |
| 20110095903 | Gudlavenkatasiva et al. | Apr 2011 | A1 |
| 20110099363 | Boynton et al. | Apr 2011 | A1 |
| 20110113109 | LeVasseur et al. | May 2011 | A1 |
| 20110119134 | Zivkovic et al. | May 2011 | A1 |
| 20110119217 | Moon et al. | May 2011 | A1 |
| 20110119444 | DeCusatis et al. | May 2011 | A1 |
| 20110126060 | Grube et al. | May 2011 | A1 |
| 20110126250 | Turner | May 2011 | A1 |
| 20110138102 | Glikson et al. | Jun 2011 | A1 |
| 20110138402 | Fleming | Jun 2011 | A1 |
| 20110145646 | Harris et al. | Jun 2011 | A1 |
| 20110151944 | Morgan | Jun 2011 | A1 |
| 20110153816 | Lloyd et al. | Jun 2011 | A1 |
| 20110153937 | Annamalaisami et al. | Jun 2011 | A1 |
| 20110158239 | Mohaban | Jun 2011 | A1 |
| 20110161484 | Van den Bogaert et al. | Jun 2011 | A1 |
| 20110165889 | Fiatal et al. | Jul 2011 | A1 |
| 20110170410 | Zhao et al. | Jul 2011 | A1 |
| 20110170464 | Sengottaiyan et al. | Jul 2011 | A1 |
| 20110173055 | Ross et al. | Jul 2011 | A1 |
| 20110177847 | Huang | Jul 2011 | A1 |
| 20110179138 | Van Geest et al. | Jul 2011 | A1 |
| 20110179377 | Fleming | Jul 2011 | A1 |
| 20110182220 | Black et al. | Jul 2011 | A1 |
| 20110184576 | Hasan et al. | Jul 2011 | A1 |
| 20110184827 | Hubert | Jul 2011 | A1 |
| 20110185355 | Chawla et al. | Jul 2011 | A1 |
| 20110189997 | Tiwari et al. | Aug 2011 | A1 |
| 20110190014 | Fiatal | Aug 2011 | A1 |
| 20110191474 | Fiatal | Aug 2011 | A1 |
| 20110194539 | Blasinski et al. | Aug 2011 | A1 |
| 20110199905 | Pinheiro et al. | Aug 2011 | A1 |
| 20110201304 | Sutaria et al. | Aug 2011 | A1 |
| 20110202988 | Otranen et al. | Aug 2011 | A1 |
| 20110207436 | Van Gent et al. | Aug 2011 | A1 |
| 20110208810 | Li et al. | Aug 2011 | A1 |
| 20110213800 | Saros et al. | Sep 2011 | A1 |
| 20110213898 | Fiatal et al. | Sep 2011 | A1 |
| 20110214182 | Adams et al. | Sep 2011 | A1 |
| 20110217982 | Zhao | Sep 2011 | A1 |
| 20110218951 | Kline et al. | Sep 2011 | A1 |
| 20110219133 | Shanmugham | Sep 2011 | A1 |
| 20110225646 | Crawford | Sep 2011 | A1 |
| 20110237222 | Niejadlik | Sep 2011 | A1 |
| 20110238772 | Fiatal | Sep 2011 | A1 |
| 20110241872 | Mahaffey | Oct 2011 | A1 |
| 20110244859 | Tsuda | Oct 2011 | A1 |
| 20110246950 | Luna et al. | Oct 2011 | A1 |
| 20110249553 | Wang et al. | Oct 2011 | A1 |
| 20110252088 | Fiatal | Oct 2011 | A1 |
| 20110264622 | Vargas et al. | Oct 2011 | A1 |
| 20110264731 | Knowles et al. | Oct 2011 | A1 |
| 20110265174 | Thornton et al. | Oct 2011 | A1 |
| 20110294463 | Fiatal | Dec 2011 | A1 |
| 20110294464 | Fiatal | Dec 2011 | A1 |
| 20110296050 | Cherukuri | Dec 2011 | A1 |
| 20110296120 | Khan | Dec 2011 | A1 |
| 20110296415 | Khan et al. | Dec 2011 | A1 |
| 20110299454 | Krishnaswamy | Dec 2011 | A1 |
| 20110302154 | Snyder | Dec 2011 | A1 |
| 20110307541 | Walsh et al. | Dec 2011 | A1 |
| 20110320614 | Makavy et al. | Dec 2011 | A1 |
| 20120005276 | Guo et al. | Jan 2012 | A1 |
| 20120008536 | Tervahauta et al. | Jan 2012 | A1 |
| 20120020219 | Kamiya et al. | Jan 2012 | A1 |
| 20120022980 | Angelone | Jan 2012 | A1 |
| 20120023190 | Backholm et al. | Jan 2012 | A1 |
| 20120023226 | Petersen et al. | Jan 2012 | A1 |
| 20120023236 | Backholm et al. | Jan 2012 | A1 |
| 20120026879 | Foottit et al. | Feb 2012 | A1 |
| 20120030280 | Wang et al. | Feb 2012 | A1 |
| 20120030750 | Bhargava et al. | Feb 2012 | A1 |
| 20120034922 | Jones et al. | Feb 2012 | A1 |
| 20120054386 | Hanes | Mar 2012 | A1 |
| 20120072910 | Martin et al. | Mar 2012 | A1 |
| 20120077482 | Backholm | Mar 2012 | A1 |
| 20120078725 | Maitra et al. | Mar 2012 | A1 |
| 20120078996 | Shah | Mar 2012 | A1 |
| 20120084397 | Shinohara | Apr 2012 | A1 |
| 20120096058 | Mameri et al. | Apr 2012 | A1 |
| 20120096092 | Davidge et al. | Apr 2012 | A1 |
| 20120099592 | Ludwig | Apr 2012 | A1 |
| 20120108200 | Rubin et al. | May 2012 | A1 |
| 20120108225 | Luna et al. | May 2012 | A1 |
| 20120110109 | Luna et al. | May 2012 | A1 |
| 20120110110 | Luna et al. | May 2012 | A1 |
| 20120110111 | Luna et al. | May 2012 | A1 |
| 20120110112 | Luna et al. | May 2012 | A1 |
| 20120110118 | Luna et al. | May 2012 | A1 |
| 20120110171 | Luna et al. | May 2012 | A1 |
| 20120110173 | Luna et al. | May 2012 | A1 |
| 20120110174 | Wootton et al. | May 2012 | A1 |
| 20120110275 | Ganti et al. | May 2012 | A1 |
| 20120130973 | Tamm et al. | May 2012 | A1 |
| 20120131095 | Luna et al. | May 2012 | A1 |
| 20120131184 | Luna et al. | May 2012 | A1 |
| 20120131685 | Broch et al. | May 2012 | A1 |
| 20120135726 | Luna et al. | May 2012 | A1 |
| 20120140750 | Yan et al. | Jun 2012 | A1 |
| 20120144038 | Hildebrand | Jun 2012 | A1 |
| 20120144336 | Pinter et al. | Jun 2012 | A1 |
| 20120144384 | Baek | Jun 2012 | A1 |
| 20120149352 | Backholm et al. | Jun 2012 | A1 |
| 20120151044 | Luna et al. | Jun 2012 | A1 |
| 20120157170 | Backholm et al. | Jun 2012 | A1 |
| 20120158837 | Kaul | Jun 2012 | A1 |
| 20120158908 | Luna et al. | Jun 2012 | A1 |
| 20120170496 | Yang et al. | Jul 2012 | A1 |
| 20120170569 | Al-Khudairi | Jul 2012 | A1 |
| 20120173616 | Luna et al. | Jul 2012 | A1 |
| 20120174220 | Rodriguez | Jul 2012 | A1 |
| 20120176968 | Luna | Jul 2012 | A1 |
| 20120178414 | Fiatal | Jul 2012 | A1 |
| 20120179801 | Luna et al. | Jul 2012 | A1 |
| 20120185597 | Luna | Jul 2012 | A1 |
| 20120185918 | Backholm et al. | Jul 2012 | A1 |
| 20120198046 | Shah et al. | Aug 2012 | A1 |
| 20120198516 | Lim | Aug 2012 | A1 |
| 20120203761 | Biran et al. | Aug 2012 | A1 |
| 20120209923 | Mathur et al. | Aug 2012 | A1 |
| 20120210121 | Boynton et al. | Aug 2012 | A1 |
| 20120221697 | Sainio et al. | Aug 2012 | A1 |
| 20120224528 | Tapia et al. | Sep 2012 | A1 |
| 20120226767 | Luna et al. | Sep 2012 | A1 |
| 20120227059 | Fleming | Sep 2012 | A1 |
| 20120246333 | Fiatal | Sep 2012 | A1 |
| 20120254417 | Luna | Oct 2012 | A1 |
| 20120265836 | Nemoto et al. | Oct 2012 | A1 |
| 20120271903 | Luna | Oct 2012 | A1 |
| 20120271908 | Luna et al. | Oct 2012 | A1 |
| 20120278431 | Luna | Nov 2012 | A1 |
| 20120278432 | Luna | Nov 2012 | A1 |
| 20120278464 | Lehane et al. | Nov 2012 | A1 |
| 20120278886 | Luna | Nov 2012 | A1 |
| 20120284356 | Luna | Nov 2012 | A1 |
| 20120289239 | Luna et al. | Nov 2012 | A1 |
| 20120290642 | Shaughnessy et al. | Nov 2012 | A1 |
| 20120290675 | Luna et al. | Nov 2012 | A1 |
| 20120290717 | Luna | Nov 2012 | A1 |
| 20120295645 | Yariv et al. | Nov 2012 | A1 |
| 20120297213 | Nishida | Nov 2012 | A1 |
| 20120304288 | Wright et al. | Nov 2012 | A1 |
| 20120316992 | Oborne | Dec 2012 | A1 |
| 20120317284 | Raleigh et al. | Dec 2012 | A1 |
| 20120317370 | Luna | Dec 2012 | A1 |
| 20120324041 | Gerber et al. | Dec 2012 | A1 |
| 20120324575 | Choi et al. | Dec 2012 | A1 |
| 20120327779 | Gell et al. | Dec 2012 | A1 |
| 20120329442 | Luft et al. | Dec 2012 | A1 |
| 20120331059 | Luna | Dec 2012 | A1 |
| 20120331087 | Luna et al. | Dec 2012 | A1 |
| 20130010693 | Luna et al. | Jan 2013 | A1 |
| 20130012180 | Backholm et al. | Jan 2013 | A1 |
| 20130013726 | Westberg et al. | Jan 2013 | A1 |
| 20130023232 | Mendiola | Jan 2013 | A1 |
| 20130031191 | Bott | Jan 2013 | A1 |
| 20130031599 | Luna et al. | Jan 2013 | A1 |
| 20130031600 | Luna et al. | Jan 2013 | A1 |
| 20130031601 | Bott | Jan 2013 | A1 |
| 20130041974 | Luna et al. | Feb 2013 | A1 |
| 20130044702 | Jayaraman et al. | Feb 2013 | A1 |
| 20130052990 | Zhang | Feb 2013 | A1 |
| 20130110636 | Bott | May 2013 | A1 |
| 20130110637 | Bott | May 2013 | A1 |
| 20130110758 | Jung et al. | May 2013 | A1 |
| 20130124442 | Tendjoukian et al. | May 2013 | A1 |
| 20130142050 | Luna | Jun 2013 | A1 |
| 20130143609 | Richardson et al. | Jun 2013 | A1 |
| 20130145010 | Luna et al. | Jun 2013 | A1 |
| 20130145017 | Luna | Jun 2013 | A1 |
| 20130151648 | Luna | Jun 2013 | A1 |
| 20130151649 | Luna | Jun 2013 | A1 |
| 20130151709 | Luna | Jun 2013 | A1 |
| 20130159395 | Backholm et al. | Jun 2013 | A1 |
| 20130159511 | Backholm et al. | Jun 2013 | A1 |
| 20130163740 | T. et al. | Jun 2013 | A1 |
| 20130165084 | Xu et al. | Jun 2013 | A1 |
| 20130166669 | Luna et al. | Jun 2013 | A1 |
| 20130170348 | Luna et al. | Jul 2013 | A1 |
| 20130170507 | Hsueh et al. | Jul 2013 | A1 |
| 20130173756 | Luna et al. | Jul 2013 | A1 |
| 20130178195 | Luna et al. | Jul 2013 | A1 |
| 20130182572 | Backholm et al. | Jul 2013 | A1 |
| 20130188543 | Dwyer et al. | Jul 2013 | A1 |
| 20130191544 | Caldeira de Andrada et al. | Jul 2013 | A1 |
| 20130203433 | Luna et al. | Aug 2013 | A1 |
| 20130205366 | Luna et al. | Aug 2013 | A1 |
| 20130267209 | Bott | Oct 2013 | A1 |
| 20130268655 | Luna et al. | Oct 2013 | A1 |
| 20130268656 | Bott | Oct 2013 | A1 |
| 20130275563 | Luna et al. | Oct 2013 | A1 |
| 20130275586 | Luna et al. | Oct 2013 | A1 |
| 20130291099 | Donfried et al. | Oct 2013 | A1 |
| 20130294307 | Johansson et al. | Nov 2013 | A1 |
| 20130304604 | Hoffman et al. | Nov 2013 | A1 |
| 20130311594 | Luna et al. | Nov 2013 | A1 |
| 20130315088 | Gerber et al. | Nov 2013 | A1 |
| 20130315161 | Luna et al. | Nov 2013 | A1 |
| 20130316675 | Luna et al. | Nov 2013 | A1 |
| 20140025953 | Venters, III et al. | Jan 2014 | A1 |
| 20140153460 | Shrivastava et al. | Jun 2014 | A1 |
| 20140226562 | Shah et al. | Aug 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 2658185 | Sep 2009 | CA |
| 2806527 | Feb 2012 | CA |
| 2806529 | Feb 2012 | CA |
| 2806548 | Feb 2012 | CA |
| 2806549 | Feb 2012 | CA |
| 2806550 | Feb 2012 | CA |
| 2806557 | Feb 2012 | CA |
| 2798523 | May 2012 | CA |
| 2797631 | Nov 2012 | CA |
| 2797631 | Nov 2013 | CA |
| 103404193 | Nov 2013 | CN |
| 103620576 | Mar 2014 | CN |
| 0772327 | May 1997 | EP |
| 0993165 | Apr 2000 | EP |
| 1278390 | Jan 2003 | EP |
| 1135741 | Feb 2004 | EP |
| 1422899 | May 2004 | EP |
| 1466261 | Oct 2004 | EP |
| 1466435 | Oct 2004 | EP |
| 1482702 | Dec 2004 | EP |
| 1483689 | Dec 2004 | EP |
| 1669878 | Jun 2006 | EP |
| 1775911 | Apr 2007 | EP |
| 1815634 | Aug 2007 | EP |
| 1815652 | Aug 2007 | EP |
| 1817883 | Aug 2007 | EP |
| 2060085 | May 2009 | EP |
| 2080123 | Jul 2009 | EP |
| 2120014 | Nov 2009 | EP |
| 2122973 | Nov 2009 | EP |
| 2206390 | Jul 2010 | EP |
| 2267968 | Dec 2010 | EP |
| 2332294 | Jun 2011 | EP |
| 2378712 | Oct 2011 | EP |
| 2386164 | Nov 2011 | EP |
| 2395412 | Dec 2011 | EP |
| 2396953 | Dec 2011 | EP |
| 2465275 | Jun 2012 | EP |
| 2503473 | Sep 2012 | EP |
| 2556441 | Feb 2013 | EP |
| 2591628 | May 2013 | EP |
| 2596658 | May 2013 | EP |
| 2599003 | Jun 2013 | EP |
| 2599004 | Jun 2013 | EP |
| 2599280 | Jun 2013 | EP |
| 2599345 | Jun 2013 | EP |
| 2599346 | Jun 2013 | EP |
| 2599363 | Jun 2013 | EP |
| 2621144 | Jul 2013 | EP |
| 2635973 | Sep 2013 | EP |
| 2636252 | Sep 2013 | EP |
| 2636268 | Sep 2013 | EP |
| 2661697 | Nov 2013 | EP |
| 2700019 | Feb 2014 | EP |
| 2700020 | Feb 2014 | EP |
| 2700021 | Feb 2014 | EP |
| 2702500 | Mar 2014 | EP |
| 2702524 | Mar 2014 | EP |
| 2702827 | Mar 2014 | EP |
| 117152 | Jun 2006 | FI |
| 118288 | Sep 2007 | FI |
| 119581 | Dec 2008 | FI |
| 123227 | Dec 2013 | FI |
| 2415335 | Dec 2005 | GB |
| 2476354 | Jun 2011 | GB |
| 2493473 | Feb 2013 | GB |
| 2495058 | Mar 2013 | GB |
| 2495066 | Mar 2013 | GB |
| 2495263 | Apr 2013 | GB |
| 2495455 | Apr 2013 | GB |
| 2495463 | Apr 2013 | GB |
| 2495877 | Apr 2013 | GB |
| 2496537 | May 2013 | GB |
| 2497012 | May 2013 | GB |
| 2493473 | Jun 2013 | GB |
| 2498064 | Jul 2013 | GB |
| 2499089 | Aug 2013 | GB |
| 2499306 | Aug 2013 | GB |
| 2499534 | Aug 2013 | GB |
| 2499741 | Aug 2013 | GB |
| 2499747 | Aug 2013 | GB |
| 2499936 | Sep 2013 | GB |
| 2500327 | Sep 2013 | GB |
| 2500333 | Sep 2013 | GB |
| 2500334 | Sep 2013 | GB |
| 2495463 | Oct 2013 | GB |
| 2495877 | Oct 2013 | GB |
| 2497012 | Oct 2013 | GB |
| 2501416 | Oct 2013 | GB |
| 2495455 | Nov 2013 | GB |
| 2502168 | Nov 2013 | GB |
| 2495066 | Dec 2013 | GB |
| 2503077 | Dec 2013 | GB |
| 2503405 | Dec 2013 | GB |
| 2503990 | Jan 2014 | GB |
| 2504019 | Jan 2014 | GB |
| 2504037 | Jan 2014 | GB |
| 2504411 | Jan 2014 | GB |
| 2495058 | Mar 2014 | GB |
| 4154233 | May 1992 | JP |
| 10-178453 | Jun 1998 | JP |
| 10-336372 | Dec 1998 | JP |
| 2001-218185 | Aug 2001 | JP |
| 2001-350718 | Dec 2001 | JP |
| 2001-356973 | Dec 2001 | JP |
| 2003-323402 | Nov 2003 | JP |
| 2005-515664 | May 2005 | JP |
| 2005-520377 | Jul 2005 | JP |
| 2006-060795 | Mar 2006 | JP |
| 2007-172044 | Jul 2007 | JP |
| 2007-226783 | Sep 2007 | JP |
| 2009-207177 | Sep 2009 | JP |
| 4386732 | Oct 2009 | JP |
| 2010-045628 | Feb 2010 | JP |
| 2010-239366 | Oct 2010 | JP |
| 2011-511580 | Apr 2011 | JP |
| 2013-537754 | Oct 2013 | JP |
| 2013-539258 | Oct 2013 | JP |
| 2013-539259 | Oct 2013 | JP |
| 2013-541238 | Nov 2013 | JP |
| 2001-0018568 | Mar 2001 | KR |
| 2006-0068186 | Jun 2006 | KR |
| 2007-0071858 | Jul 2007 | KR |
| 10-0765238 | Oct 2007 | KR |
| 2007-0102091 | Oct 2007 | KR |
| 2007-0112412 | Nov 2007 | KR |
| 2007-0117874 | Dec 2007 | KR |
| 2008-0067477 | Jul 2008 | KR |
| 2009-0038217 | Apr 2009 | KR |
| 2009-0054528 | Jun 2009 | KR |
| 2009-0077515 | Jul 2009 | KR |
| 2010-0064605 | Jun 2010 | KR |
| 2011-0138122 | Dec 2011 | KR |
| 10-1227769 | Jan 2013 | KR |
| 10-1227821 | Jan 2013 | KR |
| WO 9741661 | Nov 1997 | WO |
| WO 9824257 | Jun 1998 | WO |
| WO 9858322 | Dec 1998 | WO |
| WO 0130130 | May 2001 | WO |
| WO 0201836 | Jan 2002 | WO |
| WO 03007570 | Jan 2003 | WO |
| WO 03058483 | Jul 2003 | WO |
| WO 03058879 | Jul 2003 | WO |
| WO 03065701 | Aug 2003 | WO |
| WO 03098890 | Nov 2003 | WO |
| WO 2004017591 | Feb 2004 | WO |
| WO 2004045171 | May 2004 | WO |
| WO 2004047409 | Jun 2004 | WO |
| WO 2005015925 | Feb 2005 | WO |
| WO 2005020108 | Mar 2005 | WO |
| WO 2006045005 | Apr 2006 | WO |
| WO 2006045102 | Apr 2006 | WO |
| WO 2006053952 | May 2006 | WO |
| WO 2006053954 | May 2006 | WO |
| WO 2006058967 | Jun 2006 | WO |
| WO 2007009252 | Jan 2007 | WO |
| WO 2007015725 | Feb 2007 | WO |
| WO 2007015726 | Feb 2007 | WO |
| WO 2007069245 | Jun 2007 | WO |
| WO 2007073422 | Jun 2007 | WO |
| WO 2007127878 | Nov 2007 | WO |
| WO 2007131914 | Nov 2007 | WO |
| WO 2007149526 | Dec 2007 | WO |
| WO 2007149540 | Dec 2007 | WO |
| 2008061042 | May 2008 | WO |
| WO 2008061042 | May 2008 | WO |
| WO 2008102265 | Aug 2008 | WO |
| WO 2008134880 | Nov 2008 | WO |
| WO 2008147258 | Dec 2008 | WO |
| WO 2009017712 | Feb 2009 | WO |
| WO 2009132700 | Nov 2009 | WO |
| WO 2009135290 | Nov 2009 | WO |
| WO 2009144688 | Dec 2009 | WO |
| WO 2010035108 | Apr 2010 | WO |
| WO 2010068842 | Jun 2010 | WO |
| WO 2010071345 | Jun 2010 | WO |
| WO 2010076997 | Jul 2010 | WO |
| WO 2010088074 | Aug 2010 | WO |
| WO 2011126889 | Oct 2011 | WO |
| WO 2011158067 | Dec 2011 | WO |
| WO 2012012109 | Jan 2012 | WO |
| WO 2012018430 | Feb 2012 | WO |
| WO 2012018431 | Feb 2012 | WO |
| WO 2012018477 | Feb 2012 | WO |
| WO 2012018479 | Feb 2012 | WO |
| WO 2012018556 | Feb 2012 | WO |
| WO 2012024030 | Feb 2012 | WO |
| WO 2012033593 | Mar 2012 | WO |
| WO 2012051044 | Apr 2012 | WO |
| WO 2012060995 | May 2012 | WO |
| WO 2012060996 | May 2012 | WO |
| WO 2012060997 | May 2012 | WO |
| WO 2012061430 | May 2012 | WO |
| WO 2012061433 | May 2012 | WO |
| WO 2012061437 | May 2012 | WO |
| WO 2012071283 | May 2012 | WO |
| WO 2012071384 | May 2012 | WO |
| WO 2012094675 | Jul 2012 | WO |
| WO 2012117157 | Sep 2012 | WO |
| WO 2012142884 | Oct 2012 | WO |
| WO 2012145533 | Oct 2012 | WO |
| WO 2012145541 | Oct 2012 | WO |
| WO 2012145544 | Oct 2012 | WO |
| WO 2012149216 | Nov 2012 | WO |
| WO 2012149221 | Nov 2012 | WO |
| WO 2012149434 | Nov 2012 | WO |
| WO 2012149443 | Nov 2012 | WO |
| WO 2012161751 | Nov 2012 | WO |
| WO 2013015835 | Jan 2013 | WO |
| WO 2013015994 | Jan 2013 | WO |
| WO 2013015995 | Jan 2013 | WO |
| WO 2013016663 | Jan 2013 | WO |
| WO 2013016666 | Jan 2013 | WO |
| WO 2013049060 | Apr 2013 | WO |
| WO 2013055413 | Apr 2013 | WO |
| WO 2013066464 | May 2013 | WO |
| WO 2013066465 | May 2013 | WO |
| WO 2013085590 | Jun 2013 | WO |
| WO 2013085591 | Jun 2013 | WO |
| WO 2013086214 | Jun 2013 | WO |
| WO 2013086225 | Jun 2013 | WO |
| WO 2013086447 | Jun 2013 | WO |
| WO 2013086455 | Jun 2013 | WO |
| WO 2013088186 | Jun 2013 | WO |
| WO 2013090212 | Jun 2013 | WO |
| WO 2013090821 | Jun 2013 | WO |
| WO 2013090834 | Jun 2013 | WO |
| WO 2013103988 | Jul 2013 | WO |
| WO 2013116852 | Aug 2013 | WO |
| WO 2013116856 | Aug 2013 | WO |
| WO 2013154905 | Oct 2013 | WO |
| WO 2013155208 | Oct 2013 | WO |
| WO 2013177390 | Nov 2013 | WO |
| WO 2013187658 | Dec 2013 | WO |
| WO 2014011216 | Jan 2014 | WO |
| Entry |
|---|
| Allchin, James Edward, “an Architecture for Reliable Decentralized Systems,” Ph.D. Thesis, Georgia Institute of Technology, 185 pages, Sep. 1983. |
| Android Developers, “Date,” 10 pages, Oct. 27, 2011. |
| Augun, Audrey, “Integrating Lotus Notes With Enterprise Data,” Lotus Notes Advisory, pp. 22-25, Jul.-Aug. 1996. |
| Balaban, Bob, “This Is Not Your Father's Basic: LotusScript in Notes Release 4,” The View, vol. 1, Issue 5, 32 pages, Nov.-Dec. 1995. |
| Bedell, Doug, “Meeting Your New Best Friends Six Degrees Widens Your Contacts in Exchange for Sampling Web Sites,” The Dallas Morning News, 4 pages, Oct. 27, 1998. |
| Bergman, Lawrence D. et al., “Programming-By-Demonstration for Behavior-Based User Interface Customization,” IBM Research Report, RC23116, 5 pages, Feb. 20, 2004. |
| B'Far, Reza et al., “Designing Effective User Interfaces for Wireless Devices,” Publication Unknown, 14 pages, Published prior to Feb. 23, 2006. |
| Blaney, Jeff, “You Can Take It With You—An Introduction to Mobile Computing With Notes R4,” The View, vol. 2, Issue 1, 14 pages, Jan.-Feb. 1996. |
| Braden, R., “Requirements for Internet Hosts—Application and Support,” RFC 1123, 80 pages, Oct. 1989. |
| Brown, Kevin et al., “Mastering Lotus Notes®,” Sybex Inc., 996 pages, 1995. |
| “Chapter: About NotesPump,” Publication Unknown, 480 pages, Published prior to Jan. 8, 2003. |
| “Chapter 13-1—Anatomy of a Note ID,” Publication Unknown, 8 pages, Published prior to Jan. 8, 2003. |
| Cole, Barb et al., “Lotus Airs Notes-To-Database Integration Tool,” Network World, 2 pages, Oct. 2, 1995. |
| “CR 3483 to Release 8 TS 25.331, Rev. 2,” 3GPP TSG-RAN2 Meeting #64, Prague, Czech Republic, 11 pages, Nov. 10-14, 2008. |
| “CR 4100 to Release 8 TS 25.331, Rev. 1,” 3GPP TSG-RAN WG2 Meeting #69, San Francisco, U.S., 6 pages, Feb. 22-26, 2010. |
| Dahl, Andrew, “Lotus Notes® 4 Administrator's Survival Guide,” Sams Publishing, 64 pages, 1996. |
| Decker, Stefan et al., “The Social Semantic Desktop,” Digital Enterprise Research Institute, DERI Technical Report 2004-05-02, 7 pages, May 2004. |
| Elz, R. et al., “Clarifications to the DNS Specification,” RFC 2181, 12 pages, Jul. 1997. |
| European Patent Application No. EP 03705704.9, Supplementary European Search Report, 4 pages, Jun. 9, 2010. |
| European Patent Application No. EP 03707338.4, Supplementary European Search Report, 2 pages, Apr. 18, 2011. |
| European Patent Application No. EP 05815115.0, Supplementary European Search Report, 7 pages, Nov. 17, 2011. |
| Falkner, Mike, “How to Plan, Develop, and Implement Lotus Notes® in Your Organization,” John Wiley & Sons, Inc., 539 pages, 1996. |
| Freeland, Pat et al., “Lotus Notes 3-3.1 for Dummies™,” IDG Books Worldwide, 389 pages, 1994. |
| Frenkel, Garry, “Pumping for Info: Notes and Database Integration,” Network Computing, 10 pages, May 1, 1996. |
| Gameline, Advertisement, 1 page, 1982. |
| Gewirtz, David, “Lotus Notes 3 Revealed!,” Prima Publishing, 261 pages, 1994. |
| Grous, Paul J., “Creating and Managing a Web Site With Lotus Internotes Web Publisher,” The View, vol. 1, Issue 4, 20 pages, Sep.-Oct. 1995. |
| GSM Association, “Network Efficiency Task Force Fast Dormancy Best Practices,” V1.0, 21 pages, May 26, 2010. |
| Haas, Zygmunt J. et al., “Mobile-TCP: An Asymmetric Transport Protocol Design for Mobile Systems,” IEEE, pp. 1054-1058, 1997. |
| Haas, Zygmunt J. et al., “The Design and Performance of Mobile TCP for Wireless Networks,” Journal of High Speed Networks, vol. 10, pp. 187-207, 2001. |
| Hajdu, Kalman et al., “Lotus Notes Release 4 in a Multiplatform Environment,” IBM Corporation, 173 pages, Feb. 1996. |
| Hardy, Ed, “Microsoft Proposes Two New Thumb-Driven User Interfaces,” Brighthand Consulting, Inc., 2 pages, 2003. |
| IBM Corporation, “The Architecture of Lotus Notes,” White Paper No. 114654, 26 pages, May 31, 1995. |
| IBM Corporation, “The History of Notes and Domino,” Lotus Developer Domain, 11 pages, Sep. 29, 2003. |
| ImTOO, “ImTOO iPod Movie Converter,” 3 pages, Nov. 9, 2005. |
| IntelliLink Corporation, “IntelliLink® for Windows User's Guide,” Version 3.0, 167 page., 1994. |
| International Application No. PCT/US2003/000618, International Search Report, 1 page, Apr. 4, 2003. |
| International Application No. PCT/US2003/000624, International Search Report, 2 pages, May 13, 2003. |
| International Application No. PCT/US2005/037702, International Preliminary Examination Report, 6 pages, Nov. 20, 2007. |
| International Application No. PCT/US2005/037702, International Search Report, 1 page, Nov. 5, 2007. |
| International Application No. PCT/US2005/037702, Written Opinion, 6 pages, Nov. 5, 2007. |
| International Application No. PCT/US2005/038135, International Search Report, 2 pages, Aug. 8, 2008. |
| International Application No. PCT/US2005/038135, Written Opinion, 8 pages, Aug. 8, 2008. |
| International Application No. PCT/US2005/038135, International Preliminary Report on Patentability, 9 pages, Oct. 31, 2011. |
| International Application No. PCT/FI2005/050424, International Search Report, 4 pages, Mar. 2, 2006. |
| International Application No. PCT/FI2005/050426, International Search Report, 3 pages, Mar. 1, 2006. |
| International Application No. PCT/FI2005/050441, International Search Report, 3 pages, Mar. 1, 2006. |
| International Application No. PCT/US2006/023426, International Search Report, 1 page, Feb. 21, 2007. |
| International Application No. PCT/US2006/023427, International Search Report, 1 page, Oct. 12, 2006. |
| International Application No. PCT/US2007/014462, International Search Report, 1 page, Jul. 2, 2008. |
| International Application No. PCT/US2007/014497, International Search Report, 1 page, Aug. 25, 2008. |
| International Application No. PCT/US2011/030534, International Search Report, 10 pages, Dec. 29, 2011. |
| International Application No. PCT/US2011/037932, International Search Report, 9 pages, Jan. 2, 2012. |
| International Application No. PCT/US2011/037943, International Search Report, 11 pages, Jan. 2, 2012. |
| International Application No. PCT/US2011/043322, International Search Report, 9 pages, Feb. 9, 2012. |
| International Application No. PCT/US2011/043328, International Search Report, 12 pages, Feb. 27, 2012. |
| International Application No. PCT/US2011/043409, International Search Report, 11 pages, Feb. 9, 2012. |
| Japanese Patent Application No. 2003-558726, Office Action, 2 pages, Jun. 10, 2008. |
| Karlson, Amy K. et al., “AppLens and LaunchTile: Two Designs for One-Handed Thumb Use on Small Devices,” Proceedings of CHI 2005, 10 pages, Apr. 2-7, 2005. |
| Kent, S. et al., “Security Architecture for the Internet Protocol,” RFC 2401, The Internet Society, 62 pages, Nov. 1998. |
| Kleinberg, Jon, “The Small-World Phenomenon: An Algorithmic Perspective,” Cornell Computer Science Technical Report 99-1776, 14 pages, Oct. 1999. |
| Koeppel, Dan, “GUIs Just Want to Have Fun,” Wired Magazine, Issue 8.10, 12 pages, Oct. 2000. |
| Kornblith, Polly Russell, “Lotus Notes Answers: Certified Tech Support,” Covers Release 3, McGraw-Hill, Inc., 326 pages, 1994. |
| Kreisle, Bill, “Teach Yourself . . . Lotus Notes 4,” MIS Press, 464 pages, 1996. |
| Lamb, John P. et al., “Lotus Notes Network Design,” McGraw-Hill, 278 pages, 1996. |
| Londergan, Stephen et al., “Lotus Notes® Release 4 for Dummies®,” IDG Books Worldwide, 229 pages, 1996. |
| Lotus Development Corporation, “Firewall Security Overview and How Firewalls Relate to Lotus Notes,” Lotus Notes Knowledge Base, 9 pages, May 22, 1996. |
| Lotus Development Corporation, “How to Set Up ‘Firewall’ Protection for a Notes Domain,” Lotus Notes Knowledge Base, 2 pages, Nov. 6, 1995. |
| Lotus Development Corporation, “Lotus Announces Lotus NotesPump 1.0,” Lotus Notes Knowledge Base, 6 pages, Oct. 31, 1995. |
| Lotus Development Corporation, “Lotus Inside Notes—The Architecture of Notes and the Domino Server,” 207 pages, 2000. |
| Lotus Development Corporation, “Lotus NotesPump 1.0 Q & A,” Lotus Notes Knowledge Base, 3 pages, Oct. 31, 1995. |
| Lotus Development Corporation, “Lotus NotesPump: Database Integration for Lotus Notes,” Lotus Notes Knowledge Base, 5 pages, Oct. 31, 1995. |
| Lotus Development Corporation, “Lotus Notes Administration,” Release 3.3, 20 pages, 1995. |
| Lotus Development Corporation, “Lotus Notes Administrator's Guide,” Release 4, 499 pages, 1995. |
| Lotus Development Corporation, “Lotus Notes Administrator's Guide—Server for NetWare, OS-2, and Unix,” Release 3.1, 509 pages, 1994. |
| Lotus Development Corporation, “Lotus Notes Administrator's Guide—Server for Windows,” Release 3.1, 345 pages, 1994. |
| Lotus Development Corporation, “Lotus Notes Application Developer's Guide,” Release 4, 475 pages, 1995. |
| Lotus Development Corporation, “Lotus Notes Customer Service Application Guide,” Release 3.1, 46 pages, 1994. |
| Lotus Development Corporation, “Lotus Notes Customer Support Guide,” 33 pages, Published prior to Jan. 8, 2003. |
| Lotus Development Corporation, “Lotus Notes Customer Support Guide—North American Guide,” Release 4.1, 51 pages, Published prior to Jan. 8, 2003. |
| Lotus Development Corporation, “Lotus Notes Database Manager's Guide,” Release 4, 115 pages, 1995. |
| Lotus Development Corporation, “Lotus Notes Deployment Guide,” Release 4, 104 pages, 1995. |
| Lotus Development Corporation, “Lotus Notes for Windows, OS-2, and Macintosh,” Release 3.3, 89 pages, 1995. |
| Lotus Development Corporation, “Lotus Notes Getting Started With Application Development,” Release 3.1, 151 pages, 1994. |
| Lotus Development Corporation, “Lotus Notes Install Guide for Servers,” Release 4, 68 pages, 1996. |
| Lotus Development Corporation, “Lotus Notes Install Guide for Workstations,” Release 4, 28 pages, 1995. |
| Lotus Development Corporation, “Lotus Notes Install Guide for Workstations,” Release 4.1, 67 pages, 1996. |
| Lotus Development Corporation, “Lotus Notes Install Guide for Workstations,” Release 4.5, 81 pages, 1996. |
| Lotus Development Corporation, “Lotus Notes Internet Cookbook for Notes Release 3,” 21 pages, Jan. 16, 1996. |
| Lotus Development Corporation, “Lotus Notes Internet Cookbook for Notes Release 4,” 35 pages, Feb. 14, 1996. |
| Lotus Development Corporation, “Lotus Notes Internotes Web Navigator Administrator's Guide,” Release 4, 60 pages, 1995. |
| Lotus Development Corporation, “Lotus Notes Internotes Web Navigator User's Guide,” Release 4, 56 pages, 1995. |
| Lotus Development Corporation, “Lotus Notes Internotes Web Publisher Guide,” Release 4, 122 pages, 1996. |
| Lotus Development Corporation, “Lotus Notes LotusScript Classes for Notes,” Release 4, 6 pages, Published prior to Jan. 8, 2003. |
| Lotus Development Corporation, “Lotus Notes Migration Guide,” Release 4, 110 pages, 1996. |
| Lotus Development Corporation, “Lotus Notes Network Configuration Guide,” Release 4.5, 121 pages, 1996. |
| Lotus Development Corporation, “Lotus Notes Network Driver Documentation,” Release 3.1, 100 pages, 1994. |
| Lotus Development Corporation, “Lotus Notes Programmer's Guide—Part 1,” Release 4, 614 pages, 1995. |
| Lotus Development Corporation, “Lotus Notes Programmer's Guide—Part 2,” Release 4, 462 pages, 1995. |
| Lotus Development Corporation, “Lotus Notes Quick Reference for Application Developers,” Release 3, 6 pages, Published prior to Jan. 8, 2003. |
| Lotus Development Corporation, “Lotus Notes Quick Reference for Macintosh,” Release 3, 6 pages, Published prior to Jan. 8, 2003. |
| Lotus Development Corporation, “Lotus Notes Quick Reference for SmartIcons,” Release 3.1, 4 pages, Published prior to Jan. 8, 2003. |
| Lotus Development Corporation, “Lotus Notes Quick Reference for Windows and Presentation Manager,” Release 3, 6 pages, Published prior to Jan. 8, 2003. |
| Lotus Development Corporation, “Lotus Notes Release Notes,” Release 4, 139 pages, 1995. |
| Lotus Development Corporation, “Lotus Notes Release Notes,” Release 4.1, 197 pages, 1996. |
| Lotus Development Corporation, “Lotus Notes Server for Windows,” Release 3.3, 7 pages, 1994. |
| Lotus Development Corporation, “Lotus Notes Server Up and Running!,” Release 4, 13 pages, 1996. |
| Lotus Development Corporation, “Lotus Notes Site and Systems Planning Guide,” Release 3.1, 169 pages, 1994. |
| Lotus Development Corporation, “Lotus Notes Start Here—Workstation Install for Windows, OS-2 and Macintosh,” Release 3.3, 47 pages, 1995. |
| Lotus Development Corporation, “Lotus Notes Step by Step—A Beginner's Guide to Lotus Notes,” Release 4, 179 pages, 1995. |
| Lotus Development Corporation, “Lotus Notes Step by Step—A Beginner's Guide to Lotus Notes,” Release 4.1, 167 pages, 1996. |
| Lotus Development Corporation, “Lotus Software Agreement,” 8 pages, Published prior to Jan. 8, 2003. |
| Lotus Development Corporation, “What Is the Notes Replicator?,” Lotus Notes Knowledge Base, 8 pages, Jul. 5, 1995. |
| “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Jun. 1995. |
| “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Aug. 1995. |
| “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Oct. 1995. |
| “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Dec. 1995. |
| “Lotus Notes Advisor,” Advisor Publications Inc., 63 pages, Jan.-Feb. 1996. |
| “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Apr. 1996. |
| “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Jun. 1996. |
| “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Aug. 1996. |
| “Lotus Notes Advisor,” Advisor Publications Inc., 55 pages, Oct. 1996. |
| “Lotus Notes Advisor,” Advisor Publications Inc., 63 pages, Dec. 1996. |
| “Lotus Notes—Notes Administration Help,” Screen Shots, 17 pages, Published prior to Jan. 8, 2003. |
| MacGregor, Rob et al., “The Domino Defense: Security in Lotus Notes and the Internet,” IBM Corporation, 183 pages, Dec. 1997. |
| Maltz, David A. et al., “MSOCKS: An Architecture for Transport Layer Mobility,” IEEE, pp. 1037-1045, 1998. |
| Marmel, Elaine, “Easy Lotus® Notes Release 4.0,” Que Corporation, 237 pages, 1996. |
| Mason, Luke, “Windows XP: New GUI Design Shows Skin Is In,” TechRepublic, 4 pages, Apr. 4, 2001. |
| McMullen, Melanie, “Network Remote Access and Mobile Computing,” Miller Freeman Inc., 226 pages, 1994. |
| Microsoft, Definition of “Access,” Microsoft Computer Dictionary, Fifth Edition, 2 pages, May 1, 2002. |
| Microsoft, Definition of “Synchronization,” Microsoft Computer Dictionary, Fifth Edition, 2 pages, May 1, 2002. |
| Milgram, Stanley, “The Small-World Problem,” Psychology Today, vol. 2, pp. 60-67, 1967. |
| Miller, Victor S., “Use of Elliptic Curves in Cryptography,” Advances in Cryptology—CRYPTO '85 Proceedings, vol. 218, pp. 417-426, 1985. |
| Mockapetris, P., “Domain Names—Concepts and Facilities,” RFC 1034, 43 pages, Nov. 1987. |
| Mockapetris, P., “Domain Names—Implementation and Specification,” RFC 1035, 43 pages, Nov. 1987. |
| Myers, Brad A. et al., “Extending the Windows Desktop Interface With Connected Handheld Computers,” WSS'00 Proceedings of the 4th Conference on USENIX Windows Systems Symposium, vol. 4, 10 pages, 2000. |
| Myers, Brad A. et al., “User Interfaces That Span Hand-Held and Fixed Devices,” CHI'2001 Workshop on Distributed and Disappearing User Interfaces in Ubiquitous Computer, 4 pages, 2001. |
| National Institute of Standards and Technology, “Advanced Encryption Standard (AES),” Federal Information Processing Standards Publication 197, 52 pages, Nov. 26, 2001. |
| National Institute of Standards and Technology, “Secure Hash Standard,” Federal Information Processing Standards Publication 180-2, 83 pages, Aug. 1, 2002. |
| Netscape Communications Corporation, “Netscape Mail Server Administrator's Guide,” Version 2.0, 172 pages, 1996. |
| Netscape Communications Corporation, “Netscape Mail Server Installation Guide,” Version 2.0 for Unix, 62 pages, 1996. |
| Netscape Communications Corporation, “Netscape Mail Server User's Guide,” Version 2.0, 35 pages, 1996. |
| Netscape Communications Corporation, “Netscape News Server Administrator's Guide for Windows NT,” Version 2.0, 119 pages, 1996. |
| Niederée, Claudia et al., “A Multi-Dimensional, Unified User Model for Cross-System Personalization,” Proceedings of the AVI 2004 Workshop on Environments for Personalized Information Access, 11 pages, 2004. |
| Nokia, “Developer Platforms,” 3 pages, 2005. |
| “NotesPump 1.0 Release Notes,” Publication Unknown, 8 pages, Published prior to Jan. 8, 2003. |
| Opyt, Barbara et al., “Use the Internet as Your Lotus Notes WAN,” Lotus Notes Advisor, pp. 17-20, Nov.-Dec. 1996. |
| Ortiz, C. Enrique, “An Introduction to the Symbian OS™ Platform for Palm OS® Developers,” Metrowerks Corp., 21 pages, 2002. |
| “Overview—What Is Lotus NotesPump?,” Publication Unknown, 88 pages, Published prior to Jan. 8, 2003. |
| Perez, Sarah, “Onavo's Data-Compressing Mobile App Raises $10 Million Series B From Horizons, Motorola Ventures,” 2 pages, Jan. 24, 2012. |
| Phillips, Joshua et al., “Modeling the Intelligence Analysis Process for Intelligent User Agent Development,” Research and Practice in Human Resource Management, vol. 9, No. 1, pp. 59-73, 2001. |
| Pyle, Hugh, “The Architecture of Lotus Notes,” Lotus Notes Advisor, Premiere Issue, pp. 18-27, 1995. |
| Pyle, Lisa, “A Jump Start to the Top Ten R3-To-R4 Migration Considerations,” The View, vol. 1, Issue 5, 22 pages, Nov.-Dec. 1995. |
| Qualcomm Incorporated, “Managing Background Data Traffic in Mobile Devices,” 16 pages, Jan. 2012. |
| Qualcomm, “System Parameter Recommendations to Optimize PS Data User Experience and UE Battery Life,” 80-W1112-1, Revision B, 9 pages, Mar. 2007. |
| Ringel, Meredith et al., “iStuff: A Scalable Architecture for Lightweight, Wireless Devices for Ubicomp User Interfaces,” Proceedings of UbiComp 2002, 2 pages, 2002. |
| Shafran, Andrew Bryce, “Easy Lotus Notes® for Windows™,” Que Corporation, 199 pages, 1994. |
| Signorini, Eugene, “SEVEN's Service-Based Wireless Solutions Enable Enterprises to Untether E-Mail,” Wireless/Mobile Enterprise & Commerce, 16 pages, Oct. 2004. |
| Swedeen, Bret et al., “Under the Microscope—Domino Replication,” LDD Today, 8 pages, Oct. 1, 1998. |
| Tamura, Randall A., “Lotus® Notes™ 4 Unleashed,” Sams Publishing, 928 pages, 1996. |
| U.S. Appl. No. 60/663,463, File History, 113 pages, filed Mar. 18, 2005. |
| Vivacqua, Adriana et al., “Profiling and Matchmaking Strategies in Support of Opportunistic Collaboration,” CoopIS/DOA/ODBASE 2003, LNCS 2888, pp. 162-177, 2003. |
| Wainwright, Andrew, “Secrets to Running Lotus Notes: The Decisions No One Tells You How to Make,” IBM Corporation, 193 pages, Oct. 1996. |
| Wilcox, Adam A., “PC Learning Labs Teaches Lotus Notes 3.0,” Ziff-Davis Press, 381 pages, 1993. |
| Wong, Harry, “Casahl's Replic-Action: Delivering True Notes-DBMS Integration,” The View, vol. 2, Issue 1, pp. 33-50, Jan.-Feb. 1996. |
| Eronen, “TCP Wake-Up: Reducing Keep-Alive Traffic in Mobile IPv4 and Ipsec NAT Traversal,” NRC-TR-2008-002, Nokia, 10 pages, Jan. 31, 2008. |
| International Application No. PCT/US2011/044974, International Search Report, 15 pages, Jun. 1, 2012. |
| International Application No. PCT/US2011/056474, International Search Report & Written Opinion, 9 pages, May 4, 2012. |
| International Application No. PCT/US2011/056476, International Search Report & Written Opinion, 12 pages, May 24, 2012. |
| International Application No. PCT/US2011/056478, International Search Report & Written Opinion, 11 pages, May 31, 2012. |
| International Application No. PCT/US2011/058840, International Search Report & Written Opinion, 10 pages, Apr. 26, 2012. |
| International Application No. PCT/US2011/058843, International Search Report & Written Opinion, 11 pages, May 16, 2012. |
| International Application No. PCT/US2011/058848, International Search Report & Written Opinion, 10 pages, Apr. 10, 2012. |
| International Application No. PCT/US2011/061512, International Search Report, 10 pages, May 10, 2012. |
| International Application No. PCT/US2011/061795, International Search Report & Written Opinion, 10 pages, Jul. 31, 2012. |
| International Application No. PCT/US2012/021459, International Search Report & Written Opinion, 10 pages, Jun. 1, 2012. |
| International Application No. PCT/US2012/022121, International Search Report & Written Opinion, 11 pages, May 14, 2012. |
| Newton, Harry, “Newton's Telecom Dictionary,” 20th Edition, pp. 67, 127, 542, Mar. 2004. |
| Seven Networks, Inc., “Seven Optimizing the Mobile Ecosystem,” www.seven.com/products.traffic—optimization.php, 1 page, May 29, 2012. |
| Wikipedia, Definition for “General Packet Radio Service,” 7 pages, downloaded on May 31, 2012. |
| International Application No. PCT/US2012/020669, International Search Report & Written Opinion, 10 pages, Sep. 12, 2012. |
| Armstrong, Trevor et al., “Efficient and Transparent Dynamic Content Updates for Mobile Clients,” The Fourth International Conference on Mobile Systems, Applications and Services, MobiSys 2006, pp. 56-68, Jun. 19-22, 2006. |
| Canadian Patent Application No. 2,806,550, Office Action, 3 pages, May 23, 2013. |
| European Patent Application No. EP 12775986.8, Supplementary European Search Report, 6 pages, Jul. 2, 2013. |
| European Patent Application No. EP 13150313.8, Supplementary European Search Report, 3 pages, Jul. 2, 2013. |
| International Application No. PCT/US2013/024657, International Search Report & Written Opinion, 14 pages, May 30, 2013. |
| International Application No. PCT/US2013/027694, International Search Report & Written Opinion, 12 pages, Jun. 4, 2013. |
| Pei, Guangyu et al., “Mobility Management in Hierarchical Multi-Hop Mobile Wireless Networks,” IEEE, pp. 324-329, 1999. |
| U.K. Patent Application No. GB1222636.1, Search Report, 4 pages, May 30, 2013. |
| U.K. Patent Application No. GB1301235.6, Examination Report, 3 pages, Jun. 24, 2013. |
| U.K. Patent Application No. GB1307218.6, Examination Report, 5 pages, Jun. 24, 2013. |
| U.K. Patent Application No. GB1307573.4, Examination Report, 4 pages, Jul. 3, 2013. |
| U.K. Patent Application No. GB1309204.4, Examination Report, 6 pages, Jun. 25, 2013. |
| U.K. Patent Application No. GB1309373.7, Examination Report, 6 pages, Jun. 26, 2013. |
| U.K. Patent Application No. GB1310340.3, Examination Report, 8 pages, Jul. 10, 2013. |
| U.K. Patent Application No. GB1310348.6, Examination Report, 5 pages, Jul. 15, 2013. |
| Yin, Chunjiang et al., “IST-2001-32125 FLOWS,” Deliverable No. D15, Information Society Technologies, 97 pages, Dec. 22, 2003. |
| Adwankar, Sandeep et al., “Universal Manager: Seamless Management of Enterprise Mobile and Non-Mobile Devices,” Proceedings of the 2004 IEEE International Conference on Mobile Data Management, 12 pages, 2004. |
| Amato, Guiseppe et al., “Detection of Images With Adult Content for Parental Control on Mobile Devices,” Mobility, 5 pages, 2009. |
| Ankeny, Jason, “F-Secure: Android to Blame for 79% of All Mobile Malware in 2012,” FierceMobileContent, FierceMarkets, 3 pages, Mar. 7, 2013. |
| Baset, Salman et al., “An Analysis of the Skype Peer-To-Peer Internet Telephony Protocol,” Columbia University, Department of Computer Science, 12 pages, Sep. 15, 2004. |
| Blefari-Melazzi, N. et al., “Autonomic Control and Personalization of a Wireless Access Network,” Computer Networks, vol. 51, pp. 2645-2676, 2007. |
| Canadian Patent Application No. 2,806,527, Office Action, 4 pages, Apr. 3, 2013. |
| Canadian Patent Application No. 2,806,529, Office Action, 4 pages, Apr. 2, 2013. |
| Canadian Patent Application No. 2,806,557, Office Action, 4 pages, Mar. 21, 2013. |
| de la Iglesia, Didac Gil et al., “Enhancing Mobile Learning Activities by the Use of Mobile Virtual Devices—Some Design and Implementation Issues,” 2010 International Conference on Intelligent Networking and Collaborative Systems, IEEE Computer Society, pp. 137-144, 2010. |
| Fukushima, Yukinobu et al., “Planning Method of Robust WDM Networks Against Traffic Changes,” IEIC Technical Report, vol. 103, No. 1, pp. 11-16, 2003. |
| International Application No. PCT/US2012/034288, International Search Report & Written Opinion, 15 pages, Nov. 23, 2012. |
| International Application No. PCT/US2012/034297, International Search Report & Written Opinion, 11 pages, Nov. 26, 2012. |
| International Application No. PCT/US2012/034300, International Search Report & Written Opinion, 9 pages, Nov. 23, 2012. |
| International Application No. PCT/US2012/035292, International Search Report & Written Opinion, 11 pages, Nov. 28, 2012. |
| International Application No. PCT/US2012/035300, International Search Report & Written Opinion, 9 pages, Nov. 28, 2012. |
| International Application No. PCT/US2012/035608, International Search Report & Written Opinion, 9 pages, Nov. 28, 2012. |
| International Application No. PCT/US2012/035617, International Search Report & Written Opinion, 9 pages, Oct. 10, 2012. |
| International Application No. PCT/US2012/042982, International Search Report & Written Opinion, 11 pages, Jan. 2, 2013. |
| International Application No. PCT/US2012/046317, International Search Report & Written Opinion, 10 pages, Jan. 3, 2013. |
| International Application No. PCT/US2012/046321, International Search Report & Written Opinion, 11 pages, Dec. 27, 2012. |
| International Application No. PCT/US2012/048623, International Search Report & Written Opinion, 13 pages, Jan. 31, 2013. |
| International Application No. PCT/US2012/048639, International Search Report & Written Opinion, 15 pages, Jan. 29, 2013. |
| International Application No. PCT/US2012/050467, International Search Report & Written Opinion, 14 pages, Mar. 4, 2013. |
| International Application No. PCT/US2012/050476, International Search Report & Written Opinion, 14 pages, Feb. 28, 2013. |
| International Application No. PCT/US2012/055931, International Search Report & Written Opinion, 9 pages, Mar. 4, 2013. |
| International Application No. PCT/US2012/055934, International Search Report & Written Opinion, 12 pages, Jan. 31, 2013. |
| International Application No. PCT/US2012/068278, International Search Report & Written Opinion, 11 pages, Mar. 21, 2013. |
| International Application No. PCT/US2012/068291, International Search Report & Written Opinion, 10 pages, Mar. 21, 2013. |
| International Application No. PCT/US2012/068612, International Search Report & Written Opinion, 10 pages, Mar. 29, 2013. |
| International Application No. PCT/US2012/068624, International Search Report & Written Opinion, 10 pages, Mar. 25, 2013. |
| International Application No. PCT/US2012/068822, International Search Report & Written Opinion, 13 pages, Mar. 29, 2013. |
| International Application No. PCT/US2012/069917, International Search Report & Written Opinion, 14 pages, Apr. 30, 2013. |
| International Application No. PCT/US2012/069931, International Search Report & Written Opinion, 10 pages, Apr. 30, 2013. |
| International Application No. PCT/US2013/020574, International Search Report & Written Opinion, 9 pages, Mar. 4, 2013. |
| International Application No. PCT/US2013/024664, International Search Report & Written Opinion, 11 pages, Apr. 1, 2013. |
| Johnsen, Lotte, Master's Thesis for “Content Distribution in Ad Hoc Networks,” Norwegian University of Science and Technology, Department of Telematics, 158 pages, Spring 2006. |
| Kanter, Theo et al., “Smart Delivery of Multimedia Content for Wireless Applications,” Computer Science, vol. 1818, pp. 70-81, 2000. |
| Kino, Toru, “Infrastructure Technology for Cloud Services,” Fujitsu Sci. Tech. J., vol. 47, No. 4, pp. 434-442, Oct. 2011. |
| LeBrun, Jason et al., “Bluetooth Content Distribution Stations on Public Transit,” ACM, Inc., 3 pages, 2006. |
| Open Mobile Alliance Ltd., “OMA AOI Architecture Principles—OMA-CD-AOI-2012-0012,” 12 pages, Dec. 17, 2012. |
| Openet Telecom, “Taming Signaling: Addressing the Signaling Storm,” Openet Labs Technical White Paper, 11 pages, 2012. |
| Parker, Tammy, “SK Telecom Aims to License, Standardize Smart Push,” FierceBroadbandWireless, 4 pages, Aug. 26, 2012. |
| Paul, Sanjoy et al., “The Cache-And-Forward Network Architecture for Efficient Mobile Content Delivery Services in the Future Internet,” First ITU-T Kaleidoscope Academic Conference for Innovations in NGN—Future Network and Services, 7 pages, May 12-13, 2008. |
| Qualcomm Incorporated, “A 3G/LTE Wi-Fi Offload Framework: Connectivity Engine (CnE) to Manage Inter-System Radio Connections and Applications,” 15 pages, Jun. 2011. |
| Sung, Dan Keun, Ph.D., “EE624 Mobile Communications Systems (MCS),” Korea Advanced Institute of Science and Technology, Department of Electrical Engineering and Computer Science, 13 pages, Fall 2000. |
| U.K. Patent Application No. GB1219986.5, Examination Report, 6 pages, Dec. 24, 2012. |
| U.K. Patent Application No. GB1222083.6, Search Report, 4 pages, Apr. 30, 2013. |
| U.K. Patent Application No. GB1300808.1, Examination Report, 10 pages, Mar. 11, 2013. |
| U.K. Patent Application No. GB1301258.8, Examination Report, 5 pages, Feb. 18, 2013. |
| U.K. Patent Application No. GB1301271.1, Examination Report, 4 pages, Mar. 14, 2013. |
| U.K. Patent Application No. GB1302158.9, Examination Report, 7 pages, Mar. 15, 2013. |
| U.K. Patent Application No. GB1302515.0, Examination Report, 3 pages, Mar. 5, 2013. |
| Zhang, Qi et al., “Cloud Computing: State-Of-The-Art and Research Challenges,” J Internet Serv Appl, vol. 1, pp. 7-18, 2010. |
| Canadian Patent Application No. 2,798,523, Office Action, 5 pages, Sep. 30, 2013. |
| Canadian Patent Application No. 2,806,527, Office Action, 8 pages, Aug. 8, 2013. |
| Canadian Patent Application No. 2,806,529, Office Action, 6 pages, Aug. 8, 2013. |
| Canadian Patent Application No. 2,806,548, Office Action, 4 pages, Oct. 10, 2013. |
| Canadian Patent Application No. 2,806,549, Office Action, 2 pages, Jul. 23, 2013. |
| Canadian Patent Application No. 2,806,549, Office Action, 3 pages, Nov. 4, 2013. |
| Canadian Patent Application No. 2,806,550, Office Action, 3 pages, Oct. 1, 2013. |
| Canadian Patent Application No. 2,806,557, Office Action, 4 pages, Jul. 18, 2013. |
| European Patent Application No. EP 11814939.2, Supplementary European Search Report, 6 pages, Nov. 6, 2013. |
| European Patent Application No. EP 11814971.5, Supplementary European Search Report, 10 pages, Oct. 24, 2013. |
| European Patent Application No. EP 11814973.1, Supplementary European Search Report, 10 pages, Oct. 30, 2013. |
| European Patent Application No. EP 11843111.3, Supplementary European Search Report, 6 pages, Oct. 21, 2013. |
| European Patent Application No. EP 13150313.8, Examination Report, 5 pages, Jul. 19, 2013. |
| International Application No. PCT/US2013/035257, International Search Report & Written Opinion, 14 pages, Jul. 26, 2013. |
| International Application No. PCT/US2013/036013, International Search Report & Written Opinion, 16 pages, Jul. 26, 2013. |
| International Application No. PCT/US2013/042417, International Search Report & Written Opinion, 19 pages, Sep. 13, 2013. |
| U.K. Patent Application No. GB1222637.9, Search Report, 4 pages, Sep. 13, 2013. |
| U.K. Patent Application No. GB1300185.4, Examination Report, 10 pages, Oct. 29, 2013. |
| U.K. Patent Application No. GB1300808.1, Examination Report, 3 pages, Sep. 20, 2013. |
| U.K. Patent Application No. GB1306198.1, Examination Report, 4 pages, Oct. 14, 2013. |
| U.K. Patent Application No. GB1307573.4, Examination Report, 4 pages, Nov. 12, 2013. |
| U.K. Patent Application No. GB1316847.1, Examination Report, 7 pages, Nov. 12, 2013. |
| Canadian Patent Application No. 2,806,548, Office Action, 3 pages, Feb. 25, 2014. |
| Canadian Patent Application No. 2,806,549, Office Action, 3 pages, Feb. 18, 2014. |
| Canadian Patent Application No. 2,806,550, Office Action, 3 pages, Feb. 14, 2014. |
| Canadian Patent Application No. 2,806,557, Office Action, 6 pages, Nov. 15, 2013. |
| European Patent Application No. EP 11748780.1, Examination Report, 4 pages, Jan. 17, 2014. |
| European Patent Application No. EP 11814940.0, Supplementary European Search Report, 7 pages, Nov. 7, 2013. |
| European Patent Application No. EP 11814971.5, Examination Report, 4 pages, Feb. 17, 2014. |
| European Patent Application No. EP 11814973.1, Examination Report, 4 pages, Feb. 17, 2014. |
| European Patent Application No. EP 11838437.9, Supplementary European Search Report, 7 pages, Dec. 18, 2013. |
| European Patent Application No. EP 11838437.9, Examination Report, 2 pages, Feb. 19, 2014. |
| European Patent Application No. EP 11838705.9, Supplementary European Search Report, 6 pages, Dec. 12, 2013. |
| European Patent Application No. EP 11842623.8, Supplementary European Search Report, 7 pages, Jan. 16, 2014. |
| European Patent Application No. EP 11843111.3, Examination Report, 4 pages, Feb. 17, 2014. |
| European Patent Application No. EP 12732122.2, Supplementary European Search Report, 6 pages, Dec. 6, 2013. |
| International Application No. PCT/US2013/070360, International Search Report & Written Opinion, 13 pages, Feb. 28, 2014. |
| Japanese Patent Application No. 2013-521801, Office Action, 6 pages, Feb. 3, 2014. |
| Japanese Patent Application No. 2013-521845, Office Action, 6 pages, Dec. 18, 2013. |
| U.K. Patent Application No. GB1300808.1, Examination Report, 4 pages, Feb. 3, 2014. |
| U.K. Patent Application No. GB1302153.0, Examination Report, 3 pages, Nov. 20, 2013. |
| U.K. Patent Application No. GB1309366.1, Search Report, 4 pages, Nov. 27, 2013. |
| U.K. Patent Application No. GB1309373.7, Examination Report, 3 pages, Dec. 5, 2013. |
| U.K. Patent Application No. GB1310340.3, Examination Report, 6 pages, Jan. 31, 2014. |
| U.K. Patent Application No. GB1317828.0, Examination Report, 7 pages, Jan. 3, 2014. |
| U.K. Patent Application No. GB1317972.6, Examination Report, 8 pages, Dec. 9, 2013. |
| U.K. Patent Application No. GB1318437.9, Examination Report, 7 pages, Feb. 6, 2014. |
| U.K. Patent Application No. GB1318796.8, Examination Report, 7 pages, Dec. 5, 2013. |
| U.K. Patent Application No. GB1318908.9, Examination Report, 6 pages, Nov. 29, 2013. |
| U.K. Patent Application No. GB1319222.4, Examination Report, 6 pages, Dec. 12, 2013. |
| U.K. Patent Application No. GB1319283.6, Examination Report, 7 pages, Nov. 21, 2013. |
| U.K. Patent Application No. GB1320293.2, Examination Report, 3 pages, Jan. 23, 2014. |
| U.K. Patent Application No. GB1321790.6, Examination Report, 6 pages, Jan. 17, 2014. |
| U.K. Patent Application No. GB1400632.4, Combined Search and Examination Report, 5 pages, Feb. 19, 2014. |
| CIPO Office Action dated Jul. 21, 2014 for application PCT/US2011/037,932 filed May 25, 2011. |
| Finnish Office Action Dated Dec. 17, 2014 for Finnish Patent Application No. 20125102. |
| Canadian Office Action dated Feb. 3, 2015 for Canadian Application No. 2,806,527 filed May 25, 2011. |
| Final Office Action mailed Jan. 14, 2015 for U.S. Appl. No. 13/115,740, filed May 25, 2011. |
| Final Office Action mailed Dec. 4, 2014 for U.S. Appl. No. 13/355,443. |
| Non-Final Office Action mailed Mar. 4, 2014 for U.S. Appl. No. 14/499,232. |
| Final Office Action mailed Mar. 11, 2015 for U.S. Appl. No. 13/618,371. |
| Number | Date | Country | |
|---|---|---|---|
| 20120023190 A1 | Jan 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61367871 | Jul 2010 | US | |
| 61367870 | Jul 2010 | US | |
| 61408858 | Nov 2010 | US | |
| 61408839 | Nov 2010 | US | |
| 61408829 | Nov 2010 | US | |
| 61408846 | Nov 2010 | US | |
| 61408854 | Nov 2010 | US | |
| 61408826 | Nov 2010 | US | |
| 61408820 | Nov 2010 | US | |
| 61416020 | Nov 2010 | US | |
| 61416033 | Nov 2010 | US | |
| 61430828 | Jan 2011 | US |
