BACKGROUND OF THE INVENTION

[0001] A variety of data is commonly exchanged via wireless short-range or near- field interconnections, for example, via a Bluetooth® interconnection. To protect private data, many wireless devices are configured to recognize specific devices with which they can establish a connection. The process of establishing a connection between wireless devices is often referred to as "pairing." In many instances, secure pairing schemes involve considerable user interaction. For example, secure pairing schemes may require a user to enter or confirm a passkey on both devices. In other cases, secure pairing schemes may require additional hardware, such as a near-field communication (NFC) chip, microphones, accelerometers, or other devices.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

[0002] The accompanying figures, where like reference numerals refer to identical or functionally similar elements throughout the separate views, together with the detailed description below, are incorporated in and form part of the specification, and serve to further illustrate embodiments of concepts that include the claimed invention, and explain various principles and advantages of those embodiments.

[0003] FIG. 1 is a diagram of a system for pairing wireless devices in accordance with some embodiments.

[0004] FIG. 2 is a diagram of a pairing device in accordance with some embodiments.

[0005] FIG. 3 is a diagram of a host device in accordance with some embodiments.

[0006] FIG. 4 is a diagram of a guest device in accordance with some embodiments.

[0007] FIG. 5 is a flowchart of a method of secure zone pairing in accordance with some embodiments.

[0008] FIG. 6 is a flowchart of a method of secure zone pairing in accordance with some embodiments. [0009] Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of embodiments of the present invention.

[0010] The apparatus and method components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments of the present invention so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

DETAILED DESCRIPTION OF THE INVENTION

[0011] One embodiment provides a host device including a transceiver and an electronic processor electrically coupled to the transceiver. The electronic processor is configured to receive, from a pairing device via the transceiver, a low-power broadcast message when the host device is within a broadcast zone of the pairing device, the low-power broadcast message including pairing information. The electronic processor is also configured to transmit, via the transceiver, a first indication that the host device is within the broadcast zone of the pairing device after receiving the low-power broadcast message. The electronic processor is further configured to receive, from a guest device via the transceiver, a second indication that the guest device is within the broadcast zone of the pairing device and pair with the guest device based on the pairing information of the low-power broadcast message and the second indication.

[0012] Another embodiment provides a method of secure zone pairing including receiving, with a host device, a low-power broadcast message when the host device is within a broadcast zone of a pairing device, the low-power broadcast message including pairing information. The method also includes transmitting, via a transceiver of the host device, a first indication that the host device is within the broadcast zone of the pairing device after receiving the low-power broadcast message. The method further includes receiving, via the transceiver, a second indication that a guest device is within the broadcast zone of the pairing device and pairing, with a processor of the host device, the host device with the guest device based on the pairing information of the low-power broadcast message and the second indication.

[0013] Another embodiment provides a system for pairing wireless devices including a pairing device having a transmitter configured to transmit a low-power broadcast message within a broadcast zone having a size. The low-power broadcast message includes pairing information. The system also includes a guest device. The guest device has a first transceiver and is configured to receive the low-power broadcast message and transmit an indication that the guest device is within the broadcast zone after receiving the low-power broadcast message. The system further includes a host device having a second transceiver and is configured to receive the indication and the low-power broadcast message. The host device is further configured to pair with the guest device based on the pairing information of the low-power broadcast message and the indication.

[0014] Yet another embodiment provides a method of secure zone pairing including transmitting, with a transmitter of a pairing device, a low-power broadcast message within a broadcast zone having a size, where the low-power broadcast message includes pairing information. The method also includes receiving, with a first transceiver of a guest device within the broadcast zone, the low-power broadcast message and transmitting, with the first transceiver, an indication that the guest device is within the broadcast zone after receiving the low-power broadcast message. The method further includes receiving, with a second transceiver of a host device within the broadcast zone, the indication and the low-power broadcast message and pairing the host device with the guest device based on pairing information of the low-power broadcast message and the indication.

[0015] FIG. 1 is a diagram of a system 100 for pairing wireless devices. In the example illustrated, the system 100 includes a pairing device 110, a host device 120, and a guest device 130. The pairing device 110 generates a low-power wireless signal including a low-power broadcast message that is transmitted within a broadcast zone 140. The low-power broadcast message may include pairing information, for example, a service identifier and a passkey.

