US20190350021A1 - Physical contact detection for device pairing - Google Patents

Physical contact detection for device pairing Download PDF

Info

Publication number
US20190350021A1
US20190350021A1 US15/978,991 US201815978991A US2019350021A1 US 20190350021 A1 US20190350021 A1 US 20190350021A1 US 201815978991 A US201815978991 A US 201815978991A US 2019350021 A1 US2019350021 A1 US 2019350021A1
Authority
US
United States
Prior art keywords
wireless
wireless device
physical contact
pairing
devices
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US15/978,991
Inventor
William R. Blum
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Honeywell International Inc
Original Assignee
Honeywell International Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Honeywell International Inc filed Critical Honeywell International Inc
Priority to US15/978,991 priority Critical patent/US20190350021A1/en
Assigned to HONEYWELL INTERNATIONAL INC. reassignment HONEYWELL INTERNATIONAL INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BLUM, WILLIAM R.
Publication of US20190350021A1 publication Critical patent/US20190350021A1/en
Priority to US17/117,591 priority patent/US11706827B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/005Discovery of network devices, e.g. terminals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/14Direct-mode setup
    • GPHYSICS
    • G01MEASURING; TESTING
    • G01PMEASURING LINEAR OR ANGULAR SPEED, ACCELERATION, DECELERATION, OR SHOCK; INDICATING PRESENCE, ABSENCE, OR DIRECTION, OF MOVEMENT
    • G01P15/00Measuring acceleration; Measuring deceleration; Measuring shock, i.e. sudden change of acceleration
    • G01P15/001Measuring acceleration; Measuring deceleration; Measuring shock, i.e. sudden change of acceleration by measuring acceleration changes by making use of a triple differentiation of a displacement signal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/04Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H04L63/0492Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload by using a location-limited connection, e.g. near-field communication or limited proximity of entities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/50Secure pairing of devices
    • GPHYSICS
    • G01MEASURING; TESTING
    • G01PMEASURING LINEAR OR ANGULAR SPEED, ACCELERATION, DECELERATION, OR SHOCK; INDICATING PRESENCE, ABSENCE, OR DIRECTION, OF MOVEMENT
    • G01P15/00Measuring acceleration; Measuring deceleration; Measuring shock, i.e. sudden change of acceleration
    • G01P15/02Measuring acceleration; Measuring deceleration; Measuring shock, i.e. sudden change of acceleration by making use of inertia forces using solid seismic masses
    • G01P15/08Measuring acceleration; Measuring deceleration; Measuring shock, i.e. sudden change of acceleration by making use of inertia forces using solid seismic masses with conversion into electric or magnetic values
    • G01P15/0891Measuring acceleration; Measuring deceleration; Measuring shock, i.e. sudden change of acceleration by making use of inertia forces using solid seismic masses with conversion into electric or magnetic values with indication of predetermined acceleration values
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60Context-dependent security
    • H04W12/61Time-dependent
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60Context-dependent security
    • H04W12/68Gesture-dependent or behaviour-dependent
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication

