Method and apparatus for controlling non-UWB device by using UWB in wireless communication system

Abstract

The present disclosure provides a method of controlling a non-UWB device by using UWB. A method for a first UWB device according to the present disclosure may comprise the steps of: identifying a position of a non-UWB device based on UWB ranging between the first UWB device and each of at least two second UWB devices; and controlling the non-UWB device based on the position of the non-UWB device.

Description

Technical Field

[0001] The present disclosure relates to UWB communications, and more particularly, to methods and devices for controlling non-UWB devices by using UWB technology. Background Art

[0002] The Internet, which is a human-centered connected network in which people generate and consume information, is now evolving into the Internet of things (IoT), in which distributed entities (such as things) exchange and process information. The Internet of everything (IoE), which is a combination of IoT technology and big data processing technology through connection with cloud servers, etc., has emerged. As technical elements, such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology" are required for IoT implementation. Recently, sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), etc. have been studied.

[0003] Such an IoT environment can provide intelligent Internet technology (IT) services, which create new value for human life by collecting and analyzing data generated among connected things. Through the integration and combination between existing information technology (IT) and various industrial applications, IoT can be applied to various fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart home appliances and advanced medical services.

[0004] With the advancement of wireless communication systems as described above, various services can be provided, and thus a way of efficiently providing these services is required. For example, a ranging technology that measures the distance between electronic devices by using ultra wide band (UWB) can be used. In particular, UWB technology tends to be loaded into devices provided to smart homes, such as door locks and smart speakers, and various portable devices (e.g., smartphones and wearable devices). Summary of the invention

[0005] Technical issues

[0006] The present disclosure provides a method capable of identifying the location of a non-UWB device that does not support UWB by using UWB ranging between UWB devices. In addition, the present disclosure provides a method for identifying and controlling a non-UWB device by using a UWB device, the location of which has been identified using UWB ranging between UWB devices.

[0007] Technical Solution

[0008] The method of the first UWB device according to various embodiments of the present disclosure may include: identifying a location of a non-UWB device based on UWB ranging between the first UWB device and each of at least two second UWB devices; and controlling the non-UWB device based on the location of the non-UWB device.

[0009] As an embodiment, the result of UWB ranging between the first UWB device and each of the at least two second UWB devices may include angle of arrival (AoA) information and information about the distance between the first UWB device and each of the at least two second UWB devices.

[0010] As an embodiment, the first UWB device may identify the distance between the first UWB device and the non-UWB device based on preconfigured information.

[0011] As an embodiment, identifying the location of a non-UWB device may include: calculating the distance between at least two second UWB devices; calculating the angle of the first UWB device relative to the location of a UWB device that is one of the at least two second UWB devices based on the distance between the at least two second UWB devices; and identifying the location of the first UWB device relative to the UWB device that is one of the at least two second UWB devices based on the calculated angle of the first UWB device.

[0012] As an embodiment, the method may include: calculating a vector from a first UWB device to a non-UWB device; calculating a vector from a UWB device that is one of at least two second UWB devices to the first UWB device; calculating the sum of the calculated vectors; and based on the sum of the vectors, identifying a position of the non-UWB device relative to the UWB device that is one of the at least two second UWB devices.

[0013] As an embodiment, the at least two second UWB devices may be UWB tag devices.

[0014] As an embodiment, UWB ranging may be performed based on a one-way ranging (OWR) method.

[0015] According to various embodiments of the present disclosure, a first UWB device may include: a transceiver; and at least one processor connected to the transceiver, wherein the at least one processor is configured to: identify a location of a non-UWB device based on UWB ranging between the first UWB device and each of at least two second UWB devices, and control the non-UWB device based on the location of the non-UWB device.

[0016] Beneficial Effects

[0017] According to the method of the present disclosure, the location of a non-UWB device that does not support UWB ranging can be identified. In addition, according to the method of the present disclosure, a non-UWB device can be identified and controlled by using a UWB device. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 is a block diagram schematically illustrating an electronic device.

[0019] Figure 2a An exemplary architecture of a UWB device is shown.

[0020] Figure 2b An exemplary configuration of a framework of a UWB device is shown.

[0021] Figure 3 An exemplary configuration of a communication system including a UWB device is shown.

[0022] Figure 4 A UWB ranging operation between UWB devices is shown.

[0023] Figure 5 A method according to an embodiment of the present disclosure is shown, in which a UWB supporting device identifies and controls a non-UWB supporting device.

[0024] Figure 6 An embodiment for identifying a location of a non-UWB supporting device according to an embodiment of the present disclosure is shown.

[0025] Figure 7 is a diagram showing a structure of an electronic device according to an embodiment of the present disclosure.

[0026] Figure 8 is a flowchart illustrating a method of a first UWB device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0027] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0028] When describing the embodiments, descriptions related to well-known technical contents in the relevant field and not directly related to the present disclosure will be omitted. Such unnecessary descriptions are omitted to prevent the main idea of ​​the present disclosure from being obscured and to convey the main idea more clearly.

[0029] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted or schematically shown. In addition, the size of each element does not fully reflect the actual size. In each of the accompanying drawings, the same or corresponding elements are given the same reference numerals.

[0030] By referring to the embodiments described in detail below in conjunction with the accompanying drawings, the advantages and features of the present disclosure and the ways to achieve them will become apparent. However, the present disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are provided only to fully disclose the present disclosure and inform those skilled in the art of the scope of the present disclosure, and the present disclosure is limited only by the scope of the attached claims. Throughout the specification, the same or similar reference numerals indicate the same or similar elements.

[0031] Here, it will be understood that each frame of the flowchart diagram and the combination of frames in the flowchart diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine so that the instructions executed by the processor of the computer or other programmable data processing device create a component for realizing the function specified in one or more flowchart frames. These computer program instructions can also be stored in a computer-available or computer-readable memory, which can instruct the computer or other programmable data processing device to operate in a particular manner so that the instructions stored in the computer-available or computer-readable memory produce a manufactured product including an instruction component for realizing the function specified in one or more flowchart frames. The instructions executed on a computer or other programmable data processing device to execute a series of operating steps on a computer or other programmable data processing device to produce a computer-implemented process can provide steps for realizing the function specified in the flowchart frame.

[0032] In addition, each box in the flowchart diagram may represent a module, a code segment or a code portion, which includes one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions mentioned in the box may not appear in order. For example, two boxes shown in succession may actually be executed substantially simultaneously, or the boxes may sometimes be executed in reverse order, depending on the functions involved.

[0033] As used in the embodiments of the present disclosure, the term "unit" refers to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), and the "unit" can perform certain functions. However, "unit" does not always have a meaning limited to software or hardware. "Unit" can be constructed to be stored in an addressable storage medium or to execute one or more processors. Therefore, "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, programs, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays, and parameters. The elements and functions provided by the "unit" can be combined into a smaller number of elements or "units", or divided into a larger number of elements or "units". In addition, elements and "units" can be implemented as replicating one or more CPUs in a device or a secure multimedia card. In addition, the "unit" in various embodiments of the present disclosure can include one or more processors.

[0034] As used herein, the term "terminal" or "device" may also be referred to as a mobile station (MS), user equipment (UE), user terminal (UT), wireless terminal, access terminal (AT), terminal, subscriber unit, subscriber station (SS), wireless device, wireless communication device, wireless transmit / receive unit (WTRU), mobile node, mobile phone or other terms. Various examples of terminals may include cellular phones, smart phones with wireless communication functions, personal digital assistants (PDA) with wireless communication functions, wireless modems, portable computers with wireless communication functions, photographing devices such as digital cameras with wireless communication functions, gaming devices with wireless communication functions, music storage and reproduction home appliances with wireless communication functions, Internet home appliances capable of wireless access and browsing the Internet, and portable units or terminals with integrated combinations of the above functions. In addition, the terminal may include a machine to machine (M2M) terminal and a machine type communication (MTC) terminal / device, but is not limited thereto. In the specification, the terminal may also be referred to as an electronic device or simply a device.

