WO2022015302A1

WO2022015302A1 - Signal strength based dockings

Info

Publication number: WO2022015302A1
Application number: PCT/US2020/042125
Authority: WO
Inventors: Isaac Lagnado; Christopher STEVEN; Thong Thai; Roger D. BENSON; Chung-Chun Chen
Original assignee: Hewlett-Packard Development Company, L.P.
Priority date: 2020-07-15
Filing date: 2020-07-15
Publication date: 2022-01-20

Abstract

In some examples, an electronic device comprises: a wireless transceiver to receive a first signal from a host device; and a controller coupled to the wireless transceiver, the controller to: verify that an identifier of the first signal matches an identifier of a trusted host device; determine that a strength of the first signal exceeds a threshold; initiate, based on the verification and the determination, a communication link with a peripheral device; and cause, based on the verification and the determination, the wireless transceiver to transmit a second signal comprising profile data of the electronic device to the host device.

Description

SIGNAL STRENGTH BASED DOCKINGS

BACKGROUND

[0001] Electronic devices (e.g., docking stations) allow host devices (e.g., notebooks, laptops, tablets, smartphones, or other mobile devices) to simultaneously couple to multiple peripheral devices (e.g., mice, keyboards, display devices, printing devices, storage devices). In some instances, a host device may couple to an electronic device utilizing a wired connection. After the wired connection is established, there is a time delay during which the electronic device and the host device complete a docking sequence. The docking sequence is a series of actions the electronic device and the host device perform to verify a connection, a speed of the connection, or an authorization of the connection. The docking sequence may take an unacceptably long time (e.g., tens of seconds) to complete.

BRIEF DESCRIPTION OF THE DRAWINGS [0002] Various examples will be described below referring to the following figures:

[0003] FIG. 1 depicts a schematic diagram of a system for signal strength based docking, in accordance with various examples;

[0004] FIG. 2 depicts a schematic diagram of an electronic device for signal strength based docking in accordance with various examples;

[0005] FIG. 3 depicts a schematic diagram of an electronic device for signal strength based docking in accordance with various examples; and [0006] FIG. 4 depicts a schematic diagram of a host device for signal strength based docking in accordance with various examples.

DETAILED DESCRIPTION

[0007] As described above, an electronic device allows a host device to simultaneously couple to multiple peripheral devices. However, until a docking sequence is complete, the host device is unable to access the peripheral devices coupled to the electronic device. To mitigate the time delay between a start of the docking sequence and a completion of the docking sequence, some electronic devices may initiate the docking sequence wirelessly. However, wireless docking sequences sometimes result in unintended consequences. For example, a user carrying a host device may pass an electronic device without intending to connect to the electronic device, but the electronic device may nonetheless detect the presence of the host device and attempt to initiate a wireless docking sequence with the host device. In other instances, a user may desire that a host device initiate a wireless docking sequence with an electronic device, but for security reasons, the electronic device may reject attempts by the host device to initiate the wireless docking sequence.

[0008] This disclosure describes an electronic device that utilizes a strength of a signal that is received wirelessly and an identifier of the signal to initiate a docking sequence. After the host device is physically coupled to the electronic device via a wired connection, the electronic device completes the docking sequence in response to determining that the host device is coupled to the electronic device utilizing the wired connection. Determining that the strength of the signal allows the electronic device to predict a user intent to connect the host device to the electronic device. The electronic device may predict a user intent to connect based on a strong signal or based on an increasing signal strength, for example. The electronic device may predict a user intent to not connect based on a weak signal or based on a decreasing signal strength, in another example. Verifying the identifier of the signal ensures that a trusted relationship exists between the electronic device and the host device. The trusted relationship indicates that a security between the electronic device and the host device has been established and that the host device has permission to connect to the electronic device. Initiating the docking sequence in response to a strength of the signal and a verification of an identifier of the signal prior to the host device establishing a wired connection with the electronic device reduces a duration of time for the electronic device to access peripheral devices once the wired connection is established from tens of seconds to a duration of as low as a few milliseconds. [0009] In one example in accordance with the present disclosure, an electronic device for signal strength based dockings is provided. The electronic device comprises a port, a wireless transceiver to receive a signal from a host device, and a controller coupled to the port and the wireless transceiver. The controller verifies an identifier of the signal and determines that a strength of the signal exceeds a threshold. The controller initiates, based on the verification and the determination, a docking sequence. The controller detects that the host device is coupled to the port. The controller completes, based on the detection, the docking sequence.