Definitions

  • the present disclosure relates generally to devices, methods, and systems for physical contact detection for device pairing.
  • Pairing may refer to and/or include a process used in computer networking to establish an initial link between computing devices that allows for communications between the devices to occur.
  • a mobile (e.g., smart) phone of the home's occupant may be paired with the central thermostat of the home to allow the home's occupant to control the thermostat (e.g., the settings of the thermostat) via the mobile phone.
  • Such a pairing of computing devices may present increased security risks for the devices, such as, for instance, unauthorized third party listening and/or hacking. These security risks can be reduced and/or eliminated by verifying that the pairing party (e.g., the person attempting to pair the devices) is in physical control (e.g., possession) of both devices (e.g., of both sides of the link).
  • the pairing party e.g., the person attempting to pair the devices
  • the pairing party is in physical control (e.g., possession) of both devices (e.g., of both sides of the link).
  • Previous approaches for verifying a user's physical control of devices to be paired may include, for instance, the user entering a PIN on the display of one or both of the devices, or the user scanning a QR code displayed on one of the devices with a camera of the other device. Such approaches, however, may not provide a uniform user experience, as they may be dependent on the specific features of the devices and/or the specific applications of the devices.
  • FIG. 1 illustrates an example of a system for physical contact detection for device pairing in accordance with an embodiment of the present disclosure.
  • FIG. 2 illustrates an example of a device for pairing with a wireless device in accordance with an embodiment of the present disclosure.
  • FIG. 3 illustrates an example of a method for physical contact detection for device pairing in accordance with an embodiment of the present disclosure.
  • an embodiment includes a mechanism configured to detect physical contact between the device and a wireless device, a memory, and a processor configured to execute executable instructions stored in the memory to perform a pairing of the wireless device and the device only upon the mechanism detecting the physical contact between the device and the wireless device.
  • Embodiments of the present disclosure can be used to reduce and/or eliminate security risks associated with device pairing, such as, for instance, unauthorized third party listening and/or hacking.
  • embodiments of the present disclosure can be used to verify that the pairing party (e.g., the person attempting to pair the devices) is in physical control (e.g., possession) of both devices (e.g., of both sides of the link being established between the devices).
  • embodiments of the present disclosure can provide a uniform user experience for the pairing party to verify that they are in physical control of both devices.
  • embodiments of the present disclosure may be capable verifying that the pairing party is in physical control of the devices to be paired independent of the specific features of the devices and the specific applications of the devices, such that the user's experience is a common one across different types of devices to be paired.
  • previous approaches for verifying the user's physical control of the devices to be paired e.g., entering a PIN or scanning a QR code
  • utilizing embodiments of the present disclosure to perform the physical control verification can make the device pairing process quicker, simpler, and/or easier for the user as compared to previous approaches.
  • a” or “a number of” something can refer to one or more such things, while “a plurality of” something can refer to more than one such things.
  • a number of devices can refer to one or more devices, while “a plurality of devices” can refer to more than one device.
  • the designator “N” as used herein, particularly with respect to reference numerals in the drawings, indicates that a number of the particular feature so designated can be included with embodiments of the present disclosure.
  • FIG. 1 illustrates an example of a system 100 for physical contact detection for device pairing in accordance with an embodiment of the present disclosure.
  • system 100 includes a number of wireless devices 102 - 1 , 102 - 2 , . . . , 102 -N and a device 104 .
  • wireless devices 102 - 1 , 102 - 2 , . . . , 102 -N are being paired with device 104 .
  • device pairing may include and/or refer to the process of establishing an initial link between devices that allows for communications between the devices to occur (e.g. over which the devices may communicate).
  • pairing wireless device 102 - 1 with device 104 may include establishing wireless link 108 - 1 with device 104
  • pairing wireless device 102 - 2 with device 104 may include establishing a wireless link 108 - 2 with device 104
  • pairing wireless device 102 -N with device 104 may include establishing wireless link 108 -N with device 104 .
  • the devices may be paired, for example, during installation and/or setup of device 104 and/or wireless devices 102 - 1 , 102 - 2 , . . . , 102 -N.
  • Wireless links 108 - 1 , 108 - 2 , . . . , 108 -N can comprise a wireless communication protocol such as, for example, IEEE 802.15.1 (e.g., Bluetooth), IEEE 802.15.4 (e.g., ZigBee), IEEE 802.3, IEEE 802.11 (e.g., WiFi), Redlink, or Bluetooth low energy wireless communication protocol, among others.
  • wireless links 108 - 1 , 108 - 2 , . . . , 108 -N can provide a virtual near-field communication (NFC) link between wireless devices 102 - 1 , 102 - 2 , . . . , 102 -N and device 104 .
  • NFC virtual near-field communication
  • embodiments of the present disclosure are not limited to a particular type(s) of wireless communication protocol.
  • Device 104 can be, for example, an energy management device.
  • device 104 can be a home energy management device that can be used to manage and/or control the energy consumption of a home.
  • device 104 can be a thermostat (e.g., a home thermostat) that can control (e.g. adjust) the operation of the furnace, air conditioner, and/or other energy loads (e.g., other energy consuming devices, systems, appliances, and/or mechanisms) of the home.
  • a thermostat e.g., a home thermostat
  • other energy loads e.g., other energy consuming devices, systems, appliances, and/or mechanisms
  • Device 104 will be further described herein (e.g., in connection with FIG. 2 ).
  • device 104 can include a mechanism to detect physical contact between device 104 and wireless devices 102 - 1 , 102 - 2 , . . . , 102 -N, and an interface to communicate with wireless devices 102 - 1 , 102 - 2 , . . . , 102 -N while being paired with wireless devices 102 - 1 , 102 - 2 , . . . , 102 -N, as will be further described herein.
  • Wireless devices 102 - 1 , 102 - 2 , . . . , 102 -N can include (e.g., be), for example, mobile devices, such as mobile (e.g., smart) phones and/or tablets.
  • mobile devices 102 - 1 , 102 - 2 , . . . , 102 -N can be a mobile device(s) of user 106 .
  • User 106 can be, for instance, an occupant of the home.
  • Wireless devices 102 - 1 , 102 - 2 , . . . , 102 -N can also include, for example, sensors, such as temperature sensors, lighting sensors, and/or humidity sensors.
  • one or more of wireless devices 102 - 1 , 102 - 2 , . . . , 102 -N can be sensors located inside and/or outside of the home.
  • Device 104 can include a mechanism to detect physical contact between device 104 and wireless devices 102 - 1 , 102 - 2 , . . . , 102 -N. For example, during a pairing of (e.g., an attempt to pair) a wireless device 102 - 1 , 102 - 2 , . . . , 102 -N with device 104 , the mechanism can detect physical contact between device 104 and the wireless device. Examples of the mechanism will be further described herein (e.g. in connection with FIG. 2 ).
  • the physical contact between device 104 and the wireless device can include, for instance, a tap of device 104 with the wireless device by user 106 .
  • device 104 e.g., the mechanism of device 104
  • device 104 can determine (e.g., verify) that user 106 is in physical control (e.g., possession) of both device 104 and the wireless device during the pairing, and determine whether to perform the device pairing based on this determination. For example, device 104 may perform the paring of the wireless device and device 104 only upon detecting the physical contact between the devices (e.g., only upon determining user 106 is in physical control of both devices); device 104 may prevent the pairing of the wireless device and device 104 in the absence of detecting physical contact between the devices (e.g., upon determining user 106 is not in physical control of both devices).
  • wireless devices 102 - 1 , 102 - 2 , . . . , 102 -N may also include a mechanism (e.g., an accelerometer or shock detector) to detect the physical contact between the wireless device and device 104 .
  • the wireless device may detect the physical contact at the same time as device 104 .
  • device 104 may perform the paring of the wireless device and device 104 only upon the wireless device and device 104 simultaneously detecting the physical contact between the devices. That is, in such embodiments, the verification that user 106 is in physical control of both devices can be determined (e.g., proven) by the aligned timing of the physical contact detection by both devices.
  • communications may occur between the devices.
  • device 104 is a home energy management device (e.g., thermostat) and the wireless device is a mobile (e.g., smart) phone of user 106
  • user 106 can send instructions for controlling the home energy management device (e.g., instructions to adjust the settings of the thermostat) to the device via the mobile phone.
  • the home energy management device e.g., instructions to adjust the settings of the thermostat
  • the subsequent communications that may occur between the devices after the devices have been paired can occur via a wired or wireless network (not shown in FIG. 1 for clarity and so as not to obscure embodiments of the present disclosure).
  • the network can be a network relationship through which device 104 and wireless devices 102 - 1 , 102 - 2 , . . . , 102 -N communicate.
  • Examples of such a network relationship can include a distributed computing environment (e.g., a cloud computing environment), a wide area network (WAN) such as the Internet, a local area network (LAN), a personal area network (PAN), a campus area network (CAN), or metropolitan area network (MAN), among other types of network relationships.
  • WAN wide area network
  • LAN local area network
  • PAN personal area network
  • CAN campus area network
  • MAN metropolitan area network
  • a “network” can provide a communication system that directly or indirectly links two or more computers and/or peripheral devices and allows users to access resources on other computing devices and exchange messages with other users.
  • a network can allow users to share resources on their own systems with other network users and to access information on centrally located systems or on systems that are located at remote locations.
  • a network can tie a number of computing devices together to form a distributed control network (e.g., cloud).
  • a network may provide connections to the Internet and/or to the networks of other entities (e.g., organizations, institutions, etc.). Users may interact with network-enabled software applications to make a network request, such as to get a file or print on a network printer. Applications may also communicate with network management software, which can interact with network hardware to transmit information between devices on the network.
  • entities e.g., organizations, institutions, etc.
  • network management software can interact with network hardware to transmit information between devices on the network.
  • device 104 may also detect subsequent movement of device 104 after it has been paired with the wireless device (e.g., after the pairing of the devices has been performed). Detection of such subsequent movement of device 104 can, for instance, provide an indication that device 104 has been tampered with and/or moved after it has been installed.
  • FIG. 2 illustrates an example of a device 204 for pairing with a wireless device in accordance with an embodiment of the present disclosure.
  • Device 204 can be, for example, device 104 previously described in connection with FIG. 1 .
  • device 204 can include a memory 212 , a processor 214 , a mechanism 216 , and an interface 218 .
  • Mechanism 216 can be used by device 204 to detect physical contact between device 204 and a wireless device (e.g., wireless devices 102 - 1 , 102 - 2 , . . . , 102 -N previously described in connection with FIG. 1 ) during a pairing of device 204 with the wireless device, as previously described herein.
  • Mechanism 216 can be, for example, an accelerometer or a shock detector included within device 204 .
  • embodiments of the present disclosure are not so limited, and can include any type of mechanism capable of detecting physical contact between device 204 and a wireless device.
  • Interface 218 can be used by device 204 to communicate with a wireless device (e.g., wireless devices 102 - 1 , 102 - 2 , . . . , 102 -N previously described in connection with FIG. 1 ) during a pairing of device 204 with the wireless device, as previously described herein.
  • a wireless device e.g., wireless devices 102 - 1 , 102 - 2 , . . . , 102 -N previously described in connection with FIG. 1
  • a wireless link e.g. wireless links 108 - 1 , 108 - 2 , . . . , 108 -N previously described in connection with FIG. 1
  • a wireless link e.g. wireless links 108 - 1 , 108 - 2 , . . . , 108 -N previously described in connection with FIG. 1
  • Memory 212 can be any type of storage medium that can be accessed by processor 214 to perform various examples of the present disclosure.
  • memory 212 can be a non-transitory computer readable medium having computer readable instructions (e.g., computer program instructions) stored thereon that are executable by processor 214 to pair device 204 with a wireless device in accordance with the present disclosure. That is, processor 214 can execute the executable instructions stored in memory 212 to pair device 204 with a wireless device in accordance with the present disclosure.
  • Memory 212 can be volatile or nonvolatile memory. Memory 212 can also be removable (e.g., portable) memory, or non-removable (e.g., internal) memory.
  • memory 212 can be random access memory (RAM) (e.g., dynamic random access memory (DRAM), resistive random access memory (RRAM), and/or phase change random access memory (PCRAM)), read-only memory (ROM) (e.g., electrically erasable programmable read-only memory (EEPROM) and/or compact-disk read-only memory (CD-ROM)), flash memory, a laser disk, a digital versatile disk (DVD) or other optical disk storage, and/or a magnetic medium such as magnetic cassettes, tapes, or disks, among other types of memory.
  • RAM random access memory
  • DRAM dynamic random access memory
  • RRAM resistive random access memory
  • PCRAM phase change random access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • memory 212 is illustrated as being located in device 204 , embodiments of the present disclosure are not so limited.
  • memory 212 can also be located internal to another computing resource (e.g., enabling computer readable instructions to be downloaded over the Internet or another wired or wireless connection).
  • FIG. 3 illustrates an example of a method 330 for physical contact detection for device pairing in accordance with an embodiment of the present disclosure.
  • Method 330 can be performed by, for example, device 104 and/or device 204 previously described in connection with FIGS. 1 and 2 , respectively.
  • method 330 includes initiating a pairing of a device and a wireless device.
  • the device can be, for example, device 104 and/or device 204 previously described in connection with FIGS. 1 and 2 , respectively, and the wireless device can be, for example, a wireless device 102 - 1 , 102 - 2 , . . . , 102 -N previously described in connection with FIG. 1 .
  • method 330 includes determining whether a user is in physical control (e.g., possession) of both the device and the wireless device. This determination can be made, for example, based on whether physical contact is detected between the device and the wireless device is detected, as previously described herein.
  • the pairing of the device and wireless device is prevented at block 336 . If it is determined the user is in physical control of both the device and the wireless device, the pairing of the device and the wireless device is performed at block 338 .
  • method 330 includes determining whether there are any additional wireless devices to pair with the device at block 340 . If there are no additional wireless devices to pair, method 330 ends at block 342 . If there is an additional wireless device to pair, method 330 returns to block 332 .

