Abstract: Methods of throttling video streaming downloads in burst transmissions to a mobile device are driven by the network client. By knowing various input parameters such as the media bitrate, the current (average) network link bitrate, transceiver state timeout characteristics (e.g., inactivity timers), and power consumption information for various mobile device operating states, the network client can decide the proportion of each repeating burst interval duration to spend in an idle state. From a control parameter and the other input parameters, it can calculate the amount of media data it then needs to request in each burst transmission. Other calculations further inform this decision, such as the relative average power consumption (as compared to staying at a high activity state continuously).

Abstract: Methods of throttling video streaming downloads in burst transmissions to a mobile device are driven by the network client. By knowing various input parameters such as the media bitrate, the current (average) network link bitrate, transceiver state timeout characteristics (e.g., inactivity timers), and power consumption information for various mobile device operating states, the network client can decide the proportion of each repeating burst interval duration to spend in an idle state. From a control parameter and the other input parameters, it can calculate the amount of media data it then needs to request in each burst transmission. Other calculations further inform this decision, such as the relative average power consumption (as compared to staying at a high activity state continuously).

Abstract: A method and system for communicating data between an integrated circuit and each of a first device and a second device. Communications between the integrated circuit and the first device use a first interface protocol, while communications between the integrated circuit and the second device use a second interface protocol. Both interface protocols, however, share the same data bus and clock bus. To communicate using the second interface protocol, the first device, which uses the first interface protocol, is first deactivated by sending address data via the shared data bus that does not identify the first device, thereby causing the first device to enter an inactive state until a stop condition is detected on the shared data bus. Then, communications using the second interface protocol can be carried out, provided that a start or stop condition for the first interface protocol is not inadvertently generated on the shared data bus.