[0016] The host device 120 and the guest device 130 are devices that may be paired with each other to exchange information without using wires or cables. Therefore, they are referred to as "wireless devices." The host device 120 may be, for example, a mobile two-way radio, a smart telephone, or other similar device. The guest device 130 may be for example, a Bluetooth® headset, a smart watch, wireless touch pad, or other similar device. In some embodiments, the functionality of the host device 120, as described herein, may be performed by the guest device 130 and the functionality of the guest device 130, as described herein, may be performed by the host device 120. The host device 120 and the guest device 130 are configured to receive the low-power broadcast message when they are within the broadcast zone 140. A device outside the broadcast zone 140, for example, the device 150 does not receive the low-power broadcast message.

[0017] The size of the broadcast zone 140 is adjustable based on the strength of the low-power wireless signal generated by the pairing device 110. As such, the size of the broadcast zone 140 may be increased or decreased based on the strength of the wireless signal generated by the pairing device 110. That is, when the power of the wireless signal is increased, the area covered by the broadcast zone 140 is increased. Similarly, when the power of the wireless signal is decreased, the area covered by the broadcast zone 140 is decreased.

[0018] FIG. 1 illustrates only one exemplary embodiment of a system 100 for pairing wireless devices. In other embodiments, the system 100 may include more of fewer components and may perform functions that are not explicitly described herein.

[0019] FIG. 2 is a diagram of one embodiment of the pairing device 110. In the example illustrated, the pairing device 110 includes an electronic processor 210, a memory 220, a transceiver 230, and an optional input/output interface 240. The electronic processor 210, the memory 220, the transceiver 230, and the input/output interface 240 communicate over one or more control and/or data buses (for example, a communication bus 250). FIG. 2 illustrates only one exemplary embodiment of the pairing device 1 10. The pairing device 110 may include more or fewer components and may perform functions other than those explicitly described herein.

[0020] In some embodiments, the electronic processor 210 is implemented as microprocessor with separate memory, such as the memory 220. In other embodiments, the electronic processor 210 may be implemented as a microcontroller (with memory 220 on the same chip). In other embodiments, the electronic processor 210 may be implemented using multiple processors. In addition, the electronic processor 210 may be implemented partially or entirely as, for example, a field- programmable gate array (FPGA), an application specific integrated circuit (ASIC), and the like and the memory 220 may not be needed or be modified accordingly. In the example illustrated, the memory 220 includes non-transitory, computer-readable memory that stores instructions that are received and executed by the electronic processor 210 to carry out functionality of the pairing device 110 described herein. The memory 220 may include, for example, a program storage area and a data storage area. The program storage area and the data storage area may include combinations of different types of memory, such as a read-only memory and random-access memory.

[0021] The transceiver 230 enables wireless communication from the pairing device 110 to, for example, the host device 120 and the guest devices 130 that are within the broadcast zone 140. In other embodiments, rather than the transceiver 230, the pairing device 1 10 may include separate transmitting and receiving components, for example, a transmitter, and a receiver. In yet other embodiments, the pairing device 110 may only include a transmitter that transmits the low-power broadcast message.

[0022] The input/output interface 240 may include one or more input mechanisms (for example, a touch pad, a button, a knob, and the like), one or more output mechanisms (for example, a display, a speaker, light emitting diodes (LEDs). and the like), or a combination thereof or a combined input and output mechanism such as a touch screen.

[0023] As described above, the pairing device 110 is configured to generate a low- power wireless signal. The pairing device 110 transmits the low-power wireless signal including the low-power broadcast message using the transceiver 230 or a transmitter of the pairing device 1 10. In some embodiments, the pairing device 1 10 is compliant with Bluetooth® Low-Energy (LE) standards. Specifications for the Bluetooth® Low-energy standards can be found at

https://www.bluetooth.com/specifications/adopted -specifications. Accordingly, the pairing device 1 10 may have a maximum transmit power of 10 milli-Watts (mW). Further, the transmit power of the pairing device 110 may be configurable to adjust the size of the broadcast zone 140. For example, the transmit power of the pairing device 1 10 may be varied between O.OlmW and lOmW. In some embodiments, the transmit power of the pairing device 110 may be under ImW to achieve a secure zone with a radius less than 1 meter (m).