Abstract

Devices, methods, and systems for physical contact detection for device pairing are described herein. One device includes a mechanism configured to detect physical contact between the device and a wireless device, a memory, and a processor configured to execute executable instructions stored in the memory to perform a pairing of the wireless device and the device only upon the mechanism detecting the physical contact between the device and the wireless device.

Description

    TECHNICAL FIELD
  • The present disclosure relates generally to devices, methods, and systems for physical contact detection for device pairing.
  • BACKGROUND
  • Pairing may refer to and/or include a process used in computer networking to establish an initial link between computing devices that allows for communications between the devices to occur. As an example, in a home energy management system, a mobile (e.g., smart) phone of the home's occupant may be paired with the central thermostat of the home to allow the home's occupant to control the thermostat (e.g., the settings of the thermostat) via the mobile phone.
  • Such a pairing of computing devices, however, may present increased security risks for the devices, such as, for instance, unauthorized third party listening and/or hacking. These security risks can be reduced and/or eliminated by verifying that the pairing party (e.g., the person attempting to pair the devices) is in physical control (e.g., possession) of both devices (e.g., of both sides of the link).
  • Previous approaches for verifying a user's physical control of devices to be paired may include, for instance, the user entering a PIN on the display of one or both of the devices, or the user scanning a QR code displayed on one of the devices with a camera of the other device. Such approaches, however, may not provide a uniform user experience, as they may be dependent on the specific features of the devices and/or the specific applications of the devices.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 illustrates an example of a system for physical contact detection for device pairing in accordance with an embodiment of the present disclosure.
  • FIG. 2 illustrates an example of a device for pairing with a wireless device in accordance with an embodiment of the present disclosure.
  • FIG. 3 illustrates an example of a method for physical contact detection for device pairing in accordance with an embodiment of the present disclosure.
  • DETAILED DESCRIPTION
  • Devices, methods, and systems for physical contact detection for device pairing are described herein. For example, an embodiment includes a mechanism configured to detect physical contact between the device and a wireless device, a memory, and a processor configured to execute executable instructions stored in the memory to perform a pairing of the wireless device and the device only upon the mechanism detecting the physical contact between the device and the wireless device.
  • Embodiments of the present disclosure can be used to reduce and/or eliminate security risks associated with device pairing, such as, for instance, unauthorized third party listening and/or hacking. For example, embodiments of the present disclosure can be used to verify that the pairing party (e.g., the person attempting to pair the devices) is in physical control (e.g., possession) of both devices (e.g., of both sides of the link being established between the devices).
  • Further, embodiments of the present disclosure can provide a uniform user experience for the pairing party to verify that they are in physical control of both devices. For instance, embodiments of the present disclosure may be capable verifying that the pairing party is in physical control of the devices to be paired independent of the specific features of the devices and the specific applications of the devices, such that the user's experience is a common one across different types of devices to be paired. In contrast, previous approaches for verifying the user's physical control of the devices to be paired (e.g., entering a PIN or scanning a QR code) may not provide a uniform user experience, as they may be dependent on the specific features of the devices and/or the specific applications of the devices, and therefore may vary across different types of devices. As such, utilizing embodiments of the present disclosure to perform the physical control verification can make the device pairing process quicker, simpler, and/or easier for the user as compared to previous approaches.
  • In the following detailed description, reference is made to the accompanying drawings that form a part hereof. The drawings show by way of illustration how one or more embodiments of the disclosure may be practiced.
  • These embodiments are described in sufficient detail to enable those of ordinary skill in the art to practice one or more embodiments of this disclosure. It is to be understood that other embodiments may be utilized and that mechanical, electrical, and/or process changes may be made without departing from the scope of the present disclosure.
  • As will be appreciated, elements shown in the various embodiments herein can be added, exchanged, combined, and/or eliminated so as to provide a number of additional embodiments of the present disclosure. The proportion and the relative scale of the elements provided in the figures are intended to illustrate the embodiments of the present disclosure, and should not be taken in a limiting sense.
  • The figures herein follow a numbering convention in which the first digit or digits correspond to the drawing figure number and the remaining digits identify an element or component in the drawing. Similar elements or components between different figures may be identified by the use of similar digits. For example, 104 may reference element “04” in FIG. 1, and a similar element may be referenced as 204 in FIG. 2.
  • As used herein, “a” or “a number of” something can refer to one or more such things, while “a plurality of” something can refer to more than one such things. For example, “a number of devices” can refer to one or more devices, while “a plurality of devices” can refer to more than one device. Additionally, the designator “N” as used herein, particularly with respect to reference numerals in the drawings, indicates that a number of the particular feature so designated can be included with embodiments of the present disclosure.
  • FIG. 1 illustrates an example of a system 100 for physical contact detection for device pairing in accordance with an embodiment of the present disclosure. In the example illustrated in FIG. 1, system 100 includes a number of wireless devices 102-1, 102-2, . . . , 102-N and a device 104. For instance, in the example illustrated in FIG. 1, wireless devices 102-1, 102-2, . . . , 102-N are being paired with device 104.
  • As used herein, device pairing may include and/or refer to the process of establishing an initial link between devices that allows for communications between the devices to occur (e.g. over which the devices may communicate). For instance, in the example illustrated in FIG. 1, pairing wireless device 102-1 with device 104 may include establishing wireless link 108-1 with device 104, pairing wireless device 102-2 with device 104 may include establishing a wireless link 108-2 with device 104, and pairing wireless device 102-N with device 104 may include establishing wireless link 108-N with device 104. The devices may be paired, for example, during installation and/or setup of device 104 and/or wireless devices 102-1, 102-2, . . . , 102-N.
  • Wireless links 108-1, 108-2, . . . , 108-N can comprise a wireless communication protocol such as, for example, IEEE 802.15.1 (e.g., Bluetooth), IEEE 802.15.4 (e.g., ZigBee), IEEE 802.3, IEEE 802.11 (e.g., WiFi), Redlink, or Bluetooth low energy wireless communication protocol, among others. For instance, wireless links 108-1, 108-2, . . . , 108-N can provide a virtual near-field communication (NFC) link between wireless devices 102-1, 102-2, . . . , 102-N and device 104. However, embodiments of the present disclosure are not limited to a particular type(s) of wireless communication protocol.
  • Device 104 can be, for example, an energy management device. For instance, device 104 can be a home energy management device that can be used to manage and/or control the energy consumption of a home. As an example, device 104 can be a thermostat (e.g., a home thermostat) that can control (e.g. adjust) the operation of the furnace, air conditioner, and/or other energy loads (e.g., other energy consuming devices, systems, appliances, and/or mechanisms) of the home.
  • Device 104 will be further described herein (e.g., in connection with FIG. 2). For instance, device 104 can include a mechanism to detect physical contact between device 104 and wireless devices 102-1, 102-2, . . . , 102-N, and an interface to communicate with wireless devices 102-1, 102-2, . . . , 102-N while being paired with wireless devices 102-1, 102-2, . . . , 102-N, as will be further described herein.
  • Wireless devices 102-1, 102-2, . . . , 102-N can include (e.g., be), for example, mobile devices, such as mobile (e.g., smart) phones and/or tablets. For instance, one or more of wireless devices 102-1, 102-2, . . . , 102-N can be a mobile device(s) of user 106. User 106 can be, for instance, an occupant of the home. Wireless devices 102-1, 102-2, . . . , 102-N can also include, for example, sensors, such as temperature sensors, lighting sensors, and/or humidity sensors. For instance, one or more of wireless devices 102-1, 102-2, . . . , 102-N can be sensors located inside and/or outside of the home.
  • Device 104 can include a mechanism to detect physical contact between device 104 and wireless devices 102-1, 102-2, . . . , 102-N. For example, during a pairing of (e.g., an attempt to pair) a wireless device 102-1, 102-2, . . . , 102-N with device 104, the mechanism can detect physical contact between device 104 and the wireless device. Examples of the mechanism will be further described herein (e.g. in connection with FIG. 2).
  • The physical contact between device 104 and the wireless device can include, for instance, a tap of device 104 with the wireless device by user 106. Further, device 104 (e.g., the mechanism of device 104) can detect the physical contact while device 104 is stationary or while device 104 is in motion (e.g., the physical contact between device 104 and the wireless device may occur while device 104 is not moving, or while both device 104 and the wireless device are moving).
  • By detecting the physical contact between device 104 and the wireless device, device 104 can determine (e.g., verify) that user 106 is in physical control (e.g., possession) of both device 104 and the wireless device during the pairing, and determine whether to perform the device pairing based on this determination. For example, device 104 may perform the paring of the wireless device and device 104 only upon detecting the physical contact between the devices (e.g., only upon determining user 106 is in physical control of both devices); device 104 may prevent the pairing of the wireless device and device 104 in the absence of detecting physical contact between the devices (e.g., upon determining user 106 is not in physical control of both devices).
  • In some embodiments, wireless devices 102-1, 102-2, . . . , 102-N may also include a mechanism (e.g., an accelerometer or shock detector) to detect the physical contact between the wireless device and device 104. For instance, the wireless device may detect the physical contact at the same time as device 104. In such embodiments, device 104 may perform the paring of the wireless device and device 104 only upon the wireless device and device 104 simultaneously detecting the physical contact between the devices. That is, in such embodiments, the verification that user 106 is in physical control of both devices can be determined (e.g., proven) by the aligned timing of the physical contact detection by both devices.
  • After the devices have been paired (e.g. after the physical contact between the wireless device and device 104 has been detected and the pairing of the devices has been performed), communications may occur between the devices. For example, in embodiments in which device 104 is a home energy management device (e.g., thermostat) and the wireless device is a mobile (e.g., smart) phone of user 106, user 106 can send instructions for controlling the home energy management device (e.g., instructions to adjust the settings of the thermostat) to the device via the mobile phone. However, embodiments of the present disclosure are not limited to this example.
  • The subsequent communications that may occur between the devices after the devices have been paired can occur via a wired or wireless network (not shown in FIG. 1 for clarity and so as not to obscure embodiments of the present disclosure). For example, the network can be a network relationship through which device 104 and wireless devices 102-1, 102-2, . . . , 102-N communicate. Examples of such a network relationship can include a distributed computing environment (e.g., a cloud computing environment), a wide area network (WAN) such as the Internet, a local area network (LAN), a personal area network (PAN), a campus area network (CAN), or metropolitan area network (MAN), among other types of network relationships.
  • As used herein, a “network” can provide a communication system that directly or indirectly links two or more computers and/or peripheral devices and allows users to access resources on other computing devices and exchange messages with other users. A network can allow users to share resources on their own systems with other network users and to access information on centrally located systems or on systems that are located at remote locations. For example, a network can tie a number of computing devices together to form a distributed control network (e.g., cloud).
  • A network may provide connections to the Internet and/or to the networks of other entities (e.g., organizations, institutions, etc.). Users may interact with network-enabled software applications to make a network request, such as to get a file or print on a network printer. Applications may also communicate with network management software, which can interact with network hardware to transmit information between devices on the network.
  • In some embodiments, device 104 (e.g., the mechanism of device 104) may also detect subsequent movement of device 104 after it has been paired with the wireless device (e.g., after the pairing of the devices has been performed). Detection of such subsequent movement of device 104 can, for instance, provide an indication that device 104 has been tampered with and/or moved after it has been installed.
  • FIG. 2 illustrates an example of a device 204 for pairing with a wireless device in accordance with an embodiment of the present disclosure. Device 204 can be, for example, device 104 previously described in connection with FIG. 1. As shown in FIG. 2, device 204 can include a memory 212, a processor 214, a mechanism 216, and an interface 218.
  • Mechanism 216 can be used by device 204 to detect physical contact between device 204 and a wireless device (e.g., wireless devices 102-1, 102-2, . . . , 102-N previously described in connection with FIG. 1) during a pairing of device 204 with the wireless device, as previously described herein. Mechanism 216 can be, for example, an accelerometer or a shock detector included within device 204. However, embodiments of the present disclosure are not so limited, and can include any type of mechanism capable of detecting physical contact between device 204 and a wireless device.
  • Interface 218 can be used by device 204 to communicate with a wireless device (e.g., wireless devices 102-1, 102-2, . . . , 102-N previously described in connection with FIG. 1) during a pairing of device 204 with the wireless device, as previously described herein. For example, interface 218 may be associated with (e.g., used to establish) a wireless link (e.g. wireless links 108-1, 108-2, . . . , 108-N previously described in connection with FIG. 1) comprising a wireless communication protocol for communicating with the wireless device during the device pairing, as previously described herein.
  • Memory 212 can be any type of storage medium that can be accessed by processor 214 to perform various examples of the present disclosure. For example, memory 212 can be a non-transitory computer readable medium having computer readable instructions (e.g., computer program instructions) stored thereon that are executable by processor 214 to pair device 204 with a wireless device in accordance with the present disclosure. That is, processor 214 can execute the executable instructions stored in memory 212 to pair device 204 with a wireless device in accordance with the present disclosure.
  • Memory 212 can be volatile or nonvolatile memory. Memory 212 can also be removable (e.g., portable) memory, or non-removable (e.g., internal) memory. For example, memory 212 can be random access memory (RAM) (e.g., dynamic random access memory (DRAM), resistive random access memory (RRAM), and/or phase change random access memory (PCRAM)), read-only memory (ROM) (e.g., electrically erasable programmable read-only memory (EEPROM) and/or compact-disk read-only memory (CD-ROM)), flash memory, a laser disk, a digital versatile disk (DVD) or other optical disk storage, and/or a magnetic medium such as magnetic cassettes, tapes, or disks, among other types of memory.
  • Further, although memory 212 is illustrated as being located in device 204, embodiments of the present disclosure are not so limited. For example, memory 212 can also be located internal to another computing resource (e.g., enabling computer readable instructions to be downloaded over the Internet or another wired or wireless connection).
  • FIG. 3 illustrates an example of a method 330 for physical contact detection for device pairing in accordance with an embodiment of the present disclosure. Method 330 can be performed by, for example, device 104 and/or device 204 previously described in connection with FIGS. 1 and 2, respectively.
  • At block 332, method 330 includes initiating a pairing of a device and a wireless device. The device can be, for example, device 104 and/or device 204 previously described in connection with FIGS. 1 and 2, respectively, and the wireless device can be, for example, a wireless device 102-1, 102-2, . . . , 102-N previously described in connection with FIG. 1.
  • At block 334, method 330 includes determining whether a user is in physical control (e.g., possession) of both the device and the wireless device. This determination can be made, for example, based on whether physical contact is detected between the device and the wireless device is detected, as previously described herein.
  • If it is determined the user is not in physical control of both the device and the wireless device, the pairing of the device and wireless device is prevented at block 336. If it is determined the user is in physical control of both the device and the wireless device, the pairing of the device and the wireless device is performed at block 338.
  • After the device and the wireless device have been paired, method 330 includes determining whether there are any additional wireless devices to pair with the device at block 340. If there are no additional wireless devices to pair, method 330 ends at block 342. If there is an additional wireless device to pair, method 330 returns to block 332.
  • Although specific embodiments have been illustrated and described herein, those of ordinary skill in the art will appreciate that any arrangement calculated to achieve the same techniques can be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments of the disclosure.
  • It is to be understood that the above description has been made in an illustrative fashion, and not a restrictive one. Combination of the above embodiments, and other embodiments not specifically described herein will be apparent to those of skill in the art upon reviewing the above description.
  • The scope of the various embodiments of the disclosure includes any other applications in which the above structures and methods are used. Therefore, the scope of various embodiments of the disclosure should be determined with reference to the appended claims, along with the full range of equivalents to which such claims are entitled.
  • In the foregoing Detailed Description, various features are grouped together in example embodiments illustrated in the figures for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the embodiments of the disclosure 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 separate embodiment.