[0010] In another example in accordance with the present disclosure, an electronic device for signal strength based dockings is provided. The electronic device comprises a wireless transceiver to receive a first signal from a host device, and a controller coupled to the wireless transceiver. The controller verifies that an identifier of the first signal matches an identifier of a trusted host device and determines that a strength of the first signal exceeds a threshold. The controller initiates, based on the verification and the determination, a communication link with a peripheral device. The controller causes, based on the verification and the determination, the wireless transceiver to transmit a second signal comprising profile data of the electronic device to the host device.

[0011] In yet another example, in accordance with the present disclosure, a host device for signal strength based dockings is provided. The host device comprises a port, a graphics processing unit (GPU), a wireless transceiver to receive a signal from an electronic device, and a processor coupled to the port, the GPU, and the wireless transceiver. The processor verifies that an identifier of the signal matches an identifier of a trusted electronic device. The controller initiates, based on the verification, handshaking between the GPU and the electronic device. The controller detects that the electronic device is coupled to the port. The controller provides, based on the detection, a video signal to the electronic device.

[0012] Referring now to FIG. 1 , a schematic diagram of a system 100 for signal strength based dockings is depicted, in accordance with various examples. The system 100 comprises a host device 102, a peripheral device 128, and an electronic device 116 coupled to the host device 102 and the peripheral device 128. The electronic device 116 may be a docking station, for example. The host device 102 may be a notebook, laptop, tablet, smartphone, or other mobile device, for example. The peripheral device 128 may be a mouse, a keyboard, a display device, a printing device, or a storage device, for example. The electronic device 116 may be coupled to the host device 102 using a wireless connection, a wired connection, or a combination thereof. The electronic device 116 may be coupled to the peripheral device 128 using a wireless connection, a wired connection, or a combination thereof. BLUETOOTH® (BT) or WI-FI® may be utilized for a wireless connection, for example. Ethernet or universal serial bus (USB) may be utilized for a wired connection, for example. Other wireless and wired connection techniques and protocols are contemplated and fall within the scope of this disclosure.

[0013] In various examples, the host device 102 comprises a processor 106 coupled to a wireless transceiver 104, a port 114, a storage device 108, and a graphics processing unit (GPU) 112. The wireless transceiver 104 is to transmit and receive wireless signals. The wireless transceiver 104 may transmit or receive a BLUETOOTH® (BT) or WI-FI® signal, for example. The storage device 108 may include a hard drive, solid state drive (SSD), flash memory, random access memory (RAM), or other suitable memory, for example. The GPU 112 may include another processor for driving a display device internal to the host device 102 or external to the host device 102 (e.g., the peripheral device 128). The port 114 may comprise an Ethernet connector or a USB connector, for example. The processor 106 may be a microprocessor, a microcomputer, a microcontroller, a programmable integrated circuit, a programmable gate array, or another suitable controller, for example. In some examples, the storage device 108 may store computer-readable instructions 110. The computer-readable instructions 110, when executed by the processor 106, may cause the processor 106 to perform some or all of the actions attributed herein to the processor 106. [0014] In various examples, the electronic device 116 comprises a controller 120 coupled to a wireless transceiver 118, a port 126, and a storage device 122. The wireless transceiver 118 is to transmit and receive signals. The wireless transceiver 118 may transmit or receive a BLUETOOTH® (BT) or WI-FI® signal, for example. The storage device 122 may include a hard drive, solid state drive (SSD), flash memory, random access memory (RAM), or other suitable memory, for example. The port 126 may comprise an Ethernet connector or a USB connector, for example. The controller 120 may be a microprocessor, a microcomputer, a microcontroller, a programmable integrated circuit, a programmable gate array, or another suitable processor, for example. In some examples, the storage device 122 may store computer-readable instructions 124. The computer-readable instructions 124, when executed by the controller 120, may cause the controller 120 to perform some or all of the actions attributed herein to the controller 120.

