With the advent of mass market digital communications, applications and content distribution, many access networks such as wireless networks, cable networks and Digital Subscriber Line (DSL) networks are pressed for user capacity, with, for example Evolution-Data Optimized (EVDO), High Speed Packet Access (HSPA), Long Term Evolution (LTE), Worldwide Interoperability for Microwave Access (WiMax), DOCSIS, DSL, and Wireless Fidelity (Wi-Fi) becoming user capacity constrained. In the wireless case, although network capacity will increase with new higher capacity wireless radio access technologies, such as Multiple-Input Multiple-Output (MIMO), and with more frequency spectrum and cell splitting being deployed in the future, these capacity gains are likely to be less than what is required to meet growing digital networking demand.
Similarly, although wire line access networks, such as cable and DSL, can have higher average capacity per user compared to wireless, wire line user service consumption habits are trending toward very high bandwidth applications and content that can quickly consume the available capacity and degrade overall network service experience. Because some components of service provider costs go up with increasing bandwidth, this trend will also negatively impact service provider profits.
The foregoing example of trends and issues is intended to be illustrative and not exclusive. Other limitations of the art will become apparent to those of skill in the relevant art upon a reading of the specification and a study of the drawings.
The invention can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. In general, the order of the steps of disclosed processes may be altered within the scope of the invention. Unless stated otherwise, a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task. As used herein, the term ‘processor’ refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.
A detailed description of one or more embodiments of the invention is provided below along with accompanying figures that illustrate the principles of the invention. The invention is described in connection with such embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims and the invention encompasses numerous alternatives, modifications and equivalents. Numerous specific details are set forth in the following description in order to provide a thorough understanding of the invention. These details are provided for the purpose of example and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not unnecessarily obscured.
As the network capacity gains are less than what is required to meet growing digital networking demand, a network capacity crunch is developing due to increasing network congestion on various wireless networks, such as mobile networks. The increasing popularity of various smart phone devices, net book devices, tablet computing devices, and various other wireless mobile computing devices, which are becoming increasingly popular on 3G, 4G, and other advanced wireless networks, is contributing to the network capacity crunch. Some network carriers have indicated that a relatively small number of users on such devices demand a disproportionately significant amount of their network capacity. For example, AT&T has recently indicated that about 3 percent of its smart phone device users (e.g., Apple iPhone® users) are generating approximately 40 percent of the operator's data traffic.
For example, in wireless networks, managing the wireless access connection capacity and network access connection resources is important to maintain network performance as network resources/capacity demand increases. Many network performance measures can be advantageously maintained or improved as network loading increases if capacity management and/or network resource management is employed. For example, these performance measures include network availability; the ability to deliver connections to all devices, users and/or applications seeking connections and enabled for service on the network; network access attempt success rate; the transmission speed experienced by one or more devices, users or applications; the average transmission speed experienced by all devices, users and/or applications; network bit error rate or packet error rate; the time delay from network access request to delivered access connection; the one-way delay or round-trip delay for a transmission; the delay timing jitter for a transmission; the time variation in transmission speed for one or more connections; the ability of the network to deliver various requested/needed levels of Quality of Service (QoS) to devices, users or applications that require differentiated connection QoS classes; the ability of the network to maintain efficiency (e.g., aggregated service throughput measured across all devices, users, and/or applications); the ability of the network to share or distribute a performance measure (e.g., the performance measures listed above) uniformly or fairly across multiple devices, users, and/or applications that all have the same service quality class or the same service plan performance parameters.
For example, if there is a limited amount of shared bandwidth for a set of user devices (e.g., a set of devices on a wireless network, such as a given base station or base station controller or femto cell or pico cell; or a set of devices on a cable modem networks, etc.), and if multiple and/or all devices allow all applications to indiscriminately access or attempt to access network resources or transmit/receive traffic, then the network can generally become overloaded. As a result, a subset of users/devices or in some cases most or all users/devices obtain poor network performance. As another example, if one or more devices forming a subset of devices on the network allow multiple and/or all applications to indiscriminately access or attempt to access network resources or transmit/receive traffic, then the network can become overloaded. As a result, a subset of users/devices or in some cases most or all users/devices obtain poor network performance.
Traditionally, mobile devices typically have specialized designs that are optimized to preserve network capacity and protect network resources from being over taxed. For example, wireless devices that browse the Internet often use specialized protocols such as WAP and data traffic compression or low resolution techniques rather than standard HTTP protocols and traffic used in wired Internet devices.
However, the wireless devices that implement specialized methods for accessing the Internet and/or other networks often implement complex specifications provided by one or more wireless carriers that own the networks that the device is designed to connect to. Such complex specifications often require time consuming design, testing, and certification processes. These processes in part have the effect of narrowing the base of device suppliers to those qualified and willing to perform the specialized design work required, slowing time to market for new devices, increasing the expense to develop new devices and reducing the types of applications that are supported.
Device OEMs have recently created wireless devices that are designed more like standard Internet devices and not fully optimized to preserve network capacity and resources. Many wireless service customers desire this type of device, and the OEMs generally want to reduce the complexity and time to market to deliver such devices. In addition, new market needs and new government requirements sometimes require that carriers offer a more open process for bringing new devices onto their network, in which the process does not require all of the specialized design and certification described above. These and various other factors are driving a growing need and trend for less complex and time consuming wireless device design and certification processes.
This trend has led many carriers to begin selling devices that are designed more as standard Internet service devices that connect to the Internet and other data networks through carrier wireless networks. As the cellular network is opened up to more and more new devices, applications and markets, there is a growing demand to allow general purpose Internet devices and applications to gain access to wireless networks without necessarily going through specialized design and certification process requirements to make the devices and applications efficient and authorized for access to such wireless networks.
However, general purpose Internet devices are not as frugal or sparing with wireless network access bandwidth. Moreover, with the advent of always on wide area network connections to the Internet has led to popular Internet services and applications that typically assume very inexpensive access and generally heed no attention to, for example, network busy state. As more general purpose Internet devices are provided for us on various wireless networks (e.g., mobile wireless networks), a high frequency of inefficient wireless network accesses continue to rise, which can reduce network capacity sometimes to levels that hinder access to service for that device (e.g., user, device, software demand) and/or other devices on that wireless network and/or that wireless network segment. As discussed above, judicious use of wireless network bandwidth, capacity, and resources generally results in better service for all users, but at present, device manufacturers and wireless network providers (e.g., wireless network carriers or carriers) have not provided or implemented more intelligent bandwidth usage techniques. These factors generally result in less carrier control of device design, which poses a threat to longer term network capacity and performance preservation as the volume of devices with less optimized wireless designs continues to grow.
There are many network performance and user performance factors that are impacted by the efficiency of the network, including, for example, overall network congestion; the access network performance experienced by one or more groups of users, devices, applications, network service sources, communication protocols, and/or operating system functions; and/or the performance experienced by a given user, device, application, network service source, communication protocol, and/or operating system function. Under a relatively low capacity demand of a wireless network, network performance as experienced by a group of devices, applications, network service sources, communication protocols, operating system functions, and/or users or by a single device, application, network service source, communication protocol, operating system function, and/or user can degrade somewhat proportionally (e.g., aggregate traffic delivered by the network may be roughly proportional to the peak available network traffic) with incremental increases in network access and/or traffic demand from one or more groups of users, devices, applications, network service sources, communication protocols and/or operating system functions. However, as network resources/network capacity demand increases (e.g., more wireless network data traffic is demanded in aggregate; more devices are serviced by the network; more users are serviced by the network; more applications are serviced by the network; more network service sources are serviced by the network; more operating system functions are serviced by the network; and/or more differentiated QoS sessions are serviced by the network), network availability/performance can decrease and/or the network may not adequately service one or more users, devices, applications, network service sources, communication protocols, and/or operating system functions, or may not service one or more groups of users, devices, applications, network service sources, communication protocols, and/or operating system functions.
There are many examples of how increasing network capacity demand can decrease network performance, including for example, to a decrease in average bandwidth offered per device (e.g., one or more users on a device, application, network service source, communication protocol, and/or operating system function executed/implemented on the device); an increase in traffic delivery latency; an increase in traffic delivery latency jitter; insufficient guaranteed or differentiated bandwidth for one or more differentiated QoS and/or dynamic QoS services (e.g., as described herein) to one or more devices, users, applications, network service sources, communication protocols, and/or operating system functions; increased latency for bandwidth reservation services; increased latency for QoS reservation services; performance problems with one or more communication protocols; unacceptable delays in user experience, and/or various other or similar consequences and device or user impacts resulting from reduced network availability and/or reduced network capacity. Examples of network communication protocols that can have degraded performance with excessive network loading or degraded network performance include, for example, Internet protocol (IP), HTML protocols, voice communication protocols including VOIP protocols, real-time video communication protocols, streaming media protocols (e.g., audio, video, etc), gaming protocols, VPN protocols, file download protocols, background service protocols, software update protocols, and/or various other network communication protocols. Thus, is it important to preserve/protect network capacity.
It is also important to control the number of transactions demanded from a given network resource (e.g., edge network segment, base station, base station controller, MAC resources, pico cell, femto cell, etc.) in a given period of time so that demand does not overcome the transaction servicing ability of that network resource. For example, network resources that should not be subjected to excess transaction demand can include base station or base station controller resources, media access control (MAC) resources, traffic transport resources, AAA resources, security or authentication resources, home agent (HA) resources, DNS resources, resources that play a part in network discovery, gateway or router resources, data session reservation or establishment resources (e.g., network resources required to manage, set up, conduct, and/or close service sessions, PPP sessions, communication flows, communication streams, QoS flows, radio access bearer reservation resources, tunnels, VPNs, APNs, special service routing, etc.), bandwidth reservation resources, QoS reservation or coordination resources, QoS transport resources, service charging resources, traffic analysis resources, network security resources, and/or various other or similar network resources. In some networks, the network performance degradation due to a given measure of incremental increase in network resource/capacity demand can become relatively large as various network resources become increasingly taxed due to either limited transaction processing capability or limited traffic bandwidth for one or more of the network resources that participate in establishing, servicing, conducting, maintaining, and/or closing the necessary network service connections and/or information exchanges required to conduct a service activity. For example, if the equipment required to establish a PPP session can only handle a certain number of new PPP session openings and/or closings per given period of time, and if device behavior is such that PPP sessions are often opened and/or closed, then the rate of PPP session transactions (e.g., openings and/or closings) can exceed the transaction capacity of the PPP session management resources. This is sometimes referred to as “flooding” or “overloading” a network resource with excess demand or excess connections, and, in such cases, the network resource may begin falling behind in servicing transaction demand in a well controlled manner (e.g., the network resource may continue processing transactions at or near a maximum rate for that network resource), or in some cases, the resource may fall behind transaction demand in a less well controlled manner (e.g., the network resource may become overwhelmed such that its processing rate not only falls below aggregate transaction demand, but the transaction rate processing capability decreases under overload as well). In the PPP session establishment resource example, once the rate of requested transactions exceeds the resource maximum transaction rate, then unmet device demand can grow to a point where one or more devices experiences delays in connecting to and/or communicating (e.g., sending/receiving data) with the network.
As another example, in any type of random access bandwidth reservation protocol, MAC protocol, or bandwidth delivery protocol, in a network without proper management and/or control of traffic access reservations and/or transmissions, as the network demand increases there may be more collisions between reservation requests, traffic transmissions, application demands, network service source demands, communication protocol demands, and/or operating system function demands causing a decreasing network efficiency that can degrade user, device, application and/or network service performance so that performance falls below acceptable levels. As another example, in systems in which there is a QoS service session reservation system, uncontrolled and/or unmanaged QoS reservation requests and/or reservation grants can lead to a situation where the QoS reservation resources and/or QoS service delivery resources are over taxed to the point where QoS service performance falls below desired levels. As another example, in networks that require some form of minimum resource allocation for transmissions, reservations, or network resource transactions, the network can become inefficient if one or more devices, applications, network service sources, operating system functions, and/or communication protocols have a relatively high rate of network resource access attempts, network accesses or data transmissions for small transmission payloads (e.g., minimum MAC reservation factors, minimum security overhead factors, minimum QoS reservation factors, minimum time responses for establishing a base station connection, minimum time responses for establishing or closing/being released from a session, etc). Even if the data packet comprising the access event is small, the network resources required to complete the access event are often busy servicing the access event for much longer periods of time than are required for the actual data transmission.
Another example of device service activity behavior that can have an impact on network performance is the way the device, device subsystem, and/or modem subsystem power cycling or transitions from one power save state to another. For example, establishing a basic connection from a device to a wireless base station consumes base station resources for a period of time and in some cases can also consume other network resources such as AAA, HLR, HA, gateway, billing, and/or charging gateway resources. If a device terminates the connection to the base station when the modem subsystem (e.g., or some other portion of the device) goes from active connection state to a power save state, then each time the device enters power save state and then exits power save state network resources are consumed, sometimes for time periods measured on the order of seconds or in extreme cases even minutes. If such a device has an aggressive power save algorithm that enters power save state after a short idle period, then the device behavior can consume a proportionally large amount of resources such that the network ability to support multiple devices is diminished, or such that the network cannot support very many similar devices on the network. Another similar example is the establishment of network sessions once the base station connection is established (e.g., establishing a PPP session between the device and a home agent (HA) or other gateway), in which network resources required to open and/or close the network session are ignorantly consumed if a device exhibits aggressive power save state cycling or frequently terminates the data session for other reasons.
Another example of device service activity behavior that can impact network performance is applications that maintain persistent network communication that generates a relatively high frequency of network data packets. Some applications have persistent signaling that falls into this category. Specific examples include frequent device signaling sequences to update widgets on a desktop; synchronize user data such as calendars, contacts, email, and/or other information/content; check or update email or RSS feeds; access social networking websites or tools; online text, voice or video chat tools; update real-time information; and conduct other repetitive actions. Additional application behavior that can significantly tie up network resources and capacity include, for example, conference meeting services, video streaming, content update, software update, and/or other or similar application behavior. For example, even when the user is not directly interacting with or benefiting from this type of application, the application can be running in the background and continuing to consume potentially significant network resources.
For example, the types of service activities and/or device behavior that can reduce network capacity and/or network resource availability include software updates for OS and applications, frequent OS and application background network accesses and signaling, frequent network discovery and/or signaling (e.g., EtherType messages, ARP messages, and/or other messaging related to network access), cloud synchronization services, RSS feeds and/or other background information feeds, application (e.g., web browser) or device behavior reporting, background email downloads, content subscription service updates and downloads (e.g., music/video downloads, news feeds, etc.), text/voice/video chat clients, virus updates, peer to peer networking applications, inefficient network access sequences during frequent power cycling or power save state cycling, large downloads or other high bandwidth accesses, and/or greedy application programs that continually and/or frequently access the network with small transmissions or requests for information. Various other examples will now be apparent to one of ordinary skill in the art.
Thus, not only can network capacity, network performance, and/or network resource availability be degraded by high device transmission bandwidth demand, but other types of persistent or frequent traffic resulting from network resource requests, network data accesses or other network interaction can also degrade network capacity, network performance, and/or network resource whether or not the aggregate bandwidth demand as measured by the total data throughput is high or not. Thus, techniques are needed to preserve network capacity by, for example, differentially controlling these types of network service usage activities in various ways depending on the type of service activity requesting network access and/or requesting transactions with network resources.
Smart phones and similar devices are exacerbating the problem by making frequent queries of the wireless network as such devices move among cell sites to, while in transit, for example, push email, access social networking tools, and/or conduct other repetitive actions. While data traffic is also growing, signaling traffic is outpacing actual mobile data traffic by 30 percent to 50 percent by some estimates. For example, a Yahoo IM user may send a message but then wait a couple of seconds between messages. To preserve battery life, the smart phone typically moves into an idle mode. When the user pushes another message seconds later, the device has to set up a signaling path again, and even when the signaling resource is released by the smart phone, the network typically does not react fast enough to allow for the next station to use resources until several seconds and sometimes minutes. As a result, the base station controller in this example is spending a lot of its resources trying to process the signaling so it cannot perform other tasks, such as allocate additional resources for data network usage, and such inefficiencies exacerbate the data network capacity crunch and dropped calls on such wireless networks.
One approach used by smart phone vendors to address this problem and save battery life on their devices is to implement a fast dormancy feature, which allows the mobile device to quickly make a query to the radio network controller to release the connection so that it can return to the idle state faster. In other words, the device is relaying the fact that the phone is going dormant saving device resources (e.g., signaling channel) rather than network resources. However, the fast dormancy feature can exacerbate this problem by prematurely requesting a network release only to follow on with a request to connect back to the network or by a request to re-establish a connection with the network.
Network carriers have typically attempted to manage network capacity using various purely central/core network based approaches. For example, some carriers have indicated a robust capacity planning process and sufficient investment is needed to alleviate this growing capacity crunch. Purely centralized network solutions with no assistance from a device based software agent (or service processor) can have several limitations. For example, for some device applications, OS functions or other service usage activities, if the activity is blocked somewhere in the network behind the base station after over the air (OTA) spectrum bandwidth is consumed to open or begin to open a communication socket, then there can still be an appreciable amount of network capacity or resources consumed even though the data transfer is not allowed to complete. In addition, if the service usage activity is aggressive in re-attempting to establish the network connection to transfer the data, and the network continues to allow the OTA portion of the connection establishment but blocks the connection somewhere in the network, then a large amount of capacity can be consumed by many devices exhibiting such behavior even though no useful service is being allowed. Accordingly, some embodiments for protecting network capacity include controlling network service usage activities at the source of the demand—the device. Furthermore, in some embodiments, service usage is controlled in a manner that delays, prevents, or reduces the frequency of service usage activity re-try attempts to connect to the network.
In some cases, an additional drawback of purely centralized network solutions to protect network capacity arises when service usage activities are controlled, blocked, throttled, and/or delayed by central network equipment with no mechanisms or support to link to a device user interface (UI) to inform the user what is happening and why it is happening. This can lead to a frustrating user experience and reduced carrier customer satisfaction. Accordingly, in some embodiments, a device based UI is provided to provide the user with real time or near real time information regarding why a service usage activity is being controlled, blocked, throttled, and/or otherwise controlled in order to protect network capacity. In some embodiments, a UI is provided that also informs the user when there are options to set, control, override, or modify service usage controls for the purpose of protecting network capacity. In some embodiments, such user preference inputs also correspond to a change in service usage billing. In some embodiments, such changes in service usage billing due to capacity sparing service control changes by the user are communicated to the user via a UI notification sequence. In some embodiments, techniques for protecting network capacity employ user warnings when a service usage activity classified for differential user notification policies is likely to cause the user to go over service plan caps (e.g., total data byte count usage caps).
What is needed is intelligent network monitoring to provide real-time traffic monitoring network service usage (e.g., at the packet level/layer, network stack application interface level/layer, and/or application level/layer) of the wireless network (e.g., radio access networks and/or core networks) and to effectively manage the network service usage for protecting network capacity (e.g., while still maintaining an acceptable user experience). Using Device Assisted Services (DAS) techniques, and in some cases, network assisted/based techniques, to provide for network service usage monitoring of devices, network carriers/operators would be provided greater insight into what devices, which users and what applications, and when and where network congestion problems occur, enabling operators to intelligently add additional resources to certain areas when necessary (e.g., offloading data traffic onto femto cells or WiFi hotspots and adding more network resources), to differentially control network service usage, and/or to differentially charge for network service usage based on, for example, a network busy state, for protecting network capacity.
Intelligent network monitoring of the wireless network to effectively manage network service usage for protecting network capacity can include providing Device Assisted Services (DAS) for protecting network capacity in accordance with various embodiments described herein. For example, intelligent network monitoring of the wireless network to effectively manage network service usage for protecting network capacity can include differentially controlling over the air software updates and/or performing software updates via wired connections only. As another example, intelligent network monitoring of the wireless network to effectively manage network service usage for protecting network capacity can include differentially controlling various applications that demand significant network resources or network capacity. As another example, intelligent network monitoring of the wireless network to effectively manage network service usage for protecting network capacity can include managing network access connection requests resulting from repeated power down modes in the modem, which can cause resource intensive re-connection and/or re-authentication processes. As another example, intelligent network monitoring of the wireless network to effectively manage network service usage for protecting network capacity can include techniques for keeping PPP sessions alive to avoid the need to consume network resources to re-establish PPP sessions (e.g., unless the application behavior analysis predicts that a mean access time is long enough for the PPP session to be dropped off and yet not causing overall network resource limitations).
Unlike traditional QoS techniques, which are used to establish a single end or end to end guaranteed service level(s) on a network, techniques disclosed herein for protecting network capacity facilitate implementation of services on a network to facilitate differential control of certain services to protect network capacity (e.g., to reduce network congestion, network capacity demand, network resource demand; and/or to increase network availability). As also disclosed herein, techniques disclosed herein for protecting network capacity facilitate implementation of services on a network to facilitate differential control of certain services to protect network capacity can also facilitate QoS implementations by maintaining needed levels of network capacity/availability to facilitate delivery of certain QoS levels/classes. For example, techniques disclosed herein for protecting network capacity can aggregate across multiple services and/or devices to facilitate differential control of certain services to protect network capacity. As another example, techniques disclosed herein for protecting network capacity can be used to provide for dynamic QoS classifications (e.g., dynamically assigning/classifying and reassigning/reclassifying (based on various criteria, events, and/or measures) network service usage activities to various QoS levels/classes, such as described herein) to facilitate differential control of certain services to protect network capacity.
Accordingly, Device Assisted Services (DAS) for protecting network capacity is provided. In some embodiments, DAS for protecting network capacity provides for protection of network capacity (e.g., network congestion and/or network access/resource demand and/or network availability on an edge element of the network, such as on the Radio Access Network (RAN) of a wireless network, and/or from a device to a base station/base station controller), such as by controlling network service activity usage activities of a device in wireless communication with the network to reduce demands on the network. For example, controlling network service usage activities can include classifying and/or controlling network access requests (e.g., IP address requests), network access reservation requests (e.g., a QoS reservation/sequence), network capacity/resources usage (e.g., bandwidth usage), and/or any other network service usage activities. In some embodiments, applications, OS functions, and/or other network service usage activities that request IP addresses from network address server resources are classified and/or controlled so that the IP address requests are withheld, delayed, time windowed, reduced in frequency, aggregated or otherwise controlled. In some embodiments, such “IP address request control policies” for one or more applications, OS functions, and/or other network service usage activities are set, updated, and/or modified before communicating it over a network connection to a network element (e.g., a service controller or another network element/function). In some embodiments, network service usage activities are generated/requested by applications, operating system (OS) functions, and/or other software/functions executed on a device in communication with the network. In some embodiments, it is desirable to apply a service usage control policy for the network service usage activities to protect network capacity (e.g., reduce network capacity demand). For example, some applications and/or OS functions have limited capabilities to defer certain traffic types based on fixed settings in the application, and such applications and/or OS functions typically cannot optimize network service usage activities based on a current network busy state (e.g., based on changing levels of network capacity and/or network performance available to the device). In some embodiments, the network busy state (e.g., or conversely the network availability state) is a characterization of the congestion (e.g., or conversely available capacity) of the network for one or more device connections. For example, the network busy state can provide a measure of how busy or congested the network or a network segment (e.g., network edge element) is for one or more device connections. As another example, network availability state can provide a measure of what network connection resources are available to one or more device connections. Thus, network busy state and network availability state can be viewed as converse ways of providing similar information, and as described herein with respect to various embodiments, these terms can be used interchangeably.
In some embodiments, techniques are provided for assigning a priority to a network service usage activity and controlling traffic associated with the network services usage activity based on the assigned priority. In some embodiments, techniques are provided for a implementing a differentiated and dynamic background services classification, for example, as a function of network availability state and/or network busy state.
In some embodiments, a service usage control policy is used for assisting in network access control of network service usage activities (e.g., deferring some or all of the network capacity demand from these source activities). In some embodiments, some or all of the network capacity demand is satisfied at a point where the network resources or capacity are more available or less busy. In some embodiments, techniques are provided for classifying network service activities associated with one or more applications or OS functions to a background service class and differentially controlling the background service class traffic. In some embodiments, techniques are provided for classifying one or more network service activities associated with an application or OS function to a background service class, while other network service activities associated with that application or OS function are classified to other service classes (e.g., or to different background service class priority levels).
In some embodiments, techniques are provided for determining a network busy state (e.g., for a network edge element connection to a device, such as for a RAN for the device's current wireless network access and/or to the current base station/base station controller in wireless communication with the device). In some embodiments, techniques are provided for implementing a service usage control policy to differentially control network services traffic based on a network busy state for an activity, a group of activities, or for a service class.
In some embodiments, DAS for protecting network capacity includes monitoring a network service usage activity of the communications device in network communication; classifying the network service usage activity for differential network access control for protecting network capacity; and associating the network service usage activity with a network service usage control policy based on a classification of the network service usage activity to facilitate differential network access control for protecting network capacity.
In some embodiments, a network service usage activity is any activity by the device that includes wireless network communication. In some embodiments, an application, an operating system (OS), and/or other device function generates a network service usage activity. In some embodiments, an application, an operating system (OS), and/or other device function generates one or more network service usage activities. Examples of a network service usage activity include the following: a voice connection (e.g., coded voice connection or voice over IP (VOIP) connection), a device application or widget connection, a device OS function connection, an email text connection, an email download connection, a file download connection, a streaming media connection, a location service connection, a map services connection, a software update (e.g., application, operating system, and/or antimalware software update) or firmware update connection, a device backup connection, an RSS feed connection, a website connection, a connection to a server, a web browser connection, an Internet connection for a device based service activity, establishing a sync service account, a user data synchronization service, a device data synchronization service, a network connection flow or stream, a socket connection, a TCP connection, a destination/port assigned connection, an IP connection, a UDP connection, an HTTP or HTTPS connection, a TLS connection, an SSL connection, a VPN connection, a general network services connection (e.g., establishing a PPP session, authenticating to the network, obtaining an IP address, DNS service), and various other types of connections via wireless network communication as will be apparent to one of ordinary skill in the art.
In some embodiments, a network service usage activity is classified, associated with, and/or assigned to a background class (e.g., a background service or QoS class) to facilitate differential network service usage control to protect network capacity. In some embodiments, differential network service usage control includes one or more of the following: monitoring network service usage activity; accounting for network service usage activity; reporting network service usage activity; generating a user notification for a network service usage activity; requesting a user preference for control of network service usage activity; accepting a user preference for network service usage activity; implementation of a network service usage activity policy (e.g., block/allow; traffic control techniques, such as throttle, delay, priority queue, time window, suspend, quarantine, kill, remove, and other well known traffic control techniques); implementing UI intercept procedures; generating a network busy state notification; generating a background class notification; generating a user notification for differential network service usage control of a network service usage activity; and various other techniques as described herein.
In some embodiments, a network availability state includes a state or measure of availability/capacity of a segment of a network (e.g., a last edge element of a wireless network). In some embodiments, a network busy state includes a state or measure of the network usage level or network congestion of a segment of a network (e.g., a last edge element of a wireless network). In some embodiments, network availability state and network busy state are inverse measures. As used herein with respect to certain embodiments, network availability state and network busy state can be used interchangeably based on, for example, a design choice (e.g., designing to assign background policies based on a network busy state or a network availability state yields similar results, but they are different ways to characterize the network performance and/or capacity and/or congestion). In some embodiments, network availability state and network busy state are dynamic measures as such states change based on network usage activities (e.g., based on a time of day, availability/capacity level, congestion level, and/or performance level). In some embodiments, differential network service usage control of a network service usage activity is based on a network busy state or network availability state.
In some embodiments, certain network service usage activities are classified as background services. In some embodiments, lower priority and/or less critical (and/or based on various other criteria/measures) network service usage activities are classified as background services based on a network busy state and differentially controlled based on a network busy state to protect network capacity. In some embodiments, differential network service usage control policies are based on a time of day, a network busy state, background services and/or QoS class changes based on a time of day and/or a network busy state, a random back-off for access for certain network service usage activities, a deterministic schedule for certain network service usage activities, a time windowing in which network service usage control policies for one or more service activities or background/QoS classes changes based on time of day, network busy state, a service plan, and various other criteria, measures, and/or techniques as described herein.
In some embodiments, a network capacity controlled service or network capacity controlled services class includes one or more network services (e.g., background download services and/or various other types or categories of services as described herein) selected for differential network service usage control for protecting network capacity. In some embodiments, a network capacity controlled services classification includes one or more network services associated with a network capacity controlled service/class priority setting for differential network service usage control for protecting network capacity. In some embodiments, a network capacity controlled service or network capacity controlled services class includes one or more network services associated with a QoS class for differential network service usage control for protecting network capacity. In some embodiments, a network capacity controlled service or network capacity controlled services class includes one or more network services associated with a dynamic QoS class for differential network service usage control for protecting network capacity.
For example, differentially controlling network service usage activities based on network capacity controlled services or dynamic QoS or QoS classifications can protect network capacity by, for example, improving network performance, increasing network availability, reducing network resources demand, and/or reducing network capacity demand (e.g., based on an individual device, aggregate devices connected to an edge element, and/or aggregate devices connected to many edge elements). In some embodiments, differentially controlling network service usage activities based on network capacity controlled services or dynamic QoS or QoS classifications can protect network capacity while maintaining proper device operation. In some embodiments, differentially controlling network service usage activities based on network capacity controlled services or dynamic QoS or QoS classifications can protect network capacity while maintaining an acceptable user experience (e.g., proper and/or expected device operation, proper and/or software/application/OS/function operation, avoiding (whenever possible) significant adverse impact on device functions, and/or user notifications to keep the user informed of various differential control implemented on the device).
In some embodiments, dynamic QoS classifications include QoS classifications that can be dynamically modified (e.g., reclassified, reprioritized, upgraded, and/or downgraded) based on various criteria, measures, settings, and/or user input as described herein (e.g., based on a time of day and/or day of week, based on a network busy state, based on a user preference, and/or based on a service plan). In some embodiments, the various techniques described herein related to DAS for providing network capacity and/or QoS for DAS are applied to dynamic QoS related techniques.
As wireless networks, such as mobile networks, evolve towards higher bandwidth services, which can include or require, for example, various levels of Quality of Service (QoS) (e.g., conversational, interactive data, streaming data, and/or various (end-to-end) real-time services that may benefit from QoS), demands will increase for converged network services to facilitate such services for end-to-end services between networks (e.g., to allow for control and/or support for such services, for example, QoS support, across network boundaries, such as between wireless networks (such as various service provider networks) and IP networks (such as the Internet), and/or other networks). While various efforts have attempted to address such QoS needs, such as policy management frameworks for facilitating QoS end-to end solutions, there exists a need to facilitate various QoS requirements using Device Assisted Services (DAS).
Accordingly, Quality of Service (QoS) for Device Assisted Services (DAS) is provided. In some embodiments, QoS for DAS is provided.
To establish a QoS channel, differentiated services are typically available, in which one class/level of service has a higher priority than another to provide for differentiated services on a network, such as a wireless network. For example, in a wireless network, various network elements/functions can be provisioned and controlled to establish a single end or end to end QoS channel. In some embodiments, a centralized QoS policy coordination and decision function using DAS techniques to assist in coordinating the QoS channel setup and control among the various elements of a wireless network is provided.
In some embodiments, QoS channel refers to the logical communication channel connected to a device that provides a desired level of QoS service level. For example, the QoS channel can be created with one or more QoS links, in which each link represents a QoS enabled connection that spans a portion of the total end to end network communication path from a near end device to a far end device. For example, the far end device can be on the same network or on a different network, potentially with different access technology and/or a different access network carrier. In some embodiments, the QoS channel includes one or more QoS links in which each link in the channel is QoS enabled, or one or more of the links in the channel is QoS enabled and others are not. As an example, a QoS channel can include the following links: a first device traffic path link, a first device to access network equipment element link (e.g., 2G/3G/4G wireless base station, WiFi access point, cable network head end, DSLAM, fiber aggregation node, satellite aggregation node, or other network access point/node), a first carrier core network, a long haul IPX network, a second carrier core network, a second device to access network equipment element link, and a second device traffic path link as similarly described herein with respect to various embodiments.
In some embodiments, each of the links described above has the ability to provide QoS services for that segment of an overall QoS channel. In some embodiments, the device traffic path link and/or the device to access network equipment element link are QoS enabled, but the carrier core network and/or IPX network links are not QoS enabled. In some embodiments, the core network and/or IPX network have sufficient over-provisioning of bandwidth that QoS is not limited by these network elements and, for example, can be limited by the device traffic link and/or the device to access network equipment element link do not have sufficient excess bandwidth making it desirable to QoS enable these QoS channel links. A common example is a 2G/3G/4G wireless network in which a device traffic path link and the device to access network element link (e.g., Radio Access Bearer (RAB)) are QoS enabled while the carrier core network and IPX network links are not (e.g., are provided at a best effort service level or other service levels).
In some embodiments, a QoS session refers to the QoS enabled traffic for a given device that flows over a QoS channel or QoS link. This QoS traffic supports a QoS service activity. In some embodiments, a QoS service activity includes a device service usage that is requested, configured, or preferably serviced with a given level of QoS. In some embodiments, a device QoS activity is a combination of one or more of the following: application, destination, source, socket (e.g., IP address, protocol, and/or port), socket address (e.g., port number), URL or other similar service identifier, service provider, network type, traffic type, content type, network protocol, session type, QoS identifier, time of day, network capacity (e.g., network busy state), user service plan authorization or standing, roaming/home network status, and/or other criteria/measures as similarly described herein. For example, QoS service activities that are supported by QoS sessions can include VOIP traffic, streaming video traffic, differentiated access bandwidth during busy network periods, real-time interactive traffic, such as network connected multimedia meetings (e.g., shared presentations, picture, video, voice, and/or other such applications/services), best effort interactive, such as Internet browsing, time sensitive services, such as email message body delivery, near real-time interactive services, such as SMS or push to talk, background download services, such as email downloads and other file transfers (e.g., FTP), and/or truly background download services, such as software updates (e.g., OS or application software updates and/or antimalware updates including content/signature updates).
In some embodiments, various QoS levels or classes are supported. For example a conversation class can provide for real-time traffic, which is typically very delay sensitive but can tolerate bit errors and packet losses. The conversational class is typically used for Voice Over IP (VOIP) and video telephony, in which users of such services benefit from the short delay features of the conversational class. A streaming class is similar to the conversational class except that the streaming class typically can tolerate more delay than the conversational class. The streaming class is generally used for when one end of the connection is a user (e.g., human user) and the other end is a machine/computer (e.g., for streaming content applications, such as streaming of video, such as movies or other video content). An interactive class is generally intended for traffic that allows delay variation while requiring reasonably low response time (e.g., web browsing or other applications in which the channel can be unused for long periods of time but when a user makes a request for a new page/data, the response time should be reasonably low). A background class is generally used for lowest priority service usages (e.g., typically used for e-mail with and without downloads/attachments, application software updates, OS software updates, and/or other similar applications/functions). In some embodiments, various QoS classes or services are applicable to the conversational class. In some embodiments, various QoS classes or services are also applicable to the streaming class. In some embodiments, various QoS classes or services are also applicable to the interactive class but typically not applicable to the background class. As will now be apparent to one of ordinary skill in the art, various other classes can be provided with lower or higher granularity based on service usage/channel requirements and/or network architectures.
In some embodiments, a QoS link or a QoS channel supports one QoS session. In some embodiments, a QoS link or a QoS channel supports multiple QoS sessions. In some embodiments, QoS link provisioning is provided to setup the QoS traffic level for a given QoS session or group of QoS sessions.
In some embodiments, a QoS channel is a single ended QoS channel or an end to end QoS channel. For example, if a QoS channel is end to end, then the QoS channel provisioning is accomplished in a coordinated manner for each QoS enabled link in the QoS channel. If a QoS channel is single ended, then the network elements and/or device participate in provisioning as much of one end of the QoS channel as possible, leaving provisioning of the QoS for the other end of the channel as the responsibility of the device and/or network elements that handle the traffic at the other end of the QoS channel. In some embodiments, a single ended QoS channel includes another single ended QoS channel at the other end. In some embodiments, only one end has single ended QoS channel enablement while the other end of the channel is a best effort service level, which, for example, can be used where one end of the QoS channel has tighter constraints on traffic capacity or quality than the other end (e.g., a VOIP call with one end that is QoS enabled on a 3G wireless network that has relatively tight bandwidth compared to a lightly loaded cable modem network device on the other end which may not need to be QoS enabled in order to achieve adequate voice quality).
In some embodiments, a QoS request (e.g., a QoS channel request or QoS service request) is a request for a QoS provisioning event to enable a QoS channel for one or more QoS service activities. In some embodiments, QoS availability assessment includes determining whether one or more of the links in a possible QoS channel are available (e.g., based on network capacity and transmission quality) to provision the necessary level of QoS for a requested QoS channel. In some embodiments, a QoS request is initiated by a device, a user, an application, and/or a network element/function as similarly described herein.
In some embodiments, a service plan refers to the collection of access service capabilities, QoS capabilities, and/or network capacity controlled services that are associated with a communications device. In some embodiments, the access service capabilities, QoS capabilities, and/or network capacity controlled services are determined by the collection of access service control policies for the device. In some embodiments, these service control policies are implemented in the network equipment. In some embodiments, these access service control policies are implemented both in the device and in the network equipment. In some embodiments, these access service control policies are implemented in the device. In some embodiments, there are different levels of service control capabilities (e.g., policies) based on different levels of service plan payments or device standing or user standing. In some embodiments, there are different levels of service control policies based on network type, time of day, network busy status, and/or other criteria/measures as similarly described herein with respect to various embodiments. In some embodiments, the access control and QoS control policies are based on the type of service activity being sought. In some embodiments, the QoS level and access level available for a given service activity for a given device or user is determined by the policies associated with the service plan. In some embodiments, a QoS authorization assessment is performed to determine whether a device or user has sufficient service plan standing to allow the requested level of QoS.
In some embodiments, before a QoS channel or link is provisioned (or before a QoS request is responded to or filled), a QoS availability assessment is performed to determine whether sufficient communication channel resources are available to provision the necessary level of QoS for the QoS channel or link. In some embodiments, this QoS availability assessment is determined by assessing the available QoS capacity for one or more necessary QoS links in the channel. For example, the available QoS link capacity can be assessed for one or more of a device traffic path, a device to access network equipment element link, a core network link, and/or an IPX network link. If the QoS assessment shows that the necessary channel capacity and quality are available for the desired QoS level for one or more desired QoS service activities, then a QoS channel request or QoS service request can be granted. In some embodiments, a QoS link or QoS channel reservation process is provided to reserve QoS capacity and quality in advance of link or channel provisioning to ensure that the available QoS resources are not assigned between the time of QoS availability assessment and QoS channel provisioning.
In some embodiments, the QoS availability assessment is performed after QoS authorization assessment. This prevents the unnecessary exercising of network elements when the device or user does not have sufficient service plan standing to receive the desired level of QoS even if it is available. This can be an important screening function performed on the device in the service processor, or by a centralized network function such as the service controller (e.g., or interchangeably, the home agent; Home Location Register (HLR); Authentication, Authorization, and Accounting (AAA) server/gateway/function; base station; one of the gateways, policy and charging rules function (PCRF), or other network element/function). In some embodiments, QoS availability is assessed without conducting a QoS authorization assessment or before receiving the response to a QoS authorization assessment.
In some embodiments, a QoS channel is provisioned to create the QoS channel to support a QoS session (e.g., a QoS service activity). In some embodiments, QoS channel provision includes assigning, routing, and/or otherwise causing the QoS session traffic to flow over one or more QoS links in the assigned QoS channel.
In some embodiments, device assisted service traffic control and QoS apply readily and directly to the problems of managing a QoS device link for QoS channel provisioning. Accordingly, in some embodiments, a service processor is provided to assist in provisioning the device portion of the QoS channel. In some embodiments, the service processor provisions the device link portion of the QoS channel by placing a higher priority on higher QoS level traffic. In some embodiments, this QoS priority is implemented in a number of ways, including routing the higher priority QoS traffic into first priority in the downstream and/or upstream traffic queues. Upstream traffic queuing is performed directly in some embodiments by transmitting guaranteed bit rate traffic first at higher available throttling rates, differentiated QoS traffic second with a controlled throttling rate, best effort traffic third with possibly lower controlled throttled rates, and/or background traffic fourth when/if bandwidth not needed by the higher levels of QoS traffic and at lower controlled throttling rates. For example, downstream traffic can be handled by queuing traffic and delaying or preventing TCP acknowledgements to be returned for the lower levels of QoS priority, while immediately passing the traffic and TCP acknowledgements for higher levels of QoS priority. The device link portion of the QoS channel is thus provisioned by assigning policies for the queuing priority, delay, throttle rate, and TCP acknowledgement return rate for device traffic in accordance with the bandwidth that is available at any point in time for the device. In some embodiments, various device service processor traffic control capabilities regulate or partially regulate QoS in accordance with a set of network policy instructions, including, in some embodiments, a service plan policy set.
In some embodiments the device service processor establishes multiple QoS channels through the device traffic path with each QoS channel having traffic control policies as described herein, with each QoS channel policy set creating a different class of QoS. In some embodiments, employing this multiple QoS channel approach, QoS for a given service activity is provided by routing the traffic for that QoS activity to the appropriate QoS channel with the appropriate QoS policy settings. The routing to the appropriate QoS channel can be provided using various techniques. For example, the routing can be provided by applying a common service traffic control policy set to traffic associated with all QoS service activities that require or request the QoS provided by the common service traffic control policy set. The application of the service traffic control policy set can be accomplished in a number of ways utilizing the embodiments described for the policy implementation agent and the policy control agent described herein. In such embodiments, the problem of assigning a QoS channel to a number of QoS service activities is reduced to applying a pre-determined set of service traffic control policies to each of the QoS service activities, with each pre-determined set of service traffic control policies representing a different QoS class. The device can then manage the overall QoS for all traffic based on the available traffic capacity and quality, the total aggregate traffic demand for each QoS traffic class and the policy rules that determine how each traffic class is provided with differential bit rate and traffic quality as compared to the other traffic classes for a given level of available traffic capacity and quality.
Based on the aggregate demand for each traffic QoS class, and the traffic capacity and quality level available to the device, the service processor can adjust the total available bit rate or percentage of available traffic capacity for each QoS class. For example, in some embodiments, the aggregate demand for the real-time interactive traffic control class (e.g., services, such as VOIP, emergency communication services or high performance real-time competitive gaming) can be determined, and the QoS routing function on the device (e.g., a QoS router agent/function) can first allocate enough constant bit rate traffic capacity from the available traffic capacity to satisfy these services, with each QoS service activity that requires this QoS class being assigned to this QoS channel. As more QoS service activities require this traffic class, the capacity allocated to the QoS channel out of the available device capacity is increased, and when fewer QoS service activities require this traffic class the capacity for this QoS channel is released. In the event that the device does not have any more available capacity with a guaranteed bit rate QoS level, then additional QoS service activities that desire, require or request this QoS level will not be provided this QoS level, and instead will either be provided with a lower QoS level or will not be allowed to connect to the access network. In some embodiments, there can be a hierarchy among the possible QoS service activities so that if there is no more capacity available at a given service QoS level, then the available capacity for that QoS class is provided to the service activities requiring that QoS from highest priority to lowest, until the available QoS class capacity is consumed, and then one or more QoS service activities that are too low on the priority list to obtain service with that QoS class are either bumped to a lower QoS class or are denied access. In some embodiments, once the required capacity to satisfy the real-time constant rate traffic needs is satisfied, the remaining capacity available to the device is then divided among the other QoS channel classes in accordance with a priority policy, with the priority policy being based on the relative priority of each service class, the relative priority of each QoS service activity, or a combination of the relative priority of each QoS service class and each QoS service activity. For example, these relative priority policies can vary from device to device based on service plan selection, device type, user standing, user group, device location, device network connection, type of network, time of day, network busy state, and/or other criteria/measures.
In some embodiments, a QoS link is established between the device and an access network equipment element. For example, such equipment element embodiments can include a 2G/3G/4G wireless base station, a wireless access point, a cable network head end, a DSL network DSLAM, a fiber network device traffic aggregator, a satellite network device traffic aggregator, a frame relay aggregation node, an ATM aggregation node, and/or other network equipment. In some embodiments, a logical communication channel is created between the device and the network equipment element, with the logical communication channel supporting a given level of QoS or QoS class traffic policy set. For example, the logical channel can include a RAB formed between a 2G/3G/4G base station and a wireless end point device. The RAB can be formed by controlling the media access control (MAC) parameters of the base station radio channel so that a given level of QoS class policies can be implemented. For example, the RAB can support constant bit rate, low latency communication traffic for guaranteed bit rate real-time traffic, or a differentiated high priority access channel for streaming traffic, or a best effort random access channel for best effort traffic, or an available unused capacity traffic for background traffic. The QoS channel link created in this manner can be dedicated to a single device, or shared with a subset of devices, or available to all devices. The QoS channel link created in this manner can be used by the device to support a single QoS activity as described herein, or a group of QoS activities as described herein. It will now be apparent to one of ordinary skill in the art that similar settings for cable head end and cable modem MAC can yield similar QoS classes for QoS links for the cable modem case and that similar techniques can be applied for a wireless access point or a satellite system MAC to achieve similar QoS classes for QoS links. It will also now be apparent to one of ordinary skill in the art that by creating multiple logical channels in the device link, and/or adjusting the available access network capacity and quality for each logical device communication channel in the DSLAM or fiber aggregator, similar QoS class QoS links can be established for the DSL and fiber distribution network cases.
In some embodiments the device service processor serves to route QoS service activities to the appropriate logical communication channel established for the desired QoS class supported by a QoS link between the device and the access network equipment element. In some embodiments, the device service processor elements (e.g., the policy implementation agent and/or the policy control agent) can be used in some embodiments to assign the same QoS traffic control policies to one or more QoS service activities that require the same QoS level. In a similar manner, in some embodiments, the device service processor elements can be used to assign or route service activity traffic for a given QoS class to the correct logical communication channel between the device and the access network element (e.g., a 2G/3G/4G base station) that supports the traffic control policies for the desired QoS class. For example, a QoS service link that supports guaranteed bit rate and latency can be established with one or more RABs from a base station to the device, and a second QoS service link can be established that supports differentiated preferred access for streaming content using one or more differentiated access RABs, and a third best effort RAB can be used to support best effort traffic. Each of the required RABs is first requested and then provisioned as described herein based on the aggregate required capacity and quality for one or more QoS service activities that require or desire the specific QoS service class associated with the RAB logical channel policy parameters. Once the set of logical QoS channels is thus established, the service processor (e.g., QoS router agent/function) routes the traffic associated with each QoS service activity to the appropriate RAB. In some embodiments, the service processor can detect increases or decreases in aggregate QoS class demand for each QoS class as QoS activities are initiated or terminated for that QoS class, and the service processor can communicate the required increases or decreases in the RAB assignments required to support that logical QoS channel.
In some embodiments, the access QoS link is established by direct communication from the device in which the device requests the QoS channel or link from the access network equipment element, or the device requests the QoS channel or link from an intermediate networking device, such as a service controller (e.g., or a readily substituted device with similar features, such as a home agent, an HLR, a mobile switching center, a base station, an access gateway, a AAA system, PCRF, or a billing system). In some embodiments, the device service processor bases the QoS channel or link request on an association the device performs to match a QoS service activity with a desired or required QoS class or QoS traffic control policy set. For example, this association of QoS class or QoS traffic control policy set with QoS service activity can be determined by a predefined policy mapping that is stored on the device and used by the service processor. In some embodiments, this policy mapping store is populated and/or updated by a service controller (e.g., or similar function as described herein). In some embodiments, the mapping is determined by a service controller (e.g., or similar function as described herein) based on a report from the device of the QoS service activity that needs the QoS channel or link.
In some embodiments, the required or desired QoS level for one or more QoS service activities is determined by a set of QoS service traffic control policies that are pre-assigned to various QoS service activities. For example, a given application can be pre-assigned a QoS class. As another example, a web service destination such as a VOIP service site can be assigned a QoS class. As another example, a given application can have one QoS assignment level for general Internet traffic but have a QoS assignment for real-time gaming traffic. As another example, a real-time broadcasting website can have a best effort QoS level assigned to programming information and general browsing and have a differentiated streaming QoS level for broadcast traffic content. In some embodiments, detection of QoS need or QoS assignment request for a given activity can be assigned by a device service processor according to a pre-defined QoS policy rules table (e.g., QoS activity table), or can be determined by a service controller based on information reported by the device, or can be requested by an application through a QoS application interface (e.g., QoS API), or can be determined by the nature of incoming traffic.
In embodiments, in which both end points in the QoS channel participate in establishing an end to end QoS channel, the required QoS level is determined and/or communicated by the originating end point. In some embodiments, the required QoS level is determined and/or communicated by the receiving end point. In some embodiments the QoS level is determined and/or communicated by the originating end point service controller (e.g., or the access network element (such as a base station), the HLR, home agent, mobile switching center, AAA, gateway, or other network element/function). In some embodiments, the QoS level is determined and/or communicated by the receiving end point service controller (e.g., or alternatively the access network element (such as a base station), the HLR, home agent, mobile switching center, AAA, gateway, or other network element/function). In some embodiments, the receiving end point service controller (e.g., or the access network element (such as a base station), the HLR, home agent, mobile switching center, AAA, gateway or other network function) and the originating end point service controller (e.g., or other similar function) communicate with one another to coordinate establishment of the QoS channel between the end points.
In some embodiments, the near end or originating end device service processor contacts the far end or terminating device service processor to initiate a QoS channel. In some embodiments, the initiation of the QoS channel from the near end or originating device is performed automatically by the far end device when its service processor detects that a given level of QoS is needed for the communication between the two devices. In some embodiments, the near end or originating device service processor detects the need for a QoS channel to the far end or terminating device and contacts a central network resources, such as the service controller (e.g., or other equipment element with similar function for this purpose), and the service controller provisions the far end of the QoS channel, either by communicating directly with the far end device or by communicating with the far end device's service controller (e.g., or other equipment element with similar function for this purpose). In some embodiments, in which the far end device service controller is contacted to assist in provisioning the QoS channel, there is a look up function to determine the address of the far end service controller based on a look up index formed from some aspect of the far end device credentials (e.g., phone number, SIM ID, MEID, IMSI, IP address, user name, and/or other device credentials).
In some embodiments, the mapping of QoS service activity to the desired level of QoS class or QoS traffic control policies is determined by providing a QoS API in the device service processor that applications use to request a QoS class or QoS channel connection. In some embodiments, an API is provided so that application developers can create application software that uses the standard interface commands to request and set up QoS channels. In some embodiments, the API does one or more of the following: accepts QoS requests from an application, formats the QoS channel request into a protocol appropriate for transmission to network equipment responsible for assessing QoS channel availability (e.g., including possibly the device traffic control system), coordinates with other network elements (e.g., including possibly the device traffic control system) to reserve a QoS channel, coordinates with other network elements (e.g., including possibly the device traffic control system) to provision a QoS channel, informs the application that the desired QoS channel can be created or not, and/or coordinates with other network elements (e.g., including possibly the device traffic control system) to connect the application with the desired QoS channel class. In some embodiments, the QoS API accepts the application QoS request and communicates and possibly coordinates with one or more QoS network equipment elements, such as a base station, cable head end or access point. In some embodiments, the QoS API accepts the QoS request from the application and communicates and possibly coordinates with an intermediate network element, such as a service processor (e.g., or other similar function as described herein). In some embodiments the QoS API assesses the QoS service plan standing for the device or user before sending QoS channel requests to other network elements, and only initiates the QoS request sequence if required service plan authorization is in place. In this manner, the potentially complex process of establishing a QoS channel with all the specific equipment communication protocols that typically need to be supported to assess QoS channel availability and provision the QoS channel are simplified into a limited set of API commands that are easy for an application development community to learn about and use for QoS differentiated services and applications.
In some embodiments, local traffic control on the device service processor is combined with traffic control in the link between the device and the access network equipment element. In this manner, both the device traffic control path QoS link and the device to access network element QoS link can be coordinated for best device QoS performance results given the available capacity and quality of the access network traffic for the device. In some embodiments, the policies for how the device manages local traffic control, establishes access network element logical channels (e.g., RABs) and routes traffic to and from the access network element logical channels is all determined by predefined policy rules loaded onto the device by the service controller (or other equivalent network element). In some embodiments, these policies are determined in the service controller itself.
In some embodiments, a QoS user interface (e.g., QoS UI) is presented to the device user. In some embodiments, the QoS UI notifies the user what level of QoS services the device is authorized to receive based on the service plan selection. In some embodiments, the QoS UI notifies the user what level of QoS services are available on the present network the device is connected to at the present time. In some embodiments, the QoS UI notifies the user when a level of QoS service that is higher than that authorized by the user service plan is required or desirable for a given service activity that the device has initiated. In some embodiments, the QoS UI provides the user with a set of one or more upgrade options to upgrade the service plan to include a higher level of QoS for one or more service activities. In some embodiments, the QoS UI provides the user with an opportunity to specify what level of QoS the user would like to employ for one or more service usage activities. In some embodiments, the QoS UI allows the user to specify a service plan setting that provides differentiated QoS during times when the network is busy. In some embodiments, the QoS UI allows the user to purchase one or more grades of service QoS with either a post-pay for a pre-defined service period and one or more pre-defined service usage limits by QoS class, a pre-pay for one or more pre-defined service usage limits by QoS class, or another payment system for differentiated QoS services. In some embodiments, the QoS UI provides the user with an opportunity to QoS enable or pay for QoS services for a connection that is initiated by an incoming connection to the device.
In some embodiments, QoS for DAS techniques include verifying that the device is properly implementing the QoS traffic control policies, for example, in accordance with a service plan. This ensures that errors, hacking, user device software settings manipulations, or other malware events do not result in inappropriate levels of QoS for a given device or group of devices. Accordingly, in some embodiments, the traffic control and QoS verification techniques described herein are employed to verify that the proper level of QoS is applied for a given service usage activity in accordance with a QoS priority policy. For example, verification of QoS channel request policy rules behavior can be implemented in a variety of ways including, as an example, monitoring device QoS channel requests and comparing the level of QoS requested with the level of QoS the device is authorized to receive in the service plan in effect for the device. Verification of proper QoS channel usage behavior by a device can be implemented in a variety of ways including, for example, monitoring network based reports of QoS service usage and comparing the network based reports against the service policy rules that should be in effect given the device service plan. Verification of proper device traffic control to implement a QoS service policy that is in effect can be accomplished in a variety of ways by verifying that the appropriate traffic control policy rules are being properly implemented as described herein. In some embodiments, DAS for protecting network capacity techniques include various verification techniques (e.g., verifying monitoring, traffic controlling, reporting, and/or other functions implemented or performed by the device), as described herein.
In some embodiments, the QoS router prioritizes traffic on the device. In some embodiments, the QoS router connects the QoS enabled session to the RAB that has the proper QoS level. In some embodiments, one session is routed to the RAB. In some embodiments, more than one session can be routed to an RAB. In some embodiments, multiple RABs providing multiple QoS levels are created to the device, and the QoS router routes each service activity to the RAB dictated by the QoS policy rules in effect on the device.
In some embodiments, the network collects service usage charges for different QoS classes. In some embodiments, there is differentiated service charging for the different classes of QoS service usage. As an example, since guaranteed bit rate traffic consumes network resources whether the traffic capacity is used or not, there can be a time element involved in the charging calculations. As a more detailed example, guaranteed bit rate services can be charged by the total bandwidth provisioned to the device at a given time multiplied by the amount of time that that bandwidth is made available. In some embodiments, differentiated access traffic that has higher QoS than best effort traffic but is not guaranteed bit rate can be charged at a higher rate than best effort traffic but lower than guaranteed bit rate. In some embodiments, such traffic can be charged based on the time the QoS channel is made available and the total amount of data transmitted over the channel, or can only be based on the total amount of data transmitted over the channel. Best effort traffic is charged in some embodiments based only on the total amount of data used, with the data charges being less than differentiated streaming access services. Background data services in some embodiments are charged at the lowest rate, possibly with only certain times of the day or periods of low network traffic demand being available for such services, and with the service being based on total data transmitted. In some embodiments, all QoS service levels can be charged based on a fixed price for a fixed charging period, possibly with a service usage cap with additional charges if the service cap is exceeded. In such fixed price scenario embodiments, the price charged is again higher for higher levels of QoS. In some embodiments, the network collects service usage charges for different network capacity controlled service classes. In some embodiments, there is differentiated service charging for the different classes of network capacity controlled service usage, as described herein.
In some embodiments, the network equipment (e.g., access network element, gateways, AAA, service usage storage systems, home agent, HLR, mobile data center, and/or billing systems) record and report service usage for one or more of the QoS service classes used by the device. In some embodiments, the device service processor records and reports service usage for one or more of the QoS service classes used by the device and reports the QoS service class usage to the service controller (e.g., or another substitute network element). In some embodiments, in which the device is recording reporting usage for one or more QoS service classes, it is important to verify the device service usage reports to ensure that the device usage reports are not distorted, tampered with, and/or otherwise in error. In some embodiments, verifying service usage reports against service usage that should be occurring given the service control policies in place on the device, service processor agent functional operation verification, test service usage events, agent query response sequences, device service processor software protection techniques, device service processor software environment checks, and several other techniques are provides as described herein. For example, using one or more of these verification techniques can provide a verifiable device assisted QoS service usage charging system. As another example, using one or more of these verification techniques can provide a verifiable network capacity controlled service usage charging system. In some embodiments, the network equipment (e.g., access network element, gateways, AAA, service usage storage systems, home agent, HLR, mobile data center, and/or billing systems) record and report service usage for one or more of the network capacity controlled service classes used by the device, as described herein.
In some embodiments, device assisted traffic control is provided for managing network congestion as follows. For example, when a given base station or group of base stations experience traffic demand that is high relative to the available capacity and/or service quality that can be provided, and such a condition is determined (e.g., detected or reported) based on a network busy state assessment as described below and further herein, then a service controller (e.g., or another network function) can issue, send, and/or implement traffic control throttling policies to/for the devices in accordance with a measure of the excess traffic demand the one or more base stations is experiencing. For example, the device service processors connected to an overly busy base station can be instructed to reduce the traffic control priority for one or more classes of QoS traffic, reducing the queuing priority, throttling rate, delay and/or access allowance for some or all of one or more classes of traffic. As another example, the device service processors connected to an overly busy base station can be instructed to reduce the traffic control priority for one or more classes of network capacity controlled services traffic, reducing the queuing priority, throttling rate, delay and/or access allowance for some or all of one or more classes of such traffic. As another example, one or more classes of network capacity controlled services traffic, such as background download processes, which can include, for example, software updates can be turned off completely or throttled back significantly. As another example, best effort traffic such as Internet browsing can be throttled or reduced for a group of devices connected to base stations experiencing excess traffic demand. As another example, a policy can be implemented on the devices connected to busy base stations in which the device is allowed to browse or conduct other best effort service activities at a relatively high throttling rate for a period of time, but if the device uses more than a certain amount of service (e.g., total data downloaded and/or uploaded) in a certain period of time then the device may be traffic controlled according to an adaptive throttling policy as described herein. In some embodiments, higher QoS level traffic cannot be throttled in such circumstances, such as VOIP traffic where real-time guaranteed bit rate is important to meet user service needs or expectations, while lower priority traffic such as interactive browsing and/or background download are throttled and/or blocked. In some embodiments, the QoS availability assessment processes described herein are adjusted so that higher QoS channels are not provided and provisioned in times or locations in which a given base station or group of base stations experience excess demand or demand above a given threshold.
In some embodiments, users or devices that have service plans with higher QoS levels, or service plans with higher priority during busy network periods have different traffic control policies (e.g., for QoS services and/or network capacity controlled services) applied to them that result in a higher level of traffic performance and/or a higher level of QoS service availability. For example, emergency service workers can be given higher traffic control access policies that result in differentiated services during peak busy times on the network or a portion of the network. In some embodiments, users can obtain a premium service plan for differentiated access during peak busy time periods or may use higher levels of QoS service settings and/or service plans to achieve differentiated service during peak busy periods. As another example, services that demand high levels of QoS classes, such as real-time voice services, instant messaging, push to talk, differentiated video streaming, and/or interactive gaming, are not traffic controlled to the same extent that other lower priority services or lower class service plans are traffic controlled during peak busy times. For example, this type of service differentiation can also be applied based on device type, user group, user standing, user reward zone points, and/or other criteria/measures as similarly described herein.
In some embodiments, the decision to control (e.g., reduce, increase, and/or otherwise control in some manner) the access traffic control settings as described above is made by the device service processor based on the device's assessment of the network capacity, which can be determined using various techniques as described herein. In some embodiments, the decision to control the access traffic control settings as described above is made by a service controller (e.g., or other interchangeable network equipment element or elements as described herein) connected to the device that provides instructions to the device to adjust the access policy settings. For example, the service controller can obtain the network capacity information from access equipment elements, from device reports of traffic capacity and/or quality as described herein, or from reports on traffic capacity and/or quality obtained from dedicated devices used for the purpose of assessing network capacity. In some embodiments, the decision to control the access traffic control settings as described above is based on the time of day, the day of week, or both to accommodate cyclical patterns in network capacity and traffic demand.
In some embodiments, a service controller (e.g., or another network equipment element or elements, as described herein) assesses network busy state and then controls device traffic demand by reducing the offered capacity for one or more service classes (e.g., for QoS services and/or network capacity controlled services) supported by the access network equipment elements, such as a wireless base station. In such embodiments, the service controller (e.g., or similar function) gathers the network capacity information with one of the techniques described herein and instructs one or more of the access network equipment elements to reduce the offered capacity for one or more levels of QoS classes and/or network capacity controlled service classes, to one or more of the devices connected to the access network equipment elements. For example, the determination of which devices to throttle back can be made based on an equal throttling of all devices of a given service plan status, or based on the device traffic usage patterns in the recent past as described herein, or based on a combination of service plan status and recent traffic usage patterns.
In some embodiments, the device is enabled with ambient services that have differentiated QoS services and/or network capacity controlled services as part of the ambient service offering. For example, ambient QoS techniques can be provided using the pre-assigned QoS policies for a given service activity set within the ambient service, or using an ambient service application that requests QoS through the QoS API. Other embodiments for providing QoS differentiated service activities within ambient service offerings will now be apparent to one of ordinary skill in the art. As another example, ambient network capacity controlled service techniques can be provided using the pre-assigned network capacity controlled policies for a given service activity set within the ambient service, monitoring and dynamically assigned techniques, and/or using an ambient service application that uses API or emulated API techniques, and/or other techniques as described herein.
In some embodiments, a QoS service control policy is adapted as a function of the type of network the device is connected to. For example, the QoS traffic control policies and/or the QoS service charging policies can be different when the device is connected to a wireless network (e.g., a 3G/4G network where there is in general less available QoS enabled traffic capacity) than when the device is connected to a wired network (e.g., a cable or DSL network where there is in general a higher level of QoS capacity available). In such embodiments, the device service processor and the service controller can coordinate to adapt the QoS service control policies and/or the QoS service charging policies to be different depending on which network the device is connected to. Similarly, the device QoS service control policy and/or QoS service charging policy can also be adapted based on whether the device is connected to a home wireless network or a roaming wireless network. In some embodiments, a network capacity controlled service control policy and/or a network capacity controlled charging policy is adapted as a function of the type of network the device is connected to, as similarly described herein.
In some embodiments, various of the QoS related techniques and/or network capacity controlled services techniques described herein are performed on the device using DAS techniques and/or on the service controller in secure communication with a verified service processor executed on the device using DAS techniques. In some embodiments, various of the QoS related techniques and/or network capacity controlled services techniques described herein are performed by/in coordination/communication with one or more intermediate network elements/functions for assisting in various techniques (e.g., functions) for QoS techniques and/or network capacity controlled services techniques as described herein.
As shown,
In some embodiments, service usage information includes network based service usage information (e.g., network based service usage measures or charging data records (CDRs), which can, for example, be generated by service usage measurement apparatus in the network equipment), which is obtained from one or more network elements (e.g., BTS/BSCs 125, RAN Gateways (not shown), Transport Gateways (not shown), Mobile Wireless Center/HLRs 132, AAA 121, Service Usage History/CDR Aggregation, Mediation, Feed 118, or other network equipment). In some embodiments, service usage information includes micro-CDRs. In some embodiments, micro-CDRs are used for CDR mediation or reconciliation that provides for service usage accounting on any device activity that is desired. In some embodiments, each device activity that is desired to be associated with a billing event is assigned a micro-CDR transaction code, and the service processor 115 is programmed to account for that activity associated with that transaction code. In some embodiments, the service processor 115 periodically reports (e.g., during each heartbeat or based on any other periodic, push, and/or pull communication technique(s)) micro-CDR usage measures to, for example, the service controller 122 or some other network element. In some embodiments, the service controller 122 reformats the heartbeat micro-CDR usage information into a valid CDR format (e.g., a CDR format that is used and can be processed by an SGSN or GGSN or other network elements/equipment used/authorized for generating or processing CDRs) and then transmits it to a network element/function for CDR mediation (e.g., CDR Storage, Aggregation, Mediation, Feed 118).
In some embodiments, CDR mediation is used to account for the micro-CDR service usage information by depositing it into an appropriate service usage account and deducting it from the user device bulk service usage account. For example, this technique provides for a flexible service usage billing solution that uses pre-existing solutions, infrastructures, and/or techniques for CDR mediation and billing. For example, the billing system (e.g., billing system 123 or billing interface 127) processes the mediated CDR feed from CDR mediation, applies the appropriate account billing codes to the aggregated micro-CDR information that was generated by the device, and then generates billing events in a manner that does not require changes to the existing billing systems (e.g., using new transaction codes to label the new device assisted billing capabilities). In some embodiments, network provisioning system 160 provisions various network elements/functions for authorization in the network, such as to authorize certain network elements/functions (e.g., CDR storage, aggregation, mediation, feed 118 or other network elements/functions) for providing micro-CDRs, reformatted micro-CDRs, and/or aggregated or reconciled CDRs.
As shown in
In some embodiments, various techniques for partitioning of device groups are used for partitioning the mobile devices 100 (e.g., allocating a subset of mobile devices 100 for a distributor, an OEM, a MVNO, and/or another partner or entity). As shown in
Those of ordinary skill in the art will appreciate that various other network architectures can be used for providing device group partitions and a settlement platform, and
In some embodiments, CDR storage, aggregation, mediation, feed 118 (e.g., service usage 118, including a billing aggregation data store and rules engine) is a functional descriptor for, in some embodiments, a device/network level service usage information collection, aggregation, mediation, and reporting function located in one or more of the networking equipment apparatus/systems attached to one or more of the sub-networks shown in
In some embodiments, a service processor download 170 is provided, which provides for periodical downloads/updates of service processors (e.g., service processor 115). In some embodiments, verification techniques include periodically updating, replacing, and/or updating an obfuscated version of the service processor, or performing any of these techniques in response to an indication of a potential compromise or tampering of any service processor functionality (e.g., QoS functionality and/or network capacity controlled services functionality) executed on or implemented on the device 100.
In some embodiments, the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) provides a device/network level service usage information collection, aggregation, mediation, and reporting function. In some embodiments, the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) collects device generated/assisted service usage information (e.g., micro-CDRs) for one or more devices on the wireless network (e.g., devices 100); and provides the device generated service usage information in a syntax and a communication protocol that can be used by the wireless network to augment or replace network generated usage information for the one or more devices on the wireless network. In some embodiments, the syntax is a charging data record (CDR), and the communication protocol is selected from one or more of the following: 3GPP, 3GPP2, or other communication protocols. In some embodiments, as described herein, the CDR storage, aggregation, mediation, feed 118 collects/receives micro-CDRs for one or more devices on the wireless network (e.g., devices 100). In some embodiments, the CDR storage, aggregation, mediation, feed 118 (e.g., or other network elements and/or various combinations of network elements) includes a service usage data store (e.g., a billing aggregator) and a rules engine for aggregating the collected device generated service usage information. In some embodiments, the network device is a CDR feed aggregator, and the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) also aggregates (network based) CDRs and/or micro-CDRs for the one or more devices on the wireless network; applies a set of rules to the aggregated CDRs and/or micro-CDRs using a rules engine (e.g., bill by account, transactional billing, revenue sharing model, and/or any other billing or other rules for service usage information collection, aggregation, mediation, and reporting), and communicates a new set of CDRs for the one or more devices on the wireless network to a billing interface or a billing system (e.g., providing a CDR with a billing offset by account/service). In some embodiments, a revenue sharing platform is provided using various techniques described herein. In some embodiments, QoS usage accounting/charging and/or network capacity controlled services usage accounting/charging is provided using various techniques described herein.
In some embodiments, the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) communicates a new set of CDRs (e.g., aggregated and mediated CDRs and/or micro-CDRs that are then translated into standard CDRs for a given wireless network) for the one or more devices on the wireless network to a billing interface (e.g., central billing interface 127) or a billing system (e.g., central billing system 123). In some embodiments, the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) communicates with a service controller (e.g., service controller 122) to collect the device generated service usage information (e.g., micro-CDRs) for the one or more devices on the wireless network. In some embodiments, the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) communicates with a service controller, in which the service controller is in communication with a billing interface or a billing system. In some embodiments, the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) communicates the device generated service usage information to a billing interface or a billing system. In some embodiments, the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) communicates with a transport gateway and/or a Radio Access Network (RAN) gateway to collect the network generated/based service usage information for the one or more devices on the wireless network. In some embodiments, the service controller 122 communicates the device assisted service usage information (e.g., micro-CDRs) to the CDR storage, aggregation, mediation, feed 118 (e.g., or other network elements and/or various combinations of network elements).
In some embodiments, the CDR storage, aggregation, mediation, feed 118 (e.g., or other network elements and/or various combinations of network elements) performs rules for performing a bill by account aggregation and mediation function. In some embodiments, the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) performs rules for performing a service billing function, as described herein, and/or for performing a service/transactional revenue sharing function, as described herein. In some embodiments, the service controller 122 in communication with the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) performs a rules engine for aggregating and mediating the device assisted service usage information (e.g., micro-CDRs). In some embodiments, a rules engine device in communication with the CDR storage, aggregation, mediation, feed 118 (e.g., or other network elements and/or various combinations of network elements) performs a rules engine for aggregating and mediating the device assisted service usage information (e.g., QOS service usage information and/or network capacity controlled services usage information).
In some embodiments, the rules engine is included in (e.g., integrated with/part of) the CDR storage, aggregation, mediation, feed 118. In some embodiments, the rules engine and associated functions, as described herein, is a separate function/device. In some embodiments, the service controller 122 performs some or all of these rules engine based functions, as described herein, and communicates with the central billing interface 127. In some embodiments, the service controller 122 performs some or all of these rules engine based functions, as described herein, and communicates with the central billing system 123.
In some embodiments, a settlement platform service is provided. For example, micro-CDRs can be aggregated and mediated to associate service usage for one or more services used by a communications device (e.g., a user of the communications device). A rules engine or another function can determine a revenue share allocation for the service usage for a particular service to determine the settlement for such service usage for the revenue sharing allocation/model and to distribute accounting and settlement information to one or more of carriers, distribution partners, MVNOs, wholesale partners, and/or other partners or entities. In some embodiments, the service is a transactional service.
In some embodiments, duplicate CDRs are sent from the network equipment to the billing system 123 that is used for generating service billing. In some embodiments, duplicate CDRs are filtered to send only those CDRs/records for devices controlled by the service controller and/or service processor (e.g., managed devices). For example, this approach can provide for the same level of reporting, lower level of reporting, and/or higher level of reporting as compared to the reporting required by the central billing system 123.
In some embodiments, a bill-by-account billing offset is provided. For example, bill-by-account billing offset information can be informed to the central billing system 123 by providing a CDR aggregator feed that aggregates the device assisted service usage data feed to provide a new set of CDRs for the managed devices to the central billing interface 127 and/or the central billing system 123. In some embodiments, transaction billing is provided using similar techniques. For example, transaction billing log information can be provided to the central billing interface 127 and/or the central billing system 123.
In some embodiments, the rules engine (e.g., performed by the service usage 118 or another network element, as described herein) provides a bill-by-account billing offset. For example, device assisted service usage information (e.g., micro-CDRs) includes a transaction type field or transaction code (e.g., indicating a type of service for the associated service usage information). For example, the rules engine can apply a rule or a set of rules based on the identified service associated with the device generated service usage information to determine a bill-by-account billing offset (e.g., a new CDR can be generated to provide the determined bill-by-account billing offset). In some examples, the determined bill-by-account billing offset can be provided as a credit to the user's service usage account (e.g., a new CDR can be generated with a negative offset for the user's service usage account, such as for network chatter service usage, or transactional service usage, or for any other purposes based on one or more rules performed by the rules engine).
As another example, for a transactional service, a first new CDR can be generated with a negative offset for the user's service usage account for that transactional service related usage, and a second new CDR can be generated with a positive service usage value to charge that same service usage to the transactional service provider (e.g., Amazon, eBay, or another transactional service provider). In some embodiments, the service controller 122 generates these two new CDRs, and the service usage 118 stores, aggregates, and communicates these two new CDRs to the central billing interface 127. In some embodiments, the service controller 122 generates these two new CDRs, and the service usage 118 stores, aggregates, and communicates these two new CDRs to the central billing interface 127, in which the central billing interface 127 applies rules (e.g., performs the rules engine for determining the bill-by-account billing offset).
In some embodiments, the service controller 122 sends the device generated CDRs to the rules engine (e.g., a service usage data store and rules engine, such as CDR storage, aggregation, mediation, feed 118), and the rules engine applies one or more rules, such as those described herein and/or any other billing/service usage related rules as would be apparent to one of ordinary skill in the art. In some embodiments, the service controller 122 generates CDRs similar to other network elements, and the rules (e.g., bill-by-account) are performed in the central billing interface 127. For example, for the service controller 122 to generate CDRs similar to other network elements, in some embodiments, the service controller 122 is provisioned on the wireless network (e.g., by network provision system 160) and behaves substantially similar to other CDR generators on the network).
In some embodiments, the service controller 122 is provisioned as a new type of networking function that is recognized as a valid, authorized, and secure source for CDRs by the other necessary elements in the network (e.g., CDR storage, aggregation, mediation, feed 118). In some embodiments, if the necessary network apparatus only recognize CDRs from certain types of networking equipment (e.g., a RAN gateway or transport gateway), then the service controller 122 provides authentication credentials to the other networking equipment that indicate that it is one of the approved types of equipment for providing CDRs. In some embodiments, the link between the service controller 122 and the necessary CDR aggregation and mediation equipment is secured, authenticated, encrypted, and/or signed.
In some embodiments, the CDR storage, aggregation, mediation, feed 118 discards the network based service usage information (e.g., network based CDRs) received from one or more network elements. In these embodiments, the service controller 122 provides the device assisted service usage information (e.g., device based CDRs or micro-CDRs) to the CDR storage, aggregation, mediation, feed 118 (e.g., the CDR storage, aggregation, mediation, feed 118 can just provide a store, aggregate, and communication function(s), as it is not required to mediate network based CDRs and device assisted CDRs), and the device based service usage information is provided to the central billing interface 127 or the central billing system 123.
In some embodiments, the device based CDRs (e.g., micro-CDRs) and/or new CDRs generated based on execution of a rules engine as described herein are provided only for devices that are managed and/or based on device group, service plan, or any other criteria, categorization, and/or grouping, such as based on ambient service or ambient service provider or transactional service or transactional service provider.
In some embodiments, QoS for DAS includes a service processor (e.g., any device assisted element/function) that facilitates coordination for and/or provisions wireless access/radio access bearers (e.g., RABs). In some embodiments, the service processor determines whether a request for QoS is authorized (e.g., according to QoS service level, user standing, available local network capacity (e.g., as reported by other device(s) and/or network)). In some embodiments, device QoS capacity demand reports provide and/or augment network capacity demand reports.
In some embodiments, QoS for DAS includes a service controller (e.g., any network device based service control element/function) that facilitates coordination for and/or provisions wireless access/radio access bearers (e.g., RABs) on a device (e.g., a communications device, such as a mobile wireless communications device and/or an intermediate networking device), on network, and/or on device plus network. In some embodiments, the service controller provides device QoS capacity demand reports to other network equipment/elements/functions, and then also provisions the RAB channel based on various criteria and determinations.
In some embodiments, QoS for DAS provides for device assisted monitoring, information, and/or functionality to facilitate QoS without and/or to assist network based monitoring, information, and/or functionality (e.g., Deep Packet Inspection (DPI) and/or provides such monitoring, information, and/or functionality that may not be available via network based monitoring, information, and/or functionality (e.g., encrypted activities on the device may not be accessible by DPI or other network based techniques). For example, QoS for DAS can assist in the QoS setup to facilitate the QoS setup and provide such information that may not otherwise be available using network based only techniques. For example, device assisted activity and/or service monitoring techniques can assist in classifying the QoS for the monitored activity and/or service using, for example, a QoS activity map (e.g., as described herein or other similar techniques). For example, using such device assisted techniques eliminates and/or minimizes DPI or other network based techniques that can give rise to privacy concerns/issues, network neutrality concerns/issues, and/or otherwise may not be able to provide similar or equivalent granular service/activity monitoring, as discussed above, and/or also off loads such processing from the network (e.g., network elements/devices/functionality) to the communications devices (e.g., at least for such communications devices that can perform such functions, based on their processing and/or memory capabilities, as would be apparent to one of ordinary skill in the art). In some embodiments, QoS for DAS includes the service provider for providing an initial authorization/clearance for a QoS request (e.g., using various techniques described herein), and the service controller determines if the QoS request should be authorized (e.g., based on various QoS authorization/clearance/approval criteria (e.g., QoS activity maps and/or QoS request rule) and/or network capacity, as described herein). In some embodiments, QoS for DAS includes the service provider for providing a QoS request including a QoS class to the service controller, and the service controller determines if the QoS request should be authorized, as described herein. In some embodiments, DAS for protecting network capacity provides for device assisted monitoring, information, and/or functionality to facilitate protecting network capacity without and/or to assist network based monitoring, information, and/or functionality (e.g., Deep Packet Inspection (DPI) and/or provides such monitoring, information, and/or functionality that may not be available via network based monitoring, information, and/or functionality (e.g., encrypted activities on the device may not be accessible by DPI or other network based techniques). In some embodiments, DAS for protecting network capacity provides for device assisted monitoring, information, and/or functionality to facilitate protecting network capacity without solely relying upon DPI and/or without any use or any significant use of DPI wireless network, which conserves network resources and network capacity by controlling device network access behavior at the device instead of deep in the core network at a DPI gateway (e.g., DPI based techniques consume over the air wireless network capacity even if chatty device behavior is blocked at a DPI gateway; in contrast, DAS for protecting network capacity techniques that do not use DPI based techniques for controlling device service usage can, for example, provide a device based usage notification and service selection UI that does not consume over the air wireless network capacity).
In some embodiments, QoS for DAS and/or DAS for protecting network capacity includes providing or facilitating reports for base station (BTS) for network capacity (e.g., sector, channel, busy state information or network capacity usage/availability, and/or network capacity expected demand) based on, for example, one or more of the following: monitored application usage on the communications device, monitored user activity on the communications device, location of the communications, other available networks, and/or other monitored or determined activity, service usage measure, and/or metric. In some embodiments, at or after execution of an application that is determined to require network service usage (e.g., may require increased wireless network bandwidth, such as based on a service usage activity map), QoS for DAS sends information to the network (e.g., a network controller or other network device element/function) that capacity demand is forthcoming for the communications device (e.g., potentially initiating a provisioning of a QoS radio access bearer (RAB) or other type of RAB).
In some embodiments, network capacity (e.g., busy state information) is collected from one or more communications devices in communication with a wireless network (e.g., network capacity/usage information measured from each respective communications device's perspective is determined and stored by the service processor on each respective communications device) and reported to the service controller, and the service controller (e.g., or another network element/function) uses this information to determine what resources are available for allocation to various levels of QoS (e.g., to respond to/facilitate various QoS requests) and/or to workload balance across multiple base stations and/or networks (e.g., wired networks, cellular, Wi-Fi, and/or other wireless networks).
In some embodiments, the service processor executed on the communications device sends a QoS request (e.g., a wireless network bearer channel reservation request or Radio Access Bearer (RAB) request) to the service controller. The service controller verifies the request using various verification techniques as described herein. In some embodiments, the service controller facilitates coordination of various device QoS requests with one or more base stations (BTSs) in communication with the communications device to provide for the requested QoS reservation to facilitate the new QoS session. In some embodiments, the service controller provides a QoS routing function by, for example, providing various QoS routing instructions to a device service processor (e.g., aggregating, prioritizing, queuing, authorizing, allocating reservations/RABs, denying, re-routing (such as to other BTSs and/or other networks) and/or otherwise managing QoS requests), in which the BTS may or may not be QoS aware. For example, QoS priority can be based on activity (e.g., service usage and/or application), service level, user standing, network capacity, time of day, and/or QoS priority can be purchased on a transaction basis, a session basis, a pre-pay basis or a plan basis. As another example, QoS priority can also vary by device type, user within a group, group, application type, content type, or any other criteria or measure and/or any combination thereof. In some embodiments, the service controller also facilitates coordination of various device QoS requests with other network elements/functions for QoS implementation and management to provide for an end to end QoS solution.
In some embodiments, QoS can be symmetric for two mobile devices or asymmetric. In some embodiments, QoS resource availability can be from communications devices, BTS(s), other network functions (e.g., service control, service controller and/or any other network elements/functions) or any combination thereof. In some embodiments, the service controller provides QoS demand information to another network element/function. In some embodiments, the service controller provides the central aggregator and policy decision point (PDP). In some embodiments, the service controller controls (e.g., at least in part) QoS related functions for communications devices, BTS(s), and/or a combination of both.
In some embodiments, charging (e.g., monitoring and/or determining associating charging or billing) for QoS service usage/transactions and/or network capacity controlled services usage/transactions is determined using various techniques described herein. For example, the service processor can assist in charging for QoS and/or network capacity controlled activities. In some embodiments, the service processor uses device assisted Charging Data Records (CDRs) or micro-CDRs to assist in charging for QoS and/or network capacity controlled activities (e.g., using QoS class related transaction codes and/or network capacity controlled related transaction codes), as described herein with respect to various embodiments. In some embodiments, charging for QoS and/or network capacity controlled services is performed in whole or in part by one or more network elements/functions (e.g., service controller, SGSN/GGSN/other gateways, and/or billing interfaces/servers).
In some embodiments, service usage information includes network based service usage information. In some embodiments, the network based service usage information includes network based CDRs. In some embodiments, service usage information includes device based service usage information. In some embodiments, device based service usage information includes device assisted CDRs, also referred to herein as micro-CDRs, as described herein. In some embodiments, micro-CDRs are used for CDR mediation or reconciliation that provides for service usage accounting on any device activity that is desired (e.g., providing granular service usage information, such as based on application layer service usage monitoring, transaction service usage monitoring, QoS activities/sessions/transactions, network capacity controlled activities/sessions/transactions, and/or other types of service usage information). In some embodiments, each device includes a service processor (e.g., a service processor executed on a processor of a communications device, such as a mobile device or an intermediate networking device that can communicate with a wireless network).
In some embodiments, each device activity that is desired to be associated with a billing event (e.g., for a QoS related billing event) is assigned a micro-CDR transaction code, and the service processor is programmed to account for that activity associated with that transaction code (e.g., various transaction codes can be associated with service usage associated with certain services, applications, and/or based on QoS classes or priorities, respectively, which can be used for providing granular service usage for these various Internet/network based services/sites/transactions and/or any other Internet/network based services/sites, which can include transactional based services). For example, using these techniques, as described herein, essentially any type of device activity (e.g., including QoS classes and prioritization and/or network capacity controlled classes and prioritization) can be individually accounted for and/or controlled (e.g., throttled, restricted, and/or otherwise controlled as desired). In some embodiments, the service processor periodically reports (e.g., during each heartbeat or based on any other periodic, push, and/or pull communication technique(s)) micro-CDR usage measures to, for example, a service controller or some other network element/function. In some embodiments, the service controller reformats the heartbeat micro-CDR usage information into a valid CDR format (e.g., a CDR format that is used and can be processed by an SGSN or GGSN or some other authorized network element/function for CDRs) and then transmits the reformatted micro-CDRs to a network element/function for performing CDR mediation.
In some embodiments, CDR mediation is used to properly account for the micro-CDR service usage information by depositing it into an appropriate service usage account and deducting it from the user device bulk service usage account. For example, this technique provides for a flexible service usage billing solution that uses pre-existing solutions for CDR mediation and billing. For example, the billing system can process the mediated CDR feed from CDR mediation, apply the appropriate account billing codes to the aggregated micro-CDR information that was generated by the device, and then generate billing events in a manner that does not require changes to existing billing systems, infrastructures, and techniques (e.g., using new transaction codes to label the new device assisted billing capabilities).
In some embodiments, the various QoS techniques performed on or by the communications device (e.g., using a service processor to provide or assist in providing QoS session provisioning, QoS policy management, QoS policy enforcement, and/or QoS accounting/charging, such as QoS charging records and reports) are verified (e.g., using various verification techniques described herein). In some embodiments, the various network capacity controlled services techniques performed on or by the communications device (e.g., using a service processor to provide or assist in providing network capacity controlled services policy management, network capacity controlled services policy enforcement, and/or network capacity controlled services charging, such as network capacity controlled services charging records and reports) are verified (e.g., using various verification techniques described herein).
For example, a QoS request, QoS related policy rules (e.g., QoS activity map, QoS related service plan and/or service policy settings) and implementation, QoS policy enforcement, and QoS charging are verified (e.g., periodically, per transaction, and/or based on some other criteria/metric). In some embodiments, verification techniques include one or more of the following: compare a network based service usage measure with a first service policy associated with the communications device, compare a device assisted service usage measure with the first service policy, compare the network based service usage measure to the device assisted service usage measure, perform a test and confirm a device assisted service usage measure based on the test, perform a User Interface (UI) notification (e.g., which can include a user authentication, password, question/answer challenge, and/or other authentication technique), and/or other similar verification techniques as will now be apparent to one of ordinary skill in the art. Accordingly, in some embodiments, QoS for DAS “closes the loop” for verification of various QoS related techniques, such as QoS requests, QoS grants, QoS usage, and/or QoS charging. In some embodiments, the service processor and the service controller serve as a verifiable QoS management/coordination system for other QoS elements/functions in network. In some embodiments, if such or other verification techniques determine or assist in determining that a QoS request, QoS report, and/or QoS policy behavior (e.g., or similarly, network capacity controlled services monitoring, reporting, and/or policy behavior) does not match expected requests, reports, and/or policy, then responsive actions can be performed, for example, the communications device (e.g., and/or suspect services) can be suspended, quarantined, killed/terminated, and/or flagged for further analysis/scrutiny to determine whether the device is malfunctioning, needs updating, has been tampered with or compromised, is infected with malware, and/or if any other problem exists.
In some embodiments, the communications device (e.g., the service processor) maintains a QoS flow table that associates or maps device activity to QoS level/class to RAB/QoS channel, and in some embodiments, the communications device also informs a QoS management network function/element of the relative priority of the QoS flows for the communications device (e.g., based on or using the QoS flow table). In some embodiments, the service controller receives or collects information from the communications device and maintains such a QoS flow table for the communications device and, in some embodiments, the service controller also informs a QoS management network function/element of the relative priority of the QoS flows for the communications device (e.g., based on or using the QoS flow table). In some embodiments, flows can be assigned to activities originating at the communications device in a transparent way, or simply by activity class or user preference, or using other techniques.
In some embodiments, the communications device maintains a table of QoS billing rates, scheduled transmission times, and/other QoS related information to implement an overlay MAC at the data networking level to manage QoS on legacy networks that are not QoS MAC enabled and/or do not have the various functionality to support QoS controls (e.g., and such techniques can also be used to provide for QoS functionality across different networks). In some embodiments, QoS related policies are exchanged between roaming and home service controllers to facilitate QoS support while roaming on a non-home network(s).
In some embodiments, the communications device serves as a network capacity indicator (e.g., collecting network capacity information for a local cell and communicating or reporting that network capacity information to the service controller). For example, permanent local cell communications devices can be placed in local cell areas to augment legacy equipment for such network capacity indicator/reporting functions. Various other techniques for determining network capacity and/or network availability are described herein.
In some embodiments, service partners and/or service providers can subsidize in whole or in part to upgrade a given user or group of users to better QoS related service level agreement (SLA)/class for a preferred destination. In some embodiments, based on monitored service usage and/or other monitored behavior of the communications device, such subsidized QoS upgrade/offers can be presented to a user of the communications device (e.g., as an incentive/reward for desired or preferred user behavior or for other reasons). Similarly, in some embodiments, these techniques are also applied to network capacity controlled services.
In some embodiments, QoS charging is based on QoS channel/reservation, service flow, or RAB charging (e.g., single flow per RAB, multi-flow per RAB, multi-RAB per flow). In some embodiments, charging (e.g., for QoS and/or for network capacity controlled services) is based on one or more of the following: network busy state, time criteria, user service class request, traffic volume and class, time and class, network capacity (e.g., network busy state) and class, time of day and class, location, traffic type, application type, application class, destination, destination type, partner service, and/or other criteria/measures. In some embodiments, QoS charging is verified using the various verification techniques described herein (e.g., test charging events). In some embodiments, network capacity controlled services charging is verified using the various verification techniques described herein (e.g., test charging events). In some embodiments, QoS charging is by data usage (e.g., by Megabyte (MB)), service flow by time by QoS class, speed by time, network busy state, time of day/day of week, service plan, current network, and/or other criteria/measures. In some embodiments, network capacity controlled services charging is by data usage (e.g., by Megabyte (MB)), service flow by time by network capacity controlled services class, speed by time, network busy state, time of day/day of week, service plan, current network, and/or other criteria/measures.
In some embodiments, QoS for DAS includes coordinating functions with one or more of the following: DAS elements/functions, Radio Access Network (RAN), Transport network, Core network, GRX network, IPX network, and/or other networks/elements/functions.
As shown,
In some embodiments,
For example, the architecture 300 provides a relatively full featured device based service processor implementation and service controller implementation. As shown, this corresponds to a networking configuration in which the service controller 122 is connected to the Internet 120 and not directly to the access network 1610. As shown, a data plane (e.g., service traffic plane) communication path is shown in solid line connections and control plane (e.g., service control plane) communication path is shown in dashed line connections. As will be apparent to one of ordinary skill in the art, the division in functionality between one device agent and another is based on, for example, design choices, networking environments, devices and/or services/applications, and various different combinations can be used in various different implementations. For example, the functional lines can be re-drawn in any way that the product designers see fit. As shown, this includes certain divisions and functional breakouts for device agents as an illustrative implementation, although other, potentially more complex, embodiments can include different divisions and functional breakouts for device agent functionality specifications, for example, in order to manage development specification and testing complexity and workflow. In addition, the placement of the agents that operate, interact with or monitor the data path can be moved or re-ordered in various embodiments. For example, the functional elements shown in
As shown in
As shown in
In some embodiments, the service control server link 1638 provides for securing, signing, encrypting and/or otherwise protecting the communications before sending such communications over the service control link 1653. For example, the service control server link 1638 can send to the transport layer or directly to the link layer for transmission. In another example, the service control server link 1638 further secures the communications with transport layer encryption, such as TCP TLS or another secure transport layer protocol. As another example, the service control server link 1638 can encrypt at the link layer, such as using IPSEC, various possible VPN services, other forms of IP layer encryption and/or another link layer encryption technique.
As shown in
In some embodiments, the access control integrity server 1654 (and/or some other agent of service controller 122) acts on access control integrity agent 1694 (e.g., service policy security agent) reports and error conditions. Many of the access control integrity agent 1654 checks can be accomplished by the server. For example, the access control integrity agent 1654 checks include one or more of the following: service usage measure against usage range consistent with policies (e.g., usage measure from the network and/or from the device); configuration of agents; operation of the agents; and/or dynamic agent download.
In some embodiments, the access control integrity server 1654 (and/or some other agent of service controller 122) verifies device service policy implementations by comparing various service usage measures (e.g., based on network monitored information, such as by using IPDRs or CDRs, and/or local service usage monitoring information) against expected service usage behavior given the policies that are intended to be in place (e.g., a QoS policy and/or a network capacity controlled services policy). For example, device service policy implementations can include measuring total QoS data passed, QoS data passed in a period of time, IP addresses, data per IP address, and/or other measures such as location, downloads, email accessed, URLs, and comparing such measures expected service usage behavior given the policies that are intended to be in place.
In some embodiments, the access control integrity server 1654 (e.g., and/or some other agent of service controller 122) verifies device service policy, and the verification error conditions that can indicate a mismatch in QoS service measure and QoS service policy include one or more of the following: unauthorized network access (e.g., access beyond ambient service policy limits); unauthorized network speed (e.g., average speed beyond service policy limit); network data amount does not match QoS policy limit (e.g., device not stop at limit without re-up/revising service policy); unauthorized network address; unauthorized service usage (e.g., VOIP, email, and/or web browsing); unauthorized application usage (e.g., email, VOIP, email, and/or web); service usage rate too high for plan, and policy controller not controlling/throttling it down; and/or any other mismatch in service measure and service policy. Accordingly, in some embodiments, the access control integrity server 1654 (and/or some other agent of service controller 122) provides a policy/service control integrity service to continually (e.g., periodically and/or based on trigger events) verify that the service control of the device has not been compromised and/or is not behaving out of policy (e.g., a QoS policy and/or a network capacity controlled services policy).
As shown in
As shown in
In some embodiments, the policy management server 1652 provides adaptive policy management on the device. For example, the policy management server 1652 can issue policy settings and objectives and rely on the device based policy management (e.g., service processor 115) for some or all of the policy adaptation. This approach can require less interaction with the device thereby reducing network chatter on the service control link 1653 for purposes of device policy management (e.g., network chatter is reduced relative to various server/network based policy management approaches described above). This approach can also provide robust user privacy embodiments by allowing the user to configure the device policy for user privacy preferences/settings so that, for example, sensitive information (e.g., geo-location data, website history, and/or other sensitive information) is not communicated to the network without the user's approval. In some embodiments, the policy management server 1652 adjusts service policy based on time of day. In some embodiments, the policy management server 1652 receives, requests, and/or otherwise obtains a measure of network availability/capacity and adjusts traffic shaping policy and/or other policy settings based on available network availability/capacity (e.g., a network busy state).
As shown in
As shown in
As shown in
As shown in
As shown in
As shown in
As shown in
As shown in
In some embodiments, the service processor 115 and service controller 122 are capable of assigning multiple service profiles associated with multiple service plans that the user chooses individually or in combination as a package. For example, a device 100 starts with ambient services that include free transaction services wherein the user pays for transactions or events rather than the basic service (e.g., a news service, eReader, PND service, pay as you go session Internet) in which each service is supported with a bill by account capability to correctly account for any subsidized partner billing to provide the transaction services (e.g., Barnes and Noble may pay for the eReader service and offer a revenue share to the service provider for any book or magazine transactions purchased from the device 100). In some embodiments, the bill by account service can also track the transactions and, in some embodiments, advertisements for the purpose of revenue sharing, all using the service monitoring capabilities disclosed herein. After initiating services with the free ambient service discussed above, the user may later choose a post-pay monthly Internet, email, and SMS service. In this case, the service controller 122 would obtain from the billing system 123 in the case of network based billing (e.g., or the service controller 122 billing event server 1622 in the case of device based billing) the billing plan code for the new Internet, email and SMS service. In some embodiments, this code is cross referenced in a database (e.g., the policy management server 1652) to find the appropriate service profile for the new service in combination with the initial ambient service. The new superset service profile is then applied so that the user maintains free access to the ambient services, and the billing partners continue to subsidize those services, the user also gets access to Internet services and may choose the service control profile (e.g., from one of the embodiments disclosed herein). The superset profile is the profile that provides the combined capabilities of two or more service profiles when the profiles are applied to the same device 100 service processor. In some embodiments, the device 100 (service processor 115) can determine the superset profile rather than the service controller 122 when more than one “stackable” service is selected by the user or otherwise applied to the device. The flexibility of the service processor 115 and service controller 122 embodiments described herein allow for a large variety of service profiles to be defined and applied individually or as a superset to achieve the desired device 100 service features.
As shown in
As shown in
In some embodiments, device assisted services (DAS) techniques for providing an activity map for classifying or categorizing service usage activities to associate various monitored activities (e.g., by URL, by network domain, by website, by network traffic type, by application or application type, and/or any other service usage activity categorization/classification) with associated IP addresses are provided. In some embodiments, a policy control agent (not shown), service monitor agent 1696 (e.g., charging agent), or another agent or function (or combinations thereof) of the service processor 115 provides a DAS activity map. In some embodiments, a policy control agent (not shown), service monitor agent, or another agent or function (or combinations thereof) of the service processor provides an activity map for classifying or categorizing service usage activities to associate various monitored activities (e.g., by Uniform Resource Locator (URL), by network domain, by website, by network traffic type, by socket (such as by IP address, protocol, and/or port), by socket id (such as port address/number), by port number, by content type, by application or application type, and/or any other service usage activity classification/categorization) with associated IP addresses and/or other criteria/measures. In some embodiments, a policy control agent, service monitor agent, or another agent or function (or combinations thereof) of the service processor determines the associated IP addresses for monitored service usage activities using various techniques to snoop the DNS request(s) (e.g., by performing such snooping techniques on the device 100 the associated IP addresses can be determined without the need for a network request for a reverse DNS lookup). In some embodiments, a policy control agent, service monitor agent, or another agent or function (or combinations thereof) of the service processor records and reports IP addresses or includes a DNS lookup function to report IP addresses or IP addresses and associated URLs for monitored service usage activities. For example, a policy control agent, service monitor agent, or another agent or function (or combinations thereof) of the service processor can determine the associated IP addresses for monitored service usage activities using various techniques to perform a DNS lookup function (e.g., using a local DNS cache on the monitored device 100). In some embodiments, one or more of these techniques are used to dynamically build and maintain a DAS activity map that maps, for example, URLs to IP addresses, applications to IP addresses, content types to IP addresses, and/or any other categorization/classification to IP addresses as applicable. In some embodiments, the DAS activity map is used for various DAS traffic control and/or throttling techniques as described herein with respect to various embodiments for providing QoS for DAS and/or for providing DAS for protecting network capacity. In some embodiments, the DAS activity map is used to provide the user various UI related information and notification techniques related to service usage as described herein with respect to various embodiments. In some embodiments, the DAS activity map is used to provide service usage monitoring, prediction/estimation of future service usage, service usage billing (e.g., bill by account and/or any other service usage/billing categorization techniques), DAS techniques for ambient services usage monitoring, DAS techniques for generating micro-CDRs, and/or any of the various other DAS related techniques as described herein with respect to various embodiments.
In some embodiments, all or a portion of the service processor 115 functions disclosed herein are implemented in software. In some embodiments, all or a portion of the service processor 115 functions are implemented in hardware. In some embodiments, all or substantially all of the service processor 115 functionality (e.g., as discussed herein) is implemented and stored in software that can be performed on (e.g., executed by) various components in device 100. In some embodiments, it is advantageous to store or implement certain portions or all of service processor 115 in protected or secure memory so that other undesired programs (e.g., and/or unauthorized users) have difficulty accessing the functions or software in service processor 115. In some embodiments, service processor 115, at least in part, is implemented in and/or stored on secure non-volatile memory (e.g., non volatile memory can be secure non-volatile memory) that is not accessible without pass keys and/or other security mechanisms (e.g., security credentials). In some embodiments, the ability to load at least a portion of service processor 115 software into protected non-volatile memory also requires a secure key and/or signature and/or requires that the service processor 115 software components being loaded into non-volatile memory are also securely encrypted and appropriately signed by an authority that is trusted by a secure software downloader function, such as service downloader 1663 as shown in
Referring to
Referring to
Referring to
In some embodiments, QoS techniques as described herein are implemented in the device (e.g., using the service processor 115) and one or more other network elements/functions, such as the BTS 125, service controller 125, RAN, SGSN/GGSN/other gateways and/or other network elements/functions, in which various of the QoS related functions can be distributed or allocated to such network elements/functions based on various design/network architecture approaches as will now be apparent to one of ordinary skill in the art, in which QoS related activities and/or functions at the device 100 are verified using various verification techniques described herein.
In some embodiments, the device determines QoS availability by directly querying QoS link reservation equipment in the network (e.g., an access point, such as the BTS 125). In some embodiments, the device determines QoS availability based on an intermediate network function that coordinates QoS requests with one or more network QoS link resources. In some embodiments, the device requests a QoS reservation in advance of QoS link establishment with one or more QoS network link resources. In some embodiments, in response to a QoS request, a QoS channel is reported as available only if/after it is determined that the necessary one or more QoS links required to create the QoS channel are available, and, for example, the QoS channel can then be reserved based on a confirmation or automatically be reserved in response to the QoS request.
In some embodiments, the service plan includes a list of activity policies, and each activity policy in the service plan specifies how the activity policy is modified by rules state information. In some embodiments, each activity policy then becomes the instruction for the engine (e.g., QoS mapping function 520) that maps the activity policy to QoS activity rules 530. In some embodiments, service controller 122 downloads QoS mapping function 520, which is implemented by service processor 115.
In some embodiments, the service processor determines (e.g., and classifies) application/service usage activity demand with or without granular application/service usage activity (e.g., depending on various user/service plan/service provider/network/legal and/or other privacy restrictions and/or any other related requirements or settings). For example, policies (e.g., service policy settings and/or service profile settings) can be downloaded to provide such application/service usage activity monitoring rules and a QoS activity map for assigning such monitored activities to various QoS classes or priorities, and, in some embodiments, such monitoring and the QoS activity map can also be implemented using various verification techniques described herein (e.g., periodically audited, tested, compared with network service usage information). In some embodiments, the QoS activity map is based on a service plan, service profile, and/or service policy settings associated with the communications device. In some embodiments, the QoS activity map is based on a device group and/or user group. In some embodiments, the QoS activity map is based on user input (e.g., a user of the communications device can identify QoS classes/service levels for various applications and/or service activities, in response to requests for user input, based on user configurations, user defined rules (e.g., to eliminate or mitigate privacy and/or net neutrality concerns/issues), and/or confirmed monitored user behavior QoS related patterns or preferences). In some embodiments, the QoS activity map includes mappings/associations based on one or more of the following: a user preference for a given destination, destination class, application, application class (e.g., by application class instead of with respect to a specific application can also eliminate or mitigate privacy and/or net neutrality concerns/issues), flow, traffic or flow class, time period, time of day, location, network busy state (e.g., provide QoS when you can, then charge more when busy, notify user of busy state), device type, user type, user plan, user group, user standing, partner service, tokens, service type, and/or other criteria or measures.
In some embodiments, various techniques described herein are managed for device 100 for incoming and/or outgoing QoS requests. In some embodiments, as shown in
In some embodiments, the service monitor agent and/or other agents implement virtual traffic tagging by tracking or tracing packet flows through the various communication stack formatting, processing and encryption steps, and providing the virtual tag information to the various agents that monitor, control, shape, throttle or otherwise observe, manipulate or modify the traffic. This tagging approach is referred to herein as virtual tagging, because there is not a literal data flow, traffic flow or packet tag that is attached to flows or packets, and the book-keeping to tag the packet is done through tracking or tracing the flow or packet through the stack instead. In some embodiments, the application interface and/or other agents identify a traffic flow, associate it with a service usage activity and cause a literal tag to be attached to the traffic or packets associated with the activity. This tagging approach is referred to herein as literal tagging. There are various advantages with both the virtual tagging and the literal tagging approaches. For example, it can be preferable in some embodiments to reduce the inter-agent communication required to track or trace a packet through the stack processing by assigning a literal tag so that each flow or packet has its own activity association embedded in the data. As another example, it can be preferable in some embodiments to re-use portions of standard communication stack software or components, enhancing the verifiable traffic control or service control capabilities of the standard stack by inserting additional processing steps associated with the various service agents and monitoring points rather than re-writing the entire stack to correctly process literal tagging information, and in such cases, a virtual tagging scheme may be desired. As yet another example, some standard communication stacks provide for unused, unspecified or otherwise available bit fields in a packet frame or flow, and these unused, unspecified or otherwise available bit fields can be used to literally tag traffic without the need to re-write all of the standard communication stack software, with only the portions of the stack that are added to enhance the verifiable traffic control or service control capabilities of the standard stack needing to decode and use the literal tagging information encapsulated in the available bit fields. In the case of literal tagging, in some embodiments, the tags are removed prior to passing the packets or flows to the network or to the applications utilizing the stack. In some embodiments, the manner in which the virtual or literal tagging is implemented can be developed into a communication standard specification so that various device or service product developers can independently develop the communication stack and/or service processor hardware and/or software in a manner that is compatible with the service controller specifications and the products of other device or service product developers.
It will be appreciated that although the implementation/use of any or all of the measurement points illustrated in
Referring to
As shown in
As shown in
Referring to
Additional Embodiments of DAS for Protecting Network Capacity
In some embodiments, DAS for protecting network capacity includes classifying a service activity as a network capacity controlled service and implementing a network capacity controlled services policy. In some embodiments, DAS for protecting network capacity includes device assisted/based techniques for classifying a service activity as a network capacity controlled service and/or implementing a network capacity controlled services policy. In some embodiments, DAS for protecting network capacity includes network assisted/based techniques (e.g., implemented on a network element/function, such as a service controller, a DPI gateway, a BTS/BTSC, etc., or a combination of network elements) for classifying a service activity as a network capacity controlled service and/or implementing a network capacity controlled services policy. In some embodiments, DAS for protecting network capacity includes providing a network access API or an emulated or virtual network access API (e.g., such an API can provide network busy state information and/or other criteria/measures and/or provide a mechanism for allowing, denying, delaying, and/or otherwise controlling network access). In some embodiments, DAS for protecting network capacity includes implementing a service plan that includes a network capacity controlled services policy (e.g., for differential network access control and/or differential charging for network capacity controlled services, which can also be based on a network busy state and/or other criteria/measures).
In some embodiments, DAS for protecting network capacity techniques also provide improved user privacy and facilitate network neutrality requirements. In contrast, network based techniques (e.g., DPI based techniques) can give rise to user privacy and network neutrality concerns and problems as discussed above. In some embodiments, DAS for protecting network capacity techniques include allowing a user to specify (e.g., permit or not permit) whether the network is aware of the user's Internet behavior (e.g., using UI input). In some embodiments, DAS for protecting network capacity techniques include allowing a user to select how they want their traffic usage and service plan costs to be managed.
In some embodiments, the service usage control policy includes a service usage notification policy. In some embodiments, the user notification includes one or more of the following: a notification that the application to be downloaded and/or launched is a network capacity controlled service; a list of one or more service activities (e.g., applications, OS/other software functions/utilities, and/or other functions/utilities as described herein) that have a network capacity controlled services classification; type of service policy in effect for one or more network capacity controlled services; notification that a service activity belongs to a network capacity controlled services class; notification that a service activity that is classified as network capacity controlled service can have the service class changed; notification that if the service class is changed for a service activity the service charges will change; notification that one or more networks are available (e.g., one or more alternative networks and/or network busy state information and/or charging information and/or incentives associated with such networks), a service plan upgrade/downgrade offer/option; and an offer for a service plan that rewards a user that responds to the notification a service plan is lower cost/discounted for responding to notification to use or not to use service activity based on usage level warning notification. In some embodiments, the user notification includes a user preference selection, including one or more of the following: a provision to associate an access policy control with the application (e.g., allow/block, notify of usage, notify of usage at a given threshold, traffic control settings, allow during certain times, allow when network not busy, and/or other policy controls as described herein), an over-ride option for selecting the service usage control policy; a modify option to select the service usage control policy; a select option to select a new service plan (e.g., an option to review and select alternative/new service plan upgrade/downgrade options), and an acknowledgement request (e.g., to confirm/acknowledge receipt of the notification, in which the acknowledgement can be transmitted to a network element/function and/or stored locally for later reference/transmission).
In some embodiments, before a given device application, process, function, OS service or other service activity is allowed to start, the intention to start is intercepted by a launch manager, the background service policy set or the network protection service policy set for the service activity is retrieved, and any necessary user notification or service launch control policies are implemented prior to allowing the service activity to launch. In such embodiments, a launch intercept manager may be used to implement this functionality. In some embodiments, this launch intercept manager is provided with a list identifying the service activities (e.g., application identifiers, OS function identifiers, aggregate service activity identifiers, and/or component service activity identifiers) that have a launch control policy in effect. In some embodiments, the list of launch control policies includes blocking or delaying launch of the one or more service activities. In some embodiments, the launch control policy includes a user notification before, during or after the service activity is launched. In some embodiments, the user is informed that a service activity that has a background service control policy in effect or a network protection service control policy in effect is attempting to launch, is about to launch or has launched. In a further set of embodiments, the launch is held up until the user is notified and is allowed to decide if they would like to launch the service activity. In some embodiments, the user notification includes a message that the service activity attempting to launch consumes a large amount of service usage and asks the user if they would like to continue (e.g., “This application consumes a large amount of data, would you like to continue?”, “This application consumes data even when you are not using it, would you like to continue?” “This application consumes data while you are roaming which adds cost to your usage bill, would you like to continue?”, etc). In some embodiments, the decision on whether or not to launch a service activity is pre-programmed into the list identifying the service activities (e.g., application identifiers, OS function identifiers, aggregate service activity identifiers, and/or component service activity identifiers) that have a launch control policy in effect. In some embodiments a portion of the list is pre-programmed by the user in accordance with user preference for controlling usage of service activities. In some embodiments, a portion of the list is pre-programmed by a network element (e.g., a service controller) in accordance with network background service or network protection service policies specified by a service policy design management system operated by a service provider as described herein. In some embodiments, the policy implementation defined by the list identifying the service activities (e.g., application identifiers, OS function identifiers, aggregate service activity identifiers, and/or component service activity identifiers) that have a launch control policy in effect is verified to ensure that the user or malicious software has not defeated the policy enforcement specified in the list. In some embodiments the list identifying the service activities that have a launch control policy in effect includes launch policies that are a function of one or more of: background service state, network busy state (or performance state or QoS state), type of network the device is connected to, home or roaming connection, time of day or day of week.
In some embodiments, the various design techniques described herein that allow for intercepting a service activity intention to launch, and applying a background service policy set or a network protection service policy set can be designed into the OS itself. For example, the intercept and policy implementation functions can be designed into the activity manager, broadcast intent manger, media service manager, service manager, or other application or service activity management function in the Android OS. One of ordinary skill in the art will recognize that similarly, the various design techniques described herein that allow for intercepting a service activity intention to launch, and applying a background service policy set or a network protection service policy set can be designed into application launch management functions in the iPhone OS, windows mobile OS, windows PC OS, Blackberry OS, Palm OS, and other OS designs.
In some embodiments, the pre-launch user notification information indicates one or more of: typical service usage or cost, or projected service usage or cost for the service activity attempting to launch. In some embodiments, the user sets limitations on access for one or more service activities and once this limit is hit then when the service activities with exceeded limits attempt to launch the user is notified. In some embodiments, the user chooses from a set of service restrictions rather than simply blocking or allowing service activity launch, with example service restrictions including but not limited to: a pre-configured set of restriction policies to chose from (e.g., full access, limited access, highly restricted access or block access), block, throttle, delay, aggregate and hold, limit amount of usage per unit time, cap usage, set limit for additional notification, specify type of network, specify busy state (performance, QoS) or background state, or choose from pre-configured settings options.
In some embodiments, the user notification occurs after the user attempts to download or load an application onto the device (e.g., an application downloaded from the web or an online application store for a smart phone or other wireless/network computing device, such as an Apple iPhone or iPad, or Google Android/Chrome based device). In some embodiments, the user notification occurs after the user attempts to run the service activity or to initiate usage of a cloud based service/application (e.g., Google or Microsoft cloud service based apps). In some embodiments, the user notification occurs after one or more of the following: the service usage activity hits a usage threshold event, the service usage activity attempts a network service usage that satisfies a pre-condition, an update to a network capacity protection service activity classification list or policy set, and a network message is sent to the device triggering the notification. In some embodiments, the user notification provides information on the service usage activity that is possible, typical, or likely for the service usage activity. In some embodiments, the user notification includes a user option for obtaining more information about the service usage of the service activity (e.g., a message that the service usage activity may result in a high service usage and/or that the service usage activity may or will result in a high service usage as compared in some way to a limit of the current service plan) to make informed user preference settings.
In some embodiments, a user notification includes displaying (e.g., and as applicable, allowing users to provide UI input) one or more of the following: current and/or past/historical/logged network service usage activity list, current and/or past/historical/logged network capacity controlled service usage activities, current activity policy settings, current or available networks, service plan options (e.g., for how to treat one or more network capacity controlled service traffic types), selection option(s) to assign a network capacity controlled service activity into a different priority traffic control and/or charging buckets, network service usage by activity (e.g., network capacity controlled services and other services), network busy state (e.g., and with resulting policies in force), service activity policy setting vs. busy state and time/day/week, network service activity priority, network service activity usage statistics (e.g., vs. network busy state and/or network service usage control policy state).
In some embodiments, a UI notification is displayed when user attempts a network capacity controlled service activity during a network busy state (e.g., that modifies a network capacity controlled services policy). In some embodiments, the UI notification includes information on service plan choice and a network capacity controlled services policy over-ride option (e.g., one time, time window, usage amount, permanent by activity, and/or all), charging information based on a user selection, and/or service plan upgrade information and options.
In some embodiments, a UI notification is displayed for user input for preferences/configurations for multiple networks (e.g., WiFi, 4G, 3G, and/or other wired or wireless access networks) including charging policy. In some embodiments, a UI notification is displayed when a specified network traffic service usage activity (e.g., based on network capacity controlled services classification, QoS classification, priority classification, time based criteria, network capacity, service plan, charging criteria, and/or other criteria/measures) is being attempted or is occurring and providing options (e.g., allow, block, delay, throttle, and/or other options).
In some embodiments, a UI fuel gauge is displayed (e.g., to depict current and/or historical network service usage, for example, relative to a service plan for the device, by network, relative to network busy state, time based criteria, and/or other criteria/measures). In some embodiments, a user notification includes a communication sent to the user (e.g., an email, SMS or other text message, voice message/call, and/or other electronic form of communication). In some embodiments, the communication sent to the user includes network service usage information, network capacity controlled service usage related information, and/or an instruction to log into a web page or send a communication for more information (e.g., regarding an information update and/or alert or warning message, such as related to network service usage and/or charging for network service usage).
In some embodiments, a notification (e.g., a user or network service cloud notification) is generated based on an aggregate service activity reports usage (e.g., allows network provider to generate user notifications and/or to notify application provider/service activity provider). In some embodiments, a notification (e.g., a user or network service cloud notification) is generated based on a publishing of an updated/new network capacity controlled services list based on an aggregate monitored activity (e.g., based on a service plan, velocity, sockets opening frequency/rate (e.g., messaging layer behavior), total data usage, peak busy time usage to formulate or update black list for monitoring, notifying, and/or controlling, which can be applied to one, multiple, group, or all devices). In some embodiments, a notification (e.g., a user or network service cloud notification) is generated based on data usage trends for particular device relative to an associated service plan and/or other comparable devices or data usage thresholds/statistical based data usage measures.
In some embodiments an application is actually composed of several component applications, processes or functions. Examples of this include but are not limited to: the components of a Java application JAR file; applications that use OS functions; applications that use a proxy service function; applications, functions or processes that coordinate with one another to implement a composite process, function or application; and OS process functions that support an application or overall OS function. In such embodiments it is important to be able to categorize all applications, functions and processes on a device that contribute to the service usage of a service activity so that the service activity can be monitored for service usage, have the service usage accounted for, implement the appropriate user notification when one or more service activity components attempts to start or use the network, implement the appropriate user notification when one or more service activity components reaches a pre-determined service usage level that requires user notification, and implement the appropriate background service or network protection service usage controls as specified herein ((including but not limited to for example: block network access, restrict network access, throttle network access, delay network access, aggregate and hold network access, select for time of day network access restrictions, select network type restrictions, select roaming network access restrictions, select service usage restrictions such as a usage limit, select service cost restrictions such as a cost limit or otherwise place on another form of background service status or network usage restriction as described herein). In the case of service activity components that belong exclusively to one aggregate service activity (e.g., an application, application JAR file or OS function), this may be accomplished by including each of the component service activities on a list that identifies the service activity components that belong to the aggregate service activity, and then monitoring, possibly controlling and providing user notifications based on the aggregate or component behavior of each service activity in accordance with the policies specified for the aggregate service activity. For example, it is necessary to group all application launch behavior and/or network access behavior under the monitoring, launch, notification, accounting and background service controls or network protection service controls (or other background or network protection service policies as specified herein) in accordance with the background service or network protection service policies for the aggregate application that the JAR file supports. As another example, if an OS network synch or update function utilizes various software components or processes to implement the network synch or update function, then each of the software components or process must be monitored and aggregated under the background service policies or network protection service policies for the aggregate OS synch or update function.
In some embodiments, this ability to group usage for a related set of service activity components dedicated to an aggregate service activity as described herein is used to improve usage reporting of service activities to a service controller for the purpose of statistically identifying service activities that are candidates for background service policy controls or network protections service policy controls.
In some cases, multiple applications, processes, functions, OS services or other service activities can utilize a common set of component software applications, processes, functions or OS services. In such cases, in order to implement background service policies and/or network protection service policies for service activity monitoring and accounting, service activity launch control, user notification, or network access control as described herein, it is necessary to associate the specific network access data or information flows to and from the common component software applications, processes or functions that belong to the specific initiating application, process, function or other service activity that is to be managed according to a background service or network protection service policy set. In what follows, a specific set of examples is provided on how to map common component service activity for a set of common OS functions referred to as proxy service functions to a specific application, process, function, OS service or other service activity for the purpose of implementing a background service policy set or a network protection service policy set as described herein. Once these examples are reviewed, it will be obvious to one of ordinary skill in the art how to apply similar mapping of service activity for a common set of components to a service activity that is to be managed in accordance with a background service policy set or a network protection service policy set as described herein.
In some embodiments, this ability to group usage for a common set of service activity components as described herein is used to improve usage reporting of service activities to a service controller for the purpose of statistically identifying service activities that are candidates for background service policy controls or network protections service policy controls.
In some embodiments, a proxy network service manager refers to an intermediary data flow function in a device operating system that sits on a data path between a device application and a device networking stack interface to provide a level of network service abstraction from the network stack interface, a higher level service function above the network stack interface, enhanced or special traffic processing functions, media service transfer management, file download service, HTTP proxy service functions, QoS differentiation, or other similar or related higher level traffic processing. Example Proxy Service Managers include the following: media service manager (e.g., android media service library function), email service manager, DNS function, software download service manager, media download manager (e.g., audio player, streaming media player, movie downloader, media service OS function, etc.), data download service manager, Android “media” library function, Android.net library function, Jave.net library function, Apache library function, other similar software/library functions or services in other device operating systems, SMTP/IMAP/POP proxy, HTTP proxy, IM proxy, VPN service manager, SSL proxy, etc. Herein these alternative network access data flows that are initiated by an application are termed application proxy service flows. In such embodiments an app can sometimes simply request a network access service activity from an OS component such as a proxy service component rather than directly accessing the network. In such embodiments, in order to implement background service controls or user notification of application service usage, it is necessary to monitor the application proxy service flows, classify them as being initiated by or belonging to a particular application or service activity, and implement the proper background service classifications, user notifications, application process launch intercept, background service accounting, and background service usage restrictions as described herein in accordance with the policies intended for the initiating application or service activity. This is accomplished by inserting service usage monitors that allow a mapping of (i) the initiating application identifier (e.g., app name, app fingerprint, application identification tag, application process number, application credential, or other secure or non-secure application or process identifier) to (ii) the request to the proxy service and subsequently to (iii) the network service flows between the proxy service and the network elements that service the information communications. Once this mapping is accomplished, the service usage flows of the proxy service can then be accounted back to the initiating application, device software process or other service activity, the proper policies can then be applied to each service usage flow for user notification, service activity launch control, service activity background accounting (including variable charge rating dependent on background service state and/or sponsored service charging), service activity background service controls or network usage restrictions as described herein (including but not limited to for example: block network access, restrict network access, throttle network access, delay network access, aggregate and hold network access, select for time of day network access restrictions, select network type restrictions, select roaming network access restrictions, select service usage restrictions such as a usage limit, select service cost restrictions such as a cost limit or otherwise place on another form of background service status or network usage restriction as described herein).
In some embodiments, this ability to track service usage for an service activity through a proxy service as described herein is used to improve usage reporting of service activities to a service controller for the purpose of statistically identifying service activities that are candidates for background service policy controls or network protections service policy controls.
In some embodiments, the various design techniques described herein that allow for monitoring, accounting for and/or implementing service policy for component service activities that belong to an aggregate service activity can be designed into the OS itself. For example, in certain current mobile OS implementations (e.g., Android, iPhone, Blackberry, etc) there are some applications available in the market that allow a user to get an estimate for how much data a certain subset of applications are consuming on a wireless service provider network, but it is not possible for the user or application to get an indication of the service usage for certain OS functions, whereas the embodiments disclosed herein will allow for this. As another example, in certain current mobile OS implementations it is not possible to associate proxy service usage (e.g., media download and media streaming proxy library software functions) with the specific applications that use the proxy service, so while the user can be informed of generic common OS functions or proxy services (e.g., in the case of Android: “media service,” “media,” “gallery,” “Google service framework” and other generic common OS software library functions or proxy services), there is no way for the user to determine what applications widgets or other service activities are actually generating this common service function usage, whereas the invention described herein permits the user full visibility on such usage monitoring examples. Furthermore, if the OS is retrofitted with the intercept and policy implementation functions can be designed into the activity manager, broadcast intent manger, media service manager, service manager, or other application or service activity management function in the Android OS. One or ordinary skill in the art will recognize that similarly, the various design techniques described herein that allow for intercepting a service activity intention to launch, and applying a background service policy set or a network protection service policy set can be designed into application launch management functions in the iPhone OS, Windows mobile OS, Windows PC OS, Blackberry OS, Palm OS, and other OS designs.
In some embodiments, the API is served or located on the device, on a network element (e.g., using a secure communication between the device and the network element for the API communication, such as HTTPS, TLS, SSL, an encrypted data connection or SS7 control channel, and/or other well known secure communication techniques), and/or both/partly in both. In some embodiments, a network based API is an API that facilitates an API or other interface communication (e.g., secure communication as discussed above) between an application executing on the device and a network element and/or service cloud for protecting network capacity. For example, a network API can provide an interface for an application to communicate with a service cloud (e.g., network server) for obtaining network access control information (e.g., network busy state, multiple network information based on available networks and/or network busy state information of available networks, network capacity controlled service priorities and availability, scheduled time/time slots for network access based on network busy state, service plan, network capacity controlled service, and/or other criteria/measures). As another example, a network API can facilitate an application provider, central network/service provider, and/or a third party with access to communicate with the application to provide and/or request information (e.g., physical location of the application, network location of the application, network service usage information for the application, network busy state information provided to the application, and/or other criteria/measures). As yet another example, a network API can facilitate a broadcast to one or more applications, OS functions, and/or devices (e.g., partitioned based on geography, network, application, OS function, and/or any other criteria/measure) with network capacity related information (e.g., network busy state, availability based on network capacity controlled service classification and/or priority level, scheduled time/time slots for certain network capacity controlled service classification and/or priority level, emergency/high priority software/antimalware/vulnerability update and scheduled time/time slots for such software updates, and/or other criteria/measures). In some embodiments, the network access API for protecting network capacity is an open API or standard/required API (e.g., required or standardized for applications for a certain network service provider, such as to be provided via the Verizon application store or the Apple AppStore) published for application and OS developers so that the applications and OS functions are designed to understand and implement the network access API for protecting network capacity. For example, a certification program can be established to provide application and OS developers with test specifications, working implementations, and/or criteria to make sure the network access API is properly implemented and is functioning in accordance with the specified requirements. In some embodiments, the network access API is an interface for communication with a service controller (e.g., service controller 122) or another network element/function (e.g., a service usage API for communication with a service usage server or billing interface/server or another network element/function that facilitates a secure communication for sending/receiving or otherwise communicating network access related information for protecting network capacity). In some embodiments, the network API provides for sponsored billing (e.g., reverse billing) of all, classified, and/or a subset of network service usage charges to a sponsored partner associated with the network service usage activity (e.g., application) that accesses the network API. In some embodiments, the network API provides for a sponsored service in which the network service usage activity (e.g., application) that accesses the network API provides a sponsored service partner credential to the network API, the credential is used as a billing mechanism to charge the sponsored partner, the user account is mediated to remove the sponsored partner charge, and the network API provides access service and/or information service (e.g., location information, local information, content information, network information, and/or any other information).
As shown in
Referring again to
In some embodiments, the service processor is secured using various hardware and software techniques described herein, including, for example, implementing all and/or portions of the service processor in a secure virtual machine, protected execution environment, secure storage (e.g., secure memory), secure modem, and/or other secure implementation techniques as described herein and/or other or similar techniques as will now be apparent to one of ordinary skill in the art in view of the various embodiments described herein. For example, the service processor can be implemented in software and executed in a protected area of an OS executed on the device and/or executed in protected execution partitions (e.g., in CPU, APU, SIM chipset, modem, modem secure execution partition, SIM, other hardware function on the device, and/or any combination of the above).
In some embodiments, a network service usage counter is embedded into a secure execution environment (e.g., a program store in secure non-volatile memory located on a modem card and/or a modem chip not accessible by device applications, secure CPU environment for executing program and/or secure program operation for data path monitoring and/or control that cannot be bypassed by device applications to get to the modem connection to the network) in a device modem (e.g., using measurement points V, VI, and/or other measurement points of
In some embodiments, the service usage counter reports the service usage to a network element (e.g., a service controller, charging gateway, PCRF, AAA, HA, billing system, mediation system, traffic accounting database, base station or base station controller, and/or another network element/function or central network element/function). In some embodiments, the information reported to the network element is encrypted or signed with a corresponding key known by the network element. In some embodiments, the communication link to the network element to pass the service usage count is conducted over a wireless network specific channel such as SMS, MMS, SS-7, or another specialized control channel. In some embodiments, the communications link to the network element to pass the service usage count is conducted over a network channel (e.g., via IP, TCP, UDP, HTTP, HTTPS, TLS, SSL, point to point signed variants of TLS or SSL, or another data network channel via the network control channel connection to the device). In some embodiments, the data network control channel traffic is injected into the PPP stream at the modem. In some embodiments, the data network control channel traffic is passed up to the device networking stack for connection to the network. In some embodiments, a signed or encrypted service usage count from the modem subsystem is coordinated to provide a service usage count for a time period that also corresponds to a similar time period for a service processor heartbeat report that includes a service usage measure or count. For example, this provides the service controller or another network element with a secondary set of information that can be used to verify and/or secure the service usage measures reported by the service processor. Various techniques can be used to synchronize the time period for the modem service usage count and the service processor service usage count. For example, the service processor can request a latest count message from the modem, in which the modem counts all service usage since the previous request for latest count until the present request for latest count, encrypts the latest count message so that the service processor or other application software or OS software on the device cannot decode and/or tamper with the message, and the modem service usage counter then passes the encrypted message to the service processor. The service processor can then pass the encrypted service usage count message from the modem to the service controller along with the service processor service usage accounting message(s) for the same or similar time period. The service controller can then decode both service count messages from the secure modem subsystem and the service processor and correlate the two measures to verify the service usage reporting by, for example, looking for discrepancies that would indicate service usage control or charging errors or device service processor tampering. In some embodiments, the secure modem subsystem records byte counts for streams (e.g., and/or flows, socket connections, or combinations of IP destination/source/ports), potentially along with time of day, network busy state, QoS level, and/or other criteria/measures, and reports these counts for each stream that had traffic activity during the current reporting interval. For example, the service controller can then correlate the stream service usage information with the service usage information provided by the service processor heartbeat service usage report to verify that the service processor service usage report is consistent with the independent measure made in the modem subsystem. In some embodiments, service usage reports (e.g., certified service usage reports) are correlated on the device and/or in the network (e.g., using one or more network elements/functions, such as the service controller).
In some embodiments, a deeper analysis of traffic can be conducted in the modem subsystem service usage count. For example, a layer 7 analysis of the service usage can be conducted for HTTP or HTTPS traffic flowing through the modem in which the modem subsystem service usage counter performs an HTTP level analysis of the traffic to associate web traffic gets and other transfers with a given higher level service classification (e.g., ad server, content server, proxy server, and/or traffic that is referred by the local host serving up a web page). In some embodiments, the modem subsystem service usage count can be augmented for HTTPS, SSL or TLS traffic by including a trusted proxy server embedded in the modem system. For example, the proxy server can be trusted by the device stack so that the encryption keys for HTTPS, TLS or SSL are known by the proxy server allowing the modem based proxy server, located, for example, in a secure execution environment, to perform layer 7 analysis of encrypted traffic in a manner similar to that described above. In some embodiments, the embedded proxy server generates server SSL certificates for each connection to a specific remote host in real time based on a root certificate trusted by the device (e.g., and/or by network service usage activity, such as by application) and also trusted by the embedded proxy server, and the proxy server then becomes a middle man emulating a remote SSL host on one side and emulating the device (e.g., and/or network service usage activity, such as application) on the other side, decrypting the traffic, analyzing it and re-encrypting before forwarding to and from the remote host. Similarly, as in the case of layer 3 and 4 traffic analysis performed by the modem service usage counting subsystem, the layer 7 service usage count messages can be encrypted and passed to the service controller via various channels. In some embodiments, the layer 7 modem subsystem service usage counting system records service usage counts for a reporting time period that is similar to the reporting time period used by the service processor so that the service controller can correlate the service processor accounting messages against the modem accounting messages with layer 7 information.
In some embodiments, the secure service usage reporting system elements are located in a secure execution environment that includes the modem driver. In some embodiments, all traffic that gets to the modem for the network traffic being controlled or accounted for is required to go through the secure modem driver so that an independent count can be generated and reported to the service controller as described above without the need to embed the secure service usage counting and reporting elements in the modem.
In some embodiments, the secure service usage reporting system elements are located in a secure execution environment that includes the modem driver and modem hardware interface controller driver (e.g., USB controller for 2/3/4G and SDIO controller for WiFi). In some embodiments, all traffic that gets to the modem for the network traffic being controlled or accounted for is required to go through the secure modem driver and modem hardware interface controller driver (e.g., USB controller for 2/3/4G and SDIO controller for WiFi) so that precise count can be generated by either the modem driver and/or modem hardware interface controller driver (e.g., USB controller for 2/3/4G and SDIO controller for WiFi) and passed to the secure service usage reporting element to send it to the service controller for customer charging/billing. This scheme provides flexibility (e.g., most of the device software and operation system and its services/applications need not be located/executed in the secure execution environment) while ensuring usage counting to occur securely as it pertains to the customer accounting and billing.
In some embodiments, the layer 7 proxy server traffic accounting and reporting techniques used for processing HTTPS, TLS, and SSL traffic, as discussed above, are also used in the service processor itself to allow a detailed accounting of encrypted layer 7 traffic by the device. In some embodiments, the information thus obtained is filtered so that private user information is not transmitted to the network (e.g., service controller, PCRF, and/or any other network element/function) but only service usage information sufficient to allow for accounting of service plan usage, to verify service control policy implementation, or to verify service charging policy implementation is transmitted to the network (e.g., service controller, PCRF, and/or any other network element/function). In some embodiments, the layer 7 proxy server for processing secure or in the clear device service usage accounting messages is located in secure hardware execution environments in the device application processor or within secure software partitions in the operating system.
Various techniques can be used to verify and/or secure service usage controls or service usage charging reports. For example, if the secondary service usage reports indicate that service usage is outside of the service usage policy limits that are intended to be in effect (e.g., based on a service plan and/or service policy associated with the device), then the service controller can indicate an error flag for further analysis and action (e.g., implementing various verification and responsive actions as described herein, such as blocking the activity, throttling the activity, quarantining the device, updating/replacing the service processor, and/or monitoring the device using various additional DAS and/or network assisted monitoring techniques). As another example, if the service usage reports from the service processor do not match up with the secondary service usage reports, then the service controller can indicate an error flag for further analysis and action. For example, the correlation can be based on bulk measures of service usage (e.g., total bytes over a given period of time), or using finer grain measures of service usage (e.g., verifying the accounting between one group of service usage activities, such as application, destination/source, port, content type, time of day, network busy state, QoS level, and/or other criteria/measures) charged to one service plan charging record versus the accounting for another group of service usage activities charged to another service plan charging record. In some embodiments, the correlation process between the two service usage accounting reports is performed continuously on all device traffic in real time or near real time as the usage accounting reports are received. In some embodiments, the usage accounting reports are stored and analyzed or correlated later (e.g., periodically, based on a request or audit, and/or based on certain events, such as threshold network service usage events and/or any other events based on various criteria/measures). In some embodiments, only an audit of a portion of time is used to correlate the two usage accounting reports, which, for example, can reduce network traffic and/or network processing load in the service controller.
In some embodiments, correlation techniques are applied by the service controller to compare two different service usage measures as described above based on one or more of the following: total amount of data (e.g., bytes for file transfers, sessions, and/or other measures), amount of data per unit time, total number of accesses, number of accesses per unit time or frequency of accesses, accesses during a time interval (e.g., peak time), accesses during a network busy state, access requests, and individual versus group transmissions at a point in time (e.g., each for a given set of destinations or destinations and traffic types).
In some embodiments, service usage monitoring includes characterizing service usage activities by streams, flows, destination/port, packet inspection, and/or other criteria/measures using the various techniques as described herein and/or other or similar techniques as would be apparent to one of ordinary skill in the art. In some embodiments, service usage monitoring includes characterizing service usage activities by streams, flows, destination/port, packet inspection, and/or other criteria/measures and then correlating to find network service usage behavior patterns that identify likely association of behavior with one or more service activities being managed.
In some embodiments, DAS for network capacity control includes classifying traffic to determine which network service usage activity(ies) are causing traffic (e.g., increasing network capacity/resources usage beyond a threshold), and then determining if access network service usage activity(ies) are violating any rules (e.g., service usage policies or service plan settings associated with the device/user). In some embodiments, DAS for network capacity control includes generating a list for network capacity controlled services that specifies behavioral characteristics for one or more network service usage activities with expected access limits based on access control policy for each managed network service usage activity (e.g., based on service usage policies or service plan settings associated with the device/user). In some embodiments, DAS for network capacity control includes monitoring and/or controlling network service usage activities based on limits, which, for example, can be based on one or more of the following: total access traffic counters, counters for different types of access traffic, destinations, ports, frequency of accesses, access behavior during a given time, access behavior during a given busy state, access behavior for groups of activities (e.g., verify clumping), and/or other criteria/measures.
Accordingly, in some embodiments, a second secure and trusted service usage measure is provided that the service controller (e.g., or another network element/function) can use to verify or secure the service control or service charging reports for the service processor. In some embodiments, the secure and trusted service usage measure also provides for enhanced verification and service security in cases, in which, for example, network based service usage measures are available for additional correlation with the service processor service usage reports. In cases in which network based service usage measures are either not available or are only available at widely spaced time intervals (e.g., roaming networks or other networks with no timely network based service usage measure), these techniques facilitate real time or near real time verification or security for the device assisted service controls and charging.
In some embodiments, a SIM card performs a portion or all of the secure environment processing described above, with the device modem traffic, or a copy of the device modem traffic, being directed to the SIM secure subsystem for traffic accounting and reporting. In some embodiments, a SIM card is used to store QoS classifications and/or network capacity controlled services classifications for various service usage activities so that the user behavior in using certain network service usage activities and/or the user preferences in controlling certain network service usage activities do not need to be relearned or redownloaded as the user swaps the SIM between different devices. In some embodiments, the SIM keeps a local record of service usage activity for multiple devices that belong to the user or the user family plan, so that the service usage notification and policies can be immediately updated on a given device as the user swaps the SIM from device to device. In some embodiments, the manner in which this service usage history is stored on the SIM is secure so that it cannot be tampered with. In some embodiments, the SIM card is used to implement various application management and/or traffic control techniques described herein. In some embodiments, the SIM card is used to inspect traffic, classify traffic, create reports (e.g., certified service activity usage reports), encrypt the report, send the report to a network element/function, and the network element/function correlates the reports (e.g., using network assisted measures for comparisons and/or using various other techniques as described herein). In some embodiments, a SIM card performs a portion or all of the secure environment processing described above using one or more modem measurement points. For example, the traffic that is to be classified can be routed through the SIM and correlated with what is measured by the modem. In some embodiments, network assisted/based network service usage activity classifications are compared SIM based/assisted classifications for service usage monitoring/reporting verification (e.g., detected inconsistencies in monitored/reported network service usage activities can be identified, such as based on total traffic, streams/flows/sockets activities, and/or other criteria/measures). In some embodiments, the reports include a verified sequence so that reports cannot be spoofed and/or missing reports can be determined.
In some embodiments, a portion or all of the secure environment processing described above are applied to implement and/or verify QoS for DAS techniques and/or DAS for network capacity controlled services techniques as described herein.
In some embodiments, the reports include one or more of the following: a number of times the device is cycled from or to a power cycle state in the modem, a number of times during a time window or network busy state, a power cycle versus number of streams initiated during the cycle, and a power cycle versus the streams that are transmitted during that cycle, In some embodiments, device power cycle events trigger generating of a report.
In some embodiments, monitoring, reporting, control, accounting, charging, and/or policy implementation for network capacity controlled services is verified (e.g., using various verification techniques described herein). If any of the verification techniques determine or assist in determining that the network capacity controlled services monitoring, reporting, control, accounting, and/or charging, and/or policy implementation has been tampered with, disabled, and/or is not properly implemented or functioning, then responsive actions can be performed, for example, the device (e.g., and/or suspect services) can be suspended, quarantined, killed/terminated, and/or flagged for further analysis/scrutiny to determine whether the device is malfunctioning, needs updating, has been tampered with or compromised, is infected with malware, and/or if any other problem exists.
In some embodiments, the service processor monitors a network service usage activity of a device. In some embodiments, monitoring of the service usage activity includes monitoring for multiple networks (e.g., to determine which networks are available and/or a network busy state of the available networks). In some embodiments monitoring a network service usage activity is performed by and/or assisted by a service cloud (e.g., one or more network elements that provide such a service). In some embodiments, monitoring the network service usage activity includes identifying the network service usage activity, measuring the network service usage of the network service usage activity, and/or characterizing the network service usage of the network service usage activity (e.g., using device assisted/based techniques, network assisted/based techniques, testing/offline monitoring/analysis techniques, and/or a combination thereof).
In some embodiments, the service processor implements differential network access service control (e.g., for network capacity controlled services), network service usage accounting, network service usage charging, and/or network service usage notification on the device to facilitate DAS for protecting network capacity.
In some embodiments, the service processor (e.g., a service processor 115) is updated, communicated with, set, and/or controlled by a network element (e.g., a service controller 122). In some embodiments, the service processor receives service policy information from a network function selected from a base station (e.g., a base station 125), a RAN gateway, a core gateway, a DPI gateway, a home agent (HA), a AAA server (e.g., AAA server 121), a service controller, and/or another network function or combinations of network functions as described herein and/or as will now be apparent to one of ordinary skill in the art in view of the various embodiments described herein. In some embodiments, the service processor is updated through over the air or over the network OS software updates or application software updates or device firmware updates. In some embodiments, the service processor uses an IP connection, SMS connection, and/or MMS connection, for a control channel with a service controller. In some embodiments, the service processor queries a service controller to determine the association of a monitored network service usage activity with a network service usage control policy. In some embodiments, the device (e.g., service processor) maintains a network capacity controlled services list and/or network capacity controlled services policy for one or more of the active services (e.g., actively executing and/or previously installed/downloaded to the device) that have been classified as a network capacity controlled service (e.g., as the number of applications continues to grow, as hundreds of thousands of applications are already available on certain platforms, maintaining a list specific and/or a set of policies unique or specific to each application is not efficient). In this embodiment, when a new application is active/launched and/or downloaded to the device, the device can request an updated network capacity controlled services list and/or an updated network capacity controlled services policy accordingly (e.g., and/or periodically refresh such lists/policies).
In some embodiments, differential network access control for protecting network capacity includes controlling network services traffic generated by the device (e.g., network capacity controlled services based on a network service usage control policy (e.g., a network capacity controlled services policy). In some embodiments, differential network access control for protecting network capacity includes providing assistance in control of the distribution of bandwidth among devices, network capacity controlled services (e.g., applications, OS operations/functions, and various other network services usage activities classified as network capacity controlled services), a differentiated QoS service offering, a fair sharing of capacity, a high user load network performance, and/or preventing one or more devices from consuming so much network capacity that other devices cannot receive adequate performance or performance in accordance with various threshold and/or guaranteed service levels. In some embodiments, differential network access control for protecting network capacity includes applying policies to determine which network the service activity should be connected to (e.g., 2G, 3G, 4G, home or roaming, WiFi, cable, DSL, fiber, wired WAN, and/or another wired or wireless or access network), and applying differential network access control rules (e.g., traffic control rules) depending on which network to which the service activity is connected. In some embodiments, differential network access control for protecting network capacity includes differentially controlling network service usage activities based on the service usage control policy and a user input (e.g., a user selection or user preference). In some embodiments, differential network access control for protecting network capacity includes differentially controlling network service usage activities based on the service usage control policy and the network the device or network service activity is gaining access from.
In some embodiments, the network service usage control policy is dynamic based on one or more of the following: a network busy state, a time of day, which network the service activity is connected to, which base station or communication channel the service activity is connected to, a user input, a user preference selection, an associated service plan, a service plan change, an application behavior, a messaging layer behavior, random back off, a power state of device, a device usage state, a time based criteria (e.g., time/day/week/month, hold/delay/defer for future time slot, hold/delay/defer for scheduled time slot, and/or hold/delay/defer until a busy state/availability state/QoS state is achieved), monitoring of user interaction with the service activity, monitoring of user interaction with the device, the state of UI priority for the service activity, monitoring the power consumption behavior of the service activity, modem power cycling or power control state changes, modem communication session set up or tear down, and/or a policy update/modification/change from the network. In some embodiments, the network service usage control policy is based on updated service usage behavior analysis of the network service usage activity. In some embodiments, the network service usage control policy is based on updated activity behavior response to a network capacity controlled service classification. In some embodiments, the network service usage control policy is based on updated user input/preferences (e.g., related to policies/controls for network capacity controlled services). In some embodiments, the network service usage control policy is based on updates to service plan status. In some embodiments, the network service usage control policy is based on updates to service plan policies. In some embodiments, the network service usage control policy is based on availability of alternative networks. In some embodiments, the network service usage control policy is based on policy rules for selecting alternative networks. In some embodiments, the network service usage control policy is based on network busy state or availability state for alternative networks. In some embodiments, the network service usage control policy is based on specific network selection or preference policies for a given network service activity or set of network service activities.
In some embodiments, associating the network service usage activity with a network service usage control policy or a network service usage notification policy, includes dynamically associating based on one or more of the following: a network busy state, a time of day, a user input/preference, an associated service plan (e.g., 25 MB data plan, 5G data plan, or an unlimited data plan or other data/service usage plan), an application behavior, a messaging layer behavior, a power state of device, a device usage state, a time based criteria, availability of alternative networks, and a set of policy rules for selecting and/or controlling traffic on one or more of the alternative networks.
In some embodiments, a network service usage control policy (e.g., a network capacity controlled services policy) includes defining the network service usage control policy for one or more service plans, defining network access policy rules for one or more devices or groups of devices in a single or multi-user scenarios such as family and enterprise plans, defining network access policy rules for one or more users or groups of users, allowing or disallowing network access events or attempts, modulating the number of network access events or attempts, aggregating network access events or attempts into a group of access events or attempts, time windowing network access events or attempts, time windowing network access events or attempts based on the application or function being served by the network access events or attempts, time windowing network access events or attempts to pre-determined time windows, time windowing network access events or attempts to time windows where a measure of network busy state is within a range, assigning the allowable types of access events or attempts, assigning the allowable functions or applications that are allowed network access events or attempts, assigning the priority of one or more network access events or attempts, defining the allowable duration of network access events or attempts, defining the allowable speed of network access events or attempts, defining the allowable network destinations for network access events or attempts, defining the allowable applications for network access events or attempts, defining the QoS rules for one or more network access events or attempts, defining or setting access policy rules for one or more applications, defining or setting access policy rules for one or more network destinations, defining or setting access policy rules for one or more devices, defining or setting access policy rules for one or more network services, defining or setting access policy rules for one or more traffic types, defining or setting access policy rules for one or more QoS classes, and defining or setting access policy rules based on any combination of device, application, network destination, network service, traffic type, QoS class, and/or other criteria/measures.
In some embodiments, a network service usage control policy (e.g., a network capacity controlled services policy) includes a traffic control policy. In some embodiments, the traffic control policy includes a traffic control setting. In some embodiments, the traffic control policy includes a traffic control/tier, and the traffic control/tier includes the traffic control setting. In some embodiments, the traffic control policy includes one or more of the following: block/allow settings, throttle settings, adaptive throttle settings, QoS class settings including packet error rate, jitter and delay settings, queue settings, and tag settings (e.g., for packet tagging certain traffic flows). In some embodiments, QoS class settings include one or more of the following: throttle level, priority queuing relative to other device traffic, time window parameters, and hold or delay while accumulating or aggregating traffic into a larger stream/burst/packet/group of packets. In some embodiments, the traffic control policy includes filters implemented as indexes into different lists of policy settings (e.g., using cascade filtering techniques), in which the policy filters include one or more of the following: a network, a service plan, an application, a time of day, and a network busy state. For example, a two dimensional traffic control implementation scheme can be provided using a network busy state and/or a time of day as an index into a traffic control setting (e.g., a certain application's priority level can be increased or decreased based on a network busy state and/or time of day). In some embodiments, the traffic control policy is used for selecting the network from a list of available networks, blocking or reducing access until a connection is made to an alternative network, and/or modifying or replacing a network stack interface of the device to provide for intercept or discontinuance of network socket interface messages to applications or OS functions.
In some embodiments, a traffic control setting is selected based on the network service usage control policy. In some embodiments, the traffic control setting is implemented on the device based on the network service usage control policy. In some embodiments, the implemented traffic control setting controls traffic/traffic flows of a network capacity controlled service. In some embodiments, the traffic control setting is selected based on one or more of the following: a time of day, a day of week, a special time/date (e.g., a holiday or a network maintenance time/date), a network busy state, a priority level associated with the network service usage activity, a QoS class associated with the network service usage activity (e.g., emergency traffic), which network the network service activity is gaining access from, which networks are available, which network the network service activity is connected to, which base station or communication channel the network service activity is connected to, and a network dependent set of traffic control policies that can vary depending on which network the service activity is gaining access from (e.g., and/or various other criteria/measures as described herein). In some embodiments, the traffic control setting includes one or more of the following: allow/block, delay, throttle, QoS class implementation, queue, tag, generate a user notification, random back off, clear to send received from a network element, hold for scheduled transmission time slot, selecting the network from the available networks, and blocking or reducing access until a connection is made to an alternative network. In some embodiments, the traffic control setting is selected based on a network capacity controlled services priority state of the network service usage activity and a network busy state. In some embodiments, the traffic control setting is selected based on a network capacity controlled services priority state of the network service usage activity and a network busy state and is global (e.g., the same) for all network capacity controlled services activities or varies based on a network service usage activity priority, user preferences or option selection, an application, a time based criteria, a service plan, a network the device or service activity is gaining access from, a redetermination of a network congestion state after adapting to a previously determined network busy state, and/or other criteria/measures as described herein.
In some embodiments, network capacity controlled services traffic (e.g., traffic flows) is differentially controlled for protecting network capacity. For example, various software updates for an OS and one or more applications on the device can be differentially controlled using the various techniques described herein. As another example, security/antimalware software (e.g., antivirus, firewall, content protection, intrusion detection/prevention, and/or other security/antimalware software) can be differentially controlled using the various techniques described herein. As yet another example, network backups/imaging, content downloads (e.g., exceeding a threshold individually and/or in aggregate, such as for image, music, video, eBook content, email attachments, content/media subscriptions, RSS/news feeds, text/image/video chat, software updates, and/or other content downloads) can be differentially controlled using the various techniques described herein.
For example, using the DAS for protecting network capacity techniques described herein an adaptive policy control for protecting network capacity can be provided. A network capacity controlled services list can be generated, updated, reported, and/or received by the device and stored on the device (e.g., the list can be based on adapted to the service plan associated with the device). If a monitored network service usage activity is not on the list, then the device can report the monitored network service usage activity to a network element (e.g., for a monitored network service usage activity that also exceeds a certain threshold, based on a network busy state, based on a time based criteria, and/or other criteria/measure). As an example, monitored network service usage activity can be reported if/when the monitored network service usage activity exceeds a data usage threshold (e.g., 50 MB total data usage per day, a socket opening frequency/rate, velocity of data usage at an instant in time, or more complicated thresholds over time, over peak periods, by content and time, by various other parameters/thresholds). As another example, the monitored network service usage activity can be reported based on testing of the network service usage behavior and/or application developer characterization input. The report can include information that identifies the network service usage activity and various network service usage parameters.
In some embodiments, a notification setting is selected based on a service usage notification policy. In some embodiments, a notification setting includes a user notification setting (e.g., various user notifications settings as described above with respect to
In some embodiments, classifying the network service usage activity further includes classifying the network service usage activity (e.g., using a usage threshold filter and/or cascading filter techniques) into one or more of a plurality of classification categories for differential network access control for protecting network capacity. In some embodiments, classifying the network service usage activity further includes classifying the network service usage activity into one or more network capacity controlled services in which the network capacity controlled services include one or more of the following: applications requiring data network access, application software updates, applications requiring network information, applications requiring GPS or physical location, operating system software updates, security software updates, network based backups, email downloads, and a set of activities configured as network capacity controlled service activities based on a service profile and/or user input (e.g., and/or various other types of network service usage activities as described herein and as will now be apparent to one of ordinary skill in the art). For example, network capacity controlled services can include software updates for OS and applications, OS background network accesses, cloud synchronization services, RSS feeds and other background information feeds, browser/application/device behavior reporting, background email downloads, content subscription service updates and downloads (e.g., music/video downloads, news feeds), text/voice/video chat clients, security updates (e.g., antimalware updates), peer to peer networking application updates, inefficient network access sequences during frequent power cycling or power save state cycling, large downloads or other high bandwidth accesses, and greedy application programs that constantly/repeatedly access the network with small transmissions or requests for information. In some embodiments, a network capacity controlled services list is static, adaptive, generated using a service processor, received from a network element (e.g., service controller or service cloud), received from a network element (e.g., service controller or service cloud) and based at least in part on device activity reports received from the service processor, based on criteria set by pre-testing, report of behavior characterization performed by the application developer, and/or based at least in part on user input. In some embodiments, the network capacity controlled services list includes one or more network service activity background (QoS) classes.
In some embodiments, classifying the network service usage activity further includes classifying the network service usage activity based on one or more of the following: application or widget (e.g., Outlook, Skype, iTunes, Android email, weather channel weather widget, iCal, Firefox Browser, etc), application type (e.g., user application, system application/utility/function/process, OS application/utility/function/process, email, browser, widget, malware (such as a virus or suspicious process), RSS feed, device synchronization service, download application, network backup/imaging application, voice/video chat, peer to peer content application or other peer to peer application, streaming media feed or broadcast reception/transmission application, network meeting application, chat application or session, and/or any other application or process identification and categorization), OS/system function (e.g., any system application/utility/function/process and/or OS application/utility/function/process, such as a OS update and/or OS error reporting), modem function, network communication function (e.g., network discovery or signaling, EtherType messages, connection flow/stream/session set up or tear down, network authentication or authorization sequences, IP address acquisition, and DNS services), URL and/or domain, destination/source IP address, protocol, traffic type, socket (e.g., IP address, protocol, and/or port), socket address/label/identifier (e.g., port address/port number), content type (e.g., email downloads, email text, video, music, eBooks, widget update streams, and download streams), port (e.g., port number), QoS classification level, time of day, on peak or off peak, network time, network busy state, access network selected, service plan selected, user preferences, device credentials, user credentials, and/or status, modem power cycling or power state changes, modem authentication processes, modem link set up or tear down, modem management communications, modem software or firmware updates, modem power management information, device power state, and modem power state. In some embodiments, classifying the network service usage activity further includes associating the classified network service usage activity with an ID (e.g., an application ID, which can be, for example, a unique number, name, and/or signature). In some embodiments, classifying the network service usage activity further includes classifying the network service usage activity using a plurality of classification parameters, including one or more of the following: application ID, remote IP (e.g., URL, domain, and/or IP address), remote port, protocol, content type, a filter action class (e.g., network busy state class, QoS class, time of day, network busy state, and/or other criteria/measures), and access network selected. In some embodiments, classifying the network service usage activity further includes using a combination of parameters as discussed above to determine the classification of the network service usage activity.
In some embodiments, classifying the network service usage activity further includes classifying the network service usage activity as a network capacity controlled service, a non-network capacity controlled service, a blocked or disallowed service, and/or a not yet classified/identified service (e.g., unknown/yet to be determined classification or pending classification). In some embodiments, an application connection, OS connection, and/or other service activity is classified as a network capacity controlled service activity when the device has been inactive (e.g., or in a power save state) for a period of time (e.g., when the user has not interacted with it for a period of time, when it has not displayed user notification policy, and/or a user input has not been received for a period of time, and/or when a power save state is entered). In some embodiments, an application connection, OS connection, and/or other service activity is classified as a network capacity controlled service activity when the monitored network service usage activity exceeds a data usage threshold for more than one application connection, OS connection, and/or other service activity (e.g., aggregated data usage exceeds the data usage threshold); or for a specific application connection. In some embodiments, an application connection, OS connection, and/or other service activity is classified as a network capacity controlled service activity when the monitored network service usage activity exceeds a data usage threshold based on a predetermined list of one or more data usage limits, based on a list received from a network element, usage time limit (e.g., based on a period of time exceeding a usage limit), and/or based on some other usage related criteria/measures. In some embodiments, classifying the network service usage activity further includes classifying the network service usage activity as a network capacity controlled service based on a network peak time, a network busy state, or a network connection to the device falls below a certain performance level (e.g., higher/lower priorities assigned based on various such criteria/other input/factors).
In some embodiments, one or more of the network capacity controlled services are associated with a different network access policy set for one or more networks and/or one or more alternative networks. In some embodiments, one or more of the network capacity controlled services are associated with a different notification policy set for one or more networks and/or one or more alternative networks. In some embodiments, the network capacity controlled services list is stored on the device. In some embodiments, the network capacity controlled services list is received/periodically updated from a network element and stored on the device. In some embodiments, the network capacity controlled services list includes network capacity controlled services, non-network capacity controlled services (e.g., foreground services or services based on various possibly dynamic criteria are not classified as network capacity controlled services), and an unclassified set of services (e.g., grey list including one or more network service activities pending classification based on further analysis and/or input, such as from a network element, service provider, and/or user). In some embodiments, the network capacity controlled services list is based on one or more of the following: predefined/predesignated (e.g., network, service plan, pre-test and/or characterized by an application developer) criteria; device assisted/based monitoring (e.g., using a service processor); network based monitoring (e.g., using a DPI gateway); network assisted analysis (e.g., based on device reports of DAS activity analysis). For example, the device can report device monitored network service usage activities (e.g., all monitored network service usage activities or a subset based on configuration, threshold, service plan, network, and/or user input) to the network element. As another example, the network element can update the network capacity controlled services list and send the updated list to the device. As yet another example, the network element can perform a statistical analysis of network service activities across a plurality of devices based on the device based and/or network based network service usage activity monitoring/reporting. In some embodiments, a network service usage activity is determined to be an active application or process (e.g., based on a user interaction with the device and/or network service usage activity, such as a pop-up and/or other criteria/measures).
In some embodiments, implementing traffic control for network capacity controlled services is provided using various techniques. In some embodiments, the device includes a service processor agent or function to intercept, block, modify, remove or replace UI messages, notifications or other UI communications generated by a network service activity that whose network service usage is being controlled or managed (e.g., using various measurement points as shown in and described with respect to
In some embodiments, implementing traffic control for network capacity controlled services using DAS techniques is provided using various techniques in which the network service usage activity is unaware of network capacity control (e.g., does not support an API or other interface for implementing network capacity control). For example, network service application messaging interface based techniques can be used to implement traffic control. Example network service application messaging interfaces include the following: network stack API, network communication stream/flow interface, network stack API messages, EtherType messages, ARP messages, and/or other messaging or other or similar techniques as will now be apparent to one of ordinary skill in the art in view of the various embodiments described herein. In some embodiments, network service usage activity control policies or network service activity messages are selected based on the set of traffic control policies or service activity messages that result in reduced or modified user notification by the service activity due to network capacity controlled service policies applied to the network service activity. In some embodiments, network service usage activity control policies or network service activity messages are selected based on the set of traffic control policies or service activity messages that result in reduced disruption of device operation due to network capacity controlled service activity policies applied to the network service activity. In some embodiments, network service usage activity control policies or network service activity messages are selected based on the set of traffic control policies or service activity messages that result in reduced disruption of network service activity operation due to network capacity controlled service activity policies applied to the network service activity. In some embodiments, implementing traffic control for network capacity controlled services is provided by intercepting opens/connects/writes. In some embodiments, implementing traffic control for network capacity controlled services is provided by intercepting stack API level or application messaging layer requests (e.g., socket open/send requests). For example, an intercepted request can be copied (e.g., to memory) and queued (e.g., delayed or throttled) or dropped (e.g., blocked). As another example, an intercepted request can be copied into memory and then a portion of the transmission can be retrieved from memory and reinjected (e.g., throttled). As yet another example, intercepting messaging transmissions can be parsed inline and allowed to transmit (e.g., allowed), and the transmission or a portion of the transmission can be copied to memory for classifying the traffic flow. In some embodiments, implementing traffic control for network capacity controlled services is provided by intercepting or controlling or modulating UI notifications. In some embodiments, implementing traffic control for network capacity controlled services is provided by killing or suspending the network service activity. In some embodiments, implementing traffic control for network capacity controlled services is provided by deprioritizing the process(es) associated with the service activity (e.g., CPU scheduling deprioritization).
In some embodiments, implementing traffic control for network capacity controlled services using DAS techniques for network service usage activities that are unaware of network capacity control is provided by emulating network API messaging (e.g., effectively providing a spoofed or emulated network API). For example, an emulated network API can intercept, modify, block, remove, and/or replace network socket application interface messages and/or EtherType messages (e.g., EWOULDBLOCK, ENETDOWN, ENETUNREACH, EHOSTDOWN, EHOSTUNREACH, EALRADY, EINPROGRESS, ECONNREFUSED, EINPROGRESS, ETIMEDOUT, and/other such messages). As another example, an emulated network API can modify, swap, and/or inject network socket application interface messages (socket( ) connect( ) read( ) write( ), close( ) and other such messages) that provide for control or management of network service activity service usage behavior. As yet another example, before a connection is allowed to be opened (e.g., before a socket is opened), transmission, or a flow/stream is initiated, it is blocked and a message is sent back to the application (e.g., a reset message in response to a sync request or another message that the application will understand and can interpret to indicate that the network access attempt was not allowed/blocked, that the network is not available, and/or to try again later for the requested network access). As yet another example, the socket can be allowed to open but after some point in time (e.g., based on network service usage, network busy state, time based criteria, and/or some other criteria/measure), the stream is blocked or the socket is terminated. As yet another example, time window based traffic control techniques can be implemented (e.g., during non-peak, not network busy state times), such as by allowing network access for a period of time, blocking for a period of time, and then repeating to thereby effectively spread the network access out either randomly or deterministically. Using these techniques, an application that is unaware of network capacity control based traffic control can send and receive standard messaging, and the device can implement traffic controls based on the network capacity control policy using messaging that the network service usage activity (e.g., application or OS or software function) can understand and will respond to in a typically predictable manner as would now be apparent to one of ordinary skill in the art.
In some embodiments, implementing traffic control for network capacity controlled services using DAS techniques is provided using various techniques in which the network service usage activity is aware of network capacity control (e.g., the network service usage activity supports an API or other interface for implementing network capacity control). For example, a network access API as described herein can be used to implement traffic control for network capacity controlled services. In some embodiments, the API facilitates communication of one or more of the following: network access conditions, network busy state or network availability state of one or more networks or alternative networks, one or more network capacity controlled service policies (e.g., the network service can be of a current network access setting, such as allow/block, throttle, queue, scheduled time/time slot, and/or defer, which can be based on, for example, a current network, a current network busy state, a time based criteria, a service plan, a network service classification, and/or other criteria/measures), a network access request from a network service activity, a query/polled request to a network service activity, a network access grant to a network service activity (e.g., including a priority setting and/or network capacity controlled service classification, a scheduled time/time slot, an alternative network, and/or other criteria/measures), a network busy state or a network availability state or a network QoS state.
In some embodiments, implementing traffic control for network capacity controlled services using network assisted/based techniques is provided using various techniques in which the network service usage activity is unaware of network capacity control (e.g., does not support an API or other interface for implementing network capacity control). In some embodiments, DPI based techniques are used to control network capacity controlled services (e.g., to block or throttle network capacity controlled services at a DPI gateway).
In some embodiments, implementing traffic control for network capacity controlled services using network assisted/based techniques is provided using various techniques in which the network service usage activity is aware of network capacity control (e.g., does support an API or other interface for implementing network capacity control). In some embodiments, the application/messaging layer (e.g., a network API as described herein) is used to communicate with a network service activity to provide associated network capacity controlled service classifications and/or priorities, network busy state information or network availability of one or more networks or alternative networks, a network access request and response, and/other criteria/measures as similarly described herein.
In some embodiments, DAS for protecting network capacity includes implementing a service plan for differential charging based on network service usage activities (e.g., including network capacity controlled services). In some embodiments, the service plan includes differential charging for network capacity controlled services. In some embodiments, the service plan includes a cap network service usage for network capacity controlled services. In some embodiments, the service plan includes a notification when the cap is exceeded. In some embodiments, the service plan includes overage charges when the cap is exceeded. In some embodiments, the service plan includes modifying charging based on user input (e.g., user override selection as described herein, in which for example, overage charges are different for network capacity controlled services and/or based on priority levels and/or based on the current access network). In some embodiments, the service plan includes time based criteria restrictions for network capacity controlled services (e.g., time of day restrictions with or without override options). In some embodiments, the service plan includes network busy state based criteria restrictions for network capacity controlled services (e.g., with or without override options). In some embodiments, the service plan provides for network service activity controls to be overridden (e.g., one time, time window, usage amount, or permanent) (e.g., differentially charge for override, differentially cap for override, override with action based UI notification option, and/or override with UI setting). In some embodiments, the service plan includes family plan or multi-user plan (e.g., different network capacity controlled service settings for different users). In some embodiments, the service plan includes multi-device plan (e.g., different network capacity controlled service settings for different devices, such as smart phone v. laptop v. net book v. eBook). In some embodiments, the service plan includes free network capacity controlled service usage for certain times of day, network busy state(s), and/or other criteria/measures. In some embodiments, the service plan includes network dependent charging for network capacity controlled services. In some embodiments, the service plan includes network preference/prioritization for network capacity controlled services. In some embodiments, the service plan includes arbitration billing to bill a carrier partner or sponsored service partner for the access provided to a destination, application, or other network capacity controlled service. In some embodiments, the service plan includes arbitration billing to bill an application developer for the access provided to a destination, application or other network capacity controlled service.
In some application scenarios, excess network capacity demand can be caused by modem power state changes on the device. For example, when an application or OS function attempts to connect to the network for any reason when the modem is in a power save state wherein the modem is not connected to the network, it can cause the modem to change power save state, reconnect to the network, and then initiate the application network connection. In some cases, this can also cause the network to re-initiate a modem connection session (e.g., PPP session) which in addition to the network capacity consumed by the basic modem connection also consumes network resources for establishing the PPP session. Accordingly, in some embodiments, network service usage activity control policies are implemented that limit or control the ability of applications, OS functions, and/or other network service usage activities (e.g., network capacity controlled services) from changing the modem power control state or network connection state. In some embodiments, a service usage activity is prevented or limited from awakening the modem, changing the power state of the modem, or causing the modem to connect to the network until a given time window is reached. In some embodiments, the frequency a service usage activity is allowed to awakening the modem, changing the power state of the modem, or causing the modem is limited. In some embodiments, a network service usage activity is prevented from awakening the modem, changing the power state of the modem, or causing the modem until a time delay has passed. In some embodiments, a network service usage activity is prevented from awakening the modem, changing the power state of the modem, or causing the modem until multiple network service usage activities require such changes in modem state, or until network service usage activity is aggregated to increase network capacity and/or network resource utilization efficiency. In some embodiments, limiting the ability of a network service usage activity to change the power state of a modem includes not allowing the activity to power the modem off, place the modem in sleep mode, or disconnect the modem from the network. In some embodiments, these limitations on network service usage activity to awaken the modem, change the power state of the modem, or cause the modem to connect to a network are set by a central network function (e.g., a service controller or other network element/function) policy communication to the modem. In some embodiments, these power control state policies are updated by the central network function.
The wireless devices 2402 will at a minimum include a processor, memory (though the memory could be implemented in the processor), a radio, and a radio interface (though the radio interface could be implemented as “part of” the radio). In order to make the wireless devices 2402 useful, they will typically have at least one input device and at least one output device, including input and output interfaces, if applicable.
The wireless devices 2402 can be implemented as stations. A station, as used herein, may be referred to as a device with a media access control (MAC) address and a physical layer (PHY) interface to the wireless medium that comply with, e.g., the IEEE 802.11 standard. A station can be described as “IEEE 802.11-compliant” when compliance with the IEEE 802.11 standard is intended to be explicit. (I.e, a device acts as described in at least a portion of the IEEE 802.11 standard.) One of ordinary skill in the relevant art would understand what the IEEE 802.11 standard comprises today and that the IEEE 802.11 standard can change over time, and would be expected to apply techniques described in this paper in compliance with future versions of the IEEE 802.11 standard if an applicable change is made. IEEE Std 802.11™-2007 (Revision of IEEE Std 802.11-1999) is incorporated by reference. IEEE 802.11k-2008, IEEE 802.11n-2009, IEEE 802.11p-2010, IEEE 802.11r-2008, IEEE 802.11w-2009, and IEEE 802.11y-2008 are also incorporated by reference.
In alternative embodiments, one or more of the wireless devices 2402 may comply with some other standard or no standard at all, and may have different interfaces to a wireless or other medium. It should be noted that not all standards refer to wireless devices as “stations,” but where the term is used in this paper, it should be understood that an analogous unit will be present on all applicable wireless networks. Thus, use of the term “station” should not be construed as limiting the scope of an embodiment that describes wireless devices as stations to a standard that explicitly uses the term, unless such a limitation is appropriate in the context of the discussion.
The wireless networks 2404 will typically include an internetworking unit (IWU) that interconnects wireless devices on the relevant one of the wireless networks 2404 with another network, such as a wired LAN. The IWU is sometimes referred to as a wireless access point (WAP). In the IEEE 802.11 standard, a WAP is also defined as a station. Thus, a station can be a non-WAP station or a WAP station. In a cellular network, the WAP is often referred to as a base station.
The wireless networks 2404 can be implemented using any applicable technology, which can differ by network type or in other ways. The wireless networks 2404 can be of any appropriate size (e.g., metropolitan area network (MAN), personal area network (PAN), etc.). Broadband wireless MANs may or may not be compliant with IEEE 802.16, which is incorporated by reference. Wireless PANs may or may not be compliant with IEEE 802.15, which is incorporated by reference. The wireless networks 2404 can be identifiable by network type (e.g., 2G, 3G, WiFi), service provider, WAP/base station identifier (e.g., WiFi SSID, base station and sector ID), geographic location, or other identification criteria.
The wireless networks 2404 may or may not be coupled together via an intermediate network. The intermediate network can include practically any type of communications network, such as, by way of example but not limitation, the Internet, a public switched telephone network (PSTN), or an infrastructure network (e.g., private LAN). The term “Internet” as used herein refers to a network of networks which uses certain protocols, such as the TCP/IP protocol, and possibly other protocols such as the hypertext transfer protocol (HTTP) for hypertext markup language (HTML) documents that make up the World Wide Web (the web).
In the example of
As used in this paper, an engine includes a dedicated or shared processor and, typically, firmware or software modules that are executed by the processor. Depending upon implementation-specific or other considerations, an engine can be centralized or its functionality distributed. An engine can include special purpose hardware, firmware, or software embodied in a computer-readable medium for execution by the processor. As used in this paper, a computer-readable 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 medium to be valid. Known statutory computer-readable mediums include hardware (e.g., registers, random access memory (RAM), non-volatile (NV) storage, to name a few), but may or may not be limited to hardware.
The network traffic analysis engine 2406 analyzes a subset of traffic between the wireless device 2402-1 and a source or destination. The analyzed traffic may or may not be limited to a network segment, such as between a cellular phone and a base station. The network traffic analysis engine 2406 can analyze traffic for a subset of devices in the wireless network 2404-1 service area. The analyzed traffic may or may not be limited to subscribers.
In the example of
The network service usage classification engine 2408 can categorize traffic based upon the service class (e.g., conversational, streaming, interactive, background, or some other service class) requested or needed for a service. The categorization facilitates identification of a snapshot of service class use at a given time, and, in some implementations, predictions of future service class use based upon the snapshot (e.g., making an assumption that future service class use is at least somewhat related to service class use of the snapshot), historical data analysis (e.g., service class usage at certain times of day/days of the week), identification of trends, or the use of some other predictive technology.
In the example of
The differential network access control engine 2410 uses the predicted service class use from the network service usage classification engine 2408 to dynamically adjust resources allocated to service classes. For example, the differential network access control engine 2410 can perform a service class availability assessment to determine whether service class capacity for service classes on a channel is sufficient for predicted service usage, and either add resources if service class availability is insufficient for predicted service usage or reduce resources if service class availability is more than sufficient for predicted service usage.
Alternatively, the differential network access control engine 2410 can instead or in addition control applications on devices such that the applications change service usage levels or delay consumption of wireless resources (e.g., by delaying software updates until more resources become available). In an embodiment, a service usage control policy is implemented on the wireless device 2402-1. This may be necessary in some cases to ensure the wireless device 2402-1 can adjust application settings that are normally fixed, optimize network service usage activation based on network state (e.g., if the network is busy), control over-the-air software updates, throttle resource-hungry applications, manage network service usage requests from repeated power down modes, keep PPP sessions active, or otherwise facilitate dynamic service class adjustments or other device behavior.
In a specific implementation, subscribers can be incented to change service classes by, for example, charging more for higher service classes. The differential network access control engine 2410 can send a notification of differential charges for service classes. Alternatively, the charges could be implemented via subscriber account settings or preferences.
In the example of
In the example of
In the example of
In the example of
A datastore can be implemented, for example, as software embodied in a physical computer-readable medium on a general- or specific-purpose machine, in firmware, in hardware, in a combination thereof, or in an applicable known or convenient device or system. Datastores in this paper are intended to include any organization of data, including tables, comma-separated values (CSV) files, traditional databases (e.g., SQL), or other applicable known or convenient organizational formats. Datastore-associated components, such as database interfaces, can be considered “part of” a datastore, part of some other system component, or a combination thereof, though the physical location and other characteristics of datastore-associated components is not critical for an understanding of the techniques described in this paper.
Datastores can include data structures. As used in this paper, a data structure is associated with a particular way of storing and organizing data in a computer so that it can be used efficiently within a given context. Data structures are generally based on the ability of a computer to fetch and store data at any place in its memory, specified by an address, a bit string that can be itself stored in memory and manipulated by the program. Thus some data structures are based on computing the addresses of data items with arithmetic operations; while other data structures are based on storing addresses of data items within the structure itself. Many data structures use both principles, sometimes combined in non-trivial ways. The implementation of a data structure usually entails writing a set of procedures that create and manipulate instances of that structure.
In the example of
The notification may or may not also include a user preference selection. For example, the notification could include a provision to associate a network service usage control policy with the network service usage activity, an over-ride option for selecting the network service usage control policy, a modify option to select the service usage control policy, and a select option to select a new service plan, to name several by way of example. Other examples include network service usage activity information for one or more network capacity controlled services, predicted network service usage activity information for one or more network capacity controlled services, an option for obtaining more information about the network service usage of the network service usage activity, a message that the network service usage activity may result in network service usage that exceeds a threshold for a service plan associated with the device, an option to review or select an alternative service plan, an acknowledgement request, and an option to submit the acknowledgement request, to name several more by way of example.
In the example of
In the example of
The computer 2602 interfaces to external systems through the communications interface 2610, which may include a modem or network interface. It will be appreciated that the communications interface 2610 can be considered to be part of the computer system 2600 or a part of the computer 2602. The communications interface 2610 can be an analog modem, ISDN modem, cable modem, token ring interface, satellite transmission interface (e.g., “direct PC”), or other interfaces for coupling a computer system to other computer systems.
The processor 2608 may be, for example, a conventional microprocessor such as an Intel Pentium microprocessor or Motorola power PC microprocessor. The memory 2612 is coupled to the processor 2608 by a bus 2670. The memory 2612 can be Dynamic Random Access Memory (DRAM) and can also include Static RAM (SRAM). The bus 2670 couples the processor 2608 to the memory 2612, also to the non-volatile storage 2616, to the display controller 2614, and to the I/O controller 2618.
The I/O devices 2604 can include a keyboard, disk drives, printers, a scanner, and other input and output devices, including a mouse or other pointing device. The display controller 2614 may control in the conventional manner a display on the display device 2606, which can be, for example, a cathode ray tube (CRT) or liquid crystal display (LCD). The display controller 2614 and the I/O controller 2618 can be implemented with conventional well known technology.
The non-volatile storage 2616 is often a magnetic hard disk, an optical disk, or another form of storage for large amounts of data. Some of this data is often written, by a direct memory access process, into memory 2612 during execution of software in the computer 2602. One of skill in the art will immediately recognize that the terms “machine-readable medium” or “computer-readable medium” includes any type of storage device that is accessible by the processor 2608 and also encompasses a carrier wave that encodes a data signal.
The computer system 2600 is one example of many possible computer systems which have different architectures. For example, personal computers based on an Intel microprocessor often have multiple buses, one of which can be an I/O bus for the peripherals and one that directly connects the processor 2608 and the memory 2612 (often referred to as a memory bus). The buses are connected together through bridge components that perform any necessary translation due to differing bus protocols.
Network computers are another type of computer system that can be used in conjunction with the teachings provided herein. Network computers do not usually include a hard disk or other mass storage, and the executable programs are loaded from a network connection into the memory 2612 for execution by the processor 2608. A Web TV system, which is known in the art, is also considered to be a computer system, but it may lack some of the features shown in
In addition, the computer system 2600 is controlled by operating system software which includes a file management system, such as a disk operating system, which is part of the operating system software. One example of operating system software with its associated file management system software is the family of operating systems known as Windows® from Microsoft Corporation of Redmond, Wash., and their associated file management systems. Another example of operating system software with its associated file management system software is the Linux operating system and its associated file management system. The file management system is typically stored in the non-volatile storage 2616 and causes the processor 2608 to execute the various acts required by the operating system to input and output data and to store data in memory, including storing files on the non-volatile storage 2616.
In the example of
In the example of
In the example of
Advantageously, the network service usage analysis engine 2704 can examine a particular service usage activity and the network service usage classification engine 2708 can determine if the particular service usage activity fits a set of one or more classification rules that define the particular service usage activity as, e.g., a background service usage activity.
In the example of
Advantageously, the application traffic prioritization engine 2710 can determine a particular service usage activity has a particular characteristic, such as being a background service usage activity. This can involve checking whether a condition is satisfied.
In the example of
Advantageously, the differential network access control engine can restrict network access of a particular service usage activity when a condition is satisfied, such as when the service usage activity is a background activity.
In the example of
In an illustrative example, the device 2700 blocks chatter for an application running in the background that is attempting to report device or user behavior. The application traffic prioritization engine 2710 determines that the chatter has zero priority, such that the network service consuming application 2702 is prevented from consuming any resources. The user can be sent a notification by the application traffic override engine 2718 that their control policy prohibits the application from consuming network resources, but that the user can opt to deviate from the control policy if they are willing to pay for the consumed resources. If the user is willing to pay for the resources, traffic can be sent at a certain rate from the application traffic cache 2716 through the network interface 2720, or perhaps sent without using the application traffic cache 2716.
As another illustrative example, the device 2700 could identify application traffic as a software update. The differential network access control engine 2714 may determine that software updates can be received at a throttled rate (perhaps even slower than the lowest QoS categorization). The application traffic override engine 2718 can receive an indication from the user, from user preferences, service provider settings, or the like that the updates can ignore the control policy for a particular application (or for all applications).
Advantageously, the control policy can set up a priority to communicate cached elements, set minimum update frequencies, provide control policy overrides (typically for payment), or the like to fine-tune differential network access control policies. This can enable the system 2700 to encourage certain behavior, such as sending low QoS traffic when it is cheaper (e.g., when the network does not have a busy state, at historically low-use times of day, when on a certain type of network, such as Wi-Fi, as opposed to another, such as cellular, etc.).
Some portions of the detailed description are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
The present invention, in some embodiments, also relates to apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus.
The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these systems will appear from the description below. In addition, the present invention is not described with reference to any particular programming language, and various embodiments may thus be implemented using a variety of programming languages.
Although the foregoing embodiments have been described in some detail for purposes of clarity of understanding, the invention is not limited to the details provided. There are many alternative ways of implementing the invention. The disclosed embodiments are illustrative and not restrictive.
This application incorporates by reference the following U.S. Patent Applications for all purposes: U.S. Ser. No. 13/134,028, filed May 25, 2011, entitled “Device-Assisted Services for Protecting Network Capacity”; U.S. Ser. No. 12/380,778 filed Mar. 2, 2009, entitled “Verifiable Device Assisted Service Usage Billing with Integrated Accounting, Mediation Accounting, and Multi-Account”; U.S. Ser. No. 12/380,780 filed Mar. 2, 2009, entitled “Automated Device Provisioning and Activation”; U.S. Ser. No. 12/695,019 filed Jan. 27, 2010, entitled “Device Assisted CDR Creation, Aggregation, Mediation and Billing”; U.S. Ser. No. 12/695,020 filed Jan. 27, 2010, entitled “Adaptive Ambient Services”; U.S. Ser. No. 12/694,445 filed Jan. 27, 2010, entitled “Security Techniques for Device Assisted Services”; U.S. Ser. No. 12/694,451 filed Jan. 27, 2010, entitled “Device Group Partitions and Settlement Platform”; U.S. Ser. No. 12/694,455 filed Jan. 27, 2010, entitled “Device Assisted Services Install”; U.S. Ser. No. 12/695,021 filed Jan. 27, 2010, entitled “Quality of Service for Device Assisted Services”; U.S. Ser. No. 12/695,980 filed Jan. 28, 2010, entitled “Enhanced Roaming Services and Converged Carrier Networks with Device Assisted Services and a Proxy”; and U.S. application Ser. No. 13/134,005, filed May 25, 2011, entitled “System and Method for Wireless Network Offloading”.
This application also incorporates by reference the following U.S. provisional applications: U.S. provisional application Ser. No. 61/206,354, filed Jan. 28, 2009, entitled “Services Policy Communication System and Method”; U.S. provisional application Ser. No. 61/206,944, filed Feb. 4, 2009, entitled “Services Policy Communication System and Method”; U.S. provisional application Ser. No. 61/207,393, filed Feb. 10, 2009, entitled “Services Policy Communication System and Method”; U.S. provisional application Ser. No. 61/207,739, filed Feb. 13, 2009, entitled “Services Policy Communication System and Method”; U.S. provisional application Ser. No. 61/270,353, filed Jul. 6, 2009, entitled “Device Assisted CDR Creation, Aggregation, Mediation and Billing”; U.S. provisional application Ser. No. 61/275,208, filed Aug. 25, 2009, entitled “Adaptive Ambient Services”; U.S. provisional application Ser. No. 61/237,753, filed Aug. 28, 2009, entitled “Adaptive Ambient Services”; U.S. provisional application Ser. No. 61/252,151, filed Oct. 15, 2009, entitled “Security Techniques for Device Assisted Services”; U.S. provisional application Ser. No. 61/252,153, filed Oct. 15, 2009, entitled “Device Group Partitions and Settlement Platform”; U.S. provisional application Ser. No. 61/264,120, filed Nov. 24, 2009, entitled “Device Assisted Services Install,” and U.S. provisional application Ser. No. 61/264,126, filed Nov. 24, 2009, entitled “Device Assisted Services Activity Map”; U.S. provisional application Ser. No. 61/348,022, filed May 25, 2010, entitled “Device Assisted Services for Protecting Network Capacity”; U.S. provisional application Ser. No. 61/381,159, filed Sep. 9, 2010, entitled “Device Assisted Services for Protecting Network Capacity”; U.S. provisional application Ser. No. 61/381,162, filed Sep. 9, 2010, entitled “Service Controller Interfaces and Workflows”; U.S. provisional application Ser. No. 61/384,456, filed Sep. 20, 2010, entitled “Securing Service Processor with Sponsored SIMs”; U.S. provisional application Ser. No. 61/389,547, filed Oct. 4, 2010, entitled “User Notifications for Device Assisted Services”; U.S. provisional application Ser. No. 61/385,020, filed Sep. 21, 2010, entitled “Service Usage Reconciliation System Overview”; U.S. provisional application Ser. No. 61/387,243, filed Sep. 28, 2010, entitled “Enterprise and Consumer Billing Allocation for Wireless Communication Device Service Usage Activities”; U.S. provisional application Ser. No. 61/387,247, filed Sep. 28, 2010, entitled “Secured Device Data Records”; U.S. provisional application Ser. No. 61/407,358, filed Oct. 27, 2010, entitled “Service Controller and Service Processor Architecture”; U.S. provisional application Ser. No. 61/418,507, filed Dec. 1, 2010, entitled “Application Service Provider Interface System”; U.S. provisional application Ser. No. 61/418,509, filed Dec. 1, 2010, entitled “Service Usage Reporting Reconciliation and Fraud Detection for Device Assisted Services”; U.S. provisional application Ser. No. 61/420,727, filed Dec. 7, 2010, entitled “Secure Device Data Records”; U.S. provisional application Ser. No. 61/422,565, filed Dec. 13, 2010, entitled “Service Design Center for Device Assisted Services”; U.S. provisional application Ser. No. 61/422,572, filed Dec. 13, 2010, entitled “System Interfaces and Workflows for Device Assisted Services”; U.S. provisional application Ser. No. 61/422,574, filed Dec. 13, 2010, entitled “Security and Fraud Detection for Device Assisted Services”; U.S. provisional application Ser. No. 61/435,564, filed Jan. 24, 2011, entitled “Framework for Device Assisted Services”; and U.S. provisional application Ser. No. 61/472,606, filed Apr. 6, 2011, entitled “Managing Service User Discovery and Service Launch Object Placement on a Device.”
Number | Name | Date | Kind |
---|---|---|---|
5131020 | Liebesny et al. | Jul 1992 | A |
5283904 | Carson et al. | Feb 1994 | A |
5325532 | Crosswy et al. | Jun 1994 | A |
5572528 | Shuen | Nov 1996 | A |
5577100 | McGregor et al. | Nov 1996 | A |
5594777 | Makkonen et al. | Jan 1997 | A |
5617539 | Ludwig et al. | Apr 1997 | A |
5630159 | Zancho | May 1997 | A |
5633484 | Zancho et al. | May 1997 | A |
5633868 | Baldwin et al. | May 1997 | A |
5751719 | Chen et al. | May 1998 | A |
5754953 | Briancon et al. | May 1998 | A |
5774532 | Gottlieb et al. | Jun 1998 | A |
5794142 | Vanttila et al. | Aug 1998 | A |
5814798 | Zancho | Sep 1998 | A |
5889477 | Fastenrath | Mar 1999 | A |
5892900 | Ginter et al. | Apr 1999 | A |
5903845 | Buhrmann et al. | May 1999 | A |
5915008 | Dulman | Jun 1999 | A |
5915226 | Martineau | Jun 1999 | A |
5933778 | Buhrmann et al. | Aug 1999 | A |
5940472 | Newman et al. | Aug 1999 | A |
5974439 | Bollella | Oct 1999 | A |
5983270 | Abraham et al. | Nov 1999 | A |
6035281 | Crosskey et al. | Mar 2000 | A |
6038452 | Strawczynski et al. | Mar 2000 | A |
6038540 | Krist et al. | Mar 2000 | A |
6047268 | Bartoli et al. | Apr 2000 | A |
6047270 | Joao et al. | Apr 2000 | A |
6058434 | Wilt et al. | May 2000 | A |
6061571 | Tamura | May 2000 | A |
6064878 | Denker et al. | May 2000 | A |
6078953 | Vaid et al. | Jun 2000 | A |
6081591 | Skoog | Jun 2000 | A |
6098878 | Dent et al. | Aug 2000 | A |
6104700 | Haddock et al. | Aug 2000 | A |
6115823 | Velasco et al. | Sep 2000 | A |
6119933 | Wong et al. | Sep 2000 | A |
6125391 | Meltzer et al. | Sep 2000 | A |
6141565 | Feuerstein et al. | Oct 2000 | A |
6141686 | Jackowski et al. | Oct 2000 | A |
6148336 | Thomas et al. | Nov 2000 | A |
6154738 | Call | Nov 2000 | A |
6157636 | Voit et al. | Dec 2000 | A |
6185576 | Mcintosh | Feb 2001 | B1 |
6198915 | McGregor et al. | Mar 2001 | B1 |
6219786 | Cunningham et al. | Apr 2001 | B1 |
6226277 | Chuah | May 2001 | B1 |
6246870 | Dent et al. | Jun 2001 | B1 |
6263055 | Garland et al. | Jul 2001 | B1 |
6292828 | Williams | Sep 2001 | B1 |
6317584 | Abu-Amara et al. | Nov 2001 | B1 |
6370139 | Redmond | Apr 2002 | B2 |
6381316 | Joyce et al. | Apr 2002 | B2 |
6393014 | Daly et al. | May 2002 | B1 |
6397259 | Lincke et al. | May 2002 | B1 |
6401113 | Lazaridis et al. | Jun 2002 | B2 |
6418147 | Wiedeman | Jul 2002 | B1 |
6438575 | Khan et al. | Aug 2002 | B1 |
6445777 | Clark | Sep 2002 | B1 |
6449479 | Sanchez | Sep 2002 | B1 |
6466984 | Naveh et al. | Oct 2002 | B1 |
6477670 | Ahmadvand | Nov 2002 | B1 |
6502131 | Vaid et al. | Dec 2002 | B1 |
6505114 | Luciani | Jan 2003 | B2 |
6510152 | Gerszberg et al. | Jan 2003 | B1 |
6522629 | Anderson, Sr. | Feb 2003 | B1 |
6526066 | Weaver | Feb 2003 | B1 |
6532235 | Benson et al. | Mar 2003 | B1 |
6532579 | Sato et al. | Mar 2003 | B2 |
6535855 | Cahill et al. | Mar 2003 | B1 |
6535949 | Parker | Mar 2003 | B1 |
6539082 | Lowe et al. | Mar 2003 | B1 |
6542465 | Wang | Apr 2003 | B1 |
6542500 | Gerszberg et al. | Apr 2003 | B1 |
6542992 | Peirce et al. | Apr 2003 | B1 |
6546016 | Gerszberg et al. | Apr 2003 | B1 |
6563806 | Yano et al. | May 2003 | B1 |
6570974 | Gerszberg et al. | May 2003 | B1 |
6574321 | Cox et al. | Jun 2003 | B1 |
6574465 | Marsh et al. | Jun 2003 | B2 |
6578076 | Putzolu | Jun 2003 | B1 |
6581092 | Motoyama | Jun 2003 | B1 |
6591098 | Shieh et al. | Jul 2003 | B1 |
6598034 | Kloth | Jul 2003 | B1 |
6601040 | Kolls | Jul 2003 | B1 |
6603969 | Vuoristo et al. | Aug 2003 | B1 |
6603975 | Inouchi et al. | Aug 2003 | B1 |
6606744 | Mikurak | Aug 2003 | B1 |
6628934 | Rosenberg et al. | Sep 2003 | B2 |
6631122 | Arunachalam et al. | Oct 2003 | B1 |
6636721 | Threadgill et al. | Oct 2003 | B2 |
6639975 | O'Neal et al. | Oct 2003 | B1 |
6640097 | Corrigan et al. | Oct 2003 | B2 |
6640334 | Rasmussen | Oct 2003 | B1 |
6650887 | McGregor et al. | Nov 2003 | B2 |
6651101 | Gai et al. | Nov 2003 | B1 |
6654786 | Fox et al. | Nov 2003 | B1 |
6654814 | Britton et al. | Nov 2003 | B1 |
6658254 | Purdy et al. | Dec 2003 | B1 |
6662014 | Walsh | Dec 2003 | B1 |
6678516 | Nordman et al. | Jan 2004 | B2 |
6683853 | Kannas et al. | Jan 2004 | B1 |
6684244 | Goldman et al. | Jan 2004 | B1 |
6690918 | Evans et al. | Feb 2004 | B2 |
6697821 | Ziff et al. | Feb 2004 | B2 |
6725031 | Watler et al. | Apr 2004 | B2 |
6725256 | Albal et al. | Apr 2004 | B1 |
6732176 | Stewart et al. | May 2004 | B1 |
6735206 | Oki et al. | May 2004 | B1 |
6748195 | Phillips | Jun 2004 | B1 |
6748437 | Mankude et al. | Jun 2004 | B1 |
6751296 | Albal et al. | Jun 2004 | B1 |
6754470 | Hendrickson et al. | Jun 2004 | B2 |
6757717 | Goldstein | Jun 2004 | B1 |
6760417 | Wallenius | Jul 2004 | B1 |
6763000 | Walsh | Jul 2004 | B1 |
6763226 | McZeal, Jr. | Jul 2004 | B1 |
6765864 | Natarajan et al. | Jul 2004 | B1 |
6765925 | Sawyer et al. | Jul 2004 | B1 |
6782412 | Brophy et al. | Aug 2004 | B2 |
6785889 | Williams | Aug 2004 | B1 |
6792461 | Hericourt | Sep 2004 | B1 |
6829596 | Frazee | Dec 2004 | B1 |
6829696 | Balmer et al. | Dec 2004 | B1 |
6839340 | Voit et al. | Jan 2005 | B1 |
6842628 | Arnold et al. | Jan 2005 | B1 |
6873988 | Herrmann et al. | Mar 2005 | B2 |
6876653 | Ambe et al. | Apr 2005 | B2 |
6879825 | Daly | Apr 2005 | B1 |
6882718 | Smith | Apr 2005 | B1 |
6885997 | Roberts | Apr 2005 | B1 |
6901440 | Bimm et al. | May 2005 | B1 |
6920455 | Weschler | Jul 2005 | B1 |
6922562 | Ward et al. | Jul 2005 | B2 |
6928280 | Xanthos et al. | Aug 2005 | B1 |
6934249 | Bertin et al. | Aug 2005 | B1 |
6934751 | Jayapalan et al. | Aug 2005 | B2 |
6947723 | Gurnani et al. | Sep 2005 | B1 |
6947985 | Hegli et al. | Sep 2005 | B2 |
6952428 | Necka et al. | Oct 2005 | B1 |
6957067 | Iyer et al. | Oct 2005 | B1 |
6959202 | Heinonen et al. | Oct 2005 | B2 |
6959393 | Hollis et al. | Oct 2005 | B2 |
6965667 | Trabandt et al. | Nov 2005 | B2 |
6965872 | Grdina | Nov 2005 | B1 |
6967958 | Ono et al. | Nov 2005 | B2 |
6970692 | Tysor | Nov 2005 | B2 |
6970927 | Stewart et al. | Nov 2005 | B1 |
6982733 | McNally et al. | Jan 2006 | B1 |
6983370 | Eaton et al. | Jan 2006 | B2 |
6996062 | Freed et al. | Feb 2006 | B1 |
6996076 | Forbes et al. | Feb 2006 | B1 |
6996393 | Pyhalammi et al. | Feb 2006 | B2 |
6998985 | Reisman et al. | Feb 2006 | B2 |
7002920 | Ayyagari et al. | Feb 2006 | B1 |
7007295 | Rose et al. | Feb 2006 | B1 |
7013469 | Smith et al. | Mar 2006 | B2 |
7017189 | DeMello et al. | Mar 2006 | B1 |
7024200 | McKenna et al. | Apr 2006 | B2 |
7024460 | Koopmas et al. | Apr 2006 | B2 |
7027055 | Anderson et al. | Apr 2006 | B2 |
7027408 | Nabkel et al. | Apr 2006 | B2 |
7031733 | Alminana et al. | Apr 2006 | B2 |
7032072 | Quinn et al. | Apr 2006 | B1 |
7039027 | Bridgelall | May 2006 | B2 |
7039037 | Wang et al. | May 2006 | B2 |
7039403 | Wong | May 2006 | B2 |
7039713 | Van Gunter et al. | May 2006 | B1 |
7042988 | Juitt et al. | May 2006 | B2 |
7043225 | Patel et al. | May 2006 | B1 |
7043226 | Yamauchi | May 2006 | B2 |
7043268 | Yukie et al. | May 2006 | B2 |
7047276 | Liu et al. | May 2006 | B2 |
7058022 | Carolan et al. | Jun 2006 | B1 |
7058968 | Rowland et al. | Jun 2006 | B2 |
7068600 | Cain | Jun 2006 | B2 |
7069248 | Huber | Jun 2006 | B2 |
7082422 | Zirngibl et al. | Jul 2006 | B1 |
7084775 | Smith | Aug 2006 | B1 |
7092696 | Hosain et al. | Aug 2006 | B1 |
7095754 | Benveniste | Aug 2006 | B2 |
7102620 | Harries et al. | Sep 2006 | B2 |
7110753 | Campen | Sep 2006 | B2 |
7113780 | Mckenna et al. | Sep 2006 | B2 |
7113997 | Jayapalan et al. | Sep 2006 | B2 |
7120133 | Joo et al. | Oct 2006 | B1 |
7133386 | Holur et al. | Nov 2006 | B2 |
7133695 | Beyda | Nov 2006 | B2 |
7136361 | Benveniste | Nov 2006 | B2 |
7139569 | Kato | Nov 2006 | B2 |
7142876 | Trossen et al. | Nov 2006 | B2 |
7149229 | Leung | Dec 2006 | B1 |
7149521 | Sundar et al. | Dec 2006 | B2 |
7151764 | Heinonen et al. | Dec 2006 | B1 |
7158792 | Cook et al. | Jan 2007 | B1 |
7162237 | Silver et al. | Jan 2007 | B1 |
7165040 | Ehrman et al. | Jan 2007 | B2 |
7167078 | Pourchot | Jan 2007 | B2 |
7174156 | Mangal | Feb 2007 | B1 |
7174174 | Boris et al. | Feb 2007 | B2 |
7177919 | Truong et al. | Feb 2007 | B1 |
7180855 | Lin | Feb 2007 | B1 |
7181017 | Nagel et al. | Feb 2007 | B1 |
7191248 | Chattopadhyay et al. | Mar 2007 | B2 |
7197321 | Erskine et al. | Mar 2007 | B2 |
7200112 | Sundar et al. | Apr 2007 | B2 |
7200551 | Senez | Apr 2007 | B1 |
7203169 | Okholm et al. | Apr 2007 | B1 |
7203721 | Ben-Efraim et al. | Apr 2007 | B1 |
7203752 | Rice et al. | Apr 2007 | B2 |
7209664 | McNicol et al. | Apr 2007 | B1 |
7212491 | Koga | May 2007 | B2 |
7219123 | Fiechter et al. | May 2007 | B1 |
7222190 | Klinker et al. | May 2007 | B2 |
7222304 | Beaton et al. | May 2007 | B2 |
7224968 | Dobson et al. | May 2007 | B2 |
7228354 | Chambliss et al. | Jun 2007 | B2 |
7236780 | Benco | Jun 2007 | B2 |
7242668 | Kan et al. | Jul 2007 | B2 |
7242920 | Morris | Jul 2007 | B2 |
7245901 | McGregor et al. | Jul 2007 | B2 |
7248570 | Bahl et al. | Jul 2007 | B2 |
7251218 | Jorgensen | Jul 2007 | B2 |
7260382 | Lamb et al. | Aug 2007 | B1 |
7266371 | Amin et al. | Sep 2007 | B1 |
7269157 | Klinker et al. | Sep 2007 | B2 |
7271765 | Stilp et al. | Sep 2007 | B2 |
7272660 | Powers et al. | Sep 2007 | B1 |
7280816 | Fratti et al. | Oct 2007 | B2 |
7280818 | Clayton | Oct 2007 | B2 |
7283561 | Picher-Dempsey | Oct 2007 | B1 |
7283963 | Fitzpatrick et al. | Oct 2007 | B1 |
7286834 | Walter | Oct 2007 | B2 |
7286848 | Vireday et al. | Oct 2007 | B2 |
7289489 | Kung et al. | Oct 2007 | B1 |
7290283 | Copeland, III | Oct 2007 | B2 |
7310424 | Gehring et al. | Dec 2007 | B2 |
7313237 | Bahl et al. | Dec 2007 | B2 |
7315892 | Freimuth et al. | Jan 2008 | B2 |
7317699 | Godfrey et al. | Jan 2008 | B2 |
7318111 | Zhao | Jan 2008 | B2 |
7320029 | Rinne et al. | Jan 2008 | B2 |
7322044 | Hrastar | Jan 2008 | B2 |
7324447 | Morford | Jan 2008 | B1 |
7325037 | Lawson | Jan 2008 | B2 |
7336960 | Zavalkovsky et al. | Feb 2008 | B2 |
7340244 | Osborne et al. | Mar 2008 | B1 |
7340772 | Panasyuk et al. | Mar 2008 | B2 |
7346410 | Uchiyama | Mar 2008 | B2 |
7349695 | Oommen et al. | Mar 2008 | B2 |
7353533 | Wright et al. | Apr 2008 | B2 |
7356011 | Waters et al. | Apr 2008 | B1 |
7356337 | Florence | Apr 2008 | B2 |
7366497 | Nagata | Apr 2008 | B2 |
7366654 | Moore | Apr 2008 | B2 |
7369848 | Jiang | May 2008 | B2 |
7369856 | Ovadia | May 2008 | B2 |
7373136 | Watler et al. | May 2008 | B2 |
7373179 | Stine et al. | May 2008 | B2 |
7379731 | Natsuno et al. | May 2008 | B2 |
7388950 | Elsey et al. | Jun 2008 | B2 |
7389412 | Sharma et al. | Jun 2008 | B2 |
7391724 | Alakoski et al. | Jun 2008 | B2 |
7395244 | Kingsford | Jul 2008 | B1 |
7401338 | Bowen et al. | Jul 2008 | B1 |
7403763 | Maes | Jul 2008 | B2 |
7409447 | Assadzadeh | Aug 2008 | B1 |
7409569 | Illowsky et al. | Aug 2008 | B2 |
7411930 | Montojo et al. | Aug 2008 | B2 |
7418253 | Kavanah | Aug 2008 | B2 |
7418257 | Kim | Aug 2008 | B2 |
7421004 | Feher | Sep 2008 | B2 |
7423971 | Mohaban et al. | Sep 2008 | B1 |
7428750 | Dunn et al. | Sep 2008 | B1 |
7433362 | Mallya et al. | Oct 2008 | B2 |
7436816 | Mehta et al. | Oct 2008 | B2 |
7440433 | Rink et al. | Oct 2008 | B2 |
7444669 | Bahl et al. | Oct 2008 | B1 |
7450591 | Korling et al. | Nov 2008 | B2 |
7450927 | Creswell et al. | Nov 2008 | B1 |
7454191 | Dawson et al. | Nov 2008 | B2 |
7457265 | Julka et al. | Nov 2008 | B2 |
7457870 | Lownsbrough et al. | Nov 2008 | B1 |
7460837 | Diener | Dec 2008 | B2 |
7466652 | Lau et al. | Dec 2008 | B2 |
7467160 | McIntyre | Dec 2008 | B2 |
7472189 | Mallya et al. | Dec 2008 | B2 |
7478420 | Wright et al. | Jan 2009 | B2 |
7486185 | Culpepper et al. | Feb 2009 | B2 |
7486658 | Kumar | Feb 2009 | B2 |
7489918 | Zhou et al. | Feb 2009 | B2 |
7493659 | Wu et al. | Feb 2009 | B1 |
7496652 | Pezzutti | Feb 2009 | B2 |
7499438 | Hinman et al. | Mar 2009 | B2 |
7499537 | Elsey et al. | Mar 2009 | B2 |
7502672 | Kolls | Mar 2009 | B1 |
7505756 | Bahl | Mar 2009 | B2 |
7505795 | Lim et al. | Mar 2009 | B1 |
7508799 | Sumner et al. | Mar 2009 | B2 |
7512128 | DiMambro et al. | Mar 2009 | B2 |
7512131 | Svensson et al. | Mar 2009 | B2 |
7515608 | Yuan et al. | Apr 2009 | B2 |
7515926 | Bu et al. | Apr 2009 | B2 |
7516219 | Moghaddam et al. | Apr 2009 | B2 |
7522549 | Karaoguz et al. | Apr 2009 | B2 |
7522576 | Du et al. | Apr 2009 | B2 |
7526541 | Roese et al. | Apr 2009 | B2 |
7529204 | Bourlas et al. | May 2009 | B2 |
7535880 | Hinman et al. | May 2009 | B1 |
7536695 | Alam et al. | May 2009 | B2 |
7539132 | Werner et al. | May 2009 | B2 |
7539862 | Edgett et al. | May 2009 | B2 |
7540408 | Levine et al. | Jun 2009 | B2 |
7545782 | Rayment et al. | Jun 2009 | B2 |
7546460 | Maes | Jun 2009 | B2 |
7546629 | Albert et al. | Jun 2009 | B2 |
7548875 | Mikkelsen et al. | Jun 2009 | B2 |
7548976 | Bahl et al. | Jun 2009 | B2 |
7551921 | Petermann | Jun 2009 | B2 |
7551922 | Roskowski et al. | Jun 2009 | B2 |
7554983 | Muppala | Jun 2009 | B1 |
7555757 | Smith et al. | Jun 2009 | B2 |
7561899 | Lee | Jul 2009 | B2 |
7562213 | Timms | Jul 2009 | B1 |
7564799 | Holland et al. | Jul 2009 | B2 |
7565141 | Macaluso | Jul 2009 | B2 |
7565328 | Donner | Jul 2009 | B1 |
7574509 | Nixon et al. | Aug 2009 | B2 |
7574731 | Fascenda | Aug 2009 | B2 |
7577431 | Jiang | Aug 2009 | B2 |
7580356 | Mishra et al. | Aug 2009 | B1 |
7580857 | VanFleet et al. | Aug 2009 | B2 |
7583964 | Wong | Sep 2009 | B2 |
7584298 | Klinker et al. | Sep 2009 | B2 |
7585217 | Lutnick et al. | Sep 2009 | B2 |
7586871 | Hamilton et al. | Sep 2009 | B2 |
7593417 | Wang et al. | Sep 2009 | B2 |
7593730 | Khandelwal et al. | Sep 2009 | B2 |
7596373 | Mcgregor et al. | Sep 2009 | B2 |
7599288 | Cole et al. | Oct 2009 | B2 |
7599714 | Kuzminskiy | Oct 2009 | B2 |
7602746 | Calhoun et al. | Oct 2009 | B2 |
7606357 | Daigle | Oct 2009 | B2 |
7606918 | Holzman et al. | Oct 2009 | B2 |
7607041 | Kraemer et al. | Oct 2009 | B2 |
7609650 | Roskowski et al. | Oct 2009 | B2 |
7609700 | Ying et al. | Oct 2009 | B1 |
7610047 | Hicks, III et al. | Oct 2009 | B2 |
7610057 | Bahl et al. | Oct 2009 | B2 |
7610328 | Haase et al. | Oct 2009 | B2 |
7610396 | Taglienti et al. | Oct 2009 | B2 |
7612712 | LaMance et al. | Nov 2009 | B2 |
7613444 | Lindqvist et al. | Nov 2009 | B2 |
7614051 | Glaum et al. | Nov 2009 | B2 |
7616962 | Oswal et al. | Nov 2009 | B2 |
7617516 | Huslak et al. | Nov 2009 | B2 |
7620041 | Dunn et al. | Nov 2009 | B2 |
7620065 | Falardeau | Nov 2009 | B2 |
7620162 | Aaron et al. | Nov 2009 | B2 |
7620383 | Taglienti et al. | Nov 2009 | B2 |
7627314 | Carlson et al. | Dec 2009 | B2 |
7627600 | Citron et al. | Dec 2009 | B2 |
7627767 | Sherman et al. | Dec 2009 | B2 |
7627872 | Hebeler et al. | Dec 2009 | B2 |
7633438 | Tysowski | Dec 2009 | B2 |
7634388 | Archer et al. | Dec 2009 | B2 |
7636574 | Poosala | Dec 2009 | B2 |
7636626 | Oesterling et al. | Dec 2009 | B2 |
7643411 | Andreasen et al. | Jan 2010 | B2 |
7644151 | Jerrim et al. | Jan 2010 | B2 |
7644267 | Ylikoski et al. | Jan 2010 | B2 |
7644414 | Smith et al. | Jan 2010 | B2 |
7647047 | Moghaddam et al. | Jan 2010 | B2 |
7650137 | Jobs et al. | Jan 2010 | B2 |
7653394 | McMillin | Jan 2010 | B2 |
7656271 | Ehrman et al. | Feb 2010 | B2 |
7657920 | Arseneau et al. | Feb 2010 | B2 |
7660419 | Ho | Feb 2010 | B1 |
7661124 | Ramanathan et al. | Feb 2010 | B2 |
7664494 | Jiang | Feb 2010 | B2 |
7668176 | Chuah | Feb 2010 | B2 |
7668612 | Okkonen | Feb 2010 | B1 |
7668903 | Edwards et al. | Feb 2010 | B2 |
7668966 | Klinker et al. | Feb 2010 | B2 |
7676673 | Weller et al. | Mar 2010 | B2 |
7680086 | Eglin | Mar 2010 | B2 |
7681226 | Kraemer et al. | Mar 2010 | B2 |
7684370 | Kezys | Mar 2010 | B2 |
7685131 | Batra et al. | Mar 2010 | B2 |
7685254 | Pandya | Mar 2010 | B2 |
7685530 | Sherrard et al. | Mar 2010 | B2 |
7688792 | Babbar et al. | Mar 2010 | B2 |
7693107 | De Froment | Apr 2010 | B2 |
7693720 | Kennewick et al. | Apr 2010 | B2 |
7697540 | Haddad et al. | Apr 2010 | B2 |
7707320 | Singhai et al. | Apr 2010 | B2 |
7710932 | Muthuswamy et al. | May 2010 | B2 |
7711848 | Maes | May 2010 | B2 |
7719966 | Luft et al. | May 2010 | B2 |
7720206 | Devolites et al. | May 2010 | B2 |
7720464 | Batta | May 2010 | B2 |
7720505 | Gopi et al. | May 2010 | B2 |
7720960 | Pruss et al. | May 2010 | B2 |
7721296 | Ricagni | May 2010 | B2 |
7724716 | Fadell | May 2010 | B2 |
7725570 | Lewis | May 2010 | B1 |
7729326 | Sekhar | Jun 2010 | B2 |
7730123 | Erickson et al. | Jun 2010 | B1 |
7734784 | Araujo et al. | Jun 2010 | B1 |
7742406 | Muppala | Jun 2010 | B1 |
7742961 | Aaron et al. | Jun 2010 | B2 |
7746854 | Ambe et al. | Jun 2010 | B2 |
7747240 | Briscoe et al. | Jun 2010 | B1 |
7747699 | Prueitt et al. | Jun 2010 | B2 |
7747730 | Harlow | Jun 2010 | B1 |
7752330 | Olsen et al. | Jul 2010 | B2 |
7756056 | Kim et al. | Jul 2010 | B2 |
7756509 | Rajagopalan et al. | Jul 2010 | B2 |
7756534 | Anupam et al. | Jul 2010 | B2 |
7756757 | Oakes, III | Jul 2010 | B1 |
7760137 | Martucci et al. | Jul 2010 | B2 |
7760711 | Kung et al. | Jul 2010 | B1 |
7760861 | Croak et al. | Jul 2010 | B1 |
7765294 | Edwards et al. | Jul 2010 | B2 |
7769397 | Funato et al. | Aug 2010 | B2 |
7770785 | Jha et al. | Aug 2010 | B2 |
7774323 | Helfman | Aug 2010 | B2 |
7774412 | Schnepel | Aug 2010 | B1 |
7774456 | Lownsbrough et al. | Aug 2010 | B1 |
7778176 | Morford | Aug 2010 | B2 |
7778643 | Laroia et al. | Aug 2010 | B2 |
7792257 | Vanier et al. | Sep 2010 | B1 |
7792538 | Kozisek | Sep 2010 | B2 |
7792708 | Alva | Sep 2010 | B2 |
7797019 | Friedmann | Sep 2010 | B2 |
7797060 | Grgic et al. | Sep 2010 | B2 |
7797204 | Balent | Sep 2010 | B2 |
7797401 | Stewart et al. | Sep 2010 | B2 |
7801523 | Kenderov | Sep 2010 | B1 |
7801783 | Kende et al. | Sep 2010 | B2 |
7801985 | Pitkow et al. | Sep 2010 | B1 |
7802724 | Nohr | Sep 2010 | B1 |
7805140 | Friday et al. | Sep 2010 | B2 |
7805522 | Schlüter et al. | Sep 2010 | B2 |
7805606 | Birger et al. | Sep 2010 | B2 |
7809351 | Panda et al. | Oct 2010 | B1 |
7809372 | Rajaniemi | Oct 2010 | B2 |
7813746 | Rajkotia | Oct 2010 | B2 |
7817615 | Breau et al. | Oct 2010 | B1 |
7817983 | Cassett et al. | Oct 2010 | B2 |
7822837 | Urban et al. | Oct 2010 | B1 |
7822849 | Titus | Oct 2010 | B2 |
7826427 | Sood et al. | Nov 2010 | B2 |
7826607 | De Carvalho Resende et al. | Nov 2010 | B1 |
7835275 | Swan et al. | Nov 2010 | B1 |
7843831 | Morrill et al. | Nov 2010 | B2 |
7843843 | Papp, III et al. | Nov 2010 | B1 |
7844034 | Oh et al. | Nov 2010 | B1 |
7844728 | Anderson et al. | Nov 2010 | B2 |
7848768 | Omori et al. | Dec 2010 | B2 |
7849161 | Koch et al. | Dec 2010 | B2 |
7849170 | Hargens et al. | Dec 2010 | B1 |
7849477 | Cristofalo et al. | Dec 2010 | B2 |
7853255 | Karaoguz et al. | Dec 2010 | B2 |
7853656 | Yach et al. | Dec 2010 | B2 |
7856226 | Wong et al. | Dec 2010 | B2 |
7860088 | Lioy | Dec 2010 | B2 |
7865182 | Macaluso | Jan 2011 | B2 |
7865187 | Ramer et al. | Jan 2011 | B2 |
7868778 | Kenwright | Jan 2011 | B2 |
7868814 | Bergman | Jan 2011 | B1 |
7873001 | Silver | Jan 2011 | B2 |
7873344 | Bowser et al. | Jan 2011 | B2 |
7873346 | Petersson et al. | Jan 2011 | B2 |
7873540 | Arumugam | Jan 2011 | B2 |
7873705 | Kalish | Jan 2011 | B2 |
7877090 | Maes | Jan 2011 | B2 |
7881199 | Krstulich | Feb 2011 | B2 |
7881697 | Baker et al. | Feb 2011 | B2 |
7882029 | White | Feb 2011 | B2 |
7882247 | Sturniolo et al. | Feb 2011 | B2 |
7882560 | Kraemer et al. | Feb 2011 | B2 |
7885644 | Gallagher et al. | Feb 2011 | B2 |
7886047 | Potluri | Feb 2011 | B1 |
7889384 | Armentrout et al. | Feb 2011 | B2 |
7890084 | Dudziak et al. | Feb 2011 | B1 |
7890111 | Bugenhagen | Feb 2011 | B2 |
7890581 | Rao et al. | Feb 2011 | B2 |
7894431 | Goring et al. | Feb 2011 | B2 |
7899039 | Andreasen et al. | Mar 2011 | B2 |
7899438 | Baker et al. | Mar 2011 | B2 |
7903553 | Liu | Mar 2011 | B2 |
7907970 | Park et al. | Mar 2011 | B2 |
7911975 | Droz et al. | Mar 2011 | B2 |
7912025 | Pattenden et al. | Mar 2011 | B2 |
7912056 | Brassem | Mar 2011 | B1 |
7917130 | Christensen et al. | Mar 2011 | B1 |
7920529 | Mahler et al. | Apr 2011 | B1 |
7921463 | Sood et al. | Apr 2011 | B2 |
7925740 | Nath et al. | Apr 2011 | B2 |
7925778 | Wijnands et al. | Apr 2011 | B1 |
7929446 | Bozarth et al. | Apr 2011 | B2 |
7929959 | DeAtley et al. | Apr 2011 | B2 |
7929960 | Martin et al. | Apr 2011 | B2 |
7929973 | Zavalkovsky et al. | Apr 2011 | B2 |
7930327 | Craft et al. | Apr 2011 | B2 |
7930446 | Kesselman et al. | Apr 2011 | B2 |
7930553 | Satarasinghe et al. | Apr 2011 | B2 |
7933274 | Verma et al. | Apr 2011 | B2 |
7936736 | Proctor, Jr. et al. | May 2011 | B2 |
7937069 | Rassam | May 2011 | B2 |
7937450 | Janik | May 2011 | B2 |
7937470 | Curley et al. | May 2011 | B2 |
7940685 | Breslau et al. | May 2011 | B1 |
7940751 | Hansen | May 2011 | B2 |
7941184 | Prendergast et al. | May 2011 | B2 |
7944948 | Chow et al. | May 2011 | B2 |
7945238 | Baker et al. | May 2011 | B2 |
7945240 | Klock et al. | May 2011 | B1 |
7945470 | Cohen et al. | May 2011 | B1 |
7945945 | Graham et al. | May 2011 | B2 |
7948952 | Hurtta et al. | May 2011 | B2 |
7948953 | Melkote et al. | May 2011 | B2 |
7948968 | Voit et al. | May 2011 | B2 |
7949529 | Weider et al. | May 2011 | B2 |
7953808 | Sharp et al. | May 2011 | B2 |
7953877 | Vemula et al. | May 2011 | B2 |
7957020 | Mine et al. | Jun 2011 | B2 |
7957381 | Clermidy et al. | Jun 2011 | B2 |
7957511 | Drudis et al. | Jun 2011 | B2 |
7958029 | Bobich et al. | Jun 2011 | B1 |
7962622 | Friend et al. | Jun 2011 | B2 |
7965983 | Swan et al. | Jun 2011 | B1 |
7966405 | Sundaresan et al. | Jun 2011 | B2 |
7969950 | Iyer et al. | Jun 2011 | B2 |
7970350 | Sheynman | Jun 2011 | B2 |
7970426 | Poe et al. | Jun 2011 | B2 |
7974624 | Gallagher et al. | Jul 2011 | B2 |
7975184 | Goff et al. | Jul 2011 | B2 |
7978627 | Taylor et al. | Jul 2011 | B2 |
7978686 | Goyal et al. | Jul 2011 | B2 |
7979069 | Hupp et al. | Jul 2011 | B2 |
7979889 | Gladstone et al. | Jul 2011 | B2 |
7979896 | McMurtry et al. | Jul 2011 | B2 |
7984130 | Bogineni et al. | Jul 2011 | B2 |
7984511 | Kocher et al. | Jul 2011 | B2 |
7986935 | D'Souza et al. | Jul 2011 | B1 |
7987496 | Bryce et al. | Jul 2011 | B2 |
7987510 | Kocher et al. | Jul 2011 | B2 |
7990049 | Shioya | Aug 2011 | B2 |
8000276 | Scherzer et al. | Aug 2011 | B2 |
8000318 | Wiley et al. | Aug 2011 | B2 |
8005009 | McKee et al. | Aug 2011 | B2 |
8005459 | Balsillie | Aug 2011 | B2 |
8005726 | Bao | Aug 2011 | B1 |
8005913 | Carlander | Aug 2011 | B1 |
8005988 | Maes | Aug 2011 | B2 |
8010080 | Thenthiruperai et al. | Aug 2011 | B1 |
8010081 | Roskowski | Aug 2011 | B1 |
8010082 | Sutaria et al. | Aug 2011 | B2 |
8010990 | Ferguson et al. | Aug 2011 | B2 |
8015133 | Wu et al. | Sep 2011 | B1 |
8015234 | Lum et al. | Sep 2011 | B2 |
8015249 | Nayak et al. | Sep 2011 | B2 |
8019687 | Wang et al. | Sep 2011 | B2 |
8019820 | Son et al. | Sep 2011 | B2 |
8019846 | Roelens et al. | Sep 2011 | B2 |
8019868 | Rao et al. | Sep 2011 | B2 |
8019886 | Harrang et al. | Sep 2011 | B2 |
8023425 | Raleigh | Sep 2011 | B2 |
8024397 | Erickson et al. | Sep 2011 | B1 |
8024424 | Freimuth et al. | Sep 2011 | B2 |
8027339 | Short et al. | Sep 2011 | B2 |
8031601 | Feroz et al. | Oct 2011 | B2 |
8032168 | Ikaheimo | Oct 2011 | B2 |
8032409 | Mikurak | Oct 2011 | B1 |
8032899 | Archer et al. | Oct 2011 | B2 |
8036387 | Kudelski et al. | Oct 2011 | B2 |
8036600 | Garrett et al. | Oct 2011 | B2 |
8044792 | Orr et al. | Oct 2011 | B2 |
8045973 | Chambers | Oct 2011 | B2 |
8046449 | Yoshiuchi | Oct 2011 | B2 |
8050275 | Iyer | Nov 2011 | B1 |
8050690 | Neeraj | Nov 2011 | B2 |
8050705 | Sicher et al. | Nov 2011 | B2 |
8054778 | Polson | Nov 2011 | B2 |
8059530 | Cole | Nov 2011 | B1 |
8060017 | Schlicht et al. | Nov 2011 | B2 |
8060463 | Spiegel | Nov 2011 | B1 |
8064418 | Maki | Nov 2011 | B2 |
8064896 | Bell et al. | Nov 2011 | B2 |
8065365 | Saxena et al. | Nov 2011 | B2 |
8068824 | Shan et al. | Nov 2011 | B2 |
8068829 | Lemond et al. | Nov 2011 | B2 |
8073427 | Koch et al. | Dec 2011 | B2 |
8073721 | Lewis | Dec 2011 | B1 |
8078140 | Baker et al. | Dec 2011 | B2 |
8078163 | Lemond et al. | Dec 2011 | B2 |
8085808 | Brusca et al. | Dec 2011 | B2 |
8086398 | Sanchez et al. | Dec 2011 | B2 |
8086497 | Oakes, III | Dec 2011 | B1 |
8086791 | Caulkins | Dec 2011 | B2 |
8090359 | Proctor, Jr. et al. | Jan 2012 | B2 |
8090361 | Hagan | Jan 2012 | B2 |
8090616 | Proctor, Jr. et al. | Jan 2012 | B2 |
8091087 | Ali et al. | Jan 2012 | B2 |
8094551 | Huber et al. | Jan 2012 | B2 |
8095112 | Chow et al. | Jan 2012 | B2 |
8095124 | Balia | Jan 2012 | B2 |
8095640 | Guingo et al. | Jan 2012 | B2 |
8095666 | Schmidt et al. | Jan 2012 | B2 |
8098579 | Ray et al. | Jan 2012 | B2 |
8099077 | Chowdhury et al. | Jan 2012 | B2 |
8099517 | Jia et al. | Jan 2012 | B2 |
8102814 | Rahman et al. | Jan 2012 | B2 |
8103285 | Kalhan | Jan 2012 | B2 |
8104080 | Burns et al. | Jan 2012 | B2 |
8107953 | Zimmerman et al. | Jan 2012 | B2 |
8108520 | Ruutu et al. | Jan 2012 | B2 |
8108680 | Murray | Jan 2012 | B2 |
8112435 | Epstein et al. | Feb 2012 | B2 |
8116223 | Tian et al. | Feb 2012 | B2 |
8116749 | Proctor, Jr. et al. | Feb 2012 | B2 |
8116781 | Chen et al. | Feb 2012 | B2 |
8121117 | Amdahl et al. | Feb 2012 | B1 |
8122128 | Burke, II et al. | Feb 2012 | B2 |
8122249 | Falk et al. | Feb 2012 | B2 |
8125897 | Ray et al. | Feb 2012 | B2 |
8126123 | Cai et al. | Feb 2012 | B2 |
8126396 | Bennett | Feb 2012 | B2 |
8126476 | Vardi et al. | Feb 2012 | B2 |
8126722 | Robb et al. | Feb 2012 | B2 |
8130793 | Edwards et al. | Mar 2012 | B2 |
8131256 | Martti et al. | Mar 2012 | B2 |
8131281 | Hildner et al. | Mar 2012 | B1 |
8131840 | Denker | Mar 2012 | B1 |
8131858 | Agulnik et al. | Mar 2012 | B2 |
8132256 | Bari | Mar 2012 | B2 |
8134954 | Godfrey et al. | Mar 2012 | B2 |
8135388 | Gailloux et al. | Mar 2012 | B1 |
8135392 | Marcellino et al. | Mar 2012 | B2 |
8135657 | Kapoor et al. | Mar 2012 | B2 |
8140690 | Ly et al. | Mar 2012 | B2 |
8144591 | Ghai et al. | Mar 2012 | B2 |
8145194 | Yoshikawa et al. | Mar 2012 | B2 |
8146142 | Lortz et al. | Mar 2012 | B2 |
8149748 | Bata et al. | Apr 2012 | B2 |
8149771 | Khivesara et al. | Apr 2012 | B2 |
8149823 | Turcan et al. | Apr 2012 | B2 |
8150394 | Bianconi et al. | Apr 2012 | B2 |
8150431 | Wolovitz et al. | Apr 2012 | B2 |
8151205 | Follmann et al. | Apr 2012 | B2 |
8152246 | Miller et al. | Apr 2012 | B2 |
8155155 | Chow et al. | Apr 2012 | B1 |
8155620 | Wang et al. | Apr 2012 | B2 |
8155666 | Alizadeh-Shabdiz | Apr 2012 | B2 |
8155670 | Fullam et al. | Apr 2012 | B2 |
8156206 | Kiley et al. | Apr 2012 | B2 |
8159520 | Dhanoa et al. | Apr 2012 | B1 |
8160015 | Rashid et al. | Apr 2012 | B2 |
8160056 | Van der Merwe et al. | Apr 2012 | B2 |
8160554 | Gosselin et al. | Apr 2012 | B2 |
8160555 | Gosselin et al. | Apr 2012 | B2 |
8160556 | Gosselin et al. | Apr 2012 | B2 |
8160598 | Savoor | Apr 2012 | B2 |
8165576 | Raju et al. | Apr 2012 | B2 |
8166040 | Brindisi et al. | Apr 2012 | B2 |
8166554 | John | Apr 2012 | B2 |
8170553 | Bennett | May 2012 | B2 |
8174378 | Richman et al. | May 2012 | B2 |
8174970 | Adamczyk et al. | May 2012 | B2 |
8175574 | Panda et al. | May 2012 | B1 |
8175966 | Steinberg et al. | May 2012 | B2 |
8180333 | Wells et al. | May 2012 | B1 |
8180881 | Seo et al. | May 2012 | B2 |
8180886 | Overcash et al. | May 2012 | B2 |
8184530 | Swan et al. | May 2012 | B1 |
8184590 | Rosenblatt | May 2012 | B2 |
8185088 | Klein et al. | May 2012 | B2 |
8185093 | Jheng et al. | May 2012 | B2 |
8185127 | Cai et al. | May 2012 | B1 |
8185152 | Goldner | May 2012 | B1 |
8185158 | Tamura et al. | May 2012 | B2 |
8190087 | Fisher et al. | May 2012 | B2 |
8190122 | Alexander et al. | May 2012 | B1 |
8190675 | Tribbett | May 2012 | B2 |
8191106 | Choyi et al. | May 2012 | B2 |
8191116 | Gazzard | May 2012 | B1 |
8191124 | Wynn et al. | May 2012 | B2 |
8194549 | Huber et al. | Jun 2012 | B2 |
8194553 | Liang et al. | Jun 2012 | B2 |
8194572 | Horvath et al. | Jun 2012 | B2 |
8194581 | Schroeder et al. | Jun 2012 | B1 |
8195093 | Garrett et al. | Jun 2012 | B2 |
8195153 | Frencel et al. | Jun 2012 | B1 |
8195163 | Gisby et al. | Jun 2012 | B2 |
8195661 | Kalavade | Jun 2012 | B2 |
8196199 | Hrastar et al. | Jun 2012 | B2 |
8200163 | Hoffman | Jun 2012 | B2 |
8200200 | Belser et al. | Jun 2012 | B1 |
8200509 | Kenedy et al. | Jun 2012 | B2 |
8200775 | Moore | Jun 2012 | B2 |
8200818 | Freund et al. | Jun 2012 | B2 |
8204190 | Bang et al. | Jun 2012 | B2 |
8204505 | Jin et al. | Jun 2012 | B2 |
8204794 | Peng et al. | Jun 2012 | B1 |
8208788 | Ando et al. | Jun 2012 | B2 |
8208919 | Kotecha | Jun 2012 | B2 |
8213296 | Shannon et al. | Jul 2012 | B2 |
8213363 | Ying et al. | Jul 2012 | B2 |
8214536 | Zhao | Jul 2012 | B2 |
8214890 | Kirovski et al. | Jul 2012 | B2 |
8219134 | Maharajh et al. | Jul 2012 | B2 |
8223655 | Heinz et al. | Jul 2012 | B2 |
8223741 | Bartlett et al. | Jul 2012 | B1 |
8224382 | Bultman | Jul 2012 | B2 |
8224773 | Spiegel | Jul 2012 | B2 |
8228818 | Chase et al. | Jul 2012 | B2 |
8229394 | Karlberg | Jul 2012 | B2 |
8229914 | Ramer et al. | Jul 2012 | B2 |
8230061 | Hassan et al. | Jul 2012 | B2 |
8233433 | Kalhan | Jul 2012 | B2 |
8233878 | Gosnell et al. | Jul 2012 | B2 |
8233883 | De Froment | Jul 2012 | B2 |
8233895 | Tysowski | Jul 2012 | B2 |
8234583 | Sloo et al. | Jul 2012 | B2 |
8238287 | Gopi et al. | Aug 2012 | B1 |
8239520 | Grah | Aug 2012 | B2 |
8242959 | Mia et al. | Aug 2012 | B2 |
8244241 | Montemurro | Aug 2012 | B2 |
8249601 | Emberson et al. | Aug 2012 | B2 |
8254880 | Aaltonen et al. | Aug 2012 | B2 |
8254915 | Kozisek | Aug 2012 | B2 |
8255515 | Melman et al. | Aug 2012 | B1 |
8255534 | Assadzadeh | Aug 2012 | B2 |
8255689 | Kim et al. | Aug 2012 | B2 |
8259692 | Bajko | Sep 2012 | B2 |
8264965 | Dolganow et al. | Sep 2012 | B2 |
8265004 | Toutonghi | Sep 2012 | B2 |
8266249 | Hu | Sep 2012 | B2 |
8266269 | Short et al. | Sep 2012 | B2 |
8266681 | Deshpande et al. | Sep 2012 | B2 |
8270955 | Ramer et al. | Sep 2012 | B2 |
8270972 | Otting et al. | Sep 2012 | B2 |
8271025 | Brisebois et al. | Sep 2012 | B2 |
8271045 | Parolkar et al. | Sep 2012 | B2 |
8271049 | Silver et al. | Sep 2012 | B2 |
8271992 | Chatley et al. | Sep 2012 | B2 |
8275415 | Huslak | Sep 2012 | B2 |
8275830 | Raleigh | Sep 2012 | B2 |
8279067 | Berger et al. | Oct 2012 | B2 |
8279864 | Wood | Oct 2012 | B2 |
8280351 | Ahmed et al. | Oct 2012 | B1 |
8280354 | Smith et al. | Oct 2012 | B2 |
8284740 | O'Connor | Oct 2012 | B2 |
8285249 | Baker et al. | Oct 2012 | B2 |
8285992 | Mathur et al. | Oct 2012 | B2 |
8290820 | Plastina et al. | Oct 2012 | B2 |
8291238 | Ginter et al. | Oct 2012 | B2 |
8291439 | Jethi et al. | Oct 2012 | B2 |
8296404 | McDysan et al. | Oct 2012 | B2 |
8300575 | Willars | Oct 2012 | B2 |
8301513 | Peng et al. | Oct 2012 | B1 |
8306505 | Bennett | Nov 2012 | B2 |
8306518 | Gailloux | Nov 2012 | B1 |
8306741 | Tu | Nov 2012 | B2 |
8307067 | Ryan | Nov 2012 | B2 |
8307095 | Clark et al. | Nov 2012 | B2 |
8310943 | Mehta et al. | Nov 2012 | B2 |
8315198 | Corneille et al. | Nov 2012 | B2 |
8315593 | Gallant et al. | Nov 2012 | B2 |
8315594 | Mauser et al. | Nov 2012 | B1 |
8315718 | Caffrey et al. | Nov 2012 | B2 |
8315999 | Chatley et al. | Nov 2012 | B2 |
8320244 | Muqattash et al. | Nov 2012 | B2 |
8320902 | Moring et al. | Nov 2012 | B2 |
8320949 | Matta | Nov 2012 | B2 |
8325638 | Jin et al. | Dec 2012 | B2 |
8325906 | Fullarton et al. | Dec 2012 | B2 |
8326319 | Davis | Dec 2012 | B2 |
8326359 | Kauffman | Dec 2012 | B2 |
8326828 | Zhou et al. | Dec 2012 | B2 |
8331223 | Hill et al. | Dec 2012 | B2 |
8331293 | Sood | Dec 2012 | B2 |
8332375 | Chatley et al. | Dec 2012 | B2 |
8332517 | Russell | Dec 2012 | B2 |
8335161 | Foottit et al. | Dec 2012 | B2 |
8339991 | Biswas et al. | Dec 2012 | B2 |
8340625 | Johnson et al. | Dec 2012 | B1 |
8340628 | Taylor et al. | Dec 2012 | B2 |
8340644 | Sigmund et al. | Dec 2012 | B2 |
8340678 | Pandey | Dec 2012 | B1 |
8340718 | Colonna et al. | Dec 2012 | B2 |
8346210 | Balsan et al. | Jan 2013 | B2 |
8346923 | Rowles et al. | Jan 2013 | B2 |
8347104 | Pathiyal | Jan 2013 | B2 |
8347362 | Cai et al. | Jan 2013 | B2 |
8347378 | Merkin et al. | Jan 2013 | B2 |
8350700 | Fast et al. | Jan 2013 | B2 |
8351592 | Freeny, Jr. et al. | Jan 2013 | B2 |
8351898 | Raleigh | Jan 2013 | B2 |
8352360 | De Judicibus et al. | Jan 2013 | B2 |
8352630 | Hart | Jan 2013 | B2 |
8352980 | Howcroft | Jan 2013 | B2 |
8353001 | Herrod | Jan 2013 | B2 |
8355570 | Karsanbhai et al. | Jan 2013 | B2 |
8355696 | Olding et al. | Jan 2013 | B1 |
8356336 | Johnston et al. | Jan 2013 | B2 |
8358638 | Scherzer et al. | Jan 2013 | B2 |
8358975 | Bahl et al. | Jan 2013 | B2 |
8363658 | Delker et al. | Jan 2013 | B1 |
8363799 | Gruchala et al. | Jan 2013 | B2 |
8364089 | Phillips | Jan 2013 | B2 |
8364806 | Short et al. | Jan 2013 | B2 |
8369274 | Sawai | Feb 2013 | B2 |
8370477 | Short et al. | Feb 2013 | B2 |
8370483 | Choong et al. | Feb 2013 | B2 |
8374090 | Morrill et al. | Feb 2013 | B2 |
8374102 | Luft et al. | Feb 2013 | B2 |
8374592 | Proctor, Jr. et al. | Feb 2013 | B2 |
8375128 | Tofighbakhsh et al. | Feb 2013 | B2 |
8375136 | Roman et al. | Feb 2013 | B2 |
8379847 | Bell et al. | Feb 2013 | B2 |
8380247 | Engstrom | Feb 2013 | B2 |
8380804 | Jain et al. | Feb 2013 | B2 |
8385199 | Coward et al. | Feb 2013 | B1 |
8385896 | Proctor, Jr. et al. | Feb 2013 | B2 |
8385964 | Haney | Feb 2013 | B2 |
8385975 | Forutanpour et al. | Feb 2013 | B2 |
8386386 | Zhu | Feb 2013 | B1 |
8391262 | Maki et al. | Mar 2013 | B2 |
8391834 | Raleigh | Mar 2013 | B2 |
8392982 | Harris et al. | Mar 2013 | B2 |
8396458 | Raleigh | Mar 2013 | B2 |
8396929 | Helfman et al. | Mar 2013 | B2 |
8401906 | Ruckart | Mar 2013 | B2 |
8401968 | Schattauer et al. | Mar 2013 | B1 |
8402165 | Deu-Ngoc et al. | Mar 2013 | B2 |
8402540 | Kapoor et al. | Mar 2013 | B2 |
8406427 | Chand et al. | Mar 2013 | B2 |
8406736 | Das et al. | Mar 2013 | B2 |
8406756 | Reeves et al. | Mar 2013 | B1 |
8407472 | Hao et al. | Mar 2013 | B2 |
8407763 | Weller et al. | Mar 2013 | B2 |
8411587 | Curtis et al. | Apr 2013 | B2 |
8411691 | Aggarwal | Apr 2013 | B2 |
8412798 | Wang | Apr 2013 | B1 |
8413245 | Kraemer et al. | Apr 2013 | B2 |
8418168 | Tyhurst et al. | Apr 2013 | B2 |
8422988 | Keshav | Apr 2013 | B1 |
8423016 | Buckley et al. | Apr 2013 | B2 |
8429403 | Moret et al. | Apr 2013 | B2 |
8437734 | Ray et al. | May 2013 | B2 |
8441955 | Wilkinson et al. | May 2013 | B2 |
8442015 | Behzad et al. | May 2013 | B2 |
8442507 | Duggal et al. | May 2013 | B2 |
8443390 | Lo et al. | May 2013 | B2 |
8446831 | Kwan et al. | May 2013 | B2 |
8447324 | Shuman et al. | May 2013 | B2 |
8447607 | Weider et al. | May 2013 | B2 |
8447980 | Godfrey et al. | May 2013 | B2 |
8448015 | Gerhart | May 2013 | B2 |
8452858 | Wu et al. | May 2013 | B2 |
8461958 | Saenz et al. | Jun 2013 | B2 |
8463194 | Erlenback et al. | Jun 2013 | B2 |
8463232 | Tuli et al. | Jun 2013 | B2 |
8468337 | Gaur et al. | Jun 2013 | B2 |
8472371 | Bari et al. | Jun 2013 | B1 |
8477778 | Lehmann, Jr. et al. | Jul 2013 | B2 |
8483135 | Cai et al. | Jul 2013 | B2 |
8483694 | Lewis et al. | Jul 2013 | B2 |
8484327 | Werner et al. | Jul 2013 | B2 |
8484568 | Rados et al. | Jul 2013 | B2 |
8488597 | Nie et al. | Jul 2013 | B2 |
8489110 | Frank et al. | Jul 2013 | B2 |
8489720 | Morford et al. | Jul 2013 | B1 |
8494559 | Malmi | Jul 2013 | B1 |
8495181 | Venkatraman et al. | Jul 2013 | B2 |
8495227 | Kaminsky et al. | Jul 2013 | B2 |
8495360 | Falk et al. | Jul 2013 | B2 |
8495700 | Shahbazi | Jul 2013 | B2 |
8495743 | Kraemer et al. | Jul 2013 | B2 |
8499087 | Hu | Jul 2013 | B2 |
RE44412 | Naqvi et al. | Aug 2013 | E |
8500533 | Lutnick et al. | Aug 2013 | B2 |
8503358 | Hanson et al. | Aug 2013 | B2 |
8503455 | Heikens | Aug 2013 | B2 |
8504032 | Lott et al. | Aug 2013 | B2 |
8504574 | Dvorak et al. | Aug 2013 | B2 |
8504687 | Maffione et al. | Aug 2013 | B2 |
8504690 | Shah et al. | Aug 2013 | B2 |
8504729 | Pezzutti | Aug 2013 | B2 |
8505073 | Taglienti et al. | Aug 2013 | B2 |
8509082 | Heinz et al. | Aug 2013 | B2 |
8510743 | Hackborn et al. | Aug 2013 | B2 |
8514927 | Sundararajan et al. | Aug 2013 | B2 |
8516552 | Raleigh | Aug 2013 | B2 |
8520589 | Bhatt et al. | Aug 2013 | B2 |
8520595 | Yadav et al. | Aug 2013 | B2 |
8521110 | Rofougaran | Aug 2013 | B2 |
8521775 | Poh et al. | Aug 2013 | B1 |
8522039 | Hyndman et al. | Aug 2013 | B2 |
8522249 | Beaule | Aug 2013 | B2 |
8522337 | Adusumilli et al. | Aug 2013 | B2 |
8523547 | Pekrul | Sep 2013 | B2 |
8526329 | Mahany et al. | Sep 2013 | B2 |
8526350 | Xue et al. | Sep 2013 | B2 |
8527013 | Guba et al. | Sep 2013 | B2 |
8527410 | Markki et al. | Sep 2013 | B2 |
8527662 | Biswas et al. | Sep 2013 | B2 |
8528068 | Weglein et al. | Sep 2013 | B1 |
8531954 | McNaughton et al. | Sep 2013 | B2 |
8531995 | Khan et al. | Sep 2013 | B2 |
8532610 | Manning Cassett et al. | Sep 2013 | B2 |
8533341 | Aguirre et al. | Sep 2013 | B2 |
8533775 | Alcorn et al. | Sep 2013 | B2 |
8535160 | Lutnick et al. | Sep 2013 | B2 |
8538394 | Zimmerman et al. | Sep 2013 | B2 |
8538421 | Brisebois et al. | Sep 2013 | B2 |
8538458 | Haney | Sep 2013 | B2 |
8539544 | Garimella et al. | Sep 2013 | B2 |
8539561 | Gupta et al. | Sep 2013 | B2 |
8543265 | Ekhaguere et al. | Sep 2013 | B2 |
8543814 | Laitinen et al. | Sep 2013 | B2 |
8544105 | Mclean et al. | Sep 2013 | B2 |
8548427 | Chow et al. | Oct 2013 | B2 |
8548428 | Raleigh | Oct 2013 | B2 |
8549173 | Wu et al. | Oct 2013 | B1 |
8554876 | Winsor | Oct 2013 | B2 |
8559369 | Barkan | Oct 2013 | B2 |
8561138 | Rothman et al. | Oct 2013 | B2 |
8565746 | Hoffman | Oct 2013 | B2 |
8566236 | Busch | Oct 2013 | B2 |
8571474 | Chavez et al. | Oct 2013 | B2 |
8571501 | Miller et al. | Oct 2013 | B2 |
8571598 | Valavi | Oct 2013 | B2 |
8571993 | Kocher et al. | Oct 2013 | B2 |
8572117 | Rappaport | Oct 2013 | B2 |
8572256 | Babbar | Oct 2013 | B2 |
8583499 | De Judicibus et al. | Nov 2013 | B2 |
8584226 | Kudla et al. | Nov 2013 | B2 |
8588240 | Ramankutty et al. | Nov 2013 | B2 |
8589541 | Raleigh | Nov 2013 | B2 |
8589955 | Roundtree et al. | Nov 2013 | B2 |
8594626 | Woodson et al. | Nov 2013 | B1 |
8594665 | Anschutz | Nov 2013 | B2 |
8595186 | Mandyam et al. | Nov 2013 | B1 |
8600895 | Felsher | Dec 2013 | B2 |
8601125 | Huang et al. | Dec 2013 | B2 |
8605691 | Soomro et al. | Dec 2013 | B2 |
8611919 | Bames, Jr. | Dec 2013 | B2 |
8615507 | Varadarajulu et al. | Dec 2013 | B2 |
8619735 | Montemurro et al. | Dec 2013 | B2 |
8620257 | Qiu et al. | Dec 2013 | B2 |
8620281 | Gosselin et al. | Dec 2013 | B2 |
8621056 | Coussemaeker et al. | Dec 2013 | B2 |
8630314 | York | Jan 2014 | B2 |
8631428 | Scott et al. | Jan 2014 | B2 |
8634425 | Gorti et al. | Jan 2014 | B2 |
8635164 | Rosenhaft et al. | Jan 2014 | B2 |
8635335 | Raleigh | Jan 2014 | B2 |
8639215 | McGregor et al. | Jan 2014 | B2 |
8644702 | Kalajan | Feb 2014 | B1 |
8644813 | Gailloux et al. | Feb 2014 | B1 |
8645518 | David | Feb 2014 | B2 |
8654952 | Wang et al. | Feb 2014 | B2 |
8655357 | Gazzard et al. | Feb 2014 | B1 |
8656472 | McMurtry et al. | Feb 2014 | B2 |
8660853 | Robb et al. | Feb 2014 | B2 |
8666395 | Silver | Mar 2014 | B2 |
8667542 | Bertz et al. | Mar 2014 | B1 |
8670334 | Keohane et al. | Mar 2014 | B2 |
8670752 | Fan et al. | Mar 2014 | B2 |
8675507 | Raleigh | Mar 2014 | B2 |
8675852 | Maes | Mar 2014 | B2 |
8676682 | Kalliola | Mar 2014 | B2 |
8676925 | Liu et al. | Mar 2014 | B1 |
8688671 | Ramer et al. | Apr 2014 | B2 |
8688784 | Zabawskyj et al. | Apr 2014 | B2 |
8693323 | McDysan | Apr 2014 | B1 |
8694772 | Kao et al. | Apr 2014 | B2 |
8700729 | Dua | Apr 2014 | B2 |
8701015 | Bonnat | Apr 2014 | B2 |
8705361 | Venkataraman et al. | Apr 2014 | B2 |
8706863 | Fadell | Apr 2014 | B2 |
8713535 | Malhotra et al. | Apr 2014 | B2 |
8713641 | Pagan et al. | Apr 2014 | B1 |
8719397 | Levi et al. | May 2014 | B2 |
8719423 | Wyld | May 2014 | B2 |
8724486 | Seto et al. | May 2014 | B2 |
8725700 | Rappaport | May 2014 | B2 |
8725899 | Short et al. | May 2014 | B2 |
8730842 | Collins et al. | May 2014 | B2 |
8731519 | Flynn et al. | May 2014 | B2 |
8732808 | Sewall et al. | May 2014 | B2 |
8739035 | Trethewey | May 2014 | B2 |
8744339 | Halfmann et al. | Jun 2014 | B2 |
8761711 | Grignani et al. | Jun 2014 | B2 |
8761809 | Faith et al. | Jun 2014 | B2 |
8775233 | Lybrook et al. | Jul 2014 | B1 |
8780857 | Balasubramanian et al. | Jul 2014 | B2 |
8787249 | Giaretta et al. | Jul 2014 | B2 |
8793304 | Lu et al. | Jul 2014 | B2 |
8798610 | Prakash et al. | Aug 2014 | B2 |
8804517 | Oerton | Aug 2014 | B2 |
8804695 | Branam | Aug 2014 | B2 |
8811338 | Jin et al. | Aug 2014 | B2 |
8811991 | Jain et al. | Aug 2014 | B2 |
8812525 | Taylor, III | Aug 2014 | B1 |
8818394 | Bienas et al. | Aug 2014 | B2 |
8819253 | Simeloff et al. | Aug 2014 | B2 |
8825109 | Montemurro et al. | Sep 2014 | B2 |
8826411 | Moen et al. | Sep 2014 | B2 |
8831561 | Sutaria et al. | Sep 2014 | B2 |
8837322 | Venkataramanan et al. | Sep 2014 | B2 |
8838686 | Getchius | Sep 2014 | B2 |
8838752 | Lor et al. | Sep 2014 | B2 |
8843849 | Neil et al. | Sep 2014 | B2 |
8845415 | Lutnick et al. | Sep 2014 | B2 |
8849262 | Desai et al. | Sep 2014 | B2 |
8849297 | Balasubramanian | Sep 2014 | B2 |
8855620 | Sievers et al. | Oct 2014 | B2 |
8856015 | Mesaros | Oct 2014 | B2 |
8862751 | Faccin et al. | Oct 2014 | B2 |
8863111 | Selitser et al. | Oct 2014 | B2 |
8868725 | Samba | Oct 2014 | B2 |
8868727 | Yumerefendi et al. | Oct 2014 | B2 |
8875042 | LeJeune et al. | Oct 2014 | B2 |
8880047 | Konicek et al. | Nov 2014 | B2 |
8891483 | Connelly et al. | Nov 2014 | B2 |
8898748 | Burks et al. | Nov 2014 | B2 |
8908516 | Tzamaloukas et al. | Dec 2014 | B2 |
8929374 | Tönsing et al. | Jan 2015 | B2 |
8930238 | Coffman et al. | Jan 2015 | B2 |
8943551 | Ganapathy et al. | Jan 2015 | B2 |
8948198 | Nee et al. | Feb 2015 | B2 |
8948726 | Smith et al. | Feb 2015 | B2 |
8949382 | Cornett et al. | Feb 2015 | B2 |
8949597 | Reeves et al. | Feb 2015 | B1 |
8955038 | Nicodemus et al. | Feb 2015 | B2 |
8966018 | Bugwadia et al. | Feb 2015 | B2 |
8971841 | Menezes et al. | Mar 2015 | B2 |
8971912 | Chou et al. | Mar 2015 | B2 |
8977284 | Reed | Mar 2015 | B2 |
8995952 | Baker et al. | Mar 2015 | B1 |
9002342 | Tenhunen et al. | Apr 2015 | B2 |
9008653 | Sparks et al. | Apr 2015 | B2 |
9014059 | Richardson et al. | Apr 2015 | B2 |
9014973 | Ruckart | Apr 2015 | B2 |
9015331 | Lai et al. | Apr 2015 | B2 |
9030934 | Shah et al. | May 2015 | B2 |
9032427 | Gallant et al. | May 2015 | B2 |
9049010 | Jueneman et al. | Jun 2015 | B2 |
9064275 | Lu et al. | Jun 2015 | B1 |
9105031 | Shen et al. | Aug 2015 | B2 |
9107053 | Davis et al. | Aug 2015 | B2 |
9111088 | Ghai et al. | Aug 2015 | B2 |
9135037 | Petrescu-Prahova et al. | Sep 2015 | B1 |
9137286 | Yuan | Sep 2015 | B1 |
9172553 | Dawes et al. | Oct 2015 | B2 |
9173090 | Tuchman et al. | Oct 2015 | B2 |
9177455 | Remer | Nov 2015 | B2 |
9183524 | Carter | Nov 2015 | B2 |
9225847 | Daymond et al. | Dec 2015 | B2 |
9252977 | Levi et al. | Feb 2016 | B2 |
9262370 | Hofstaedter et al. | Feb 2016 | B2 |
9282460 | Souissi | Mar 2016 | B2 |
9286469 | Kraemer et al. | Mar 2016 | B2 |
9286604 | Aabye et al. | Mar 2016 | B2 |
9288276 | Adamczyk et al. | Mar 2016 | B2 |
9313708 | Nam et al. | Apr 2016 | B2 |
9325737 | Gutowski et al. | Apr 2016 | B2 |
9326173 | Luft | Apr 2016 | B2 |
9344557 | Gruchala et al. | May 2016 | B2 |
9350842 | Swanburg et al. | May 2016 | B2 |
9363285 | Kitamura | Jun 2016 | B2 |
9367680 | Mahaffey et al. | Jun 2016 | B2 |
9402254 | Kneckt et al. | Jul 2016 | B2 |
9413546 | Meier et al. | Aug 2016 | B2 |
9418381 | Ahuja et al. | Aug 2016 | B2 |
9501803 | Bilac et al. | Nov 2016 | B2 |
9589117 | Ali et al. | Mar 2017 | B2 |
9609459 | Raleigh | Mar 2017 | B2 |
9609544 | Raleigh | Mar 2017 | B2 |
9615192 | Raleigh | Apr 2017 | B2 |
9634850 | Taft et al. | Apr 2017 | B2 |
9691082 | Burnett et al. | Jun 2017 | B1 |
9712476 | Boynton et al. | Jul 2017 | B2 |
9749899 | Raleigh | Aug 2017 | B2 |
9852426 | Bacastow | Dec 2017 | B2 |
9923790 | Patel et al. | Mar 2018 | B2 |
10034220 | Silver | Jul 2018 | B2 |
10064033 | Raleigh | Aug 2018 | B2 |
10171681 | Raleigh et al. | Jan 2019 | B2 |
10171990 | Raleigh et al. | Jan 2019 | B2 |
10237773 | Raleigh | Mar 2019 | B2 |
10285025 | Baker et al. | May 2019 | B1 |
10321515 | Shen et al. | Jun 2019 | B2 |
10395216 | Coffing | Aug 2019 | B2 |
10492102 | Raleigh et al. | Nov 2019 | B2 |
10521781 | Singfield | Dec 2019 | B1 |
10567930 | Silver | Feb 2020 | B2 |
10582375 | Raleigh | Mar 2020 | B2 |
10616818 | Silver | Apr 2020 | B2 |
20010048738 | Baniak et al. | Dec 2001 | A1 |
20010053694 | Igarashi et al. | Dec 2001 | A1 |
20020013844 | Garrett et al. | Jan 2002 | A1 |
20020022472 | Watler et al. | Feb 2002 | A1 |
20020022483 | Thompson et al. | Feb 2002 | A1 |
20020049074 | Eisinger et al. | Apr 2002 | A1 |
20020099848 | Lee | Jul 2002 | A1 |
20020116338 | Gonthier et al. | Aug 2002 | A1 |
20020120370 | Parupudi et al. | Aug 2002 | A1 |
20020120540 | Kende et al. | Aug 2002 | A1 |
20020131397 | Patel et al. | Sep 2002 | A1 |
20020131404 | Mehta et al. | Sep 2002 | A1 |
20020138599 | Dilman et al. | Sep 2002 | A1 |
20020138601 | Piponius et al. | Sep 2002 | A1 |
20020154751 | Thompson et al. | Oct 2002 | A1 |
20020161601 | Nauer et al. | Oct 2002 | A1 |
20020164983 | Raviv et al. | Nov 2002 | A1 |
20020176377 | Hamilton | Nov 2002 | A1 |
20020188732 | Buckman et al. | Dec 2002 | A1 |
20020191573 | Whitehill et al. | Dec 2002 | A1 |
20020199001 | Wenocur et al. | Dec 2002 | A1 |
20030004937 | Salmenkaita et al. | Jan 2003 | A1 |
20030005112 | Krautkremer | Jan 2003 | A1 |
20030013434 | Rosenberg et al. | Jan 2003 | A1 |
20030018524 | Fishman et al. | Jan 2003 | A1 |
20030028623 | Hennessey et al. | Feb 2003 | A1 |
20030046396 | Richter et al. | Mar 2003 | A1 |
20030050070 | Mashinsky et al. | Mar 2003 | A1 |
20030050837 | Kim | Mar 2003 | A1 |
20030084321 | Tarquini et al. | May 2003 | A1 |
20030088671 | Klinker et al. | May 2003 | A1 |
20030133408 | Cheng et al. | Jul 2003 | A1 |
20030134650 | Sundar et al. | Jul 2003 | A1 |
20030159030 | Evans | Aug 2003 | A1 |
20030161265 | Cao et al. | Aug 2003 | A1 |
20030171112 | Lupper et al. | Sep 2003 | A1 |
20030182420 | Jones et al. | Sep 2003 | A1 |
20030182435 | Redlich et al. | Sep 2003 | A1 |
20030184793 | Pineau | Oct 2003 | A1 |
20030188006 | Bard | Oct 2003 | A1 |
20030188117 | Yoshino et al. | Oct 2003 | A1 |
20030220984 | Jones et al. | Nov 2003 | A1 |
20030224781 | Milford et al. | Dec 2003 | A1 |
20030229900 | Reisman | Dec 2003 | A1 |
20030233332 | Keeler et al. | Dec 2003 | A1 |
20030236745 | Hartsell et al. | Dec 2003 | A1 |
20040019539 | Raman et al. | Jan 2004 | A1 |
20040019564 | Goldthwaite et al. | Jan 2004 | A1 |
20040021697 | Beaton et al. | Feb 2004 | A1 |
20040024756 | Rickard | Feb 2004 | A1 |
20040030705 | Bowman-Amuah | Feb 2004 | A1 |
20040039792 | Nakanishi | Feb 2004 | A1 |
20040044623 | Wake et al. | Mar 2004 | A1 |
20040047358 | Chen et al. | Mar 2004 | A1 |
20040054779 | Takeshima et al. | Mar 2004 | A1 |
20040073672 | Fascenda | Apr 2004 | A1 |
20040082346 | Skytt et al. | Apr 2004 | A1 |
20040098715 | Aghera et al. | May 2004 | A1 |
20040102182 | Reith et al. | May 2004 | A1 |
20040103193 | Pandya et al. | May 2004 | A1 |
20040107360 | Herrmann et al. | Jun 2004 | A1 |
20040116140 | Babbar et al. | Jun 2004 | A1 |
20040127200 | Shaw et al. | Jul 2004 | A1 |
20040127208 | Nair et al. | Jul 2004 | A1 |
20040127256 | Goldthwaite et al. | Jul 2004 | A1 |
20040132427 | Lee et al. | Jul 2004 | A1 |
20040133668 | Nicholas, III | Jul 2004 | A1 |
20040137890 | Kalke | Jul 2004 | A1 |
20040165596 | Garcia et al. | Aug 2004 | A1 |
20040167958 | Stewart et al. | Aug 2004 | A1 |
20040168052 | Clisham et al. | Aug 2004 | A1 |
20040170191 | Guo et al. | Sep 2004 | A1 |
20040176104 | Arcens | Sep 2004 | A1 |
20040198331 | Coward et al. | Oct 2004 | A1 |
20040203755 | Brunet et al. | Oct 2004 | A1 |
20040203833 | Rathunde et al. | Oct 2004 | A1 |
20040225561 | Hertzberg et al. | Nov 2004 | A1 |
20040225898 | Frost et al. | Nov 2004 | A1 |
20040236547 | Rappaport et al. | Nov 2004 | A1 |
20040243680 | Mayer | Dec 2004 | A1 |
20040243992 | Gustafson et al. | Dec 2004 | A1 |
20040249918 | Sunshine | Dec 2004 | A1 |
20040255145 | Chow | Dec 2004 | A1 |
20040259534 | Chaudhari et al. | Dec 2004 | A1 |
20040260766 | Barros et al. | Dec 2004 | A1 |
20040267872 | Serdy et al. | Dec 2004 | A1 |
20050007993 | Chambers et al. | Jan 2005 | A1 |
20050009499 | Koster | Jan 2005 | A1 |
20050021995 | Lal et al. | Jan 2005 | A1 |
20050041617 | Huotari et al. | Feb 2005 | A1 |
20050048950 | Morper | Mar 2005 | A1 |
20050055291 | Bevente et al. | Mar 2005 | A1 |
20050055309 | Williams et al. | Mar 2005 | A1 |
20050055595 | Frazer et al. | Mar 2005 | A1 |
20050060266 | Demello et al. | Mar 2005 | A1 |
20050060525 | Schwartz et al. | Mar 2005 | A1 |
20050075115 | Corneille et al. | Apr 2005 | A1 |
20050079863 | Macaluso | Apr 2005 | A1 |
20050091505 | Riley et al. | Apr 2005 | A1 |
20050096024 | Bicker et al. | May 2005 | A1 |
20050097516 | Donnelly et al. | May 2005 | A1 |
20050107091 | Vannithamby et al. | May 2005 | A1 |
20050108075 | Douglis et al. | May 2005 | A1 |
20050111463 | Leung et al. | May 2005 | A1 |
20050128967 | Scobbie | Jun 2005 | A1 |
20050135264 | Popoff et al. | Jun 2005 | A1 |
20050163320 | Brown et al. | Jul 2005 | A1 |
20050166043 | Zhang et al. | Jul 2005 | A1 |
20050183143 | Anderholm et al. | Aug 2005 | A1 |
20050186948 | Gallagher et al. | Aug 2005 | A1 |
20050198377 | Ferguson et al. | Sep 2005 | A1 |
20050216421 | Barry et al. | Sep 2005 | A1 |
20050228985 | Ylikoski et al. | Oct 2005 | A1 |
20050238046 | Hassan et al. | Oct 2005 | A1 |
20050239447 | Holzman et al. | Oct 2005 | A1 |
20050245241 | Durand et al. | Nov 2005 | A1 |
20050246282 | Naslund et al. | Nov 2005 | A1 |
20050250508 | Guo et al. | Nov 2005 | A1 |
20050250536 | Deng et al. | Nov 2005 | A1 |
20050254435 | Moakley et al. | Nov 2005 | A1 |
20050266825 | Clayton | Dec 2005 | A1 |
20050266880 | Gupta | Dec 2005 | A1 |
20060014519 | Marsh et al. | Jan 2006 | A1 |
20060019632 | Cunningham et al. | Jan 2006 | A1 |
20060020787 | Choyi et al. | Jan 2006 | A1 |
20060026679 | Zakas | Feb 2006 | A1 |
20060030306 | Kuhn | Feb 2006 | A1 |
20060034256 | Addagatla et al. | Feb 2006 | A1 |
20060035631 | White et al. | Feb 2006 | A1 |
20060040642 | Boris et al. | Feb 2006 | A1 |
20060045245 | Aaron et al. | Mar 2006 | A1 |
20060048223 | Lee et al. | Mar 2006 | A1 |
20060068796 | Millen et al. | Mar 2006 | A1 |
20060072451 | Ross | Apr 2006 | A1 |
20060072550 | Davis et al. | Apr 2006 | A1 |
20060072646 | Feher | Apr 2006 | A1 |
20060075506 | Sanda et al. | Apr 2006 | A1 |
20060085543 | Hrastar et al. | Apr 2006 | A1 |
20060095517 | O'Connor et al. | May 2006 | A1 |
20060098627 | Karaoguz et al. | May 2006 | A1 |
20060099970 | Morgan et al. | May 2006 | A1 |
20060101507 | Camenisch | May 2006 | A1 |
20060112016 | Ishibashi | May 2006 | A1 |
20060114821 | Willey et al. | Jun 2006 | A1 |
20060114832 | Hamilton et al. | Jun 2006 | A1 |
20060126562 | Liu | Jun 2006 | A1 |
20060135144 | Jothipragasam | Jun 2006 | A1 |
20060136882 | Noonan et al. | Jun 2006 | A1 |
20060143066 | Calabria | Jun 2006 | A1 |
20060143098 | Lazaridis | Jun 2006 | A1 |
20060156398 | Ross et al. | Jul 2006 | A1 |
20060160536 | Chou | Jul 2006 | A1 |
20060165060 | Dua | Jul 2006 | A1 |
20060168128 | Sistla et al. | Jul 2006 | A1 |
20060173959 | Mckelvie et al. | Aug 2006 | A1 |
20060174035 | Tufail | Aug 2006 | A1 |
20060178917 | Merriam et al. | Aug 2006 | A1 |
20060178918 | Mikurak | Aug 2006 | A1 |
20060178943 | Rollinson et al. | Aug 2006 | A1 |
20060182137 | Zhou et al. | Aug 2006 | A1 |
20060183462 | Kolehmainen | Aug 2006 | A1 |
20060190314 | Hernandez | Aug 2006 | A1 |
20060190987 | Ohta et al. | Aug 2006 | A1 |
20060193280 | Lee et al. | Aug 2006 | A1 |
20060199608 | Dunn et al. | Sep 2006 | A1 |
20060200663 | Thornton | Sep 2006 | A1 |
20060206709 | Labrou et al. | Sep 2006 | A1 |
20060206904 | Watkins et al. | Sep 2006 | A1 |
20060218395 | Maes | Sep 2006 | A1 |
20060221829 | Holmstrom et al. | Oct 2006 | A1 |
20060233108 | Krishnan | Oct 2006 | A1 |
20060233166 | Bou-Diab et al. | Oct 2006 | A1 |
20060236095 | Smith et al. | Oct 2006 | A1 |
20060242685 | Heard et al. | Oct 2006 | A1 |
20060258341 | Miller et al. | Nov 2006 | A1 |
20060277590 | Limont et al. | Dec 2006 | A1 |
20060291419 | McConnell et al. | Dec 2006 | A1 |
20060291477 | Croak et al. | Dec 2006 | A1 |
20070005795 | Gonzalez | Jan 2007 | A1 |
20070019670 | Falardeau | Jan 2007 | A1 |
20070022289 | Alt et al. | Jan 2007 | A1 |
20070025301 | Petersson et al. | Feb 2007 | A1 |
20070033194 | Srinivas et al. | Feb 2007 | A1 |
20070033197 | Scherzer et al. | Feb 2007 | A1 |
20070036312 | Cai et al. | Feb 2007 | A1 |
20070038763 | Oestvall | Feb 2007 | A1 |
20070055694 | Ruge et al. | Mar 2007 | A1 |
20070060200 | Boris et al. | Mar 2007 | A1 |
20070061243 | Ramer et al. | Mar 2007 | A1 |
20070061800 | Cheng et al. | Mar 2007 | A1 |
20070061878 | Hagiu et al. | Mar 2007 | A1 |
20070073899 | Judge et al. | Mar 2007 | A1 |
20070076616 | Ngo et al. | Apr 2007 | A1 |
20070093243 | Kapadekar et al. | Apr 2007 | A1 |
20070100981 | Adamczyk et al. | May 2007 | A1 |
20070101426 | Lee et al. | May 2007 | A1 |
20070104126 | Calhoun et al. | May 2007 | A1 |
20070109983 | Shankar et al. | May 2007 | A1 |
20070111740 | Wandel | May 2007 | A1 |
20070124077 | Hedlund | May 2007 | A1 |
20070130283 | Klein et al. | Jun 2007 | A1 |
20070130315 | Friend et al. | Jun 2007 | A1 |
20070140113 | Gemelos | Jun 2007 | A1 |
20070140145 | Kumar et al. | Jun 2007 | A1 |
20070140275 | Bowman et al. | Jun 2007 | A1 |
20070143824 | Shahbazi | Jun 2007 | A1 |
20070147317 | Smith et al. | Jun 2007 | A1 |
20070147324 | McGary | Jun 2007 | A1 |
20070155365 | Kim et al. | Jul 2007 | A1 |
20070165630 | Rasanen et al. | Jul 2007 | A1 |
20070168499 | Chu | Jul 2007 | A1 |
20070171856 | Bruce et al. | Jul 2007 | A1 |
20070174490 | Choi et al. | Jul 2007 | A1 |
20070191006 | Carpenter | Aug 2007 | A1 |
20070192460 | Choi et al. | Aug 2007 | A1 |
20070198656 | Mazzaferri et al. | Aug 2007 | A1 |
20070201502 | Abramson | Aug 2007 | A1 |
20070213054 | Han | Sep 2007 | A1 |
20070220251 | Rosenberg et al. | Sep 2007 | A1 |
20070226225 | Yiu et al. | Sep 2007 | A1 |
20070226775 | Andreasen et al. | Sep 2007 | A1 |
20070234402 | Khosravi et al. | Oct 2007 | A1 |
20070242619 | Murakami et al. | Oct 2007 | A1 |
20070242659 | Cantu et al. | Oct 2007 | A1 |
20070243862 | Coskun et al. | Oct 2007 | A1 |
20070244965 | Dowling | Oct 2007 | A1 |
20070248100 | Zuberi et al. | Oct 2007 | A1 |
20070254646 | Sokondar | Nov 2007 | A1 |
20070254675 | Zorlu Ozer et al. | Nov 2007 | A1 |
20070255769 | Agrawal et al. | Nov 2007 | A1 |
20070255797 | Dunn et al. | Nov 2007 | A1 |
20070255848 | Sewall et al. | Nov 2007 | A1 |
20070257767 | Beeson | Nov 2007 | A1 |
20070259656 | Jeong | Nov 2007 | A1 |
20070259673 | Willars et al. | Nov 2007 | A1 |
20070263558 | Salomone | Nov 2007 | A1 |
20070266422 | Germano et al. | Nov 2007 | A1 |
20070274327 | Kaarela et al. | Nov 2007 | A1 |
20070280453 | Kelley | Dec 2007 | A1 |
20070282896 | Wydroug et al. | Dec 2007 | A1 |
20070293191 | Mir et al. | Dec 2007 | A1 |
20070294395 | Strub et al. | Dec 2007 | A1 |
20070294410 | Pandya et al. | Dec 2007 | A1 |
20070297378 | Poyhonen et al. | Dec 2007 | A1 |
20070298764 | Clayton | Dec 2007 | A1 |
20070299965 | Nieh et al. | Dec 2007 | A1 |
20070300252 | Acharya et al. | Dec 2007 | A1 |
20080005285 | Robinson et al. | Jan 2008 | A1 |
20080005561 | Brown et al. | Jan 2008 | A1 |
20080010379 | Zhao | Jan 2008 | A1 |
20080010452 | Holtzman et al. | Jan 2008 | A1 |
20080018494 | Waite et al. | Jan 2008 | A1 |
20080022354 | Grewal et al. | Jan 2008 | A1 |
20080025230 | Patel et al. | Jan 2008 | A1 |
20080032715 | Jia et al. | Feb 2008 | A1 |
20080034063 | Yee | Feb 2008 | A1 |
20080034419 | Mullick et al. | Feb 2008 | A1 |
20080039102 | Sewall et al. | Feb 2008 | A1 |
20080049630 | Kozisek et al. | Feb 2008 | A1 |
20080050715 | Golczewski et al. | Feb 2008 | A1 |
20080051076 | O'Shaughnessy et al. | Feb 2008 | A1 |
20080052387 | Heinz et al. | Feb 2008 | A1 |
20080056273 | Pelletier et al. | Mar 2008 | A1 |
20080057894 | Aleksic et al. | Mar 2008 | A1 |
20080059474 | Lim | Mar 2008 | A1 |
20080059743 | Bychkov et al. | Mar 2008 | A1 |
20080060066 | Wynn et al. | Mar 2008 | A1 |
20080062900 | Rao | Mar 2008 | A1 |
20080064367 | Nath et al. | Mar 2008 | A1 |
20080066149 | Lim | Mar 2008 | A1 |
20080066150 | Lim | Mar 2008 | A1 |
20080066181 | Haveson et al. | Mar 2008 | A1 |
20080070550 | Hose | Mar 2008 | A1 |
20080077705 | Li et al. | Mar 2008 | A1 |
20080080457 | Cole | Apr 2008 | A1 |
20080081606 | Cole | Apr 2008 | A1 |
20080082643 | Storrie et al. | Apr 2008 | A1 |
20080083013 | Soliman et al. | Apr 2008 | A1 |
20080085707 | Fadell | Apr 2008 | A1 |
20080089295 | Keeler et al. | Apr 2008 | A1 |
20080089303 | Wirtanen et al. | Apr 2008 | A1 |
20080095339 | Elliott et al. | Apr 2008 | A1 |
20080096559 | Phillips et al. | Apr 2008 | A1 |
20080098062 | Balia | Apr 2008 | A1 |
20080109679 | Wright et al. | May 2008 | A1 |
20080120129 | Seubert et al. | May 2008 | A1 |
20080120668 | Yau | May 2008 | A1 |
20080120688 | Qiu et al. | May 2008 | A1 |
20080125079 | O'Neil et al. | May 2008 | A1 |
20080126287 | Cox et al. | May 2008 | A1 |
20080127304 | Ginter et al. | May 2008 | A1 |
20080130534 | Tomioka | Jun 2008 | A1 |
20080130656 | Kim et al. | Jun 2008 | A1 |
20080132201 | Karlberg | Jun 2008 | A1 |
20080132268 | Choi-Grogan et al. | Jun 2008 | A1 |
20080134330 | Kapoor et al. | Jun 2008 | A1 |
20080139210 | Gisby et al. | Jun 2008 | A1 |
20080147454 | Walker et al. | Jun 2008 | A1 |
20080160958 | Abichandani et al. | Jul 2008 | A1 |
20080161041 | Pernu | Jul 2008 | A1 |
20080162637 | Adamczyk et al. | Jul 2008 | A1 |
20080162704 | Poplett et al. | Jul 2008 | A1 |
20080164304 | Narasimhan et al. | Jul 2008 | A1 |
20080166993 | Gautier et al. | Jul 2008 | A1 |
20080167027 | Gautier et al. | Jul 2008 | A1 |
20080167033 | Beckers | Jul 2008 | A1 |
20080168275 | DeAtley et al. | Jul 2008 | A1 |
20080168523 | Ansari et al. | Jul 2008 | A1 |
20080177998 | Apsangi et al. | Jul 2008 | A1 |
20080178300 | Brown et al. | Jul 2008 | A1 |
20080183811 | Kotras et al. | Jul 2008 | A1 |
20080183812 | Paul et al. | Jul 2008 | A1 |
20080184127 | Rafey et al. | Jul 2008 | A1 |
20080189760 | Rosenberg et al. | Aug 2008 | A1 |
20080201266 | Chua et al. | Aug 2008 | A1 |
20080207167 | Bugenhagen | Aug 2008 | A1 |
20080212470 | Castaneda et al. | Sep 2008 | A1 |
20080212751 | Chung | Sep 2008 | A1 |
20080219268 | Dennison | Sep 2008 | A1 |
20080221951 | Stanforth et al. | Sep 2008 | A1 |
20080222692 | Andersson et al. | Sep 2008 | A1 |
20080225748 | Khemani et al. | Sep 2008 | A1 |
20080229385 | Feder et al. | Sep 2008 | A1 |
20080229388 | Maes | Sep 2008 | A1 |
20080235511 | O'Brien et al. | Sep 2008 | A1 |
20080240373 | Wilhelm | Oct 2008 | A1 |
20080242290 | Bhatia et al. | Oct 2008 | A1 |
20080250053 | Aaltonen et al. | Oct 2008 | A1 |
20080256593 | Vinberg et al. | Oct 2008 | A1 |
20080259924 | Gooch et al. | Oct 2008 | A1 |
20080262798 | Kim et al. | Oct 2008 | A1 |
20080263348 | Zaltsman et al. | Oct 2008 | A1 |
20080268813 | Maes | Oct 2008 | A1 |
20080270212 | Blight et al. | Oct 2008 | A1 |
20080279216 | Sharif-Ahmadi et al. | Nov 2008 | A1 |
20080282319 | Fontijn et al. | Nov 2008 | A1 |
20080293395 | Mathews et al. | Nov 2008 | A1 |
20080298230 | Luft et al. | Dec 2008 | A1 |
20080305793 | Gallagher et al. | Dec 2008 | A1 |
20080311885 | Dawson et al. | Dec 2008 | A1 |
20080313315 | Karaoguz et al. | Dec 2008 | A1 |
20080313730 | Iftimie et al. | Dec 2008 | A1 |
20080316923 | Fedders et al. | Dec 2008 | A1 |
20080316983 | Daigle | Dec 2008 | A1 |
20080318547 | Ballou et al. | Dec 2008 | A1 |
20080318550 | DeAtley | Dec 2008 | A1 |
20080319879 | Carroll et al. | Dec 2008 | A1 |
20080320497 | Tarkoma et al. | Dec 2008 | A1 |
20090005000 | Baker et al. | Jan 2009 | A1 |
20090005005 | Forstall et al. | Jan 2009 | A1 |
20090006116 | Baker et al. | Jan 2009 | A1 |
20090006200 | Baker et al. | Jan 2009 | A1 |
20090006229 | Sweeney et al. | Jan 2009 | A1 |
20090013157 | Beaule | Jan 2009 | A1 |
20090016310 | Rasal | Jan 2009 | A1 |
20090036111 | Danford et al. | Feb 2009 | A1 |
20090042536 | Bernard et al. | Feb 2009 | A1 |
20090044185 | Krivopaltsev | Feb 2009 | A1 |
20090046707 | Smires et al. | Feb 2009 | A1 |
20090046723 | Rahman et al. | Feb 2009 | A1 |
20090047989 | Harmon et al. | Feb 2009 | A1 |
20090048913 | Shenfield et al. | Feb 2009 | A1 |
20090049156 | Aronsson et al. | Feb 2009 | A1 |
20090049518 | Roman et al. | Feb 2009 | A1 |
20090054030 | Golds | Feb 2009 | A1 |
20090054061 | Dawson et al. | Feb 2009 | A1 |
20090065571 | Jain | Mar 2009 | A1 |
20090067372 | Shah et al. | Mar 2009 | A1 |
20090068984 | Burnett | Mar 2009 | A1 |
20090070379 | Rappaport | Mar 2009 | A1 |
20090077622 | Baum et al. | Mar 2009 | A1 |
20090079699 | Sun | Mar 2009 | A1 |
20090109898 | Adams et al. | Apr 2009 | A1 |
20090113514 | Hu | Apr 2009 | A1 |
20090125619 | Antani | May 2009 | A1 |
20090132860 | Liu et al. | May 2009 | A1 |
20090149154 | Bhasin et al. | Jun 2009 | A1 |
20090157792 | Fiatal | Jun 2009 | A1 |
20090163173 | Williams | Jun 2009 | A1 |
20090172077 | Roxburgh et al. | Jul 2009 | A1 |
20090180391 | Petersen et al. | Jul 2009 | A1 |
20090181662 | Fleischman et al. | Jul 2009 | A1 |
20090197585 | Aaron | Aug 2009 | A1 |
20090197612 | Kiiskinen | Aug 2009 | A1 |
20090203352 | Fordon et al. | Aug 2009 | A1 |
20090217065 | Araujo, Jr. | Aug 2009 | A1 |
20090217364 | Salmela et al. | Aug 2009 | A1 |
20090219170 | Clark et al. | Sep 2009 | A1 |
20090248883 | Suryanarayana et al. | Oct 2009 | A1 |
20090254857 | Romine et al. | Oct 2009 | A1 |
20090257379 | Robinson et al. | Oct 2009 | A1 |
20090261783 | Gonzales et al. | Oct 2009 | A1 |
20090271514 | Thomas et al. | Oct 2009 | A1 |
20090282127 | Leblanc et al. | Nov 2009 | A1 |
20090286507 | O'Neil et al. | Nov 2009 | A1 |
20090287921 | Zhu et al. | Nov 2009 | A1 |
20090288140 | Huber et al. | Nov 2009 | A1 |
20090291665 | Gaskarth et al. | Nov 2009 | A1 |
20090299857 | Brubaker | Dec 2009 | A1 |
20090307696 | Vals et al. | Dec 2009 | A1 |
20090307746 | Di et al. | Dec 2009 | A1 |
20090315735 | Bhavani et al. | Dec 2009 | A1 |
20090320110 | Nicolson et al. | Dec 2009 | A1 |
20100010873 | Moreau | Jan 2010 | A1 |
20100017506 | Fadell | Jan 2010 | A1 |
20100020822 | Zerillo et al. | Jan 2010 | A1 |
20100027469 | Gurajala et al. | Feb 2010 | A1 |
20100027559 | Lin et al. | Feb 2010 | A1 |
20100030890 | Dutta et al. | Feb 2010 | A1 |
20100041364 | Lott et al. | Feb 2010 | A1 |
20100041365 | Lott et al. | Feb 2010 | A1 |
20100042675 | Fujii | Feb 2010 | A1 |
20100043068 | Varadhan et al. | Feb 2010 | A1 |
20100069074 | Kodialam et al. | Mar 2010 | A1 |
20100071053 | Ansari et al. | Mar 2010 | A1 |
20100075666 | Garner | Mar 2010 | A1 |
20100077035 | Li et al. | Mar 2010 | A1 |
20100080202 | Hanson | Apr 2010 | A1 |
20100082431 | Ramer et al. | Apr 2010 | A1 |
20100088387 | Calamera | Apr 2010 | A1 |
20100103820 | Fuller et al. | Apr 2010 | A1 |
20100113020 | Subramanian et al. | May 2010 | A1 |
20100121744 | Belz et al. | May 2010 | A1 |
20100131584 | Johnson | May 2010 | A1 |
20100142478 | Forssell et al. | Jun 2010 | A1 |
20100144310 | Bedingfield | Jun 2010 | A1 |
20100151866 | Karpov et al. | Jun 2010 | A1 |
20100153781 | Hanna | Jun 2010 | A1 |
20100167696 | Smith et al. | Jul 2010 | A1 |
20100188975 | Raleigh | Jul 2010 | A1 |
20100188990 | Raleigh | Jul 2010 | A1 |
20100188992 | Raleigh | Jul 2010 | A1 |
20100188994 | Raleigh | Jul 2010 | A1 |
20100190469 | Vanderveen et al. | Jul 2010 | A1 |
20100191576 | Raleigh | Jul 2010 | A1 |
20100191612 | Raleigh | Jul 2010 | A1 |
20100191846 | Raleigh | Jul 2010 | A1 |
20100192170 | Raleigh | Jul 2010 | A1 |
20100192212 | Raleigh | Jul 2010 | A1 |
20100195503 | Raleigh | Aug 2010 | A1 |
20100197268 | Raleigh | Aug 2010 | A1 |
20100198698 | Raleigh et al. | Aug 2010 | A1 |
20100198939 | Raleigh | Aug 2010 | A1 |
20100227632 | Bell et al. | Sep 2010 | A1 |
20100235329 | Koren et al. | Sep 2010 | A1 |
20100241544 | Benson et al. | Sep 2010 | A1 |
20100248719 | Scholaert | Sep 2010 | A1 |
20100284327 | Miklos | Nov 2010 | A1 |
20100284388 | Fantini et al. | Nov 2010 | A1 |
20100287599 | He et al. | Nov 2010 | A1 |
20100311402 | Srinivasan et al. | Dec 2010 | A1 |
20100318652 | Samba | Dec 2010 | A1 |
20100325420 | Kanekar | Dec 2010 | A1 |
20110004917 | Saisa et al. | Jan 2011 | A1 |
20110013569 | Scherzer et al. | Jan 2011 | A1 |
20110019574 | Malomsoky et al. | Jan 2011 | A1 |
20110071854 | Medeiros et al. | Mar 2011 | A1 |
20110081881 | Baker et al. | Apr 2011 | A1 |
20110082790 | Baker et al. | Apr 2011 | A1 |
20110110309 | Bennett | May 2011 | A1 |
20110126141 | King et al. | May 2011 | A1 |
20110145920 | Mahaffey et al. | Jun 2011 | A1 |
20110159818 | Scherzer et al. | Jun 2011 | A1 |
20110173678 | Kaippallimalil et al. | Jul 2011 | A1 |
20110177811 | Heckman et al. | Jul 2011 | A1 |
20110182220 | Black et al. | Jul 2011 | A1 |
20110185202 | Black et al. | Jul 2011 | A1 |
20110195700 | Kukuchka et al. | Aug 2011 | A1 |
20110238545 | Fanaian et al. | Sep 2011 | A1 |
20110241624 | Park et al. | Oct 2011 | A1 |
20110244837 | Murata et al. | Oct 2011 | A1 |
20110249668 | Milligan et al. | Oct 2011 | A1 |
20110252430 | Chapman et al. | Oct 2011 | A1 |
20110264923 | Kocher et al. | Oct 2011 | A1 |
20110277019 | Pritchard, Jr. | Nov 2011 | A1 |
20120020296 | Scherzer et al. | Jan 2012 | A1 |
20120029718 | Davis | Feb 2012 | A1 |
20120108225 | Luna et al. | May 2012 | A1 |
20120144025 | Melander et al. | Jun 2012 | A1 |
20120155296 | Kashanian | Jun 2012 | A1 |
20120166364 | Ahmad et al. | Jun 2012 | A1 |
20120166604 | Fortier et al. | Jun 2012 | A1 |
20120196644 | Scherzer et al. | Aug 2012 | A1 |
20120238287 | Scherzer | Sep 2012 | A1 |
20120330792 | Kashanian | Dec 2012 | A1 |
20130024914 | Ahmed et al. | Jan 2013 | A1 |
20130029653 | Baker et al. | Jan 2013 | A1 |
20130030960 | Kashanian | Jan 2013 | A1 |
20130058274 | Scherzer et al. | Mar 2013 | A1 |
20130065555 | Baker et al. | Mar 2013 | A1 |
20130072177 | Ross et al. | Mar 2013 | A1 |
20130084835 | Scherzer et al. | Apr 2013 | A1 |
20130095787 | Kashanian | Apr 2013 | A1 |
20130117140 | Kashanian | May 2013 | A1 |
20130144789 | Aaltonen et al. | Jun 2013 | A1 |
20130225151 | King et al. | Aug 2013 | A1 |
20130326356 | Zheng et al. | Dec 2013 | A9 |
20140073291 | Hildner et al. | Mar 2014 | A1 |
20140241342 | Constantinof | Aug 2014 | A1 |
20150181628 | Haverinen et al. | Jun 2015 | A1 |
Number | Date | Country |
---|---|---|
2688553 | Dec 2008 | CA |
1310401 | Aug 2001 | CN |
1345154 | Apr 2002 | CN |
1508734 | Jun 2004 | CN |
1538730 | Oct 2004 | CN |
1567818 | Jan 2005 | CN |
101035308 | Mar 2006 | CN |
1801829 | Jul 2006 | CN |
1802839 | Jul 2006 | CN |
1889777 | Jul 2006 | CN |
101155343 | Sep 2006 | CN |
1867024 | Nov 2006 | CN |
1878160 | Dec 2006 | CN |
1937511 | Mar 2007 | CN |
101123553 | Sep 2007 | CN |
101080055 | Nov 2007 | CN |
101115248 | Jan 2008 | CN |
101127988 | Feb 2008 | CN |
101183958 | May 2008 | CN |
101335666 | Dec 2008 | CN |
101341764 | Jan 2009 | CN |
101815275 | Aug 2010 | CN |
1098490 | May 2001 | EP |
1289326 | Mar 2003 | EP |
1463238 | Sep 2004 | EP |
1503548 | Feb 2005 | EP |
1545114 | Jun 2005 | EP |
1739518 | Jan 2007 | EP |
1772988 | Apr 2007 | EP |
1850575 | Oct 2007 | EP |
1887732 | Feb 2008 | EP |
1942698 | Jul 2008 | EP |
1978772 | Oct 2008 | EP |
2007065 | Dec 2008 | EP |
2026514 | Feb 2009 | EP |
2466831 | Jun 2012 | EP |
2154602 | Jun 2017 | EP |
3148713 | Mar 2001 | JP |
2005339247 | Dec 2005 | JP |
2006041989 | Feb 2006 | JP |
2006155263 | Jun 2006 | JP |
2006197137 | Jul 2006 | JP |
2006344007 | Dec 2006 | JP |
2007318354 | Dec 2007 | JP |
2008301121 | Dec 2008 | JP |
2009111919 | May 2009 | JP |
2009212707 | Sep 2009 | JP |
2009218773 | Sep 2009 | JP |
2009232107 | Oct 2009 | JP |
20040053858 | Jun 2004 | KR |
1998058505 | Dec 1998 | WO |
1999027723 | Jun 1999 | WO |
1999065185 | Dec 1999 | WO |
0208863 | Jan 2002 | WO |
2002045315 | Jun 2002 | WO |
2002067616 | Aug 2002 | WO |
2002093877 | Nov 2002 | WO |
2003014891 | Feb 2003 | WO |
2003017063 | Feb 2003 | WO |
2003017065 | Feb 2003 | WO |
2003058880 | Jul 2003 | WO |
2004028070 | Apr 2004 | WO |
2004064306 | Jul 2004 | WO |
2004077797 | Sep 2004 | WO |
2004095753 | Nov 2004 | WO |
2005008995 | Jan 2005 | WO |
2005053335 | Jun 2005 | WO |
2005083934 | Sep 2005 | WO |
2006004467 | Jan 2006 | WO |
2006004784 | Jan 2006 | WO |
2006012610 | Feb 2006 | WO |
2006050758 | May 2006 | WO |
2006073837 | Jul 2006 | WO |
2006077481 | Jul 2006 | WO |
2006093961 | Sep 2006 | WO |
2006120558 | Nov 2006 | WO |
2006130960 | Dec 2006 | WO |
2007001833 | Jan 2007 | WO |
2007014630 | Feb 2007 | WO |
2007018363 | Feb 2007 | WO |
2007053848 | May 2007 | WO |
2007068288 | Jun 2007 | WO |
2007069245 | Jun 2007 | WO |
2007097786 | Aug 2007 | WO |
2007107701 | Sep 2007 | WO |
2007120310 | Oct 2007 | WO |
2007124279 | Nov 2007 | WO |
2007126352 | Nov 2007 | WO |
2007129180 | Nov 2007 | WO |
2007133844 | Nov 2007 | WO |
2008017837 | Feb 2008 | WO |
2008051379 | May 2008 | WO |
2008066419 | Jun 2008 | WO |
2008080139 | Jul 2008 | WO |
2008080430 | Jul 2008 | WO |
2008099802 | Aug 2008 | WO |
2009008817 | Jan 2009 | WO |
2009091295 | Jul 2009 | WO |
2010088413 | Aug 2010 | WO |
2010128391 | Nov 2010 | WO |
2010128391 | Jan 2011 | WO |
2011002450 | Jan 2011 | WO |
2011149532 | Dec 2011 | WO |
Entry |
---|
“Ads and movies on the run,” the Gold Coast Bulletin, Southport, QId, Jan. 29, 2008. |
“ASA/PIX: Allow Split Tunneling for VPN Clients on the ASA Configuration Example,” Document ID 70917, Jan. 10, 2008. |
“Communication Concepts for Mobile Agent Systems,” by Joachim Baumann et al.; Inst. of Parallel and Distributed High-Performance Systems, Univ. of Stuttgart, Germany, pp. 123-135, 1997. |
“End to End QoS Solution for Real-time Multimedia Application;” Computer Engineering and Applications, 2007, 43 (4):155-159, by Tan Zu-guo, Wang Wen-juan; Information and Science School, Zhanjian Normal College, Zhan jiang, Guangdong 524048, China. |
“Jentro Technologies launches Zenlet platform to accelerate location-based content delivery to mobile devices,” The Mobile Internet, Boston, MA, Feb. 2008. |
“The Construction of Intelligent Residential District in Use of Cable Television Network,” Shandong Science, vol. 13, No. 2, Jun. 2000. |
3rd Generation Partnership Project, “Technical Specification Group Core Network and Terminals; Access Network Discovery and Selection Function (ANDSF) Management Object (MO),” Release 9, Document No. 3GPP TS 24.312, V9.1.0, Mar. 2010. |
3rd Generation Partnership Project, “Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) Enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Access,” Release 8, Document No. 3GPP TS 23.401, V8.4.0, Dec. 2008. |
3rd Generation Partnership Project, “Technical Specification Group Services and System Aspects; Policy and Charging Control Architecture,” Release 8, Document No. 3GPP TS 23.203, V8.4.0, Dec. 2008. |
3rd Generation Partnership Project; “Technical Specification Group Services and System Aspects; IP Flow Mobility and seamless WLAN offlload; Stage 2,” Release 10, Document No. 3GPP TS 23.261, V1.0.0, Mar. 2010. |
Accuris Networks, “The Business Value of Mobile Data Offload—a White Paper”, 2010. |
Ahmed et al., “A Context-Aware Vertical Handover Decision Algorithm for Multimode Mobile Terminals and Its Performance,” BenQ Mobile, Munich Germany; University of Klagenfurt, Klagenfurt, Austria; 2006. |
Ahmed et al., “Multi Access Data Network Connectivity and IP Flow Mobility in Evolved Packet System (EPS),” 2010 IEEE. |
Alonistioti et al., “Intelligent Architectures Enabling Flexible Service Provision and Adaptability,” 2002. |
Amazon Technologies, Inc., “Kindle™ User's Guide,” 3rd Edition, Copyright 2004-2009. |
Android Cupcake excerpts, The Android Open Source Project, Feb. 10, 2009. |
Anton, B. et al., “Best Current Practices for Wireless Internet Service Provider (WISP) Roaming”; Release Date Feb. 2003, Version 1.0; Wi-Fi Alliance—Wireless ISP Roaming (WISPr). |
Blackberry Mobile Data System, version 4.1, Technical Overview, 2006. |
Chandrasekhar et al., “Femtocell Networks: A Survey,” Jun. 28, 2008. |
Chaouchi et al., “Policy Based Networking in the Integration Effort of 4G Networks and Services,” 2004 IEEE. |
Cisco Systems, Inc., “Cisco Mobile Exchange (CMX) Solution Guide: Chapter 2—Overview of GSM, GPRS, and UMTS,” Nov. 4, 2008. |
Client Guide for Symantec Endpoint Protection and Symantec Network Access Control, 2007. |
Dikaiakos et al., “A Distributed Middleware Infrastructure for Personalized Services,” Nov. 24, 2003. |
Dixon et al., Triple Play Digital Services: Comcast and Verizon (Digital Phone, Television, and Internet), Aug. 2007. |
Ehnert, “Small application to monitor IP trafic on a Blackberry—1.01.03”, Mar. 27, 2008; http://www.ehnert.net/MiniMoni/. |
European Commission, “Data Roaming Tariffs—Transparency Measures,” obtained from EUROPA—Europe's Information Society Thematic Portal website, Jun. 24, 2011: “http://ec.europa.eu/information_society/activities/roaming/data/measures/index_en.htm.” |
Farooq et al., “An IEEE 802.16 WiMax Module for the NS-3 Simulator,” Mar. 2-6, 2009. |
Fujitsu, “Server Push Technology Survey and Bidirectional Communication in HTTP Browser,” Jan. 9, 2008 (JP). |
Han et al., “Information Collection Services for Qos-Aware Mobile Applications,” 2005. |
Hartmann et al., “Agent-Based Banking Transactions & Information Retrieval—What About Performance Issues?” 1999. |
Hewlett-Packard Development Company, LP, “IP Multimedia Services Charging,” white paper, Jan. 2006. |
Hossain et al., “Gain-Based Selection of Ambient Media Services in Pervasive Environments,” Mobile Networks and Applications. Oct. 3, 2008. |
Jing et al., “Client-Server Computing in Mobile Environments,” GTE Labs. Inc., Purdue University, ACM Computing Surveys, vol. 31, No. 2, Jun. 1999. |
Kasper et al., “Subscriber Authentication in mobile cellular Networks with virtual software SIM Credentials using Trusted Computing,” Fraunhofer-Institute for Secure Information Technology SIT, Darmstadt, Germany; ICACT 2008. |
Kassar et al., “An overview of vertical handover decision strategies in heterogeneous wireless networks,” ScienceDirect, University Pierre & Marie Curie, Paris, France, Jun. 5, 2007. |
Kim, “Free wireless a high-wire act; MetroFi needs to draw enough ads to make service add profits,” San Francisco Chronicle, Aug. 21, 2006. |
Knight et al., “Layer 2 and 3 Virtual Private Networks: Taxonomy, Technology, and Standarization Efforts,” IEEE Communications Magazine, Jun. 2004. |
Koutsopoulou et al., “Charging, Accounting and Billing Management Schemes in Mobile Telecommunication Networks and the Internet,” IEEE Communications Surveys & Tutorials, First Quarter 2004, vol. 6, No. 1. |
Koutsopoulou et al., “Middleware Platform for the Support of Charging Reconfiguration Actions,” 2005. |
Kuntze et al., “Trustworthy content push,” Fraunhofer-Institute for Secure Information Technology SIT; Germany; WCNC 2007 proceedings, IEEE. |
Kyriakakos et al., “Ubiquitous Service Provision in Next Generation Mobile Networks,” Proceedings of the 13th IST Mobile and Wireless Communications Summit, Lyon, France, Jun. 2004. |
Li, Yu, “Dedicated E-Reading Device: The State of the Art and the Challenges,” Scroll, vol. 1, No. 1, 2008. |
Loopt User Guide, metroPCS, Jul. 17, 2008. |
Muntermann et al., “Potentials und Sicherheitsanforderungen mobiler Finanzinformationsdienste und deren Systeminfrastrukturen,” Chair of Mobile Commerce & Multilateral Security, Goethe Univ. Frankfurt, 2004. |
NetLimiter Lite 4.0.19.0; http://www.heise.de/download/netlimiter-lite-3617703.html from vol. 14/2007. |
Nilsson et al., “A Novel MAC Scheme for Solving the QoS Parameter Adjustment Problem in IEEE802.11e EDCA,” Feb. 2006. |
Nuzman et al., “A compund model for TCP connection arrivals for LAN and WAN applications,” Oct. 22, 2002. |
Open Mobile Alliance (OMA), Push Architecture, Candidate Version 2.2; Oct. 2, 2007; OMA-AD-PUSH-V2_2-20071002-C. |
Oppliger, Rolf, “Internet Security: Firewalls and Bey,” Communications of the ACM, May 1997, vol. 40. No. 5. |
Quintana, David, “Mobile Multitasking,” Apr. 14, 2010. |
Rao et al., “Evolution of Mobile Location-Based Services,” Communication of the ACM, Dec. 2003. |
Richtel, “Cellphone consumerism; If even a debit card is too slow, now you have a new way to act on impulse: [National Edition],” National Post, Canada, Oct. 2, 2007. |
Rivadeneyra et al., “A communication architecture to access data services through GSM,” San Sebastian, Spain, 1998. |
Roy et al., “Energy Management in Mobile Devices with the Cinder Operating System”, Stanford University, MIT CSAIL, Jun. 3, 2010. |
Ruckus Wireless—White Paper; “Smarter Wi-Fi for Mobile Operator Infrastructures” 2010. |
Sabat, “The evolving mobile wireless value chain and market structure,” Nov. 2002. |
Sadeh et al., “Understanding and Capturing People's Privacy Policies in a Mobile Social Networking Application,” ISR School of Computer Science, Carnegie Mellon University, 2007. |
Schiller et al., “Location-Based Services,” The Morgan Kaufmann Series in Data Management Systems, 2004. |
Steglich, Stephan, “I-Centric User Interaction,” Nov. 21, 2003. |
Sun et al., “Towards Connectivity Management Adaptability: Context Awareness in Policy Representation and End-to-end Evaluation Algorithm,” Dept. of Electrical and Information Engineering, Univ. of Oulu, Finland, 2004. |
Thurston, Richard, “WISPr 2.0 Boosts Roaming Between 3G and Wi-Fi”; Jun. 23, 2010; Web page from zdnet.com; Zdnet.com/wispr-2-0-boosts-roaming-between-3g-and-wi-fi-3040089325/. |
Van Eijk, et al., “GigaMobile, Agent Technology for Designing Personalized Mobile Service Brokerage,” Jul. 1, 2002. |
VerizonWireless.com news, “Verizon Wireless Adds to Portfolio of Cosumer-Friendly Tools With Introduction of Usage Controls, Usage Controls and Chaperone 2.0 Offer Parents Full Family Security Solution,” Aug. 18, 2008. |
Windows7 Power Management, published Apr. 2009. |
Wireless Broadband Alliance, “WISPr 2.0, Apr. 8, 2010”; Doc. Ref. No. WBA/RMNVISPr, Version 01.00. |
Zhu et al., “A Survey of Quality of Service in IEEE 802.11 Networks,” IEEE Wireless Communications, Aug. 2004. |
Byrd, “Open Secure Wireless,” May 5, 2010. |
Droid Wall 1.3.7 description Apr. 28, 2010; obtained from https://www.freewarelovers.com/android/apps/droid-wall. |
Sharkey, “Coding for Life—Battery Life That Is,” May 27, 2009. |
Number | Date | Country | |
---|---|---|---|
20190327624 A1 | Oct 2019 | US |
Number | Date | Country | |
---|---|---|---|
61472606 | Apr 2011 | US | |
61435564 | Jan 2011 | US | |
61422565 | Dec 2010 | US | |
61422572 | Dec 2010 | US | |
61422574 | Dec 2010 | US | |
61420727 | Dec 2010 | US | |
61418509 | Dec 2010 | US | |
61418507 | Dec 2010 | US | |
61407358 | Oct 2010 | US | |
61389547 | Oct 2010 | US | |
61387243 | Sep 2010 | US | |
61387247 | Sep 2010 | US | |
61385020 | Sep 2010 | US | |
61384456 | Sep 2010 | US | |
61381162 | Sep 2010 | US | |
61381159 | Sep 2010 | US | |
61348022 | May 2010 | US | |
61264126 | Nov 2009 | US | |
61264120 | Nov 2009 | US | |
61252151 | Oct 2009 | US | |
61252153 | Oct 2009 | US | |
61237753 | Aug 2009 | US | |
61275208 | Aug 2009 | US | |
61270353 | Jul 2009 | US | |
61207739 | Feb 2009 | US | |
61207393 | Feb 2009 | US | |
61206944 | Feb 2009 | US | |
61206354 | Jan 2009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13134028 | May 2011 | US |
Child | 14082040 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15977766 | May 2018 | US |
Child | 16272114 | US | |
Parent | 15681726 | Aug 2017 | US |
Child | 15977766 | US | |
Parent | 14687715 | Apr 2015 | US |
Child | 15681726 | US | |
Parent | 14082040 | Nov 2013 | US |
Child | 14687715 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12695021 | Jan 2010 | US |
Child | 13134028 | US | |
Parent | 13134005 | May 2011 | US |
Child | 12695021 | US | |
Parent | 12380780 | Mar 2009 | US |
Child | 12695021 | US | |
Parent | 12380780 | Mar 2009 | US |
Child | 13134005 | US | |
Parent | 12380778 | Mar 2009 | US |
Child | 12380780 | US | |
Parent | 12695019 | Jan 2010 | US |
Child | 13134028 | US | |
Parent | 12695020 | Jan 2010 | US |
Child | 12695019 | US | |
Parent | 12694445 | Jan 2010 | US |
Child | 12695020 | US | |
Parent | 12694451 | Jan 2010 | US |
Child | 12694445 | US | |
Parent | 12694455 | Jan 2010 | US |
Child | 12694451 | US | |
Parent | 12695980 | Jan 2010 | US |
Child | 12694455 | US |