Claims (20)

1. A device, comprising:
a mechanism configured to detect physical contact between the device and a wireless device, wherein the physical contact includes a tap of the device with the wireless device;
a memory; and
a processor configured to execute executable instructions stored in the memory to perform a pairing of the wireless device and the device only upon the mechanism detecting the physical contact between the device and the wireless device.
2. The device of claim 1, wherein the device includes an interface configured to communicate with the wireless device during the pairing of the wireless device and the device.
3. The device of claim 2, wherein the interface is a wireless link that uses a wireless communication protocol to communicate with the wireless device during the pairing of the wireless device and the device.
4. The device of claim 1, wherein the mechanism is an accelerometer.
5. The device of claim 1, wherein the mechanism is a shock detector.
6. The device of claim 1, wherein the mechanism is configured to detect movement of the device after the wireless device and the device have been paired.
7. The device of claim 1, wherein the processor is configured to execute the instructions to perform the pairing of the wireless device and the device by establishing a link between the wireless device and the device over which the wireless device and device communicate.
8. A method of operating a device, comprising:
determining, by a device, whether a user of the device is in physical control of both the device and a wireless device during a pairing of the wireless device and the device based only upon whether physical contact is detected between the device and the wireless device, wherein the physical contact includes a tap of the device with the wireless device;
performing, by the device, the pairing of the wireless device and the device only upon determining the user of the device is in physical control of both the device and the wireless device; and
preventing, by the device, the pairing of the wireless device and the device upon determining the user of the device is not in physical control of both the device and the wireless device.
9. (canceled)
10. (canceled)
11. The method of claim 8, wherein the method includes determining whether the user of the device is in physical control of both the device and the wireless device based on whether the physical contact between the device and the wireless device is detected simultaneously by the device and the wireless device.
12. The method of claim 8, wherein the method includes determining whether the user of the device is in physical control of both the device and the wireless device using an accelerometer of the device.
13. The method of claim 8, wherein the method includes determining whether the user of the device is in physical control of both the device and the wireless device using a shock detector of the device.
14. A system, comprising:
a wireless device; and
a device configured to:
communicate with the wireless device during a pairing of the wireless device and the device;
detect physical contact between the device and the wireless device, wherein the physical contact includes a tap of the device with the wireless device; and
perform the pairing of the wireless device and the device only upon detecting the physical contact between the device and the wireless device.
15. The system of claim 14, wherein:
the device is an energy management device; and
the wireless device is a mobile phone.
16. The system of claim 14, wherein:
the device is an energy management device; and
the wireless device is a sensor.
17. (canceled)
18. The system of claim 14, wherein:
the wireless device is configured to detect the physical contact between the device and the wireless device; and
the device is configured to perform the pairing of the wireless device and the device only upon the device and the wireless device simultaneously detecting the physical contact between the device and the wireless device.
19. The system of claim 14, wherein the device is configured to detect the physical contact between the device and the wireless device while the device is stationary.
20. The system of claim 14, wherein the device is configured to detect the physical contact between the device and the wireless device while both the device and the wireless device are in motion.
US15/978,991 2018-05-14 2018-05-14 Physical contact detection for device pairing Abandoned US20190350021A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/978,991 US20190350021A1 (en) 2018-05-14 2018-05-14 Physical contact detection for device pairing
US17/117,591 US11706827B2 (en) 2018-05-14 2020-12-10 Physical contact detection for device pairing

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US15/978,991 US20190350021A1 (en) 2018-05-14 2018-05-14 Physical contact detection for device pairing

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/117,591 Continuation US11706827B2 (en) 2018-05-14 2020-12-10 Physical contact detection for device pairing