[0015] In some examples, the wireless transceiver 104 of the host device 102 transmits a signal. The signal may be transmitted even in instances where the host device 102 is in a low-power state, for example. The low-power state conserves a battery power of the host device 102. For example, the signal may be a BLUETOOTH® Low Energy (BLE) signal. The wireless transceiver 118 of the electronic device 116 may receive the signal and determine that a strength of the signal. The strength of the signal may be determined by a received signal strength indicator (RSSI), for example. The RSSI represents a power level of a signal received by the wireless transceiver 118. As described above, the electronic device 116 may predict a user intent to connect based on a strong RSSI (e.g., the RSSI having a higher value than a threshold) or based on the RSSI having a higher value than a previously determined RSSI (e.g., increasing signal strength). The electronic device 116 may predict a user intent to not connect based on a weak RSSI (e.g., the RSSI having a lower value than a threshold) or based on the RSSI having a lower value than a previously determined RSSI (e.g., decreasing signal strength).

[0016] In other examples, the electronic device 116 may verify that an identifier of the wireless signal from the wireless transceiver 104 matches an identifier of a host device having a trusted relationship with the electronic device 116. A host device having a trusted relationship with the electronic device 116 may be referred to as a trusted host device in some examples. As described above, the trusted relationship indicates that a security between the electronic device 116 and a host device has been established and that the host device has permission to connect to the electronic device 116. For example, the storage device 122 of the electronic device 116 may include a security key. In response to the identifier of the host device 102 matching the security key, the electronic device 116 may determine the host device 102 is a trusted host device. In another example, the storage device 122 of the electronic device 116 may include a data structure of identifiers of host devices that have coupled to the electronic device 116 in the past or that have been granted permission to couple to the electronic device 116. The data structure may be installed during manufacture, for example. In another example, the data structure may be installed by an administrator having a security access to the electronic device 116. In yet another example, the data structure may be populated or updated as trusted host devices are identified using a security key. By verifying that the identifier of the host device 102 matches an identifier of a host device having a trusted relationship with the electronic device 116, the electronic device 116 may prevent an unauthorized host device from accessing a network connection of the electronic device 116.

[0017] The electronic device 116 may initiate a docking sequence with the host device 102 based on the signal strength and the verification of the identifier, in various examples. As described above, the docking sequence is a series of actions the electronic device 116 and the host device 102 perform to verify a connection, a speed of the connection, or an authorization of the connection. Initiating the docking sequence may include bringing the peripheral device 128 out of a low-power state, enabling a communication link with the peripheral device 128, transmitting a signal to the host device 102 to acknowledge that the docking sequence has started, transmitting a signal to the host device 102 comprising profile data of the electronic device 116, or some combination thereof. Bringing a device out of a low-power state may include restoring power to a component or multiple components of the device, restoring a previous operating state of the device, or some combination thereof. For example, bringing a display device out of a low-power state may include enabling the display of the display device.

[0018] Enabling the communication link establishes a communication protocol with the peripheral device 128. Data of the communication link may include data transfer rates, data widths, or some combination thereof. For example, in response to the peripheral device 128 being a display device, the electronic device 116 may utilize Extended Display Interface Data (EDID) to establish the communication link. The EDID may include a manufacturer of the display device, a serial number of the display device, a filter type, data transfer rates supported by the display device, information related to a resolution (e.g., size, luminance, pixel mapping) of the display device, or some combination thereof. The EDID may be stored on the storage device 122, for example. The profile data of the electronic device 116 may include an identifier of the electronic device 116, an identifier of the peripheral device 128, the communication link data for the peripheral device 128, an EDID of the peripheral device 128 (when applicable), an identifier of additional peripheral devices coupled to the electronic device 116, a communication link data for each additional peripheral device, the EDID of each additional peripheral device (when applicable), or some combination thereof. [0019] In response to a signal transmitted by the electronic device 116 that acknowledges that the docking sequence has started, the host device 102 may bring itself out of a low-power state. The signal may be received by the wireless transceiver 104, for example. Bringing the host device 102 out of a low-power state may include restoring an operating state of an operating system of the host device 102, bringing the GPU 112 out of a low-power state, initiating a communication link with the peripheral device 128, or some combination thereof, as described below with respect to FIG. 4. In some examples, the host device 102 may leave some components (e.g., display device of host device 102 (not expressly shown)) in a low-power state. Leaving some components in a low- power state may reduce power consumption of the host device 102, reduce a number of actions performed in response to pausing or stopping the docking sequence (as described below with respect to FIG. 2), and prevent a user experience from being impacted by background tasks.

