Abstract: An Internet of Things (IoT) system may include a publisher computer connected to IoT devices. The publisher computer may execute operations to provide data for the IoT devices to a remote computer which may be included in a cloud infrastructure. The publisher computer can receive data from the IoT devices, convert the data to a publisher-subscriber format that conforms to a predetermined specification, and transmit the data to the cloud infrastructure or other remote computers.

Abstract: Mobile computing device power consumption can be reduced by using expiration window timers, state-based timers and/or the coordination of keep-alive timers. A mobile computing device can execute tasks associated with multiple keep-alive timers used for maintaining communication links between the device and cloud-based service providers in a single active state. A cloud-based keep-alive service can maintain mobile computing device-service provider communication links by sending one keep-alive communication to a mobile computing device in place of multiple communications. Upon receiving a response, the keep-alive surface can send a plurality of keep-alive communications to a plurality of cloud-based service providers.

Abstract: Mobile computing device power consumption can be reduced by using expiration window timers, state-based timers and/or the coordination of keep-alive timers. A mobile computing device can execute tasks associated with multiple keep-alive timers used for maintaining communication links between the device and cloud-based service providers in a single active state. A cloud-based keep-alive service can maintain mobile computing device-service provider communication links by sending one keep-alive communication to a mobile computing device in place of multiple communications. Upon receiving a response, the keep-alive surface can send a plurality of keep-alive communications to a plurality of cloud-based service providers.

Abstract: Mobile computing device power consumption can be reduced by using expiration window timers, state-based timers and/or the coordination of keep-alive timers. A mobile computing device can execute tasks associated with multiple keep-alive timers used for maintaining communication links between the device and cloud-based service providers in a single active state. A cloud-based keep-alive service can maintain mobile computing device-service provider communication links by sending one keep-alive communication to a mobile computing device in place of multiple communications. Upon receiving a response, the keep-alive surface can send a plurality of keep-alive communications to a plurality of cloud-based service providers.

Abstract: An Internet of Things (IoT) system may include a publisher computer connected to IoT devices. The publisher computer may execute operations to provide data for the IoT devices to a remote computer which may be included in a cloud infrastructure. The publisher computer can receive data from the IoT devices, convert the data to a publisher-subscriber format that conforms to a predetermined specification, and transmit the data to the cloud infrastructure or other remote computers.

Abstract: Mobile computing device power consumption can be reduced by using expiration window timers, state-based timers and/or the coordination of keep-alive timers. A mobile computing device can execute tasks associated with multiple keep-alive timers used for maintaining communication links between the device and cloud-based service providers in a single active state. A cloud-based keep-alive service can maintain mobile computing device-service provider communication links by sending one keep-alive communication to a mobile computing device in place of multiple communications. Upon receiving a response, the keep-alive surface can send a plurality of keep-alive communications to a plurality of cloud-based service providers.

Abstract: A method of coordinating tasks of a mobile computing device may include initializing a timer associated with one or more tasks and a state condition. The state condition may depend on a device state of the mobile computing device and/or a component state of a mobile computing device component. An expiration of the timer is detected. Upon detecting the expiration, a determination is made whether the state condition is satisfied based on whether the mobile computing device is in the device state and/or the mobile computing device component is in the component state. Based at least in part on the determination that the state condition is satisfied, performance of the one or more tasks associated with the timer can be initiated.

Abstract: APIs discussed herein promote efficient and timely interoperability between hardware and software components within the media processing pipelines of media content players. A PhysMemDataStructure API facilitates a hardware component's direct access to information within a memory used by a software component, to enable the hardware component to use direct memory access techniques to obtain the contents of the memory, instead of using processor cycles to execute copy commands. The PhysMemDataStructure API exposes one or more fields of data structures associated with units of media content stored in a memory used by a software component, and the exposed fields store information about the physical properties of the memory locations of the units of media content. SyncHelper APIs are used for obtaining information from, and passing information to, hardware components, which information is used to adjust the hardware components' timing for preparing media samples of synchronously-presentable media content streams.

Abstract: APIs discussed herein promote efficient and timely interoperability between hardware and software components within the media processing pipelines of media content players. A PhysMemDataStructure API facilitates a hardware component's direct access to information within a memory used by a software component, to enable the hardware component to use direct memory access techniques to obtain the contents of the memory, instead of using processor cycles to execute copy commands. The PhysMemDataStructure API exposes one or more fields of data structures associated with units of media content stored in a memory used by a software component, and the exposed fields store information about the physical properties of the memory locations of the units of media content. SyncHelper APIs are used for obtaining information from, and passing information to, hardware components, which information is used to adjust the hardware components' timing for preparing media samples of synchronously-presentable media content streams.