[0035] Hereinafter, the operating principle of the present disclosure will be described in detail in conjunction with the accompanying drawings. When describing the present disclosure below, when it is determined that the description may make the subject matter of the present disclosure unnecessarily unclear, the detailed description of the known functions or configurations incorporated herein will be omitted. The terms to be described below are terms defined in consideration of the functions in the present disclosure, and may be different depending on the user, the user's intention or custom. Therefore, the definition of the terms should be made based on the content of the entire specification.

[0036] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the following description of the embodiments of the present disclosure, a communication system using UWB will be described by way of example, but the embodiments of the present disclosure may be applied to other communication systems having similar technical backgrounds or characteristics. Examples of such communication systems may include communication systems Bluetooth or ZigBee. Therefore, based on the determination of those skilled in the art, the embodiments of the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure.

[0037] When describing the present disclosure below, when it is determined that the description may make the subject matter of the present disclosure unnecessarily unclear, the detailed description of the known functions or configurations incorporated herein will be omitted. The terms to be described below are terms defined in consideration of the functions in the present disclosure, and may differ depending on the user, the user's intention or custom. Therefore, the definition of the terms should be made based on the content of the entire specification.

[0038] Generally, wireless sensor network technology is roughly divided into wireless local area network (WLAN) technology and wireless personal area network (WPAN) technology according to the identification distance. In this case, WLAN is a technology based on IEEE 802.11 and is a technology that enables access to a backbone network within a radius of 100 m. In addition, WPAN is a technology based on IEEE 802.15 and includes Bluetooth, ZigBee, ultra-wideband (UWB), etc. A wireless network in which such a wireless network technology is implemented may include multiple electronic devices.

[0039] According to the definition of the Federal Communications Commission (FCC), UWB may refer to a wireless communication technology that uses a bandwidth of 500 MHz or higher, or a bandwidth corresponding to 20% or more of its center frequency. UWB may refer to the frequency band itself to which UWB communication is applied. UWB may enable secure and accurate ranging between devices. Therefore, UWB enables relative position estimation based on the distance between two devices, or accurate position estimation of a device based on the distance to a fixed device (whose position is known).

[0040] Specific terms used in the following description are provided to help understanding of the present disclosure, and the use of these specific terms may be changed into other forms without departing from the technical spirit of the present disclosure.

[0041] An "application dedicated file (ADF)" may be, for example, a data structure within an application data structure that may contain application or application specific data.

[0042] An "application protocol data unit" (APDU) may be a command and response used when communicating with an application data structure within a UWB device.

[0043] The “application specific data” may be, for example, a file structure having a root level and an application layer, including UWB controller information and UWB session data required for a UWB session.

[0044] A "controller" may be a ranging device that defines and controls ranging control messages (RCMs) (or control messages). A controller may define and control ranging characteristics by sending control messages.

[0045] A "controller" may be a ranging device that uses ranging parameters in an RCM (or control message) received from a controller. A controller may use ranging features such as those configured by a controller through a control message.

[0046] Unlike the "static scrambled timestamp sequence (STS)", the "dynamic STS mode" may be an operation mode in which the STS is not repeated during a ranging session. In this mode, the STS is managed by the ranging device, and the ranging session key for generating the STS may be managed by the security component.

[0047] An "applet" may be, for example, an applet executed on a secure component that includes UWB parameters and service data. The applet may be a FiRa applet.

[0048] A “ranging device” may be a device capable of performing UWB ranging. In the present disclosure, a ranging device may be an enhanced ranging device (ERDEV) or a FiRa device defined in IEEE802.15.4z. A ranging device may be referred to as a UWB device.

[0049] A "UWB-enabled application" may be an application for UWB services. For example, a UWB-enabled application may be an application that uses the framework API to configure an OOB connector, security services, and / or UWB services for a UWB session. A "UWB-enabled application" may simply be referred to as an application or a UWB application. A UWB-enabled application may be a FiRa-enabled application.

[0050] A "framework" may be a component for providing access to profiles, individual UWB configurations and / or notifications. The framework may be, for example, a collection of logical software components including a profile manager, an OOB connector, security services and / or UWB services. The framework may be a FiRa framework.

[0051] An "OOB connector" may be a software component for establishing an out-of-band (OOB) connection (eg, a BLE connection) between ranging devices. The OOB connector may be a FiRa OOB connector.

[0052] A "profile" may be a set of predefined UWB and OOB configuration parameters. The profile may be a FiRa profile.

[0053] A "profile manager" may be a software component that implements the profiles available on the ranging device. The profile manager may be a FiRa profile manager.

[0054] A "service" may correspond to an implementation of a use case that provides a service to an end user.

[0055] A "smart ranging device" may be a ranging device that can implement the optional framework API. A smart ranging device may be a FiRa smart device.

[0056] A "global dedicated file (GDF)" can be application-specific data at the root level, including data required to establish a UWB session.

[0057] A "framework API" may be an API used by UWB-enabled applications to communicate with the framework.

[0058] An "initiator" may be a ranging device that initiates a ranging exchange. The initiator may initiate a ranging exchange by sending a first RFRAME (ranging exchange message).

[0059] An "object identifier (OID)" may be an identifier of an ADF in an application data structure.

[0060] "Out-of-band (OOB)" may correspond to data communications that do not use UWB as the underlying wireless technology.

[0061] A “ranging data set (RDS)” may be data necessary to establish a UWB session that requires protection of confidentiality, authenticity, and integrity (eg, UWB session key, session ID, etc.).

[0062] A "responder" may be a ranging device that responds to an initiator in a ranging exchange. A responder may respond to a ranging exchange message received from an initiator.

[0063] "STS" may be an encryption sequence used to increase the integrity and accuracy of the ranging measurement timestamp. STS may be generated based on the ranging session key.

[0064] A "secure channel" may be a data channel that is protected from eavesdropping and tampering.

[0065] A “secure component” may be, for example, an entity with a defined security level (eg, a secure element (SE) or a trusted execution environment (TEE)) that interfaces with the UWBS to provide the RDS to the UWBS when using a dynamic STS.

[0066] “SE” may be a tamper-resistant secure hardware component that may be used as a secure component in a ranging device.

[0067] "Secure ranging" may be ranging based on an STS generated through a strong cryptographic operation.

[0068] A “security service” may be a software component used to interface with a secure component such as a secure element or TEE.

[0069] A "servlet" may be an applet on a secure component that handles service-specific transactions.

[0070] "Service data" may be data defined by a service provider, which needs to be transmitted between two ranging devices to implement a service.

[0071] A "service provider" may be an entity that defines and provides the hardware and software necessary to deliver a specific service to an end user.

[0072] "Static STS mode" is an operation mode in which the STS is repeated during a session and does not need to be managed by a security component.

[0073] A "secure UWB service (SUS) applet" may be an applet on the SE that communicates with the applet to retrieve the data required to implement a secure UWB session with another ranging device. In addition, the SUS applet may transmit corresponding data (information) to the UWBS.

[0074] A "UWB Service" may be a software component that provides access to a UWB S.

[0075] A "UWB session" may be a period from when a controller and a controlled party start communicating via UWB until they stop communicating. A UWB session may include ranging, data transfer, or both ranging and data transfer.

[0076] The “UWB session ID” may be an ID (eg, a 32-bit integer) that identifies a UWB session and is shared between a controller and a controllable.

[0077] The "UWB session key" may be a key used to protect a UWB session. The UWB session key may be used to generate an STS. The UWB session key may be a UWB ranging session key (URSK) and may be referred to simply as a session key.

[0078] A "UWB subsystem (UWBS)" may be a hardware component that implements the UWB PHY and MAC layers (specifications). The UWBS may have an interface for the framework, and an interface for searching the security components of the RDS.

[0079] A "UWB message" may be a message including a payload IE sent by a UWB device (e.g., ERDEV). A UWB message may be, for example, a ranging initiation message (RIM), a ranging response message (RRM), a ranging final message (RFM), a control message (CM), a measurement report message (MRM), a ranging result report message (RRRM), a control update message (CUM), or a one-way ranging (OWR) message. If desired, multiple ranging messages may be combined into one message.