[0024] In some embodiments, the pairing device 1 10 is a device solely operating as a pairing device. In other embodiments, the pairing device 110 is a wireless communication capable device configured to function as a pairing device. For example, the functionality of the pairing device 1 10 may be built into a mobile two- way radio, a smart telephone, a wireless-capable universal serial bus (USB) dongle that can be plugged into a laptop, and the like. In yet other embodiments, the functionality of the pairing device 1 10 may be built into the host device 120 or the guest device 130.

[0025] FIG. 3 is a diagram of one embodiment of the host device 120. In the example illustrated, the host device 120 includes a host electronic processor 310, a host memory 320, a host transceiver 330, and a host input/output interface 340. The host electronic processor 310, the host memory 320, the host transceiver 330, and the host input/output interface 340 communicate over one or more control and/or data buses (for example, a host communication bus 350). FIG. 3 illustrates only one exemplary embodiment of the host device 120. The host device 120 may include more or fewer components and may perform functions other than those explicitly described herein.

[0026] The host electronic processor 310 may be implemented in various ways including ways that are similar to those described above with respect to the electronic processor 210. Likewise, the host memory 320 may be implemented in various ways including ways that are similar to those described with respect to the memory 220. The host memory 320 may store instructions that are received and executed by the host electronic processor 310 to carry out functionality described herein.

[0027] The host transceiver 330 enables wireless communication for the host device 120, for example, with the pairing device 110 and/or the guest device 130. In other embodiments, rather than a host transceiver 330, the host device 120 may include separate transmitting and receiving components, for example, a transmitter, and a receiver.

[0028] The host input/output interface 340 may include one or more input mechanisms (for example, a touch pad, a keypad, a button, a knob, and the like), one or more output mechanisms (for example, a display, a speaker, and the like), or a combination thereof or a combined input and output mechanism such as a touch screen.

[0029] FIG. 4 is a diagram of one embodiment of the guest device 130. In the example illustrated, the guest device 130 includes a guest electronic processor 410, a guest memory 420, a guest transceiver 430, and a guest input/output interface 440. The guest electronic processor 410, the guest memory 420, the guest transceiver 430, and the guest input/output interface 440 communicate over one or more control and/or data buses (for example, a guest communication bus 450). FIG. 4 illustrates only one exemplary embodiment of the guest device 130. The guest device 130 may include more or fewer components and may perform functions other than those explicitly described herein.

[0030] The guest electronic processor 410 and the guest memory 420 may be implemented in various ways including ways that are similar to those described above with respect to other processors and memory. Likewise, the guest memory 420 may store instructions that are received and executed by the guest electronic processor 410 to carry out functionality described herein.

[0031] The guest transceiver 430 enables wireless communication for the guest device 130, for example, with the pairing device 110 and/or the host device 120. In other embodiments, rather than a guest transceiver 430, the guest device 130 may include separate transmitting and receiving components, for example, a transmitter, and a receiver.

[0032] The guest input/output interface 440 may include components similar to those described with respect to the host input/output interface 340.

[0033] FIG. 5 is a flowchart illustrating one example method 400 of secure zone pairing. As illustrated in FIG. 5, the method 500 includes transmitting, with the pairing device 110, a low-power broadcast message within the broadcast zone 140 (at block 510). The low-power broadcast message includes pairing information that is used by the host device 120 to pair with the guest device 130. The pairing device 110 transmits the low-power broadcast message with the transceiver 230 or a transmitter of the pairing device 110.

[0034] The pairing information includes, for example, a pairing service identifier, a passkey, and a timeout value. The pairing service identifier may be a service identifier assigned to secure zone pairing service and provided to devices capable of secure zone pairing. In some embodiments, the pairing service identifier allows other devices, such as the host device 120 and the guest device 130 to recognize the pairing device 110 and initiate a secure zone pairing operation. The passkey is, for example, a random number generated by the pairing device 110 to be exchanged between the host device 120 and the guest device 130. The timeout value specifies the amount of time after which the passkey expires. Accordingly, the pairing device 110 may generate a new passkey after an old passkey expires. For example, the pairing device 110 may generate a new passkey every one minute.