Abstract: A method of coordinating tasks of a mobile computing device may include initializing a timer associated with one or more tasks and a state condition. The state condition may depend on a device state of the mobile computing device and/or a component state of a mobile computing device component. An expiration of the timer is detected. Upon detecting the expiration, a determination is made whether the state condition is satisfied based on whether the mobile computing device is in the device state and/or the mobile computing device component is in the component state. Based at least in part on the determination that the state condition is satisfied, performance of the one or more tasks associated with the timer can be initiated.

Abstract: Mobile computing device power consumption can be reduced by using expiration window timers, state-based timers and/or the coordination of keep-alive timers. Upon detecting a trigger event causing a mobile computing device to transition from a low-power state to an active state, the device can determine whether the trigger event occurs within the expiration window of a timer, and execute tasks associated with the trigger event and the timer. Tasks associated with state-based timers can be executed if the mobile computing device or a component thereof is in (or, alternatively, not in) a specified state. A mobile computing device can execute tasks associated with multiple keep-alive timers used for maintaining communication links between the device and cloud-based service providers in a single active state.

Abstract: Software interfaces are configured to enable functionality that is commonly implemented in special-purpose hardware for mixing AV content into a set of 2.5-D graphics planes to be exposed to high level processes executing in a computing environment in a fully portable manner. Illustratively, the interfaces include a planar mixer (named “IPlanarMixer”) that abstracts the mixing hardware, and a graphics plane interface (named “IPlane”) that abstracts individual instances of planes that are retrieved from, and handed off to the planar mixer as the 2.5-D graphics planes are built up and rendered in a computing environment to support interactive graphic experiences for a user.

Abstract: APIs discussed herein promote efficient and timely interoperability between hardware and software components within the media processing pipelines of media content players. A PhysMemDataStructure API facilitates a hardware component's direct access to information within a memory used by a software component, to enable the hardware component to use direct memory access techniques to obtain the contents of the memory, instead of using processor cycles to execute copy commands. The PhysMemDataStructure API exposes one or more fields of data structures associated with units of media content stored in a memory used by a software component, and the exposed fields store information about the physical properties of the memory locations of the units of media content. SyncHelper APIs are used for obtaining information from, and passing information to, hardware components, which information is used to adjust the hardware components' timing for preparing media samples of synchronously-presentable media content streams.

Abstract: APIs discussed herein promote efficient and timely interoperability between hardware and software components within the media processing pipelines of media content players. A PhysMemDataStructure API facilitates a hardware component's direct access to information within a memory used by a software component, to enable the hardware component to use direct memory access techniques to obtain the contents of the memory, instead of using processor cycles to execute copy commands. The PhysMemDataStructure API exposes one or more fields of data structures associated with units of media content stored in a memory used by a software component, and the exposed fields store information about the physical properties of the memory locations of the units of media content. SyncHelper APIs are used for obtaining information from, and passing information to, hardware components, which information is used to adjust the hardware components' timing for preparing media samples of synchronously-presentable media content streams.

Abstract: Mobile computing device power consumption can be reduced by using expiration window timers, state-based timers and/or the coordination of keep-alive timers. Upon detecting a trigger event causing a mobile computing device to transition from a low-power state to an active state, the device can determine whether the trigger event occurs within the expiration window of a timer, and execute tasks associated with the trigger event and the timer. Tasks associated with state-based timers can be executed if the mobile computing device or a component thereof is in (or, alternatively, not in) a specified state. A mobile computing device can execute tasks associated with multiple keep-alive timers used for maintaining communication links between the device and cloud-based service providers in a single active state.

Abstract: Software interfaces are configured to enable functionality that is commonly implemented in special-purpose hardware for mixing AV content into a set of 2.5-D graphics planes to be exposed to high level processes executing in a computing environment in a fully portable manner. Illustratively, the interfaces include a planar mixer (named “IPlanarMixer”) that abstracts the mixing hardware, and a graphics plane interface (named “IPlane”) that abstracts individual instances of planes that are retrieved from, and handed off to the planar mixer as the 2.5-D graphics planes are built up and rendered in a computing environment to support interactive graphic experiences for a user.

Abstract: APIs discussed herein promote efficient and timely interoperability between hardware and software components within the media processing pipelines of media content players. A PhysMemDataStructure API facilitates a hardware component's direct access to information within a memory used by a software component, to enable the hardware component to use direct memory access techniques to obtain the contents of the memory, instead of using processor cycles to execute copy commands. The PhysMemDataStructure API exposes one or more fields of data structures associated with units of media content stored in a memory used by a software component, and the exposed fields store information about the physical properties of the memory locations of the units of media content. SyncHelper APIs are used for obtaining information from, and passing information to, hardware components, which information is used to adjust the hardware components' timing for preparing media samples of synchronously-presentable media content streams.