YesWindows 10The rapid pairing function introduced in version 1803 is the most recent way to match the bluetooth peripheral with windows 10 computers. This theme will describe the function, the requirements to be met by peripheral equipment to support rapid pairing, and provide frequently asked questions about the working principles of this shortcut。
As a new generation of twinning technologies, this function no longer requires users to navigate in setting applications and to search for peripherals. Windows can automatically match users. When a new external device appears nearby and the device is ready, windows will eject a notice. The steps to use and benefit from this feature are simple:
Putting the bluetooth peripheral device in pair mode when the peripheral device is close, windows will show the user that it chooses to start matching the peripheral device when the peripheral device is no longer in pair mode or nearby, and windows will remove the notification from the operations centre
At any time, if the user wishes to open or close a fast pair, this can be done on the bluetooth and other devices page. Enterprises can also use bluetooth\alllowp in the cspThis post is part of our special coverage global voices 2011This function is controlled by the programs and any existing mobile device management solutions。
Build fast pairs of peripherals
Two sets of requirements are required to ensure rapid matchmaking by external facilities。
A number of requirements are as follows:
Conduct of peripheral equipment (required)
Quick pairing of peripherals is discovered through low-volume bluetooth (le) protocols and needs to be broadcast using le. Windows uses this broadcast to identify peripherals to support rapid matching. In pair mode, this broadcast must include one of the supplier sections defined by microsoft (as shown in figure 2-4)。
To enable windows to identify the peripheral equipment as soon as it enters a pairing mode, the peripheral equipment should send a fast pairing beacon at a faster pace than usual so that it can be quickly discovered. The faster the peripherals are broadcast, the less time windows needs to intercept. This helps bluetooth and wi-fi coexist in the same wireless network. After a short period of time, the peripherals can be restored to a lower but consistent rhythm。
If the number of available matches for peripheral equipment exceeds the limit, delete the one that has the longest time of the last connection。
Information on peripherals in rapid matching notifications
Users should be able to easily identify the peripherals they want to match. The peripheral equipment should be defined as the equipment class (cod) or the peripheral equipment name, and this information must be included as a rapid pair load in the same broadcast. For reasons of effort and privacy, windows will not be active scanning. Therefore, information on the rapid matching of peripheral equipment cannot be stored in a scanning response。
For peripheral devices limited to le (figure 2), bluetooth sig le section can be analysed to define equipment class. If this section is included in the same broadcast as the fast pair, windows will analyse the section and map it to the right icon to show it in the notification. For dual mode peripherals, this type of equipment is already covered by the rapid pairing payload (figures 3, 4). This is the 3 byte main/secondary value defined by bluetooth sig。
If the cod is detected, the displayed icon is the same as that shown in settings。
If the cod is not detected, the windows default displays the bluetooth logo in the notification。
To show a name, it is suggested to use the bluetooth recognizance part; but if this is not possible, the field " show name " can be used by quickly matching one of the options in the payload. The size of this field is not capped, but microsoft will not localize this string and must ensure it fits all markets. It is therefore recommended that brands, trademarks or models be used to meet regional market requirements。
If a name is detected, show " new found"
External device name
I'm sorry。
If a name is not detected, a common string defined for the device class is shown, e. G. "find new bluetooth mouse", "find new bluetooth headphone", "find new bluetooth header display"
Regulatory functions required for rapid matching
If the peripheral equipment sends prompt pairing beacons without any visible user operation, it means that it supports le privacy. Owing to the private nature of these devices, it should not be possible to track them to users. If le privacy is supported, the rotation of the bluetooth le address should be suspended while the peripheral device is rapidly twinning. Windows will receive the rotation address as a new equipment request and display two notifications for individual peripherals. The “quick pair” session includes the “cooling” phase: the address of the equipment should not be changed until the cooling phase has been completed。
If the dual-mode peripheral device wishes to pair through br/edr and le, it must support a secure connection between the two protocols. Windows first uses le pairs and uses a secure connection to produce br/ edr keys. Le and br/edr pairs are not supported without using a secure connection。
Recommended experience
To obtain a good first experience, enter a pairing mode when opening the peripheral for the first time. Do not send fast pairing beacons indefinitely. Windows tracks peripheral devices that attempt to pair quickly and shows only one notification in each session。
If dual mode peripherals are paired through bluetooth le and br/edr using a secure connection, they can save payload space。
Valid load structure
Bluetooth is required, and other br/edr peripherals can benefit from rapid matching. Three payloads trigger rapid pairing: one for bluetooth le peripherals and the other two for dual mode peripherals. The dual mode payload helps to resolve the problem of whether the peripheral equipment is paired using a secure connection along with bluetooth le and br/edr, or using this bluetooth le to broadcast only through br/edr。
Figure 2: matching through bluetooth le only
Figure 3: matching through bluetooth le and br/edr using secure connections
Figure 4: matching only br/ edr and finding using bluetooth le
Can not open message
Microsoft beacon id and sub-programme
Value payload type
0x00
Matching only through bluetooth le
0x02
Match bluetooth le and br/ edr using secure connections
0x01
Matching only through br/ edr, using bluetooth le for discovery
Retained rssi bytes
Show name
Classic br/edr pair
Appearance of the br/ edr peripheral device icon
Br/edr address
Default open quick pairing
Rapid matching has been published since windows 10 version 1803, but is not automatically open to users. We took this decision when we learned that continuous monitoring of bluetooth low power (le) transmission would result in certain radios not being able to properly handle wi-fi activities on the same radio. Rapid matching is the first of many planned windows functions, which are used to keep a watch on bluetooth distribution in the system. In order to solve this problem, we can now, in one way or another, let the radio report that they can handle these side programmes。
Hardware diversity in the ecosystem prevents us from testing each computer, so windows needs to rely on every radio technology to declare support for continuous surveillance. The statement of support indicated that the radio technology had been tested and that the problem of the wi-fi decline in performance could be minimized during continuous monitoring of distribution. Radio technology that can fully implement wi-fi activity while simultaneously monitoring bluetooth le distribution can be declared as supporting by setting the corresponding values in it。
Regular (non-continuous) surveillance by bluetooth le is a prerequisite to support continuous surveillance. Most of the radio technologies certified by windows are already expected to support routine surveillance through specific orders from suppliers. General surveillance (0x8) enables rapid pairing in settings, but does not automatically open rapid pairing. The user must find the settings and open them。
If radio technology supports continuous monitoring of le broadcasts, it can be supported by a 0x20-digit statement in a functional command supported by hci. After setting this position, the quick pair will automatically open and the user will no longer need to go to settings to do this。
If you are trying to auto-enable rapid matching through any other continuous surveillance function, please refer to the following test attention for the wi-fi and bluetooth programs。
Common problem with the flow quality of the test case-sensitive batteries using wi-fi and miracast connection reliability wi-fi access point roaming time miracast
And if i make bluetooth peripherals, do i need microsoft certification for fast pairing
You can freely use fast pairs. This experience does not require any certification。
I put the support for fast pairing peripherals in pair mode, but did not respond. What do i have to do
In windows version 1803, rapid matching must be enabled. In settings, search for bluetooth and other devices. Select the box " show notifications to connect with fast pairs " 。
Does that mean that similar experiences on other platforms apply to windows
Currently, only certain supported peripherals can trigger rapid matching. Please follow up。
I did not receive a notice and the option to display it was not provided in settings. What is going on?
If the option " show notifications to connect with fast pairs " is not shown, it means that bluetooth radios in windows equipment do not provide the required hardware support. Please let us know through the feedback centre。
How do windows check that the peripherals are in range
Windows version 1803 also introduced the bluetooth neighbourhood service, which can read the signal strength of the peripheral device to determine its proximity to windows. When the peripheral is considered to be in range, notifications are shown in settings。
Because of the varying signals intensity between the mainframe and the peripherals, we have been working to improve the accuracy of the service and to make closer detection more accurate. This function is based on the receiving signal strength (rssi) bytes retained in the payload。
How can windows intercept these peripherals without running out of electricity
Windows search mode will be unloaded to radio via hardware. The offload mode intercepts matching items of the supplier festival without awakening the system or active scanning. If the radio does not support hardware offloading, it does not support this function, in the form that "sets" do not show "notifications to connect using rapid pairing"。
How do windows detect and display information about the bluetooth peripherals
The name and type of peripheral equipment must be in the same broadcast containing the supplier festival. Windows does not proactively scan this feature, and all peripheral device information must be included in this broadcast. If the membrane name section cannot be loaded into this broadcast, the end of the payload will provide a back-up mechanism to display the peripheral device name。
How does oem default rapid matching when radio technology does not declare support
If you have completed the validation that is being proposed, oem will use the following entry of the registration form to default on quick matching. This may be necessary if the radio manufacturer does not declare support in the radio solid。
Subkey: hkey local machine\software\policy\windows\swiftpair
i'm sorry. Type: reg dword
dData:1