[0035] The guest device 130 receives the low-power broadcast message when the guest device 130 is within the broadcast zone 140 (at block 520). The guest device 130 receives the low-power broadcast message via the guest transceiver 430 (for example, a first transceiver) of the guest device 130. In some embodiments, the guest device 130 receives a user input to enable the secure zone pairing mode. In these embodiments, the guest device 130 is configured to receive the low-power broadcast message when in the secure zone pairing mode. [0036] After receiving the low-power broadcast message, the guest device 130 transmits an indication that the guest device 130 is within the broadcast zone 140 (at block 530). The guest device 130 transmits the indication via the guest transceiver 430 (that is, a first transceiver) of the guest device 130. When in the broadcast zone 140, the guest device 130 transmits, for example, a service identifier, a guest device identifier, and a flag. The service identifier indicates that the device is capable of secure zone pairing. In some embodiments, the service identifier may be the service identifier received as part of the pairing information. The guest device identifier includes identifying information about the guest device 130 that enables other devices, such as the host device 120 to pair with the guest device 130. The guest device identifier is, for example, a serial number assigned to the guest device 130 or other identifying information of the guest device 130. The flag indicates whether the guest device 130 is currently within the broadcast zone 140. The indication may include the service identifier, the guest device identifier, and the flag. However, in some implementations, the indication may include only the flag indicating that the guest device 130 is within the broadcast zone 140. In some embodiments, the guest device 130 transmits the indication only when in the secure zone pairing mode.

[0037] The host device 120 receives the low-power broadcast message from the pairing device 1 10 and the indication from the guest device 130 when the host device 120 is within the broadcast zone 140 (at block 540). The host device 120 receives the indication and the low-power broadcast message via the host transceiver 330 (for example, a second transceiver). In some embodiments, the host device 120 receives a user input to enable the secure zone pairing mode. In these embodiments, the host device 120 is configured to receive the low-power broadcast message when in the secure zone pairing mode.

[0038] In some embodiments, the host device 120 also transmits an indication (for example, a third indication) that the host device 120 is within the broadcast zone 140. The indication transmitted by the host device 120 may include information similar to that described above with respect to the indication transmitted by the guest device 130. In some embodiments, the host device 120 transmits the indication only when in the secure zone pairing mode.

[0039] The host device 120 pairs with the guest device 130 based on the pairing information included in the low-power broadcast message received from the pairing device 1 10 and the indication received from the guest device 130 (at block 550). That is, the host device 120 establishes a connection with the guest device 130 by exchanging, without user interaction, the passkey included in the low-power broadcast message when the guest device 130 and host device 120 are within the broadcast zone 140. The host device 120 initiates the passkey exchange when the indication received from the guest device 130 indicates that the guest device 130 is within the broadcast zone 140. Similarly, the guest device 130 accepts the passkey exchange when the indication received from the host device 120 indicates that the host device 120 is within the broadcast zone 140. The pairing initiated is, for example, utilizing Classic Bluetooth® pairing, Wi-Fi™ direct pairing, and the like.

[0040] FIG. 6 is a flowchart illustrating one example method 600 of secure zone pairing. As illustrated in FIG. 6, the method 600 includes receiving, with the host device 120, the low-power broadcast message when the host devicel20 is within the broadcast zone 140 of the pairing device 1 10 (at block 610). As described above, the low-power broadcast message includes pairing information that is used by the host device 120 to pair with the guest device 130. The host device 120 may be configured to receive the low-power broadcast message when the secure zone pairing mode is enabled.

[0041] After receiving the low-power broadcast message, the host device 120 transmits, via the host transceiver 330, a first indication that the host device 120 is within the broadcast zone 140 of the pairing device 110 (at block 620). As described above, in some embodiments, the host device 120 transmits the first indication only when the host device 120 is in the secure zone pairing mode. The host device 120 also receives, via the host transceiver 330, a second indication from the guest device 130 that the guest device 130 is within the broadcast zone 140 of the pairing device 110 (at block 630). [0042] The host device 120 pairs with the guest device 130 based on the pairing information included in the low-power broadcast message received from the pairing device 1 10 and the second indication received from the guest device 130 (at block 640). As described above, the pairing is initiated when the first indication and the second indication indicate that the host device 120 and the guest device 130 are both within the broadcast zone 140. The pairing is performed by, for example, exchanging the passkey included in the pairing information.