[0020] By initiating a docking sequence based on a wireless signal from the host device 102, the electronic device 116 and the host device 102 utilize a duration of time while the user may still be in transit to a work area that includes the electronic device 116 to perform the time-intensive actions of the docking sequence.

[0021] The electronic device 116 completes the docking sequence in response to determining that the host device 102 has been coupled via a wired connection to the electronic device 116, in some examples. Completing the docking sequence may include the electronic device 116 receiving a signal from the host device 102 via the port 126. The electronic device 116 may verify that an identifier of the signal matches an identifier of a trusted host device. In response to verification of the identifier, the electronic device 116 may enable signals to propagate to the peripheral device 128. In various examples, the host device 102 may provide a video signal to the electronic device 116 after the docking sequence is completed. In some examples, the final actions of the docking sequence are not discernible by a user. For example, the user may connect the port 114 of the host device 102 to the port 126 of the electronic device 116 utilizing a cable (e.g., Ethernet cable, USB cable) and the video signal may appear to be instantaneously available or nearly instantaneously for viewing on a display of the peripheral device 128.

[0022] Referring now to FIG. 2, a schematic diagram of the electronic device 116 for signal strength based dockings is depicted, in accordance with various examples. As described above with respect to FIG. 1 , the electronic device 116 comprises the wireless transceiver 118, the port 126, the storage device 122, and the controller 120 coupled to the wireless transceiver 118, the port 126, and the storage device 122. The storage device 122 may store computer-readable instructions 200, 202, 204, 206, and 208. The computer-readable instructions 200, 202, 204, 206, 208 may be the computer-readable instructions 124, for example.

[0023] In various examples, when executed by the controller 120, the computer- readable instructions 200, 202, 204, 206, 208 cause the electronic device 116 to initiate a docking sequence based on a signal strength. Execution of the computer-readable instruction 200 may cause the controller 120 to verify an identifier of a signal. As described above with respect to FIG. 1 , the signal may be a signal transmitted by the wireless transceiver 104 of the host device 102, for example. The signal may be received by the wireless transceiver 118, for example. The controller 120 may verify that the identifier of the signal matches an identifier of a host device having a trusted relationship with the electronic device 116 utilizing any of the actions described above with respect to FIG. 1. Execution of the computer-readable instruction 202 may cause the controller 120 to determine that a strength of the signal exceeds a threshold. The threshold may be stored in the storage device 122, for example. Execution of the computer- readable instruction 204 may cause the controller 120 to initiate, based on the verification and the determination, a docking sequence. Execution of the computer-readable instruction 206 may cause the controller 120 to detect that the host device 102 is physically coupled to the port 126. Execution of the computer- readable instruction 208 may cause the controller 120 to complete, based on the detection, the docking sequence. The controller 120 may complete the docking sequence using the actions described above with respect to FIG. 1 , for example. [0024] In some examples, the storage device 122 may store the threshold. In response to the controller 120 determining that the strength of the signal has a value greater than the threshold, the controller 120 may initiate the docking sequence utilizing the actions described above with respect to FIG. 1. In other examples, the storage device 122 may include a data structure of thresholds. The controller 120 may compare the strength of the signal to the thresholds to determine what actions to perform. For example, the controller 120 may compare the strength of the signal to a first threshold. In response to the strength of the signal having a value greater than the first threshold, the controller 120 may bring the peripheral device 128 out of a low-power state, initiate a communication link with the peripheral device 128, or some combination thereof. The controller 120 may initiate the communication link with the peripheral device 128 by utilizing the actions described above with respect to FIG. 1. In another example, the controller 120 may compare the strength of the signal to a second threshold. In response to the strength of the signal having a value greater than the second threshold, the controller 120 may cause the wireless transceiver 118 to transmit a signal to the host device 102. In various examples, the signal may comprise an identifier of the electronic device 116. In yet another example, the controller 120 may cause the wireless transceiver 118 to transmit another signal comprising an identifier of the peripheral device 128. In further examples, the controller 120 may cause the wireless transceiver 118 to transmit yet another signal comprising communication link data of the peripheral device 128. [0025] In other examples, the storage device 122 may include a data structure of ranges of RSSI values and corresponding distances associated with the RSSI ranges. The controller 120 may compare the strength of the signal to the RSSI ranges to determine that a corresponding distance of the signal. The controller 120 may compare the corresponding distance to a threshold. If the corresponding distance matches or has a value less than the threshold, the controller 120 may initiate the docking sequence. For example, in response to the strength of the signal having a value within a first RSSI range, the controller 120 may determine that a corresponding distance of 10 feet. The controller 120 may compare 10 feet to a threshold having a value of 10 feet. In response to the corresponding distance matching the threshold, the controller 120 may bring the peripheral device 128 out of a low-power state, initiate a communication link with the peripheral device 128, or some combination thereof. In another example, the controller 120 may compare the strength of the signal to a second RSSI range. In response to the strength of the signal having a value within the second RSSI range, the controller 120 may determine that a corresponding distance of 5 feet. The controller 120 may compare 5 feet to a threshold of 6 feet. In response to the corresponding distance having a value that is less than the threshold, the controller 120 may bring the peripheral device 128 out of a low-power state, initiate a communication link with the peripheral device 128, cause the wireless transceiver 118 to transmit a signal to wake the host device 102, or some combination thereof.

