WO2016085214A1 - Method and apparatus for pairing a wearable device and a smart device - Google Patents

Method and apparatus for pairing a wearable device and a smart device Download PDF

Info

Publication number
WO2016085214A1
WO2016085214A1 PCT/KR2015/012588 KR2015012588W WO2016085214A1 WO 2016085214 A1 WO2016085214 A1 WO 2016085214A1 KR 2015012588 W KR2015012588 W KR 2015012588W WO 2016085214 A1 WO2016085214 A1 WO 2016085214A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
electronic device
wearable
smart
smart device
Prior art date
Application number
PCT/KR2015/012588
Other languages
English (en)
French (fr)
Inventor
Mangesh Abhimanyu INGALE
Vijaya Kumar Tukka
Jaehyuk Jang
Diwakar Sharma
Original Assignee
Samsung Electronics Co., Ltd.
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 Samsung Electronics Co., Ltd. filed Critical Samsung Electronics Co., Ltd.
Priority to EP15862185.4A priority Critical patent/EP3225073A4/en
Publication of WO2016085214A1 publication Critical patent/WO2016085214A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/38—Services specially adapted for particular environments, situations or purposes for collecting sensor information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2807—Exchanging configuration information on appliance services in a home automation network
    • H04L12/2809—Exchanging configuration information on appliance services in a home automation network indicating that an appliance service is present in a home automation network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/30—Security of mobile devices; Security of mobile applications
    • H04W12/33—Security of mobile devices; Security of mobile applications using wearable devices, e.g. using a smartwatch or smart-glasses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/50—Secure pairing of devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • H04W4/21—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel for social networking applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/63—Location-dependent; Proximity-dependent

Definitions

  • the present disclosure relates to Internet of things (IoT) related applications and use case scenarios. More particularly, the present disclosure relates to automatic association/disassociation of an IoT device with another smart device based on user identification. Further, smart triggering of cellular radio for mobile initiated calls by the IoT device is envisaged based on trigger metric detection.
  • IoT Internet of things
  • the 5G or pre-5G communication system is also called a ‘Beyond 4G Network’ or a ‘Post LTE System’.
  • the 5G communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., 60GHz bands, so as to accomplish higher data rates.
  • mmWave e.g., 60GHz bands
  • MIMO massive multiple-input multiple-output
  • FD-MIMO Full Dimensional MIMO
  • array antenna an analog beam forming, large scale antenna techniques are discussed in 5G communication systems.
  • RANs Cloud Radio Access Networks
  • D2D device-to-device
  • CoMP Coordinated Multi-Points
  • FQAM Hybrid FSK and QAM Modulation
  • SWSC sliding window superposition coding
  • ACM advanced coding modulation
  • FBMC filter bank multi carrier
  • NOMA non-orthogonal multiple access
  • SCMA sparse code multiple access
  • the Internet which is a human centered connectivity network where humans generate and consume information
  • IoT Internet of Things
  • IoE Internet of Everything
  • sensing technology “wired/wireless communication and network infrastructure”, “service interface technology”, and “Security technology”
  • M2M Machine-to-Machine
  • MTC Machine Type Communication
  • IoT Internet technology services
  • IoT may be applied to a variety of fields including smart home, smart building, smart city, smart car or connected cars, smart grid, health care, smart appliances and advanced medical services through convergence and combination between existing Information Technology (IT) and various industrial applications.
  • IT Information Technology
  • 5G communication systems to IoT networks.
  • technologies such as a sensor network, Machine Type Communication (MTC), and Machine-to-Machine (M2M) communication may be implemented by beamforming, MIMO, and array antennas.
  • MTC Machine Type Communication
  • M2M Machine-to-Machine
  • Application of a cloud Radio Access Network (RAN) as the above-described Big Data processing technology may also be considered to be as an example of convergence between the 5G technology and the IoT technology.
  • RAN Radio Access Network
  • IoT Internet of things
  • wireless connectivity is expected to be native to devices which would connect directly to other devices in proximity (e.g., a Bluetooth connection, a Wi-Fi connection, a Zigbee connection etc.) or would connect to application servers with a cellular link (e.g., a second generation (2G) global system for mobile communications (GSM)/code division multiple access (CDMA) connection, a third generation (3G) universal mobile telecommunications system (UMTS) connection, a fourth generation (4G) long term evolution (LTE)/worldwide interoperability for microwave access (WiMAX) connection, etc.) or through a local hub (e.g., a hub having cellular radio capability or digital subscriber line (DSL) connectivity).
  • 2G second generation
  • GSM global system for mobile communications
  • CDMA code division multiple access
  • UMTS universal mobile telecommunications system
  • 4G long term evolution
  • LTE long term evolution
  • WiMAX wireless wide area network
  • DSL digital subscriber line
  • IoT technology is commercially available in many home appliances providing users the so called smart home experience. IoT is also referred as machine-to-machine (M2M) or machine type communication (MTC). IoT deployments are already picking up in metering applications for periodic reports about usage of electricity, water, gas, etc. to utility provider’s application servers. This automation is not only convenient to a utility provider for avoiding manual meter readings but also would help users to control utility bills and contribute towards energy conservation through smartphone applications communicating with smart meters.
  • M2M machine-to-machine
  • MTC machine type communication
  • IoT is also expected to take its position in the automobile industry where users would benefit from extending the smart home environment to the smart car environment, such that a user’s smart device connects to an electronic console/dashboard inside the automobile.
  • Smartphones and tablets are commonplace and technologies are extending towards wearable devices such as smart watches, health monitoring bands, smart glasses etc.
  • Wearable devices are equipped with widely available sensors that are currently in smartphones, such as accelerometers, gyroscopes, cameras, fingerprint scanners, etc., and in addition health monitoring sensors for heart rate, blood pressure etc.
  • Wearable devices are equipped with radios for proximity connectivity such Bluetooth, Wi-Fi, near field communication (NFC), Zigbee, etc., as well as cellular connectivity using 2G/3G/4G radios based on GSM, CDMA, UMTS, WiMAX and LTE.
  • radios for proximity connectivity such Bluetooth, Wi-Fi, near field communication (NFC), Zigbee, etc.
  • 2G/3G/4G radios based on GSM, CDMA, UMTS, WiMAX and LTE.
  • the IoT device referred above is not restricted to wearable devices like smart watches, but could also cover health bands, kid-care or childcare monitoring bands, eldercare bands, smart glasses, smart necklaces, electronic consoles/dashboards inside automobiles etc., including widely known IoT devices for metering, in smart homes for thermostat control and home appliances. Even though the present disclosure is illustrated in detail referring to wearable kind of IoT device, the scope of the present disclosure is equally applicable for various categories of IoT devices citing a few examples as mentioned above. The description of the present disclosure referring to the wearable IoT device should not be considered as limiting for the applicability of the present disclosure.
  • the existing manual/NFC based procedure for association/disassociation (pairing/un-pairing) of the IoT device with a smart device is not user friendly.
  • the existing manual/NFC based procedure for association/disassociation (pairing/un-pairing) of the IoT device with multiple smart devices is cumbersome and it needs to be manually tracked for multi-device connectivity of the same user.
  • the radio capability is disabled when an IoT device is in proximity of associated (paired) smart device.
  • a radio capability e.g., second generation (2G)/third generation (3G)/fourth generation (4G)
  • the radio capability is disabled when an IoT device is in proximity of associated (paired) smart device.
  • activating the radio capability of an IoT device is typically triggered based on losing the proximity connectivity with associated (paired) smart device. This is inadequate to address several use cases of an IoT device when applied to childcare monitoring and notification, eldercare alerts and tracking unauthorized usage of the IoT device which cannot be useful for theft detection and tracking.
  • an aspect of the present disclosure is to provide an automatic association/disassociation (pairing/un-pairing) procedure for an Internet of things (IoT) device (e.g., a wearable smart watch) to pair with a smart device (e.g., a smartphone) is proposed based on user identification.
  • IoT Internet of things
  • the procedure is made user friendly by creating an association context based on which pre-defined actions are taken by the IoT device.
  • Another aspect of the present disclosure is to provide a shared wearable (IoT) device.
  • the shared wearable (IoT) device associates with the smart device corresponding to the user using the wearable and in accordance to pre-defined or pre-configured association context.
  • the shared car console/dashboard e.g., the IoT device
  • the smart device e.g., a smartphone or a smart watch
  • the shared IoT device associates the private settings of user to activate the shared resources and upon detection of another user in proximity the private settings are de-activated and public settings are activated.
  • Another aspect of the present disclosure is to provide a wearable (IoT) device with a nearest smart device of the user based on displacement detection which triggers automatic association/disassociation procedure.
  • IoT wearable
  • Another aspect of the present disclosure is to provide triggers for turning a cellular radio ON or triggers for a mobile initiated notification when the wearable (IoT) device is not associated (paired) with a smart device or when in standby mode to address emergency situations notifying an incident.
  • IoT wearable
  • Another aspect of the present disclosure is to provide theft detection and tracking based on user identification and then disabling the automatic association/disassociation functionality in the wearable (IoT) device and notifying the owner by triggering cellular radio ON or triggering the mobile initiated notification.
  • IoT wearable
  • an electronic device in a wireless communication system includes one or more sensor units electrically coupled with a processor and configured to identify user identity metrics of a user, a radio frequency (RF) unit electrically coupled with the processor and configured to perform communication with another electronic device, and to pair with the other electronic device or un-pair from the other electronic device, a memory unit electrically coupled with the processor and configured to store association information, and the processor configured to control the one or more sensor units to identify the user identity metrics, to identify the user based on the association information and the user identity metrics, and to determine that the user is an authorized user based on a result of a comparison between the identified user identity metrics and the stored association information.
  • RF radio frequency
  • a method of an electronic device for communicating with another electronic device includes capturing user identity metrics of a user and determining, by a processor of the electronic device, that the user is an authorized user based on a result of a comparison between the identified user identity metrics and association information.
  • FIG. 1 illustrates manual association and disassociation (pairing and unpairing) between an Internet of things (IoT) device and a smart device according to an embodiment of the present disclosure
  • FIG. 2 illustrates a concept of an association context according to an embodiment of the present disclosure
  • FIG. 3 illustrates a procedure for automatic association (pairing) according to an embodiment of the present disclosure
  • FIG. 4 illustrates a shared device scenario between authorized users according to an embodiment of the present disclosure
  • FIG. 5 illustrates an automatic association procedure for a shared device scenario according to an embodiment of the present disclosure
  • FIG. 6 illustrates smart pairing to multiple devices in a smart home environment according to an embodiment of the present disclosure
  • FIG. 7 illustrates a procedure to connect to a nearest smart device in a home environment according to an embodiment of the present disclosure
  • FIG. 8 illustrates automatic triggering of a cellular radio communication capability of an IoT device according to an embodiment of the present disclosure
  • FIG. 9 illustrates a general procedure for sending an alert notification to an authorized user according to an embodiment of the present disclosure
  • FIG. 10 illustrates a specific procedure for sending an alert notification to an authorized user according to an embodiment of the present disclosure.
  • FIG. 11 is a block diagram of a wearable device according to an embodiment of the present disclosure.
  • An electronic device may be a device including a communication function.
  • the electronic device may include at least one of a smartphone, a tablet personal computer (PC), a mobile phone, a video phone, an electronic book (e-book) reader, a desktop PC, a laptop PC, a netbook computer, a personal digital assistant (PDA), a portable multimedia player (PMP), a motion picture experts group (MPEG) audio layer 3 (MP3) player, a mobile medical appliance, a camera, and a wearable device (e.g., a head-mounted-device (HMD), such as electronic glasses, electronic clothes, an electronic bracelet, an electronic necklace, an electronic appcessory, electronic tattoos, or a smartwatch).
  • HMD head-mounted-device
  • the electronic device may be a smart home appliance with a communication function.
  • the smart home appliance as the electronic device may include at least one of a television (TV), a digital versatile disc (DVD) player, an audio, a refrigerator, an air conditioner, a vacuum cleaner, an oven, a microwave oven, a washing machine, an air cleaner, a set-top box, a TV box (e.g., Samsung HOMESYNCTM, APPLE TVTM, or GOOGLE TVTM), a game console, an electronic dictionary, an electronic key, a camcorder, and an electronic photo frame.
  • TV television
  • DVD digital versatile disc
  • the electronic device may include at least one of various medical devices (e.g., magnetic resonance angiography (MRA), magnetic resonance imaging (MRI), computed tomography (CT), and ultrasonic machines), navigation equipment, a global positioning system (GPS) receiver, an event data recorder (EDR), a flight data recorder (FDR), an automotive infotainment device, electronic equipment for ships (e.g., ship navigation equipment and a gyrocompass), avionics equipment, security equipment, a vehicle head unit, an industrial or home robot, an automatic teller machine (ATM) of a banking system, and a point of sales (POS) in a shop.
  • various medical devices e.g., magnetic resonance angiography (MRA), magnetic resonance imaging (MRI), computed tomography (CT), and ultrasonic machines
  • GPS global positioning system
  • EDR event data recorder
  • FDR flight data recorder
  • automotive infotainment device e.g., avionics equipment, security equipment, a vehicle head
  • the electronic device may include at least one of a part of furniture or a building/structure, an electronic board, an electronic signature receiving device, a projector, and various kinds of measuring instruments (e.g., a water meter, an electric meter, a gas meter, and a radio wave meter).
  • various kinds of measuring instruments e.g., a water meter, an electric meter, a gas meter, and a radio wave meter.
  • the electronic device according to various embodiments of the present disclosure may be a combination of one or more of the aforementioned various devices. Further, the electronic device according to various embodiments of the present disclosure may be a flexible device. Further, the electronic device according to various embodiments of the present disclosure is not limited to the aforementioned devices.
  • the term “user” may refer to any person who uses an electronic device or any other device (e.g., an artificial intelligence electronic device) using an electronic device.
  • wearables e.g., Internet of things (IoT) devices
  • IoT Internet of things
  • NFC near field communication
  • the existing pairing/un-pairing is based on a manual procedure or an NFC enabled procedure, which is quite inconvenient in the context of a scenario where the wearable device will be shared by more than one user.
  • shared wearable means the owner or primary user of the wearable (device) would share the device with other authorized users. For example, in home it is possible that the wearable is shared between husband and wife (in this case husband may be the primary user and the wife is an authorized user with whom the wearable is shared) such that the manual association/disassociation needs to be done every time the concerned user is using the wearable and pairs with his/her corresponding smart device.
  • the shared wearable was paired with smart device of user #1, and user #1 removes the wearable but forgets to manually un-pair from his/her smart device.
  • the wearable is then used by user #2 (user #2 is also an authorized user) but the wearable still remains paired with the smart device of user #1 (provided it is in proximity of the shared wearable).
  • the shared usage scenario for automatic association/disassociation is not limited within the scope of wearable devices (e.g., a smart watch) and a smart device (e.g., a smartphone) in a home environment, but is also equally applicable in a smart car environment.
  • a smart car is normally shared by the family and passengers in the car, other than the one who is in driver seat, can fully enjoy the smart car environment in terms of connectivity, entertainment, music etc. (assuming the driver is not distracted with entertainment videos, but the driver can send verbal commands and receive audio notifications for messages or navigation through the car console/dashboard). So, the car’s console/dashboard will be shared by family members such that the corresponding smart device (smartphone or smart watch) of the concerned family member is associated with the car’s console/dashboard.
  • the car console/dashboard is the shared IoT device having proximity connectivity and/or cellular radio capability.
  • the console/dashboard receive notification of messages (e.g., short message service (SMS) and electronic mail (e-mail)) on the console/dashboard (notification messages may be converted to audio messages by the car’s console/dashboard) while he can still concentrate on the driving because there is no need for the driver to look at the console display.
  • SMS short message service
  • e-mail electronic mail
  • the environment inside the car is automatically set according to his choice and taste like the music directory is set for his favorite songs, the car air fresheners or the car perfume is according to his taste or the lighting inside the car is set according to his choice.
  • the car ambience is set according to the person who is in the driver’s seat when the car is a shared entity. This is taken care by the association context which resides inside the car console/dashboard and it is able to identify the person in the driver’s seat.
  • the car console/dashboard as an IoT device which may be typically equipped with several sensors, navigation capability, proximity connectivity, cellular radio capability and the usual audio/video control and the display unit.
  • driver #2 wife who is currently occupying the driver seat
  • driver #1 husband who is resting after couple of hours of driving and assuming he has not manually unpaired his smartphone. This leads to not only exposing of the privacy of the user (husband in this example) but also driver inconvenience assuming manually pairing in the shared car environment.
  • association/disassociation procedures such that the car console/dashboard is able to first identify the user occupying the driver seat and after user identification the car console/dashboard performs automatic procedure to associate with the concerned driver’s smart device (e.g., smartphone or smart watch) currently occupying the driver seat.
  • smart device e.g., smartphone or smart watch
  • the shared usage could also be extended to further use cases like small office environment or school environment or smart hotel environment where a team of employees (students) or hotel guests would need to associate their respective smart device with IoT device depending on the usage scenario.
  • Automatic association/disassociation (pairing/un-pairing) based on user identification would definitely enhance the user experience.
  • FIGS. 1 through 11, discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way that would limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged communications system.
  • the terms used to describe various embodiments are exemplary. It should be understood that these are provided to merely aid the understanding of the description, and that their use and definitions in no way limit the scope of the present disclosure. Terms first, second, and the like are used to differentiate between objects having the same terminology and are in no way intended to represent a chronological order, unless where explicitly stated otherwise.
  • a set is defined as a non-empty set including at least one element.
  • FIG. 1 illustrates manual association and disassociation (pairing and un-pairing) between an IoT device and a smart device according to an embodiment of the present disclosure.
  • an IoT device 100 is illustrated, where the IoT device 100 (e.g., a wearable device) can be associated with smart device #1 120 corresponding to user #1 110 using a manual procedure, which in one example may be based on an existing Bluetooth based connection set-up and pairing.
  • the IoT device 100 and smart device #1 120 When the Bluetooth interface in the IoT device 100 and smart device #1 120 is activated, then the IoT device 100 will send a discovery signal for Bluetooth devices in the proximity thereof, and on detecting the Bluetooth activated device, an association protocol between the IoT device 100 and smart device #1 120 is used to establish the connectivity. This establishment of the association/connectivity between two devices based on Bluetooth is called pairing. After pairing the devices, the two associated devices are allowed to transfer data using Bluetooth interface for any application specific exchange.
  • the association could be based on an NFC protocol, such that when the IoT device 100 having a passive NFC chip and smart device #1 120 enabled with active NFC chip come in physical contact data can be transferred from the smart device #1 120 to the IoT device 100.
  • the NFC based protocol can be leveraged to bootstrap the Bluetooth interface for pairing the IoT device 100 with smart device #1 120 when the two devices touch each other.
  • Bluetooth based association (pairing) remains intact as long as the two paired devices are in close proximity (a few meters). When the paired devices are out of range then the connectivity is lost. Un-pairing the two devices need to manually remove the bond between the two devices.
  • Association context means the smart device identity (e.g., name of a smart device i.e., smart device #1 120, smart device #2 121, smart device #3 122 so on and so forth) is associated with an authorized user (e.g., user #1 110, user #2 111, user #3 112, respectively) of the device based on user credential such as user identity metric.
  • Bluetooth pairing just creates association between the devices and not an association context which would tag the smart device (e.g., smartphone) to its authorised user and his credentials such as user identity metric.
  • the IoT device 100 is a shared device used by more than one authorized user (e.g., user #1 110, user #2 111, user #3 112 so on and so forth) then the existing association/disassociation does not take user identity into account and it is vulnerable to privacy encroachment. Further, this existing manual procedure works fine but could be further enhanced with user identification and based on association context which would automate the procedure and may eliminate the concern of privacy encroachment.
  • FIG. 2 illustrates a concept of an association context according to an embodiment of the present disclosure.
  • association context 210 a concept of creating an association context 210 is illustrated, where this concept can be based on using a database or look-up table to store the association context 210, where a unique user identity is tagged with a smart device (e.g., a smartphone) identity as an attribute for authorized usage of a shared wearable 200 (e.g., a smart watch which is an IoT device).
  • a smart device e.g., a smartphone
  • shared wearable 200 e.g., a smart watch which is an IoT device.
  • the unique user identity is based on a user identity metric which needs to be input (configured) in the wearable 200 through on board sensors to create the association context 210 using an application running on the wearable 200.
  • the association context 210 resides in the car console or dashboard comprising the user identity metric input through on board sensors in the car and/or car console.
  • the car console or dashboard is the wearable 200 (e.g., the IoT device), as illustrated in FIG. 2.
  • association context 210 is a list of unique user identity metrics for a plurality of authorized users of the shared wearable 200 (e.g., the IoT device).
  • a user identity metric is at least one of a finger print of the authorized user, an image of a face of the authorized user, an eye iris/retina of the authorized user, any biological parameter such as heart rate/blood flow rate/blood pressure of the authorized user, and the length of the strap of the wearable based on thickness of the wrist of the authorized user.
  • the user identity metric could be a combination of independent identity metrics.
  • the length of the strap of the wearable 200, when user #1 220 wears the wearable 200 is combined with the finger print or the eye iris/retina of user #1 220 to strengthen the uniqueness of the user identity metric.
  • the association context 210 can be enriched by tagging the unique user identity metric with several attributes.
  • One example of such attribute is the name of the smart devices (e.g., smart device #1 230 which may be a smartphone or tablet) belonging to that authorized user (i.e., user #1 220).
  • Another attribute could be protected storage space in the wearable 200 such that when data is transfer to the wearable 200 after user identification using the association context 210 of user #1 220 from the smart device #1 230, the data is stored in a pre-defined folder of that user (i.e., user #1 220 which is protected).
  • a further attribute could be auto sign-in/sign-out for social networking applications of the user such as KakaoTalk, Facebook, etc. running on the wearable 200 which would protect the incoming notifications to the wearable 200 when wearable is shared with another authorized user.
  • the association context 210 residing in the wearable 200 would first identify user #2 221 based on the user identity metric.
  • the wearable 200 then automatically un-pairs with smart device #1 230, signs-out of the social networking applications running on the wearable 200 associated with user #1 220 and automatically pairs with smart device #2 231 activating the social networking applications associated with user #2 221.
  • the attributes of the association context 210 can be list of audio/video files, air freshener or car perfume settings, inside car lighting settings or driver seat adjustment settings so on and so forth.
  • association context 210 of an authorized user can be enriched for filtering data, notifications, etc., associated with application used by that particular user so that it could be protected from privacy encroachment especially in a shared wearable (IoT device) scenario such as smart home environment or the smart car environment.
  • IoT device shared wearable
  • the association context concept is illustrated in FIG. 2, such that the wearable 200 maintains a database or look-up table of the unique identity metric tagged with one or more attributes associated with the authorized user.
  • the underlying assumption for creating such association context 210 is that the wearable 200 (e.g., the IoT device) is equipped with appropriate sensors to collect the unique identity metric of the authorized user through an application program running on the wearable 200.
  • the corresponding sensor on board the wearable 200 remains activated for user identification to further trigger the automatic association/ disassociation procedure proposed in the present disclosure.
  • the wearable 200 is wearable, the sensors are placed on board of the wearable.
  • the IoT device is car console or car dashboard the sensors like finger print detection sensor or the camera is placed on the steering of the car or some other convenient location inside the car.
  • the association context 210 may also include a primary user or master user of the wearable 200 (e.g., the IoT device).
  • the primary user could be the owner of the wearable 200 (e.g., the IoT device) or it could be someone who needs to be notified of certain situations and incident if an alert is triggered (e.g., in case of unauthorized usage or use cases like childcare/kid-care/eldercare etc.).
  • the association context 210 has an entry for primary user or master user of the IoT device who would be notified in certain situation if an alert is triggered for handling emergency situations.
  • the association context 210 can be stored in a server which can be fetched by the shared wearable to authorize the user for the usage of the wearable 200 and automatically associate/disassociate with a user’s (e.g., user #3 222) smart device (e.g., smart device #3 232) which is one of the attribute of the association context 210.
  • the association context 210 can be created by transferring the association context 210 from a user’s smart device (e.g., a smartphone) to a shared wearable device (e.g., a smartwatch). It is also possible to create a shared or public association context especially in a family environment where some information could be open information or public information which is not subject to privacy concerns.
  • Such shared association context 210 could be open to all authorized users or a pre-configured set of authorized users of the wearable 200 (IoT device).
  • the shared association context 210 is activated so that audio/video files settings and the car ambience setting is suitable for the entire family which is not subject to privacy concerns unlike the case when the car is exclusively used by either husband or wife where the association context 210 needs to take care of privacy encroachment.
  • certain applications in wearable device 200 are available for multiple authorized users (e.g., applications for smart home need to be usable for both authorized users, i.e., a husband and a wife).
  • FIG. 3 illustrates a procedure for automatic association (pairing) according to an embodiment of the present disclosure.
  • a flowchart is illustrated, such that an appropriate sensor on a wearable (e.g., an IoT device) is activated to capture a user identity metric of the user at operation 300.
  • a wearable e.g., an IoT device
  • the appropriate on board sensor captures the unique user identity metric for the creation of association context in the wearable (e.g., the IoT device)at operation 310.
  • association context list of user identity metric
  • the IoT device the wearable
  • all the authorized users and corresponding user identification metric are inputted.
  • the respective user identification metric is tagged with list of smart devices as attributes belonging to those authorized users to create the association context at operation 320
  • the captured unique user identity metric at operation 310 is at least one of a finger print of the authorized user or image of the face of the authorized user, eye iris/retina of the authorized user, any biological parameter such as heart rate/blood flow rate/blood pressure/weight of the authorized user, and the length of the strap of the wearable based on thickness of the wrist of the authorized user.
  • the association context is created at operation 320 for user #1 220 (refer FIG. 2) based on his/her unique identity metric and tagged with the attribute of smart device #1 230 belonging to user #1 220.
  • association context is created at operation 320 for user #2 221 (refer FIG.
  • the wearable e.g., the IoT device
  • the wearable is pre-configured at operation 320 by enriching the respective association context with several attributes such as smart device name belonging to that user or list of social networking applications associated with that user or other attributes mentioned for the smart car scenario.
  • the sensors such as the finger print detection sensor and/or the weight measurement sensor, or the camera may be placed at multiple places like the steering wheel of the car (especially the finger print sensor) or the seat of the car may be equipped with weight measurement sensor or the backrest of the driver seat and navigation seat is equipped with camera.
  • the attribute tagged to the unique identity metric is the identity or name of the smart device.
  • the smart device identity e.g., smartphone
  • the smart device identity may be something like Bluetooth name which is normally set to the manufacturer and model of the smartphone.
  • user friendly smart device identity can also be created by identifying the smart device by authorized user’s name something like ‘John smartphone’ or ‘Bill laptop’ etc.
  • the same smart device name used in the association context attribute is also configured within the smart device, for example changing the default Bluetooth name set by the manufacturer and model of the phone to ‘John smartphone’ if ‘John smartphone’ is the attribute tagged to the user identity metric of John (i.e., user #1 220) in the association context created at operation 320.
  • MAC media access control
  • the activated sensor at operation 330 captures the user identity for determining whether user #1 220 is an authorized user based on the identification metric at operation 340.
  • the IoT device performs a check with the association context for user identification.
  • the attributes are fetched from the association context of the user including a list of smart devices (i.e., smart device #1 230 associated with user #1 220) in operation 360.
  • the existing wearable pairing status is checked. If the wearable is already paired with some smart device, then the paired smart device is matched with the smart device #1 230 of user #1 220 based on the fetched attributes. If the smart device #1 230 name matches an already paired smart device name then nothing is done. If there is no matching then the existing device is automatically un-paired and then the wearable is paired with the smart device #1 230 belonging to user #1 220 based on the attribute tagged with user identity metric of user #1 220 in the association context in operation 370.
  • a proximity communication interface like Bluetooth is enabled and the wearable is automatically paired with the smart device #1 230 belonging to user #1 220 if detected in operation 370.
  • a successful user identification at operation 340 would trigger the Bluetooth protocol pairing functionality and the shared wearable gets paired with the smart device #1 230 of the user #1 220 (assume John as user #1 referring to FIG. 2) at operation 370. After operation 370, an exchange of information is performed between the wearable and smart device #1 230 at operation 380.
  • the wearable dissociates from the existing smart device and goes into a standby mode or a cellular trigger radio for alert at operation 350.
  • the operations mentioned in the automatic pairing/un-pairing procedure are merely listed in logical sequence to explain the working principle of the procedure. It should not be considered very restrictive to realize the automatic pairing/un-pairing procedure because the logical sequence may be slightly changed or some operations can be combined without deviating from the working principle of the procedure.
  • user #1 220 removes the shared IoT device and user #2 221 (assume Bill as user #2 referring to FIG. 2) is now using the shared IoT device, the IoT device is still paired with user #1 220 smart device (i.e., John smartphone #1 230).
  • user #1 220 smart device i.e., John smartphone #1 230.
  • the IoT device is able to detect/check change in user. Based on this operation at 340 some pre-defined operations are invoked as mentioned above where shared IoT device (200 referring to FIG. 2) shall disassociate itself from ‘John smartphone’ 230 and associate with ‘Bill laptop’ 231.
  • shared IoT device (200 referring to FIG. 2) shall disassociate itself from ‘John smartphone’ 230 and associate with ‘Bill laptop’ 231.
  • the association context is structured and enriched the data exchange performed by the respective user of the shared IoT device (wearable) is protected from privacy encroachment.
  • IoT device upon successful detection of authorized user, performs at least one of: triggering the proximity connectivity protocol to perform connection release with currently associated smart device of previous user and connection setup with another smart device of another authorized user using the smart device attribute tagged to the user identity metric based on the association context querying.
  • IoT device upon successful detection of authorized user and after establishing connection (association) with smart device, IoT device performs at least one of: exchange of information with associated smart device and secure information storage maintaining confidentiality of stored data based on pre-defined filters.
  • the proposed association procedure is explained using the Bluetooth protocol functionality for pairing. However, this is not the limiting case and it may be based on discovery functionality of any proximity connectivity interface like Wi-Fi, Zigbee etc.
  • the car console or car dashboard (IoT) device In case of smart car it is not necessary that the car console or car dashboard (IoT) device always pairs with the smart device of the person sitting in the driver seat. This may be left to configuration of attributes of the association context. In some cases just the car ambience settings are tuned according to the person sitting is driver seat (private attributes activated) when he or she is the sole passenger in the car while when there are multiple passengers inside the car then the car ambience settings are tuned according to the family attribute (shared or public or open attribute) of the association context.
  • driver seat private attributes activated
  • IoT device upon successful detection of authorized user or users IoT device (car console or dash board) performs at least one of the actions: setting the audio/video directory, air freshener or car perfume settings, inside car lighting settings or driver seat adjustment settings based on pre-defined filters (i.e., either activating a private attribute associated with the user sitting in the driver seat if he or she is alone or activating shared or public attribute associated with the user sitting in the driver seat if accompanied by a fellow passenger, such as family.
  • pre-defined filters i.e., either activating a private attribute associated with the user sitting in the driver seat if he or she is alone or activating shared or public attribute associated with the user sitting in the driver seat if accompanied by a fellow passenger, such as family.
  • the wearable 200 is still paired with the smart device #1 230 (i.e., John smartphone 230) of user #1 220.
  • the wearable 200 Upon capturing the user identity metric of user #N and checking the association context the wearable 200 is able to detect that user #N user identity metric does not match with any user identity metric stored in the available association context.
  • the IoT 200 may perform at least one the following operations depending on the usage scenario.
  • the wearable 200 may merely disassociate itself from existing smart device ‘John smartphone’ 230 (if still paired) to protect the privacy of user #1 220. Before disassociating (un-pairing) the wearable 200 may send an alert to user #1 220 (i.e., John smartphone 230) to notify unauthorized usage of the wearable 200.
  • the wearable 200 may completely disable the automatic association procedure so that unauthorized user cannot pair the wearable 200 with any of his/her device even manually.
  • the wearable 200 is not initially paired with authorized user device and it has cellular radio capability (e.g., global system for mobile communications (GSM) connectivity, universal mobile telecommunications system (UMTS) connectivity, long term evolution (LTE) connectivity, or code division multiple access (CDMA) connectivity, etc.), then upon detection of unauthorized usage it may trigger the cellular radio ON if OFF and it may trigger mobile originated call.
  • the mobile originated call may also be triggered if cellular radio inside the wearable 200 is in sleep state to active state according to mode of the cellular radio (e.g., GSM, UMTS, LTE, or CDMA radio, etc.).
  • the wearable 200 may send a notification with captured snapshot data like location information and user identity metric of unauthorized user etc. via cellular link to the user #1 220 who is authorized user (primary user or master user) of the wearable 200.
  • wearable may send notification/alert to one or more authorized users configured in the association context.
  • the IoT device (car console or car dash board) was not initially paired with authorized user smart device (i.e., smartphone of the owner of car) and the car console or car dash board has cellular radio capability (e.g., GSM, UMTS, LTE, or CDMA, etc.), then upon detection of unauthorized usage (assuming intruder is expert in disabling the in-built alarm functionality of car and manages to slip inside the car) it may trigger the cellular radio ON if OFF and it may trigger mobile originated call.
  • cellular radio capability e.g., GSM, UMTS, LTE, or CDMA, etc.
  • the mobile originated call may also be triggered if cellular radio equipped in the IoT device is in sleep state to active state according to mode of the cellular radio so that notification is sent to the authorized user smart device (e.g., smartphone) indicating his/her car is getting stolen.
  • the authorized user smart device e.g., smartphone
  • IoT device upon detection of unauthorized usage of IoT device at least one of: disabling the automatic association functionality and sending an alert to primary user and/or one or more authorized user either through proximity connectivity or cellular connectivity.
  • alert notification upon detection of unauthorized usage of IoT device if alert notification is sent to primary user and/or one or more authorized user then it includes at least one of: user identity metric of unauthorized user and location information if available.
  • FIG. 4 illustrates a shared device scenario between authorized users according to an embodiment of the present disclosure.
  • a wearable device 400 (e.g., an IoT device) that is shared with user #1 420 and user #2 421 is illustrated, such that all details of the authorized users among whom the wearable device 400 is shared, are pre-configured into the wearable device 400 residing in an association context 410 (e.g., a context association stored in a database or a look-up table) along with smart device names of user #1 420 (i.e., smart device #1 430) and user #2 421 (i.e., smart device #2 431) tagged to the user identity metric of user #1 420 and user #2 421 respectively.
  • an association context 410 e.g., a context association stored in a database or a look-up table
  • the car ambience settings like the audio/video file directory, the air freshener or car perfume setting, the seat adjustment settings etc. is according to user #1 420 who is currently occupying the driver seat (assuming private attribute is activated for user #1 420). After driving the car for some distance user #1 420 picks up a friend who is neither part of the family nor is an authorized user.
  • the car ambience setting is a private setting to user #1 420
  • the association context residing in the car console/dashboard detects another co-passenger in the car and identifies he/she is neither member of the family nor an authorized user, then it may de-activate the private setting of user #1 420 so that his privacy is not compromised and activates a shared setting using the shared association context (shared attribute or public attribute is activated while private attribute is de-activated).
  • the car console/dashboard equipped with the IoT device is paired with smart device #1 430 of user #1 420 who is currently occupying the driver seat and also paired with smart device #2 431 of user #2 421, if user #2 421 is co-passenger in the car and user #2 421 is a family member. Since user #1 420 is driving the car the only useful interaction he/she can have with the car console/dashboard is for notification from his/her smart device #1 430 to display on the car console or for navigation commands on the display of the car dashboard. However, user #2 421 who is co-passenger either in navigator seat or passenger seat can have more active interaction with the console/dashboard in terms of using the display for playing games or watching video provided it does not distract user #1 420 who is occupying the driver seat.
  • console Such interactive use of the console is possible if the display on the backrest of the driver seat or navigator seat is activated when user #2 421 is sitting in the passenger seat. If user #2 421 is sitting in navigator seat then it seems reasonable to deactivate entertainment video on the display of the car console/dashboard since it will distract user #1 420 who is driving the car such that safe driving is given the most importance. In this scenario even though the console is paired with multiple smart devices (i.e., the smart devices #1 430 and #2 431 of user #1 420 and user #2 421) the control is with user #2 421 to enjoy the smart car environment.
  • the console is paired with multiple smart devices (i.e., the smart devices #1 430 and #2 431 of user #1 420 and user #2 421) the control is with user #2 421 to enjoy the smart car environment.
  • user #1 420 main device i.e., smart phone #1 430
  • smart speaker or smart TV or smart display or tablet etc. either as single connection or as simultaneous connections with above shared devices connected through a shared IoT device.
  • user #1 420 is enjoying either the smart home or smart office or smart environment according to his/her private settings for the interaction with various devices (here private setting would mean since user #1 420 is alone in the smart environment so he/she is enjoying the video on smart TV or smart display, listening to loud and high quality music from smart speaker etc.).
  • the IoT device When the IoT device detects that another user #2 421 is coming in proximity of user #1 420, then in order not to encroach his privacy the IoT device deactivates the private settings of user #1 420 by disconnecting the speaker if music from the smart device #1 430 of user #1 420 is played on the speaker, or disconnects the smart TV or smart display if something from user #1 420 smart device is displayed on the big display of TV while activating the public setting.
  • the guest rooms of the hotel will be shared among many guests staying/visiting the hotel on a time basis (i.e., hotel room is shared when one guest check-out and another guest check-in).
  • the smart hotel room with all the resources of the room like TV, Refrigerator, washing machine, lighting, heating, ventilating, and air conditioning (HVAC), door lock etc. will be the shared entity among multiple users on a time basis.
  • Frequent visiting guest’s association context can be stored on the hotel servers or room gateway or guest’s smart phone with unique identification metric like mobile phone number, his/her passport or social security number, his/her smart phone’s wireless MAC identifier (e.g., Bluetooth or NFC MAC ID) or membership number of loyalty program for frequent guests etc.
  • Hotel server will also have room booking or reservation details and corresponding guest details with identification metric.
  • One way of authentication of the guest can be performed by the devices like smart door lock which can recognize the unique pin or mobile number, or guest smart phone’s hardware details etc., or by device like camera at the door which can authenticate guest by the techniques like by face detection, iris detection etc.
  • the association context of the corresponding guest will be fetched from any possible sources like guest’s mobile phone/wearable, or any device in the room like gateway, or hotel server etc. to activate the attributes (i.e., settings of the guest room) tagged to the user identity metric in the association context.
  • the attributes i.e., settings of the guest room
  • all the devices/resources inside the guest room allocated to the guest will be configured as per the guest’s preferences when he/she check-in. Guest might set preferences like preferred room temperature level, preferred humidity level, favorite TV channels, room lighting, housekeeping preferences, additional services (e.g., food, gym, transport, swimming pool etc.) subscriptions etc.
  • the private setting is de-activated and the public settings are activated without interruption in user activity and protecting the user privacy.
  • the user identity metric for uniquely identify the user can be anything with which the user can be identified.
  • FIG. 5 illustrates an automatic association procedure for a shared device scenario according to an embodiment of the present disclosure. It is assumed that with sensors on a wearable, that the wearable detects when a user wears or removes the wearable and upon identification of change in user the association/pairing procedure is triggered. The detailed association/pairing procedure is described in FIG 3.
  • a procedure is illustrated, such that it is assumed a wearable 500 (e.g., an IoT device) (400 referring to FIG. 4) is currently used by user #1 420 and therefore is associated with smart device #1 501 (430 referring to FIG. 4) which belongs to user #1 420 (i.e., current activated association context refers to user #1 420).
  • a wearable 500 e.g., an IoT device
  • smart device #1 501 430 referring to FIG. 4
  • current activated association context refers to user #1 420.
  • the pre-defined user identity metric of the user is captured by the activated onboard sensor on the wearable 500.
  • the association context residing in the wearable 500 is invoked for user identification to authenticate the user identity metric captured in operation 510.
  • the wearable 500 After invoking the association context at operation 520, the wearable 500 is able to detect if user #2 421 (of FIG. 4) of the wearable 500 is an authorized user by ascertaining the user identity metric captured in operation 510 with the stored user identity metric in the invoked association context. After user identification the wearable 500 compares the invoked association context with the current activated association context for checking if there is change in user at operation 530.
  • user #2 421 If the user identity data of user #2 421 captured by the onboard sensor at operation 510 of the wearable 500 matches with the user identity metric retrieved from the invoked association context at operation 520, then user #2 421 will be identified as the authorized user and the wearable 500 performs one or more predefined operations mentioned below.
  • wearable 500 keeps the association context activated for user #1 420. Since wearable 500 is already paired with a smart device #1 501 (i.e., smart device #1 430 belonging to user #1 by referring to FIG. 4), then verify if the paired smart device #1 501 belongs to the user #1 420. If smart device #1 501 belongs to the user #1 420, then nothing to be done, pairing status will be maintained as it is as shown in operation 550 (in this case activated association context refers to smart device #1 501).
  • a smart device #1 501 i.e., smart device #1 430 belonging to user #1 by referring to FIG. 4
  • wearable 500 disassociate (un-pairs) with the smart device #1 501, and associates (pairs) with smart device #2 502 (431 referring to FIG. 4) based on the activated association context it will discover smart device #2 502 (431 referring to FIG. 4) is belonging to user #2 421(in this case activated association context refers to smart device #2 502).
  • wearable 500 If wearable 500 is not paired with any smart device (i.e., it is in standby mode), then upon user identification (in this case user #2 421 is authorized) the wearable device 500 activates the association context for user #2 421 and auto pairs with the user's smart device pre-configured in the activated association context (in this case at operation 560 the activated association context refers to smart device #2 502).
  • wearable 500 automatically performs at least one of the following pre-defined tasks. These predefined tasks can be turning on the cellular radio capability of the wearable 500 (if equipped with 2G/3G/4G) and send notification to the primary user of the device; automatically un-pair the wearable 500 if already paired with some smart device and disable the automatic association (pairing) feature of the wearable 500 etc.
  • the wearable 500 Upon removing the wearable 500, the wearable 500 auto detects and un-pairs with the smart device and enters a standby mode at operation 540.
  • FIG. 6 illustrates smart pairing to multiple devices in a smart home environment according to an embodiment of the present disclosure.
  • Smart pairing to multiple devices means switching pairing among multiple devices of a user, such that an IoT device is paired to any one smart device at a given time from a plurality of smart devices.
  • a smart home environment is illustrated, such that in the smart home environment a wearable 600 (e.g., an IoT device) is required to pair to multiple devices in different locations in the home.
  • a wearable 600 e.g., an IoT device
  • the wearable 600 associates with the nearest smart device. This is possible through the proposed automatic association procedure and enriched association context as described in FIG 3.
  • Multiple smart devices e.g., smart device #1 610 at location #1, smart device #2 620 at location #2, smart device #3 630 at location #3, smart device #4 640 at location #4 etc.
  • User 601 of the wearable 600 may have multiple smart devices at home in different rooms. When user is in a living room, then the wearable 600 shall automatically pair with the device present in the living room. If the user moves to a bedroom, then the wearable 600 automatically pairs with a device present in the bedroom. The wearable 600 always connects to the nearest smart device of the user 601 such that battery power of both the wearable 600 and the smart device are saved.
  • auto pairing with the nearest smart device would help not only in saving the battery power of the wearable 600 but also providing a seamless service in terms of user experience.
  • the wearable 600 is paired with smart device #1 610 when the user 601 is in location #1 of his/her home.
  • the wearable 600 would pair with the nearest smart device #2 620 at location #2 and un-pair from the smart device #1 610 at location #1 because smart device #1 610 is far compared to smart device #2 620 with respect to the location of the wearable 600.
  • the smart device is a mobile device like a smart phone, laptop or a tablet etc.
  • the battery level of the smart device also will be considered while auto-pairing the wearable 600.
  • the wearable 600 may be periodically receiving updates of the battery level of the smart device to which it is connected.
  • the connectivity protocols like Bluetooth provides a mechanism for exchanging the battery level information between the connected devices. If the wearable 600 detects that the battery level of the connected smart device reaches lower than the preconfigured level, then wearable automatically scans for any other smart devices in the vicinity with a better battery level than the current paired smart device. If there is/are other smart device/s with better battery level discovered by the wearable 600, then at least one of the following is performed.
  • the proximity connectivity interface such as Bluetooth pairing functionality is triggered to check if there are other smart devices in vicinity based on the list in the association context. If other smart device from list is detected then the battery level of the smart devices with respect to all detected devices is estimated and compared.
  • the wearable 600 disassociates with currently paired device and associates with the smart device having the highest battery level.
  • the wearable 600 may perform signal strength measurement with the paired smart device and also account for the battery power level of the smart device. Based on these two metrics (i.e., signal strength measurement and/or battery power level) the IoT device automatically pairs with the smart device such that battery power consumption of the both the IoT wearable and smart device will be minimized.
  • FIG. 7 illustrates a procedure to connect to a nearest smart device in a home environment according to an embodiment of the present disclosure.
  • an IoT device 700 such as a wearable device, is illustrated, where the IoT device 700 is currently associated with smart device #1 701 using the proposed automatic association/pairing procedure such that smart device #1 701 placed at location #1 gets paired since a currently identified user is also located at location #1.
  • FIG. 7 illustrates the process of the IoT device 700 connecting to one of smart device #1 701, smart device #2 702 and smart device #N 703.
  • Operations 710 and 720 are performed according to operations 300, 310, 320, 330, 340, 350, 360, 370 and 380, as illustrated in and as described with respect to FIG 3.
  • the IoT device 700 is equipped with a displacement sensor such as a pedometer.
  • the IoT device 700 identifies displacement then it updates the distance covered by the movement of the user.
  • the displacement sensor may also be optionally assisted with indoor positioning mechanisms if equipped in the IoT device 700 to more accurately estimate the distance based on location information.
  • the sensor detects the current user’s movement and identifies the movement by accounting for number of steps taken by the user compared to first step update when movement was detected to estimate if the distance is above a pre-defined threshold at operation 740. If the distance moved by the IoT device 700 is above a pre-defined threshold then some pre-defined actions are invoked. During an observation window the displacement sensor (pedometer) estimates the number of steps (current location if equipped with indoor positioning mechanism) and stores it for future comparison when the observation window is invoked next time. Comparing the displacement (optionally location) samples from the two observation windows the distance moved is estimated and compared with a threshold value. The displacement metric may be combined with the battery level metric of the currently paired smart device and compared with threshold value.
  • the proximity connectivity interface such as Bluetooth pairing functionality is triggered to check if there are other smart devices in vicinity based on the list in the association context at operation 750.
  • the IoT device 700 detects smart device #2 702 (620 with reference to FIG. 6). If another smart device from the list is detected then the signal strength (either as power measurement in decibel-milliwatts (dBm) or signal to noise ratio measurement in decibels (dB) and/or battery level) with respect to all detected devices is estimated and compared at operation 760.
  • the signal strength either as power measurement in decibel-milliwatts (dBm) or signal to noise ratio measurement in decibels (dB) and/or battery level
  • the IoT device 700 compares the signal strength measurement between itself and smart device #1 701 (currently paired device and battery level of smart device #1 701) and the signal strength measurement between itself and smart device #2 702 (device detected at location #2 and belonging to device list in the association context and battery level of smart device #2 702). IoT device 700 associates with the smart device having the strongest signal strength (and/or highest battery level) and disassociates from the currently paired device at operation 770. Based on the signal strength and/or battery level comparison if the signal strength and/or battery level with respect to smart device #2 is highest then IoT device 700 un-pairs from smart device #1 701 at location #1 and pairs with smart device #2 702 at location #2.
  • the pairing between wearable 700 and a smart device #1 701 remains at operation 780.
  • the IoT device 700 upon detection of displacement above a threshold value, performs at least one of: triggering the proximity connectivity protocol to perform connection release with currently associated smart device; and connection setup with another smart device based on the comparative signal strength and/or battery level and using the smart device attribute tagged to the user identity metric based on the association context querying.
  • IoT device 700 upon detection of battery level below a threshold value of currently associated smart device, IoT device 700 performs at least one of: triggering the proximity connectivity protocol to perform connection release with currently associated smart device; and connection setup with another smart device based on the comparative signal strength and/or battery level and using the smart device attribute tagged to the user identity metric based on the association context querying.
  • FIG. 8 illustrates automatic triggering of a cellular radio communication capability of an IoT device according to an embodiment of the present disclosure
  • a wearable 800 paired with a smart device 830 is illustrated, where it is assumed that when the wearable 800 is paired with the smart device 830 of a user 820, the cellular capability of the wearable 800 (e.g., an IoT device) is OFF.
  • the wearable 800 e.g., an IoT device
  • such paired wearable 800 may have its own subscription identity (subscriber identity module (SIM)/universal integrated circuit card (UICC)) or may share the subscription identity (SIM/UICC) of the authorized paired smart device using the SIM access profile (SAP) defined in Bluetooth specification. Further, it can also be assumed such cellular capable wearable 800 may have very long sleep cycles configured (on order few seconds/minutes) in order to save battery. Wearable technology will be adopted for many use cases like physical fitness, kid-care, childcare and eldercare, etc. in future. Conserving battery power will be most important requirement for such cellular capable wearable 800.
  • SIM subscriber identity module
  • UICC universal integrated circuit card
  • trigger condition 840 it is assumed the wearable 800 has on board sensors (e.g., camera, fingerprint scanner, accelerometer, gyroscope, etc.) that are activated.
  • sensors e.g., camera, fingerprint scanner, accelerometer, gyroscope, etc.
  • the following use cases are expected to gain market penetration requiring the above mentioned functionality.
  • Health care or physical fitness related wearables having cellular capability (3G/4G) would need the triggering of the cellular radio when the user 810 leaves home environment to do sports activity involving running, jogging, cycling, etc. in which case the wearable 800 is no more paired with the smart device 830 and the user does not carry the smart device 830 (smartphone) while doing physical activity.
  • the wearable 800 needs to detect trigger condition 840 which would turn ON the cellular radio automatically when the user takes outdoors for physical activity.
  • Wearables having cellular capability (3G/4G) are expected to be widely used for childcare/kid-care/eldercare scenarios where the cellular capable wearable (IoT device) is in standby mode (means not paired with associated smart device 830) and there is a need (e.g., a trigger condition 840) to either turn ON the cellular radio automatically or wake-up the cellular radio from sleep cycle to trigger mobile initiated call to send notification to smart device (smartphone) 830 through cellular link to notify either parents of a kid or a caretaker of elderly people in case of unwanted incident which may prove fatal.
  • the wearable 800 shall be able to send alert notification to parents 820 on the smart phone 830.
  • the wearable 800 shall be able to detect trigger condition 840 to send alert notification to caretaker 820 on the smart phone 830.
  • FIG. 9 illustrates a general procedure for sending an alert notification to an authorized user according to an embodiment of the present disclosure.
  • a wearable 900 e.g., an IoT device
  • a smart device #1 901 are illustrated, where the wearable 900 has cellular radio capability and is normally associated with the smart device #1 901 when it is close proximity.
  • This pairing at operations 910 and 920 may be based on the proposed automatic association/pairing operations 300, 310, 320, 330, 340, 350, 360, 370 and 380, as illustrated in and as described with respect to FIG. 3.
  • the wearable 900 When the wearable 900 is already paired with the smart device 901, the radio capability is turned OFF. In another scenario the wearable 900 may be in standby mode (i.e., not paired with a smart device) when it is not in proximity of the smart device 901 and may either have cellular radio capability turned OFF or if ON then it may be in long sleep cycle at operation 930. So, for the different use cases mentioned above there is need to identify a trigger condition (operation 840 referring to FIG. 8) to either turn ON the cellular radio capability if OFF or wake-up the cellular radio from long sleep cycle to trigger mobile initiated call if the trigger condition is met.
  • a trigger condition operation 840 referring to FIG. 8
  • a cellular radio capability of the wearable 900 is turned ON and the wearable 900 is used to send/receive messages, make calls, or send notifications if not in proximity of smart device 901.
  • the cellular radio capability of the wearable is turned ON or the cellular radio is woke up from a long sleep cycle and a connection establishment procedure is started with a cellular network.
  • an alert notification is sent to the receiver (parents/caretaker) including a snapshot of the incident (unwanted incident to child/kid or accident of elderly person) in the form picture, audio or video clip and/or live streaming of incident etc.
  • the trigger condition 840 (refer to FIG. 8) for such alerting could be pre-defined and tagged as an attribute to the user identity metric in the association context described above.
  • the association context can be enriched by tagging the user identity metric with the trigger condition.
  • the trigger condition could be based on at least one or a combination of more than one attribute as follows: a biological parameter like heart rate, blood pressure (the user identity metric itself); or emotional gesture attribute like crying, shouting, yelling (for kid-care at day care); or speech attribute like use of abusive words, help-help call (childcare at school or playground); or gravitational fall threshold (eldercare) or smoke detection attribute (childcare).
  • a biological parameter like heart rate, blood pressure (the user identity metric itself); or emotional gesture attribute like crying, shouting, yelling (for kid-care at day care); or speech attribute like use of abusive words, help-help call (childcare at school or playground); or gravitational fall threshold (eldercare) or smoke detection attribute (childcare).
  • operation 970 is performed to keep the wearable 900 associated with the smart device #1 901 or to place the wearable 900 in a standby mode.
  • FIG. 10 illustrates a specific procedure for sending an alert notification to an authorized user according to an embodiment of the present disclosure.
  • a procedure is illustrated, such that if a trigger condition is not detected then a wearable (IoT) remains either associated with a smart device or remains in a standby mode.
  • the automatic triggering of the cellular capability of the wearable device for a specific case of elderly care is described here.
  • the wearable (IoT) device (900 referring to FIG 9) having a cellular radio capability is normally associated with a smart device (901 referring to FIG 9) when it is in close proximity. But when the elderly person wearing the wearable device goes out of the proximity range from the smart device, then the wearable device cannot be paired with the smart device based on proximity connectivity such as Bluetooth.
  • the identification of the person based on user authentication metric may be based on the proposed automatic association/pairing procedure described in FIG 3.
  • wearable detects that the device is worn by a person then sensors on board of the wearable device will be activated for user identification and authentication at operation 1000.
  • the user identification details collected from sensors on board of the wearable device are used to create the association context through an application program and stored in the wearable device at operation 1010.
  • the association context with respect to an elderly care scenario can contain one or more user identity metric for at least one of any biological parameters of the user like heart rate, blood pressure rate etc. and trigger condition such as displacement threshold (such as gravitational fall threshold) to detect the fall of the elderly person.
  • the cellular capable wearable device radio will either be turned OFF or wearable device enters the standby mode such that the cellular radio is in a deep sleep cycle at operation 1020.
  • the wearable sensors only which are required as per the user identity metric or trigger condition defined in operation 1010 to form the association context are enabled on the wearable device at operation 1030.
  • the sensors on board of the wearable device are activated when the user is wearing the wearable device to capture the user identity metric and/or trigger condition to match with the association context details after fetching from the association context to check if he/she is an authorized user.
  • the wearable will gather data from all the required onboard sensors of the wearable device to detect the trigger condition to turn ON the cellular radio or wake-up the cellular radio from sleep cycle. For example, if the elderly person was sleeping in bed or taking the stair-case for climbing up or coming down and if he/she falls due to losing control then the onboard sensor would detect the gravitational fall through the onboard sensor such as accelerometer or gyroscope or any other appropriate sensor and match for data captured through the sensor with the trigger condition configured in the association context for identification of the trigger condition.
  • the onboard sensor such as accelerometer or gyroscope or any other appropriate sensor and match for data captured through the sensor with the trigger condition configured in the association context for identification of the trigger condition.
  • the wearable If the cellular capable wearable detects that the trigger condition is met based on the captured data received from the onboard sensor of the wearable, the wearable soon turns ON the cellular radio of the device if OFF or wakes-up from the sleep cycle and triggers connection establishment with the cellular network at operation 1050.
  • the wearable After the wearable establishes the cellular connection with the network, it performs at least one of the pre-defined actions like notifying smart device of care taker associated with elderly person configured in the association context or any authorized users configured smart device through cellular network with the snap shot of the incident at operation 1060.
  • the snap shot of the incident can contain any useful information about the incident like audio, video etc. of the elderly person who is wearing the wearable device, current location of the elderly person where incident happened, live audio/video streaming with the configured smart device, the speed of fall if wearable detected fall of the person etc.
  • wearable device detects at operation 1040 that the triggered condition is not met based on the captured data received from the onboard sensor, then it will be remain associated with the smart device of the elderly person if wearable is within the proximity of the smart device, else enters standby mode with the onboard sensors active for monitoring the trigger condition. As shown in FIG 10 if the trigger condition is not detected then wearable (IoT device) remains either associated with smart device or remains in standby mode at operation 1070.
  • the attribute to auto trigger IoT device having radio capability can be at least one of the following: a biological parameter like heart rate, blood pressure; emotional gesture attribute like crying, shouting, yelling; speech attribute like use of abusive words, help-help; gravitational fall threshold and smoke detection threshold.
  • cellular radio capable wearable turned OFF in home environment.
  • the cellular capable wearable can be turned ON/OFF automatically based on the biological metric like heart rate, blood flow rate etc. which would be above threshold when user doing physical activity.
  • cellular radio capable wearable For the day-care use case, case when baby is normal and happy in daycare so cellular radio capable wearable OFF.
  • the cellular capable wearable can be turned ON automatically or wake-up the cellular radio from long sleep cycle if already ON based on emotional gesture recognition like crying when baby is left in day-care facility. Auto trigger notify parents for quick action and save battery of wearable.
  • the cellular capable wearable can be turned ON automatically or wake-up the cellular radio from long sleep cycle if already ON if it is detached from the baby intentionally when left in day-care facility to notify parents
  • cellular radio capability of wearable For childcare use case, children when normal at school i.e., playing and studying in school so cellular radio capability of wearable OFF.
  • the cellular radio capability of wearable can be turned ON automatically or wake-up the cellular radio from long sleep cycle if already ON based on emotional gesture or speech recognition like yelling or use of abusive language etc. when child is at school or playground having quarrel. Auto trigger notify parents for quick action and save battery of wearable
  • the cellular radio capability of wearable can be turned ON automatically or wake-up the cellular radio from long sleep cycle if already ON based on speech recognition like ‘help-help call’ when child is getting kidnapped by anti-social elements. Auto trigger notify parents for quick action and save battery of wearable
  • the cellular radio capability of wearable can be turned ON automatically or wake-up the cellular radio from long sleep cycle if already ON based on smoke detection when due to new change in life style child may be exposed bad company and starts smoking cigarettes. Auto trigger notify parents for quick action and save battery of wearable.
  • the cellular radio capability of wearable can be turned ON automatically or wake-up the cellular radio from long sleep cycle if already ON based on location and time attribute when child goes out of the school campus during school working hours. Auto trigger notify parents for quick action and save battery of wearable.
  • the cellular capable wearable is OFF during normal activity of elderly person.
  • the cellular capable wearable can be turned ON automatically or wake-up the cellular radio from long sleep cycle if already ON based on gravitational fall detected by accelerometer when elderly person falls. Auto trigger notify caretaker for quick action and save battery of wearable.
  • FIG. 11 is a block diagram of a wearable device according to an embodiment of the present disclosure.
  • a wearable device 1100 (e.g., an IoT device) is illustrated, where the wearable device 1100 comprises a radio frequency (RF) front-end 1110, one or more baseband processors 1111, 1112, a processor 1120, a memory 1140 and one or more sensors 1130, 1131, 1132.
  • the RF front-end 1110 and the baseband processors 111, 112 are able to handle multiple wireless technologies including cellular radio, Bluetooth and RF channel (RFC).
  • the processor 1120 is connected with the one or more baseband processors 1111, 1112, the memory 1140, and the one or more sensors 1130, 1131, 1132.
  • the one or more sensors 1130, 1131, 1132 comprising camera 1130, a heart rate sensor 1131 and other multiple sensors are configured to capture user identity metrics of a user and/or capturing data to detect trigger condition used for alerting of unwanted or fatal situations.
  • the wireless interface comprising the RF front-ends and the one or more baseband processor is configured to perform communication with other electronic device, and to pair/un-pair with/from the other electronic device automatically.
  • the processor configured to control the sensor to capture the user identity metrics, and identify a user based on an association context and the user identity metrics and/or to control sensor to capture data to detect trigger condition used for alerting of unwanted or fatal situation.
  • the memory 1140 is configured to store the association context.
  • the processor 1120 is further configured to determine that the user is an authorized user based on a comparison result between the captured user identity metrics and the stored association context, and the processor 1120 is further configured to fetch attributes in the association context from the memory 1140, check a pairing status of the electronic device, if the user is the authorized user.
  • the processor is further configured to determine a first device belongs to the user based on the fetched attributes, if the electronic device is already paired with the first electronic device, and the processor 1120 is further configured to control the one or more wireless interfaces to un-pair from the first device automatically, and pair with an electronic device of the user, if the first device belongs to other user.
  • the processor 1120 is further configured to control to the one or more wireless interfaces to pair with an electronic device of the user automatically, if the IoT device is not paired with any electronic device.
  • the processor 1120 is further configured to control the one or more wireless interfaces to alert a notification to the authorized user using cellular radio if the user is not the authorized user or to alert some authorized person in the event that the IoT device detects the trigger condition is met about and unwanted or fatal situation.
  • the processor 1120 is further configured to control the one or more wireless interfaces to un-pair from an electronic device which is already paired with the IoT device, and to scan other electronic device to pair with, if the IoT device is moved a distance greater than a threshold.
  • the processor 1120 is further configured to store the user identity metrics and/or trigger condition to construct the associated context to the memory 1140.
  • a non-transitory computer readable recording medium is any data storage device that can store data which can be thereafter read by a computer system. Examples of the non-transitory computer readable recording medium include Read-Only Memory (ROM), Random-Access Memory (RAM), CD-ROMs, magnetic tapes, floppy disks, and optical data storage devices.
  • ROM Read-Only Memory
  • RAM Random-Access Memory
  • CD-ROMs Compact Disc-Read Only Memory
  • the non-transitory computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion. Also, functional programs, code, and code segments for accomplishing the present disclosure can be easily construed by programmers skilled in the art to which the present disclosure pertains.
  • various embodiments of the present disclosure as described above typically involve the processing of input data and the generation of output data to some extent.
  • This input data processing and output data generation may be implemented in hardware or software in combination with hardware.
  • specific electronic components may be employed in a mobile device or similar or related circuitry for implementing the functions associated with the various embodiments of the present disclosure as described above.
  • one or more processors operating in accordance with stored instructions may implement the functions associated with the various embodiments of the present disclosure as described above. If such is the case, it is within the scope of the present disclosure that such instructions may be stored on one or more non-transitory processor readable mediums.
  • processor readable mediums examples include Read-Only Memory (ROM), Random-Access Memory (RAM), CD-ROMs, magnetic tapes, floppy disks, and optical data storage devices.
  • ROM Read-Only Memory
  • RAM Random-Access Memory
  • CD-ROMs Compact Disc-ROMs
  • magnetic tapes magnetic tapes
  • floppy disks optical data storage devices.
  • the processor readable mediums can also be distributed over network coupled computer systems so that the instructions are stored and executed in a distributed fashion.
  • functional computer programs, instructions, and instruction segments for accomplishing the present disclosure can be easily construed by programmers skilled in the art to which the present disclosure pertains.
PCT/KR2015/012588 2014-11-26 2015-11-23 Method and apparatus for pairing a wearable device and a smart device WO2016085214A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP15862185.4A EP3225073A4 (en) 2014-11-26 2015-11-23 Method and apparatus for pairing a wearable device and a smart device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN1243KO2014 2014-11-26
IN1243/KOL/2014 2014-11-26

Publications (1)

Publication Number Publication Date
WO2016085214A1 true WO2016085214A1 (en) 2016-06-02

Family

ID=55743294

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2015/012588 WO2016085214A1 (en) 2014-11-26 2015-11-23 Method and apparatus for pairing a wearable device and a smart device

Country Status (4)

Country Link
US (1) US20160150350A1 (zh)
EP (1) EP3225073A4 (zh)
CN (2) CN106211022A (zh)
WO (1) WO2016085214A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108174015A (zh) * 2017-11-27 2018-06-15 拉卡拉支付股份有限公司 功耗控制方法、装置、可穿戴设备及计算机可读存储介质
US10697811B2 (en) 2016-10-31 2020-06-30 Nokia Technologies Oy Method, apparatus and computer program product for providing sensor data collection and sensor configuration
CN112153633A (zh) * 2019-06-29 2020-12-29 华为技术有限公司 一种发送、接收能力信息的方法及设备

Families Citing this family (73)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101673305B1 (ko) * 2014-12-11 2016-11-22 현대자동차주식회사 이기종간 멀티 스트리밍 서비스를 제공하는 헤드 유닛 및 그의 스트리밍 제어 방법, 그리고 이를 실행하는 프로그램이 기록된 컴퓨터 판독 가능한 기록매체
US10291595B2 (en) 2014-12-18 2019-05-14 Afero, Inc. System and method for securely connecting network devices
US10187364B2 (en) * 2015-02-27 2019-01-22 Plantronics, Inc. Wearable user device for use in a user authentication system
US10045150B2 (en) 2015-03-30 2018-08-07 Afero, Inc. System and method for accurately sensing user location in an IoT system
US9922186B1 (en) * 2015-03-30 2018-03-20 Dp Technologies, Inc. Wearable device for improved safety
US10331459B2 (en) * 2015-03-30 2019-06-25 Sony Corporation Apparatus and method
BR102015014422B1 (pt) * 2015-06-17 2024-01-23 Samsung Eletrônica Da Amazônia Ltda Método para comunicação entre dispositivos eletrônicos através da interação de usuários com objetos
US9729528B2 (en) 2015-07-03 2017-08-08 Afero, Inc. Apparatus and method for establishing secure communication channels in an internet of things (IOT) system
US10716059B2 (en) * 2015-07-16 2020-07-14 Apple Inc. Intelligent PLMN selection for link budget limited wireless devices
US9930598B2 (en) 2015-08-21 2018-03-27 Samsung Electronics Co., Ltd. Method and apparatus for offload operation of the idle mode in a cellular device
US10028225B2 (en) * 2015-08-26 2018-07-17 International Business Machines Corporation Efficient usage of internet services on mobile devices
US10564794B2 (en) * 2015-09-15 2020-02-18 Xerox Corporation Method and system for document management considering location, time and social context
US10250403B2 (en) 2015-11-23 2019-04-02 International Business Machines Corporation Dynamic control of smart home using wearable device
WO2017099520A1 (ko) * 2015-12-10 2017-06-15 삼성전자 주식회사 링크된 디바이스들에 대한 신호 송수신을 위한 방법 및 장치
US10178530B2 (en) * 2015-12-14 2019-01-08 Afero, Inc. System and method for performing asset and crowd tracking in an IoT system
US10592700B2 (en) * 2016-01-11 2020-03-17 The Adt Security Corporation Securing electronic property from unauthorized use
US9948398B2 (en) 2016-03-18 2018-04-17 Orion Labs Image-acquisition-based linking for wearable group communication device
DE102016210351A1 (de) * 2016-06-10 2017-12-14 Continental Teves Ag & Co. Ohg Verfahren zum Koppeln eines Mobilfunkendgeräts und zum Überwachen einer Kopplung
JP6657025B2 (ja) * 2016-06-17 2020-03-04 シャープ株式会社 操作者推定システム
DE102016211244B4 (de) * 2016-06-23 2018-01-18 Kuka Roboter Gmbh Roboter-Bedienhandgerätverbund mit einem Grundsteuerungs-Lagesensor
US11256828B1 (en) * 2016-07-05 2022-02-22 Wells Fargo Bank, N.A. Method and apparatus for controlling IoT devices by agent device
US10856142B2 (en) 2016-07-14 2020-12-01 Huawei Technologies Co., Ltd. Method and device for performing communication by using virtual subscriber identity module
CN107644189B (zh) * 2016-07-20 2021-02-02 腾讯科技（深圳）有限公司 一种生物特征识别的方法及装置
CN106211159B (zh) * 2016-07-29 2019-12-27 北京小米移动软件有限公司 基于蓝牙的身份识别方法及装置
US10650621B1 (en) 2016-09-13 2020-05-12 Iocurrents, Inc. Interfacing with a vehicular controller area network
CN113068165B (zh) * 2016-09-22 2022-04-12 华为技术有限公司 一种功能资源的配置方法及设备
KR20180039821A (ko) * 2016-10-11 2018-04-19 삼성전자주식회사 모니터링 시스템 제어 방법 및 이를 지원하는 전자 장치
WO2018072830A1 (en) * 2016-10-20 2018-04-26 Sonova Ag Wireless hearing device comprising split pairing tables
US10528725B2 (en) 2016-11-04 2020-01-07 Microsoft Technology Licensing, Llc IoT security service
US10972456B2 (en) 2016-11-04 2021-04-06 Microsoft Technology Licensing, Llc IoT device authentication
CN106597893A (zh) * 2016-12-12 2017-04-26 重庆笨瓜科技有限公司 一种分辨率为240*240的手表屏幕
FR3060916A1 (fr) * 2016-12-20 2018-06-22 Orange Automatisation des echanges entre objets communicants
US10916243B2 (en) * 2016-12-27 2021-02-09 Amazon Technologies, Inc. Messaging from a shared device
US10325112B2 (en) * 2016-12-29 2019-06-18 T-Mobile Usa, Inc. Privacy breach detection
EP3571829B1 (en) * 2017-01-30 2022-03-02 Samsung Electronics Co., Ltd. Apparatus and method for managing operations for providing services automatically
US10868857B2 (en) 2017-04-21 2020-12-15 Johnson Controls Technology Company Building management system with distributed data collection and gateway services
US11665758B2 (en) 2017-05-01 2023-05-30 Axon Enterprise, Inc. Systems and methods for dynamic pairing of electronic devices
US10912132B2 (en) * 2017-05-01 2021-02-02 Axon Enterprise, Inc. Systems and methods for dynamic pairing of electronic devices
US20180322273A1 (en) * 2017-05-04 2018-11-08 GM Global Technology Operations LLC Method and apparatus for limited starting authorization
US10333810B2 (en) 2017-06-09 2019-06-25 Johnson Controls Technology Company Control system with asynchronous wireless data transmission
US10739028B2 (en) * 2017-06-09 2020-08-11 Johnson Controls Technology Company Thermostat with efficient wireless data transmission
US11751260B2 (en) * 2017-06-24 2023-09-05 Kaha Pte. Ltd. Apparatus and method of identifying for pairing one or more devices with a master device
JP7086541B2 (ja) * 2017-08-09 2022-06-20 オムロンヘルスケア株式会社 データ受信装置、データ送信装置およびデータ伝送システム
WO2019036241A1 (en) * 2017-08-14 2019-02-21 Carrier Corporation USING A USER PREFERENCE IN REMOTE APPLICATIONS
US20190057189A1 (en) * 2017-08-17 2019-02-21 Innovative World Solutions, LLC Alert and Response Integration System, Device, and Process
CN107645548A (zh) * 2017-09-13 2018-01-30 广东乐心医疗电子股份有限公司 一种数据的处理方法、设备服务器以及公用设备
US10912146B2 (en) 2017-09-22 2021-02-02 Qualcomm Incorporated Performing a reliable broadcast to a plurality of nodes
US11044764B2 (en) * 2017-10-31 2021-06-22 Ayla Networks, Inc. Roaming of a device between stationary devices and mobile devices
US10455633B2 (en) 2017-11-14 2019-10-22 Knowmadics, Inc. Wireless communication system and method for monitoring and alerting a broken pairing between electronic devices
US20190208051A1 (en) * 2017-12-29 2019-07-04 Motorola Mobility Llc Context detection with accelerated ai training and adaptive device engagement
KR102440088B1 (ko) * 2018-04-20 2022-09-05 삼성전자 주식회사 근거리 통신을 이용하여 디바이스들을 페어링하는 방법 및 이를 사용하는 전자 장치
CN108629167B (zh) * 2018-05-09 2020-10-27 西安交通大学 一种结合可穿戴设备的多智能设备身份认证方法
TWI697843B (zh) * 2018-06-08 2020-07-01 智能動感有限公司 識別計時系統及其方法
US20200014591A1 (en) * 2018-07-06 2020-01-09 Hitachi, Ltd. Method and system of device deployment integrating with automatic configuration and asset management
CN109120993B (zh) * 2018-09-30 2021-12-03 Tcl通力电子（惠州）有限公司 语音识别方法、智能终端、语音识别系统及可读存储介质
US10959092B2 (en) 2018-10-16 2021-03-23 Aeris Communications, Inc. Method and system for pairing wireless mobile device with IoT device
US20200126108A1 (en) * 2018-10-18 2020-04-23 Muhammad Bassam Adil Khan Earn with activity monitored by wearable smart devices
CN111294729A (zh) * 2018-12-07 2020-06-16 中国移动通信集团终端有限公司 移动终端的网络切换方法、装置、设备及介质
KR102623349B1 (ko) * 2019-04-05 2024-01-11 삼성전자 주식회사 빔을 이용하여 외부 장치와 페어링 하는 방법 및 그를 위한 전자 장치
CN110139270B (zh) * 2019-04-10 2023-05-09 努比亚技术有限公司 可穿戴设备配对方法、可穿戴设备及计算机可读存储介质
US10880382B2 (en) * 2019-04-18 2020-12-29 T-Mobile Usa, Inc. Configuring meaning and state conditions for paired IoT devices
US11942989B2 (en) * 2020-04-01 2024-03-26 Google Llc Communication methods and systems
KR20220007445A (ko) * 2020-07-10 2022-01-18 삼성전자주식회사 증강 현실 장치 및 증강 현실 시스템
CN111953750B (zh) * 2020-07-29 2023-01-31 江苏人先医疗科技有限公司 一种医疗器械的配对方法、平台以及服务器和网关设备
US20220086929A1 (en) * 2020-09-16 2022-03-17 Ford Global Technologies, Llc Passenger identifier seat access
CN112333189B (zh) * 2020-11-06 2021-07-30 北京木铭春天文化传媒有限公司 基于物联网通信和直播平台的数据处理方法及云计算中心
US11589407B2 (en) 2021-06-06 2023-02-21 International Business Machines Corporation Dynamically grouping communicatively connected devices based on device location and tracked motion
US11785012B2 (en) 2021-06-07 2023-10-10 Bank Of America Corporation Data processing for internet of things (IoT) devices based on recorded user behavior
CN113505157B (zh) * 2021-07-08 2023-10-20 深圳市研强物联技术有限公司 一种基于IoT云的可穿戴设备配对方法及系统
CN114363452B (zh) * 2021-12-31 2023-07-28 湖南工学院 基于体感交互的智能手机防盗与追踪的方法
WO2023164067A1 (en) * 2022-02-25 2023-08-31 Stryker Corporation Communication system for patient support apparatuses and temperature management devices
CN116033431B (zh) * 2022-08-18 2023-10-31 荣耀终端有限公司 穿戴设备的连接方法及装置
CN115880113A (zh) * 2022-11-24 2023-03-31 浙江省通信产业服务有限公司 一种基于智慧乡村综合治理的数字化管理系统及管理方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110167262A1 (en) * 2010-01-04 2011-07-07 Pillar Ventures, Llc Identification and authorization of communication devices
US20140089672A1 (en) * 2012-09-25 2014-03-27 Aliphcom Wearable device and method to generate biometric identifier for authentication using near-field communications
US20140244710A1 (en) * 2013-02-25 2014-08-28 Qualcomm Incorporated Context aware actions among heterogeneous internet of things (iot) devices
US20140279528A1 (en) * 2013-03-15 2014-09-18 Motorola Mobility Llc Wearable Authentication Device
US20140329497A1 (en) * 2013-05-04 2014-11-06 Ameya M Sanzgiri Smartdevices Enabled Secure Access to Multiple Entities (SESAME)

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8099761B2 (en) * 2008-08-14 2012-01-17 Microsoft Corporation Protocol for device to station association
US20120317024A1 (en) * 2011-06-10 2012-12-13 Aliphcom Wearable device data security
AU2013208080A1 (en) * 2012-01-09 2014-07-24 Imation Corp. Wireless audio player and speaker system
US20140082227A1 (en) * 2012-04-18 2014-03-20 Barco Nv Electronic tool and methods for meetings
US20140068725A1 (en) * 2012-08-31 2014-03-06 Apple Inc. Wireless Pairing and Communication Between Devices Using Biometric Data
JPWO2014147713A1 (ja) * 2013-03-18 2017-02-16 株式会社東芝 電子機器および認証制御方法
GB201317294D0 (en) * 2013-09-30 2013-11-13 Microsoft Corp Device pairing

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110167262A1 (en) * 2010-01-04 2011-07-07 Pillar Ventures, Llc Identification and authorization of communication devices
US20140089672A1 (en) * 2012-09-25 2014-03-27 Aliphcom Wearable device and method to generate biometric identifier for authentication using near-field communications
US20140244710A1 (en) * 2013-02-25 2014-08-28 Qualcomm Incorporated Context aware actions among heterogeneous internet of things (iot) devices
US20140279528A1 (en) * 2013-03-15 2014-09-18 Motorola Mobility Llc Wearable Authentication Device
US20140329497A1 (en) * 2013-05-04 2014-11-06 Ameya M Sanzgiri Smartdevices Enabled Secure Access to Multiple Entities (SESAME)

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3225073A4 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10697811B2 (en) 2016-10-31 2020-06-30 Nokia Technologies Oy Method, apparatus and computer program product for providing sensor data collection and sensor configuration
US11585685B2 (en) 2016-10-31 2023-02-21 Nokia Technologies Oy Method, apparatus and computer program product for providing sensor data collection and sensor configuration
CN108174015A (zh) * 2017-11-27 2018-06-15 拉卡拉支付股份有限公司 功耗控制方法、装置、可穿戴设备及计算机可读存储介质
CN108174015B (zh) * 2017-11-27 2019-03-22 拉卡拉支付股份有限公司 功耗控制方法、装置、可穿戴设备及计算机可读存储介质
CN112153633A (zh) * 2019-06-29 2020-12-29 华为技术有限公司 一种发送、接收能力信息的方法及设备

Also Published As

Publication number Publication date
CN205179369U (zh) 2016-04-20
EP3225073A1 (en) 2017-10-04
US20160150350A1 (en) 2016-05-26
CN106211022A (zh) 2016-12-07
EP3225073A4 (en) 2017-11-01

Similar Documents

Publication Publication Date Title
WO2016085214A1 (en) Method and apparatus for pairing a wearable device and a smart device
WO2021000808A1 (zh) 设备控制方法和设备
WO2020041952A1 (zh) 一种基于快递消息控制快递柜的方法及电子设备
US20200082690A1 (en) Doorbell camera package detection
CN112449328B (zh) 一种蓝牙搜索方法、系统及相关装置
US9900757B2 (en) Wearable device-based information transfer method and related device
CN104765990B (zh) 智能设备管理账户的设置方法及装置
US10028112B2 (en) Event triggered messaging
WO2015126091A1 (en) Controlling input/output devices
US20130132572A1 (en) System and Method for Monitoring Outbreak of Contagious Diseases
JP2016519866A (ja) ネットワーク化されたコンピューティングのためのポータブル・プラットフォーム
CN109074443A (zh) 一种解锁方法及装置
US9900921B2 (en) Communication control method, electronic device, and storage medium
US20170134698A1 (en) Video composite techniques
US10515224B2 (en) Method, device and storage medium for printing information
WO2020124322A1 (zh) 网络注册的方法及装置
US9990832B2 (en) Occupancy detection by social media
WO2015080437A1 (en) Electronic device and method for providing data service in electronic device
CN113449273A (zh) 解锁方法、移动终端及存储介质
US11363017B2 (en) Smart home network security through blockchain
CN105634928B (zh) 基于可穿戴设备的社交提醒方法和装置
WO2023045928A1 (zh) 设备控制方法、中枢设备及装置
CN106161514A (zh) 信息处理方法及装置
CN108595977A (zh) 用户模式控制方法和装置、可读存储介质、终端
CN116340913A (zh) 登录方法、电子设备及计算机可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15862185

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015862185

Country of ref document: EP