Microsoft Technology Licensing, LLC

J Adrian Lannin

Justin Allen Hutchings

Frank Gorgenyi

Esaias Engelbertus Greeff

Michael P Fenelon

Samuel David Adams

David Walker Duhon

Erik O Peterson

Arun Babu Nagarajan

Niket Ashok Sanghvi

Robert Franz Hain

Herman Richard Forrest, Iii

Guillermo Eduardo Guillen

Kyle P Wojtaszek

Daniel Oliver

Jerry K Koh

Steve Seixeiro

Robert John Anderson

Lindsey R Noll

Shawn E Maloney

Frank Olivier

Esaias Englebertus Greeff

Justin A Hutchings

David W Duhon

Robert F Hain

Esaias E Greeff

Niket A Sanghvi

Platform neutral device protocol techniques are described in which functionality to customize device interactions through communication busses is made accessible through platform independent script-based infrastructure. Functionality provided by an operating system to manipulate standard protocols of a communication bus used to interact with a connected device is exposed as script-based objects. Script-based protocol definition files associated with connected device may be employed to customize device protocols for the communications using the functionality exposed through the script-based objects. A computing device may acquire a protocol definition file for a particular device in various ways and host the protocol definition file via a suitable run-time platform. Requests for interaction with the particular device may then be handled using the custom protocols defined by the hosted protocol definition file.

Platform neutral device protocols

Device association data for peripheral devices, which is data used to connect to the peripheral devices, is maintained and synchronized across multiple computing devices associated with a user account on a service. When a new peripheral device is associated with a computing device, device association data for the new peripheral device is added to the computing device. The device association data for the new peripheral device is also sent to the service, which provides the device association to the other computing devices from which the user logs into his or her account, and those other computing devices in turn automatically associate themselves with the peripheral device. Device use data describing how a user desires to use the peripheral device on one computing device, as well as changes to the device association data on one computing device, can similarly be synchronized across the multiple computing devices.

Synchronizing device association data among computing devices

In accordance with the automatic peripheral device sharing, a peripheral device that has been newly installed on a device is detected and is shared with one or more additional devices coupled to the device. A notification of the peripheral device is automatically published to the one or more additional devices. This notification includes an indication of how the one or more additional devices can access the peripheral device. Each of the one or more additional devices can receive this notification and determine whether the peripheral device can be automatically installed on that device without user input. For each of the one or more additional devices, the peripheral device is installed on that device only if the peripheral device can be automatically installed on that device without user input.

Automatic peripheral device sharing

Growing community of inventors

Sammamish, WA, United States of America

J Adrian Lannin