[0026] In some examples, the wireless transceiver 118 receives a second signal from the host device 102. The controller 120 may determine that an identifier of the second signal does not match an identifier of a trusted host device. In response to the failed verification of the identifier of the second signal, the controller 120 may terminate the docking sequence. Terminating the docking sequence may include allowing the peripheral device 128 to return to a low-power state, disabling the communication link with the peripheral device 128, or some combination thereof. In other examples, the controller 120 may determine that a strength of the second signal falls below the threshold. The controller 120 may utilize a data structure, as described above, in the determination, for example. In response to the strength of the second signal falling below the threshold, the controller 120 may terminate the docking sequence. By terminating the docking sequence based on the strength of the second signal falling below the threshold, the controller 120 may be predicting a user intent to not couple the host device 102 to the electronic device 116.

[0027] In yet other examples, in response to the strength of the second signal falling below the threshold, the controller 120 may pause the docking sequence to monitor for a third signal from the host device 102. Pausing the docking sequence may include not establishing a communication link with the peripheral device 128, not transmitting a signal to the host device 102, or some combination thereof. In response to a verification of an identifier of the third signal and a determination that a strength of the third signal exceeds the threshold, the controller 120 may resume the docking sequence. By pausing the docking sequence based on the strength of the second signal falling below the threshold and resuming the docking sequence based on the strength of the third signal exceeding the threshold, the controller 120 may be predicting a user intent to couple the host device 102 to the electronic device 116.

[0028] The wireless transceiver 118 receives a second signal from the host device 102 in some examples. The controller 120 calculates a slope based on the strength of the first signal and the strength of the second signal. In response to the slope having a negative value, the controller 120 may terminate the docking sequence. The slope having a negative value indicates a decreasing signal strength. The decreasing signal strength may indicate that the user is moving away from the electronic device 116 and may not intend to couple the host device 102 to the electronic device 116. In further examples, in response to the negative slope, the controller 120 may pause the docking sequence to monitor for a third signal from the host device 102. The controller 120 may calculate a second slope based on the strength of the second signal and a strength of the third signal. In response to the second slope having a positive value, the controller 120 may resume the docking sequence. The slope having a positive value indicates an increasing signal strength. The increasing signal strength may indicate that the user is moving toward the electronic device 116 and may intend to couple the host device 102 to the electronic device 116.

[0029] Referring now to FIG. 3, a schematic diagram of the electronic device 116 for signal strength based dockings is depicted, in accordance with various examples. As described above with respect to FIGS. 1 and 2, the electronic device 116 comprises the wireless transceiver 118, the port 126, the storage device 122, and the controller 120 coupled to the wireless transceiver 118, the port 126, and the storage device 122. The storage device 122 may store computer-readable instructions 300, 302, 304, and 306. The computer-readable instructions 300, 302, 304, 306 may be the computer-readable instructions 124, for example.

