`
`Attorney Docket No. RALEP031+
`
`DEVICE ASSISTED SERVICES FOR PROTECTING NETWORK
`
`CAPACITY
`
`By Inventor(s):
`
`Gregory G. Raleigh
`Woodside, CA
`A Citizen of the United States
`
`Ali Raissinia
`Monte Sereno, CA
`A Citizen of the United States
`
`James Lavine
`Marin, CA
`A Citizen of the United States
`
`Assignee:
`
`Headwater Partners I LLC, a Delawarelimited liability company
`
`VAN PELT, YI & JAMES LLP
`10050 N. Foothill Blvd., Suite 200
`Cupertino, CA 95014
`Telephone (408) 973-2585
`
`
`
`DEVICE ASSISTED SERVICES FOR PROTECTING NETWORK
`
`CAPACITY
`
`BACKGROUND OF THE INVENTION
`
`[0001]
`
`With the advent of mass market digital communications, applications and content
`
`distribution, many access networks such as wireless networks, cable networks and DSL (Digital
`
`Subscriber Line) networks are pressed for user capacity, with, for example, EVDO (Evolution-
`
`Data Optimized), HSPA (High Speed Packet Access), LTE (Long Term Evolution), WiMax
`
`(Worldwide Interoperability for Microwave Access), DOCSIS, DSL, and Wi-Fi (Wireless
`
`Fidelity) becoming user capacity constrained. In the wireless case, although network capacity
`
`will increase with new higher capacity wireless radio access technologies, such as MIMO
`
`(Multiple-Input Multiple-Output), and with more frequency spectrum andcell splitting being
`
`deployedin the future, these capacity gainsare likely to be less than whatis required to meet
`
`growing digital networking demand.
`
`[0002]
`
`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 providerprofits.
`
`Attorney Docket No. RALEP031+
`
`1
`
`PATENT
`
`
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0003]
`
`Various embodiments of the invention are disclosed in the following detailed
`
`description and the accompanying drawings.
`
`[0004]
`
`Figure 1 illustrates a functional diagram of a network architecture for providing
`
`quality of service (QoS) for device assisted services (DAS) and/or for providing DASfor
`
`protecting network capacity in accordance with some embodiments.
`
`[0005]
`
`Figure 2 illustrates another functional diagram of another network architecture
`
`for providing quality of service (QoS) for device assisted services (DAS) and/or for providing
`
`DASfor protecting network capacity in accordance with some embodiments.
`
`[0006]
`
`Figure 3 illustrates a functional diagram of an architecture including a device
`
`based service processor and a service controller for providing quality of service (QoS) for device
`
`assisted services (DAS)and/or for providing DASfor protecting network capacity in accordance
`
`with some embodiments.
`
`[0007]
`
`Figures 4A through 4Cillustrates a functional diagram for providing quality of
`
`service (QoS) for device assisted services (DAS) in accordance with some embodiments.
`
`[0008]
`
`Figure 5 illustrates a functional diagram for generating a QoS activity map for
`
`quality of service (QoS) for device assisted services (DAS) in accordance with some
`
`embodiments.
`
`[0009]
`
`Figure 6 illustrates a functional diagram for quality of service (QoS) for device
`
`assisted services for an end to end coordinated QoS service channel control in accordance with
`
`some embodiments.
`
`[0010]
`
`Figure 7 illustrates a flow diagram for quality of service (QoS) for device assisted
`
`services (DAS) in accordance with some embodiments.
`
`[0011]
`
`Figures 8A through 8C eachillustrate another flow diagram for quality of
`
`service (QoS) for device assisted services (DAS) in accordance with some embodiments.
`
`Attorney Docket No. RALEP031+
`
`2
`
`PATENT
`
`
`
`[0012]
`
`Figure 9 illustrates another flow diagram for quality of service (QoS) for device
`
`assisted services (DAS) in accordance with some embodiments.
`
`[0013]
`
`Figure 10 illustrates another flow diagram for quality of service (QoS) for device
`
`assisted services (DAS) in accordance with some embodiments.
`
`[0014]
`
`Figure 11 illustrates another flow diagram for quality of service (QoS) for device
`
`assisted services (DAS) in accordance with some embodiments.
`
`[0015]
`
`Figure 12 illustrates a device stack for providing various service usage
`
`measurement techniques in accordance with some embodiments.
`
`[0016]
`
`Figure 13 illustrates another device stack for providing various service usage
`
`measurement techniques in accordance with some embodiments.
`
`[0017]
`
`Figure 14 illustrates a flow diagram for device assisted services (DAS) for
`
`protecting network capacity in accordance with some embodiments.
`
`[0018]
`
`Figure 15 illustrates another flow diagram for device assisted services (DAS) for
`
`protecting network capacity in accordance with some embodiments.
`
`[0019]
`
`Figure 16 illustrates another flow diagram for device assisted services (DAS) for
`
`protecting network capacity in accordance with some embodiments.
`
`[0020]
`
`Figure 17 illustrates another flow diagram for device assisted services (DAS) for
`
`protecting network capacity in accordance with some embodiments.
`
`[0021]
`
`Figure 18 illustrates another flow diagram for device assisted services (DAS) for
`
`protecting network capacity in accordance with some embodiments.
`
`[0022]
`
`Figure 19 illustrates another flow diagram for device assisted services (DAS) for
`
`protecting network capacity in accordance with some embodiments.
`
`[0023]
`
`Figure 20 illustrates another flow diagram for device assisted services (DAS) for
`
`protecting network capacity in accordance with some embodiments.
`
`Attorney Docket No. RALEP031+
`
`3
`
`PATENT
`
`
`
`[0024]
`
`Figure 21 illustrates another flow diagram for device assisted services (DAS) for
`
`protecting network capacity in accordance with some embodiments.
`
`[0025]
`
`Figure 22 illustrates another flow diagram for device assisted services (DAS) for
`
`protecting network capacity in accordance with some embodiments.
`
`[0026]
`
`Figure 23 illustrates a network capacity controlled services priority level chart for
`
`device assisted services (DAS) for protecting network capacity in accordance with some
`
`embodiments.
`
`Attorney Docket No. RALEP031+
`
`4
`
`PATENT
`
`
`
`DETAILED DESCRIPTION
`
`[0027]
`
`The invention can be implemented in numerousways, 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 processoror a
`
`memory described as being configured to perform a task may be implemented as a general
`
`componentthat 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.
`
`[0028]
`
`A detailed description of one or more embodiments of the invention is provided
`
`below along with accompanyingfigures 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 ofthe invention is limited only by the claims and the invention
`
`encompasses numerousalternatives, 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 someorall of these specific details. For the purpose of
`
`clarity, technical material that is knownin the technicalfields related to the invention has not
`
`been described in detail so that the invention is not unnecessarily obscured.
`
`[0029]
`
`Asthe network capacity gains are less than whatis 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
`
`Attorney Docket No. RALEP031+
`
`5
`
`PATENT
`
`
`
`carriers have indicated that a relatively small number of users on such devices demanda
`
`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 datatraffic.
`
`[0030]
`
`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 networkavailability; the ability to deliver connectionsto all devices, users and/or
`
`applications seeking connections and enabled for service on the network; network access attempt
`
`successrate; the transmission speed experienced by one or more devices, users or applications;
`
`the average transmission speed experiencedbyall 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 timingjitter for a
`
`transmission; the time variation in transmission speed for one or more connections; the ability of
`
`the network to deliver various requested/neededlevels 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 measuredacrossall devices,
`
`users, and/or applications); the ability of the network to share or distribute a performance
`
`measure (e.g., the performance measureslisted above) uniformly or fairly across multiple
`
`devices, users, and/or applicationsthat all have the same service quality class or the same service
`
`plan performance parameters.
`
`[0031]
`
`For example, if there is a limited amount of shared bandwidthfor a set of user
`
`devices(e.g., a set of devices on a wireless network, such as a given basestation 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/orall devices allow all applications to indiscriminately access or attempt to access
`
`network resourcesor transmit/receivetraffic, then the network can generally become overloaded.
`
`Asa result, a subset of users/devices or in some cases mostorall users/devices obtain poor
`
`network performance. As another example, if one or more devices forming a subset of devices
`
`Attorney Docket No. RALEP031+
`
`6
`
`PATENT
`
`
`
`on the network allow multiple and/orall 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 mostor all users/devices obtain poor
`
`network performance.
`
`[0032]
`
`Traditionally, mobile devices typically have specialized designsthat are
`
`optimized to preserve network capacity and protect network resources from being overtaxed.
`
`For example, wireless devices that browse the Internet often use specialized protocols such as
`
`WAPanddata traffic compression or low resolution techniques rather than standard HTTP
`
`protocols andtraffic used in wired Internet devices.
`
`[0033]
`
`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 consumingdesign,testing, and certification processes.
`
`These processesin 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.
`
`[0034]
`
`Device OEMshaverecently created wireless devices that are designed morelike
`
`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 wantto
`
`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 processfor
`
`bringing new devices onto their network, in which the process does not requireall of the
`
`specialized design and certification described above. These and variousother factors are driving
`
`a growing need and trend for less complex and time consuming wireless device design and
`
`certification processes.
`
`[0035]
`
`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,
`
`Attorney Docket No. RALEP031+
`
`7
`
`PATENT
`
`
`
`applications and markets, there is a growing demandto 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.
`
`[0036]
`
`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
`
`connectionsto the Internet has led to popular Internet services and applicationsthat 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 frequencyofinefficient wireless network accesses
`
`continue to rise, which can reduce network capacity sometimesto 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 moreintelligent bandwidth usage techniques. These
`
`factors generally result in less carrier control of device design, which posesa threat to longer
`
`term network capacity and performancepreservation as the volume of devices with less
`
`optimized wireless designs continues to grow.
`
`[0037]
`
`There are many network performance and user performance factors that are
`
`impacted bythe efficiency of the network, including, for example, overall network congestion;
`
`the access network performance experienced by one or more groupsofusers, 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. Undera relatively
`
`low capacity demand ofa 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 somewhatproportionally (e.g.,
`
`aggregate traffic delivered by the network may be roughly proportional to the peak available
`
`Attorney Docket No. RALEP031+
`
`8
`
`PATENT
`
`
`
`networktraffic) 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
`
`groupsof users, devices, applications, network service sources, communication protocols, and/or
`
`operating system functions.
`
`[0038]
`
`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 consequencesand 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), HTMLprotocols, 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, backgroundservice protocols, software update protocols, and/or various
`
`other network communication protocols. Thus, is it important to preserve/protect network
`
`capacity.
`
`Attorney Docket No. RALEP031+
`
`9
`
`PATENT
`
`
`
`[0039]
`
`It is also important to control the numberoftransactions 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 resourcesthat
`
`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,
`
`resourcesthat play a part in network discovery, gateway or router resources, data session
`
`reservation or establishmentresources(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 becomerelatively large as various network resources
`
`become increasingly taxed dueto either limited transaction processing capability or limited
`
`traffic bandwidth for one or more of the network resourcesthat participate in establishing,
`
`servicing, conducting, maintaining, and/or closing the necessary network service connections
`
`and/or information exchanges required to conducta 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
`
`PPPsessions 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 sometimesreferred 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 demandin 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
`
`somecases, the resource may fall behind transaction demandin a less well controlled manner
`
`(e.g., the network resource may become overwhelmedsuchthat its processing rate not only falls
`
`below aggregate transaction demand,but the transaction rate processing capability decreases
`
`Attorney Docket No. RALEP031+
`
`10
`
`PATENT
`
`
`
`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.
`
`[0040]
`
`Asanother example, in any type of random access bandwidth reservation
`
`protocol, MAC protocol, or bandwidth delivery protocol, in a network without proper
`
`managementand/or control of traffic access reservations and/or transmissions, as the network
`
`demandincreases there may be morecollisions between reservation requests, traffic
`
`transmissions, application demands, network service source demands, communication protocol
`
`demands, and/or operating system function demandscausing a decreasing network efficiency
`
`that can degrade user, device, application and/or network service performance so that
`
`performancefalls 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
`
`performancefalls 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 becomeinefficient if one or more devices, applications, network
`
`service sources, operating system functions, and/or communication protocols havea relatively
`
`high rate of network resource access attempts, network accesses or data transmissions for small
`
`transmission payloads (e.g., minimum MACreservation factors, minimum security overhead
`
`factors, minimum QoS reservation factors, minimum time responses for establishing a base
`
`station connection, minimum time responsesfor 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.
`
`[0041]
`
`Another example of device service activity behavior that can have an impact on
`
`network performanceis the way the device, device subsystem, and/or modem subsystem power
`
`cycling or transitions from one powersave state to another. For example, establishing a basic
`
`connection from a device to a wireless base station consumesbase station resources for a period
`
`Attorney Docket No. RALEP031+
`
`11
`
`PATENT
`
`
`
`of time and in some cases can also consumeother network resources such as AAA, HLR, HA,
`
`gateway,billing, and/or charging gateway resources.
`
`Ifa 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 powersave state, then each time the device enters powersave state
`
`and then exits power save state network resources are consumed, sometimesfor time periods
`
`measured on the order of seconds or in extreme cases even minutes. If such a device has an
`
`aggressive powersave algorithm that enters powersave state after a short idle period, then the
`
`device behavior can consumea 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 oncethe base station connectionis established (e.g., establishing a PPP session between
`
`the device and a homeagent (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
`
`powersavestate cycling or frequently terminates the data session for other reasons.
`
`[0042]
`
`Another example of device service activity behavior that can impact network
`
`performanceis applications that maintain persistent network communication that generates a
`
`relatively high frequency of network data packets. Some applications havepersistent signaling
`
`that falls into this category. Specific examples include frequent device signaling sequencesto
`
`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
`
`conductother 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 whenthe useris 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.
`
`[0043]
`
`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 andsignaling, frequent
`
`Attorney Docket No. RALEP031+
`
`12
`
`PATENT
`
`
`
`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 behaviorreporting,
`
`background email downloads, content subscription service updates and downloads(e.g.,
`
`music/video downloads, newsfeeds, etc.), text/voice/video chat clients, virus updates, peer to
`
`peer networking applications, inefficient network access sequences during frequent power
`
`cycling or powersave state cycling, large downloadsor other high bandwidth accesses, and/or
`
`greedy application programsthat 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 theart.
`
`[0044]
`
`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 frequenttraffic resulting from network resource requests, network data
`
`accesses or other network interaction can also degrade network capacity, network performance,
`
`and/or network resource whetheror not the aggregate bandwidth demand as measured by the
`
`total data throughputis 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.
`
`[0045]
`
`Smart phone andsimilar devices are exacerbating the problem by making
`
`frequent queries of the wireless network as such devices move amongcell sites to while in
`
`transit, for example, push email, access social networking tools, and/or conduct other repetitive
`
`actions. While datatraffic 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 preservebattery life, the smart
`
`phonetypically moves into an idle mode. When the user pushes another message secondslater,
`
`the device has to set up a signaling path again, and even whenthe signaling resourceis 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 spendinga lot of its resources trying to process the signaling soit
`
`Attorney Docket No. RALEP031+
`
`13
`
`PATENT
`
`
`
`cannot perform other tasks, such as allocate additional resources for data network usage, and
`
`such inefficiencies exacerbates the data network capacity crunch and droppedcalls on such
`
`wireless networks.
`
`[0046]
`
`One approach used by smart phone vendors to address this problem and save
`
`battery life on their devices is to implementa 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.
`
`[0047]
`
`Networkcarriers 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 processandsufficient investment is neededto alleviate this
`
`growing capacity crunch. Purely centralized network solutions with no assistance from a device
`
`based software agent (or service processor) can haveseveral limitations. For example, for some
`
`device applications, OS functions or other service usageactivities, if the activity is blocked
`
`somewherein the network behind the base station after over the air (OTA) spectrum bandwidth
`
`is consumedto open or begin to open a communication socket, then there canstill 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 activ