4 Device-Specific Protocols
The following documents describe the Windows interoperability services for interacting with devices.
Specification short name |
Description |
|
---|---|---|
Automatic Bluetooth Pairing Protocol |
This protocol facilitates the establishment of a secure, trusted Bluetooth (BT) pairing relationship between two devices without requiring any user interaction at the time of pairing. To use the Automatic Bluetooth Pairing Protocol, the Bluetooth media access control address (MAC address) of the server device and a shared secret are exchanged between the two devices using an out-of-band (OOB) mechanism. |
|
Connected Devices Platform Service Protocol Version 3 |
This protocol facilitates communication with any OneCore device. These companion apps may be on iOS devices, Android devices, or a OneCore device like Hololens or Windows. It enables Windows to send status information and messages to companion apps. It also allows companion apps to provide virtual input to the OneCore target device. |
|
Device Registration Discovery Protocol |
This protocol is used to discover the information needed to register devices. |
|
Device Registration Enrollment Protocol |
This protocol provides a lightweight mechanism for registering personal or corporate-owned devices with a workplace. It uses information obtained through the Device Registration Discovery Protocol [MS-DVRD] to register a device in the device registration service. |
|
Enterprise Client Synchronization Protocol |
This protocol is used in synchronizing files across multiple devices in an enterprise network. |
|
This protocol enables enrolling a device in a Device Management Service through an Enrollment Service; it includes the discovery of the Management Enrollment Service and enrollment with that service. Version 2 of this protocol provides a new enrollment method. |
||
Mobile Device Management Protocol |
This protocol is used for managing devices which have previously enrolled into a management system through the Mobile Device Enrollment Protocol Version 2 ([MS-MDE2]). It is a subset of the Open Mobile Association (OMA) Device Management Protocol version 1.2.1 (OMA-TS-DM_Protocol-V1_2_1-20080617-A) [OMA-DMP1.2.1]. |
|
Near Field Proximity: Bidirectional Services Protocol |
This protocol enables devices such as smartphones to discover services and version information on other devices. It provides a transport-agnostic means of building impromptu connections between peers, so it can be used on any transport system where peers can subscribe to message types and publish messages based on those types. |
|
Near Field Proximity: Sharing Protocol |
This protocol relies on the Near Field Proximity: Bidirectional Services Protocol [MS-NFPB] as a trigger for completing the message exchange specified in this protocol. After being triggered, this protocol then relies on Office Open XML File Format [ECMA-376] for creating an OPC package and then TCP/IP and/or Bluetooth/RFCOMM for data transport. |
|
Tethering Control Channel Protocol |
This protocol facilitates the sharing of a server’s network connection with one or more clients. By using it, clients can make a request to share a server's Internet connection. The server responds to clients with the appropriate Wi-Fi information, specifying the tethering configuration settings. |
|
UPnP Device and Service Templates: Media Property and Compatibility Extensions |
These extensions include the Microsoft Media Property Extensions (MMPE), the Microsoft Compatibility Extension Flags (MCEF), the Microsoft Power Management Extensions (MPME), and the Microsoft ProtocolInfo Extensions. These flags and extensions extend the Universal Plug and Play (UPnP) interoperability guidelines, as specified by the UPnP Forum ([UPnP]) and used by the Digital Living Network Alliance ([DLNA]). |
|
Wi-Fi Direct (WFD) Application to Application Protocol |
This protocol (WFDA2A) enables two or more devices to establish a direct connection without requiring an intermediary, such as an infrastructure wireless access point (WAP). |