[0030] In various examples, when executed by the controller 120, the computer- readable instructions 300, 302, 304, 306 cause the electronic device 116 to initiate a docking sequence based on signal strengths. Execution of the computer-readable instruction 300 may cause the controller 120 to verify that an identifier of a first signal matches an identifier of a trusted host device. As described above with respect to FIGS. 1 and 2, the first signal may be a signal transmitted by the wireless transceiver 104 of the host device 102, for example. The signal may be received by the wireless transceiver 118, for example. The controller 120 may verify that the identifier of the signal matches an identifier of a host device having a trusted relationship with the electronic device 116 utilizing any of the actions described above with respect to FIGS. 1 and 2. Execution of the computer-readable instruction 302 may cause the controller 120 to determine that a strength of the first signal exceeds a threshold. The controller 120 may determine that the strength of the first signal exceeds the threshold using the actions described above with respect to FIG. 2. Execution of the computer- readable instruction 304 may cause the controller 120 to initiate, based on the verification and the determination, a communication link with a peripheral device. The peripheral device may be the peripheral device 128, for example. The controller 120 may initiate the communication link with the peripheral device using the actions described above with respect to FIGS. 1 and 2. Execution of the computer-readable instruction 306 may cause the controller 120 to cause, based on the verification and the determination, the wireless transceiver 118 to transmit a second signal comprising profile data of the electronic device 116 to the host device 102. The controller 120 may cause the wireless transceiver 118 to transmit the second signal comprising profile data, as described above with respect to FIGS. 1 and 2, for example.

[0031] In various examples, the controller 120 detects that the host device 102 is coupled to the port 126. In response to detecting that the host device 102 is coupled to the port 126, the controller 120 completes the communication link with the peripheral device 128. As described above with respect to FIG. 1 , completing the docking sequence may include the electronic device 116 receiving a video signal from the host device 102 via the port 126. The electronic device 116 may verify that an identifier of the video signal matches an identifier of a trusted host device. In response to verification of the identifier, the electronic device 116 may enable the video signal to propagate to the peripheral device 128. Enabling the video signal provided by the electronic device 116 to propagate to the peripheral device 128 may be referred to as completing the communication link with the peripheral device 128, for example.

[0032] In some examples, the controller 120 detects that the host device 102 is coupled to the port 126. In response to detecting that the host device 102 is coupled to the port 126, the controller 120 may cause a transfer of the profile data of the electronic device 116 to the host device 102 utilizing the port 126. The host device 102 may store the profile data to decrease a duration of a future docking sequence.

[0033] Referring now to FIG. 4, a schematic diagram of the host device 102 for signal strength based dockings is depicted, in accordance with various examples. As described above with respect to FIG. 1 , the host device 102 comprises the wireless transceiver 104, the GPU 112, the port 114, the storage device 108, and the processor 106 coupled to the wireless transceiver 104, the GPU 112, the port 114, and the storage device 108. The storage device 108 may store computer- readable instructions 400, 402, 404, and 406. The computer-readable instructions 400, 402, 404, 406 may be the computer-readable instructions 110, for example. [0034] In various examples, when executed by the processor 106, the computer-readable instructions 400, 402, 404, 406 cause the host device 102 to initiate a docking sequence based on a signal strength. Execution of the computer-readable instruction 400 may cause the processor 106 to verify that an identifier of a signal matches an identifier of a trusted electronic device. The signal may be transmitted by the wireless transceiver 118 of the electronic device 116, for example. The signal may be received by the wireless transceiver 104, for example. Execution of the computer-readable instruction 402 may cause the processor 106 to initiate, based on the verification, handshaking between the GPU 112 and the electronic device 116. Execution of the computer-readable instruction 404 may cause the processor 106 to detect that the electronic device 116 is coupled to the port 114. Execution of the computer-readable instruction 406 may cause the processor 106 to provide, based on the detection, a video signal to the electronic device 116.

[0035] In some examples, the wireless transceiver 118 of the electronic device 116 transmits a signal. As described above, the signal may be a BT or a WI-FI signal. In various examples, the signal may be transmitted even in instances where the electronic device 116 is in a low-power state. For example, the signal may be a BLUETOOTFI® Low Energy (BLE) signal. The wireless transceiver 104 of the host device 102 may receive the signal, and the processor 106 may verify that an identifier of the signal matches an identifier of an electronic device having a trusted relationship with the host device 102. In some examples, an electronic device having a trusted relationship with the host device 102 may be referred to as a trusted electronic device. As described above with respect to FIG. 1 , the trusted relationship indicates that a security between the host device 102 and an electronic device has been established and that the electronic device has permission to connect to the host device 102.

