Abstract: Resources used by a foreground process associated with an application as well as one or more background tasks associated with the application that are running as separate processes on the computing device are tracked. Historical data relating to resource usage by the application is utilized to predict a resource usage amount for the application which is then stored. A subsequent launch of the application can be conditioned upon whether the predicted resource usage amount is available. If the predicted resource usage amount is available, it can be allocated to the application and the application can be launched. If the application then exceeds the predicted resource usage amount, other processes executing concurrently therewith may be terminated to free up the resource. Regardless of how the application performs, new resource usage data is obtained for the application, which is then used to adjust the predicted resource usage amount.

Abstract: Resources used by a foreground process associated with an application as well as one or more background tasks associated with the application that are running as separate processes on the computing device are tracked. Historical data relating to resource usage by the application is utilized to predict a resource usage amount for the application which is then stored. A subsequent launch of the application can be conditioned upon whether the predicted resource usage amount is available. If the predicted resource usage amount is available, it can be allocated to the application and the application can be launched. If the application then exceeds the predicted resource usage amount, other processes executing concurrently therewith may be terminated to free up the resource. Regardless of how the application performs, new resource usage data is obtained for the application, which is then used to adjust the predicted resource usage amount.

Abstract: Resources used by a foreground process associated with an application as well as one or more background tasks associated with the application that are running as separate processes on the computing device are tracked. Historical data relating to resource usage by the application is utilized to predict a resource usage amount for the application which is then stored. A subsequent launch of the application can be conditioned upon whether the predicted resource usage amount is available. If the predicted resource usage amount is available, it can be allocated to the application and the application can be launched. If the application then exceeds the predicted resource usage amount, other processes executing concurrently therewith may be terminated to free up the resource. Regardless of how the application performs, new resource usage data is obtained for the application, which is then used to adjust the predicted resource usage amount.

Abstract: Techniques are described that enable an application executing on a computing device to dynamically control how an allocated portion of a resource of the computing device is to be divided among multiple processes associated with the application. For example, an application executing on the computing device may interact with an operating system of the computing device to dynamically control how an allocated portion of a resource of the computing device is to be divided among a foreground process associated with the application and one or more background processes associated with the application.

Abstract: Techniques are described that enable an application executing on a computing device to dynamically control how an allocated portion of a resource of the computing device is to be divided among multiple processes associated with the application. For example, an application executing on the computing device may interact with an operating system of the computing device to dynamically control how an allocated portion of a resource of the computing device is to be divided among a foreground process associated with the application and one or more background processes associated with the application.

Abstract: Resources used by a foreground process associated with an application as well as one or more background tasks associated with the application that are running as separate processes on the computing device are tracked. Historical data relating to resource usage by the application is utilized to predict a resource usage amount for the application which is then stored. A subsequent launch of the application can be conditioned upon whether the predicted resource usage amount is available. If the predicted resource usage amount is available, it can be allocated to the application and the application can be launched. If the application then exceeds the predicted resource usage amount, other processes executing concurrently therewith may be terminated to free up the resource. Regardless of how the application performs, new resource usage data is obtained for the application, which is then used to adjust the predicted resource usage amount.

Abstract: A mobile station having a Voice-Over-Internet-Protocol client sends a message proposing a frame packing and frame repeating parameter set (1001). The called client may either accept the proposal or offer a revision (1003). If accepted the VoIP call is established (1009). If a revised proposal is received, it is determined whether the parameters are acceptable (1005). If not the call is declined (1007). If acceptable the call may proceed (1011). Both clients may then monitor network conditions (1013) and propose revisions to the parameters as conditions change. In this way, the VoIP application layer compensates for physical and Medium Access Control (MAC) layer inefficiencies in transporting the small frames used for audio data transfer for VoIP.

Abstract: A mobile station having a Voice-Over-Internet-Protocol client sends a message proposing a frame packing and frame repeating parameter set (1001). The called client may either accept the proposal or offer a revision (1003). If accepted the VoIP call is established (1009). If a revised proposal is received, it is determined whether the parameters are acceptable (1005). If not the call is declined (1007). If acceptable the call may proceed (1011). Both clients may then monitor network conditions (1013) and propose revisions to the parameters as conditions change. In this way, the VoIP application layer compensates for physical and Medium Access Control (MAC) layer inefficiencies in transporting the small frames used for audio data transfer for VoIP.