Publications (1)

Publication Number Publication Date
US20190350021A1 true US20190350021A1 (en) 2019-11-14

Family

ID=68464448

Family Applications (2)

Application Number Title Priority Date Filing Date
US15/978,991 Abandoned US20190350021A1 (en) 2018-05-14 2018-05-14 Physical contact detection for device pairing
US17/117,591 Active 2039-01-07 US11706827B2 (en) 2018-05-14 2020-12-10 Physical contact detection for device pairing

Family Applications After (1)

Application Number Title Priority Date Filing Date
US17/117,591 Active 2039-01-07 US11706827B2 (en) 2018-05-14 2020-12-10 Physical contact detection for device pairing

Country Status (1)

Country Link
US (2) US20190350021A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200396613A1 (en) * 2019-04-29 2020-12-17 Sonicwall Inc. Securing transmission paths in a mesh network
US11638149B2 (en) 2019-04-29 2023-04-25 Sonicwall Inc. Instant secure wireless network setup

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11711860B2 (en) * 2021-06-06 2023-07-25 Kyndryl, Inc. Device pairing by cognitive computing

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170091412A1 (en) * 2014-05-30 2017-03-30 Apple Inc. Systems and Methods for Facilitating Health Research Using a Personal Wearable Device With Multiple Pairing Configurations
US20180054509A1 (en) * 2016-08-22 2018-02-22 Adobe Systems Incorporated Touch and device orientation-based device pairing
US20180132287A1 (en) * 2016-11-04 2018-05-10 Htc Corporation Method, electronic apparatus and recording medium for establishing wireless connection through vibration
US20190261166A1 (en) * 2018-02-19 2019-08-22 Ingenico Inc Method for pairing electronic terminals, corresponding pairing devices, terminals and program

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9942661B2 (en) 2013-05-14 2018-04-10 Logitech Europe S.A Method and apparatus for controlling portable audio devices
US9593861B1 (en) * 2014-02-13 2017-03-14 Dust Free, Lp Controlling and monitoring indoor air quality (IAQ) devices

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170091412A1 (en) * 2014-05-30 2017-03-30 Apple Inc. Systems and Methods for Facilitating Health Research Using a Personal Wearable Device With Multiple Pairing Configurations
US20180054509A1 (en) * 2016-08-22 2018-02-22 Adobe Systems Incorporated Touch and device orientation-based device pairing
US20180132287A1 (en) * 2016-11-04 2018-05-10 Htc Corporation Method, electronic apparatus and recording medium for establishing wireless connection through vibration
US20190261166A1 (en) * 2018-02-19 2019-08-22 Ingenico Inc Method for pairing electronic terminals, corresponding pairing devices, terminals and program

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200396613A1 (en) * 2019-04-29 2020-12-17 Sonicwall Inc. Securing transmission paths in a mesh network
US11638149B2 (en) 2019-04-29 2023-04-25 Sonicwall Inc. Instant secure wireless network setup