[0036] For example, the storage device 108 of the host device 102 may include a security key. In response to the identifier of the electronic device 116 matching the security key, the processor 106 may determine that the electronic device 116 is a trusted electronic device. In another example, the storage device 108 may include a data structure of identifiers of electronic devices that have coupled to the host device 102 in the past or that have been granted permission to couple to the host device 102. The data structure may be installed during manufacture, for example. In another example, the data structure may be installed by an administrator having a security access to the host device 102. The processor 106 may compare the identifier of the electronic device 116 to identifiers of the data structure to determine whether the electronic device 116 is a trusted electronic device, for example. By verifying that the identifier matches an identifier of a trusted electronic device, the processor 106 may prevent an unauthorized electronic device from accessing the host device 102.

[0037] In other examples, in response to verifying that the identifier matches an identifier of a trusted electronic device, the processor 106 may bring the host device 102 out of a low-power state. Bringing the host device 102 out of a low- power state may include restoring an operating state of an operating system of the host device 102, bringing the GPU 112 out of a low-power state, initiating a communication link with the electronic device 116, or some combination thereof. For example, the processor 106 may initiate handshaking between the electronic device 116 and the GPU 112. To initiate handshaking between the electronic device 116 and the GPU 112, the processor 106 may cause the GPU 112 to exit a low-power state, may initiate a communication link between the GPU 112 and the electronic device 116, or a combination thereof. Initiating the communication link establishes a communication protocol between the GPU 112 and the electronic device 116. As described above with respect to FIG. 1 , data of the communication link may include data transfer rates, data widths, or some combination thereof. In another example, the processor 106 may bring a sub system (e.g., GPU 112) out of a low-power state while leaving other sub-systems (e.g., display device (not expressly shown)) in a low-power state. Leaving some components in a low-power state may reduce power consumption of the host device 102, reduce a number of actions performed in response to pausing or stopping the docking sequence (as described above with respect to FIG. 2), and prevent a user experience from being impacted by background tasks.

[0038] In various examples, the storage device 108 stores profile data of a trusted electronic device. In response to verifying that an identifier of the signal matches an identifier of a trusted electronic device, the processor 106 may initiate a communication link between the GPU 112 and the peripheral device 128 based on the stored profile data. For example, the profile data stored on the storage device 108 may include an identifier of the electronic device 116, a communication link data for the electronic device 116, a communication link data for the peripheral device 128, an identifier of additional peripheral devices coupled to the electronic device 116, a communication link data for each additional peripheral device, or some combination thereof. In some examples, such as when the peripheral device 128 is a display device, the communication link data may comprise EDID for the display device.

[0039] In some examples, the signal received from the electronic device 116 comprises profile data of the electronic device 116. In response to receiving the profile data of the electronic device 116, the processor 106 initiates handshaking between the GPU 112 and the electronic device 116 by causing the GPU 112 to exit a low-power state. The processor 106 enables a communication link between the GPU 112 and the electronic device 116 based on the profile data of the electronic device 116 received in the signal.

[0040] In other examples, the processor 106 detects the electronic device 116 is physically coupled to the port 114. For example, the processor 106 may detect a signal at the port 114. The processor 106 may determine that the signal comprises profile data of the electronic device 116. The processor 106 may store the profile data to the storage device 108. By storing the profile data, a duration of a future docking sequence with the electronic device 116 may be decreased. In some examples, in response to detecting the electronic device 116 coupled to the port 114, the processor 106 enables a video signal to propagate from the GPU 112 to the electronic device 116 to complete the docking sequence. In another example, the host device 102 may bring the display device of the host device 102 out of a low-power state in response to the processor 106 detecting the electronic device 116 is physically coupled to the port 114. In various examples, the host device 102 may enable the video signal based on a sensor indicating that a display device of the host device 102 is enabled. For example, the sensor may be an open notebook sensor or a camera on display sensor. [0041] Implementing an electronic device 116 for signal strength based docking or a host device 102 for signal strength based docking as described above increases security between the electronic device 116 and the host device 102; increases efficiency of the docking process; and provides an improved user experience.

[0042] The above discussion is meant to be illustrative of the principles and various examples of the present disclosure. Numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.