[0080] "OWR" may be a ranging method that uses messages sent in one direction between a ranging device and one or more other ranging devices. OWR may be used to measure time difference of arrival (TDoA). In addition, OWR may be used to measure AoA on the receiving side instead of measuring TDoA. In this case, a pair of advertisers and observers may be used. OWR for measuring AoA allows an observer to receive an OWR message from an advertiser and measure the AoA to determine the intent, action, or movement of the observer's user. For example, a user's intent to control a particular advertiser may be verified by measuring the AoA of an OWR message from the advertiser. In the present disclosure, OWR may be referred to as UWB OWR.

[0081] An "advertiser" is a ranging device that sends an AoA measurement message. An advertiser may include application data (application payload data) as part of the MAC payload of an AoA measurement message by using a data message IE. The application data may be configured by an upper layer. In the present disclosure, an advertiser may be referred to as an advertiser device or a UWB advertiser device. In the present disclosure, an AoA measurement message may also be referred to as an OWB message for AoA measurement, a UWB OWR message for AoA measurement, a UWB advertisement message, an advertisement message, etc.

[0082] An "observer" is a ranging device that receives an AoA measurement message and measures the AoA of each message. The observer may send the measured AoA to an upper layer. When application data is included in the MAC payload of an AoA measurement message, the observer may send application data to an upper layer. In the present disclosure, an observer may be referred to as an observer device or a UWB observer device.

[0083] "TWR" may be a ranging method that is capable of estimating the relative distance between two devices by measuring the time of flight (ToF) via exchanging ranging messages between the two devices. The TWR method may be one of double-sided two-way ranging (DS-TWR) and single-sided two-way ranging (SS-TWR). SS-TWR may be a procedure for performing ranging through a round-trip time measurement. For example, SS-TWR may include a transmission operation from an initiator to a responder's RIM, and a transmission operation from a responder to an initiator's RRM. DS-TWR may be a procedure for performing ranging through two round-trip time measurements. For example, DS-TWR may include a transmission operation from an initiator to a responder's RIM, a transmission operation from a responder to an initiator's RRM, and a transmission operation from an initiator to a responder's RFM. Through this ranging exchange (ranging message exchange), the time of flight (ToF) can be calculated, and the distance between the two devices can be estimated. Meanwhile, during the TWR process, the measured AoA information (eg, AoA azimuth result and AoA elevation result) may be transmitted to another ranging device through RRRM or other messages. In the present disclosure, TWR may be referred to as UWB TWR.

[0084] "AoA" is the angle of arrival of a received signal and can be expressed as relative angles, such as AoA azimuth and AoA elevation. For example, it can be assumed that the measurement device is a mobile phone with a display, the Y axis is the vertical display axis of the phone, the X axis is the horizontal display axis of the phone, and the Z axis is orthogonal to the display of the phone. In this case, the AoA azimuth can be the relative angle between the input signal projected on the XZ plane and the Z axis, and the AoA elevation can be the relative angle between the input signal and the XZ plane.

[0085] In the case of TWR, the controller (initiator) can measure the AoA azimuth of RRM and send the measured AoA azimuth through the UCI notification message. The controlled party (responder) can measure the AoA azimuth of the RIM message and send the measured AoA azimuth through RRRM.

[0086] In the case of TWR, the controller (initiator) can measure the AoA elevation angle of RRM and send the measured AoA elevation angle through the UCI notification message. The controlled party (responder) can measure the AoA elevation angle of the RIM message and send the measured AoA elevation angle through RRRM.

[0087] In the case of OWR, the observer can measure the AoA azimuth and AoA elevation of the AoA measurement message.

[0088] Furthermore, in describing the present disclosure, a detailed description of known functions or configurations incorporated herein will be omitted when it is determined that the description may make the subject matter of the present disclosure unnecessarily unclear.

[0089] Hereinafter, various embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0090] Figure 1 is a block diagram schematically illustrating an electronic device.

[0091] exist Figure 1 In the embodiment of the present invention, the electronic device may be a UWB device or a non-UWB device.

[0092] refer to Figure 1, the electronic device 101 in the network environment 100 may communicate with the electronic device 102 via the first network 198 (e.g., a short-range wireless communication network), or communicate with the electronic device 104 or the server 108 via the second network 199 (e.g., a long-range wireless communication network). According to an embodiment, the electronic device 101 may communicate with the electronic device 104 via the server 108. According to an embodiment, the electronic device 101 may include a processor 120, a memory 130, an input module 150, a sound output module 155, a display module 160, an audio module 170, a sensor module 176, an interface 177, a connection terminal 178, a haptic module 179, a camera module 180, a power management module 188, a battery 189, a communication module 190, a subscriber identification module 196, or an antenna module 197. In some embodiments, at least one component (e.g., the connection terminal 178) may be omitted from the electronic device 101, or one or more other components may be added in the electronic device 101. In some embodiments, some components (eg, sensor module 176 , camera module 180 , or antenna module 197 ) may be integrated into a single component (eg, display module 160 ).

[0093] The processor 120 may execute, for example, software (e.g., program 140) to control at least one other component (e.g., hardware or software component) of the electronic device 101 coupled to the processor 120, and may perform various data processing or calculations. According to an embodiment, as at least part of the data processing or calculation, the processor 120 may store a command or data received from another component (e.g., sensor module 176 or communication module 190) in the volatile memory 132, process the command or data stored in the volatile memory 132, and store the resultant data in the non-volatile memory 134. According to an embodiment, the processor 120 may include a main processor 121 (e.g., a central processing unit (CPU) or an application processor (AP)) or an auxiliary processor 123 (e.g., a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor) that may operate independently of the main processor 121 or in conjunction with the main processor 121. For example, when the electronic device 101 includes a main processor 121 and an auxiliary processor 123, the auxiliary processor 123 may be adapted to consume less power than the main processor 121 or be dedicated to a designated function. The auxiliary processor 123 may be implemented separately from the main processor 121 or as part of the main processor 121.

[0094] When the main processor 121 is in an inactive (e.g., sleep) state, the auxiliary processor 123 may replace the main processor 121, or when the main processor 121 is in an active (e.g., executing an application) state, the auxiliary processor 123 may control, together with the main processor 121, at least some functions or states related to, for example, at least one of the components of the electronic device 101 (e.g., the display module 160, the sensor module 176, or the communication module 190). According to an embodiment, the auxiliary processor 123 (e.g., an image signal processor or a communication processor) may be implemented as a part of another component (e.g., a camera module 180 or a communication module 190) that is functionally related to the auxiliary processor 123. According to an embodiment, the auxiliary processor 123 (e.g., a neural processing unit) may include a hardware structure designated for artificial intelligence model processing. The artificial intelligence model may be generated by machine learning. Such learning may be performed, for example, by the electronic device 101 executing the artificial intelligence model or via a separate server (e.g., server 108). The learning algorithm may include, but is not limited to, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning. The artificial intelligence model may include a plurality of artificial neural network layers. The artificial neural network may be a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep brief network (DBN), a bidirectional recurrent deep neural network (BRDNN), a deep Q network, and a combination of two or more thereof, but is not limited to the above examples. Additionally or alternatively, in addition to the hardware structure, the artificial intelligence model may include a software structure.

[0095] The memory 130 may store various data used by at least one component of the electronic device 101 (e.g., the processor 120 or the sensor module 176). The various data may include, for example, input data or output data of software (e.g., the program 140) and commands related thereto. The memory 130 may include a volatile memory 132 or a nonvolatile memory 134.

[0096] The program 140 may be stored as software in the memory 130 , and may include, for example, an operating system (OS) 142 , middleware 144 , or an application 146 .

[0097] The input module 150 may receive a command or data to be used by another component (e.g., the processor 120) of the electronic device 101 from outside (e.g., a user) of the electronic device 101. The input module 150 may include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus).

