Mobile devices, such as smart phones and netbooks are prone to make application network calls, even when not needed. Often this occurs as applications hosted on mobile devices make network calls such as checks, updates, and functions over the network. The increasing frequency of these network calls by an increasing number of applications generates significant signaling load that harms the network. Also, if a mobile device makes use of a data plan based on the volume of data transmitted and received over the network, then the application network calls constitute a charge against that data plan. Furthermore, on mobile devices, radio activity has a relatively high power draw. If a mobile device is powered by battery, the application network calls will reduce the battery lifetime between charges.
However, there are a number of scenarios where a mobile device performs an application network call that would not have resulted in a degraded user experience if the application network call had not been done at all. Such a network call would constitute an unnecessary charge against the user's data plan and an unnecessary draw against the user's battery. Also, the network call would unnecessarily consume resources of the network, such as radio frequency (RF) spectrum.
The detailed description is set forth with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items or features.
This disclosure describes, in part, application controllers implemented at a telecommunication device and at a network proxy device to perform signaling reduction actions on uplink and downlink traffic, respectively. The signaling reduction actions conserve user and device resources, such as elements of a subscription plan and battery life, as well as network resources, such as RF spectrum. Example signaling reduction actions include buffering a packet for later transmission, discarding a packet, bundling a packet with one or more other packets, requesting that an application or application server wait for a time period before transmitting further packets, padding a packet to increase the size of the packet, modifying content associated with the packet (e.g., requesting that an application or application server perform compression), or triggering a radio of the telecommunication device into an active or dormant mode.
In various embodiments, the telecommunication device and network proxy device each receive or retrieve signaling reduction rules from a network operator or service provider. These signaling reduction rules are utilized by the application controllers in determining signaling reduction actions. The signaling reduction rules may be provided a single time, provided incrementally, or may be provided and then updated at intervals. The signaling reduction rules may specify one or more signaling reduction actions associated with an application or category and may, in some embodiments, associate actions with at least one or device information, network information, or user preferences. If provided by the network operator, the network operator may take into account both telecommunication device conditions and network conditions in generating and updating the signaling reduction rules.
In determining which signaling reduction action or actions to perform, the application controllers may utilize both signaling reduction rules and at least one of telecommunication device information, network information, or user preferences. The telecommunication device information may include at least one of a battery power state, an indication of whether a telecommunication display screen is on or off, or an indication of whether a telecommunication device radio is in an active mode or a dormant mode. The network information may include at least one of network congestion information, a radio channel condition, a network latency, or information associated with a cell in which the telecommunication device is located. User preferences may include a preference for application updates occurring at a certain frequency. In some embodiments, the application controllers of the telecommunication device and the network proxy device may exchange at least one of device information, network information, or user preferences with each other. In other embodiments, the application controller of the network proxy device may receive at least one of device information, network information, or user preferences from a radio interface layer (RIL) probe of the telecommunication device.
In various embodiments, the application controller of the telecommunication device may receive packets from applications of the telecommunication device and may, in response, determine application identifiers for those packets. The application controller of the telecommunication device may then utilize the application identifiers to retrieve signaling reduction rules associated with the application identifiers. An application identifier may include one or more of an internet protocol (IP) address, a communication protocol, a source port, a destination port, an application name, a signature, or a website name. In some embodiments, determining the signaling reduction rules may include mapping application identifiers to categories and categories to signaling reduction rules. The application controller of the telecommunication device may then also determine at least one of telecommunication device information, network information, or user preferences. Based on the determined signaling reduction rules and, optionally, the at least one of telecommunication device information, network information, or user preferences, the application controller of the telecommunication device performs signaling reduction actions.
The application controller of the telecommunication device may be part of the operating system of the telecommunication device or may be a layer between the applications and operating system or between the operating system and the RIL.
In some embodiments, the application controller of the network proxy device may receive a packet from an application server and may, in response, determine an application identifier for the packet. The application controller of the network proxy device may then utilize the application identifier to retrieve a signaling reduction rule associated with the application identifier. An application identifier may include one or more of an internet protocol (IP) address, a communication protocol, a source port, a destination port, an application name, a signature, or a website name. In some embodiments, determining the signaling reduction rule may include mapping the application identifier to a category and the category to a signaling reduction rule. The application controller of the network proxy device may then also determine at least one of telecommunication device information, network information, or user preferences. Based on the determined signaling reduction rule and, optionally, the at least one of telecommunication device information, network information, or user preferences, the application controller of the network proxy device performs one or more signaling reduction actions.
The signaling reduction actions may reduce or improve the transmission of packets 106 over a telecommunication network 120 to remote recipients, such as applications servers 122. The application servers 122 may be connected to the telecommunication network 120 by a network proxy device 124 of the telecommunication network 120 and by a public network, such as the Internet 126. Because packets from the application servers 112 may also cause significant traffic to the telecommunication device 102, thereby straining network resources, and consumption of the telecommunication device's battery charge, the network proxy device 124 may also be configured with an application controller 128 to perform signaling reductions actions associated with transmission of packets from the application servers 122 to the telecommunication device 102. These signaling reduction actions may be determined based on signaling reduction rules 130 and based on at least one of device information, network information, or user preferences 132. And like the application controller 104, the application controller 128 may include a buffer 134. Also, as shown in
In various embodiments, the telecommunication device 102 may be any sort device capable of cellular or wireless network communication, such as a cellular phone, a tablet computer, a personal digital assistant (PDA), a personal computer (PC), a laptop computer, a media center, a work station, etc. The telecommunication device 102 may be associated with a subscription to telecommunication services of a network operator of the telecommunication network 120. An example telecommunication device 102 is illustrated in
The applications 108 may be any sort of network applications, such as video call clients, voice call clients, network browsers, social media clients, messaging clients, or media streaming clients. Such applications may send and receive both signaling and data in the form of packets, such as packets 106. These packets 106 may specify any or all of an IP address of a packet destination, a communication protocol, a source port of the telecommunication device 102, a destination port of the packet destination, an application name, a signature, or a website name. The applications 108 may also receive packets from a remote device, such as an application server 122. In some embodiments, the applications 108 may expose or otherwise make available any of device information, network information, or user preferences 112.
In some embodiments, the operating system 118 may be any sort of telecommunication device operating system, such as an iOS®, an Android® operating system, a Windows® operating system, or a Unix-based operating system. The operating system 118 may also include the application controller 104 as, for example, a modification of a kernel of the operating system 118. In some embodiments, the operating system 118 may expose or otherwise make available any of device information, network information, or user preferences 112.
The RIL 116 may be an RIL of a network stack and may service as an interface to a radio of the telecommunication device 102. The RIL 116 may support a number of radio bearers for different packet flows, applications 108, or categories of applications 108. The radio bearers of RIL 116 may further receive packets 106, either from the operating system 118 or from the application controller 104, and may transmit the packets 106 over the telecommunication network 120 via the radio of the telecommunication device 102. The radio bearers may also receive inbound packets associated with their respective packet flows or applications 108 and may provide those inbound packets to the applications 108. In some embodiments, the RIL 116 may further include a probe that is configured to provide at least one of device information, network information, or user preferences 112 to a network proxy device 124 of the telecommunication network 120.
In various embodiments, the signaling reduction rules 110 may be stored locally on the telecommunication device 102 or remotely. The signaling reduction rules 110 may be stored in a database, file, collection, or other data structure. In one embodiment, they may be specified in an extensible markup language (XML) file. The telecommunication device 102 receives or retrieves the signaling reduction rules 110 from a network operator or service provider. The one or more rules servers 136 illustrated in
The device information, network information, or user preferences 112 may be retrieved or compiled from any source, such as applications 108, operating system 118, RIL 118, network proxy device 124, or another device of the telecommunication network 120. The device information, network information, or user preferences 112 may be retrieved or compiled by the application controller 104, by the network proxy device 124, or by another component of the telecommunication device 102 or another device. The device information 112 may include at least one of a battery power state, an indication of whether a telecommunication display screen is on or off, or an indication of whether a telecommunication device radio is in an active mode or a dormant mode. The network information 112 may include at least one of network congestion information, a radio channel condition, a network latency, or information associated with a cell in which the telecommunication device is located. User preferences 112 may include a preference for application updates occurring at a certain frequency, which may be related to the delay responses associated with the respective applications.
As mentioned above, the application controller 104 may be part of the operating system 118. Alternatively, the application controller 104 may be a layer, such as a layer in a network stack. In such embodiments, that layer may be between the applications 108 and the operating system 118 or between the operating system 118 and RIL 116. Regardless of whether it is incorporated in operating system 118 or is a layer, the application controller 104 is in the communication path from applications 108 to the RIL 116.
In various embodiments, the application controller 104 receives or traps packets 106 provided by the applications 108 for transmission via the radio of the telecommunication device 102. Upon receiving a packet 106, the application controller 104 determines the application identifier of the packet 106. The application identifier may include one or more of an internet protocol (IP) address, a communication protocol, a source port, a destination port, an application name, a signature, or a website name. The application controller 104 then utilizes the application identifier of the packet 106 to retrieve a signaling reduction rule 110 from the set of signaling reduction rules 110. To retrieve the signaling reduction rule 110, the application controller 104 may utilize mappings of application identifiers to signaling reduction rules 110 or mappings of application identifiers to categories and categories to signaling reduction rules 110. As mentioned, the signaling reduction rules 110 may be stored locally on the telecommunication device 102 or remotely at, for example, rules server(s) 136. In some embodiments, no signaling reduction rule 110 may be associated with the application identifier of the packet 106. In such embodiments, the application controller 104 may simply provide the packet 106 to the RIL 116 for transmission. In further embodiments, rather than performing these actions (e.g., retrieving signaling reduction rules 110) for each packet 106, the application controller 104 may perform the actions once for a packet flow that includes the packet 106.
In some embodiments, the application controller 104 may further retrieve any of or more of device information, network information, or user preferences 112 from any source, such as applications 108, operating system 118, RIL 118, network proxy device 124, or another device of the telecommunication network 120. Examples of device information, network information, or user preferences 112 are described further herein. In some embodiments, the application controller 104 of the telecommunication device 102 and the application controller 128 of the network proxy device 124 may exchange at least one of device information, network information, or user preferences 112 with each other.
The retrieved signaling reduction rule 110 specifies one or more signaling reduction actions, and the application controller 104 select at least one of those one or more signaling reduction actions to perform, in some embodiments based on or more of device information, network information, or user preferences 112. The application controller 104 may then perform the at least one selected signaling reduction action. For example, the application controller 104 may buffer the packet 106 and/or packets of the packet flow including packet 106 for later transmission, storing that packet 106/packet flow in a buffer 114 of the application controller 104. Also or instead, the application controller 104 may discard the packet 106/packet flow, bundle the packet 106/packet flow with one or more other packets 106/packet flows, request that an application 108 wait for a time period before transmitting further packets 106/packet flows, pad the packet 106/packets of the packet flow to increase the size of the packet 106/packets, modify content associated with the packet 106/packets of the packet flow (e.g., requesting that an application 108 perform compression), or trigger a radio of the telecommunication device 102 into an active or dormant mode. In some embodiments, such as those where the packet 106/packet flow has been buffered, bundled, padded, or modified, the application controller 104 may then provide the packet 106/packet flow to the RIL 116 for transmission.
The telecommunication network 120 may be a telecommunication network of a telecommunication service provider that provides a plan or services to the telecommunication device 102. The telecommunication network 120 may include a core network and a plurality of access networks that are associated with base stations, nodeBs, eNodeBs, or other access points. In some embodiments, the network proxy device 124 may be an edge device of the core network and may communicate with another device of the core network, such as a gateway GPRS (general packet radio service) support node (GGSN), a serving gateway (SGW), or packet data network gateway (PGW). The access networks of the telecommunication network 120 may each be associated with a specific geographic area (e.g., a cell, a macrocell, a microcell, a femtocell, etc.). In some embodiments, the telecommunication network 120 may be a cellular network having spectrum to allocate for cellular communications. Because that spectrum is a scare resource, signaling reduction by application controllers 104 and 128 on uplink and downlink transmissions is important in making sure that spectrum is optimally used.
In various embodiments, the application server(s) 122, network proxy device 124, and rule server(s) 136 may each be or include a server or server farm, multiple, distributed server farms, a mainframe, a work station, a personal computer (PC), a laptop computer, a tablet computer, an embedded system, or any other sort of device or devices. In one implementation, one or more of the application server(s) 122, network proxy device 124, and rule server(s) 136 represent a plurality of computing devices working in communication, such as a cloud computing network of nodes.
The application server(s) 122 may be associated with any sort of network application and may provide services to any number of remote clients, such as application 108. For example the application server(s) 108 may be video call server(s), voice call server(s), web server(s), social media server(s), messaging server(s), or media streaming server(s). The application server(s) 108 may receive packets 106 and may respond to those received communications. In some embodiments, the application server(s) 122 may be connected to an edge device of the telecommunication network 120, such as a network proxy device 124, via a public network, such as the Internet 126.
As mentioned above, the network proxy device 124 may be an edge device of the telecommunication network 120 between other devices of the telecommunication network 120, such as a GGSN, SGW, or PGW, and a public network, such as the Internet 126. The network proxy device 124 is configured with an application controller 128 to perform signaling reduction actions associated with the transmission of packets across the telecommunication network 120 to the telecommunication device 102, thereby conserving resources of both the telecommunication device 102 and of the telecommunication network 120.
In various embodiments, the application controller 128 may perform the signaling reduction functions for downlink communications that the application controller 104 performs for uplink communications. The application controller 128 receives or traps packets received from, e.g., the application server(s) 122 for transmission to the telecommunication device 102. Upon receiving a packet, the application controller 128 determines the application identifier of the packet. The application identifier may include one or more of an internet protocol (IP) address, a communication protocol, a source port, a destination port, an application name, a signature, or a website name. The application controller 128 then utilizes the application identifier of the packet to retrieve a signaling reduction rule 130 from the set of signaling reduction rules 130. The set of signaling reduction rules 130 may be similar to or the same as the above-described set of signaling reduction rules 110. To retrieve the signaling reduction rule 130, the application controller 128 may utilize mappings of application identifiers to signaling reduction rules 130 or mappings of application identifiers to categories and categories to signaling reduction rules 130. The signaling reduction rules 130 may be stored locally on the network proxy device 124 or remotely at, for example, rules server(s) 136. In some embodiments, no signaling reduction rule 130 may be associated with the application identifier of the packet. In such embodiments, the application controller 128 may simply transmit the packet across the telecommunication network 120 to its destination telecommunication device 102.
In some embodiments, the application controller 128 may further retrieve any of or more of device information, network information, or user preferences 132 from any source, such as telecommunication device 102, another device of the telecommunication network 120, or specialized server(s) (e.g., network congestion information may be provided by specialized server(s)). Device information, network information, and user preferences 132 may be similar to, or the same as, device information, network information, and user preferences 112, and examples of device information, network information, or user preferences 112 are described further herein. In some embodiments, the application controller 128 of the network proxy device 124 and the application controller 104 of the telecommunication device 102 may exchange at least one of device information, network information, or user preferences 132 with each other. In further embodiments, the application controller 128 of the network proxy device 124 may receive at least one of device information, network information, or user preferences 132 from a RIL probe of the telecommunication device 102.
The retrieved signaling reduction rule 130 specifies one or more signaling reduction actions, and the application controller 128 selects at least one of those one or more signaling reduction actions to perform, in some embodiments based on or more of device information, network information, or user preferences 132. The application controller 128 may then perform the at least one selected signaling reduction action. For example, the application controller 128 may buffer the packet or other packets of a packet flow that includes the packet for later transmission, storing that packet/packet flow in a buffer 134 of the application controller 128. Also or instead, the application controller 128 may discard the packet/packet flow, bundle the packet/packet flow with one or more other packets/packet flows, request that an application server 122 wait for a time period before transmitting further packets/packet flows, pad the packet/packets to increase the size of the packet/packets, modify content associated with the packet/packets (e.g., requesting that an application server 122 perform compression), or trigger a radio of the telecommunication device 102 into an active or dormant mode.
In some embodiments, the rule server(s) 136 may be devices of the network operator or service provider associated with the telecommunication network 120. As mentioned, the signaling reduction rules 110 specified by the rule server(s) 136 may be specific to an application 108 or a category of applications 108. Also, signaling reduction rules 110 may be associated with specific sectors of the telecommunication network 120 and may be updated by the rule server(s) 136 based on changing conditions, such as server failures or security exploits. In addition, the signaling reduction rules may be specific to any one or more of device information 112, network information 112, user preferences 112, or a subscription plan associated with a user of the telecommunication device 102. The rule server(s) 136 may receive network information, such as congestion conditions at cells, from the telecommunication network 120. The rule server(s) 136 may also receive device information from the telecommunication device 102 (e.g., from the application controller 104) or from the telecommunication network 120 (e.g., from the application controller 128 of the network proxy device 124). The rule server(s) 136 may utilize the network information and device information in formulating signaling reduction rules 110 or updates to signaling reduction rules 110.
In some embodiments, specification or updating of signaling reduction rules 110 may be triggered by the telecommunication network 120. As mentioned above, the signaling reduction rules 110 may specify signaling reduction actions. The may also each be associated with an application identifier, either in the set of signaling reduction rules 110 itself or in an accompanying table or structure. In embodiments where rules are associated with categories, the rule server(s) 136 may generate a further mapping of application identifiers to categories, and associate categories with signaling reduction rules 110. The signaling reduction rules 110 may be provided periodically or responsive to the generating or updating or signaling reduction rules 110. In one embodiment, the signaling reduction rules 110 are stored at the rule server(s) 136, and the application controller 104 may retrieve specific signaling reduction rules 110 by providing an application identifier and, optionally an indication of device information, network information, or user preferences 112.
In various embodiments, system memory 202 is volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination of the two. The application controller 104, the applications 108, the radio interface layer 116, and the operating system 118 are described above in detail with regard to
In some embodiments, the processor(s) 206 is a central processing unit (CPU), a graphics processing unit (GPU), or both CPU and GPU, or any other sort of processing unit.
Telecommunication device 102 also includes additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated in
In some embodiments, the radio 212 includes any sort of radio known in the art. For example, radio 212 may include a radio transceiver that performs the function of transmitting and receiving radio frequency communications via an antenna. The radio 212 may facilitate wireless connectivity between the telecommunication device 102 and various cell towers, base stations and/or access points of the telecommunication network 120. In addition to radio 212, the telecommunication device 102 may also include a wireless communication transceiver and a near field antenna for communicating over unlicensed wireless IP networks, such as local wireless data networks and personal area networks (e.g., Bluetooth or near field communication (NFC) networks).
In some embodiments, the output devices 214 include any sort of output devices known in the art, such as a display (e.g., a liquid crystal display), speakers, a vibrating mechanism, or a tactile feedback mechanism. Output devices 214 also include ports for one or more peripheral devices, such as headphones, peripheral speakers, or a peripheral display.
In various embodiments, input devices 216 include any sort of input devices known in the art. For example, input devices 216 may include a camera, a microphone, a keyboard/keypad, or a touch-sensitive display. A keyboard/keypad may be a push button numeric dialing pad (such as on a typical telecommunication device), a multi-key keyboard (such as a conventional QWERTY keyboard), or one or more other types of keys or buttons, and may also include a joystick-like controller and/or designated navigation buttons, or the like.
In some embodiments, the battery 218 may be any sort of battery, such as a lithium ion battery. The battery 218 may be rechargeable, and may be associated with logic of the telecommunication device 102 capable of exposing a charge level of the battery 218 to a platform or applications of the telecommunication device 102, such as the application controller 104.
The GPS 220 may be functionality and logic capable of wirelessly communicating with a GPS system to receive GPS locations, such as GPS coordinates, from the GPS system. The GPS 220 may expose those GPS locations to a platform or applications of the telecommunication device 102, such as the application controller 104.
In various embodiments, system memory 302 is volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination of the two. The application controller 128 is described above in detail with regard to
In some embodiments, the processor(s) 306 is a central processing unit (CPU), a graphics processing unit (GPU), or both CPU and GPU, or any other sort of processing unit.
Network proxy device 124 also includes additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated in
In some embodiments, the transceivers 312 include any sort of transceivers known in the art. For example, transceivers 312 may include a radio transceiver that performs the function of transmitting and receiving radio frequency communications via an antenna. The radio 212 may facilitate wireless connectivity between the network proxy device 124 and various nodes of the telecommunication network 120 or between the network proxy device 124 and routers or other devices of the Internet 126. In addition, the transceivers 312 may also include a wireless communication transceiver and a near field antenna for communicating over unlicensed wireless IP networks, such as local wireless data networks and personal area networks (e.g., Bluetooth or near field communication (NFC) networks). Further, the transceivers 312 may include wired communication components, such as an Ethernet port, that connect the network proxy device 124 in a wired fashion to one or more nodes of the telecommunication network 120 and routers or other devices of the Internet 126.
In some embodiments, the output devices 314 include any sort of output devices known in the art, such as a display (e.g., a liquid crystal display), speakers, a vibrating mechanism, or a tactile feedback mechanism. Output devices 314 also include ports for one or more peripheral devices, such as headphones, peripheral speakers, or a peripheral display.
In various embodiments, input devices 316 include any sort of input devices known in the art. For example, input devices 316 may include a camera, a microphone, a keyboard/keypad, or a touch-sensitive display. A keyboard/keypad may be a push button numeric dialing pad (such as on a typical telecommunication device), a multi-key keyboard (such as a conventional QWERTY keyboard), or one or more other types of keys or buttons, and may also include a joystick-like controller and/or designated navigation buttons, or the like.
At 404, the application controller of the telecommunication device receives a packet from an application of the telecommunication device. In response, at 406, the application controller determines a signaling reduction rule associated with the application. At 406a, the determining comprises retrieving the signaling reduction rule from a set of signaling reduction rules based on an application identifier associated with the application. The application identifier includes one or more of an internet protocol (IP) address, a communication protocol, a source port, a destination port, an application name, a signature, or a website name. At 406b, the determining comprises determining a category associated with the application and determining a signaling reduction rule that is associated with the category.
At 408, the application controller determines at least one of device information, network information, or user preferences. The device information may include at least one of a battery power state, an indication of whether a telecommunication display screen is on or off, or an indication of whether the radio is in an active mode or a dormant mode. The network information may include at least one of network congestion information, a radio channel condition, a network latency, or information associated with a cell in which the telecommunication device is located.
At 410, based at least on the determined signaling reduction rule, the application controller performs a signaling reduction action associated with the transmission of the packet. The signaling reduction action may be one of buffering the packet for later transmission, discarding the packet, bundling the packet with one or more other packets, requesting that the application wait for a time period before transmitting further packets, padding the packet to increase the size of the packet, modifying content associated with the packet, or triggering a radio of the telecommunication device into an active or dormant mode. At 410a, the performing may be based both on the signaling reduction rule and on the at least one of the device information, the network information, or the user preferences.
At 504, the application controller of the network proxy device receives a packet from an application server that is destined for a telecommunication device. In response, at 506, the application controller determines a signaling reduction rule associated with an application of the application server. At 506a, the determining comprises retrieving the signaling reduction rule from a set of signaling reduction rules based on an application identifier associated with the application. The application identifier includes one or more of an internet protocol (IP) address, a communication protocol, a source port, a destination port, an application name, a signature, or a website name. At 506b, the determining comprises determining a category associated with the application and determining a signaling reduction rule that is associated with the category.
At 508, the application controller may exchange at least one of device information, network information, or user preferences with an application controller of the telecommunication device.
At 510, the application controller may receive at least one of device information, network information, or user preferences from a radio interface layer probe of the telecommunication device.
At 512, based at least on the determined signaling reduction rule, the application controller performs a signaling reduction action associated with the transmission of the packet. The signaling reduction action may be one of buffering the packet for later transmission, discarding the packet, bundling the packet with one or more other packets, requesting that the application server wait for a time period before transmitting further packets, padding the packet to increase the size of the packet, modifying content associated with the packet, or triggering a radio of the telecommunication device into an active or dormant mode. At 512a, the performing may be based both on the signaling reduction rule and on the at least one of the device information, the network information, or the user preferences.
At 514, the application controller may trigger an update to a set of signaling reduction rules based at least in part on telecommunication device information, network information, or user preferences.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claims.
This application claims priority to U.S. provisional patent application No. 61/619,895, entitled “Network Signaling Reduction and Battery Life Extension” and filed on Apr. 3, 2012. Application No. 61/619,895 is fully incorporated herein by this reference.
Number | Date | Country | |
---|---|---|---|
61619895 | Apr 2012 | US |