[0043] In the figures, certain features and components disclosed herein may be shown exaggerated in scale or in somewhat schematic form, and some details of certain elements may not be shown in the interest of clarity and conciseness. In some of the figures, in order to improve clarity and conciseness, a component or an aspect of a component may be omitted.

[0044] In the above discussion and in the claims, the term "comprising" is used in an open-ended fashion, and thus should be interpreted to mean "including, but not limited to... ." Also, the term "couple" or "couples" is intended to be broad enough to encompass both indirect and direct connections. Thus, if a first device couples to a second device, that connection may be through a direct connection or through an indirect connection via other devices, components, and connections. As used herein, including in the claims, the word “or” is used in an inclusive manner. For example, “A or B” means any of the following: “A” alone, “B” alone, or both “A” and “B.”

Claims

CLAIMS What is claimed is:

1. An electronic device, comprising: a port; a wireless transceiver to receive a signal from a host device; and a controller coupled to the port and the wireless transceiver, the controller to: verify an identifier of the signal; determine that a strength of the signal exceeds a threshold; initiate, based on the verification and the determination, a docking sequence; detect that the host device is coupled to the port; and complete, based on the detection, the docking sequence.

2. The electronic device of claim 1 , wherein the wireless transceiver is to receive a second signal from the host device, and wherein the controller is to: terminate the docking sequence in response to a failed verification of an identifier of the second signal or a determination that a strength of the second signal falls below the threshold.

3. The electronic device of claim 1 , wherein the wireless transceiver is to receive a second signal from the host device, and wherein the controller is to: calculate a slope based on the strength of the signal and a strength of the second signal; and terminate the docking sequence in response to the slope having a negative value.

4. The electronic device of claim 1 , wherein the controller is to cause the wireless transceiver to transmit a second signal comprising an identifier of the electronic device to the host device.

5. The electronic device of claim 1 , wherein the controller is to cause the wireless transceiver to: transmit a second signal comprising an identifier of a display device coupled to the electronic device; and transmit a third signal comprising communication link data of the display device to the host device.

6. An electronic device, comprising: a wireless transceiver to receive a first signal from a host device; and a controller coupled to the wireless transceiver, the controller to: verify that an identifier of the first signal matches an identifier of a trusted host device; determine that a strength of the first signal exceeds a threshold; initiate, based on the verification and the determination, a communication link with a peripheral device; and cause, based on the verification and the determination, the wireless transceiver to transmit a second signal comprising profile data of the electronic device to the host device.

7. The electronic device of claim 6, wherein the profile data comprises an identifier for the electronic device, an identifier for the peripheral device, a communication link data of the peripheral device, or a combination thereof.

8. The electronic device of claim 7, wherein the peripheral device comprises a display device.

9. The electronic device of claim 6, wherein the electronic device comprises a port, and wherein the controller is to: detect that the host device is coupled to the port; and complete, based on the detection, the communication link with the peripheral device.

10. The electronic device of claim 9, wherein the controller is to cause transfer of the profile data to the host device through the port.

11. The electronic device of claim 6, wherein the wireless transceiver is to receive a second signal from the host device and the controller is to: calculate a slope based on the strength of the first signal and a strength of the second signal; and terminate the communication link based on the slope having a negative value.

12. A host device, comprising: a port; a graphics processing unit (GPU); a wireless transceiver to receive a signal from an electronic device; and a processor coupled to the port, the GPU, and the wireless transceiver, the processor to: verify that an identifier of the signal matches an identifier of a trusted electronic device; initiate, based on the verification, handshaking between the GPU and the electronic device; detect that the electronic device is coupled to the port; and provide, based on the detection, a video signal to the electronic device.

13. The host device of claim 12, wherein the signal comprises profile data of the electronic device, and wherein the processor is to initiate handshaking between the GPU and the electronic device by: causing the GPU to exit a low-power state; and enabling a communication link between the GPU and the electronic device based on the profile data of the electronic device.

14. The host device of claim 13, wherein the host device comprises a storage device coupled to the processor, and wherein the processor is to: detect, at the port, a second signal comprising a second profile data of the electronic device; and store the second profile data to the storage device.

15. The host device of claim 12, wherein the host device comprises a storage device coupled to the processor, the storage device to store profile data of the trusted electronic device, and wherein the processor is to initiate, based on the verification, a communication link between the GPU and the electronic device based on the stored profile data of the trusted electronic device.