[0098] The sound output module 155 can 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 playing back multimedia or recording. The receiver can be used to receive incoming calls. Depending on the embodiment, the receiver can be implemented as a part of the speaker or as a part of the speaker.

[0099] The display module 160 can visually provide information to the outside of the electronic device 101 (e.g., a user). The display module 160 may include, for example, a display, a holographic device, or a projector, and a control circuit for controlling a corresponding one of the display, the holographic device, and the projector. According to an embodiment, the display module 160 may include a touch sensor adapted to detect a touch, or a pressure sensor adapted to measure the strength of a force caused by a touch.

[0100] The audio module 170 may convert sound into an electrical signal, and vice versa. According to an embodiment, the audio module 170 may obtain sound via the input module 150, or output sound via the sound output module 155 or an external electronic device (e.g., electronic device 102 (e.g., speaker or earphone)) directly or wirelessly coupled to the electronic device 101.

[0101] The sensor module 176 may detect an operating state (e.g., power or temperature) of the electronic device 101 or an environmental state (e.g., a user's state) outside the electronic device 101, and then generate an electrical signal or data value corresponding to the detected state. According to an embodiment, the sensor module 176 may include, for example, a gesture sensor, a gyro sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illumination sensor.

[0102] The interface 177 may support one or more designated protocols to be used for direct or wireless coupling of the electronic device 101 with an external electronic device (e.g., the electronic device 102). According to an embodiment, the interface 177 may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.

[0103] The connection terminal 178 may include a connector via which the electronic device 101 may be physically connected to an external electronic device (eg, the electronic device 102). According to an embodiment, 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).

[0104] The haptic module 179 may convert the electrical signal into mechanical stimulation (eg, vibration or movement) or electrical stimulation, which the user may recognize through his sense of touch or kinesthetic sense. According to an embodiment, the haptic module 179 may include, for example, a motor, a piezoelectric element, or an electrical stimulator.

[0105] The camera module 180 may capture still images or moving images. According to an embodiment, the camera module 180 may include one or more lenses, image sensors, image signal processors, or flashes.

[0106] The power management module 188 may manage power supplied to the electronic device 101. According to an embodiment, the power management module 188 may be implemented as, for example, at least a part of a power management integrated circuit (PMIC).

[0107] The battery 189 may supply power to at least one component of the electronic device 101. According to an embodiment, the battery 189 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0108] The communication module 190 may support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device 101 and an external electronic device (e.g., electronic device 102, electronic device 104, or server 108), and perform communication via the established communication channel. The communication module 190 may include one or more communication processors that may operate independently of the processor 120 (e.g., an application processor) and support direct (e.g., wired) communication or wireless communication. According to an embodiment, the communication module 190 may include a wireless communication module 192 (e.g., 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 (e.g., a local area network (LAN) communication module or a power line communication (PLC) module). A corresponding one of these communication modules can communicate with the external electronic device 104 via a first network 198 (e.g., a short-range communication network such as Bluetooth™, wireless-fidelity (Wi-Fi) direct, or infrared data association (IrDA)) or a second network 199 (e.g., such as a traditional cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or a wide area network (WAN)). These various types of communication modules may be incorporated into a single component (e.g., a single chip), or may be implemented as multiple components (e.g., multiple chips) separated from each other. The wireless communication module 192 may identify or authenticate the electronic device 101 in a communication network such as the first network 198 or the second network 199 using subscriber information (e.g., an international mobile subscriber identity (IMSI)) stored in the subscriber identification module 196.

[0109] The wireless communication module 192 can support 5G networks and next-generation communication technologies after the 4G network, such as new radio (NR) access technology. NR access technology can support enhanced mobile broadband (eMBB), massive machine type communications (mMTC) or ultra-reliable and low-latency communications (URLLC). The wireless communication module 192 can support high-frequency bands (e.g., millimeter wave bands) to achieve, for example, high data transmission rates. The wireless communication module 192 can support various technologies for ensuring performance on high-frequency bands, such as, for example, beamforming, massive multiple-input multiple-output (massive MIMO), full-dimensional MIMO (full dimensional MIMO, FD-MIMO), array antennas, analog beamforming or massive antennas. The wireless communication module 192 can support various requirements specified in the electronic device 101, an external electronic device (e.g., an electronic device 104) or a network system (e.g., a second network 199). According to an embodiment, the wireless communication module 192 can support a peak data rate for implementing eMBB (e.g., 20 Gbps or higher), a coverage loss for implementing mMTC (e.g., 164 dB or lower), or a U-plane latency for implementing URLLC (e.g., 0.5 ms or lower for each of the downlink (DL) and uplink (UL), or 1 ms or lower for a round trip).

[0110] The antenna module 197 may transmit a signal or power to the outside of the electronic device 101 (e.g., an external electronic device), or receive a signal or power from the outside of the electronic device 101 (e.g., an external electronic device). According to an embodiment, the antenna module 197 may include an antenna including a radiating element formed of a conductive material or a conductive pattern formed in or on a substrate (e.g., a printed circuit board (PCB)). According to an embodiment, the antenna module 197 may include a plurality of antennas (e.g., an array antenna). In this case, for example, at least one antenna suitable for a communication scheme used in a communication network (such as the first network 198 or the second network 199) may be selected from the plurality of antennas by the communication module 190. The signal or power may then be transmitted or received between the communication module 190 and the external electronic device via the selected at least one antenna. According to an embodiment, another component (e.g., a radio frequency integrated circuit (RFIC)) other than the radiating element may be additionally formed as a part of the antenna module 197.

[0111] According to various embodiments, the antenna module 197 may form a millimeter wave antenna module. According to an embodiment, the millimeter wave antenna module may include a printed circuit board, an RFIC disposed at or adjacent to a first surface (e.g., a lower surface) of the printed circuit board and capable of supporting a specific high frequency band (e.g., a millimeter wave band), and a plurality of antennas (e.g., array antennas) disposed at or adjacent to a second surface (e.g., an upper surface or a side surface) of the printed circuit board and capable of transmitting or receiving signals in the specific high frequency band.

[0112] At least some of the above components can be coupled to each other via an inter-peripheral communication scheme (e.g., a bus, a general purpose input and output (GPIO), a serial peripheral interface (SPI), or a mobile industry processor interface (MIPI)) and communicate signals (e.g., commands or data) therebetween.

[0113] According to an embodiment, a command or data may be sent or received between the electronic device 101 and the external electronic device 104 via a server 108 coupled to the second network 199. Each of the external electronic devices 102 or 104 may be a device of the same type or a different type as the electronic device 101. According to an embodiment, all or some operations to be performed at the electronic device 101 may be performed at one or more of the external electronic devices 102, 104, or 108. For example, if the electronic device 101 should automatically or in response to a request from a user or another device to perform a function or service, the electronic device 101 may request one or more external electronic devices to perform at least a portion of the function or service instead of or in addition to performing the function or service. The one or more external electronic devices receiving the request may perform at least a portion of the requested function or service, or an additional function or additional service related to the request, and transmit the result of the execution to the electronic device 101. The electronic device 101 may provide a result with or without further processing of the result as at least a part of the reply to the request. To this end, for example, cloud computing, distributed computing, mobile edge computing (MEC) or client-server computing technology may be used. The electronic device 101 may use, for example, distributed computing or mobile edge computing to provide ultra-low latency services. In another embodiment, the external electronic device 104 may include an Internet of Things (IoT) device. The server 108 may be an intelligent server using machine learning and / or neural networks. According to an embodiment, the external electronic device 104 or the server 108 may be included in the second network 199. The electronic device 101 may be applied to smart services (e.g., smart homes, smart cities, smart cars, or healthcare) based on 5G communication technology or IoT-related technologies.

[0114] The electronic device according to the various embodiments set forth herein may be one of various types of electronic devices. The electronic device may include, for example, a portable communication device (e.g., a smart phone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a household appliance. The electronic device according to the embodiments of the present disclosure is not limited to those described above.

[0115] It should be understood that the various embodiments of the present disclosure and the terms used therein are not intended to limit the technical features set forth herein to specific embodiments, and the present disclosure includes various changes, equivalents or substitutes of the corresponding embodiments. Regarding the description of the accompanying drawings, similar reference numerals may be used to represent similar or related elements. The singular form of a noun corresponding to an item may include one or more items, unless the relevant context clearly indicates otherwise. As used herein, each of the phrases such as "A or B", "at least one of A and B", "at least one of A or B", "A, B or C", "at least one of A, B and C" and "at least one of A, B or C" may include any one or all possible combinations of the items listed together in the corresponding one of the phrases. Terms such as "first", "second", "first" and "second" may be used to simply distinguish the corresponding element from another element, and do not limit other aspects (e.g., importance or order) of the element. If an element (e.g., a first element) is referred to as being “coupled” / “coupled to” another element (e.g., a second element) or “connected to” / “with” another element (e.g., a second element), whether or not there is the term “operably” or “communicatively”, it means that the element may be coupled / connected / coupled to / connected to the other element directly (e.g., wired), wirelessly, or via a third element.

[0116] As used in various embodiments of the present disclosure, the term "module" may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with other terms, such as "logic", "logic block", "component", or "circuit". A "module" may be a single integrated component or its smallest unit or part suitable for performing one or more functions. For example, according to an embodiment, a "module" may be implemented in the form of an application-specific integrated circuit (ASIC).

[0117] The various embodiments set forth herein may be implemented as software (e.g., program 140) that includes one or more instructions stored in a storage medium (e.g., internal memory 136 or external memory 138) readable by a machine (e.g., electronic device 101). For example, a processor (e.g., processor 120) of a machine (e.g., electronic device 101) may call at least one of the one or more instructions stored in the storage medium and execute it. This allows the machine to be operated to perform at least one function according to the at least one instruction called. Each of the one or more instructions may include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, the term "non-transitory" simply means that the storage medium is a tangible device and does not include signals (e.g., electromagnetic waves), but the term does not distinguish between a case where data is semi-permanently stored in a storage medium and a case where data is temporarily stored in a storage medium.

[0118] According to an embodiment, the method according to various embodiments of the present disclosure may be included and provided in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., a compact disc read only memory (CD-ROM)), or distributed online (e.g., downloaded or uploaded) via an application store (e.g., Play Store TM), or distributed directly between two user devices (e.g., smart phones). If distributed online, at least a portion of the computer program product may be temporarily generated or at least temporarily stored in a machine-readable storage medium, such as a memory of a manufacturer's server, an application store's server, or a relay server.

[0119] According to various embodiments, each of the above-mentioned elements (e.g., a module or a program) may include a single entity or multiple entities, and some of the multiple entities may be arranged separately in another element. According to various embodiments, one or more of the above-mentioned elements or operations may be omitted, or one or more other elements or operations may be added. Alternatively or additionally, multiple elements (e.g., a module or a program) may be integrated into a single element. In this case, according to various embodiments, the integrated element may still perform one or more functions of each of the multiple elements in the same or similar manner as performed by a corresponding one of the multiple elements before integration. According to various embodiments, the operations performed by a module, a program or another element may be performed sequentially, in parallel, repeatedly or heuristically, or one or more of the operations may be performed or omitted in a different order, or one or more other operations may be added.

[0120] Figure 2a An exemplary architecture of a UWB device is shown.

[0121] In the present disclosure, the UWB device 200 may be an electronic device supporting UWB communication. Figure 1 The UWB device 200 may be, for example, a ranging device (RDEV) supporting UWB ranging. In an embodiment, the ranging device may be an enhanced ranging device (ERDEV) defined in IEEE 802.15.4z or a FiRa device defined by the FiRa standard.

[0122] exist Figure 2a In the embodiment of the present invention, the UWB device 200 can interact with another UWB device through a UWB session.

[0123] In addition, the UWB device 200 may implement a first interface (Interface #1), which is an interface between the UWB-enabled application 210 and the UWB framework 220, and the first interface enables the UWB-enabled application 210 on the UWB device 200 to use the UWB capability of the UWB device 200 in a predetermined scheme. In an embodiment, the first interface may be a framework API or a proprietary interface, but is not limited thereto.

[0124] In addition, the UWB device 200 may implement a second interface (Interface #2), which is an interface between the UWB framework 210 and the UWB subsystem (UWBS) 230. In an embodiment, the second interface may be a UWB command interface (UCI) or a proprietary interface, but is not limited thereto.

[0125] refer to Figure 2a , the UWB device 200 may include a UWB-enabled application 210, a framework (UWB framework) 220, and / or a UWBS 230 including a UWB MAC layer and a UWB physical layer. Depending on the embodiment, some entities may not be included in the UWB device, or additional entities (eg, a security layer) may be further included.

[0126] The UWB-enabled application 210 can trigger the UWBS 230 to establish a UWB session by using the first interface. In addition, the UWB-enabled application 210 can use one of the predefined profiles. For example, the UWB-enabled application 210 can use one of the profiles defined in the FiRa standard or a custom profile. The UWB-enabled application 210 can use the first interface to handle related events such as service discovery, ranging notifications, and / or error conditions.

[0127] The framework 220 may provide access to profiles, individual UWB configurations, and / or notifications. In addition, the framework 220 may support at least one of a function for performing UWB ranging and transactions, a function for providing an interface to applications and the UWBS 230, and a function for estimating the location of the UWB device 200. The framework 220 may be a set of software components. As described above, the UWB-enabled application 210 may interface with the framework 220 via a first interface, and the framework 220 may interface with the UWBS 230 via a second interface.

[0128] Meanwhile, in the present disclosure, the UWB-enabled application 210 and / or the framework 220 may be implemented by an application processor (AP) (or a processor). Therefore, in the present disclosure, the operation of the UWB-enabled application 210 and / or the framework 220 may be understood to be performed by the AP (or a processor). In the present disclosure, the framework may be referred to as an AP or a processor.

[0129] UWBS 230 may be a hardware component including a UWB MAC layer and a UWB physical layer. UWBS 230 may perform UWB session management and communicate with the UWBS of another UWB device. UWBS 230 may interface with framework 220 through a second interface and obtain security data from a security component. In an embodiment, framework (or application processor) 220 may send a command to UWBS 230 through UCI, and UWBS 230 may transmit a response to the command to framework 220. UWBS 230 may transmit a notification to framework 220 through UCI.

[0130] Figure 2b An exemplary configuration of a framework of a UWB device is shown.

[0131] Figure 2b The framework of the UWB device of FIG. 2A may be an example of the framework of the UWB device of FIG. 2A .

[0132] refer to Figure 2b , the framework 220 may include, for example, software components such as a profile manager 221 , an OOB connector 222 , a security service 223 , and / or a UWB service 224 .

[0133] The profile manager 221 may be used to manage the profiles available on the UWB device. The profile may be a set of parameters required to establish communication between UWB devices. For example, the profile may include parameters indicating which OOB secure channel to use, UWB / OOB configuration parameters, parameters indicating whether the use of a specific security component is mandatory, and / or parameters related to the file structure of the ADF. The UWB-enabled application 210 may communicate with the profile manager 221 via a first interface (e.g., a framework API).

[0134] The OOB connector 222 may be used to establish an OOB connection with another device. The OOB connector 222 may process an OOB procedure including a discovery procedure and / or a connection procedure. An OOB component (eg, a BLE component) 250 may be connected to the OOB connector 222 .

[0135] The security service 223 may be used to interface with a security component 240 such as a SE or a TEE.

[0136] The UWB service 224 may be used to manage the UWBS 230. The UWB service 224 may provide access from the profile manager 221 to the UWBS 230 by implementing a second interface.

[0137] Figure 3 An exemplary configuration of a communication system including a UWB device is shown.

[0138] refer to Figure 3 , the communication system 300 includes a first UWB device 310 and a second UWB device 320. In an embodiment, the first UWB device 310 and the second UWB device 320 may be, for example, the UWB devices of FIG. 2 or electronic devices including the UWB devices of FIG.

[0139] For example, the first UWB device 310 may host one or more UWB-enabled applications 311, which may be installed by a user (e.g., a mobile phone). This may be based on, for example, a framework API. The second UWB device 320 may not provide a framework API, and may use, for example, a proprietary interface to implement a specific UWB-enabled application. Also, unlike what is shown, depending on the embodiment, the first UWB device 310 and the second UWB device 320 may both be ranging devices using a framework API, or the first UWB device 310 and the second UWB device 320 may both be ranging devices using a proprietary interface.

[0140] The first UWB device 310 and the second UWB device 320 may include UWB-enabled application layers 311 and 321, frameworks 312 and 322, OOB components 313 and 323, security components 314 and 324, and / or UWBS 315 and 325. Meanwhile, in the present disclosure, the OOB component 313 or 323 and / or the security component 314 or 324 are optional components and may not be included in the UWB device depending on the embodiment.

[0141] The framework 312 or 322 may be used to provide access to profiles, individual UWB configurations, and / or notifications. The framework 312 or 322 may be a set of software components and may include, for example, a profile manager, an OOB connector, a security service, and / or a UWB service. The description of each component is referred to above.

[0142] The OOB component 313 or 323 may be a hardware component including a MAC layer and / or a physical layer for OOB communication (e.g., BLE communication). The OOB component 313 or 323 may communicate with an OOB component of another device. In an embodiment, the first UWB device 310 and the second UWB device 320 may generate an OOB connection (channel) by using the OOB components 313 and 323, and exchange parameters for establishing a UWB session through the OOB channel. In the present disclosure, the OOB component 313 or 323 may be referred to as an OOB subsystem.

[0143] The security component 314 or 324 may be a hardware component that interfaces with the framework and / or UWBS to provide the RDS.

[0144] The UWBS 315 or 325 may be a hardware component including a UWB MAC layer and a UWB physical layer. The UWBS 315 or 325 may perform UWB session management and communicate with the UWB of another UWB device. In an embodiment, the first UWB device 310 and the second UWB device 320 may perform transactions of service data and UWB ranging through a UWB session established via the UWBS using exchanged parameters.

[0145] As described above, in the present disclosure, the UWB-enabled application layer 311 or 321 and / or the framework 312 or 322 may be implemented by an application processor (AP) (or a processor). Therefore, in the present disclosure, the operation of the UWB-enabled application layer 311 or 321 and / or the framework 312 or 322 may be understood to be performed by the AP (or a processor).

[0146] Figure 4 A UWB ranging operation between UWB devices is shown.

[0147] Figure 4 The UWB device 41 or 42 may be Figures 1 to 3 The UWB device shown is, but not limited to, and may be various types of electronic devices supporting UWB ranging.

[0148] exist Figure 4 In the embodiment of the present invention, the first UWB device 41 may be a ranging device that initiates ranging exchange by sending a first ranging frame (ranging initiation message). In the present disclosure, the first UWB device 41 may be referred to as an initiator.

[0149] The second UWB device 42 may be a ranging device that responds to a ranging initiation message received from an initiator. In the present disclosure, the second UWB device 42 may be referred to as a responder. In an embodiment, a responder may send a ranging response message.

[0150] In an embodiment, the first UWB device 41 may be a controller, and the second UWB device 42 may be a controlled device. The reverse may also be true. Here, the controller may be a ranging device that defines and controls ranging features by sending control messages. The controlled device may be a ranging device that uses ranging features configured by control messages from the controller.

[0151] In an embodiment, the first UWB device 41 and the second UWB device 42 may perform a ranging operation by using a preconfigured ranging method. In an embodiment, the ranging method may include a two-way ranging (two-way ranging, TWR) method and / or a one-way ranging (one-way ranging, OWR) method. In an embodiment, the TWR method may include a single-sided two-way ranging (single-sided two-way ranging, SS-TWR) and / or a double-sided two-way ranging (double-sided two-way ranging, DS-TWR). This ranging method refers to the description of the IEEE 802.15.4 / 4z standard and the FiRa standard that refers to the standard.

[0152] refer to Figure 4 , to explain TWR, in operation 410 , the first UWB device 41 may transmit a ranging initiation message to the second UWB device 42 .

[0153] In operation 410, the second UWB device 42 may send a ranging response message to the first UWB device 41. As an embodiment, the ranging response message may be generated based on the ranging initiation message. Through this exchange operation of the UWB ranging message, the first UWB device 41 and / or the second UWB device 42 may obtain distance information and / or direction information, and identify the relative position and / or direction of the UWB device based on the distance information and / or direction information. This is described with reference to the IEEE 802.15.4 / 4z standard and the FiRa standard with reference to the standard. At the same time, in the case of the DS-TWR method, the first UWB device 41 may further send a ranging final message to the second UWB device 42.

[0154] In an embodiment, the distance information may include time of flight (ToF) information (ToF measurement information). ToF corresponds to the UWB propagation time between a transmitter and a receiver. By using accurate message timestamps, ToF can provide an accurate estimate of the relative distance between two devices. ToF information may be measured by one or two ranging devices and exchanged between an initiator and a responder via a predefined signaling scheme (e.g., a control message including a UWB ranging result).

[0155] In an embodiment, the direction information may include angle of arrival (AoA) information (AoA measurement information). AoA may be obtained by measuring the phase difference or arrival time difference of the arriving signal at the antenna. AoA information may include AoA azimuth (horizontal angle) and AoA elevation (vertical angle). AoA information may be used together with ToF information to determine the relative position of the UWB device. AoA information may be measured by one or two ranging devices and exchanged between the initiator and the responder through a predefined signaling scheme (e.g., a control message including the UWB ranging result).

[0156] Hereinafter, various embodiments of a method of recognizing and controlling a non-UWB supporting device by using a UWB tag device and UWB ranging are described with reference to each accompanying drawing.

[0157] In the present disclosure, various embodiments of the present disclosure are described assuming that at least two UWB supporting devices are UWB devices supporting UWB ranging, and the other is a user device (e.g., a user's smartphone) supporting UWB ranging. However, the present disclosure is not limited thereto, and the UWB supporting device may be various electronic devices supporting UWB ranging. In an embodiment, the UWB device and the user device may be Figures 1 to 4 The UWB device illustrated in FIG.

[0158] In the present disclosure, a user device supporting UWB ranging may be referred to as a UWB user device, a user device, a first UWB supporting device, or a first UWB device. In addition, a UWB device supporting UWB ranging may be referred to as a UWB tag device, a tag device, a second UWB supporting device, or a second UWB device.

[0159] In the present disclosure, a non-UWB supporting device is a device controlled by a UWB supporting device (eg, a user device), and may be referred to as a target device or a non-UWB device.

[0160] Figure 5 A method according to an embodiment of the present disclosure is shown, in which a UWB supporting device identifies and controls a non-UWB supporting device.

[0161] Figure 5 The embodiment discloses a method in which a UWB user device (or user equipment) 510 (e.g., a user's smart phone) points to and controls a target device 530 (e.g., an air conditioner) which is a non-UWB supporting device by using UWB ranging results with at least two UWB devices 520a and 520b (e.g., UWB tag devices).

[0162] As an example, the UWB ranging operation between the user device 510 and the UWB tag devices 520a and 520b may follow Figure 4 UWB ranging operations. For example, you can perform Figure 4 The UWB ranging operation of the OWR or TWR method of the present invention can be performed. In this case, the user device 510 can act as an initiator and the reference device 520 can act as a responder. In addition, the opposite situation is also possible. In addition, the user device can perform ranging by using the signals received from the UWB tag devices 520a and 520b.

[0163] exist Figure 5 In an embodiment of the present invention, the user device 510 can be used to identify the approximate location of the target device 530 by pointing to a point on the target device 530, and point to and control the target device 530 based on the approximate location. Figure 5 In the embodiment of the present invention, the user device 510 needs to know the distance between the user device 510 and the target device 530 in order to point to and control the target device 530. As an embodiment, the user device 510 can directly measure the distance to the target device 530 by using functions such as ToF / Radar. In addition, when the distance cannot be measured directly, the user guide can enable the user device 510 to use the functions proposed in the present application within a certain distance, thereby determining the distance between the target device 530 and the user device 510.

[0164] Hereinafter, an embodiment of a method in which a UWB device identifies and controls a non-UWB supporting device by using at least two UWB tag devices is described.

[0165] Figure 6 A method for a UWB supporting device to identify and control a location of a non-UWB supporting device according to another embodiment of the present disclosure is shown.

[0166] Figure 6 An embodiment of the present invention discloses a method in which a user device 610 (e.g., a user's smart phone) as a UWB device identifies the location of a target device 630 (e.g., an electronic device such as an air conditioner) as a non-UWB supporting device by using UWB ranging with multiple UWB tag devices 620a and 620b (or at least two UWB tag devices). Figure 6 The UWB user device 610 and at least two UWB tag devices 620a and 620b may be Figures 1 to 4 The at least two UWB tag devices may include a first UWB tag device 620a and a second UWB tag device 620b.

[0167] As an example, the UWB ranging operation between the user device 610 and the plurality of UWB tag devices 620a and 620b may follow Figure 4 OWR ranging or UWB ranging operation. For example, you can perform Figure 4 In this case, the user device 610 may act as an initiator, and the UWB tag devices 620a and 620b may act as responders. In addition, the opposite situation is also possible.

[0168] exist Figure 6 In the embodiment of the present invention, it is assumed that the user device 610 is located at a distance "d" from the target device 630 and is provided to the user. The distance from the target device 630 can be identified as a two-dimensional distance and can be known in advance through the user guide. The user guide can be configured so that various embodiments of the application for identifying the location of the target device 630 can be applied from the time when the user device 610 is located at a distance "d" from the target device 930.

[0169] exist Figure 6 In an embodiment, at least two UWB tag devices 620a and 620b may be required. Each of the UWB tag devices 620a and 620b may include a single antenna for UWB communication, and UWB ranging may not need to be performed between the UWB tag devices 620a and 620b. The user device 610 may include an inertial measurement unit (IMU) (inertial sensor). In addition, the user device 610 may measure the angle of arrival (AoA) (azimuth AoA measurement is possible) by including multiple antennas for UWB communication. When the reception angle of the signal cannot be measured using only AoA, a gyroscope can be used to measure angular acceleration to supplement the angle calculation.

[0170] refer to Figure 6 , the user device 610 can perform UWB ranging with multiple UWB tag devices 620a and 620b. For example, the user device 610 can perform UWB ranging in the TWR method and / or the OWR method with multiple UWB tag devices 620a and 620b. Through the UWB ranging in the TWR method, the user device 610 can calculate the distances l1 and l2 to the multiple UWB tag devices 620a and 620b, respectively. Assuming that the distance between the user device 610 and the target device 630 is known, the user device 610 can identify all distances to the multiple UWB tag devices 620a and 620b and the target device 630.

[0171] In an embodiment, the user device 610 may calculate its own position by communicating with the UWB tag devices 620a and 620b. The user device 610 may measure the AoA (AoA) of each of the plurality of UWB tag devices 620a and 620b by using the signals received from the plurality of UWB tag devices 620a and 620b. , ). For example, the user device 610 may measure the AoA of each of the plurality of UWB tag devices 620a and 620b by using a signal received from the plurality of UWB tag devices 620a and 620b in a UWB ranging process in a TWR or OWR method ( , ). By using the obtained AoA, the user device 610 can calculate the angles between the plurality of UWB tag devices 620a and 620b and the user device 610 ( ), as shown in Equation 1.

[0172] [Equation 1]

[0173]

[0174] The user device 610 may calculate the angle ( ), and calculates the distance between the first UWB tag device and the second UWB tag device by using the distances l1 and l2 between the user device 610 and each of the plurality of UWB tag devices 620a and 620b, as shown in Equation 2.

[0175] [Equation 2]

[0176]

[0177] exist Figure 6 In the example, the position of the user equipment 610 is set to P, and the position of the first UWB tag device is set to F 1 , the position of the second UWB tag device is set to F 2 , and the position of the target device is set to T. Because the triangle (△PF) formed by the user device 610 and the plurality of UWB tag devices 620a and 620b 1 F 2 ) are identified, so the lengths of the three sides of the triangle (△PF 1 F 2 ) at all angles.

[0178] For example, the angle at which the first UWB tag device 620a observes the user device 610 ( ) can be calculated based on the distance between the devices and is shown in Equation 3.

[0179] [Equation 3]

[0180]

[0181] In addition, the angle at which the second UWB tag device 620b observes the user device 610 may also be calculated in a manner similar to Equation 3.

[0182] By using the angle obtained by Equation 3 and the distance between the devices, the coordinates (or position) of the user device 610 can be determined using the first UWB tag device 620a as the origin, as shown in Figure 6 If the coordinates are expressed in polar coordinates, the position of the user device 610 can be expressed as , and if expressed using the obtained distance and angle, the position can be expressed as (Here is ). When displayed in a rectangular coordinate system, the calculated polar coordinates of the user device 610 may appear as shown in Equation 4.

[0183] [Equation 4]

[0184]

[0185] refer to Figure 6 , the user device 610 may calculate the position of the target device 630 based on the calculated position of the user device 610. In order to calculate the position of the target device 630 by using a vector, a vector from the first UWB tag device 620a set as the origin to the target device 630 is obtained, which may be expressed as in Equation 5.

[0186] [Equation 5]

[0187]

[0188] To calculate Equation 5, we need to calculate and First, in order to obtain the vector to the target device 630 using the user device 610 as a reference point, the vector By using the first UWB tag device 620a to observe the angle of the user device 610 ( ) and the obtained AoA value To determine the angle . The distance between the user device 610 and the target device 630 and the obtained angle ( ) The calculation in Equation 6 is performed according to the vector formula.

[0189] [Equation 6]

[0190]

[0191] Next, due to is the vector value from the first UWB tag device 620a set as the origin to the user device 610, so it can be determined using the coordinates of the user device 610 obtained in advance. Therefore, it can be determined as .

[0192] Therefore, by applying the obtained value to Equation 5, calculation as in Equation 7 can be performed.

[0193] [Equation 7]

[0194]

[0195] The user device 610 may identify the position of the target device 630 relative to the user device 610 through a series of calculations described in this embodiment, and when the position is identified, the user device may perform an operation for controlling the target device 630 .

[0196] Through such a registration process, the location of the target device 630 can be identified with reference to the location (reference location) of the user device 610. The location of the target device 630 identified in this way can be stored and used in a recognition procedure performed later.

[0197] In various embodiments according to the present disclosure, the user device 610 may perform UWB ranging with at least two UWB tag devices 620a and 620b (or UWB anchor devices). The user device 610 may receive signals from the at least two UWB tag devices 620a and 620b, and calculate the AoA and the distance to the at least two UWB tag devices 620a and 620b. The user device 610 may measure the distance between the at least two UWB tag devices 620a and 620b by using the calculated AoA and the distance to the at least two UWB tag devices 620a and 620b. The user device 610 may calculate the angle formed by the first UWB tag device 620a and the user device 610 based on the measured distance between the at least two UWB tag devices 620a and 620b. The user device 610 may calculate its own position based on the calculated angle.

[0198] In various embodiments according to the present disclosure, the user device 610 may calculate its own position to calculate the position of the target device 630 by calculating the vector from the user device 610 to the target device 630. In this case, the distance from the target device 630 to the user device 610 may have been determined by the user guide, and the user device 610 may know the distance. In order to determine the position of the target device 630, the user device 610 may calculate the vector from the first UWB tag device 620a to the user device 610, and calculate the vector from the user device 610 to the target device 610 to obtain the sum of the vectors.

[0199] Figure 7 is a diagram showing a structure of an electronic device according to an embodiment of the present disclosure.

[0200] exist Figure 7In an embodiment, the electronic device may be a UWB device (eg, a user device (or a first UWB device) or a UWB tag device (or a second UWB device) as described in the present disclosure) or a non-UWB device (eg, a target device as described in the present disclosure).

[0201] refer to Figure 7 , the electronic device may include a transceiver 710 and a controller 720. In the present disclosure, the controller 720 may be defined as a circuit or an application specific integrated circuit, or at least one processor.

[0202] The transceiver 710 may send or receive a signal to or from another network entity or electronic device (eg, a UWB device, a UWB tag device, or a non-UWB device). For example, the transceiver 710 may send or receive data for UWB ranging by using UWB communication.

[0203] According to various embodiments proposed in the present disclosure, the controller 720 may control the overall operation of the electronic device. Specifically, the controller 720 may control the reference Figures 1 to 6 Describe the operation of an electronic device.

[0204] Although not shown, the electronic device may include a storage unit. The storage unit may store at least one of information transmitted or received by the transceiver 710 and information generated by the controller 720. For example, the storage unit may store information generated using the reference signal. Figures 1 to 6 Describes the information and data required for UWB registration and identification of non-UWB devices.

[0205] Figure 8 is a flowchart illustrating a method of a first UWB device according to an embodiment of the present disclosure.

[0206] exist Figure 8 In an embodiment of the present invention, the first UWB device may correspond to the above-mentioned user device, the second UWB device may correspond to the above-mentioned UWB tag device, and the non-UWB device may correspond to the above-mentioned target device.

[0207] refer to Figure 8 , the first UWB device may identify a location of the non-UWB device based on UWB ranging between the first UWB device and each of the at least two second UWB devices ( 810 ).

[0208] As an embodiment, the result of UWB ranging between the first UWB device and each of the at least two second UWB devices may include angle of arrival (AoA) information and information about the distance between the first UWB device and each of the at least two second UWB devices.

[0209] As an embodiment, the first UWB device may identify the distance between the first UWB device and the non-UWB device based on pre-configured information.

[0210] As an embodiment, identifying the location of a non-UWB device may include: calculating the distance between at least two second UWB devices; calculating the angle of the first UWB device relative to the location of a UWB device that is one of the at least two second UWB devices based on the distance between the at least two second UWB devices; and identifying the location of the first UWB device relative to the UWB device that is one of the at least two second UWB devices based on the calculated angle of the first UWB device.

[0211] As an embodiment, the method may include: calculating a vector from a first UWB device to a non-UWB device; calculating a vector from a UWB device that is one of at least two second UWB devices to the first UWB device; calculating the sum of the calculated vectors; and based on the sum of the vectors, identifying a position of the non-UWB device relative to the UWB device that is one of the at least two second UWB devices.

[0212] As an embodiment, the at least two second UWB devices may be UWB tag devices.

[0213] As an embodiment, UWB ranging may be performed based on a one-way ranging (OWR) method.

[0214] As an embodiment, the first UWB device may include a transceiver and at least one processor connected to the transceiver, wherein the at least one processor may be configured to: identify the location of a non-UWB device based on UWB ranging between the first UWB device and each of at least two second UWB devices, and control the non-UWB device based on the location of the non-UWB device.

[0215] As an embodiment, at least one processor may be configured to: calculate the distance between at least two second UWB devices, calculate the angle of the first UWB device relative to the position of a UWB device that is one of the at least two second UWB devices based on the distance between the at least two second UWB devices, and identify the position of the first UWB device relative to the UWB device that is one of the at least two second UWB devices based on the calculated angle of the first UWB device.

[0216] As an embodiment, at least one processor may be further configured to: calculate a vector from the first UWB device to the non-UWB device, calculate a vector from the UWB device that is one of the at least two second UWB devices to the first UWB device, calculate the sum of the calculated vectors, and based on the sum of the vectors, identify the position of the non-UWB device relative to the UWB device that is one of the at least two second UWB devices.

[0217] In the above detailed embodiments of the present disclosure, the elements included in the present disclosure are expressed in the singular or plural, depending on the detailed embodiments presented. However, for the convenience of description, the singular form or the plural form is appropriately selected as the presented situation, and the present disclosure is not limited to the elements expressed in the singular or plural. Therefore, the elements expressed in the plural may also include a single element, or the elements expressed in the singular may also include multiple elements.

[0218] Although specific embodiments have been described in the detailed description of the present disclosure, it is apparent that various modifications and changes may be made thereto without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be defined as being limited to the embodiments set forth herein, but should be defined by the appended claims and their equivalents.

Claims

1. A method of a first UWB device, the method comprising: identifying a location of a non-UWB device based on UWB ranging between the first UWB device and each of at least two second UWB devices; as well as Based on the location of the non-UWB device, the non-UWB device is controlled.

2. The method according to claim 1, wherein: A result of the UWB ranging between the first UWB device and each of the at least two second UWB devices includes angle of arrival (AoA) information and information about a distance between the first UWB device and each of the at least two second UWB devices.

3. The method according to claim 2, wherein: The first UWB device is configured to identify a distance between the first UWB device and the non-UWB device based on preconfigured information.

4. The method according to claim 3, wherein: The identifying the location of the non-UWB device comprises: Calculating a distance between the at least two second UWB devices; calculating an angle of the first UWB device relative to a position of a UWB device based on a distance between the at least two second UWB devices, the UWB device being one of the at least two second UWB devices; and Based on the calculated angle of the first UWB device, a position of the first UWB device relative to the UWB device is identified, the UWB device being one of the at least two second UWB devices.

5. The method according to claim 4, further comprising: Calculating a vector from the first UWB device to the non-UWB device; Calculating a vector from the UWB device to the first UWB device, the UWB device being one of the at least two second UWB devices; Calculating the sum of the calculated vectors; and Based on the sum of the vectors, a position of the non-UWB device relative to the UWB device is identified, the UWB device being one of the at least two second UWB devices.

6. The method according to claim 1, wherein: The at least two second UWB devices are UWB tag devices.

7. The method according to claim 1, wherein: The UWB ranging is performed based on a One-Way Ranging (OWR) method.

8. A first UWB device comprising: Transceiver; as well as at least one processor connected to said transceiver, Wherein, the at least one processor is configured to: identifying a location of a non-UWB device based on UWB ranging between the first UWB device and each of at least two second UWB devices; and Based on the location of the non-UWB device, the non-UWB device is controlled.

9. The first UWB device according to claim 8, wherein: A result of the UWB ranging between the first UWB device and each of the at least two second UWB devices includes angle of arrival (AoA) information and information about a distance between the first UWB device and each of the at least two second UWB devices.

10. The first UWB device according to claim 9, wherein: The first UWB device is configured to identify a distance between the first UWB device and the non-UWB device based on preconfigured information.

11. The first UWB device according to claim 10, wherein: The at least one processor is configured to: Calculating a distance between the at least two second UWB devices; calculating an angle of the first UWB device relative to a position of a UWB device based on a distance between the at least two second UWB devices, the UWB device being one of the at least two second UWB devices; and Based on the calculated angle of the first UWB device, a position of the first UWB device relative to the UWB device is identified, the UWB device being one of the at least two second UWB devices.

12. The first UWB device according to claim 11, wherein: The at least one processor is further configured to: Calculating a vector from the first UWB device to the non-UWB device; Calculating a vector from the UWB device to the first UWB device, the UWB device being one of the at least two second UWB devices; Calculating the sum of the calculated vectors; and Based on the sum of the vectors, a position of the non-UWB device relative to the UWB device is identified, the UWB device being one of the at least two second UWB devices.

13. The first UWB device according to claim 8, wherein: The at least two second UWB devices are UWB tag devices.

14. The first UWB device according to claim 8, wherein: The UWB ranging is performed based on a One-Way Ranging (OWR) method.

Images