[0043] In some embodiments, the pairing device 1 10 may include additional security features to notify a user when the broadcast zone 140 is not secure. For example, the pairing device 1 10 may scan for other devices that are capable of secure zone pairing, such as other pairing devices. The pairing device 110 may detect another pairing device (for example, a second pairing device) by detecting a low-power broadcast message from the second pairing device that includes the pairing service identifier. When the pairing device 110 determines that there are other pairing devices nearby, the pairing device 1 10 provides an indication (for example, a second indication) to a user that the broadcast zone 140 is not secure. The pairing device 1 10 notifies the user by, for example, flashing an LED on the pairing device 110, changing the color of the LED on the pairing device 110, and the like.

[0044] In some embodiments, the low-power broadcast message may also include a secure zone number. The secure zone number may be randomly generated at power up of the pairing device 1 10. This secure zone number may also be included in the indications transmitted by the host device 120 and the guest device 130. This will allow the host device 120 to pair with the guest device 130 only when they are both in the same secure zone created by the broadcast zone 140 of the pairing device 1 10.

[0045] As described above, the pairing device 110, the host device 120, and the guest device 130 may communicate with one another using Bluetooth® low-energy signals. In some embodiments, the pairing device 110, the host device 120, and the guest device 130 may use other low-power communication techniques to communicate with one another. For example, the pairing device 110, the host device 120, and the guest device 130 may use ANT™ protocol, ZigBee® protocol, and the like. In addition to communicating within the broadcast zone using low-power technologies, the pairing device 1 10, the host device 120, and the guest device 130 are capable of

communicating with other devices (for example, device 150) using high-power communication technologies. For example, the pairing device 110, the host device 120, and the guest device 130 are capable of communicating with other devices using Bluetooth®, Wi-Fi™, and the like. Further, the pairing device 110, the host device 120, and the guest device 130 may also communicate over a communication network, such as, a cellular network , a land mobile radio (LMR) network, the Internet, and the like.

[0046] One advantage of the above techniques is that the techniques provide the similar or better security levels as using near field communication, or other out-of- band pairing mechanisms, but without requiring the end devices to have any special hardware.

[0047] In the foregoing specification, specific embodiments have been described. However, one of ordinary skill in the art appreciates that various modifications and changes can be made without departing from the scope of the invention as set forth in the claims below. Accordingly, the specification and figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of present teachings.

[0048] The benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential features or elements of any or all the claims. The invention is defined solely by the appended claims including any amendments made during the pendency of this application and all equivalents of those claims as issued.

[0049] Moreover in this document, relational terms such as first and second, top and bottom, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms "comprises," "comprising," "has," "having," "includes," "including," "contains," "containing" or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises, has, includes, contains a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises ... a," "has ... a," "includes ... a," or "contains ... a" does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises, has, includes, contains the element. The terms "a" and "an" are defined as one or more unless explicitly stated otherwise herein. The terms "substantially," "essentially," "approximately," "about" or any other version thereof, are defined as being close to as understood by one of ordinary skill in the art, and in one non-limiting embodiment the term is defined to be within 10%, in another embodiment within 5%, in another embodiment within 1% and in another embodiment within 0.5%. The term "coupled" as used herein is defined as connected, although not necessarily directly and not necessarily mechanically. A device or structure that is "configured" in a certain way is configured in at least that way, but may also be configured in ways that are not listed.

[0050] It will be appreciated that some embodiments may be comprised of one or more generic or specialized processors (or "processing devices") such as

microprocessors, digital signal processors, customized processors and field programmable gate arrays (FPGAs) and unique stored program instructions (including both software and firmware) that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the method and/or apparatus described herein. Alternatively, some or all functions could be implemented by a state machine that has no stored program instructions, or in one or more application specific integrated circuits (ASICs), in which each function or some combinations of certain of the functions are implemented as custom logic. Of course, a combination of the two approaches could be used.

[0051] Moreover, an embodiment can be implemented as a computer-readable storage medium having computer readable code stored thereon for programming a computer (e.g., comprising a processor) to perform a method as described and claimed herein. Examples of such computer-readable storage mediums include, but are not limited to, a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a ROM (Read Only Memory), a PROM (Programmable Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), an EEPROM (Electrically Erasable Programmable Read Only Memory) and a Flash memory. Further, it is expected that one of ordinary skill, notwithstanding possibly significant effort and many design choices motivated by, for example, available time, current technology, and economic considerations, when guided by the concepts and principles disclosed herein will be readily capable of generating such software instructions and programs and ICs with minimal experimentation.

[0052] The Abstract of the Disclosure is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in various embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter.