WO2023043073A1 - 복수의 사물 인터넷 장치들을 제어하기 위한 웨어러블 전자 장치, 그 동작 방법 및 저장 매체 - Google Patents
복수의 사물 인터넷 장치들을 제어하기 위한 웨어러블 전자 장치, 그 동작 방법 및 저장 매체 Download PDFInfo
- Publication number
- WO2023043073A1 WO2023043073A1 PCT/KR2022/012548 KR2022012548W WO2023043073A1 WO 2023043073 A1 WO2023043073 A1 WO 2023043073A1 KR 2022012548 W KR2022012548 W KR 2022012548W WO 2023043073 A1 WO2023043073 A1 WO 2023043073A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- electronic device
- iot
- wearable electronic
- present disclosure
- iot devices
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims description 43
- 238000003860 storage Methods 0.000 title claims description 15
- 238000004891 communication Methods 0.000 claims abstract description 129
- 230000006870 function Effects 0.000 claims description 144
- 230000004044 response Effects 0.000 claims description 26
- 238000013507 mapping Methods 0.000 claims description 14
- 238000010586 diagram Methods 0.000 description 21
- 238000005516 engineering process Methods 0.000 description 12
- 238000012545 processing Methods 0.000 description 10
- 238000013528 artificial neural network Methods 0.000 description 8
- 230000033001 locomotion Effects 0.000 description 6
- 238000013473 artificial intelligence Methods 0.000 description 4
- 238000004590 computer program Methods 0.000 description 4
- 230000001360 synchronised effect Effects 0.000 description 4
- 241001122767 Theaceae Species 0.000 description 3
- 230000001133 acceleration Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000013527 convolutional neural network Methods 0.000 description 2
- 230000007613 environmental effect Effects 0.000 description 2
- 230000036541 health Effects 0.000 description 2
- 238000009434 installation Methods 0.000 description 2
- 238000010801 machine learning Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000011017 operating method Methods 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000000306 recurrent effect Effects 0.000 description 2
- 230000002457 bidirectional effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000003749 cleanliness Effects 0.000 description 1
- 239000004020 conductor Substances 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 239000000446 fuel Substances 0.000 description 1
- 230000001939 inductive effect Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000003155 kinesthetic effect Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000001537 neural effect Effects 0.000 description 1
- 230000002787 reinforcement Effects 0.000 description 1
- 230000005236 sound signal Effects 0.000 description 1
- 230000000638 stimulation Effects 0.000 description 1
- 239000000758 substrate Substances 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/16—Constructional details or arrangements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
- G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
- G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
-
- 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]
-
- 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
- H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
Definitions
- the present disclosure relates to a wearable electronic device for controlling a plurality of IoT devices, an operating method thereof, and a storage medium.
- the present disclosure detects a user environment in advance in a wearable electronic device, grasps an operating state of a plurality of external devices, and efficiently configures a plurality of Internet of Things devices based on the identified operating state and the current user environment. It relates to a wearable electronic device for controlling, an operation method thereof, and a storage medium.
- IoT Internet of Things
- Such IoT is used in various fields such as smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliance, or advanced medical service through the convergence and combination of existing IT technology and various industries.
- IoT devices can be used to provide various services based on the Internet of Things.
- An electronic device eg, a smart phone
- an electronic device such as a smart phone may display various contents such as an execution screen of an application for management of IoT devices or an icon.
- an application for management of IoT devices or an icon.
- a wearable electronic device eg, smart watch
- an aspect of the present disclosure is to address at least the problems and/or disadvantages noted above and provide the advantages described below. Therefore, an aspect of the present disclosure is to detect a user environment in advance in a wearable electronic device, determine an operating state of a plurality of external devices, and efficiently operate a plurality of Internet of Things based on the identified operating state and the current user environment. It is intended to provide a wearable electronic device for controlling devices, an operation method thereof, and a storage medium.
- a wearable electronic device includes a housing formed to be worn on the body, at least one sensor, a communication module, a display, and at least one processor operatively connected to the at least one sensor, the communication module, and the display, wherein the at least one One processor obtains state information related to a plurality of IoT devices from an electronic device connected to the plurality of IoT devices through wireless communication, obtains sensor data using the at least one sensor, and obtains sensor data using the sensor. Based on data and state information related to the plurality of IoT devices, a candidate function that can be provided by at least one IoT device among the plurality of IoT devices is identified, and provided by the at least one IoT device. Information on possible candidate functions may be set to be displayed on the display.
- a method for controlling a plurality of IoT devices in a wearable electronic device may include an operation of obtaining state information related to a plurality of IoT devices from an electronic device connected to the plurality of IoT devices through wireless communication, an operation of acquiring sensor data using at least one sensor, and the sensor. Identifying a candidate function that can be provided by at least one IoT device among the plurality of IoT devices based on data and state information related to the plurality of IoT devices, and in the at least one IoT device An operation of displaying information on candidate functions that can be provided may be included.
- a non-volatile storage medium storing commands set to cause a wearable electronic device to perform at least one operation.
- the at least one operation may include obtaining status information related to a plurality of IoT devices from an electronic device connected to the plurality of IoT devices through wireless communication. , Obtaining sensor data using at least one sensor, based on the sensor data and state information related to the plurality of IoT devices, in at least one IoT device among the plurality of IoT devices. It may include an operation of identifying a candidate function that can be provided and an operation of displaying information on a candidate function that can be provided by the at least one IoT device.
- a wearable electronic device detects a user environment in advance, identifies an operating state of a plurality of external devices, and efficiently and easily determines a plurality of external devices based on the identified operating state and the current user environment. of external devices can be controlled.
- a customized UI (user interface) is provided based on user-related sensor data collected from a wearable electronic device and status information on a plurality of external devices, and notification recommendations are provided. Detailed control is possible, providing an improved user experience to the user.
- FIG. 1 is a block diagram of an electronic device in a network environment according to an embodiment of the present disclosure.
- FIG. 2 is a diagram illustrating a system configuration in an IoT environment according to an embodiment of the present disclosure.
- FIG. 3 is an internal block diagram of a wearable electronic device according to an embodiment of the present disclosure.
- FIG. 4 is a flowchart of an operation in a wearable electronic device for controlling IoT devices according to an embodiment of the present disclosure.
- FIG. 5 is a signal flowchart schematically illustrating a procedure for controlling IoT devices in a wearable electronic device according to an embodiment of the present disclosure.
- FIG. 6 is a diagram schematically illustrating a UI in an electronic device and a customized UI in a wearable electronic device according to an embodiment of the present disclosure.
- FIG. 7 is a diagram schematically illustrating a wearable electronic device related to control of IoT devices and internal operating components in the electronic device according to an embodiment of the present disclosure.
- FIG. 8 is a signal flow diagram schematically illustrating a procedure for a wearable electronic device to acquire information related to control of IoT devices from an electronic device according to an embodiment of the present disclosure.
- FIG. 9 is a diagram schematically illustrating a UI for registering a preferred IoT device in an electronic device and a customized UI in a wearable electronic device according to an embodiment of the present disclosure.
- FIG. 10 is a diagram schematically illustrating a customized UI related to a preferred IoT device in a wearable electronic device according to an embodiment of the present disclosure.
- FIG. 11 is a diagram schematically illustrating a customized UI when a location is changed in a wearable electronic device according to an embodiment of the present disclosure.
- FIG. 12 is a screen based on sensor data and state information of a preferred IoT device in a wearable electronic device according to an embodiment of the present disclosure.
- FIG. 13 is a screen based on a use history of a preferred IoT device in a wearable electronic device according to an embodiment of the present disclosure.
- FIG. 14 is a diagram for explaining a communication protocol between a wearable electronic device and an electronic device according to an embodiment of the present disclosure.
- FIG. 1 is a block diagram of an electronic device in a network environment according to an embodiment of the present disclosure.
- an electronic device 101 communicates with an external electronic device 102 through a first network 198 (eg, a short-range wireless communication network) or a second network 199. ) (eg, a long-distance wireless communication network) may communicate with at least one of the electronic device 104 or the server 108 .
- the electronic device 101 may communicate with the electronic device 104 through the server 108 .
- the electronic device 101 includes a processor 120, a memory 130, an input module 150, an audio output module 155, a display module 160, an audio module 170, Sensor module 176, interface 177, connection terminal 178, haptic module 179, camera module 180, power management module 188, battery 189, communication module 190, subscriber identification module (196), or an antenna module (197).
- at least one of these components eg, the connection terminal 178) may be omitted or one or more other components may be added.
- some of these components are one component (eg, display module 160). ) can be incorporated.
- the processor 120 for example, executes software (eg, the program 140) to cause at least one other component (eg, hardware or software component) of the electronic device 101 connected to the processor 120. It can control and perform various data processing or calculations. According to one embodiment of the present disclosure, as at least part of data processing or operation, the processor 120 transfers commands or data received from other components (eg, sensor module 176 or communication module 190) to volatile memory. 132, process the command or data stored in the volatile memory 132, and store the resulting data in the non-volatile memory 134.
- software eg, the program 140
- the processor 120 transfers commands or data received from other components (eg, sensor module 176 or communication module 190) to volatile memory. 132, process the command or data stored in the volatile memory 132, and store the resulting data in the non-volatile memory 134.
- the processor 120 may include a main processor 121 (eg, a central processing unit or an application processor) or a secondary processor 123 (eg, a graphic processing unit, a neural network) that may operate independently or together with the main processor 121 It may include a processing unit (NPU: neural processing unit), an image signal processor, a sensor hub processor, or a communication processor).
- a main processor 121 e.g, a central processing unit or an application processor
- a secondary processor 123 eg, a graphic processing unit, a neural network
- the main processor 121 may include a processing unit (NPU: neural processing unit), an image signal processor, a sensor hub processor, or a communication processor.
- NPU neural processing unit
- the auxiliary processor 123 may use less power than the main processor 121 or be set to be specialized for a designated function.
- the secondary processor 123 may be implemented separately from or as part of the main processor 121 .
- the secondary processor 123 may, for example, take the place of the main processor 121 while the main processor 121 is in an inactive (eg, sleep) state, or the main processor 121 is active (eg, running an application). ) state, together with the main processor 121, at least one of the components of the electronic device 101 (eg, the display module 160, the sensor module 176, or the communication module 190) It is possible to control at least some of the related functions or states.
- the auxiliary processor 123 eg, an image signal processor or a communication processor
- the auxiliary processor 123 is a part of other functionally related components (eg, the camera module 180 or the communication module 190).
- the auxiliary processor 123 may include a hardware structure specialized for processing an artificial intelligence model.
- AI models can be created through machine learning. Such learning may be performed, for example, in the electronic device 101 itself where the artificial intelligence model is performed, or may be performed through a separate server (eg, the server 108).
- the learning algorithm may include, for example, supervised learning, unsupervised learning, semi-supervised learning or reinforcement learning, but in the above example Not limited.
- the artificial intelligence model may include a plurality of artificial neural network layers.
- Artificial neural networks include deep neural networks (DNNs), convolutional neural networks (CNNs), recurrent neural networks (RNNs), restricted boltzmann machines (RBMs), deep belief networks (DBNs), bidirectional recurrent deep neural networks (BRDNNs), It may be one of deep Q-networks or a combination of two or more of the foregoing, but is not limited to the foregoing examples.
- the artificial intelligence model may include, in addition or alternatively, software structures in addition to hardware structures.
- the memory 130 may store various data used by at least one component (eg, the processor 120 or the sensor module 176) of the electronic device 101 .
- the data may include, for example, input data or output data for software (eg, program 140) and commands related thereto.
- the memory 130 may include volatile memory 132 or non-volatile memory 134 .
- the program 140 may be stored as software in the memory 130 and may include, for example, an operating system 142 , middleware 144 , or an application 146 .
- the input module 150 may receive a command or data to be used by a component (eg, the processor 120) of the electronic device 101 from the outside of the electronic device 101 (eg, a user).
- the input module 150 may include, for example, a microphone, a mouse, a keyboard, a key (eg, a button), or a digital pen (eg, a stylus pen).
- the sound output module 155 may output sound signals to the outside of the electronic device 101 .
- the sound output module 155 may include, for example, a speaker or a receiver.
- the speaker can be used for general purposes such as multimedia playback or recording playback.
- a receiver may be used to receive an incoming call. According to one embodiment of the present disclosure, the receiver may be implemented separately from the speaker or as part of it.
- the display module 160 may visually provide information to the outside of the electronic device 101 (eg, a user).
- the display module 160 may include, for example, a display, a hologram device, or a projector and a control circuit for controlling the device.
- the display module 160 may include a touch sensor configured to detect a touch or a pressure sensor configured to measure the intensity of force generated by the touch.
- the audio module 170 may convert sound into an electrical signal or vice versa. According to one embodiment of the present disclosure, the audio module 170 acquires sound through the input module 150, the sound output module 155, or an external electronic device connected directly or wirelessly to the electronic device 101. (eg, the electronic device 102) (eg, sound may be output through a speaker or a headphone).
- the sensor module 176 detects an operating state (eg, power or temperature) of the electronic device 101 or an external environmental state (eg, a user state), and generates an electrical signal or data value corresponding to the detected state. can do.
- the sensor module 176 may include, for example, a gesture sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, It may include a biological sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.
- the interface 177 may support one or more designated protocols that may be used to directly or wirelessly connect the electronic device 101 to an external electronic device (eg, the electronic device 102).
- the interface 177 may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.
- HDMI high definition multimedia interface
- USB universal serial bus
- SD card interface Secure Digital Card interface
- audio interface audio interface
- connection terminal 178 may include a connector through which the electronic device 101 may be physically connected to an external electronic device (eg, the electronic device 102).
- the connection terminal 178 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (eg, a headphone connector).
- the haptic module 179 may convert electrical signals into mechanical stimuli (eg, vibration or motion) or electrical stimuli that a user may perceive through tactile or kinesthetic senses.
- the haptic module 179 may include, for example, a motor, a piezoelectric element, or an electrical stimulation device.
- the camera module 180 may capture still images and moving images. According to one embodiment of the present disclosure, the camera module 180 may include one or more lenses, image sensors, image signal processors, or flashes.
- the power management module 188 may manage power supplied to the electronic device 101 .
- the power management module 188 may be implemented as at least part of a power management integrated circuit (PMIC), for example.
- PMIC power management integrated circuit
- the battery 189 may supply power to at least one component of the electronic device 101 .
- the battery 189 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.
- the communication module 190 is a direct (eg, wired) communication channel or wireless communication between the electronic device 101 and an external electronic device (eg, the external electronic device 102, the external electronic device 104, or the server 108). Establishing a channel and performing communication through the established communication channel can be supported.
- the communication module 190 may include one or more communication processors that operate independently of the processor 120 (eg, an application processor) and support direct (eg, wired) communication or wireless communication.
- the communication module 190 is a wireless communication module 192 (eg, a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module (194 ) (eg, a local area network (LAN) communication module or a power line communication module).
- a wireless communication module 192 eg, a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module
- GNSS global navigation satellite system
- wired communication module (194 ) eg, a local area network (LAN) communication module or a power line communication module.
- a corresponding communication module is a first network 198 (eg, a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network 199 (eg, legacy It may communicate with the external electronic device 104 through a cellular network, a 5G network, a next-generation communication network, the Internet, or a telecommunications network such as a computer network (eg, a LAN or a WAN).
- a telecommunications network such as a computer network (eg, a LAN or a WAN).
- These various types of communication modules may be integrated as one component (eg, a single chip) or implemented as a plurality of separate components (eg, multiple chips).
- the wireless communication module 192 uses subscriber information (eg, International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module 196 within a communication network such as the first network 198 or the second network 199.
- subscriber information eg, International Mobile Subscriber Identifier (IMSI)
- IMSI International Mobile Subscriber Identifier
- the electronic device 101 may be identified or authenticated.
- the wireless communication module 192 may support a 5G network after a fourth generation (4G) network and a next-generation communication technology, for example, a new radio access technology (NR access technology).
- NR access technologies include high-speed transmission of high-capacity data (enhanced mobile broadband (eMBB)), minimization of terminal power and access of multiple terminals (massive machine type communications (mMTC)), or high reliability and low latency (ultra-reliable and low latency (URLLC)). -latency communications)) can be supported.
- the wireless communication module 192 may support a high frequency band (eg, mmWave band) to achieve a high data rate, for example.
- a high frequency band eg, mmWave band
- the wireless communication module 192 uses various technologies for securing performance in a high frequency band, such as beamforming, massive multiple-input and multiple-output (MIMO), and full-dimensional multiplexing. Technologies such as input/output (FD-MIMO: full dimensional MIMO), array antenna, analog beam-forming, or large scale antenna may be supported.
- the wireless communication module 192 may support various requirements defined for the electronic device 101, an external electronic device (eg, the external electronic device 104), or a network system (eg, the second network 199).
- the wireless communication module 192 is a peak data rate for realizing eMBB (eg, 20 Gbps or more), a loss coverage for realizing mMTC (eg, 164 dB or less), or U-U- for realizing URLLC.
- Plane latency eg, downlink (DL) and uplink (UL) 0.5 ms or less, or round trip 1 ms or less
- DL downlink
- UL uplink
- round trip 1 ms or less can be supported.
- the antenna module 197 may transmit or receive signals or power to the outside (eg, an external electronic device).
- the antenna module 197 may include an antenna including a radiator formed of a conductor or a conductive pattern formed on a substrate (eg, PCB).
- the antenna module 197 may include a plurality of antennas (eg, an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network such as the first network 198 or the second network 199 is selected from the plurality of antennas by the communication module 190, for example. can be chosen A signal or power may be transmitted or received between the communication module 190 and an external electronic device through the selected at least one antenna.
- other components eg, a radio frequency integrated circuit (RFIC)
- RFIC radio frequency integrated circuit
- the antenna module 197 may form a mmWave antenna module.
- the mmWave antenna module may be disposed on or adjacent to a printed circuit board, a first surface (eg, a lower surface) of the printed circuit board, and support a designated high frequency band (eg, mmWave band).
- a RFIC, and a plurality of antennas eg, an array antenna
- a second surface eg, a top surface or a side surface
- peripheral devices eg, a bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)
- signal e.g. commands or data
- commands or data may be transmitted or received between the electronic device 101 and the external electronic device 104 through the server 108 connected to the second network 199 .
- Each of the external electronic devices 102 or 104 may be the same as or different from the electronic device 101 .
- all or part of operations executed in the electronic device 101 may be executed in one or more external electronic devices among the external electronic devices 102 , 104 , or 108 .
- the electronic device 101 when the electronic device 101 needs to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device 101 instead of executing the function or service by itself.
- one or more external electronic devices may be requested to perform the function or at least part of the service.
- One or more external electronic devices receiving the request may execute at least a part of the requested function or service or an additional function or service related to the request, and deliver the execution result to the electronic device 101 .
- the electronic device 101 may provide the result as at least part of a response to the request as it is or additionally processed.
- cloud computing distributed computing, mobile edge computing (MEC), or client-server computing technology may be used.
- the electronic device 101 may provide an ultra-low latency service using, for example, distributed computing or mobile edge computing.
- the external electronic device 104 may include an internet of things (IoT) device.
- Server 108 may be an intelligent server using machine learning and/or neural networks.
- the external electronic device 104 or server 108 may be included in the second network 199 .
- the electronic device 101 may be applied to intelligent services (eg, smart home, smart city, smart car, or health care) based on 5G communication technology and IoT-related technology.
- FIG. 2 is a diagram illustrating a configuration of a system in an IoT environment according to an embodiment of the present disclosure.
- the electronic device 201 in FIG. 2 may be the electronic device 101 in FIG. 1 .
- a system 200 in an IoT environment includes an electronic device 201, a wearable electronic device 202, a hub 210, a plurality of external devices 220, and/or an IoT server 240.
- the system 200 may further include servers such as a cloud server and an application market server in addition to the IoT server 240 .
- the hub 210 may include a communication unit and may receive data from a plurality of external devices 220 through the communication unit.
- the hub 210 may be referred to as a hub device, a control device, an access point (AP), a coordinator, or a server.
- the hub 210 may communicate with the plurality of external devices 220 and the electronic device 201 using the first type of communication or the second type of communication.
- the hub 210 communicates with the plurality of external devices 220 using a first type of communication and communicates with the electronic device 201 using a second type of communication. communication can be performed.
- the communication of the first method and the communication of the second method may be different from each other or may be the same, and if they are different, the communication of the first method may consume relatively less power than the communication of the second method.
- Zigbee communication is used for communication between the plurality of external devices 220 and the hub 210
- Wi-Fi communication is used for communication between the electronic device 201 and the hub 210.
- the hub 210 may perform communication with at least some of the plurality of external devices 220 using a third type of communication instead of the first type of communication.
- Zigbee communication is used for communication between at least some of the plurality of external devices 220 and the hub 210, and communication between some of the plurality of external devices 220 and the hub 210 is used.
- Z-Wave communication may be used.
- communication with the hub 210 may be possible with low power.
- power efficiency is higher than that of ZigBee. this could be higher.
- the hub 210 may collect data received from a plurality of external devices 220 in the home using ZigBee or G-Wave communication, and the collected data may be sent to the electronic device 201 in the home or remotely. It can be transmitted to a server (eg, IoT server 240) in .
- a server eg, IoT server 240
- the hub 210 may be formed as a separate device or embedded in an electronic device such as a TV.
- the plurality of external devices 220 may be located in various spaces within a home and may be communicatively connected to the electronic device 201 through the hub 210 .
- the plurality of external devices 220 may include various types of electronic devices or digital devices that operate based on Internet of Things (IoT) technology such as a smart home.
- IoT Internet of Things
- the plurality of external devices 220 may be referred to as IoT devices or IoT devices.
- the plurality of external devices 220 may include a sensor or switch for sensing the surrounding environment.
- a device that cannot perform direct communication may be communicatively connected to the electronic device 201 through another external device connected to the electronic device 201.
- the plurality of external devices 220 according to the embodiment disclosed in this document are not limited to the above types of devices, and may include all devices capable of communicating with the electronic device 201 .
- the electronic device 201 may be capable of 1:N communication with the plurality of external devices 220 .
- the plurality of external devices 220 may be operated by user manipulation or automatically when a given condition is satisfied. For example, when an event occurs, the plurality of external devices 220 may output data (or signals) to the hub 210 in response to the occurrence of the event.
- the data may include device identification information (eg, device ID), and the device unique ID may be set during device manufacturing.
- the external devices 220 may include a communication module and output the data to the hub 210 through the communication module.
- at least some of the plurality of external devices 220 may be connected to the Internet where the IoT server 240 exists through a Wi-Fi connection mainly based on a Wi-Fi method. .
- the plurality of external devices 220 connect to the hub 210 by establishing a connection with the electronic device 201 and receiving information about the hub 210 to be directly connected through the established connection.
- the electronic device 201 is a device for managing a plurality of external devices 220, searches for a plurality of external devices 220 in the vicinity, and searches for each of the plurality of external devices ( 220) and communication can be established. Accordingly, the electronic device 201 may receive data from the plurality of external devices 220 and display a screen of the plurality of external devices 220 in response to the received data.
- the electronic device 201 may be a user device (eg, a smart phone).
- the electronic device 201 is an IoT-based application (hereinafter referred to as IoT) for controlling a plurality of external devices 220 disposed in a plurality of places, for example, separated spaces of an indoor environment.
- IoT management app is executed, a user interface (UI) related to the executed application may be displayed.
- the electronic device 201 uses the IoT management app to set up a first group of external devices (eg, lighting 1, a refrigerator) disposed in the first space (eg, the user's house). , TV 1, or Bluetooth speaker) and external devices (eg, lighting 2, air conditioner, TV 2, or air purifier) of the second group disposed in the second space (eg, the user's office).
- a first group of external devices eg, lighting 1, a refrigerator
- TV 1, or Bluetooth speaker external devices
- external devices eg, lighting 2, air conditioner, TV 2, or air purifier
- the wearable electronic device 202 may be communicatively connected to the electronic device 201, and the wearable electronic device 202 may also install the IoT management app.
- the wearable electronic device 202 may share state information about a plurality of external devices 220 managed by the electronic device 201 .
- the state information may include identification information of the plurality of external devices 220, arrangement positions (or places) of each of the plurality of external devices 220, context information, favorites (or It may include at least one of a favorite list, group, device type, executable function information, authority information, or a control method.
- the wearable electronic device 202 may receive all or part of state information about the plurality of external devices 220 from the electronic device 201 .
- the wearable electronic device 202 transmits state information about at least one external device registered as a preferred device group among a plurality of external devices 220 communicatively connected to the electronic device 201 to the electronic device ( 201) can be obtained.
- the preferred device group (or favorite device group) may be a set of IoT devices for operating in a specified mode or scene by grouping IoT-related external devices.
- operation information related to a home, office, music listening mode or scene, or function is defined, and each IoT device (eg, TV, speakers, refrigerators, lights, ).
- the wearable electronic device 202 may obtain sensor data using at least one sensor.
- the wearable electronic device 202 identifies a candidate function that can be provided by at least one external device from among the group using the sensor data and state information related to at least one external device registered in the preferred device group, and displays the candidate function. can do.
- the sensor data may be used to identify a state of the wearable electronic device 202 .
- the wearable electronic device 202 detects at least one of whether the wearable electronic device 202 is worn, a state of a user wearing the wearable electronic device 202, or the environment around the user. In relation to , the state of the wearable electronic device may be identified.
- the wearable electronic device 202 may display candidate functions of at least one controllable external device corresponding to the sensor data in a designated display method.
- the wearable electronic device 202 may guide the user to easily select candidate functions that can be provided using text or graphic objects. In this way, based on the display size of the wearable electronic device 202, candidate functions that can be provided in various visual ways may be displayed.
- FIG. 3 is an internal block diagram of a wearable electronic device according to an embodiment of the present disclosure.
- a wearable electronic device 302 may include a processor 320, a memory 330, a display 360, a sensor 376, and a communication module 390. there is.
- the senor 376 may operate substantially the same as the sensor module 176 of FIG. ), or an external environmental state (eg, user state) may be sensed, and an electrical signal or data value corresponding to the sensed state may be generated.
- an external environmental state eg, user state
- the senor 376 is at least one sensor for detecting an operating state of the wearable electronic device 302, a user state wearing the wearable electronic device 302, and/or a user's surrounding environment. can include
- the senor 376 may include an acceleration sensor or a gyro sensor that detects the motion of the wearable electronic device 302, and also, for example, the wearable electronic device 302 It may include a biosensor that acquires a biosignal related to a user state (eg, exercise state, sleep state).
- a user state eg, exercise state, sleep state
- the senor 376 may include a biosignal detector (not shown) and a biosignal processor (not shown).
- the biosignal detector for detecting a photoplethysmogram (PPG) signal may include a light emitting unit and a light receiving unit. The light emitting unit may output light to the user's skin.
- components included in the biological signal detector for detecting the PPG signal are not limited to the light emitting unit and the light receiving unit.
- Components of the sensor 376 for detecting the PPG signal eg, a light emitting unit, a light receiving unit, and a biosignal processing unit
- a 'PPG sensor' e.g, a light emitting unit, a light receiving unit, and a biosignal processing unit
- the biosignal detector for detecting an electrocardiogram (ECG) signal may include a plurality of electrodes (eg, three or more electrodes).
- the plurality of electrodes may receive biosignals having different electrical physical quantities.
- a component of the sensor 376 for detecting an ECG signal eg, three or more electrodes and a biosignal processor
- the sensor 376 may be implemented in one physical package including an ECG sensor and a PPG sensor.
- sensor 376 may include, for example, a distance sensor or an illuminance sensor, and may obtain sensor data related to the user's surrounding environment, for example.
- sensor 376 may include an air sensor.
- sensor data including temperature information, humidity information, wind information, or air cleanliness information of an air sensor may be obtained.
- the sensor 376 as described above represents only one example of a sensor for obtaining data related to a user wearing the wearable electronic device 302, and the type of sensor may not be limited thereto.
- the memory 330 stores a mapping table in which candidate functions supportable by at least one IoT device are mapped in response to sensor data and state information related to at least one IoT device.
- the wearable electronic device 302 includes a table associating supportable functions for each state of the wearable electronic device 302 identified based on sensor data, for each state of Internet of Things devices, or for each combination thereof. may be stored in the memory 330, and information on candidate functions of the IoT device controllable by the wearable electronic device 302 may be identified from the table.
- the wearable electronic device 302 may obtain information about candidate functions of an IoT device controllable by the wearable electronic device 302 from the IoT server 240 .
- the wearable electronic device 302 may transmit state information of the wearable electronic device 302 based on sensor data to the IoT server 240, and the wearable electronic device 302 is stored by the IoT server 240.
- Information on at least one candidate function of the IoT device identified based on the state information of the IoT server 240 may be obtained.
- the wearable electronic device 302 uses state information of the wearable electronic device 302 based on sensor data instead of obtaining information about the candidate function from the IoT server 240.
- Supportable candidate functions of the IoT device may be directly identified.
- the wearable electronic device 302 may store in the memory 330 a mapping table used to directly identify supportable candidate functions of the IoT device.
- the mapping table may be stored when the wearable electronic device 302 is manufactured or may be provided together when an IoT-based application (hereinafter referred to as IoT management app) is downloaded.
- the mapping table may be provided when the wearable electronic device 302 accesses the IoT server 240 .
- the IoT server may be a cloud server and may be a server that operates an application (eg, Samsung SmartThings application) for managing a plurality of interlocked IoT devices.
- Table 1 below shows an example of a mapping table managed by the wearable electronic device 302 .
- the wearable electronic device 302 may store candidate functions that can be provided by the IoT device based on the relationship between state information and sensor data.
- the wearable electronic device 302 may acquire the state information in Table 1 in various ways.
- the wearable electronic device 302 obtains status information related to IoT devices from the electronic device 301 through a communication connection with the electronic device 301, thereby obtaining the obtained status information and Based on sensor data from the wearable electronic device 302 , candidate functions that can be provided by the IoT device may be identified. According to another embodiment of the present disclosure, the wearable electronic device 302 may directly obtain state information related to the IoT devices from the IoT device or the IoT server 240 .
- the memory 330 may store, in addition to the mapping table, information for grouping IoT devices included in a preferred device group (or favorite device group) to operate in a designated mode or scene.
- the status information related to the IoT devices is not limited to the example in Table 1, and for example, in addition to the operation status of the IoT devices, the location of each IoT device and information about the IoT devices. It may further include identification information and/or scene information in which information instructing at least some of the IoT devices to perform a designated function corresponding to the sensor data is grouped, and the types may be various.
- the processor 320 upon communication connection with the electronic device 301, obtains information on a preferred device group registered by a user in the electronic device 301 and stores it in the memory 330.
- the preferred device group may be one registered in the electronic device 301 through a separate menu for the wearable electronic device 302 by the user.
- the processor 320 may acquire information about some of the preferred device groups registered in the electronic device 301 and store it in the memory 330 . In this case, the preferred device group may be synchronized based on the user account.
- the display 360 may display a user interface related to the IoT management app being executed.
- the display 360 includes sensor data from the sensor 376 and a plurality of Internet of Things provided from an electronic device (eg, the electronic device 201 of FIG. 2 ) through the communication module 390.
- Sensor data from the sensor 376 and a plurality of Internet of Things provided from an electronic device (eg, the electronic device 201 of FIG. 2 ) through the communication module 390.
- Candidate functions that can be provided by at least one IoT device may be displayed based on state information related to the devices.
- the display 360 may simultaneously support input/output functions of data and detect a touch.
- the display 360 may include a touch sensor.
- the display 360 may display information on candidate functions that can be provided by at least one IoT device, receive a touch input for selecting the candidate function, and transmit the information to the processor 320. can be forwarded to For example, the user can check the functions that can be provided by the IoT management app without executing the IoT management app, and the IoT management app can be executed for detailed control of the IoT device according to a user input for selecting a candidate function.
- the information on the candidate function that can be provided may include at least one of a name of a function that can be provided, a description of the function that can be provided, and a name of an IoT device that performs the function that can be provided. there is.
- a customized UI may be provided based on user-related sensor data collected by the wearable electronic device 302 and status information on a plurality of IoT devices, and notification recommendations may be provided.
- detailed control can be performed by executing an IoT management app for controlling IoT devices connected to the electronic device 301 according to a user input for selecting it in response to the notification recommendation, thereby providing an improved user experience to the user.
- the communication module 390 may communicate with the electronic device 301 under the control of the processor 320 .
- the communication module 390 uses Zigbee, Z-Wave, Wi-Fi, Bluetooth, Ultra-Wide Band (UWB), and Wireress. Communication may be performed using at least one communication method among communication methods including USB or Near Field Communication (NFC).
- NFC Near Field Communication
- the communication module 390 may communicate with the electronic device 301 through short-range communication such as Bluetooth or BLE. If the user wearing the wearable electronic device 302 moves out of the short-range communication connectable radius of the electronic device 301, a situation in which it is difficult to find IoT devices connectable through the electronic device 301 may occur.
- the communication module 390 may perform communication with the electronic device 301 based on a network communication method such as long term evolution (LTE). For example, when a user leaves the electronic device 301 at home and wears the wearable electronic device 302 while carrying a personal Internet of Things device (or IoT device) while going out, the wearable electronic device 302 ) and the personal IoT device may not be searched for in the wearable electronic device 302 even if the personal IoT device is located in the immediate vicinity.
- LTE long term evolution
- the communication module 390 performs a short-range communication connection between the electronic device 301 and the wearable electronic device 302 under the control of the processor 320, in the wearable electronic device 302.
- a device to device (D2D) search operation for directly finding IoT devices in the vicinity may be performed.
- the wearable electronic device 302 may search for nearby IoT devices and establish communication with at least some of the searched IoT devices.
- D2D search may be preferentially performed in the electronic device 301 instead of the wearable electronic device 302 .
- the processor 320 may drive an application (eg, an IoT management app) that manages at least some of a plurality of IoT devices.
- the IoT management app checks the communication state with the IoT devices through connection with the electronic device 301 or the connection with the IoT server 240, and outputs a user interface for controlling at least one IoT device.
- the IoT management app may be downloaded through an application market server (eg, an app store) and installed in the wearable electronic device 302 or the electronic device 301 .
- the IoT management app may support a background service, and information about IoT devices registered by the user and information about the electronic device 301 may be transmitted from the IoT server 240 when the application is executed. It may be obtained and stored in the memory 330 .
- the processor 320 may manage various IoT devices disposed in a plurality of places using an IoT management app substantially the same as the electronic device 301 .
- the IoT management app provides a background service even when the IoT management app is not running, a candidate function that can be provided by at least one external device among external devices connected to the electronic device 301 is notified when the specified condition is satisfied. It can be output (or displayed) in the form.
- the processor 320 may identify candidate functions that can be provided in relation to the state of the wearable electronic device 302 (eg, exercise state, sleep state, worn state, ...) and notify the user of them. Accordingly, the notification function for the candidate function may play a role of inducing the user to select a function of the IoT device controllable through the wearable electronic device 302 .
- the wearable electronic device 302 may display a list including objects representing candidate functions that can be provided by the IoT device.
- the wearable electronic device 302 responds to a user input for selecting a specific object included in the list, and provides detailed information (eg, name of the available function, information on the available function) corresponding to the specific object.
- detailed information eg, name of the available function, information on the available function
- the processor 320 in response to obtaining a user selection for a candidate function, transmits information related to execution of the specific function to the electronic device 301 through the communication module 390.
- the information related to the execution of the specific function may correspond to a command for controlling an operation of an IoT device.
- the IoT device has the same function, the form of a command for controlling it may be different.
- the command to power on is defined as '/sec/tv/power'
- the command to power on is '/power/ can be defined as 'switch'.
- the processor 320 may generate a command for controlling the operation of the IoT device based on the metadata format commonly defined with the electronic device 301 .
- the processor 320 may transmit a command generated in a common format (or details) such as '/capability/power' to the electronic device 301 . Therefore, when the electronic device 301 transmits the command to the corresponding IoT device, it may convert the command into a format supported by the IoT device and then transmit the command in the converted format.
- the wearable electronic device 302 generates a command based on a common format and transmits it to the electronic device 301, so that even if the format supported by the IoT device is changed in the future, the format is updated only in the electronic device 301, thereby providing wearable Processing speed in the electronic device 302 may be guaranteed.
- the wearable electronic device 302 includes a housing formed to be worn on the body, at least one sensor 376, a communication module 390, a display 360, and the at least one sensor 376. ), and at least one processor 320 operatively connected to the communication module 390 and the display 360, wherein the at least one processor 320 is wirelessly connected to a plurality of IoT devices.
- state information related to the plurality of IoT devices is acquired, sensor data is obtained using the at least one sensor 376, and the sensor data and the plurality of IoT devices Based on state information related to , a candidate function that can be provided by at least one IoT device among the plurality of IoT devices is identified, and information of a candidate function that can be provided by the at least one IoT device is displayed on the display ( 360) can be set to be displayed on.
- the information on the candidate function that can be provided may include at least one of a function name, a description of the function, and a name of an IoT device that performs the function.
- the at least one processor 320 refers to a mapping table in which functions that can be provided corresponding to sensor data and state information of at least one IoT device are mapped, and the mapping table Based on the function, a candidate function that can be provided by the at least one IoT device may be configured to be identified.
- the at least one processor 320 when the at least one processor 320 communicates with the electronic device 301 through the communication module 390, the preferred device group in the electronic device 301 It may be configured to acquire state information related to the plurality of registered IoT devices.
- the status information may correspond to a location of each of the plurality of IoT devices, identification information on the plurality of IoT devices, or sensor data of the plurality of IoT devices. At least some of them may include at least one of scene information in which information instructing to perform a designated function is grouped.
- the at least one processor 320 determines the wearing state of the wearable electronic device and the wearing state of the wearable electronic device based on sensor data acquired using the at least one sensor.
- a state of the wearable electronic device may be identified in relation to at least one of a user state and the user's surrounding environment.
- the at least one processor 320 determines the plurality of IoT devices based on the state of the wearable electronic device 302 and the use history of the plurality of IoT devices. Among them, a candidate function that can be provided by the at least one IoT device may be configured to be identified.
- the at least one processor 320 receives a user input for selecting a candidate function that can be provided by the at least one IoT device displayed on the display, and responds to the user input.
- a command for controlling the operation of the at least one IoT device may be transmitted to the electronic device 301 through the communication module.
- the at least one processor 320 determines the at least one object based on a metadata format commonly defined between the electronic device 301 and the wearable electronic device 302.
- a command for controlling an operation of an internet device may be transmitted through the communication module.
- the at least one processor 320 generates an IoT-based application for controlling the plurality of IoT devices connected to the electronic device 301 in response to the user input. can be set to run.
- FIG. 4 is a flowchart 400 of an operation in a wearable electronic device for controlling IoT devices according to an embodiment of the present disclosure.
- the operating method may include operations 405 to 420 .
- Each operation of the operation method of FIG. 4 is a wearable electronic device (eg, the external electronic device 102 of FIG. 1 , the wearable electronic device 202 of FIG. 2 , the wearable electronic device 302 of FIG. 3 ), the wearable electronic device It may be performed by at least one processor (eg, at least one of the processor 320 of FIG. 3).
- at least one of operations 405 to 420 may be omitted, the order of some operations may be changed, or another operation may be added.
- the wearable electronic device 302 connects the plurality of external devices 220 and the plurality of external devices 220 from the electronic device 301 (eg, the electronic device 201 of FIG. 2) connected to the plurality of IoT devices through wireless communication. Relevant status information can be obtained.
- the wearable electronic device 302 communicates with the electronic device 301
- the plurality of external devices 220 registered in the preferred device group of the electronic device 301 State information related to can be obtained.
- the state information corresponds to the arrangement position of each of the plurality of external devices 220, identification information about the plurality of external devices 220, or sensor data. It may include at least one of scene information in which information instructing at least some of the external devices 220 to perform a designated function is grouped.
- the scene refers to a division in which scenarios are easily accessible, and may be referred to as an operation mode or a control mode. Multiple external control modes, for example, frequently used at home (e.g. break mode, sleep mode, ...), frequently used control modes at office (e.g. work mode, meeting mode, tea time mode, ...)
- a mode in which at least some of the devices 220 perform designated functions may be indicated.
- the wearable electronic device 302 may obtain sensor data using at least one sensor 376.
- the wearable electronic device 302 performs an operation in at least one IoT device among the plurality of external devices 220 based on the sensor data and state information related to the plurality of external devices 220.
- Candidate features that can be provided can be identified.
- the wearable electronic device 302 refers to a mapping table in which functions that can be provided corresponding to sensor data and state information of at least one IoT device are mapped, and based on the mapping table, the A candidate function that can be provided by at least one IoT device may be identified.
- the wearable electronic device 302 determines a wearing state of the wearable electronic device 302 and the wearable electronic device 302 based on sensor data obtained using the at least one sensor 376.
- a state of the wearable electronic device 302 may be identified in relation to at least one of a state of the user wearing 302 and the surrounding environment of the user.
- the wearable electronic device 302 determines the plurality of external devices ( 220), candidate functions that can be provided by the at least one IoT device may be identified.
- the wearable electronic device 302 may display information on candidate functions that can be provided by the at least one IoT device.
- the information on the candidate function that can be provided may include at least one of a function name, a description of the function, and a name of an IoT device that performs the function.
- the wearable electronic device 302 may receive a user input for selecting a candidate function that can be provided by the at least one IoT device displayed on the display 360 of the wearable electronic device. there is.
- the wearable electronic device 302 may transmit a command for controlling an operation of the at least one IoT device to the electronic device 301 in response to the user input.
- the wearable electronic device 302 determines the at least one IoT device based on a metadata format commonly defined between the electronic device 301 and the wearable electronic device 302.
- a command for controlling an operation may be generated, and the generated command may be transmitted to the electronic device 301 .
- the electronic device 301 converts the command into a format supportable by the IoT device, and then transmits the command to the corresponding IoT device through the corresponding IoT device or hub 210.
- the electronic device 301 may convert the format into a format supported by each IoT device and transmit the same.
- the wearable electronic device 302 may execute an IoT-based application for controlling the plurality of IoT devices connected to the electronic device 301 in response to the user input. .
- FIG. 5 is a signal flowchart schematically illustrating a procedure for controlling IoT devices in a wearable electronic device according to an embodiment of the present disclosure.
- the interlocking electronic device 301 obtains IoT device information from the IoT server 340 (eg, the IoT server 240 of FIG. 2) in operation 505. can do.
- the electronic device 301 may provide information on the electronic device 301 together with IoT device information.
- the IoT device information may include a current on/off state of the IoT device, an execution history of the IoT device, sensor information of the IoT device, and controllable information of the IoT device.
- the information of the electronic device 301 is information of an IoT device currently connected (or registered) to the electronic device 301, UI information configured in the electronic device 301 for controlling the IoT device, or network connection. It may contain status information.
- the wearable electronic device 302 may display a notification after identifying a controllable candidate function of the IoT device by combining the sensor data. For example, based on the sensor data, the wearable electronic device 302 determines at least one of whether or not the wearable electronic device 302 is worn, a user state wearing the wearable electronic device 302, or the user's surrounding environment. In relation to , the state of the wearable electronic device 302 may be identified. By combining the state information of the wearable electronic device 302 with the IoT device information and the information of the electronic device 301, controllable candidate functions of the IoT device may be identified.
- the wearable electronic device 302 may implement and display a control UI based on the use history.
- the wearable electronic device 302 may refer to the use history of the IoT device when identifying controllable candidate functions of the IoT device. For example, based on the sensor data reflecting the user's situation and the history of use of the IoT device, it is possible to prioritize functions that are frequently used according to the small screen of the wearable electronic device 302 to the user. You can control IoT devices efficiently and easily.
- FIG. 6 is a diagram schematically illustrating a UI in an electronic device and a customized UI in a wearable electronic device according to an embodiment of the present disclosure.
- the electronic device 301 may set a specific function for an IoT device to be controlled according to a user input.
- the electronic device 301 includes names of functions supportable by an IoT device (eg, an air conditioner) (eg, a windless function or a clean function) and an operating state (eg, on/off state of a function). ) may be displayed on the display 600 .
- the electronic device 301 may set a specific function for the IoT device in response to a user input for selecting an item displayed on the display 600 (eg, a supportable function).
- all functions supported by the IoT device may be displayed on the large screen of the electronic device 301 in a list form, but in the case of the wearable electronic device 302, some functions may be displayed due to limitations in screen size.
- the wearable electronic device 302 uses an IoT management app.
- Information related to the items 610 that are frequently used during execution may be provided.
- 6 illustrates a case of providing use history-based items for one IoT device, but may also be applied to a plurality of IoT devices connected to the electronic device 301. Accordingly, on the display 620 of the wearable electronic device 302, frequently used IoT devices and items supported by the IoT devices may be preferentially displayed based on the use history.
- the electronic device 301 has the plurality of IoT devices.
- IoT devices eg, air purifier, home TV, living room TV, light 1, light 2, or light 3
- the electronic device 301 has the plurality of IoT devices.
- items that can be supported by at least some IoT devices based on use history eg, living room TV control, or control of a bundle of lights 1 to 3 may be exposed.
- controllable IoT devices and supportable items may be displayed based on an operating state of at least one IoT device and sensor data from the wearable electronic device 302 .
- controllable IoT device and the supportable IoT device are based not only on the operating state of the at least one IoT device and the sensor data, but also on the history of using the at least one IoT device (eg, usage time zone). items can be displayed.
- FIG. 7 is a diagram schematically illustrating a wearable electronic device related to control of IoT devices and internal operating components in the electronic device according to an embodiment of the present disclosure. A description of each operation component in FIG. 7 will be given with reference to FIG. 8 .
- 8 is a signal flow diagram schematically illustrating a procedure for a wearable electronic device to acquire information related to control of IoT devices from an electronic device according to an embodiment of the present disclosure.
- components for controlling IoT devices include an IoT management app (eg, SmartThings) 702 in a wearable electronic device 302 and IoT management in an electronic device 301 App (eg, SmartThings) 701 may be included.
- IoT management app eg, SmartThings
- IoT management in an electronic device 301 App eg, SmartThings
- the wearable electronic device 302 transmits a request for controlling IoT devices to the electronic device 301 through a communication interface (eg, wearablekit wearable) 732 based on a common library (eg, wearablekit) 736, and transmits a request for controlling the IoT devices. You can receive results.
- the electronic device 301 may mutually communicate with the wearable electronic device 302 through a communication interface (eg, wearablekit mobile) 720 based on a common library (eg, wearablekit) 726 .
- the wearable electronic device 302 may exchange information with the electronic device 301 through a datalayer 738 .
- the core module 710 in the electronic device 301 may manage a database 715 by group or by device to provide IoT service, and by referring to the database 715 Information for managing and controlling IoT devices may be provided in response to a request for information on IoT devices from the wearable electronic device 302 .
- a communication interface eg, wearablekit mobile
- An event may be transmitted to an IoT management app (eg, SmartThings) 702 of the wearable electronic device 302 through 720 .
- the electronic device 301 is capable of interworking with a plurality of wearable electronic devices 702a and 702b including wireless earphones as well as a smart watch through a wearable manager 722. Therefore, the occurrence of the event can also be transmitted to the plurality of wearable electronic devices 702a and 702b.
- FIG. 8 is a signal flow diagram schematically illustrating a procedure for obtaining information related to control of IoT devices from an electronic device by a wearable electronic device according to an embodiment of the present disclosure. More specifically, FIG. 8 illustrates a process in which the wearable electronic device 302 acquires information required in relation to the execution of the IoT management app through the electronic device 301 .
- the wearable electronic device 302 may execute the IoT management app.
- the wearable electronic device 302 when the IoT management app is executed after the initial installation of the IoT management app, the wearable electronic device 302 performs initial installation (or initial setting) of IoT devices through the electronic device 301 to be interlocked. ) can be initiated.
- an IoT management app already installed on the wearable electronic device 302 when an IoT management app already installed on the wearable electronic device 302 is executed, information on IoT devices is retrieved from the electronic device 301, and based on this, IoT devices are After modifying the state for , you can update it.
- the wearable electronic device 302 is set and operated based on at least one IoT device disposed in a certain space in relation to the execution of the IoT management app, so that any IoT device in any place are deployed, and it is necessary to check the current operating state of each IoT device.
- the wearable electronic device 302 may collect information about IoT devices required to control at least one IoT device disposed in a certain space in relation to the execution of the IoT management app. For example, the wearable electronic device 302 may generate (or provide) a command specifying information to be collected (810).
- the command 810 may mean access to other components in the wearable electronic device 302 through an application program interface (API) caller.
- API application program interface
- the command 810 indicates the type of information to be retrieved from the electronic device 301, for example, a location request command 811 and a favorite request command 812 , a device request command 813, a device group command 814, or a scene command 815.
- a command (or call) (eg, “Get Locations”) 820 may include an operation 821 requesting locations and operations 822 and 823 obtaining a list including location information.
- the location information refers to divided spaces (or places) in an indoor environment, and the list including the location information includes not only office and home, but also various spaces in the house (eg : living room, kitchen, room, room) can be included.
- the list including the location information may include locations registered in the IoT management app of the electronic device 301 .
- the wearable electronic device 302 updates the view in operation 824.
- a command (or call) for the wearable electronic device 302 to fetch information related to the favorites from the electronic device 301 may include operations 831 of requesting information related to favorites and operations 832 and 833 of obtaining a list including information related to favorites.
- the list including information related to favorites may include whether or not IoT devices to be preferentially controlled among a plurality of IoT devices connected to the electronic device 301 are registered as preferred target devices. For example, it may correspond to an operation of checking whether there is a favorites list registered in the IoT management app of the electronic device 301 .
- a command for the wearable electronic device 302 to obtain information of at least one device registered as a preference target device from the electronic device 301 (eg, “Get Devices”) 840 is an operation of requesting information on preferred target devices (841) and an operation of obtaining a list including information on the preferred target devices (842, 843) may be included.
- the list including information on the preferred target devices may be a preferred device group (or a favorite device group).
- the wearable electronic device 302 updates the view in operation 844.
- a command (or , call) (eg, “Get DevicesGroups”) (850) requests information on devices in the batch control group (851), and obtains a list including information on devices in the batch control group. (852, 853).
- a plurality of surveillance cameras or a plurality of lights may be disposed in a divided space in the house, and the list including information on the devices of the batch control group includes a surveillance camera group or a light group that can be collectively controlled.
- the wearable electronic device 302 updates the view in operation 854.
- the preferred device group registered in the electronic device 301 and the preferred device group acquired by the wearable electronic device 302 from the electronic device 301 may be the same as or different from each other.
- the preferred target device within the preferred device group in the wearable electronic device 302 can be managed separately.
- the preferred device group (or favorite target list) that can be displayed on the wearable electronic device 302 is set differently from the preferred device group in the electronic device 301.
- the electronic device 301 may provide a user interface (UI) for registering a preferred device group in the wearable electronic device 302 according to a user input.
- UI user interface
- the wearable electronic device 302 may provide a user interface for registering at least some of the preferred device groups in the electronic device 301 according to a user input. For example, the user directly selects and registers target devices to be displayed on the wearable electronic device 302 from a list of preferred devices in the electronic device 301 through a menu (or item) provided by the wearable electronic device 302. can do.
- the wearable electronic device 302 can be synchronized with the IoT 340 as well as the electronic device 301 at any time based on a service account registered in the wearable electronic device 302, In the case of a preferred device group registered based on a user account, it can be maintained.
- a command (or call) for the wearable electronic device 302 to obtain scene information from the electronic device 301 may include an operation 861 of requesting information about a favorite scene and operations 862 and 863 of obtaining a list including information about the scene. Also, the wearable electronic device 302 updates the view in operation 864.
- the wearable electronic device 302 when the wearable electronic device 302 transmits each command (or call) 820, 830, 840, 850, 860 to the electronic device 301, information corresponding to the corresponding command is obtained.
- the wearable electronic device 302 may obtain all information corresponding to the collective command from the electronic device 301 in the form of a response with one collective command (eg, “Get AllInformation”).
- the batch command may be for obtaining information on IoT devices managed by the electronic device 301 at once.
- FIG. 8 illustrates a case in which the wearable electronic device 302 obtains information on the IoT device from the electronic device 301 using a command (or call), but the IoT device in the electronic device 301
- An event may be received whenever the state of information about is changed.
- the wearable electronic device 302 is communicatively connected to the electronic device 301, when the operating state of at least one IoT device registered in the preferred device group changes or the scene changes, an event from the electronic device 301 is generated. occurrence can be received.
- the wearable electronic device 302 may display a notification for notifying the user of a state change in response to the occurrence of the event.
- the user can execute the IoT management app on the wearable electronic device 302 by recognizing the notification. Also, when the IoT management app is running, the user may select a desired operation in response to the notification through a notification displayed on the wearable electronic device 302 .
- FIG. 9 is a diagram schematically illustrating a UI for registering a preferred IoT device in an electronic device and a customized UI in a wearable electronic device according to an embodiment of the present disclosure.
- the landing screen may correspond to a screen after initial setting.
- the landing screen 900 of the electronic device 301 may include a favorite (or preference) page including recommended items.
- the favorite page may be a home screen or a first page of the landing screen 900 .
- these recommended items may be formed as icons or buttons composed of titles, images, texts, photos, or a combination thereof in relation to an IoT-based environment.
- the favorites page may display shortcut items related to IoT devices frequently controlled by the user.
- at least a part of the first page of the landing screen 900 may include a 'Favorites' tab 902 or a 'Devices' tab 904 that the user may designate as a favorite. there is.
- the electronic device 301 may switch to and display a screen for controlling IoT devices for each location (or space). For example, the electronic device 301 may display a screen including a plurality of pages in response to a user selection of the 'Devices' tab 904 of FIG. 9 .
- a plurality of IoT devices including a hub may be displayed in an assigned state in any one space (eg, an office).
- various elements related to each IoT device may be displayed on the page.
- information for identifying each IoT device and status information of each IoT device may be displayed using an object.
- This landing page may play a role of guiding which IoT devices are in which state (eg, on state, off state, open state, closed state, connected state, or disconnected state).
- the wearable electronic device 302 may receive information related to IoT devices registered through the 'Favorites' tab 902 of the electronic device 301 and synchronize the received information from the electronic device 301 .
- IoT devices in the electronic device 301 and corresponding IoT devices are grouped to operate in a designated scene. Content informing that the bookmark can be accessed may be displayed.
- FIG. 10 is a diagram schematically illustrating a customized UI related to a preferred IoT device in a wearable electronic device according to an embodiment of the present disclosure.
- an authentication operation for the user and/or the wearable electronic device 302 may be required when the IoT management app is executed. For example, content guiding the user to log in for authentication may be displayed on the screen. On the other hand, if login information (or authentication information) related to the user is already registered in the IoT management app, authentication of the user and/or the wearable electronic device 302 can be performed using the registered login information, and registration If there is no registered login information, you may be guided to register a new account.
- a first screen 1010 illustrates a user interface (UI) for synchronizing information about preferred IoT devices and scenes registered through a preference menu in an electronic device 301 with a wearable electronic device 302, and there is.
- the second screen 1020 may be a launcher screen of an IoT management app when there is a service account registered in the wearable electronic device 302 . If there is no account registered in the wearable electronic device 302, a screen for logging in to a service account may be displayed.
- a service account is a concept including user authentication in which login is performed based on an ID and a password.
- the service account may be implemented as an account such as a Samsung account TM .
- screens 1030 and 1040 related to control of IoT devices on a small screen may be performed through a swipe operation.
- screens 1050 and 1060 including a scene selectable in the selected place and information on an IoT device registered in a preferred device group may be displayed.
- the wearable electronic device 302 may acquire the same data as the data of the electronic device 301 registered in the service account from the electronic device 301 by logging into the registered service account.
- the data from the electronic device 301 may be data that allows the wearable electronic device 302 to control connected IoT devices.
- it may be synchronized with the electronic device 301 through the service account, and accordingly, the wearable electronic device 302 may obtain information about a preferred device group registered in the electronic device 301 .
- the wearable electronic device 302 may obtain data capable of controlling IoT devices communicatively connected to the electronic device 301 from the IoT server 340 .
- FIG. 11 is a diagram schematically illustrating a customized UI when a location is changed in a wearable electronic device according to an embodiment of the present disclosure.
- the wearable electronic device 302 may execute an IoT management app (1010), and select a desired place (eg, a user's office or home) through the IoT management app (1120). For example, when a user selects a place, as shown in FIG. 11 , a screen 1130 including information about scenes selectable in the selected place and IoT devices registered in the preferred device group this can be displayed. For example, movement between screens related to control of IoT devices on a small screen may be performed through a swipe operation. For example, a screen 1140 including a scene (eg, work, meeting, or tea time) designated through a swipe operation may be displayed.
- the preferred device group may be a set of IoT devices for operating in a specified mode or scene by grouping IoT-related external devices.
- the preferred device group defines motion information related to a company-specified scene (eg, work, meeting, or tea time), and each IoT device for performing the motion information (Example: TV, speaker, refrigerator, light, ).
- FIG. 12 is an exemplary view of a screen based on sensor data and status information of a preferred IoT device in a wearable electronic device according to an embodiment of the present disclosure.
- the wearable electronic device 302 may display a recommendation screen including an object corresponding to a specific function on the display 360 based on sensor data and status information of a preferred IoT device. there is.
- the wearable electronic device 302 obtains status information about a plurality of IoT devices, for example, temperature information from an air conditioner and a sensor device (eg, a temperature sensor or a humidity sensor) ( 1210) can.
- the wearable electronic device 302 may receive status information on a plurality of IoT devices from the electronic device 301 connected thereto.
- the wearable electronic device 302 in order for the wearable electronic device 302 to directly collect status information on a plurality of IoT devices, the electronic device 301 as well as the connected IoT server 340, other devices or It can also connect to Internet of Things devices.
- the wearable electronic device 302 may obtain status information from at least some pre-registered IoT devices or obtain status information from the hub 210 to which the IoT devices are connected.
- the wearable electronic device 302 acquires exercise state information, which is state information of the wearable electronic device 302, based on sensor data, for example, based on a biosignal of a user wearing the wearable electronic device 302 (1215) can do.
- the wearable electronic device 302 may acquire the exercise state information (1215).
- the wearable electronic device 302 may obtain temperature information as a recommended function to be performed by the IoT devices. Accordingly, the wearable electronic device 302 may display a recommendation screen 1220 including an object corresponding to a specific function of the air conditioner based on the temperature information and the exercise state information.
- the recommendation screen 1220 corresponding to the specific function includes an object for executing the function, a name of the function, main state information of the function, and an IoT device that performs the function. At least one of a name or an indicator may be included.
- an IoT device eg, an air conditioner
- a user can control an IoT device (eg, an air conditioner) corresponding to the function by manipulating an object (eg, an execution button) for executing the function (eg, an air conditioner on function).
- the wearable electronic device 302 may acquire state information about a plurality of IoT devices, for example, state information about how lights are turned on ( 1230 ).
- the wearable electronic device 302 obtains state information of a user wearing the wearable electronic device 302 lying on a bed based on sensor data, for example, based on a biosignal of the user wearing the wearable electronic device 302 (1235) can.
- the wearable electronic device 302 may display a recommendation screen 1240 including an object corresponding to a specific function of the light (eg, turning off the light) based on the light state information and the lying state information.
- the wearable electronic device 302 may acquire state information about a plurality of IoT devices, for example, air quality information from an air purifier (1250).
- the wearable electronic device 302 may obtain, for example, user's surrounding environment information of the wearable electronic device 302 based on sensor data.
- the wearable electronic device 302 may acquire location information by itself using a global position system (GPS) or obtain location information from the connected electronic device 301 (1245). Accordingly, the wearable electronic device 302 can detect that the current user has entered the house by using the surrounding environment information and the location information. Accordingly, the wearable electronic device 302 may display a recommendation screen 1250 including an object corresponding to a specific function of the air purifier (eg, air purifier on) based on the air quality information and occupancy information.
- a recommendation screen 1250 including an object corresponding to a specific function of the air purifier (eg, air purifier on) based on the air quality information and occupancy information.
- the wearable electronic device 302 obtains, for example, the temperature information, information on a state in which a light is turned on, or information about an Internet of Things (IoT) state, such as information on air quality, from the electronic device 301.
- IoT Internet of Things
- the wearable electronic device 302 may obtain state information about the IoT device through the IoT server 340.
- the electronic device 301 may register an IoT device and functions (eg, a temperature/hygrometer function, a light function, or an air purifier function) of the IoT device with the IoT server 340, and the wearable electronic The device 302 may acquire state information about the IoT device by accessing the IoT server 340 .
- functions eg, a temperature/hygrometer function, a light function, or an air purifier function
- FIG. 13 is an exemplary view of a screen based on a use history of a preferred IoT device in a wearable electronic device according to an embodiment of the present disclosure.
- the wearable electronic device 302 may obtain use history information about the IoT device, such as TV viewing history information 1310, from the electronic device 301. At this time, the wearable electronic device 302 may obtain the usage history information through the IoT server 340 . In addition, the wearable electronic device 302 may check occupancy information by using the user's surrounding environment information based on sensor data and location information from the electronic device 301 (1315). Accordingly, the wearable electronic device 302 may display a recommendation screen 1320 including an object corresponding to a specific TV function (eg, channel 16 turned on) based on the viewing air quality information and room occupancy information.
- a specific TV function eg, channel 16 turned on
- the wearable electronic device 302 may obtain usage history information (usage history information on lights and speakers) based on usage history information and state information about the Internet of Things device obtained from the electronic device 301 or the IoT server 340. 1330) and the off state 1335 of the corresponding IoT device.
- the wearable electronic device 302 may check occupancy information by using the user's surrounding environment information based on sensor data and location information from the electronic device 301 (1335). Therefore, based on the usage history information, the wearable electronic device 302 creates an object for controlling a specific function of a light (eg, turning on a light) and a specific function of a speaker (eg, speaker on and playing a recommended song) when a corresponding time arrives.
- a recommendation screen 1340 including the screen may be displayed.
- FIG. 14 is an exemplary diagram for explaining a communication protocol between a wearable electronic device and an electronic device according to an embodiment of the present disclosure.
- functions are defined in the form of resources for each of the IoT devices 220a and 220b, and resources for executing specific functions may be different.
- the command to power on may be defined as '/sec/tv/power'
- the command to power on may be defined as '/power/switch'. It can be.
- the information (or resource) related to the execution of the specific function may correspond to a command for controlling an operation of an IoT device.
- the wearable electronic device 302 may generate a command for controlling the operation of the IoT device based on the metadata format commonly defined with the electronic device 301 .
- the wearable electronic device 302 sends a command generated in a common format (or details) such as '/capability/power' to power on the light 220a and the TV 220b, respectively. It can be transmitted (1410) to (301).
- the wearable electronic device 302 may transmit (1415) a command 1415 in the same form as the command transmitted to the electronic device 301 to the IoT server 340 without going through the electronic device 301.
- the IoT server 340 may have a metadata format for command compatibility with the wearable electronic device 302 .
- the electronic device 301 may have a format supported by each IoT device in advance in order to transmit the command to each of the lighting 220a and the TV 220b. Accordingly, the electronic device 301 converts into a format that can be supported by each of the lighting 220a and the TV 220b, and then transmits commands 1420 and 1430 of the converted format through the IoT server 340, respectively. At this time, the electronic device 301 may directly transmit each command to the light 220a and the TV 220b.
- the wearable electronic device 302 generates a command based on a common format and transmits the command to the electronic device 301, so that the format can be updated only in the electronic device 301 even if a format supported by the IoT device is changed in the future. there is.
- update (or synchronization) of a common metadata format between the wearable electronic device 302 and the electronic device 301 may be performed when checking the version of the IoT management app.
- the IoT management app installed on the wearable electronic device 302 and the IoT management app installed on the electronic device 301 may be synchronized by mutually checking version information described in each of them during communication connection. For example, whether an IoT management app needs to be updated may be determined based on a version of a common library (eg, wearablekit) 736 .
- a common library eg, wearablekit
- IoT management in the electronic device 301 An update to the app may be performed. If an update is required for the IoT management app in the wearable electronic device 302, the wearable electronic device 302 requests an update from the electronic device 301 or the wearable electronic device 302 directly sends the IoT server (if necessary) 340) to perform an update. Accordingly, in the wearable electronic device 302, as in the electronic device 301, even if the display size of the wearable electronic device is limited, the user can efficiently and easily control the IoT devices.
- Electronic devices may be devices of various types.
- the electronic device may include, for example, a portable communication device (eg, a smart phone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance.
- a portable communication device eg, a smart phone
- a computer device e.g., a smart phone
- a portable multimedia device e.g., a portable medical device
- a camera e.g., a portable medical device
- a camera e.g., a portable medical device
- a camera e.g., a portable medical device
- a camera e.g., a camera
- a wearable device e.g., a smart bracelet
- first, second, or first or secondary may simply be used to distinguish a given component from other corresponding components, and may be used to refer to a given component in another aspect (eg, importance or order) is not limited.
- a (e.g., first) component is said to be “coupled” or “connected” to another (e.g., second) component, with or without the terms “functionally” or “communicatively.”
- the certain component may be connected to the other component directly (eg by wire), wirelessly, or through a third component.
- module used in various embodiments of this document may include a unit implemented in hardware, software, or firmware, and is interchangeable with terms such as, for example, logic, logical blocks, parts, or circuits.
- a module may be an integrally constructed component or a minimal unit of components or a portion thereof that performs one or more functions.
- the module may be implemented in the form of an application-specific integrated circuit (ASIC).
- ASIC application-specific integrated circuit
- a storage medium eg, internal memory 136 or external memory 138
- a machine eg, electronic device 101
- a processor eg, the processor 120
- a device eg, the electronic device 101
- the one or more instructions may include code generated by a compiler or code executable by an interpreter.
- the device-readable storage medium may be provided in the form of a non-transitory storage medium.
- the storage medium is a tangible device and does not contain a signal (e.g. electromagnetic wave), and this term refers to the case where data is stored semi-permanently in the storage medium. It does not discriminate when it is temporarily stored.
- a signal e.g. electromagnetic wave
- methods according to various embodiments disclosed in this document may be included in and provided in a computer program product.
- Computer program products may be traded between sellers and buyers as commodities.
- a computer program product is distributed in the form of a device-readable storage medium (eg compact disc read only memory (CD-ROM)), or through an application store (eg Play Store TM ) or on two user devices ( It can be distributed (eg downloaded or uploaded) online, directly between smart phones.
- a device-readable storage medium eg compact disc read only memory (CD-ROM)
- an application store eg Play Store TM
- It can be distributed (eg downloaded or uploaded) online, directly between smart phones.
- at least part of the computer program product may be temporarily stored or temporarily created in a device-readable storage medium such as a manufacturer's server, an application store server, or a relay server's memory.
- each component (eg, module or program) of the components described above may include a single object or a plurality of entities, and some of the plurality of entities are separated from other components. may be placed.
- one or more components or operations among the corresponding components described above may be omitted, or one or more other components or operations may be added.
- a plurality of components eg modules or programs
- the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by a corresponding component of the plurality of components prior to the integration. .
- operations performed by a module, program, or other component are executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations are executed in a different order. may be added, omitted, or one or more other actions may be added.
- the instructions are set to cause the wearable electronic device to perform at least one operation when executed by at least one processor of the wearable electronic device.
- the at least one operation may include obtaining state information related to a plurality of IoT devices from an electronic device connected to the plurality of IoT devices through wireless communication, and obtaining sensor data using at least one sensor. identifying a candidate function that can be provided by at least one IoT device among the plurality of IoT devices based on the sensor data and state information related to the plurality of IoT devices; and An operation of displaying candidate functions that can be provided by the Internet of Things device may be included.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Automation & Control Theory (AREA)
- Computing Systems (AREA)
- User Interface Of Digital Computer (AREA)
- Telephone Function (AREA)
Abstract
Description
Claims (15)
- 웨어러블 전자 장치에 있어서,신체 착용 가능하도록 형성된 하우징;적어도 하나의 센서;통신 모듈;디스플레이; 및상기 적어도 하나의 센서, 상기 통신 모듈 및 상기 디스플레이와 작동적으로 연결된 적어도 하나의 프로세서를 포함하고, 상기 적어도 하나의 프로세서는,복수의 사물 인터넷 장치들과 무선 통신 연결된 전자 장치로부터, 상기 통신 모듈을 통해 상기 복수의 사물 인터넷 장치들과 관련된 상태 정보를 획득하고,상기 적어도 하나의 센서를 이용하여 센서 데이터를 획득하고,상기 센서 데이터 및 상기 복수의 사물 인터넷 장치들과 관련된 상태 정보에 기반하여, 상기 복수의 사물 인터넷 장치들 중 적어도 하나의 사물 인터넷 장치 장치에서 제공 가능한 후보 기능을 식별하고,상기 적어도 하나의 사물 인터넷 장치에서 제공 가능한 후보 기능의 정보를 상기 디스플레이 상에 표시하도록 설정된, 웨어러블 전자 장치.
- 제1항에 있어서, 상기 적어도 하나의 프로세서는,센서 데이터와 적어도 하나의 사물 인터넷 장치의 상태 정보에 대응하여 제공 가능한 기능들을 맵핑한 맵핑 테이블을 참조하고,상기 맵핑 테이블에 기반하여 상기 적어도 하나의 사물 인터넷 장치에서 제공 가능한 후보 기능을 식별하도록 더 설정된, 웨어러블 전자 장치.
- 제1항에 있어서, 상기 적어도 하나의 프로세서는,상기 통신 모듈을 통해 상기 전자 장치와의 통신 연결 시, 상기 전자 장치에서의 선호 기기 그룹에 등록된 상기 복수의 사물 인터넷 장치들과 관련된 상태 정보를 획득하도록 더 설정된, 웨어러블 전자 장치.
- 제3항에 있어서, 상기 상태 정보는,상기 복수의 사물 인터넷 장치들 각각의 배치 위치, 상기 복수의 사물 인터넷 장치들에 대한 식별 정보, 또는 센서 데이터에 대응하여 상기 복수의 사물 인터넷 장치들 중 적어도 일부가 지정된 기능을 수행하도록 지시하는 정보를 그룹핑한 씬(scene) 정보 중 적어도 하나를 포함하는, 웨어러블 전자 장치.
- 제1항에 있어서, 상기 적어도 하나의 프로세서는,상기 적어도 하나의 센서를 이용하여 획득된 센서 데이터에 기반하여, 상기 웨어러블 전자 장치의 착용 상태, 상기 웨어러블 전자 장치를 착용한 사용자 상태, 또는 상기 사용자 주변 환경 중 적어도 하나와 관련하여, 상기 웨어러블 전자 장치의 상태를 식별하도록 더 설정된, 웨어러블 전자 장치.
- 제5항에 있어서, 상기 적어도 하나의 프로세서는,상기 웨어러블 전자 장치의 상태 및 상기 복수의 사물 인터넷 장치들에 대한 사용 이력에 기반하여, 상기 복수의 사물 인터넷 장치들 중 상기 적어도 하나의 사물 인터넷 장치 장치에서 제공 가능한 후보 기능을 식별하도록 더 설정된, 웨어러블 전자 장치.
- 제1항에 있어서, 상기 적어도 하나의 프로세서는,상기 디스플레이 상에 표시되는 상기 적어도 하나의 사물 인터넷 장치에서 제공 가능한 후보 기능을 선택하는 사용자 입력을 수신하고,상기 사용자 입력에 대응하여, 상기 적어도 하나의 사물 인터넷 장치의 동작을 제어하기 위한 명령어를 상기 통신 모듈을 통해 상기 전자 장치로 전송하도록 더 설정된, 웨어러블 전자 장치.
- 제7항에 있어서, 상기 적어도 하나의 프로세서는,상기 전자 장치와 상기 웨어러블 전자 장치 간에 공통적으로 정의된 메타 데이터 포맷에 기반하여, 상기 적어도 하나의 사물 인터넷 장치의 동작을 제어하기 위한 명령어를 상기 통신 모듈을 통해 전송하도록 더 설정된, 웨어러블 전자 장치.
- 제7항에 있어서, 상기 적어도 하나의 프로세서는,상기 사용자 입력에 대응하여, 상기 전자 장치에 연결된 상기 복수의 사물 인터넷 장치들을 제어하기 위한 사물 인터넷 기반의 어플리케이션을 실행하도록 더 설정된, 웨어러블 전자 장치.
- 웨어러블 전자 장치에서 복수의 사물 인터넷 장치들을 제어하기 위한 방법에 있어서,복수의 사물 인터넷 장치들과 무선 통신 연결된 전자 장치로부터, 상기 복수의 사물 인터넷 장치들과 관련된 상태 정보를 획득하는 동작;적어도 하나의 센서를 이용하여 센서 데이터를 획득하는 동작;상기 센서 데이터 및 상기 복수의 사물 인터넷 장치들과 관련된 상태 정보에 기반하여, 상기 복수의 사물 인터넷 장치들 중 적어도 하나의 사물 인터넷 장치 장치에서 제공 가능한 후보 기능을 식별하는 동작; 및상기 적어도 하나의 사물 인터넷 장치에서 제공 가능한 후보 기능의 정보를 표시하는 동작을 포함하는, 복수의 사물 인터넷 장치들을 제어하기 위한 방법.
- 제10항에 있어서, 상기 적어도 하나의 사물 인터넷 장치 장치에서 제공 가능한 후보 기능을 식별하는 동작은,센서 데이터와 적어도 하나의 사물 인터넷 장치의 상태 정보에 대응하여 제공 가능한 기능들을 맵핑한 맵핑 테이블을 참조하는 동작; 및상기 맵핑 테이블에 기반하여 상기 적어도 하나의 사물 인터넷 장치에서 제공 가능한 후보 기능을 식별하는 동작을 포함하는, 복수의 사물 인터넷 장치들을 제어하기 위한 방법.
- 제10항에 있어서, 상기 복수의 사물 인터넷 장치들과 관련된 상태 정보를 획득하는 동작은,상기 전자 장치와의 통신 연결 시, 상기 전자 장치에서의 선호 기기 그룹에 등록된 상기 복수의 사물 인터넷 장치들과 관련된 상태 정보를 획득하는 동작을 포함하는, 복수의 사물 인터넷 장치들을 제어하기 위한 방법.
- 제12항에 있어서, 상기 상태 정보는,상기 복수의 사물 인터넷 장치들 각각의 배치 위치, 상기 복수의 사물 인터넷 장치들에 대한 식별 정보, 또는 센서 데이터에 대응하여 상기 복수의 사물 인터넷 장치들 중 적어도 일부가 지정된 기능을 수행하도록 지시하는 정보를 그룹핑한 씬(scene) 정보 중 적어도 하나를 포함하는, 복수의 사물 인터넷 장치들을 제어하기 위한 방법.
- 제10항에 있어서, 상기 제공 가능한 후보 기능의 정보는, 기능명, 기능의 설명, 또는 기능을 수행하는 사물 인터넷 장치의 이름 중 적어도 하나를 포함하는, 복수의 사물 인터넷 장치들을 제어하기 위한 방법.
- 명령들을 저장하고 있는 적어도 하나의 비휘발성 저장 매체에 있어서, 상기 명령들은 웨어러블 전자 장치의 적어도 하나의 프로세서에 의하여 실행될 때에 상기 웨어러블 전자 장치로 하여금 적어도 하나의 동작을 수행하도록 설정된 것으로서, 상기 적어도 하나의 동작은,복수의 사물 인터넷 장치들과 무선 통신 연결된 전자 장치로부터, 상기 복수의 사물 인터넷 장치들과 관련된 상태 정보를 획득하는 동작;적어도 하나의 센서를 이용하여 센서 데이터를 획득하는 동작;상기 센서 데이터 및 상기 복수의 사물 인터넷 장치들과 관련된 상태 정보에 기반하여, 상기 복수의 사물 인터넷 장치들 중 적어도 하나의 사물 인터넷 장치 장치에서 제공 가능한 후보 기능을 식별하는 동작; 및상기 적어도 하나의 사물 인터넷 장치에서 제공 가능한 후보 기능의 정보를 표시하는 동작을 포함하는, 저장 매체.
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP22870159.5A EP4344139A4 (en) | 2021-09-15 | 2022-08-22 | PORTABLE ELECTRONIC DEVICE FOR CONTROLLING A PLURALITY OF INTERNET OF THINGS DEVICES, METHOD OF OPERATION THEREOF, AND STORAGE MEDIUM |
CN202280061929.8A CN117981282A (zh) | 2021-09-15 | 2022-08-22 | 控制多个物联网装置的可穿戴电子装置、操作方法和存储介质 |
US17/896,621 US20230083823A1 (en) | 2021-09-15 | 2022-08-26 | Wearable electronic device for controlling multiple iot devices, method for operating same, and storage medium |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR10-2021-0123030 | 2021-09-15 | ||
KR1020210123030A KR20230039996A (ko) | 2021-09-15 | 2021-09-15 | 복수의 사물 인터넷 장치들을 제어하기 위한 웨어러블 전자 장치, 그 동작 방법 및 저장 매체 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/896,621 Continuation US20230083823A1 (en) | 2021-09-15 | 2022-08-26 | Wearable electronic device for controlling multiple iot devices, method for operating same, and storage medium |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023043073A1 true WO2023043073A1 (ko) | 2023-03-23 |
Family
ID=85603128
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2022/012548 WO2023043073A1 (ko) | 2021-09-15 | 2022-08-22 | 복수의 사물 인터넷 장치들을 제어하기 위한 웨어러블 전자 장치, 그 동작 방법 및 저장 매체 |
Country Status (2)
Country | Link |
---|---|
KR (1) | KR20230039996A (ko) |
WO (1) | WO2023043073A1 (ko) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20160095397A (ko) * | 2015-02-03 | 2016-08-11 | 아주대학교산학협력단 | 웨어러블 디바이스를 이용한 사물 인터넷 기기의 제어 방법, 시스템 및 컴퓨터 판독 가능한 기록 매체 |
US20180059716A1 (en) * | 2015-03-09 | 2018-03-01 | Koninklijke Philips N.V. | Wearable health interface for controlling internet of things devices |
KR20180097977A (ko) * | 2017-02-24 | 2018-09-03 | 삼성전자주식회사 | 복수의 IoT 장치들을 제어하기 위한 방법 및 장치 |
KR102025552B1 (ko) * | 2018-05-09 | 2019-09-26 | 경북대학교 산학협력단 | 웨어러블 장치를 이용한 위치 기반 사물 인터넷 서비스 중계기 및 중계 방법 |
KR20200094571A (ko) * | 2019-01-30 | 2020-08-07 | 삼성전자주식회사 | 사용자 데이터를 처리하는 시스템, 및 그 시스템의 제어 방법 |
-
2021
- 2021-09-15 KR KR1020210123030A patent/KR20230039996A/ko active Search and Examination
-
2022
- 2022-08-22 WO PCT/KR2022/012548 patent/WO2023043073A1/ko active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20160095397A (ko) * | 2015-02-03 | 2016-08-11 | 아주대학교산학협력단 | 웨어러블 디바이스를 이용한 사물 인터넷 기기의 제어 방법, 시스템 및 컴퓨터 판독 가능한 기록 매체 |
US20180059716A1 (en) * | 2015-03-09 | 2018-03-01 | Koninklijke Philips N.V. | Wearable health interface for controlling internet of things devices |
KR20180097977A (ko) * | 2017-02-24 | 2018-09-03 | 삼성전자주식회사 | 복수의 IoT 장치들을 제어하기 위한 방법 및 장치 |
KR102025552B1 (ko) * | 2018-05-09 | 2019-09-26 | 경북대학교 산학협력단 | 웨어러블 장치를 이용한 위치 기반 사물 인터넷 서비스 중계기 및 중계 방법 |
KR20200094571A (ko) * | 2019-01-30 | 2020-08-07 | 삼성전자주식회사 | 사용자 데이터를 처리하는 시스템, 및 그 시스템의 제어 방법 |
Also Published As
Publication number | Publication date |
---|---|
KR20230039996A (ko) | 2023-03-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2022154286A1 (ko) | 사용자 인터페이스를 제공하는 방법 및 그 전자 장치 | |
WO2023043073A1 (ko) | 복수의 사물 인터넷 장치들을 제어하기 위한 웨어러블 전자 장치, 그 동작 방법 및 저장 매체 | |
WO2022030860A1 (ko) | Iot 환경에서 타겟 전자 장치를 제어하기 위한 전자 장치 및 그에 관한 방법 | |
WO2023008697A1 (ko) | 가전기기 및 가전기기의 동작 방법 | |
WO2022149797A1 (ko) | 위치 기반의 복수의 외부 디바이스들을 제어하기 위한 전자 장치, 그 동작 방법 및 저장매체 | |
WO2021221317A1 (ko) | 광고 공유 방법 및 그 장치 | |
WO2024151042A1 (ko) | 어플리케이션 목록을 제공하기 위한 전자 장치, 그 동작 방법 및 저장 매체 | |
WO2024076008A1 (ko) | 파일을 공유하는 전자 장치, 방법, 및 비일시적 컴퓨터 판독가능 저장 매체 | |
WO2024049088A1 (ko) | 미디어 기반의 조명 제어 서비스를 제공하기 위한 전자 장치, 그 동작 방법 및 저장 매체 | |
WO2022215865A1 (ko) | 전자 장치 및 iot 제어 정보 공유 방법 | |
WO2024143884A1 (ko) | 컨텐트 재생에 기반한 출력 장치들을 제어하는 전자 장치, 그 동작 방법 및 저장 매체 | |
WO2024080680A1 (ko) | 상황 특정 설정을 위한 사용자 인터페이스를 표시하는 전자 장치, 방법, 및 비일시적 컴퓨터 판독가능 저장 매체 | |
WO2023153622A1 (ko) | 기기 설정 동기화 방법 및 장치 | |
WO2024025194A1 (ko) | 알림과 관련된 동작을 수행하기 위한 방법 및 이를 지원하는 전자 장치 | |
WO2023054897A1 (ko) | 영상 통화를 수행하는 전자 장치 및 방법 | |
WO2023075337A1 (ko) | 외부 전자 장치와 통신하는 전자 장치 및 그 동작 방법 | |
WO2022211245A1 (ko) | 전자 장치 및 전자 장치에서 동적 조건으로 태스크를 수행하는 방법 | |
WO2023085822A1 (ko) | 디바이스 위치 결정 방법 및 상기 방법을 수행하는 전자 장치 | |
WO2024117650A1 (ko) | 전자 장치 및 전자 장치의 쿠키 정보 관리 방법 | |
WO2023018086A1 (ko) | 외부 장치의 자동 완성 텍스트를 동기화하는 전자 장치 및 방법 | |
WO2023022349A1 (ko) | 적어도 하나의 외부 장치를 제어하는 전자 장치 및 이의 동작 방법 | |
WO2023054905A1 (ko) | 외부 전자 장치의 데이터를 활용하는 방법 및 전자 장치 | |
WO2024101916A1 (ko) | 장치 설정 방법 및 이를 지원하는 전자 장치 | |
WO2023054991A1 (ko) | 적어도 하나의 입력 장치를 제어하는 전자 장치 및 그 제어 방법 | |
WO2024111976A1 (ko) | 전자 장치 및 가상 iot 환경을 제공하는 방법 |
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: 22870159 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022870159 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2022870159 Country of ref document: EP Effective date: 20231222 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202417001792 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202280061929.8 Country of ref document: CN |
|
NENP | Non-entry into the national phase |
Ref country code: DE |