EP2764734A1 - Systeme und verfahren zur überwachung von hintergrundanwendungsereignissen - Google Patents

Systeme und verfahren zur überwachung von hintergrundanwendungsereignissen

Info

Publication number
EP2764734A1
EP2764734A1 EP12784107.0A EP12784107A EP2764734A1 EP 2764734 A1 EP2764734 A1 EP 2764734A1 EP 12784107 A EP12784107 A EP 12784107A EP 2764734 A1 EP2764734 A1 EP 2764734A1
Authority
EP
European Patent Office
Prior art keywords
communication
list
rules
delayed
permitted
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP12784107.0A
Other languages
English (en)
French (fr)
Inventor
Gerardo Giaretta
Arnaud Meylan
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US13/490,396 external-priority patent/US8838086B2/en
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Publication of EP2764734A1 publication Critical patent/EP2764734A1/de
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 

Definitions

  • the present application relates generally to wireless communications, and more specifically to systems, methods, and devices for managing background application events.
  • Apps or device applets are now available that operate to provide a wide range of add-on services and features to wireless devices. For example, it is now possible for wireless devices to download and launch device applets to perform value-added functions such as, shopping, searching, position location, driving navigation, and an array of other functions. Network and application providers generally offer these device applets to device users for additional fees. Thus, the use of device applets increases the functionality and usability of wireless devices and offers device users features and convenience not originally available on the devices themselves.
  • a wireless device interfaces with one or more communication networks using any of a plurality of radios.
  • the wireless device may include a variety of radios providing communications using cellular, Wi-Fi, Bluetooth or other types of radio access technologies. Accordingly, applications executing on the wireless device are provided with a default routing that determines the radio and associated radio channel the applications will use to communicate with the appropriate network.
  • the wireless device includes a network interface configured to exchange data with a communication network.
  • the wireless device further includes an input device configured to receive one or more inputs.
  • the wireless device further includes a processor electrically connected to the network interface.
  • the processor is configured to determine whether the device is in a background state or a foreground state based on the presence or absence of one or more inputs.
  • the processor is further configured to execute a plurality of applications configured to communicate with the communication network via the network interface.
  • the processor is further configured to collect one or more communication statistics, for one or more of the plurality of applications, when the device is in the background state.
  • the processor is further configured to, when the device is in the foreground state, either collect, separately from the communication statistics collected when the device is in the background state, the one or more communication statistics, or refrain from collecting the one or more communication statistics.
  • Another aspect of the disclosure provides a method of collecting application communication statistics.
  • the method includes determining whether a device is in a foreground state or a background state based on the presence or absence of one or more inputs.
  • the method further includes executing a plurality of applications configured to communicate with a communication network.
  • the method further includes collecting one or more communication statistics, for one or more of the plurality of applications, when the device is in the background state.
  • the method further includes, when the device is in the foreground state, either collecting, separately from the communication statistics collected when the device is in the background state, the one or more communication statistics, or refraining from collecting the one or more communication statistics.
  • the apparatus includes means for determining whether the apparatus is in a foreground state or a background state based on the presence or absence of one or more inputs.
  • the apparatus further includes means for executing a plurality of applications configured to communicate with a communication network.
  • the apparatus further includes means for collecting one or more communication statistics, for one or more of the plurality of applications, when the apparatus is in the background state.
  • the apparatus further includes either means for collecting, separately from the communication statistics collected when the device is in the background state, the one or more communication statistics when the device is in the foreground state or means for refraining from collecting the one or more communication statistics when the device is in the foreground state.
  • the medium includes code that, when executed, causes an apparatus to determine whether the apparatus is in a foreground state or a background state based on the presence or absence of one or more inputs.
  • the medium further includes code that, when executed, causes the apparatus to execute a plurality of applications configured to communicate with a communication network.
  • the medium further includes code that, when executed, causes the apparatus to collect one or more communication statistics, for one or more of the plurality of applications, when the apparatus is in the background state.
  • the medium further includes code that, when executed, causes the apparatus to, when the apparatus is in the foreground state, either collect, separately from the communication statistics collected when the apparatus is in the background state, the one or more communication statistics, or refrain from collecting the communication statistics.
  • the wireless device configured to execute a plurality of applications and communicate with a communication network.
  • the wireless device includes a receiver configured to receive a plurality of rules specifying how one or more of the plurality of applications should communicate with the communication network.
  • the wireless device further includes an input an input device configured to receive one or more inputs.
  • the wireless device further includes a processor configured to determine whether the device is in a foreground state or a background state based on the presence or absence of one or more inputs.
  • the processor is further configured to modify communication by one or more of the plurality of applications in compliance with the rules.
  • the processor is further configured to allow transmission of the communication by one or more of the plurality of applications in accordance with the rules, when the device is in the foreground state.
  • Another aspect of the disclosure provides a method of communicating with a communication network.
  • the method includes receiving a plurality of rules specifying how one or more of a plurality of applications should communicate with the communication network.
  • the method further includes determining whether the device is in a foreground state or a background state based on the presence or absence of one or more inputs.
  • the method further includes modifying communication by one or more of the plurality of applications in compliance with the rules.
  • the method further includes allowing transmission of the communication by one or more of the plurality of applications, in accordance with the rules, when the user interface is in the foreground state.
  • the apparatus includes means for receiving a plurality of rules specifying how one or more of a plurality of applications should communicate with the communication network.
  • the apparatus further includes means for determining whether the device is in a foreground state or a background state based on the presence or absence of one or more inputs.
  • the apparatus further includes means for modifying communication by one or more of the plurality of applications in compliance with the rules.
  • the apparatus further includes means for allowing transmission of the communication by one or more of the plurality of applications, in accordance with the rules, when the user interface is in the foreground state.
  • the medium includes code that, when executed, causes an apparatus to receive a plurality of rules specifying how one or more of a plurality of applications should communicate with a communication network.
  • the medium further includes code that, when executed, causes the apparatus to determine whether the device is in a foreground state or a background state based on the presence or absence of one or more inputs.
  • the medium further includes code that, when executed, causes the apparatus to modify communication by one or more of the plurality of applications in compliance with the rules.
  • the medium further includes code that, when executed, causes the apparatus to allow transmission of the communication by one or more of the plurality of applications, in accordance with the rules, when the user interface is in the foreground state.
  • the device includes a processor configured to generate a plurality of rules specifying how one or more of a plurality of applications, executing on a wireless device, should communicate with the communication network.
  • the device further includes a transmitter configured to transmit the plurality of rules, over the communication network, to the wireless device.
  • Another aspect of the disclosure provides a method of communicating with a communication network.
  • the method includes generating a plurality of rules specifying how one or more of a plurality of applications, executing on a wireless device, should communicate with the communication network.
  • the method further includes transmitting the plurality of rules, over the communication network, to the wireless device.
  • the apparatus includes means for generating a plurality of rules specifying how one or more of a plurality of applications, executing on a wireless device, should communicate with the communication network.
  • the apparatus further includes means for transmitting the plurality of rules, over the communication network, to the wireless device.
  • the medium includes code that, when executed, causes an apparatus to generate a plurality of rules specifying how one or more of a plurality of applications, executing on a wireless device, should communicate with the communication network.
  • the medium further includes code that, when executed, causes the apparatus to transmit the plurality of rules, over the communication network, to the wireless device.
  • FIG. 1 shows an exemplary network environment illustrating aspects of a communication management system
  • FIG. 2 shows an exemplary wireless device configured to provide communication management
  • FIG. 3 shows a flowchart of an exemplary method of providing communication management
  • FIG. 4 shows a graph of application network activity for an exemplary device
  • FIG. 5 shows an exemplary block diagram of a hardware/software system configured to aggregate application communication
  • FIG. 6 shows an exemplary timeline of application communication aggregation implemented by the hardware/software system of FIG. 5;
  • FIG. 7 shows a timeline of application communication aggregations, according to another embodiment
  • FIG. 8 shows an exemplary device configured to implement a communication access policy
  • FIG. 9 shows a flowchart of an exemplary method of collecting communication statistics
  • FIG. 10 shows a flowchart of an exemplary method of analyzing communication statistics
  • FIG. 11 shows a flowchart of another exemplary method of collecting communication statistics.
  • FIG. 12 shows a flowchart of an exemplary method of implementing the communication access policy
  • FIG. 13 shows another exemplary device configured to implement the communication access policy.
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal FDMA
  • SC-FDMA Single-Carrier FDMA
  • a CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), CDMA2000, etc.
  • UTRA includes Wideband-CDMA (W-CDMA) and Low Chip Rate (LCR).
  • CDMA2000 covers IS- 2000, IS-95 and IS-856 standards.
  • a TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM).
  • GSM Global System for Mobile Communications
  • An OFDMA network may implement a radio technology such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.15, IEEE 802.16, IEEE 802.20, Flash-OFDM®, etc.
  • E-UTRA Evolved UTRA
  • GSM Universal Mobile Telecommunication management system
  • LTE Long Term Evolution
  • UTRA, E-UTRA, GSM, UMTS and LTE are described in documents from an organization named "3rd Generation Partnership Project" (3GPP).
  • CDMA2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2).
  • FIG. 1 shows an exemplary network environment 100 illustrating aspects of a communication management system 108.
  • the network environment 100 includes a wireless device 102, a communication network 104, and one or more servers 110 and 111.
  • the device 102 includes a plurality of radios (not shown) to communicate with the network 104 using corresponding radio channels 106.
  • the device 102 also includes a communication management system 108 that operates to control access to the plurality of radios, for example by a particular application.
  • the wireless device 102 may communicate with the servers 110 and 111 via the communication network 104.
  • the servers 110 and 111 connect to the communication network 104 via communication channels 112 and 113, respectively.
  • the communication channels 112 and 113 may be either a wired or wireless channel.
  • the wireless device 102 executes applications which may interface with the network 104 using any of the plurality of radios.
  • an executing application may issue a networking function call, such as a socket layer call, to request a network resource for communication with the network 104.
  • the communication management system 108 may process the socket layer call based on a default routing configuration to bind a pre-determined radio resource to the application.
  • the server 110 may obtain a communication access policy.
  • the server 110 may generate the communication access policy based on compiled network statistics, may retrieve a previously compiled communication access policy, or may receive the communication access policy from another source.
  • the wireless device 102 may collect communication statistics via the communication management system 108.
  • Communication statistics may include, for example, information about applications that attempt to access the radio channels 106, when the applications attempt to access the radio channels 106, what kind of access is attempted, etc.
  • the wireless device 102 may provide the communication statistics to the server 111.
  • One or both of the servers 110 and 111 may process the communication statistics received from the wireless device 102, and may compile communication access policy, either alone or in tandem.
  • the server 110 and the server 111 may be collocated, or their functionality can be combined on a single server.
  • the communication access policy may include rules about which applications are allowed to access the radio channels 106, when the applications are allowed to access the radio channels 106, what kind of access is allowed, etc.
  • the server 110 may provide the communication access policy to the wireless device 102 via the communication network 104.
  • the server 110 may provide the communication access policy to the wireless device 102 via Access Network Discovery and Selection Function (ANDSF), Open Mobile Alliance Device Management (OMA-DM), and/or any other suitable method, over-the-air or otherwise.
  • ANDSF Access Network Discovery and Selection Function
  • OMA-DM Open Mobile Alliance Device Management
  • the communication management system 108 operates to intercept the networking function call from the application.
  • the communication management system 108 may select an appropriate radio for use by the application according to the communication access policy.
  • the communication management system 108 may also modify communications of the application according to the communication access policy. As used herein, modification of communications can include, but is not limited to, delaying communications or otherwise impacting or affecting communications.
  • the intelligent radio selection system 108 may also bind the application to a network resource (i.e., the radio that has been selected). Because the communication management system 108 operates in response to the normal operations of the applications when they use a radio resource, the system may operate with both legacy and non-legacy applications without any application changes or upgrades. A more detailed description of the communication management system 108 is provided below.
  • FIG. 2 shows an exemplary wireless device 200 configured to provide communication management.
  • the device 200 includes a processor 202, a memory 204, and a TX/RX radio 212, all coupled to communicate using a communication bus 214.
  • the wireless device 200 may be the wireless device 102, described above with respect to FIG. 1. It should be noted that the device 200 is just one implementation and that other implementations are possible.
  • the processor 202 includes an application layer module 206, a connectivity engine 208, and a networking module 210.
  • the processor 202 may also include at least one of a CPU, microprocessor, gate array, hardware logic, memory elements, and/or hardware executing software (not shown).
  • the processor 202 is configured to control the operation of the device 200 such that communications of applications executing on the device 200 may be selectively modified, impacted, delayed and/or bound to a desired radio.
  • the processor 202 is configured to execute computer-readable instructions related to performing any of a plurality of functions.
  • the processor 202 operates to analyze information received or communicated from the device 200 to effectuate communication management.
  • the processor 202 operates to generate information that may be utilized by the memory 204, the application layer module 206, the TX/RX radio 212, and/or connectivity engine 208 to effectuate communication management.
  • the TX/RX radio 212 includes hardware and/or a processor executing software that is configured to provide a plurality of radios/interfaces that may be used to interface the device 200 with a plurality of external entities, such as the external communication network 104 (FIG. 1) using a plurality of radio channels 216.
  • the radio channels 216 may be, for example, the radio channels 106 described above with respect to FIG. 1.
  • the TX/RX radio 212 may provide radios/interfaces to communicate using cellular, Wi-Fi, Bluetooth, or any other technologies to communicate with communication networks using the radio channels 216.
  • the application layer module 206 includes hardware and/or a processor executing software that is configured to execute one or more applications on the device 200 and to store the applications in the memory 204.
  • the application layer module 206 is configured to allow applications to initiate networking function calls to the networking module 210 to request networking services.
  • the networking function calls may include a connection request to a radio/interface at the TX/RX radio 212 for the purpose of communicating with an external network or system via the radio channels 216.
  • the networking module 210 includes hardware and/or a processor executing software that is configured to perform networking functions.
  • the networking functions include such functions as Connect(), Bind(), Write(), and Setsockopt().
  • the connect() function operates to establish a connection between an application and a particular radio/interface.
  • the write() function operates to send data over the connection.
  • a particular radio/interface may be selected from the plurality of candidate radios provided by the TX/RX radio 212.
  • networking module 210 is configured to perform a variety of networking functions or commands.
  • the networking module 210 may allow certain functions to proceed, and may not allow other functions to proceed, while a device is in a background mode (FIG. 8).
  • the device can be in a background mode, for example, when a user interface is not in use.
  • the connectivity engine 208 includes hardware and/or a processor executing software that is configured to assess system resources to manage communication from applications.
  • the connectivity engine 208 is configured to intercept application communication, selectively modify, impact, and/or delay the communication, and/or select a particular radio based on one or more of the following selection criteria.
  • Application requirements - requirements associated with requesting applications such as bandwidth requirements or latency/performance requirements.
  • Network usability information regarding the availability of a particular network on a particular radio interface.
  • Vendor Supplied Metrics information to translate from radio metrics such as Receive Signal Strength Indication and Packet Loss Rate to the throughput and latency available for a particular radio interface.
  • Access Point Availability - information specifying the unique identifier for access points congested by the traffic from other devices or those that may configure a radio link but do not forward packets to the network.
  • the processor 202 may download one or more of the aforementioned selection criteria via the TX/RX radio 212.
  • the selection criteria may be stored in the memory 204.
  • the processor 202 may retrieve the operator policy and the connectivity engine 208 may apply the operator policy.
  • the operator policy may include a plurality of rules regulating network access by applications on the wireless device 200.
  • the memory 204 includes RAM, ROM, EEPROM or any other type of memory device that operates to allow the applications and/or the selection criteria to be stored and retrieved at the device 200.
  • the memory 204 is configured to store computer-readable instructions executed by processor 202.
  • the memory 204 may also be configured to store any of a plurality of other types of data including data generated by any of the processor 202, TX/RX radio 212, application layer module 206, networking module 210, and/or connectivity engine 208.
  • the memory 204 may be configured in a number of different configurations, including as random access memory, battery-backed memory, hard disk, magnetic tape, etc.
  • Various features may also be implemented upon memory 204, such as compression and automatic back up.
  • the memory 204 is configured to store a pre-load library 218 and a networking library 220.
  • the pre-load library 218 intercepts socket calls from applications.
  • the networking library 220 provides the networking API used by applications to create and connect sockets to establish network communications.
  • the connectivity engine 208 is configured to selectively modify, impact, and/or delay application communication in various ways.
  • the connectivity engine 208 may be configured to delay communication using one or more of the above selection criteria.
  • the connectivity engine 208 may delay only communication from delay-tolerant applications.
  • the connectivity engine 208 may delay communication only when the wireless device 200 is in a background state.
  • the connectivity engine 208 delays communication for delay- tolerant applications until the wireless device 200 enters a foreground state.
  • the connectivity engine 208 delays communication for delay-tolerant applications until a delay-intolerant application initiates communication.
  • the connectivity engine 208 may also be configured to select a radio from the plurality of candidate radios in various ways. For example, the connectivity engine 208 may be configured to select a radio using one or more of the above selection criteria. Once a radio is selected, the connectivity engine 208 binds the application to the interface representing that radio. For example, in one implementation, the connectivity engine 208 binds the application to the radio's interface by calling into the original networking library 220. Thus, functions at the connectivity engine 208 and the pre-load library 218 may easily access functions, such as a bind() function, in the networking library 220 to bind to the radio that has been selected for the application.
  • functions at the connectivity engine 208 and the pre-load library 218 may easily access functions, such as a bind() function, in the networking library 220 to bind to the radio that has been selected for the application.
  • the communication management system includes a computer program product having one or more program instructions ("instructions") or sets of "codes" stored or embodied on a computer-readable medium.
  • the codes are executed by at least one processor, for instance, processor 202, their execution causes the processor 202 to control the device 200 to provide the functions of the intelligent interface selection system described herein.
  • the computer- readable medium includes a floppy disk, CDROM, memory card, FLASH memory device, RAM, ROM, or any other type of memory device or computer-readable medium that interfaces to the device 200.
  • the sets of codes may be downloaded into the device 200 from an external device or communication network resource. The sets of codes, when executed, operate to provide aspects of the intelligent interface selection system described herein.
  • FIG. 3 shows a flowchart 300 of an exemplary method of providing communication management.
  • the flowchart 300 is described below with reference to the device 200 shown in FIG. 2.
  • the processor 202 executes one or more sets of codes to control the functional elements of the device 200 to perform the functions described below.
  • the processor 202 launches an application.
  • the application may be a legacy or non-legacy application that is part of the application layer module 206.
  • the application may be a network browser that generates a networking function call to connect to a wireless network using a radio available at the TX/RX radio 212.
  • the processor 202 configures and loads a pre-load library.
  • the pre-load library 218 includes a subset of the networking functions that are provided in the networking library 220 used by applications to assess communication networks.
  • the networking functions in the pre-load library 218 are configured to intercept networking function calls from applications executing at a device.
  • the pre-load library 218 includes POSIX socket functions that may be used to intercept socket calls by applications executing at the device 200.
  • the pre-load library 218 in stored in memory 204.
  • the pre-load library 218 functions are configured to receive arguments passed from calling applications and use these arguments to generate a request to the connectivity engine 208 to select the radio best suited for the application's purpose.
  • the processor 202 links the pre-load library into the execution environment. For example, the processor 202 links the pre-load library 218 into the execution environment at a higher priority than the networking library 220. Thus, networking functions calls by applications will be intercepted and processed by functions in the pre-load library 218 and not processed by similar functions in the networking library 220.
  • the processor 202 intercepts a networking function call from the application.
  • the networking function call may be a POSIX socket function call, such as the connect() function or the write() function.
  • the application generates the networking function call to connect to a radio to allow communication with external networks.
  • the processor 202 intercepts (or processes) the networking function call via the functions in the pre-load library 218.
  • the processor 202 can delay the networking function call in accordance with the received operator policy, as discussed below with respect to FIG. 12.
  • the called function in the pre-load library 218 generates a selection request to the connectivity engine 208 to select the appropriate radio for use by the application.
  • the request includes any information that is part of the selection criteria used by the connectivity engine 208 to select the appropriate radio for use by the application.
  • the called function in the pre-load library 218 generates a selection request to the connectivity engine 208 to determine whether the communication should be delayed.
  • selection criteria are assessed.
  • the connectivity engine 208 operates to assess the selection criteria described above.
  • the connectivity engine 208 may communicate with the processor 202 to assess Operator Policies that are part of the selection criteria.
  • the connectivity engine 208 selects a radio based on the assessment of the selection criteria. For example, the connectivity engine 208 operates to select the radio that best matches the selection criteria.
  • the connectivity engine 208 binds to the radio's interface that has been selected for the application. For example, in one implementation, the connectivity engine 208 calls a bind() function of the networking library 220 to bind to the radio that has been selected for the application. For example, the connectivity engine 208 is aware of the networking library 220 and how to access its functions directly without being intercepted by the pre-load library 218. In an embodiment, the connectivity engine 208 delays communication prior or post to binding the application to the radio.
  • the application then utilizes the radio that has been selected for network communications.
  • the method proceeds to block 312 where the connectivity engine 208 operates to perform periodic assessment of the selection criteria to determine if the current radio best matches the selection criteria. If the connectivity engine 208 determines after another assessment of the selection criteria that a radio other than the current radio best matches the selection criteria, then the connectivity engine 208 may destroy the connection as a means to trigger the application into restarting the connection to select a different radio for the new connection. Thus, the optional operation allows the selection criteria to be periodically assessed to assure that the most appropriate radio is selected to conduct the desired communication.
  • the flowchart 300 provides communication management for use with legacy and non-legacy applications. It should be noted that the flowchart 300 is just one implementation and that the operations of the flowchart 300 may be rearranged or otherwise modified such that other implementations are possible. Connectivity Management for Wireless device Applications
  • wireless devices such as smart phones, personal digital assistants, etc.
  • software applications may continue to operate even though the device is in the background state (for example, when a user is not actively using the device).
  • Applications such as social networking applications, email or other communication applications, data feeds, etc. (popular examples include Facebook®, Gmail®, Twitter®, etc.) may continue to send and receive data even though a user is not using the device.
  • a mobile device may be in background mode when certain inputs of the device are not operational or are in a sleep state.
  • the device may be in background mode when a user is not using the device.
  • audio inputs such as a microphone
  • visual inputs such as a display of the device
  • the device may be determined to be in a background mode. Additional inputs may be used to determine whether or not the mobile device is in a background mode, as will be described below.
  • FIG. 4 shows a graph 400 of application network activity for an exemplary device.
  • the x-axis of the graph 400 shows time, and the y-axis shows an amount of data transferred, in bytes, at each time.
  • the graph 400 shows network activity during an approximately two-hour period, during which the device is in an idle mode.
  • the device is in an idle mode when a user does not interact with the device and/or a display is off.
  • applications that continue to operate create spikes in activity, for example, spikes 410a-i.
  • Such applications can be referred to as "background” applications.
  • the activity by these applications may utilize communication resources such as the radios in radio 212, etc.
  • the background mode can be an "idle" mode.
  • Network activity spikes such as spikes 410a-i, may cause the wireless device to transition from the idle mode to a connected mode.
  • the device In the connected mode, the device may power-up a radio, may generate signaling traffic, and may consume a greater amount of power than when in the idle mode.
  • the spikes may prevent the wireless device from transitioning from the connected mode to the idle mode, or to alternate connection modes such as a discontinuous reception (DRX) mode.
  • DRX discontinuous reception
  • Such elevated levels of radio activity by the applications when the user is not actively engaging the device may result in shortened battery life, increased load of radio networks, or other undesired effects.
  • a device may employ a software layer (also referred to as a "wrapper") that provides an application program interface (API) to capture data from background applications and hold them until a desired point where radio resources may be activated and the application data transferred and tasks executed in a synchronized manner.
  • a software layer also referred to as a "wrapper”
  • API application program interface
  • FIG. 5 shows an exemplary block diagram of a hardware/software system 500 configured to aggregate application communication.
  • the software components are divided between an application processor 550 and a modem processor 560, but the various functionalities may be organized differently from the example of FIG. 5.
  • functions described as software may be implemented in hardware and vice versa, functions may be distributed differently between components, etc.
  • the hardware/software system 500 may be the communication management system 108, discussed above with respect to FIG. 1.
  • the hardware software system 500 may be implemented on the wireless device 200, described above with respect to FIG. 2.
  • functions of the application processor 550 may be implemented by one or more of the processor 202, the application layer module 206, and/or the connectivity engine 208.
  • Functions of the modem processor 560 may be implemented by one or more of the TX/RX radio 212, the networking module 210, and/or the connectivity engine 208.
  • applications 502 interact with an application connection engine 508 and with a high level operating system (HLOS) 506.
  • the HLOS 506 may be, for example, the Android operating system produced by Google Inc., Mountain View, CA.
  • the application connection engine 508 may communicate with a modem connection engine 510.
  • the modem connection engine may manage communication resources such as a radio 212 and the radios therein.
  • the wrapper 504 is capable of capturing data between the applications 502 and the HLOS 506.
  • the wrapper 504 may aggregate data from the applications 502 during a period of user inactivity and hold them until a determined time before releasing them to the HLOS 506 and ultimately the radio 212 for operation/transmission.
  • the wrapper 504 may be invisible to the applications 502 such that they are unaware that their data/requests are being held/aggregated.
  • the wrapper 504 may emulate functions of the HLOS 506.
  • the wrapper 504 may be a separate component or may be incorporated into another component such as the application connection engine 508.
  • the wrapper 504 may be implemented by the connectivity engine 208, described above with respect to FIG. 2.
  • FIG. 6 shows an exemplary timeline 600 of application communication aggregation implemented by the hardware/software system 500 of FIG. 5.
  • applications APP 1-4 each initiate a request for use of a radio resource in succession during an aggregation period 610.
  • application communication may be delayed during the aggregation period 610.
  • the aggregation period 610 can include a period in which the device 200 is in the idle mode.
  • the applications APP 1-4 may be delay-tolerant applications. Delay-tolerant applications may carry relatively time-insensitive data such as, for example, e-mail or a bulk file transfer.
  • the application APP 1 makes a connect() request. Then, the application APP 2 makes a write() request. Next, the application APP 3 makes a connect() request. Finally, the application APP 4 makes a connect() request.
  • the wrapper 504 receives the connect() and write() socket calls. Instead of acting on the socket calls immediately, the wrapper 504 delays the communication during the aggregation period 610. At a determined time, the wrapper 504 releases the socket calls together, as aggregated data requests 620.
  • the wrapper 504 may release the aggregated data requests 620 during a transmit window 630.
  • the transmit window 630 may include a period in which the device 200 is in the idle mode, and may include a period in which the device 200 is in the active mode.
  • the wrapper 504 may release aggregated data requests 620 from APPs 1-4.
  • the wrapper 504 may also allow application communications requests made during the transmit window 630 to proceed without delay. In other words, during the transmit window 630, the wrapper 504 may not delay further communication.
  • APP 5 initiates a connect() request during the transmit window 630.
  • the wrapper 504 allows the connect() request of APP 5 to proceed without delay.
  • wrapper 504 may open the transmit window 630 at regular or intermittent intervals. For example, the wrapper 504 may open transmit window 630, once every 5 minutes, 10 minutes, 15 minutes, 30 minutes, 60 minutes, etc. In another example, the wrapper 504 may release delayed application communications at a random or pseudo-random time. The intervals at which the wrapper 504 opens the transmit window 630 may be determined by the device 200 or received from another device, such as the server 110 (FIG. 1).
  • the wrapper 504 can determine when to open the transmit window 630 dynamically, based on the aggregated data requests 620. For example, the wrapper 504 can open the transmit window 630 when the number of aggregated data requests 620 surpasses a threshold.
  • the threshold can be determined by the device 200 or received from another device, such as the server 110.
  • the wrapper 504 can keep the transmit window 630 open for a predetermined or dynamic period of time. For example, the wrapper 504 may keep the transmit window 630 open for 15 seconds, 30 seconds, 1 minute, 5 minutes, etc., after the transmit window 630 is opened. As another example, the wrapper 504 may keep the transmit window 630 open for 15 seconds, 30 seconds, 1 minute, 5 minutes, etc., after the last application communication is transmitted. The amount of time which the wrapper 504 keeps the transmit window 630 open may be determined by the device 200 or received from another device, such as the server 110.
  • the wrapper 504 may open the transmit window 630 when a delay-intolerant application initiates communication.
  • APP 5 may be a delay-intolerant application. Accordingly, the wrapper 504 may open the transmit window 630 when the connect() request is received from APP 4. The wrapper 504 may allow the connect() request from APP 4 to proceed, and may also release the aggregated data requests 620 from the APPs 1-4.
  • FIG. 7 shows a timeline 700 of application communication aggregations, according to another embodiment.
  • applications APP 1-2 each initiate a request for use of a radio resource in succession.
  • the applications APP 1-2 may indicate their delay tolerance via a connection engine API.
  • the application APP 1-2 may include background activity and/or requirements for operation that are only tolerant of specific delays.
  • the applications APP 1-2 may be location tracking applications that report the location of the device 200 periodically, such as every 10 seconds.
  • the application APP 1 initiates a communication request, and indicates to the wrapper 504 that it will only tolerate an X-second delay.
  • the application APP 2 initiates a communication request, and indicates to the wrapper 504 that it will only tolerate a Y-second delay.
  • the wrapper 504 may provide a callback function (e.g., API.Go), which may indicate to an application that communication is allowed. After receiving the callback, the application may proceed with communication.
  • API.Go a callback function
  • the wrapper 504 provides the API.Go callback to the application APP 1 before the X-second delay has elapsed. The application APP 1 then communicates through the wrapper 504, without further delay. Similarly, the wrapper 504 provides the API.Go callback to the application APP 2 before the Y-second delay has elapsed. The application APP 2 then communicates through the wrapper 504, without further delay.
  • applications may provide the wrapper 504 with specific transmission deadlines via the API.
  • the wrapper 504 may transparently delay communication from the applications, within the constraints of the provided deadlines. Accordingly, the wrapper 504 will allow the application communication to proceed prior to any deadlines.
  • the API may allow also an application to register as a delay-intolerant application.
  • Applications that may request immediate access include child tracking applications, emergency notification applications, etc.
  • the wrapper 504 may learn the delay tolerance of various applications by monitoring the application communications.
  • the wrapper 504 may receive a list of application delay tolerances from a list or database, either stored locally on the device 102 or received from the server 110. The list or database may be received along with a communication access policy such as the operator policy.
  • the wrapper 504 may aggregate or delay application communications in a manner that reduces user disruption.
  • the wrapper 504 may analyze a variety of factors to determine when to delay or aggregate application communication. For example, the wrapper 504 may delay application communication based on characteristics of the wireless device 102 such as a display state (on or off), an audio state (on or off), etc.
  • the wrapper 504 may only delay application communications known to be tolerant of delay.
  • the wrapper 504 may delay application communication when the radio is not loaded, when the wireless device is not otherwise in use (e.g., no phone calls, audio streaming, etc.).
  • the wrapper 504 may determine when to delay application communication based on any combination of the above factors, in addition to other suitable factors.
  • the wrapper 504 may analyze a variety of factors to determine when to release delayed or aggregated communication and to permit unrestricted application communication.
  • a delay-intolerant application such as, for example, an emergency notification application
  • the unrestricted application communication may trigger the wrapper 504 to release previously delayed or aggregated application communications.
  • previously delayed application communications may use radio resources in conjunction with the emergency application.
  • the wrapper 504 may open a transmit window for all applications when a delay-intolerant application communication is initiated.
  • the wrapper 504 may release delayed or aggregated application communications when a specific radio is activated or selected as a default.
  • the specific radio may include, for example, a Wi-Fi radio, a cellular radio, a particular mode of the cellular radio (e.g. 2G or 3G communication modes), a Bluetooth radio, etc.
  • the wrapper 504 may delay application communications when only a cellular radio is enabled, and may release the delayed application communications when a Wi-Fi radio is enabled.
  • the wrapper 504 may release delayed or aggregated application communications when a radio channel quality is above a threshold.
  • Radio channel quality may include metrics such as signal strength, signal-to-noise ratio (SNR), etc.
  • the wrapper 504 may delay application communications when the SNR of a cellular radio is below a threshold, and may release the delayed application communications when the SNR of the cellular radio rises to or above the threshold.
  • the wrapper 504 may release delayed or aggregated application communications periodically or in non-continuous windows. For example, the wrapper 504 may release delayed application communications every 15 minutes. In another example, the wrapper 504 may release delayed application communications at a random or pseudo-random time every 15 to 20 minutes.
  • the wrapper 504 releases delayed or aggregated application communications when user interaction is received.
  • the wrapper 504 may release delayed application communications when a display is activated, a button press is detected, etc.
  • the wireless device 102 may anticipate user interaction.
  • the wireless device 102 may include an accelerometer that may detect movement of the wireless device 102.
  • the wrapper 504 may release delayed application communications when accelerometer output indicates a likelihood of imminent user interaction.
  • the wireless device 102 may anticipate user interaction via a proximity detector.
  • the wrapper 504 may release delayed application communications in response to any combination of the above, and additionally in response to any other suitable event.
  • the communication management system 108 may receive a communication access policy from the server 110.
  • the communication access policy may include the operator policy used by the connectivity engine 208 (FIG. 2) when delaying and releasing application communications during the aggregation period 610 (FIG. 6) and the transmit window 630, respectively.
  • the communication access policy can include one or more of: timing information indicating how long application communication may be delayed during the aggregation period 610, a list of applications for which communication may be delayed (an "inclusion list”), a list of applications for which communication may not be delayed (an “exclusion list”), a list of communication types for which communication may or may not be delayed, a list of network conditions during which communication may or may not be delayed, a list of events or triggers for which the wrapper 504 should open or close the transmit window 630, an indication of times during which communication may or may not be delayed, an indication of locations in which communications may or may not be delayed, how often the device 200 should request an update communication access policy from the server 110, a list of radio access technologies (RATs) in which communications may be delayed, etc.
  • RATs radio access technologies
  • communication types can include one or more socket operations such as, for example, bind(), connect(), accept(), send(), recv(), write(), read(), sendto(), recvfrom(), close(), gethostbyname(), and gethostbyaddr().
  • Communication types can further include classifications of traffic types such as, for example, conversational traffic, best effort traffic, and emergency traffic.
  • Conversational traffic can include communication representing intermittent one or two- way communication and/or interactive content such as, for example, text chat traffic, voice chat traffic, video chat traffic, World Wide Web traffic (e.g., mapping and navigation functions), etc.
  • Best effort traffic can include relatively low-priority and/or non-interactive traffic such as, for example, bulk data transfers (e.g., File Transfer Protocol (FTP) traffic), e-mail, video pre-loading, etc.
  • Emergency communication can include relatively high-priority traffic such as, for example, child-tracking position data, time- sensitive alert traffic, emergency voice traffic, etc.
  • communication types can be based on information typically contained in an IP header such as, for example, source IP address, destination IP address, source port, destination port, etc.
  • the communication access policy can include a synchronization frequency indicating how often the wrapper 540 should open the transmit window 630 in the absence of a transmit trigger or event.
  • the communication access policy may indicate that the wrapper 540 should open the transmit window 630 at least every 5 minutes, 10 minutes, 15 minutes, 30 minutes, 60 minutes, etc.
  • the communication access policy can include a threshold amount of aggregated data requests over which the wrapper 504 should open the transmit window 630.
  • communication access policy may indicate that the wrapper 540 should open the transmit window 630 when the amount of aggregated data requests 620 is sufficient to occupy the radio 212 for a threshold amount of time.
  • the wrapper can open the gate if the number of applications, for which communications are delayed, is greater than a threshold.
  • the communication access policy can include the threshold.
  • the wrapper can open the gate if the number of socket calls, for which communications are delayed, is greater than a threshold.
  • the communication access policy can include the threshold.
  • the communication access policy can include a list of application delay tolerances from the server 110.
  • the list of application delay tolerances may include a list of delay-intolerant applications, which may be referred to as an "exclusion list.”
  • the wrapper 504 (FIG. 5) may exclude applications identified in the exclusion list from aggregation.
  • the list of application delay tolerances may include a list of delay-tolerant applications, which may be referred to as an "inclusion list.”
  • the wrapper 504 may include applications identified in the inclusion list when aggregating application communications.
  • the wrapper 504 may exclude applications by default, and may only delay application communications for applications specifically identified in the inclusion list.
  • the inclusion list may include an application identifier such as, for example, a string representing an application name, a numerical identifier, a version number, an author identification, or any combination thereof.
  • the inclusion and/or exclusion lists can identify application communications on a granularity including communication types represented by individual socket operations. For example, the inclusion list may identify connect() operations from an application "Application A" as a delay-tolerant socket operation. Accordingly, the wrapper 504 may aggregate connect() operations from "Application A", but may not aggregate, for example, write() operations from "Application A”.
  • wrapper 504 may not aggregate connect() operations from "Application B", but may aggregate, for example, write() operations from "Application B".
  • the lists can include other combinations of application identifiers, socket operations, and the like.
  • the communication access policy includes an indication of network conditions during which communication may or may not be delayed.
  • the communication access policy can include a threshold amount of radio traffic, based on which the wrapper 504 will adjust the aggregation period 610 and/or the transmit window 630.
  • the wrapper 504 can open the transmit window 630 when an amount of network traffic drops below a threshold specified in the communication access policy.
  • the communication access policy includes a list of events or triggers for which the wrapper 504 should open or close the transmit window 630.
  • the communication access policy may indicate that the wrapper 504 should open the transmit window 630 when an application and/or socket call not on the inclusion list attempts to transfer data.
  • the communication access policy may indicate that the wrapper 504 should open the transmit window 630 when an application and/or socket call on the exclusion list attempts to transfer data.
  • the communication access policy may indicate that the wrapper 504 should close the transmit window 630 when only applications and/or socket calls on the inclusion lists attempt to transfer data.
  • the communication access policy may indicate that the wrapper 504 should open the transmit window 630 when the device 200 enters the active mode.
  • the communication access policy may indicate that the wrapper 504 should open the transmit window 630 when a user interface 822 (FIG. 8) receives input.
  • the wrapper 504 may not open the transmit window 630 when the device 200 enters the active mode, but may otherwise disable the wrapper 504 and/or stop delaying communications when the device 200 is in the active mode.
  • the communication access policy includes a list of times, dates, and/or locations in which the wrapper 504 should or should not delay application communications.
  • the communication access policy may indicate that the wrapper 504 should or should not delay communications between certain hours or the day, during certain days of the week, when the device 200 is in certain cities or countries, etc.
  • time, date, and/or location policies can be specified with granularities specific to one or more particular applications and/or socket operations.
  • the server 110 can receive information regarding the state of the communication network 104. For example, the server 110 can determine how long Network Address Translation (NAT) tables in the communication network 104 maintain their records. The server 110 can adjust the communication access policy to indicate that the wrapper 504 should open the transmit window 630 with a frequency sufficient for applications to refresh their NAT entries, to keep their connections alive, etc.
  • NAT Network Address Translation
  • the communication access policy can combine two or more access criteria such as the aforementioned timing information, application lists, communication types, network conditions, etc.
  • the communication access policy can indicate that all traffic to port 80 can be delayed by up to 5 minutes when the device 802 is in standby.
  • the communication access policy can indicate that, when the device 802 is in standby, only a WLAN interface can be used.
  • the communication access policy can indicate that "connect()" socket calls from "Application X" may complete without delay while the device 802 is in standby.
  • the communication access policy can indicate that "connectO" and "write()" socket calls from "Application Y" may be delayed while the device 802 is in standby.
  • the communication access policy can incorporate other delay criteria such as, for example, which socket operations are attempted, the source and/or destination ports of attempted communications, the destination IP address, etc.
  • the communication access policy can indicate that communications may be delayed when the radio access technology is High Speed Packet Access (HSPA), but may not be delayed when the radio access technology is LTE.
  • HSPA High Speed Packet Access
  • LTE Long Term Evolution
  • FIG. 8 shows an exemplary device 802 configured to implement a communication access policy.
  • the device may be employed within the network environment 100, described above with respect to FIG. 1.
  • the device 802 is an example of a device that may be configured to implement the various methods described herein.
  • the device 802 may implement one or more functions of the wireless device 102.
  • the device 802 may implement one or more functions of the server 110.
  • the device 802 may include a processor 804 which controls operation of the device 802.
  • the processor 804 may also be referred to as a central processing unit (CPU).
  • the memory 806, which may include both read-only memory (ROM) and random access memory (RAM), provides instructions and data to the processor 804.
  • a portion of the memory 806 may also include non-volatile random access memory (NVRAM).
  • the processor 804 may perform logical and arithmetic operations based on program instructions stored within the memory 806.
  • the instructions in the memory 806 may be executable to implement the methods described herein.
  • the processor 804 may be configured to execute one or more applications, which may be stored in the memory 806. During execution, the applications may initiate communication over the transceiver 814, the transmitter 810, and/or the receiver 812.
  • the processor 804 may implement the hardware/software system 500, described above with respect to FIG. 5. Accordingly, the processor 804 may monitor the communications of executed applications, record communication statistics, receive a communication access policy via the receiver 812, and may store the communication access policy in the memory 806.
  • the processor 804 may implement the communication access policy as described above with respect to FIGs. 6-7.
  • the processor 804 may comprise or be a component of a processing system implemented with one or more processors.
  • the one or more processors may be implemented with any combination of general-purpose microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate array (FPGAs), programmable logic devices (PLDs), controllers, state machines, gated logic, discrete hardware components, dedicated hardware finite state machines, or any other suitable entities that may perform calculations or other manipulations of information.
  • the processing system may also include machine -readable media for storing software.
  • Software shall be construed broadly to mean any type of instructions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Instructions may include code (e.g., in source code format, binary code format, executable code format, or any other suitable format of code). The instructions, when executed by the one or more processors, cause the processing system to perform the various functions described herein.
  • the device 802 may also include a housing 808 that may include a transmitter 810 and/or a receiver 812 to allow transmission and reception of data between the device 802 and a remote location.
  • the transmitter 810 and receiver 812 may be combined into a transceiver 814.
  • An antenna 816 may be attached to the housing 808 and electrically coupled to the transceiver 814. In some embodiments, the antenna 816 may be omitted, and the device 802 may be configured for wired communication.
  • the device 802 may also include (not shown) multiple transmitters, multiple receivers, multiple transceivers, and/or multiple antennas.
  • the device 802 may also include a signal detector 818 that may be used in an effort to detect and quantify the level of signals received by the transceiver 814.
  • the signal detector 818 may detect such signals as total energy, energy per subcarrier per symbol, power spectral density and other signals.
  • the device 802 may also include a digital signal processor (DSP) 820 for use in processing signals.
  • DSP 820 may be configured to generate a packet for transmission.
  • the packet may comprise a physical layer data unit (PPDU).
  • PPDU physical layer data unit
  • the device 802 may further comprise a user interface 822 in some aspects.
  • the user interface 822 may comprise a proximity detector, one or more input buttons, a keypad, a microphone, a speaker, an interface port (for example, a Universal Serial Bus (USB) port, a High-Definition Multimedia Interface (HDMI) port, etc.), a touchscreen, a network interface, and/or a display.
  • the user interface 822 may include any element or component that conveys information to a user of the device 802 and/or receives input from the user.
  • the user interface 822 may be considered active when it is receiving input, or sending output (for example, from a USB port, network interface, to a display, from a microphone, etc.).
  • the user interface 822 may also be considered active when it has received input, or has sent output within a threshold time period (for example, 1 second, 1 minute, 5 minutes, etc.).
  • the user interface 822 may be considered inactive or idle when it is not active.
  • the device 802 When the user interface 822 receives no input, the device 802 may be said to be in a background state, or an idle mode. In the background state, a display may be off, and one or more functions of the device 802 may be disabled. In an embodiment, processes and communications of the device 802 that are not initiated in response to user interface 822 input may be referred to as background or idle processes or communications .
  • the device 802 may be said to be in a foreground state, or an active mode.
  • the display In the foreground state, the display may be on, and input may have been received within an input idle period.
  • the input idle period may be configurable and may be, for example, 1 minute.
  • background processes and communications may occur in the active mode, but may not be initiated in direct response to user interface 822 input.
  • the various components of the device 802 may be coupled together by a bus system 826.
  • the bus system 826 may include a data bus, for example, as well as a power bus, a control signal bus, and a status signal bus in addition to the data bus.
  • a data bus for example, as well as a power bus, a control signal bus, and a status signal bus in addition to the data bus.
  • Those of skill in the art will appreciate the components of the device 802 may be coupled together or accept or provide inputs to each other using some other mechanism.
  • processor 804 may be used to implement not only the functionality described above with respect to the processor 804, but also to implement the functionality described above with respect to the signal detector 818 and/or the DSP 820. Further, each of the components illustrated in FIG. 8 may be implemented using a plurality of separate elements.
  • FIG. 9 shows a flowchart 900 of an exemplary method of collecting communication statistics.
  • the method of flowchart 900 is described herein with reference to the device 802 discussed above with respect to FIG. 8, a person having ordinary skill in the art will appreciate that the method of flowchart 900 may be implemented by the wireless device 102 discussed above with respect to FIG. 1, the wireless device 202 discussed above with respect to FIG. 2, and/or any other suitable device.
  • the steps in flowchart 900 may be performed by the processor 805 in conjunction with the transmitter 810, the receiver 812, the memory 806, and the user interface 822.
  • the method of flowchart 900 is described herein with reference to a particular order, in various embodiments, blocks herein may be performed in a different order, or omitted, and additional blocks may be added.
  • the device 802 receives the ignore list via the receiver 812.
  • the processor 804 may store the ignore list in the memory 806.
  • the device 802 receives the ignore list from the server 110.
  • the ignore list may be pre-provisioned on the device 802.
  • the ignore list may specify one or more applications for which the device 802 should not monitor or record communication statistics.
  • the device 802 may also receive other information from the server 110, such as the inclusion list and/or the exclusion list.
  • the processor 804 intercepts one or more communications from an application executing on the processor 804.
  • the processor 804 may intercept the communications via facilities described above with respect to the communication management system 108 and/or the connectivity engine 208.
  • the DSP 820, the signal detector 818, the transmitter 810, and/or the transceiver 814 may intercept the communications.
  • the processor 804 determines a device state.
  • the device may be in one of at least two states, which may include a background state and a foreground state.
  • the processor 804 may determine the state of the device via the user interface 822.
  • the processor 804 determines whether the device is in the background state. If the device is in the foreground state, the processor 804 does not record communication statistics and waits for further communication at block 925. If the device is in the background state, the processor 804 continues to block 930.
  • the processor 804 determines whether the intercepted communication is a background communication. If the intercepted communication is not a background communication, the processor 804 does not record communication statistics and waits for further communication at block 925. If the intercepted communication is a background communication, the processor 804 continues to block 930. [00123] Thereafter, at block 930, the processor 804 determines whether the application associated with the intercepted communication is on the ignore list received from the server 110. If the application that generated the intercepted communication is on the ignore list, the processor 804 does not record communication statistics and waits for further communication at block 925. If the application that generated the intercepted communication is not on the ignore list, the processor 804 continues to block 935.
  • Communication statistics may include, for example, an application identifier (e.g. a full or partial name, or a numerical identifier) for an applications active during the idle mode, an amount of data transferred by the application, how many connections the application initiated, a number of Transmission Control Protocol (TCP) requests made by the application, a number of User Datagram Protocol (UDP) packets sent, a number of Domain Name Service (DNS) requests sent, etc.
  • TCP request statistics may include statistics about specific requests such as "connect,” “write,” “FIN,” “RST”, etc.
  • the communication statistics may include raw data, or calculated statistics such as min, max, mean, median, standard deviation, etc.
  • the communication statistics may also include additional information such as, for example, a device identifier, a SIM card identifier, a home network identity, a mobile country code, a mobile network code, a location of the device 802, etc.
  • the processor 804 may store the recorded communication statistics in the memory 806, and may compress, encrypt or otherwise encode the recorded communication statistics via the DSP 820.
  • the processor 804 determines whether to report the accumulated communication statistics.
  • the processor 804 may determine reporting criteria, such as a threshold number of recorded statistics, that will cause the processor 804 to report the communications statistics to the server 110.
  • the processor 804 may report recorded communication statistics on a periodic basis, such as hourly, daily, weekly, monthly, etc.
  • the processor 804 may report recorded communication statistics when the number of recorded statistics reaches a threshold value and/or when the size of the recorded statistics reaches a threshold value.
  • the processor 804 may only report statistics when a specified radio is enable, for example, a Wi-Fi or cellular radio.
  • the processor 804 may combine one or more of the aforementioned reporting criteria, or use additional criteria.
  • the processor 804 may receive instructions about how and when to report communication statistics from the server 110. If the processor 804 determines that the reporting criteria has not been met, the processor does not report the recorded communication statistics and waits at block 925 If the processor 804 determines that the reporting criteria has been met, the processor continues to block 945.
  • the processor 804 sends the recorded communication statistics to the server 110, via the transmitter 810 and/or the transceiver 814.
  • the processor 804 may send the recorded communication statistics via an HTTP POST method, a File Transfer Protocol (FTP) transfer, as an e-mail, or via any other communication means.
  • FTP File Transfer Protocol
  • the processor 804 may delete the recorded communication statistics from the memory 806, or may retain the recorded communication statistics for later use.
  • the processor 804 may receive a response from the server 110, which may include one or more of the ignore list, the exclusion list, the inclusion list, a list of instructions about when to report communication statistics, and a list of instructions about how to record communication statistics.
  • FIG. 10 shows a flowchart 1000 of an exemplary method of analyzing communication statistics.
  • the method of flowchart 100 is described herein with reference to the device 802 discussed above with respect to FIG. 8, a person having ordinary skill in the art will appreciate that the method of flowchart 100 may be implemented by the server 110 discussed above with respect to FIG. 1 or any other suitable device.
  • the steps in flowchart 1000 may be performed by the processor 805 in conjunction with the transmitter 810, the receiver 812, and the memory 806.
  • the method of flowchart 1000 is described herein with reference to a particular order, in various embodiments, blocks herein may be performed in a different order, or omitted, and additional blocks may be added.
  • Communication statistics may include, for example, an application identifier (e.g. a full or partial name, or a numerical identifier), a number of Transmission Control Protocol (TCP) requests made by the application, a number of User Datagram Protocol (UDP) packets sent, a number of Domain Name Service (DNS) requests sent, etc.
  • TCP request statistics may include statistics about specific requests such as "connect,” “write,” “FIN,” “RST”, etc.
  • the communication statistics may include raw data, or calculated statistics such as min, max, mean, median, standard deviation, etc. of requests or packets during a specified time window.
  • the communication statistics may also include additional information such as, for example, a device identifier, a SIM card identifier, a home network identity, a mobile country code, a mobile network code, a location of the device 802, etc.
  • the processor 804 may store the received communication statistics in the memory 806, and may compress, encrypt or otherwise encode the received communication statistics via the DSP 820.
  • the processor 804 generates the ignore list.
  • the processor 804 may generate the ignore list based on the received communication statistics from the device 102 and/or communication statistics received at other times and/or from other devices. For example, the processor 804 may add an application identifier to the ignore list once it has received a threshold number of communication statistics for that application.
  • the ignore list may be initially seeded with applications that have already been analyzed. The processor 804 may occasionally remove one or more application identifiers form the ignore list in order to learn whether the application communication behavior has changed over time.
  • the processor 804 generates the inclusion list.
  • the processor 804 may generate the inclusion list based on the received communication statistics from the device 102 and/or communication statistics received at other times and/or from other devices. For example, the processor 804 may add an application identifier to the inclusion list once the recorded number of communication attempts by the application drops below a threshold.
  • the inclusion list may be initially seeded with applications that have already been determined to be delay-tolerant. The processor 804 may remove one or more application identifiers form the inclusion list if, for example, the received communication statistics indicate that the application is delay-intolerant.
  • the processor 804 generates the exclusion list.
  • the processor 804 may generate the exclusion list based on the received communication statistics from the device 102 and/or communication statistics received at other times and/or from other devices. For example, the processor 804 may add an application identifier to the exclusion list once the recorded number of communication attempts by the application surpasses a threshold.
  • the exclusion list may be initially seeded with applications that have already been determined to be delay- intolerant. The processor 804 may remove one or more application identifiers form the exclusion list if, for example, the received communication statistics indicate that the application is delay-tolerant.
  • the processor 804 generates a review list.
  • the processor 804 may generate the review list based on the received communication statistics from the device 102 and/or communication statistics received at other times and/or from other devices. For example, the processor 804 may add an application identifier to the review list once the recorded number of communication attempts by the application drops below a threshold.
  • the review list may be a precursor to the inclusion list.
  • the processor 804 may add candidate applications to the review list for further analysis. Further analysis may be performed by either the processor 804 and/or manually via the user interface 822.
  • the processor 804 may move an application from the review list to the inclusion list according to a signal from the user interface 822.
  • the processor 804 transmits one or more of the aforementioned lists to the wireless device 102 via the transmitter 810 and/or the transceiver 814.
  • the processor 804 may transmit the lists in response to the received communication statistics via, for example, an HTTP POST response.
  • the processor 804 may push the lists to the wireless device 102.
  • the processor 804 may transmit a list of instructions about when to report communication statistics and/or a list of instructions about how to record communication statistics.
  • FIG. 11 shows a flowchart 1100 of an exemplary method of collecting communication statistics.
  • the method of flowchart 1100 is described herein with reference to the device 802 discussed above with respect to FIG. 8, a person having ordinary skill in the art will appreciate that the method of flowchart 1100 may be implemented by the wireless device 102 discussed above with respect to FIG. 1, the wireless device 202 discussed above with respect to FIG. 2, and/or any other suitable device.
  • the steps in flowchart 1100 may be performed by the processor 805 in conjunction with the transmitter 810, the receiver 812, the memory 806, and the user interface 822.
  • the method of flowchart 1100 is described herein with reference to a particular order, in various embodiments, blocks herein may be performed in a different order, or omitted, and additional blocks may be added.
  • the device 802 receives the ignore list via the receiver 812.
  • the processor 804 may store the ignore list in the memory 806.
  • the device 802 receives the ignore list from the server 110.
  • the ignore list may specify one or more applications for which the device 802 should not monitor or record communication statistics.
  • the device 802 may also receive other information from the server 110, such as the inclusion list and/or the exclusion list.
  • the processor 804 intercepts one or more communications from an application executing on the processor 804.
  • the processor 804 may intercept the communications via facilities described above with respect to the communication management system 108 and/or the connectivity engine 208.
  • the DSP 820, the signal detector 818, the transmitter 810, and/or the transceiver 814 may intercept the communications.
  • the processor 804 determines whether the application associated with the intercepted communication is on the ignore list received from the server 110. If the application that generated the intercepted communication is on the ignore list, the processor 804 does not record communication statistics and waits for further communication at block 1120. If the application that generated the intercepted communication is not on the ignore list, the processor 804 continues to block 1125.
  • the processor 804 determines a state of the device 802.
  • the user interface 826 may be in one of at least two states, which may include a background state and a foreground state.
  • the processor 804 may determine the state of the user interface 822 based on the presence or absence of one or more inputs to the user interface 826. In an embodiment, the processor 804 may determine whether the intercepted is a background communication, generated automatically by an application, as opposed to being generated in response to an input via the user interface 822.
  • the processor 804 determines a state of a network interface.
  • the network interface can include the transceiver 814, the transmitter 810, and/or the receiver 812.
  • the network interface may be in one of at least two states, which may include a background state and a foreground state.
  • the processor 804 may determine the state of the user interface 822 based on a radio power and/or connection state of the transceiver 814. In an embodiment, the processor 804 may determine a plurality of network interface states.
  • Communication statistics may include, for example, an application identifier (e.g. a full or partial name, or a numerical identifier) for an applications active during the background mode, an amount of data transferred by the application, how many connections the application initiated, a number of Transmission Control Protocol (TCP) requests made by the application, a number of User Datagram Protocol (UDP) packets sent, a number of Domain Name Service (DNS) requests sent, etc.
  • TCP request statistics may include statistics about specific requests such as "connect,” “write,” “FIN,” “RST”, etc.
  • the communication statistics may include raw data, or calculated statistics such as min, max, mean, median, standard deviation, etc.
  • the communication statistics may also include additional information such as, for example, a device identifier, a SIM card identifier, a home network identity, a mobile country code, a mobile network code, a location of the device 802, etc.
  • the processor 804 may store the recorded communication statistics in the memory 806, and may compress, encrypt or otherwise encode the recorded communication statistics via the DSP 820.
  • the processor 804 may store the communication statistics separately, based on the states of the user interface 826 and/or the network interface. For example, the processor 804 may store the communication statistics separately for each of the following states of the wireless device 802: user interface 826 active and network interface active, user interface 826 active and network interface inactive, user interface 826 inactive and network interface active, and/or user interface 826 inactive and network interface inactive.
  • the processor 804 may store the communication statistics "separately" by maintaining a plurality of different databases, by tagging each communication statistic with a state of the user interface 826 and/or the network interface, etc.
  • a person having ordinary skill in the art will appreciate that separate storage of the communication statistics can be accomplished in any manner that allows differentiation between communication statistics recorded during different states of the wireless device 802.
  • the processor 804 may separately store communication statistics based on other states of the wireless device 802 such as, for example, a power state, a clock state indicating a time and/or date, a network access state, etc.
  • the processor 804 determines whether to report the accumulated communication statistics.
  • the processor 804 may determine reporting criteria, such as a threshold number of recorded statistics, that will cause the processor 804 to report the communications statistics to the server 110.
  • the processor 804 may report recorded communication statistics on a periodic basis, such as hourly, daily, weekly, monthly, etc.
  • the processor 804 may report recorded communication statistics when the number of recorded statistics reaches a threshold value and/or when the size of the recorded statistics reaches a threshold value.
  • the processor 804 may only report statistics when a specified radio is enable, for example, a Wi-Fi or cellular radio.
  • the processor 804 may combine one or more of the aforementioned reporting criteria, or use additional criteria.
  • the processor 804 may receive instructions about how and when to report communication statistics from the server 110. If the processor 804 determines that the reporting criteria has not been met, the processor does not report the recorded communication statistics and waits at block 1125 If the processor 804 determines that the reporting criteria has been met, the processor continues to block 1145.
  • the processor 804 sends the recorded communication statistics to the server 110, via the transmitter 810 and/or the transceiver 814.
  • the processor 804 may send the recorded communication statistics via an HTTP POST method, a File Transfer Protocol (FTP) transfer, as an e-mail, or via any other communication means.
  • FTP File Transfer Protocol
  • the processor 804 may delete the recorded communication statistics from the memory 806, or may retain the recorded communication statistics for later use.
  • the processor 804 may receive a response from the server 110, which may include one or more of the ignore list, the exclusion list, the inclusion list, a list of instructions about when to report communication statistics, and a list of instructions about how to record communication statistics.
  • FIG. 12 shows a flowchart 1200 of an exemplary method of applying the communication access policy.
  • one or more aspects of the flowchart 1200 can correspond to block 308 of FIG. 3.
  • the method of flowchart 1200 is described herein with reference to the device 802 discussed above with respect to FIG. 8, a person having ordinary skill in the art will appreciate that the method of flowchart 1200 may be implemented by the wireless device 132 discussed above with respect to FIG. 1, the wireless device 202 discussed above with respect to FIG. 2, and/or any other suitable device.
  • the steps in flowchart 1200 may be performed by the processor 805 in conjunction with the transmitter 810, the receiver 812, the memory 806, and the user interface 822.
  • blocks herein may be performed in a different order, or omitted, and additional blocks may be added.
  • the device 802 receives the communication access policy via the receiver 812.
  • the processor 804 may store the communication access policy in the memory 806.
  • the device 802 receives the communication access policy from the server 110.
  • the communication access policy may specify how the device 802 should delay application communication.
  • the processor 804 intercepts one or more communications from an application executing on the processor 804.
  • the processor 804 may intercept the communications via facilities described above with respect to the communication management system 138 and/or the connectivity engine 208.
  • the DSP 820, the signal detector 818, the transmitter 810, and/or the transceiver 814 may intercept the communications.
  • the processor 804 determines a device state.
  • the device may be in one of at least two states, which may include a foreground state and a background state.
  • the foreground state can be a foreground state
  • the background state can be a background state.
  • the processor 804 may determine the state of the device via the user interface 822.
  • the processor 804 may determine whether the intercepted is a background communication, generated automatically by an application, as opposed to being generated in response to an input via the user interface 822.
  • the processor 804 determines whether the device 802 is in the background state. If the device is in the not in the background state, the processor 804 does not delay the application communication and allows the communication to proceed at block 1225. If the device is in the background state, the processor 804 continues to block 1230. In one embodiment, blocks 1215 and 1220 can be omitted, and application communications may be delayed regardless of whether the device 802 is in the background state.
  • the processor 804 determines whether the transmit window 630 is open. As discussed above with respect to FIGs. 6-7, the processor 804 can determine whether to open the transmit window 630 based on the communication access policy. For example, the processor 804 may open the transmit window 630 if the intercepted application communication is not in the inclusion list. In an embodiment, determining whether the transmit window 630 is open can include opening the transmit window 630 in response to an application communication, event, or other trigger. If the transmit window 630 is open, the processor 804 does not delay the application communication and allows the communication to proceed at block 1225. If the transmit window 630 is closed, the processor 804 continues to block 1235.
  • the processor 804 delays the intercepted communication in accordance with the communication access policy. For example, the processor 804 may determine one or more delay criteria of: a list of applications for which communication may be delayed (an "inclusion list"), a list of applications for which communication may not be delayed (an "exclusion list”), a list of communication types for which communication may or may not be delayed, a list of network conditions during which communication may or may not be delayed, an indication of times during which communication may or may not be delayed, and an indication of locations in which communications may or may not be delayed.
  • the processor 804 will allow or delay the application communication based on the determined delay criteria. In some embodiments, the processor 804 may determine additional delay criteria. If the processor 804 determines that the application communication should be allowed, the processor 804 continues to block 1225. If the processor 804 determines that the application communication should be delayed, the processor 804 continues to block 1210.
  • FIG. 13 shows another exemplary device 1300 configured to implement the communication access policy.
  • the device 1300 comprises a receiving module 1310, a delaying module 1320, and an allowing module 1330.
  • the receiving module 1310 may be configured to perform one or more of the functions discussed above with respect to the block 1205 illustrated in FIG. 12.
  • the receiving module 1310 may correspond to one or more of the receiver 812, the processor 804, the transceiver 814, and the memory 806, discussed above with respect to FIG. 8.
  • the receiving module 1310 may also correspond to one or more of the TX/RX radio 212 and the processor 202, discussed above with respect to FIG. 2.
  • the delaying module 1320 may be configured to perform one or more of the functions discussed above with respect to the block 1235 illustrated in FIG. 12.
  • the delaying module 1320 may correspond to one or more of the processor 804 and the transmitter 810, discussed above with respect to FIG. 8.
  • the delaying module 1320 may also correspond to one or more of the TX/RX radio 212, the connectivity engine 208, the networking module 210, and the processor 202, discussed above with respect to FIG. 2.
  • the allowing module 1330 may be configured to perform one or more of the functions discussed above with respect to the block 1225 illustrated in FIG. 12.
  • the allowing module 1330 may correspond to one or more of the processor 804 and the transmitter 810, discussed above with respect to FIG. 8.
  • the allowing module 1330 may also correspond to one or more of the TX/RX radio 212, the connectivity engine 208, the networking module 210, and the processor 202, discussed above with respect to FIG. 2.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • a general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • a software module may reside in Random Access Memory (RAM), flash memory, Read Only Memory (ROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor such that the processor may read information from, and write information to, the storage medium.
  • the storage medium may be integral to the processor.
  • the processor and the storage medium may reside in an ASIC.
  • the ASIC may reside in a user terminal.
  • the processor and the storage medium may reside as discrete components in a user terminal.
  • the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media may be any available media that may be accessed by a computer.
  • such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to carry or store desired program code in the form of instructions or data structures and that may be accessed by a computer.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
  • Disk and disc includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephone Function (AREA)
EP12784107.0A 2011-10-05 2012-10-05 Systeme und verfahren zur überwachung von hintergrundanwendungsereignissen Withdrawn EP2764734A1 (de)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201161543701P 2011-10-05 2011-10-05
US13/490,396 US8838086B2 (en) 2011-08-29 2012-06-06 Systems and methods for management of background application events
PCT/US2012/059102 WO2013052897A1 (en) 2011-10-05 2012-10-05 Systems and methods for management of background application events

Publications (1)

Publication Number Publication Date
EP2764734A1 true EP2764734A1 (de) 2014-08-13

Family

ID=48044207

Family Applications (1)

Application Number Title Priority Date Filing Date
EP12784107.0A Withdrawn EP2764734A1 (de) 2011-10-05 2012-10-05 Systeme und verfahren zur überwachung von hintergrundanwendungsereignissen

Country Status (6)

Country Link
EP (1) EP2764734A1 (de)
JP (1) JP5728623B2 (de)
KR (1) KR101488650B1 (de)
CN (1) CN103918320B (de)
BR (1) BR112014008257A2 (de)
WO (1) WO2013052897A1 (de)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9823928B2 (en) 2011-09-30 2017-11-21 Qualcomm Incorporated FIFO load instruction
CN104684049A (zh) * 2013-11-26 2015-06-03 中兴通讯股份有限公司 一种并发数据传输控制方法、装置及终端
KR101679138B1 (ko) * 2015-01-30 2016-11-23 주식회사 엘지유플러스 Nsrm 정책제공 시스템, 이동통신단말기 및 그 nsrm 정책 수신방법, 정책제공 서버 및 그 nsrm 정책제공 방법
US11146449B2 (en) 2016-02-19 2021-10-12 Intel Corporation Network architecture for internet-of-things device
US10310832B2 (en) 2016-02-19 2019-06-04 Intel Corporation Internet-of-things device blank
CN109426505B (zh) * 2017-08-16 2022-03-29 中国移动通信有限公司研究院 一种软件的安装方法、装置、电子设备及存储介质

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7506059B2 (en) 2001-10-26 2009-03-17 Nokia Corporation Mobile client provisioning web service
US8073436B2 (en) 2006-01-31 2011-12-06 Toshiba America Research, Inc. Applications and/or situation responsive utilization of silent periods
US20090049518A1 (en) * 2007-08-08 2009-02-19 Innopath Software, Inc. Managing and Enforcing Policies on Mobile Devices
JP2009182443A (ja) * 2008-01-29 2009-08-13 Ntt Docomo Inc 通信端末、動作モード管理プログラム、および動作モード管理方法
WO2010016849A1 (en) * 2008-08-08 2010-02-11 Innopath Software, Inc. Intelligent mobile device management client
JP2010183414A (ja) * 2009-02-06 2010-08-19 Sanyo Electric Co Ltd 電話装置
US8904206B2 (en) * 2010-01-26 2014-12-02 Motorola Mobility Llc Mobile computing device and method for maintaining application continuity
CN102186167B (zh) * 2011-04-11 2016-02-10 中兴通讯股份有限公司 一种对应用进行监控的方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2013052897A1 *

Also Published As

Publication number Publication date
WO2013052897A1 (en) 2013-04-11
KR101488650B1 (ko) 2015-01-30
BR112014008257A2 (pt) 2017-04-18
KR20140080526A (ko) 2014-06-30
CN103918320A (zh) 2014-07-09
JP5728623B2 (ja) 2015-06-03
CN103918320B (zh) 2016-07-06
JP2014533457A (ja) 2014-12-11

Similar Documents

Publication Publication Date Title
US8838086B2 (en) Systems and methods for management of background application events
US9178965B2 (en) Systems and methods for synchronization of application communications
US9264868B2 (en) Management of network access requests
US9571952B2 (en) Offloading of data to wireless local area network
EP2984789B1 (de) Anwendungsverkehrspaarung
KR101557843B1 (ko) 네트워크 액세스 요청들의 관리
KR20130121115A (ko) 네트워크에 대한 애플리케이션 액세스의 제어
KR101488650B1 (ko) 백그라운드 애플리케이션 이벤트들의 관리를 위한 시스템들 및 방법들
KR101723203B1 (ko) 통신 네트워크 내의 모바일 디바이스로의 애플리케이션 데이터의 전송 제어를 위한 장치 및 방법
KR20140117624A (ko) 우선순위 기반 세션을 위한 시스템들 및 방법들 및 이동성 관리 이중 우선순위 mtc 디바이스들
US20130028159A1 (en) Silent power-save mode for a wireless communication device
US20170086210A1 (en) Managing Inter-Radio Access Technology Procedure Concurrency

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20140328

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAX Request for extension of the european patent (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20170109

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20170520