Also Published As

Publication number Publication date
US11706827B2 (en) 2023-07-18
US20210092784A1 (en) 2021-03-25

Similar Documents

Publication Publication Date Title
US11706827B2 (en) Physical contact detection for device pairing
US10854029B2 (en) Decentralized virtual trustless database for access control
US10097529B2 (en) Semiconductor device for controlling access right to server of internet of things device and method of operating the same
US9967366B2 (en) Internet of things (IoT) API platform
US9674879B2 (en) Provisioning of electronic devices
US10135805B2 (en) Connected authentication device using mobile single sign on credentials
US10509476B2 (en) Enhanced device authentication using magnetic declination
US20160337322A1 (en) Semiconductor device for managing user data according to security level and method of operating the same
US10713657B2 (en) Systems and methods for estimating authenticity of local network of device initiating remote transaction
WO2016184380A1 (en) Processing method and device for network access
US20200001822A1 (en) Method and apparatus for authenticating vehicle smart key
US20170134393A1 (en) Method, apparatus, and recording medium for sharing use authority with respect to service
US11025595B2 (en) Secure and anonymous data sharing
US20220408263A1 (en) Access control system and method
EP3497950B1 (en) Presence identification
CN112446985A (en) Intelligent door lock unlocking method and device
US11363017B2 (en) Smart home network security through blockchain
Khan et al. chownIoT: enhancing IoT privacy by automated handling of ownership change
GB2590357A (en) Access control system and method
GB2590607A (en) Access control system and method
WO2018014555A1 (en) Data transmission control method and apparatus
Nadargi et al. Addressing identity and location privacy of things for indoor—Case study on Internet of Everything’s (IoE)
KR20130005635A (en) System for providing secure card payment system using mobile terminal and method thereof
US20210150837A1 (en) Decentralized virtual trustless database for access control
GB2590355A (en) Access control system and method

Legal Events

Date Code Title Description
AS Assignment

Owner name: HONEYWELL INTERNATIONAL INC., NEW JERSEY

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BLUM, WILLIAM R.;REEL/FRAME:045797/0793

Effective date: 20180514

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION