EP2774331B1 - Systems and methods for synchronization of application communications - Google Patents
Systems and methods for synchronization of application communications Download PDFInfo
- Publication number
- EP2774331B1 EP2774331B1 EP11788657.2A EP11788657A EP2774331B1 EP 2774331 B1 EP2774331 B1 EP 2774331B1 EP 11788657 A EP11788657 A EP 11788657A EP 2774331 B1 EP2774331 B1 EP 2774331B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- application
- packet
- transmit
- delay tolerance
- indicative
- 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.)
- Not-in-force
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/41—Flow control; Congestion control by acting on aggregated flows or links
-
- 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/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/62—Establishing a time schedule for servicing the requests
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/50—Queue scheduling
- H04L47/56—Queue scheduling implementing delay-aware scheduling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/542—Intercept
-
- 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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/50—Service provisioning or reconfiguring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephone Function (AREA)
- Telephonic Communication Services (AREA)
Description
- The present application relates generally to wireless communications, and more specifically to systems, methods, and devices for synchronizing application communications.
- Applications ("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. For example, 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.
- There is an increased interest, however, in intelligently managing application communications. This is due, in part, to an increase in the number of multi-radio devices (e.g. 3G/Wi-Fi devices) and an increase in network traffic that may create capacity problems for operators, and power consumption problems for users. Thus, with respect to such capacity and power consumption problems, it may be desirable to delay communications during certain periods.
- Accordingly, there is a need for efficient and cost effective mechanisms to provide communication management for applications on wireless devices. Specifically, there is a need for systems and methods of managing policies regarding delayed transmission of communications.
- The systems, methods, and devices of the invention each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this invention as expressed by the claims which follow, some features will now be discussed briefly. After considering this discussion, and particularly after reading the section entitled "Description" one will understand how the features of this invention provide advantages that include management of application communication delay tolerance.
- One aspect of the disclosure provides a method of aggregating data for transmission. The method includes receiving information from an application via an application programming interface. The information is indicative of a transmit delay tolerance. The method further includes receiving, via the application programming interface, a packet from the application. The method further includes determining when to transmit the packet based on the received transmit delay tolerance.
- Another aspect of the disclosure provides a wireless device for aggregating data for transmission. The wireless device includes a processor configured to receive information from an application via an application programming interface. The information is indicative of a transmit delay tolerance. The processor is further configured to receive, via the application programming interface, a packet from the application. The wireless device further includes a network driver configured to determine when to transmit the packet based on the received transmit delay tolerance.
- Another aspect of the disclosure provides a wireless device for aggregating data for transmission. The wireless device includes means for receiving information from an application via an application programming interface. The information is indicative of a transmit delay tolerance. The wireless device further includes means for receiving, via the application programming interface, a packet from the application. The wireless device further includes means for determining when to transmit the packet based on the received transmit delay tolerance.
- Another aspect of the disclosure provides a non-transitory computer-readable medium having instruction encoded thereon which, when executed, cause an apparatus to perform a method of aggregating data for transmission. The method includes receiving information from an application, via an application programming interface. The information is indicative of a transmit delay tolerance. The method further includes receiving, via the application programming interface, a packet from the application. The method further includes determining when to transmit the packet based on the received transmit delay tolerance. Liu et al (Mobi Arch ' 11 - Proceedings of the sixth international workshop on MobiArch.) discloses utilizing energy from the trailing end of transmission pulses. G. Ananthanarayaran et al. discloses a communications API.
US2007/104162A1 discloses various embodiments relating to the use of timing or timing-related information for handling aggregated frames in a wireless network. - The foregoing aspects described herein will become more readily apparent by reference to the following Description when taken in conjunction with the accompanying drawings wherein:
-
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 ofFIG. 5 ; -
FIG. 7 shows a timeline of application communication aggregations, according to another embodiment; -
FIG. 8 shows an exemplary device configured to manage application communications; -
FIG. 9 shows a flowchart of an exemplary method of managing application communications; -
FIG. 10 shows another exemplary device configured to manage application communications. - Various aspects of the novel systems, apparatuses, and methods are described more fully hereinafter with reference to the accompanying drawings. The teachings disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein one skilled in the art should appreciate that the scope of the disclosure is intended to cover any aspect of the novel systems, apparatuses, and methods disclosed herein, whether implemented independently of or combined with any other aspect of the invention. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the invention is intended to cover such an apparatus or method which is practiced using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the invention set forth herein. It should be understood that any aspect disclosed herein may be embodied by one or more elements of a claim.
- Although particular aspects are described herein, many variations and permutations of these aspects fall within the scope of the disclosure. Although some benefits and advantages of the preferred aspects are mentioned, the scope of the disclosure is not intended to be limited to particular benefits, uses, or objectives. Rather, aspects of the disclosure are intended to be broadly applicable to different wireless technologies, system configurations, networks, and transmission protocols, some of which are illustrated by way of example in the figures and in the following description of the preferred aspects. The detailed description and drawings are merely illustrative of the disclosure rather than limiting, the scope of the disclosure being defined by the appended claims and equivalents thereof.
- The techniques described herein may be used for various wireless communication networks such as Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, Single-Carrier FDMA (SC-FDMA) networks, etc. The terms "networks" and "systems" are often used interchangeably. 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). 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. UTRA, E-UTRA, and GSM are part of Universal Mobile Telecommunication management system (UMTS). Long Term Evolution (LTE) is an upcoming release of UMTS that uses E-UTRA. 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). These various radio technologies and standards are known in the art. -
FIG. 1 shows anexemplary network environment 100 illustrating aspects of acommunication management system 108. Thenetwork environment 100 includes awireless device 102, acommunication network 104, and aserver 110. Thedevice 102 includes a plurality of radios/interfaces (not shown) to communicate with thenetwork 104 using corresponding radio/interface channels 106. Thedevice 102 also includes acommunication management system 108 that operates to control access to the plurality of radios/interfaces, for example by a particular application. - The
wireless device 102 may communicate with theserver 110 via thecommunication network 104. Theserver 110 connects to thecommunication network 104 via a communication channel 112. The communication channel 112 may be either a wired or wireless channel. - During operation, the
wireless device 102 executes applications which may interface with thenetwork 104 using any of the plurality of radios/interfaces. For example, an executing application may issue a networking function call, such as a socket layer call, to request a network resource for communication with thenetwork 104. In an embodiment, thecommunication management system 108 may process the socket layer call based on a default routing configuration to bind a pre-determined radio/interface resource to the application. - The application may transmit one or more packets of data, for example, via the communication channel 112 to the
server 110. In an embodiment, the application may include a transmit delay tolerance parameter in the transmitted packets. The transmit delay tolerance parameter may be included in, for example, a header of each packet. The transmit delay tolerance parameter may indicate an allowable delay for application communication. For example, applications that occasionally access theserver 110 for updates, such as social media applications, may be relatively delay-tolerant. On the other hand, interactive applications, such as video chat or web browsing applications, may be relatively delay-intolerant. - In various embodiments, the transmit delay tolerance parameter may indicate the allowable delay demarcated in a number of temporal units such as, for example, minutes, seconds, milliseconds, microseconds, symbols, clock ticks, frame periods, etc. In an embodiment, the transmit delay tolerance parameter may indicate the allowable delay demarcated as a relative priority value (e.g., high, medium, or low). In an embodiment, the transmit delay tolerance parameter may indicate a maximum allowable number of packets that may be delayed at one time. In various embodiments, the transmit delay tolerance parameter may indicate the maximum allowable number of delayed packets from a single application, or as an aggregate of all application traffic.
- The application may generate the transmit delay tolerance for a packet based on a number of factors, including user preferences, whether the application is running in the foreground or the background, or the time of day. The application can set the transmit delay tolerance differently for different types of packets, e.g., FIN packets or content packets. The transmit delay tolerance may be set for each packet individually or may be set by an application using an application programming interface (API) to define kernel metadata regarding future generated packets of a particular type.
- In various implementations, the
communication management system 108 operates to intercept packets from the application. For example, thecommunication management system 108 may receive packets from the application via an application programming interface (API). Thecommunication management system 108 may modify communications of the application according to the transmit delay tolerance parameter in each intercepted packet. As used herein, modification of communications can include, but is not limited to, delaying communications or otherwise impacting or affecting communications. - In embodiments where the
communication management system 108 delays communications according to the delay tolerance parameter, thecommunication management system 108 may disable one or more radios/interfaces in order to conserve power. After the delay, thecommunication management system 108 may power-up one or more disabled radios/interfaces. Thecommunication management system 108 may then bind the application to a network resource (i.e., the radio/interface that has been selected). A more detailed description of thecommunication management system 108 is provided below. -
FIG. 2 shows anexemplary wireless device 200 configured to provide communication management. Thedevice 200 includes aprocessor 202, amemory 204, and a TX/RX radio 212, all coupled to communicate using acommunication bus 214. Thewireless device 200 may be thewireless device 102, described above with respect toFIG. 1 . It should be noted that thedevice 200 is just one implementation and that other implementations are possible. - In one aspect, the
processor 202 includes anapplication layer module 206, aconnectivity engine 208, and anetworking module 210. Theprocessor 202 may also include at least one of a CPU, microprocessor, gate array, hardware logic, memory elements, and/or hardware executing software (not shown). Theprocessor 202 is configured to control the operation of thedevice 200 such that communications of applications executing on thedevice 200 may be selectively modified, impacted, delayed and/or bound to a desired radio. In one implementation, theprocessor 202 is configured to execute computer-readable instructions related to performing any of a plurality of functions. For example, theprocessor 202 operates to analyze information received or communicated from thedevice 200 to effectuate communication management. In another aspect, theprocessor 202 operates to generate information that may be utilized by thememory 204, theapplication layer module 206, the TX/RX radio 212, and/orconnectivity 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 thedevice 200 with a plurality of external entities, such as the external communication network 104 (FIG. 1 ) using a plurality ofradio channels 216. Theradio channels 216 may be, for example, theradio channels 106 described above with respect toFIG. 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 theradio channels 216. The radios/interfaces of the TX/RX radio 212 may be selectively enabled and disabled, for example to conserve power when there is no data to be transmitted. - The
application layer module 206 includes hardware and/or a processor executing software that is configured to execute one or more applications on thedevice 200 and to store the applications in thememory 204. In one implementation, theapplication layer module 206 is configured to allow applications to initiate networking function calls to thenetworking 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 theradio channels 216. - The
networking module 210 includes hardware and/or a processor executing software that is configured to perform networking functions. In one implementation, 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. For example, a particular radio/interface may be selected from the plurality of candidate radios provided by the TX/RX radio 212. In an embodiment, the Setsockopt() function may be used to set the delay tolerance parameter. In an aspect,networking module 210 is configured to perform a variety of networking functions or commands. In one aspect, thenetworking module 210 may allow certain functions to proceed, and may not allow other functions to proceed, based on, for example, the delay tolerance parameter. - The
connectivity engine 208 includes hardware and/or a processor executing software that is configured to assess system resources to manage communication from applications. In various implementations, theconnectivity 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. - 1. User Policy - policy set by the device user regarding radio access by applications executing at the device.
- 2. Operator Policy - policy set by network operators regarding network access by devices or applications.
- 3. Radio metrics - measurements of radio performance or other types of measurements that are used to select the most preferred radio for a particular application or operating environment.
- 4. Application requirements - requirements associated with requesting applications, such as bandwidth requirements or latency/performance requirements. Application requirements may include, for example, the delay tolerance parameter.
- 5. Network usability - information regarding the availability of a particular network on a particular radio interface.
- 6. 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.
- 7. 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 thememory 204. For example, theprocessor 202 may retrieve the operator policy and theconnectivity engine 208 may apply the operator policy. The operator policy may include a plurality of rules regulating network access by applications on thewireless 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 thedevice 200. In one implementation, thememory 204 is configured to store computer-readable instructions executed byprocessor 202. Thememory 204 may also be configured to store any of a plurality of other types of data including data generated by any of theprocessor 202, TX/RX radio 212,application layer module 206,networking module 210, and/orconnectivity engine 208. Thememory 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 uponmemory 204, such as compression and automatic back up. - The
memory 204 is configured to store apre-load library 218 and anetworking library 220. Thepre-load library 218 intercepts socket calls from applications. Thenetworking 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. For example, theconnectivity engine 208 may be configured to delay communication using one or more of the above selection criteria. For example, theconnectivity engine 208 may delay only communication from delay-tolerant applications, based on the delay tolerance parameter. - In an embodiment, the
connectivity engine 208 may delay communication based on whether thewireless device 200 is in an idle state. In an embodiment, theconnectivity engine 208 delays communication for delay-tolerant applications until thewireless device 200 enters an active state. In another embodiment, theconnectivity 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, theconnectivity engine 208 may be configured to select a radio using one or more of the above selection criteria. In an embodiment, theconnectivity engine 208 may selectively enable/disable one or more radios, for example, to save power when application communications are being delayed. When application communications are not being delayed, theconnectivity engine 208 binds the application to the interface representing that radio. For example, in one implementation, theconnectivity engine 208 binds the application to the radio's interface by calling into theoriginal networking library 220. Thus, functions at theconnectivity engine 208 and thepre-load library 218 may easily access functions, such as a bind() function, in thenetworking library 220 to bind to the radio that has been selected for the application. - In various implementations, 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. When the codes are executed by at least one processor, for instance,
processor 202, their execution causes theprocessor 202 to control thedevice 200 to provide the functions of the intelligent interface selection system described herein. For example, 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 thedevice 200. In another aspect, the sets of codes may be downloaded into thedevice 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 aflowchart 300 of an exemplary method of providing communication management. For clarity, theflowchart 300 is described below with reference to thedevice 200 shown inFIG. 2 . However, a person having ordinary skill in the art will appreciate that the illustrated method can be implemented with any suitable device. In one implementation, theprocessor 202 executes one or more sets of codes to control the functional elements of thedevice 200 to perform the functions described below. - At
block 302, theprocessor 202 launches an application. The application may be a legacy or non-legacy application that is part of theapplication layer module 206. For example, 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. - At
block 304, theprocessor 202 configures and loads a pre-load library. For example, thepre-load library 218 includes a subset of the networking functions that are provided in thenetworking library 220 used by applications to assess communication networks. The networking functions in thepre-load library 218 are configured to intercept networking function calls from applications executing at a device. For example, thepre-load library 218 includes POSIX socket functions that may be used to intercept socket calls by applications executing at thedevice 200. In one implementation, thepre-load library 218 in stored inmemory 204. - In one implementation, the
pre-load library 218 functions are configured to receive arguments passed from calling applications and use these arguments to generate a request to theconnectivity engine 208 to select the radio best suited for the application's purpose. - At
block 306, theprocessor 202 links the pre-load library into the execution environment. For example, theprocessor 202 links thepre-load library 218 into the execution environment at a higher priority than thenetworking library 220. Thus, networking functions calls by applications will be intercepted and processed by functions in thepre-load library 218 and not processed by similar functions in thenetworking library 220. - At
block 308, theprocessor 202 receives a packet from the application. Theprocessor 202 may also receive a transmit delay tolerance from the application. In an embodiment, the application may initiate transmission of the packet via an API using, for example, a networking function call. The networking function call may be a POSIX socket function call, such as the connect() function or the write() function. In an embodiment, the application may indicate a delay tolerance of the packet by setting the transmit delay tolerance. In an embodiment, the application may set the transmit delay tolerance using, for example, a setsockopt() function call. - In an embodiment, the application may generate the transmit delay tolerance for a packet based on a user preferences. For example, an application that receives periodic updates may allow a user to determine a minimum and maximum amount of time between updates. In another embodiment, the application may generate the transmit delay tolerance for a packet based whether the application is running in the foreground or the background. For example, the application may assign a lower delay tolerance when operating in the foreground, and a higher delay tolerance when operating in the background. In another embodiment, the application may generate the transmit delay tolerance for a packet based on the time of day. For example, the application may assign a higher delay tolerance to packets sent in the middle of the night.
- In certain embodiments, the application can set the transmit delay tolerance differently for different types of packets. For example, a Web browsing application may set a relatively high transmit delay tolerance for FIN packets, and a relatively low transmit delay tolerance for content packets. Accordingly, FIN packets might be delayed until content packets reach their delay tolerance. In various embodiments, different transmit delay tolerances can be assigned to different packet types including, SYN packets, FIN packets, and data packets.
- In an embodiment, the application may set the transmit delay tolerance for each packet individually. In another embodiment, the application may provide a delay policy via an application programming interface (API) to define kernel metadata regarding future generated packets of a particular type. The delay policy may include one or more rules, based on which the network stack may assign delay tolerances. For example, the application may provide a rule that the network stack should assign a particular delay tolerance to all FIN packets. The rules can include criteria including source application, destination host name, destination host address, source and destination port numbers, environment variables, etc.
- The application generates the networking function call to connect to a radio to allow communication with external networks. Due to the linking of the
pre-load library 218 into the execution environment at a higher priority than thenetworking library 220, theprocessor 202 intercepts (or processes) the networking function call via the functions in thepre-load library 218. In an embodiment, theprocessor 202 can delay the networking function call in accordance with the application delay parameter. Additional details are described herein, for example, with respect toFIG. 9 . - At
block 310, the called function in thepre-load library 218 generates a selection request to theconnectivity 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 theconnectivity engine 208 to select the appropriate radio for use by the application. In another embodiment, the called function in thepre-load library 218 generates a selection request to theconnectivity engine 208 to determine whether the communication should be delayed. - At
block 312, selection criteria are assessed. In one implementation, theconnectivity engine 208 operates to assess the selection criteria described above. For example, theconnectivity engine 208 may communicate with theprocessor 202 to assess Operator Policies that are part of the selection criteria. - At
block 314, theconnectivity engine 208 selects a radio based on the assessment of the selection criteria. For example, theconnectivity engine 208 operates to select the radio that best matches the selection criteria. - At
block 316, theconnectivity engine 208 binds to the radio's interface that has been selected for the application. For example, in one implementation, theconnectivity engine 208 calls a bind() function of thenetworking library 220 to bind to the radio that has been selected for the application. For example, theconnectivity engine 208 is aware of thenetworking library 220 and how to access its functions directly without being intercepted by thepre-load library 218. In an embodiment, theconnectivity engine 208 delays communication prior or post to binding the application to the radio. In an embodiment, binding the radio may include enabling or powering-up a disabled or powered-down radio after delaying application communications. - At
block 318, the application then utilizes the radio that has been selected for network communications. - In an optional operation, 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 theconnectivity engine 208 determines after another assessment of the selection criteria that a radio other than the current radio best matches the selection criteria, then theconnectivity 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. - Therefore, the
flowchart 300 provides communication management for use with legacy and non-legacy applications. It should be noted that theflowchart 300 is just one implementation and that the operations of theflowchart 300 may be rearranged or otherwise modified such that other implementations are possible. - In wireless devices such as smart phones, personal digital assistants, etc., software applications may run in the background, and may initiate network activity every few minutes. For example, a mailer application may cause the network driver to wake up the modem to transmit information every three minutes. A financial tracker application may cause the network driver to wake up the modem to transmit information every two minutes. Because of the different periods (and relative phases), the modem is woken more frequently than every two minutes, wasting power. Applications such as social networking applications, email or other communication applications, data feeds, etc. (popular examples include Facebook, Gmail, Market, Twitter, etc.) may send and receive data with varied periodicity.
-
FIG. 4 shows agraph 400 of application network activity for an exemplary device. The x-axis of thegraph 400 shows time, and the y-axis shows an amount of data transferred, in bytes, at each time. Thegraph 400 shows network activity during an approximately two-hour period, during which the device is in an idle mode. In an embodiment, the device is in an idle mode when a user does not interact with the device and/or a display is off. Although the device is in the idle mode, applications that continue to operate create spikes in activity, for example, first application 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 inradio 212, etc. - Network activity spikes, such as first application spikes 410a-i, may cause the wireless device to transition from the idle mode to a connected mode. 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. In some cases, 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. 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. Moreover, different applications may generate traffic at different times, potentially increasing the number of times the radio powers-up, or increasing the amount of time the radio stays powered-up. For example, second application spikes 420a-e do not occur at the same times as the first application spikes 410a-i.
- Employing the techniques and structures disclosed herein, 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. By aggregating such tasks/data requests, frequent waking of the wireless device may be reduced and other communication resources conserved during periods where the user is not actively engaging with the device.
-
FIG. 5 shows an exemplary block diagram of a hardware/software system 500 configured to aggregate application communication. As shown, the software components are divided between anapplication processor 550 and amodem processor 560, but the various functionalities may be organized differently from the example ofFIG. 5 . For example, functions described as software may be implemented in hardware and vice versa, functions may be distributed differently between components, etc. In an embodiment, the hardware/software system 500 may be thecommunication management system 108, discussed above with respect toFIG. 1 . In another embodiment, thehardware software system 500 may be implemented on thewireless device 200, described above with respect toFIG. 2 . For example, functions of theapplication processor 550 may be implemented by one or more of theprocessor 202, theapplication layer module 206, and/or theconnectivity engine 208. Functions of themodem processor 560 may be implemented by one or more of the TX/RX radio 212, thenetworking module 210, and/or theconnectivity engine 208. - In the illustrated embodiment,
applications 502 interact with anapplication connection engine 508 and with a high level operating system (HLOS) 506. TheHLOS 506 may be, for example, the Android operating system produced by Google Inc., Mountain View, CA. Theapplication connection engine 508 may communicate with amodem connection engine 510. The modem connection engine may manage communication resources such as aradio 212 and the radios therein. Thewrapper 504 is capable of capturing data between theapplications 502 and theHLOS 506. Thewrapper 504 may aggregate data from theapplications 502 during a period of user inactivity and hold them until a determined time before releasing them to theHLOS 506 and ultimately theradio 212 for operation/transmission. Thewrapper 504 may be invisible to theapplications 502 such that they are unaware that their data/requests are being held/aggregated. In an embodiment, thewrapper 504 may emulate functions of theHLOS 506. Thewrapper 504 may be a separate component or may be incorporated into another component such as theapplication connection engine 508. For example, thewrapper 504 may be implemented by theconnectivity engine 208, described above with respect toFIG. 2 . -
FIG. 6 shows anexemplary timeline 600 of application communication aggregation implemented by the hardware/software system 500 ofFIG. 5 . As shown, applications APP 1-4 each initiate a request for use of a radio resource in succession during anaggregation period 610. In an embodiment, application communication may be delayed during theaggregation period 610. In an embodiment, theaggregation period 610 can include a period in which thedevice 200 and/or the TX/RX radio 212 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. - In the illustrated embodiment, the
application APP 1 transmits a packet, which may include a first transmit delay tolerance. Then, theapplication APP 2 transmits a packet, which may include a second transmit delay tolerance. Next, theapplication APP 3 transmits a packet, which may include a third transmit delay tolerance. Finally, theapplication APP 4 transmits a packet, which may include a fourth transmit delay tolerance. Thewrapper 504 receives the packets (for example, via API calls such as connect() and write() socket calls). Instead of acting on the socket calls immediately, thewrapper 504 delays the communication during theaggregation period 610. At a determined time, thewrapper 504 releases the socket calls together, as aggregatedpackets 620. - In an embodiment, the
wrapper 504 may release the aggregatedpackets 620 during a transmitwindow 630. In various embodiments, the transmitwindow 630 may include a period in which thedevice 200 is in the idle mode, and may include a period in which thedevice 200 is in the active mode. During the transmitwindow 630, one or more radio interfaces (such as, for example TX/RX radio 212) may be enabled or powered-up. Thewrapper 504 may release aggregatedpackets 620 from APPs 1-4. Thewrapper 504 may also allow application communications requests made during the transmitwindow 630 to proceed without delay. In other words, during the transmitwindow 630, thewrapper 504 may not delay further communication. For example, in the illustrated embodiment,APP 5 transmits a packet, which may include a fifth transmit delay tolerance, during the transmitwindow 630. Thewrapper 504 packet received fromAPP 5 to proceed without delay. - In an embodiment,
wrapper 504 may open the transmitwindow 630 at regular or intermittent intervals. For example, thewrapper 504 may open transmitwindow 630, once every 5 minutes, 10 minutes, 15 minutes, 30 minutes, 60 minutes, etc. In another example, thewrapper 504 may release delayed application communications at a random or pseudo-random time. The intervals at which thewrapper 504 opens the transmitwindow 630 may be determined by thedevice 200 or received from another device, such as the server 110 (FIG. 1 ). - In an embodiment, the
wrapper 504 can determine when to open the transmitwindow 630 dynamically, based on the aggregatedpackets 620. For example, thewrapper 504 can open the transmit window when any of the aggregatedpackets 620 has experienced a delay equal to its transmit delay tolerance. In other words, once a single delayed packet has reached a threshold delay (e.g., the transmit delay tolerance), all delayed packets may be released. As another example, thewrapper 504 can open the transmitwindow 630 when the number of aggregatedpackets 620 surpasses a threshold. The threshold can be determined by thedevice 200 or received from another device, such as theserver 110. - The
wrapper 504 can keep the transmitwindow 630 open for a predetermined or dynamic period of time. For example, thewrapper 504 may keep the transmitwindow 630 open for 15 seconds, 30 seconds, 1 minute, 5 minutes, etc., after the transmitwindow 630 is opened. As another example, thewrapper 504 may keep the transmitwindow 630 open for 15 seconds, 30 seconds, 1 minute, 5 minutes, etc., after the last application communication is transmitted. The amount of time which thewrapper 504 keeps the transmitwindow 630 open may be determined by thedevice 200 or received from another device, such as theserver 110. When the transmitwindow 630 is closed, one or more radio interfaces (such as, for example TX/RX radio 212) may be disabled or powered-down. - In an embodiment, the
wrapper 504 can close the transmitwindow 630 after all aggregatedpackets 620 have been transmitted. In another embodiment, thewrapper 504 can close the transmitwindow 630 after all aggregatedpackets 620 that have been delayed longer than a threshold value have been transmitted. The threshold value for each packet may be the transmit delay tolerance. In various embodiments, the threshold delay value for each packet can be that packet's transmit delay tolerance, modified by a safety factor. For example, the threshold delay value for each packet can be that packet's transmit delay tolerance divided by a constant, or minus a constant. - In an embodiment, the
wrapper 504 may open the transmitwindow 630 when a delay-intolerant application initiates communication. For example,APP 5 may be a delay-intolerant application. Accordingly, thewrapper 504 may open the transmitwindow 630 when a packet is received fromAPP 5. Thewrapper 504 may allow the packet fromAPP 5 to proceed, and may also release the aggregatedpackets 620 from the APPs 1-4. -
FIG. 7 shows atimeline 700 of application communication aggregations, according to another embodiment. As shown, 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. For example, the application APP 1-2 may include background activity and/or requirements for operation that are only tolerant of specific delays. For example, the applications APP 1-2 may be location tracking applications that report the location of thedevice 200 periodically, such as every 10 seconds. - As shown, the
application APP 1 initiates a communication request, and indicates to thewrapper 504 that it will only tolerate an X-second delay. Next, theapplication APP 2 initiates a communication request, and indicates to thewrapper 504 that it will only tolerate a Y-second delay. Thewrapper 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. - As shown, the
wrapper 504 provides the API.Go callback to theapplication APP 1 before the X-second delay has elapsed. Theapplication APP 1 then communicates through thewrapper 504, without further delay. Similarly, thewrapper 504 provides the API.Go callback to theapplication APP 2 before the Y-second delay has elapsed. Theapplication APP 2 then communicates through thewrapper 504, without further delay. - In an alternative embodiment, applications may provide the
wrapper 504 with specific transmission deadlines via the API. Thewrapper 504 may transparently delay communication from the applications, within the constraints of the provided deadlines. Accordingly, thewrapper 504 will allow the application communication to proceed prior to any deadlines. - In yet another aspect, 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. In an embodiment, the
wrapper 504 may learn the delay tolerance of various applications by monitoring the application communications. In another embodiment, thewrapper 504 may receive a list of transmit delay tolerances from a list or database, either stored locally on thedevice 102 or received from theserver 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. Thewrapper 504 may analyze a variety of factors to determine when to delay or aggregate application communication. For example, thewrapper 504 may delay application communication based on characteristics of thewireless device 102 such as a display state (on or off), an audio state (on or off), etc. Thewrapper 504 may only delay application communications known to be tolerant of delay. Thewrapper 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.). A person having ordinary skill in the art would appreciate that thewrapper 504 may determine when to delay application communication based on any combination of the above factors, in addition to other suitable factors. - Moreover, the
wrapper 504 may analyze a variety of factors to determine when to release delayed or aggregated communication and to permit unrestricted application communication. For example, a delay-intolerant application (such as, for example, an emergency notification application) may initiate an unrestricted application communication. The unrestricted application communication may trigger thewrapper 504 to release previously delayed or aggregated application communications. Accordingly, previously delayed application communications may use radio resources in conjunction with the emergency application. In other words, thewrapper 504 may open a transmit window for all applications when a delay-intolerant application communication is initiated. - In an embodiment, 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. For example, thewrapper 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. - In another embodiment, 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. For example, thewrapper 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. - In an embodiment, the
wrapper 504 releases delayed or aggregated application communications when user interaction is received. For example, thewrapper 504 may release delayed application communications when a display is activated, a button press is detected, etc. In another embodiment, thewireless device 102 may anticipate user interaction. For example, thewireless device 102 may include an accelerometer that may detect movement of thewireless device 102. Thewrapper 504 may release delayed application communications when accelerometer output indicates a likelihood of imminent user interaction. In another example, thewireless device 102 may anticipate user interaction via a proximity detector. A person having ordinary skill in the art will appreciate that thewrapper 504 may release delayed application communications in response to any combination of the above, and additionally in response to any other suitable event. - Although the preceding description discusses application communication aggregation and delay with respect to an API, the concepts equally apply in hardware, firmware, or any combination of hardware and software.
-
FIG. 8 shows anexemplary device 802 configured to manage application communications. The device may be employed within thenetwork environment 100, described above with respect toFIG. 1 . Thedevice 802 is an example of a device that may be configured to implement the various methods described herein. For example, thedevice 802 may implement one or more functions of thewireless device 102. In another embodiment, thedevice 802 may implement one or more functions of theserver 110. - The
device 802 may include aprocessor 804 which controls operation of thedevice 802. Theprocessor 804 may also be referred to as a central processing unit (CPU). Thememory 806, which may include both read-only memory (ROM) and random access memory (RAM), provides instructions and data to theprocessor 804. A portion of thememory 806 may also include non-volatile random access memory (NVRAM). Theprocessor 804 may perform logical and arithmetic operations based on program instructions stored within thememory 806. The instructions in thememory 806 may be executable to implement the methods described herein. - When the
device 802 is implemented or used as thewireless device 102, theprocessor 804 may be configured to execute one or more applications, which may be stored in thememory 806. During execution, the applications may initiate communication over thetransceiver 814, thetransmitter 810, and/or thereceiver 812. Theprocessor 804 may implement the hardware/software system 500, described above with respect toFIG. 5 . For example, theprocessor 804 may manage application communications as described above with respect toFIGs. 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 ahousing 808 that may include atransmitter 810 and/or areceiver 812 to allow transmission and reception of data between thedevice 802 and a remote location. Thetransmitter 810 andreceiver 812 may be combined into atransceiver 814. Anantenna 816 may be attached to thehousing 808 and electrically coupled to thetransceiver 814. In some embodiments, theantenna 816 may be omitted, and thedevice 802 may be configured for wired communication. Thedevice 802 may also include (not shown) multiple transmitters, multiple receivers, multiple transceivers, and/or multiple antennas. - The
device 802 may also include asignal detector 818 that may be used in an effort to detect and quantify the level of signals received by thetransceiver 814. Thesignal detector 818 may detect such signals as total energy, energy per subcarrier per symbol, power spectral density and other signals. Thedevice 802 may also include a digital signal processor (DSP) 820 for use in processing signals. TheDSP 820 may be configured to generate a packet for transmission. In some aspects, the packet may comprise a physical layer data unit (PPDU). - The
device 802 may further comprise auser interface 822 in some aspects. Theuser 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, and/or a display. Theuser interface 822 may include any element or component that conveys information to a user of thedevice 802 and/or receives input from the user. In an embodiment, theuser interface 822 may be considered active when it is receiving input, or sending output (for example, from a USB port, to a display, from a microphone, etc.). Theuser 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.). Theuser interface 822 may be considered inactive or idle when it is not active. - When the
user interface 822 receives no input, thedevice 802 may be said to be in an idle state, or an idle mode. In the idle state, a display may be off, and one or more functions of thedevice 802 may be disabled. In an embodiment, processes and communications of thedevice 802 that are not initiated in response touser interface 822 input may be referred to as background or idle processes or communications. - When the
user interface 822 receives input, thedevice 802 may be said to be in an active state, or an active mode. In the active 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. In an embodiment, background processes and communications may occur in the active mode, but may not be initiated in direct response touser interface 822 input. - The various components of the
device 802 may be coupled together by abus system 826. Thebus 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. Those of skill in the art will appreciate the components of thedevice 802 may be coupled together or accept or provide inputs to each other using some other mechanism. - Although a number of separate components are illustrated in
FIG. 8 , those of skill in the art will recognize that one or more of the components may be combined or commonly implemented. For example, theprocessor 804 may be used to implement not only the functionality described above with respect to theprocessor 804, but also to implement the functionality described above with respect to thesignal detector 818 and/or theDSP 820. Further, each of the components illustrated inFIG. 8 may be implemented using a plurality of separate elements. -
FIG. 9 shows aflowchart 900 of an exemplary method of managing application communications. In one embodiment, one or more aspects of theflowchart 900 can correspond to block 308 ofFIG. 3 . Although the method offlowchart 900 is described herein with reference to thedevice 802 discussed above with respect toFIG. 8 , a person having ordinary skill in the art will appreciate that the method offlowchart 900 may be implemented by thewireless device 102 discussed above with respect toFIG. 1 , thewireless device 202 discussed above with respect toFIG. 2 , and/or any other suitable device. In an embodiment, the steps inflowchart 900 may be performed by the processor 805 in conjunction with thetransmitter 810, thereceiver 812, thememory 806, and theuser interface 822. Although the method offlowchart 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. - First, at
block 910, thedevice 802 receives the transmit delay tolerance from an application. In an embodiment, the transmit delay tolerance is received in a packet. In an embodiment, the transmit delay tolerance is received via the API described above. Theprocessor 804 may store the transmit delay tolerance in thememory 806. In an embodiment, thedevice 802 receives the transmit delay tolerance from theserver 110. As discussed above with respect toFIGs. 7-8 , the transmit delay tolerance may specify how thedevice 802 should delay application communication. - Next, at
block 920, theprocessor 804 receives one or more communications (e.g. a packet) from an application executing on theprocessor 804. Theprocessor 804 may intercept the communications via facilities described above with respect to thecommunication management system 108 and/or theconnectivity engine 208. In an embodiment, theDSP 820, thesignal detector 818, thetransmitter 810, and/or thetransceiver 814 may intercept the communications. When the packet is received, the transceiver 814 (including one or more of thetransmitter 810 and the receiver 812) may be in a powered-off, disabled, inactive, and/or idle state. - Then, at
block 930, theprocessor 804 determines when to transmit the packet. For example, theprocessor 804 may determine a delay threshold as described above with respect toFIGs. 6-7 . In an embodiment, theprocessor 804 may determine when to open and close the transmitwindow 630. Subsequently, atblock 940, theprocessor 804 transmits the packet via thetransmitter 810 at the time determined atblock 930. Before the packet is transmitted, theprocessor 804 may power-on, enable, and/or activate thetransceiver 814. -
FIG. 10 shows anotherexemplary device 1000 configured to manage application communications. Thedevice 1000 comprises areceiving module 1010, a determiningmodule 1020, and atransmitting module 1030. Thereceiving module 1010 may be configured to perform one or more of the functions discussed above with respect to theblock 910 and/or theblock 920 illustrated inFIG. 9 . Thereceiving module 1010 may correspond to one or more of thereceiver 812, theprocessor 804, thetransceiver 814, and thememory 806, discussed above with respect toFIG. 8 . Thereceiving module 1010 may also correspond to one or more of the TX/RX radio 212 and the processor 202 (including theapplication layer module 206, thenetworking module 210, and the connectivity engine 208), discussed above with respect toFIG. 2 . - The determining
module 1020 may be configured to perform one or more of the functions discussed above with respect to theblock 930 illustrated inFIG. 9 . The determiningmodule 1020 may correspond to one or more of theprocessor 804, theDSP 820, and thememory 808 discussed above with respect toFIG. 8 . The determiningmodule 1020 may also correspond to one or more of theprocessor 202 and thememory 204 discussed above with respect toFIG. 2 . - The
transmitting module 1030 may be configured to perform one or more of the functions discussed above with respect to theblock 940 illustrated inFIG. 9 . Thetransmitting module 1030 may correspond to one or more of theprocessor 804 and thetransmitter 810, discussed above with respect toFIG. 8 . Thetransmitting module 1030 may correspond to one or more of thetransmitter 810, theprocessor 804, thetransceiver 814, and thememory 806, discussed above with respect toFIG. 8 . Thetransmitting module 1030 may also correspond to one or more of the TX/RX radio 212 and theprocessor 202, discussed above with respect toFIG. 2 . - Those of skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
- Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the exemplary embodiments of the invention.
- The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. 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.
- The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. 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. In the alternative, 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. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.
- In one or more exemplary embodiments, 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. By way of example, and not limitation, 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. Also, any connection is properly termed a computer-readable medium. For example, if 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, then 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, as used herein, 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.
- The previous description of the disclosed exemplary embodiments is provided to enable any person skilled in the art to make or use the invention. Various modifications to these exemplary embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the scope of the invention. Thus, the invention is not intended to be limited to the exemplary embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
- It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.
- While the foregoing is directed to aspects of the present disclosure, other and further aspects of the disclosure may be devised without departing from the basic scope thereof, and the scope thereof is determined by the claims that follow.
Claims (13)
- A method of aggregating data for transmission, the method comprising:receiving (910) information from an application, via an application programming interface, indicative of a transmit delay tolerance;receiving, (920) via the application programming interface, a packet from the application;determining (930) when to transmit the packet based on the received transmit delay tolerance; and characterised in that:
determining when to transmit the packet comprises aggregating multiple packets and determining dynamically to open a transmit window until all aggregated packets have been transmitted, when at least one of the aggregated packets has experienced a delay equal to its transmit delay tolerance. - The method of claim 1, wherein receiving information from the application indicative of a transmit delay tolerance comprises retrieving information from a memory written by the application via the application programming interface.
- The method of claim 1, wherein receiving information from the application indicative of a transmit delay tolerance comprises receiving a header of the packet.
- The method of claim 1, wherein the information indicative of transmit delay tolerance comprises information indicative of a number of temporal units.
- The method of claim 1, wherein determining when to transmit the packet of data is based on whether an amount of time elapsed from receiving the packet of data exceeds an amount of time based on the transmit delay tolerance.
- The method of claim 1, wherein receiving information indicative of a transmit delay tolerance comprises receiving information from the application, via the application programming interface, indicative of a first transmit delay tolerance associated with a first type of packet and receiving information from the application, via the application programming interface, indicative of a second transmit delay tolerance associated with a second type of packet, wherein receiving the packet comprises determining whether the packet is of the first type or of the second type, and wherein determining when to transmit the packet comprises determining when to transmit the packet based on the determined type of the packet.
- A wireless device for aggregating data for transmission, the wireless device comprising:means for receiving (910) information from an application, via an application programming interface, indicative of a transmit delay tolerance;means for receiving (920), via the application programming interface, a packet from the application;means for determining (930) when to transmit the packet based on the received transmit delay tolerance; and characterised in that:
the means for determining when to transmit the packet comprises means for aggregating multiple packets and determining dynamically to open a transmit window until all aggregated packets have been transmitted, when at least one of the aggregated packets has experienced a delay equal to its transmit delay tolerance. - The wireless device of claim 7, wherein the means for receiving information from the application indicative of a transmit delay tolerance comprises means for retrieving information from a memory written by the application via the application programming interface.
- The wireless device of claim 7, wherein the means receiving information from the application indicative of a transmit delay tolerance comprises means for receiving a header of the packet.
- The wireless device of claim 7, wherein the information indicative of transmit delay tolerance comprises information indicative of a number of temporal units.
- The wireless device of claim 7, wherein determining when to transmit the packet of data is based on whether an amount of time elapsed from receiving the packet of data exceeds an amount of time based on the transmit delay tolerance.
- The wireless device of claim 7, wherein the means receiving information indicative of a transmit delay tolerance comprises means for receiving information from the application, via the application programming interface, indicative of a first transmit delay tolerance associated with a first type of packet and receiving information from the application, via the application programming interface, indicative of a second transmit delay tolerance associated with a second type of packet, wherein the means for receiving the packet comprises means for determining whether the packet is of the first type or of the second type, and wherein the means for determining when to transmit the packet comprises means for determining when to transmit the packet based on the determined type of the packet.
- A non-transitory computer-readable medium having instruction encoded thereon which, when executed, cause an apparatus to perform the method of any of claims 1 to 6.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/288,928 US9178965B2 (en) | 2011-03-18 | 2011-11-03 | Systems and methods for synchronization of application communications |
PCT/US2011/059445 WO2013066354A1 (en) | 2011-11-03 | 2011-11-04 | Systems and methods for synchronization of application communications |
Publications (2)
Publication Number | Publication Date |
---|---|
EP2774331A1 EP2774331A1 (en) | 2014-09-10 |
EP2774331B1 true EP2774331B1 (en) | 2018-06-27 |
Family
ID=45048219
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP11788657.2A Not-in-force EP2774331B1 (en) | 2011-11-03 | 2011-11-04 | Systems and methods for synchronization of application communications |
Country Status (6)
Country | Link |
---|---|
US (1) | US9178965B2 (en) |
EP (1) | EP2774331B1 (en) |
JP (1) | JP5863217B2 (en) |
KR (1) | KR101604204B1 (en) |
CN (1) | CN104025536B (en) |
WO (1) | WO2013066354A1 (en) |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9603085B2 (en) | 2010-02-16 | 2017-03-21 | Qualcomm Incorporated | Methods and apparatus providing intelligent radio selection for legacy and non-legacy applications |
WO2013015835A1 (en) | 2011-07-22 | 2013-01-31 | Seven Networks, Inc. | Mobile application traffic optimization |
US8831658B2 (en) | 2010-11-05 | 2014-09-09 | Qualcomm Incorporated | Controlling application access to a network |
US9264868B2 (en) | 2011-01-19 | 2016-02-16 | Qualcomm Incorporated | Management of network access requests |
US9571952B2 (en) | 2011-04-22 | 2017-02-14 | Qualcomm Incorporatd | Offloading of data to wireless local area network |
US9137737B2 (en) | 2011-08-29 | 2015-09-15 | Qualcomm Incorporated | Systems and methods for monitoring of background application events |
US9356804B1 (en) * | 2012-06-12 | 2016-05-31 | Amazon Technologies, Inc. | Policy-based network connection resource selection |
CN103582170B (en) * | 2012-07-23 | 2018-08-10 | 百度在线网络技术(北京)有限公司 | The method and apparatus of communication connection is provided for multiple candidate applications in a mobile device |
US9565637B2 (en) | 2013-03-14 | 2017-02-07 | T-Mobile Usa, Inc. | High power channel state notification for mobile applications |
US10216549B2 (en) | 2013-06-17 | 2019-02-26 | Seven Networks, Llc | Methods and systems for providing application programming interfaces and application programming interface extensions to third party applications for optimizing and minimizing application traffic |
US20150023161A1 (en) | 2013-07-22 | 2015-01-22 | Seven Networks, Inc. | Modifying system timers for optimizing mobile traffic management |
CN104780183B (en) * | 2014-01-09 | 2019-07-05 | 腾讯科技(深圳)有限公司 | A kind of information sharing method, device and electronic equipment |
JP6477040B2 (en) * | 2015-03-06 | 2019-03-06 | 日本電気株式会社 | Communication terminal, communication method, and program |
JP6679658B2 (en) * | 2018-06-01 | 2020-04-15 | ソニー株式会社 | Mobile terminal, system and method for protocol mode switching |
TWI713333B (en) * | 2020-01-15 | 2020-12-11 | 聚騰科技股份有限公司 | Data transmission and reception methods |
CN111773714B (en) * | 2020-07-09 | 2024-01-19 | 网易(杭州)网络有限公司 | Game skill configuration method and device and game skill control method and device |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070104162A1 (en) * | 2005-11-10 | 2007-05-10 | Kneckt Jarkko L S | Use of timing information for handling aggregated frames in a wireless network |
Family Cites Families (102)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5737687A (en) | 1995-03-01 | 1998-04-07 | Qualcomm Incorporated | Self-attenuating RF transceiver system using antenna and modem interfaces and cable link |
GB2301751B (en) | 1995-06-02 | 2000-02-09 | Dsc Communications | Control message transmission in telecommunications systems |
US6115744A (en) | 1996-07-30 | 2000-09-05 | Bea Systems, Inc. | Client object API and gateway to enable OLTP via the internet |
JP3420006B2 (en) | 1996-12-18 | 2003-06-23 | 株式会社東芝 | Data transmission device and communication system using the same |
US6122514A (en) | 1997-01-03 | 2000-09-19 | Cellport Systems, Inc. | Communications channel selection |
US5842114A (en) | 1997-02-12 | 1998-11-24 | Interdigital Technology Corporation | Global channel power control to minimize spillover in a wireless communication environment |
US7013284B2 (en) | 1999-05-04 | 2006-03-14 | Accenture Llp | Component based interface to handle tasks during claim processing |
JP3389951B2 (en) | 2000-02-07 | 2003-03-24 | 日本電気株式会社 | CDMA mobile communication system and downlink transmission power control method in the CDMA mobile communication system |
US7260635B2 (en) | 2000-03-21 | 2007-08-21 | Centrisoft Corporation | Software, systems and methods for managing a distributed network |
EP3024283A1 (en) | 2000-04-03 | 2016-05-25 | Nokia Technologies Oy | Determining which plurality of cells a mobile station is associated with in idle state |
US7107063B1 (en) | 2000-05-03 | 2006-09-12 | International Business Machines Corporation | Selective display of display information packets in a packet-based communication medium |
JP2001339465A (en) | 2000-05-26 | 2001-12-07 | Mitsubishi Electric Corp | Message flow control method and communication system |
US7418489B2 (en) | 2000-06-07 | 2008-08-26 | Microsoft Corporation | Method and apparatus for applying policies |
CA2421609A1 (en) | 2000-09-12 | 2002-03-21 | Netmotion Wireless, Inc. | Method and apparatus for providing mobile and other intermittent connectivity in a computing environment |
JP2002091841A (en) | 2000-09-13 | 2002-03-29 | Sanyo Electric Co Ltd | Network system and equipment recognizing method |
JP2002203017A (en) * | 2000-10-30 | 2002-07-19 | Mitsubishi Electric Corp | System for managing food supply, server and terminal used for system |
US6718176B2 (en) | 2001-03-01 | 2004-04-06 | Nokia Corporation | Apparatus, and associated method, for displaying positional data associated with mobile stations of a radio communication system |
GB2373887A (en) | 2001-03-28 | 2002-10-02 | Hewlett Packard Co | Context dependent operation, including power management, of a mobile computer |
US7433922B2 (en) | 2001-05-11 | 2008-10-07 | Varia Llc | Method and system for collecting and displaying aggregate presence information for mobile media players |
US7506059B2 (en) | 2001-10-26 | 2009-03-17 | Nokia Corporation | Mobile client provisioning web service |
US7065367B2 (en) | 2002-07-11 | 2006-06-20 | Oliver Michaelis | Interface selection in a wireless communication network |
US6961595B2 (en) | 2002-08-08 | 2005-11-01 | Flarion Technologies, Inc. | Methods and apparatus for operating mobile nodes in multiple states |
WO2004064333A1 (en) | 2003-01-10 | 2004-07-29 | Sharp Kabushiki Kaisha | Communication device, network system, communication management method, request signal, response signal, program, and recording medium containing the program |
US7228563B2 (en) | 2003-02-06 | 2007-06-05 | Symantec Corporation | Shell code blocking system and method |
JP3902560B2 (en) | 2003-03-25 | 2007-04-11 | 三洋電機株式会社 | Channel allocation method and base station apparatus and communication system using the same |
EP1634468A4 (en) | 2003-06-18 | 2011-03-30 | Qualcomm Inc | System and method for gsm hard handoff |
US20040264396A1 (en) | 2003-06-30 | 2004-12-30 | Boris Ginzburg | Method for power saving in a wireless LAN |
US20050060583A1 (en) | 2003-07-15 | 2005-03-17 | Jeou-Kai Lin | System and method for advanced intrusion avoidance |
KR100557468B1 (en) | 2003-12-17 | 2006-03-07 | 한국전자통신연구원 | Socket Compatibility Layer for TOE |
US20050182958A1 (en) | 2004-02-17 | 2005-08-18 | Duc Pham | Secure, real-time application execution control system and methods |
US7610057B2 (en) | 2004-04-23 | 2009-10-27 | Microsoft Corporation | Selecting a wireless networking technology on a device capable of carrying out wireless network communications via multiple wireless technologies |
US7664838B2 (en) | 2004-05-10 | 2010-02-16 | Nortel Networks Limited | System and method for translating application program network service requests into actions and performing those actions through the management and/or control plane responsive to previously defined policies and previous requests by the same or another application program |
US20060217116A1 (en) | 2005-03-18 | 2006-09-28 | Cassett Tia M | Apparatus and methods for providing performance statistics on a wireless communication device |
EP1705855B1 (en) | 2005-03-22 | 2011-12-14 | Swisscom AG | Method and System for establishing a Peer-to-peer communications channel |
US7486954B2 (en) | 2005-03-25 | 2009-02-03 | Alcatel-Lucent Usa Inc. | Method of controlling load sharing between in-cell and soft handoff users |
US20060229025A1 (en) * | 2005-03-30 | 2006-10-12 | Lucent Technologies Inc. | Method for extracting optimal reverse link capacity by scaling reverse link Eb/No setpoint based on aggregate channel load and condition |
US20060221953A1 (en) | 2005-04-01 | 2006-10-05 | Claude Basso | Method and apparatus for blind checksum and correction for network transmissions |
US8526463B2 (en) | 2005-06-01 | 2013-09-03 | Qualcomm Incorporated | System and method to support data applications in a multi-homing, multi-mode communication device |
US8024785B2 (en) | 2006-01-16 | 2011-09-20 | International Business Machines Corporation | Method and data processing system for intercepting communication between a client and a service |
EP3177081B1 (en) | 2006-01-17 | 2018-03-14 | Telefonaktiebolaget LM Ericsson (publ) | Method and arrangement for reducing power consumption in a mobile communication network |
US8073436B2 (en) | 2006-01-31 | 2011-12-06 | Toshiba America Research, Inc. | Applications and/or situation responsive utilization of silent periods |
US7769887B1 (en) | 2006-02-03 | 2010-08-03 | Sprint Communications Company L.P. | Opportunistic data transfer over heterogeneous wireless networks |
CN105357145B (en) | 2006-02-03 | 2019-12-27 | 诺基亚公司 | Providing threshold-based buffer status reports from a user equipment to a wireless network |
US20070245171A1 (en) | 2006-03-27 | 2007-10-18 | Patrick Ohly | Methods and apparatus to perform distributed memory checking |
US8160000B2 (en) | 2006-06-08 | 2012-04-17 | Qualcomm Incorporated | Achieving power savings through packet grouping |
US8223729B2 (en) | 2006-07-19 | 2012-07-17 | Qualcomm Incorporated | Radio interface selection for a terminal |
JP4837487B2 (en) | 2006-08-11 | 2011-12-14 | 京セラ株式会社 | Channel allocation method and base station apparatus using the same |
US7940735B2 (en) | 2006-08-22 | 2011-05-10 | Embarq Holdings Company, Llc | System and method for selecting an access point |
JP2008072568A (en) | 2006-09-15 | 2008-03-27 | Hiroshi Makino | Adaptive asynchronous communication control program |
US8923852B2 (en) | 2006-11-01 | 2014-12-30 | Seven Networks, Inc. | System, method, and computer-readable medium for user equipment decision-making criteria for connectivity and handover |
JP4970066B2 (en) | 2007-01-29 | 2012-07-04 | 京セラ株式会社 | Wireless communication device, control method thereof, and control method |
US8626171B2 (en) | 2006-11-29 | 2014-01-07 | Kyocera Corporation | Wireless communication terminal and method of controlling the same |
US8089970B2 (en) * | 2006-12-14 | 2012-01-03 | Ntt Docomo, Inc. | Method and apparatus for managing admission and routing in multi-hop 802.11 networks taking into consideration traffic shaping at intermediate hops |
US8055761B2 (en) | 2007-01-31 | 2011-11-08 | International Business Machines Corporation | Method and apparatus for providing transparent network connectivity |
US7756068B2 (en) | 2007-02-08 | 2010-07-13 | Sony Ericsson Mobile Communications Ab | Selecting an interface in a multi-radio enabled device |
US7860469B2 (en) | 2007-03-19 | 2010-12-28 | Intel Corporation | Sleep optimization for mobile devices in a wireless network |
US20080234012A1 (en) | 2007-03-22 | 2008-09-25 | Changwen Liu | Scheduling for power savings in a wireless network |
US8027293B2 (en) | 2007-07-16 | 2011-09-27 | Cellport Systems, Inc. | Communication channel selection and use |
US7873746B2 (en) | 2007-07-27 | 2011-01-18 | Lagavulin Limited | User interface for a portable, image-processing transmitter |
JP5049069B2 (en) | 2007-08-02 | 2012-10-17 | ソフトバンクテレコム株式会社 | Wireless communication terminal device and communication network program |
US20090049518A1 (en) | 2007-08-08 | 2009-02-19 | Innopath Software, Inc. | Managing and Enforcing Policies on Mobile Devices |
WO2009086316A1 (en) | 2007-12-21 | 2009-07-09 | Citrix Systems, Inc. | Systems and methods for efficient processing of data displayed by a window |
US8417187B2 (en) | 2008-01-07 | 2013-04-09 | Apple Inc. | Methods and apparatus for wireless device coexistence |
JP2009182443A (en) | 2008-01-29 | 2009-08-13 | Ntt Docomo Inc | Communication terminal, operation mode management program, and operation mode management method |
KR20100106550A (en) | 2008-01-29 | 2010-10-01 | 교세라 가부시키가이샤 | Radio communication terminal control method and radio communication terminal |
US8144725B2 (en) | 2008-05-28 | 2012-03-27 | Apple Inc. | Wireless femtocell setup methods and apparatus |
US20090318124A1 (en) | 2008-06-23 | 2009-12-24 | At&T Mobility Ii Llc | Mobile device management through an offloading network |
FI20085676A0 (en) | 2008-06-30 | 2008-06-30 | Nokia Corp | Transmission of delay tolerant data |
US8010842B2 (en) | 2008-08-08 | 2011-08-30 | Innopath Software, Inc. | Intelligent mobile device management client |
JP5374717B2 (en) | 2008-08-21 | 2013-12-25 | 独立行政法人情報通信研究機構 | Sensor network system that realizes highly reliable control command transmission and reception and bandwidth efficiency |
US8160598B2 (en) | 2008-12-10 | 2012-04-17 | At&T Intellectual Property Ii, L.P. | Lightweight application level policy management for portable wireless devices under varying network |
US8312531B2 (en) | 2009-01-09 | 2012-11-13 | At&T Intellectual Property I, L.P. | Communicating via a wireless gateway device and SSL |
JP2010183414A (en) | 2009-02-06 | 2010-08-19 | Sanyo Electric Co Ltd | Telephone set |
US7990897B2 (en) | 2009-03-11 | 2011-08-02 | Sony Corporation | Method and apparatus for a wireless home mesh network with network topology visualizer |
US8271057B2 (en) | 2009-03-16 | 2012-09-18 | Waze Mobile Ltd. | Condition-based activation, shut-down and management of applications of mobile devices |
US8255011B2 (en) | 2009-05-01 | 2012-08-28 | L3 Communications Integrated Systems, L.P. | Mobile communication device and communication method |
US20100287281A1 (en) | 2009-05-11 | 2010-11-11 | Motorola, Inc. | Telecommunication network resource management based on social network characteristics |
CA2667820C (en) | 2009-05-29 | 2013-10-01 | Research In Motion Limited | Signal quality determination methods and apparatus suitable for use in wlan-to-wwan transitioning |
US9313800B2 (en) | 2009-06-23 | 2016-04-12 | Nokia Technologies Oy | Method and apparatus for optimizing energy consumption for wireless connectivity |
US8509193B2 (en) * | 2009-07-21 | 2013-08-13 | Microsoft Corporation | Packet aggregation |
US8996659B2 (en) | 2009-07-24 | 2015-03-31 | Plumchoice, Inc. | Systems and methods for providing remote services using a cross-device database |
US8249499B2 (en) | 2009-07-31 | 2012-08-21 | Sierra Wireless, Inc. | Method, system and device for initiating wireless communication |
JP5354557B2 (en) | 2009-08-24 | 2013-11-27 | インテル・コーポレーション | Low-power and high-speed application service transmission |
CA2675666A1 (en) | 2009-08-27 | 2009-11-05 | Ibm Canada Limited - Ibm Canada Limitee | Accelerated execution for emulated environments |
EP2491745B1 (en) | 2009-12-18 | 2018-07-04 | Intel Corporation | System and method of utilizing a framework for information routing in large-scale distributed systems using swarm intelligence |
US8169935B2 (en) | 2009-12-22 | 2012-05-01 | Intel Corporation | Multi-radio connection management and bundling using web browsers |
US8228832B2 (en) | 2010-01-25 | 2012-07-24 | Motorola Mobility, Inc. | USSD transport method and device |
US8904206B2 (en) | 2010-01-26 | 2014-12-02 | Motorola Mobility Llc | Mobile computing device and method for maintaining application continuity |
KR101624749B1 (en) | 2010-01-29 | 2016-05-26 | 삼성전자주식회사 | Apparatus and method for controlling sleep mode in a communication system based on a packet |
US9603085B2 (en) | 2010-02-16 | 2017-03-21 | Qualcomm Incorporated | Methods and apparatus providing intelligent radio selection for legacy and non-legacy applications |
US8570993B2 (en) | 2010-05-20 | 2013-10-29 | At&T Mobility Ii Llc | Wi-Fi intelligent selection engine |
US8670362B2 (en) | 2010-07-26 | 2014-03-11 | Texas Instruments Incorporated | Power state and medium access coordination in coexisting wireless networks |
US8831658B2 (en) | 2010-11-05 | 2014-09-09 | Qualcomm Incorporated | Controlling application access to a network |
US8359016B2 (en) | 2010-11-19 | 2013-01-22 | Mobile Iron, Inc. | Management of mobile applications |
US8971841B2 (en) | 2010-12-17 | 2015-03-03 | Microsoft Corporation | Operating system supporting cost aware applications |
US9264868B2 (en) | 2011-01-19 | 2016-02-16 | Qualcomm Incorporated | Management of network access requests |
CN102186167B (en) | 2011-04-11 | 2016-02-10 | 中兴通讯股份有限公司 | A kind of to applying the method and system monitored |
US9571952B2 (en) | 2011-04-22 | 2017-02-14 | Qualcomm Incorporatd | Offloading of data to wireless local area network |
US9137737B2 (en) | 2011-08-29 | 2015-09-15 | Qualcomm Incorporated | Systems and methods for monitoring of background application events |
JP5831207B2 (en) | 2011-12-21 | 2015-12-09 | 富士通株式会社 | Mobile terminal device, control program and control method for mobile terminal device |
EP2815593A4 (en) | 2012-02-17 | 2015-08-12 | Intertrust Tech Corp | Systems and methods for vehicle policy enforcement |
US9774525B2 (en) * | 2013-03-25 | 2017-09-26 | Altiostar Networks, Inc. | Systems and methods for scheduling of data packets based on delay tolerance of applications |
-
2011
- 2011-11-03 US US13/288,928 patent/US9178965B2/en active Active
- 2011-11-04 KR KR1020147014857A patent/KR101604204B1/en not_active IP Right Cessation
- 2011-11-04 EP EP11788657.2A patent/EP2774331B1/en not_active Not-in-force
- 2011-11-04 CN CN201180074590.7A patent/CN104025536B/en active Active
- 2011-11-04 WO PCT/US2011/059445 patent/WO2013066354A1/en active Application Filing
- 2011-11-04 JP JP2014539913A patent/JP5863217B2/en not_active Expired - Fee Related
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070104162A1 (en) * | 2005-11-10 | 2007-05-10 | Kneckt Jarkko L S | Use of timing information for handling aggregated frames in a wireless network |
Also Published As
Publication number | Publication date |
---|---|
WO2013066354A1 (en) | 2013-05-10 |
JP5863217B2 (en) | 2016-02-16 |
CN104025536A (en) | 2014-09-03 |
EP2774331A1 (en) | 2014-09-10 |
US20120236772A1 (en) | 2012-09-20 |
KR101604204B1 (en) | 2016-03-16 |
US9178965B2 (en) | 2015-11-03 |
JP2015504262A (en) | 2015-02-05 |
CN104025536B (en) | 2017-06-06 |
KR20140095527A (en) | 2014-08-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2774331B1 (en) | Systems and methods for synchronization of application communications | |
US8838086B2 (en) | Systems and methods for management of background application events | |
US9571952B2 (en) | Offloading of data to wireless local area network | |
EP3391556B1 (en) | Method and apparatus for selecting reception antenna set of user terminal | |
US9264868B2 (en) | Management of network access requests | |
KR101557843B1 (en) | Management of network access requests | |
KR102202647B1 (en) | Method for communicating data and electronic device thereof | |
EP2896168B1 (en) | Apparatus and method for delivery control of application data to a mobile device in a communication network | |
KR101488650B1 (en) | Systems and methods for management of background application events | |
JP2018515822A (en) | Method and system for operating state coordination among multiple SOCs in a computing device | |
JP6672167B2 (en) | Fast sleep systems and processes | |
JP2017521905A (en) | Methods and mechanisms for power saving and performance balancing in transmitters | |
KR102252094B1 (en) | Terminal and power management method of terminal | |
TW201340753A (en) | Method and system for triggering fast dormancy mechanism |
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: 20140410 |
|
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) | ||
17Q | First examination report despatched |
Effective date: 20170724 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602011049592 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: H04L0012700000 Ipc: H04L0012891000 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04L 12/891 20130101AFI20180207BHEP Ipc: H04L 29/08 20060101ALI20180207BHEP Ipc: H04L 12/851 20130101ALI20180207BHEP |
|
INTG | Intention to grant announced |
Effective date: 20180219 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 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 |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 1013287 Country of ref document: AT Kind code of ref document: T Effective date: 20180715 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602011049592 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 8 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180927 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180927 |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20180627 |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180928 Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 Ref country code: RS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1013287 Country of ref document: AT Kind code of ref document: T Effective date: 20180627 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20181027 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SM Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602011049592 Country of ref document: DE |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 |
|
26N | No opposition filed |
Effective date: 20190328 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20181104 Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20181130 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20181130 Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20181130 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20181104 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20181130 Ref country code: AL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20181104 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20180627 Ref country code: MK Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180627 Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO Effective date: 20111104 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20201023 Year of fee payment: 10 Ref country code: GB Payment date: 20201029 Year of fee payment: 10 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602011049592 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: H04L0012891000 Ipc: H04L0047410000 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20211013 Year of fee payment: 11 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20211104 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20211104 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20211130 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 602011049592 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20230601 |