Method and apparatus for UWB communication

Abstract

The present disclosure provides a service started using UWB OWR and a user gesture input method. According to various embodiments of the present disclosure, a method of an ultra wide band (UWB) device comprises the steps of: receiving, from a second UWB device, a first UWB announcement message for measuring an angle of arrival (AoA) with a third UWB device, the UWB announcement message being a message for UWB one-way ranging (OWR) and including information on a transmission period of the UWB announcement message; and determining a mode for recognizing a user gesture input of the first UWB device based on the information on the transmission period, wherein the mode for recognizing the user gesture input may be one of a first mode using UWB OWR in order to recognize the user gesture input and a second mode using both UWB OWR and UWB bidirectional ranging (TWR) with a third UWB device in order to recognize the user gesture input.

Description

Technical Field

[0001] The present disclosure relates to UWB communications, and more particularly, to a method and apparatus for providing service initiation and user gesture input using UWB One-Way Ranging (OWR). Background Art

[0002] The Internet is evolving into the Internet of Things (IoT), where distributed entities (i.e., things) exchange and process information without human intervention. The Internet of Everything (IoE) has emerged through a combination of IoT technology and big data processing technology connected to a cloud server. Since IoT implementation requires technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology", and "security technology", sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), etc. are being studied.

[0003] The IoT environment can provide intelligent Internet technology services by collecting and analyzing data generated between connected things. IoT can be applied to a variety of fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, health care, smart appliances and advanced medical services, through the integration and combination of existing information technology (IT) and various industrial applications.

[0004] As various services can be provided with the development of wireless communication systems, methods for efficiently providing these services are also needed. For example, ranging technology for measuring the distance between electronic devices using UWB can be used. Summary of the invention

[0005] Technical issues

[0006] The present disclosure provides a method and apparatus for providing service initiation using UWB OWR and user gesture input.

[0007] Technical Solutions

[0008] A method of an ultra-wideband (UWB) device according to one aspect of the present disclosure may include the following steps: receiving a UWB announcement message for measuring an angle of arrival (AoA), wherein the UWB announcement message is a message for UWB one-way ranging (OWR) and includes information about a transmission period of the UWB announcement message; and determining a scheme for identifying a user gesture input of the UWB device based on the information about the transmission period, and the scheme for identifying the user gesture input may be one of a first scheme for identifying the user gesture input using UWB OWR and a second scheme for identifying the user gesture input using both UWB OWR and UWB two-way ranging (TWR) with another UWB device.

[0009] An ultra-wideband (UWB) device according to another aspect of the present disclosure may include a transceiver and a controller, wherein the controller may be configured to: receive a UWB announcement message for measuring an angle of arrival (AoA), wherein the UWB announcement message is a message for UWB one-way ranging (OWR) and includes information about a transmission period of the UWB announcement message; and determine a scheme for identifying a user gesture input of the UWB device based on the information about the transmission period, and the scheme for identifying the user gesture input is one of a first scheme for identifying the user gesture input using UWB OWR and a second scheme for identifying the user gesture input using both UWB OWR and UWB two-way ranging (TWR) with another UWB device.

[0010] A method of a first ultra-wideband (UWB) device according to an aspect of the present disclosure may include the following steps: receiving a first UWB announcement message from a second UWB device for measuring an angle of arrival (AoA) with a third UWB device, wherein the UWB announcement message is a message for UWB one-way ranging (OWR) and includes information about a transmission period of the UWB announcement message; and determining a scheme for identifying a user gesture input of the first UWB device based on the information about the transmission period, and the scheme for identifying the user gesture input may be one of a first scheme for identifying the user gesture input using UWB OWR and a second scheme for identifying the user gesture input using both UWBOWR and UWB two-way ranging (TWR) with a third UWB device.

[0011] According to another aspect of the present disclosure, a first ultra-wideband (UWB) device may include a transceiver and a controller, wherein the controller may be configured to: receive a first UWB announcement message for measuring an angle of arrival (AoA) with a third UWB device from a second UWB device, wherein the UWB announcement message is a message for UWB one-way ranging (OWR) and includes information about a transmission period of the UWB announcement message; and determine a scheme for identifying a user gesture input of the first UWB device based on the information about the transmission period, and the scheme for identifying the user gesture input is one of a first scheme for identifying the user gesture input using UWB OWR and a second scheme for identifying the user gesture input using both UWB OWR and UWB two-way ranging (TWR) with a third UWB device. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 An example structure of a UWB device according to an embodiment of the present disclosure is shown.

[0013] Figure 2 An example configuration of a framework of a UWB device according to an embodiment of the present disclosure is shown.

[0014] Figure 3 A method for performing communication by a plurality of electronic devices according to an embodiment of the present disclosure is illustrated.

[0015] Figure 4 The structure of a UWB MAC frame according to an embodiment of the present disclosure is shown.

[0016] FIG5 shows the structure of a UWB PHY packet according to an embodiment of the present disclosure.

[0017] Figure 6 An example of the structure of a ranging block and a loop for UWB ranging according to an embodiment of the present disclosure is shown.

[0018] Figure 7 A system for providing service initiation using UWB OWR and user gesture input according to an embodiment of the present disclosure is shown.

[0019] Fig. 8A A method for an electronic device to recognize a user gesture input by using a first scheme according to an embodiment of the present disclosure is illustrated.

[0020] Figure 8B A method for an electronic device to recognize a user gesture input by using a second scheme according to an embodiment of the present disclosure is illustrated.

[0021] Fig. 9A , Fig. 9B and Fig. 9C A method for an electronic device to recognize a user gesture input based on AoA information according to a first solution according to an embodiment of the present disclosure is shown.

[0022] Fig. 10A and Fig. 10B A method for an electronic device to recognize a user gesture input based on AoA information according to a second solution according to an embodiment of the present disclosure is shown.

[0023] Fig.11 An exemplary process of a method for an electronic device to recognize a user gesture input based on AoA information according to a second solution according to an embodiment of the present disclosure is shown.

[0024] Fig.12 A flowchart of a method for an electronic device to recognize a user gesture input based on AoA information according to a first solution according to an embodiment of the present disclosure is shown.

[0025] Fig.13 Shown according to Fig.12 An exemplary operation of the method.

[0026] Fig.14A flowchart of a method for an electronic device to recognize a user gesture input based on AoA information according to a second solution according to an embodiment of the present disclosure is shown.

[0027] Fig.15 Shown according to Fig.14 An exemplary operation of the method.

[0028] Fig.16 A method for an electronic device to register a user-defined gesture according to an embodiment of the present disclosure is shown.

[0029] Fig.17 Shown according to Fig.16 A graph of the AOA information obtained by the method for registering user-defined gestures.

[0030] Fig.18 A method for an electronic device to recognize a user gesture input by using AoA information obtained based on OWRs received from a plurality of UWB advertising devices according to an embodiment of the present disclosure is illustrated.

[0031] Fig.19 Shown according to Fig.18 A graph of AOA information obtained by the method for recognizing user gestures.

[0032] Fig. 20 A motion sensing scenario using UWB OWR according to an embodiment of the present disclosure is shown.

[0033] Fig.21 Shows the use of Fig. 20 A graph of AoA information collected for a motion sensing scenario.

[0034] Fig.22A and Fig. 22B A graph of AoA information obtained based on a motion sensor and a graph of AoA information obtained based on an OWR according to an embodiment of the present disclosure are shown.

[0035] Fig.23 An example of a structure of a ranging block for UWB OWR according to an embodiment of the present disclosure is shown.

[0036] Fig.24 is a flowchart illustrating a method for a UWB device to recognize a user gesture input by using OWR according to an embodiment of the present disclosure.

[0037] Fig.25 is a device diagram of a UWB device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0038] Hereinafter, various embodiments of the present disclosure are described in detail with reference to the accompanying drawings.

[0039] In describing the embodiments, descriptions of technologies known in the art and not directly related to the present disclosure are omitted. This is to further clarify the main points of the present disclosure without making it unclear.

[0040] For the same reason, some elements may be exaggerated or schematically shown. The size of each element does not necessarily reflect the actual size of the element. In all the drawings, the same reference numerals are used to represent the same elements.

[0041] The advantages and features of the present disclosure and the methods for realizing them can be understood by the embodiments described below in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed herein, and various changes may be made thereto. The embodiments disclosed herein are provided only to inform the technical personnel of the art of the categories of the present disclosure. The present disclosure is limited only by the attached claims. Throughout the specification, the same reference numerals represent the same elements.

[0042] It should be understood that the blocks in each flowchart and the combination of flowcharts can be executed by computer program instructions. Since computer program instructions can be provided in a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device, the instructions executed by the processor of the computer or other programmable data processing device generate means for performing the functions described in conjunction with the blocks of each flowchart. Since computer program instructions can be stored in a computer-usable or computer-readable memory, which can be directed to a computer or other programmable data processing device to implement functions in a specified manner, the instructions stored in the computer-usable or computer-readable memory can produce a product including an instruction device, which is used to perform the functions described in conjunction with the blocks in each flowchart. Since computer program instructions can be provided in a computer or other programmable data processing device, the instructions for generating a process performed by a computer as a series of operating steps are executed on the computer or other programmable data processing device, and the operating computer or other programmable data processing device can provide steps for performing the functions described in conjunction with the blocks in each flowchart.

[0043] In addition, each block can represent a module, segment or part of code including one or more executable instructions for performing a specified logical function. In addition, it should also be noted that in some alternative execution examples, the functions mentioned in the block can occur in different orders. For example, two blocks shown in succession can be performed substantially simultaneously, or in reverse order according to the corresponding functions.

[0044] As used herein, the term "unit" may refer to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). The unit plays a specific role. However, the term "unit" is not limited to mean a software or hardware element. A "unit" may be configured in a storage medium that can be addressed or may be configured to reproduce one or more processors. For example, a "unit" includes elements, such as software elements, object-oriented software elements, class elements and task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays and variables. The functions provided in an element or unit may be combined with additional elements or may be divided into sub-elements or sub-units. In addition, an element or unit may be implemented as one or more central processing units (CPUs) in a reproduction device or a secure multimedia card. A unit may include one or more processors.

[0045] As used herein, the term "terminal" or "device" may include a mobile station (MS), a user equipment (UE), a user terminal (UT), a terminal, a wireless terminal, an access terminal (AT), a subscriber unit, a subscriber station, a wireless device, a wireless communication device, a wireless transmit / receive unit (WTRU), a mobile node, a mobile device, etc. The terminal may also include a cellular phone, a smart phone with wireless communication capability, a personal digital assistant (PDA) with wireless communication capability, a wireless modem, a portable computer with wireless communication capability, a capture / recording / shooting / photography device, such as a digital camera with wireless communication capability, a game console with wireless communication capability, a music storage and playback home appliance with wireless communication capability, an Internet home appliance capable of accessing wireless Internet and browsing the Internet, or a portable unit or terminal incorporating a combination of these capabilities. In addition, the terminal may include an M2M terminal and an MTC terminal / device, but is not limited thereto. In the present disclosure, a terminal may be referred to as an electronic device or simply as a device.

[0046] Hereinafter, the working principle of the present disclosure will be described with reference to the accompanying drawings. When it is determined that the subject matter of the present disclosure is unclear, the detailed description of known functions or configurations can be skipped. The terms used herein are defined to consider the role in the present disclosure, and can be replaced with other terms according to the intention or practice of the user or operator. Therefore, these terms should be defined based on the overall nature of the present disclosure.

[0047] Hereinafter, embodiments of the present disclosure are described in detail with reference to the accompanying drawings. In addition, although a communication system using UWB is described in conjunction with an embodiment of the present disclosure as an example, embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or features. For example, a communication system using Bluetooth or ZigBee may be included therein. In addition, at the determination of a person of ordinary skill in the art, embodiments of the present disclosure may be modified within the scope of not significantly departing from the scope of the present disclosure, and such modifications may be applied to other communication systems.

[0048] When it is determined that the subject matter of the present disclosure is unclear, the detailed description of known technologies or functions can be skipped. The terms used herein are defined to consider the role in the present disclosure, and can be replaced with other terms according to the intention or practice of the user or operator. Therefore, these terms should be defined based on the overall nature of the present disclosure.

[0049] Generally, wireless sensor network technology is mainly 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, which enables access to the backbone network within a radius of about 100m. WPAN is a technology based on IEEE 802.15, including Bluetooth, ZigBee and ultra-wideband (UWB). The wireless network in which this wireless network technology is implemented can include multiple electronic devices.

[0050] 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 more or a bandwidth corresponding to a center frequency of 20% or more. UWB may mean the frequency band itself to which UWB communication is applied. UWB can achieve secure and accurate ranging between devices. Therefore, UWB can achieve relative position estimation based on the distance between two devices, or achieve accurate position estimation of a device based on the distance from a fixed device (whose position is known).

[0051] The terms used herein are for better understanding of the present disclosure and may be changed without departing from the technical spirit of the present disclosure.

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

[0053] An "Application Protocol Data Unit (APDU)" may be a command and response used when communicating with an application data structure in a UWB device.

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

[0055] A "controller" may be a ranging device that defines and controls ranging control messages (RCMs) (or control messages).

[0056] A "controller" may be a ranging device that uses ranging parameters in an RCM (or control message) received from a controller.

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

[0058] An "applet" may be, for example, an applet executed on a secure component including UWB parameters and service data. In this disclosure, an applet may be a FiRa applet defined by FiRa.

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

[0060] A "UWB-enabled application" may be an application for UWB services. For example, a UWB-enabled application may be an application that uses a framework API to configure an OOB connector, security services, and / or UWB services for a UWB session. In the present disclosure, a "UWB-enabled application" may be abbreviated as an application or a UWB application. A UWB-enabled application may be a FiRa-enabled application defined by FiRa.

[0061] A "framework" may be a component that provides access to profiles, individual UWB configurations, and / or notifications. A "framework" may be, for example, a collection of logical software components that include a profile manager, an OOB connector, security services, and / or UWB services. In the present disclosure, a framework may be a FiRa framework defined by FiRa.

[0062] The "OOB connector" may be a software component for establishing an out-of-band (OOB) connection (eg, a BLE connection) between ranging devices. In the present disclosure, the OOB connector may be a FiRa OOB connector defined by FiRa.

[0063] A "profile" may be a previously defined set of UWB and OOB configuration parameters. In the present disclosure, a profile may be a FiRa profile defined by FiRa.

[0064] A "profile manager" may be a software component that implements a profile available on a ranging device. In the present disclosure, the profile manager may be a FiRa profile manager defined by FiRa.

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

[0066] A "smart ranging device" may be a ranging device that may implement an optional framework API. In the present disclosure, a smart ranging device may be a FiRa smart device defined by FiRa.

[0067] A "Global Private File (GDF)" may be a root level of application specific data that includes data needed to establish a USB session.

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

[0069] An "initiator" may be a ranging device that initiates a ranging exchange.

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

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

[0072] A “Ranging Data Set (RDS)” may be data required to establish a UWB session when confidentiality, authenticity, and integrity need to be protected (eg, UWB session key, session ID, etc.).

[0073] A "responder" may be a ranging device that responds to an initiator in a ranging exchange.

[0074] "STS" may be an encryption sequence used to increase the integrity and accuracy of the ranging time stamp. STS may be generated from the ranging session key.

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

[0076] A "secure component" may be an entity (eg, SE or TEE) with a defined security level that interfaces with the UWBS to provide RDS to the UWBS, for example when using dynamic STS.

[0077] A “secure element (SE)” may be a tamper-resistant secure hardware component that may be used as a secure component in a ranging device.

[0078] “Secure ranging” can be performed based on the STS generated through strong cryptographic operations.

[0079] A “security service” may be a software component used to interface with a security component such as a secure element or a trusted execution environment (TEE).

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

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

[0082] 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.

[0083] "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.

[0084] A "Secure UWB Service (SUS) applet" may be an applet on the SE that communicates with the applet to retrieve data required to implement a secure UWB session with other ranging devices. The SUS applet may transmit corresponding data (information) to the UWBS.

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

[0086] A "UWB session" may be a time period from when a controller and a controlled device start communicating via UWB until the communication stops. A UWB session may include ranging, data transmission, or both ranging and data transmission.

[0087] The “UWB session ID” may be an ID (eg, a 32-bit integer) identifying a UWB session shared between a controller and controllers.

[0088] The "UWB session key" may be a key for protecting a UWB session. The UWB session key may be used to generate an STS. In the present disclosure, the UWB session key may be a UWB ranging session key (URSK) and may be abbreviated as a session key.

[0089] UWB Subsystem (UWBS): A hardware component that implements the UWB PHY and MAC layer specifications. The UWBS may have an interface to the framework and an interface to the security component to search for RDS.

[0090] "Scheduled ranging" may be used for ranging cycles in which the controller is scheduled by the controller to send RFRAME and / or measurement reports in different ranging time slots. In the present disclosure, scheduled ranging may also be referred to as time-scheduled ranging. A scheduling mode using scheduled ranging may be referred to as a time-scheduled mode.

[0091] When the controller does not know the MAC address of the controller participating in the UWB session (ranging session), "contention-based ranging" can be used. In contention-based ranging, the controller can be the initiator and can perform ranging with another unknown UWB device. In the present disclosure, the scheduling mode using contention-based ranging can be referred to as a contention-based mode.

[0092] Contention-based ranging may be used for ranging cycles in which a controller determines the size of a contention access period (CAP) and notifies the CAP size through a ranging control message. In the present disclosure, the contention access period may be referred to as a contention window or a contention window period.

[0093] In content-based mode, the UWB device can operate as a controller and initiator, and in this case, the ranging control phase (RCP) and the ranging initiation phase (RIP) can be merged into the RIP. In the ranging phase (RP), the allocation of the CAP size can determine the CAP period of a responder (multiple responders) participating in the ranging cycle in units of ranging slots. Each responder can randomly select a slot in the CAP to send a ranging response message (RRM). The message used in contention-based ranging can use SP1 as the RFRAME configuration.

[0094] When there are known controllables and unknown controllables, "hybrid ranging" may be used. As described above, a known controllable may be a controllable whose MAC address is known by the controller, and an unknown controllable may be a controllable whose MAC address is unknown by the controller. In the present disclosure, hybrid ranging may be referred to as hybrid-based ranging. A scheduling mode using hybrid ranging may be referred to as a hybrid-based mode.

[0095] In the hybrid-based mode, the controller may perform ranging with known controlees in a scheduling-based mode and perform ranging with unknown controlees in a contention-based mode.

[0096] In the hybrid-based mode, the ranging cycle may include a ranging control phase (RCP) and a ranging phase (RP). The RP may include a contention-free period for scheduling-based ranging (access) and a contention access period (CAP) for contention-based ranging (access). In the present disclosure, the control message (ranging control message) used in the RCP of the hybrid-based mode may be referred to as a ranging management message (RMM).

[0097] A "UWB message" may be a message including a payload IE (e.g., ERDEV) sent by a UWB device. For example, a UWB message may be a message such as 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), and a one-way ranging (OWR) message. If necessary, multiple messages may be combined into one message.

[0098] The 'Payload IE' may be referred to as a payload information element and may be included in a MAC payload of a UWB MAC frame defined in IEEE 802.15.4 / 4.

[0099] "Data message IE (Data message payload IE)" may be an additional payload IE for transmitting application data. The application data may be data transferred from a framework or application above the UWB MAC layer.

[0100] The data message IE may be used in the process of two-way ranging (TWR). In this case, the ranging message (UIB message) may include at least one or both of a payload IE for ranging and a data message IE for application data transmission. For example, the data message IE may be included and sent as part of a MAC payload IE of a ranging initiation message (RIM), ranging response message (RRM), ranging final message (RFM), measurement report message (MRM), and ranging result report message (RRRM) for ranging.

[0101] The data message IE may be used for angle of arrival (AoA) measurement in the process of one-way ranging (OWR). In this case, the AoA measurement message may include at least one or both of a payload IE for AoA measurement and a data message IE for application data transmission. For example, the data message IE may be included and sent as part of the payload IE of the MAC payload of the AoA measurement message.

[0102] "OWR" may be a ranging scheme 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 at the receiving end instead of measuring TDoA. In this case, a pair of announcers and an observer may be used. OWR for measuring AoA enables the observer to receive the OWR message from the announcer and measure the AoA to determine the user's intent, action, or action of the observer. For example, the user's intent to control a particular announcer may be verified by measuring the AoA of the OWR message from the announcer. In the present disclosure, OWR may be referred to as UWB OWR.

[0103] 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 announcer device or a UWB announcer 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 announcement message, an announcement message, etc.

[0104] An "observer" is a ranging device that receives AoA measurement messages and measures AoA for each message. The observer may send the measured AoA to an upper layer. When an application 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.

[0105] "TWR" may be a ranging scheme capable of estimating the relative distance between two devices by measuring the time of flight (ToF) by exchanging ranging messages between the two devices. The TWR scheme may be one of dual-sided two-way ranging (DS-TWR) and single-sided two-way ranging (SS-TWR). SS-TWR may be a process of performing ranging through one round-trip time measurement. DS-TWR may be a process of performing ranging through two round-trip time measurements. For example, DS-TWR may include a transmission operation of the RIM from the initiator to the responder, a transmission operation of the RRM from the responder to the initiator, and a transmission operation of the RRM from the initiator to the responder. During the TWR process, the measured AoA information (e.g., AoA azimuth result and AoA elevation result) may be sent to another ranging device via RRRM or other messages. In the present disclosure, TWR may be referred to as UWB TWR.

[0106] "AoA" is the angle of arrival of the received signal, which can be expressed as relative angles, such as AoA azimuth and AoA elevation. Meanwhile, it can be assumed that the measuring 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 phone display. In this case, the AoA azimuth may be the relative angle between the input signal projected on the XZ plane and the Z axis, and the AoA elevation may be the relative angle between the input signal and the XZ plane.

[0107] 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 controllable (responder) can measure the AoA azimuth of the RIM message and send the measured AoA azimuth through RRRM.

[0108] 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 controlee (responder) can measure the AoA elevation angle of the RIM message and send the measured AoA elevation angle through RRRM.

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

[0110] Detailed description of known technologies or functions may be skipped when it is determined that it would make the subject matter of the present disclosure unclear.

[0111] Hereinafter, various embodiments of the present disclosure are described with reference to the accompanying drawings.

[0112] Figure 1 An example structure of a UWB device according to an embodiment of the present disclosure is shown.

[0113] In the present disclosure, the UWB device 100 may be an electronic device supporting UWB communication. The UWB device 100 may be, for example, a ranging device supporting UWB ranging. In an embodiment, the ranging device may be an ERDEV or FiRa device.

[0114] exist Figure 1 In the embodiment of the present invention, the UWB device 100 can interact with other UWB devices through a UWB session.

[0115] The UWB device 100 may implement a first interface (Interface #1), which is an interface between the UWB-enabled application 110 and the framework 120, and the first interface allows the UWB-enabled application 110 on the UWB device 100 to use the UWB capabilities of the UWB device 100 in a predetermined manner. In an embodiment, the first interface may be a framework API or a proprietary interface, but is not limited thereto.

[0116] The UWB device 100 may implement a second interface (Interface #2) which is an interface between the UWB framework 110 and the UWB subsystem (UWBS, 130). In an embodiment, the second interface may be a UWB command interface (UCI) or a proprietary interface, but is not limited thereto.

[0117] refer to Figure 1 , the UWB device 100 may include a UWB-enabled application 110, a framework (UWB framework) 120, and / or a UWBS 130 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.

[0118] The UWB-enabled application 110 may trigger the UWBS 130 to establish a UWB session via the first interface. The UWB-enabled application 110 may use one of the previously defined profiles (profiles). For example, the UWB-enabled application 110 may use one of the profiles defined in FiRa or a custom profile. The UWB-enabled application 110 may use the first interface to handle related events such as service discovery, ranging notifications, and / or error conditions.

[0119] The framework 120 may provide access to configuration files, individual UWB configurations, and / or notifications. The framework 120 may support at least one of a function for UWB ranging and transaction execution, a function for providing an interface to an application and the UWBS 130, or a function for estimating the location of the device 100. The framework 120 may be a set of software components. As described above, the UWB-enabled application 110 may interface with the framework 120 through a first interface, and the framework 120 may interface with the UWBS 130 through a second interface.

[0120] At the same time, in the present disclosure, the UWB-enabled application 110 and / or the framework 120 can be implemented by an application processor (AP) (or processor), and therefore, in the present disclosure, the operations of the UWB-enabled application 110 and / or the framework 120 can be understood as being performed by the AP (or processor), and in the present disclosure, the framework can be referred to as the AP or the processor.

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

[0122] Figure 2 An example configuration of a framework of a UWB device according to an embodiment of the present disclosure is shown.

[0123] Figure 2 A UWB device can be Figure 1 Examples of UWB devices.

[0124] Reference Figure 2 , 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 .

[0125] The profile manager 221 may be used to manage profiles available on UWB devices, which 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 particular 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)).

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

[0127] The security service 223 may function as an interface with a security component 240 (such as a SE or TEE).

[0128] The UWB service 224 may perform a role of managing the UWBS 230. The UWB service 224 may provide access to the UWBS 230 from the profile manager 221 by implementing a second interface.

[0129] Figure 3 A method for performing communication through a plurality of electronic devices according to an embodiment of the present disclosure is illustrated.

[0130] Figure 3 The first electronic device 301 and the second electronic device 302 may be, for example, Figure 1 or Figure 2 UWB devices.

[0131] refer to Figure 3 , the first electronic device 301 and the second electronic device 302 may perform a device search / connection establishment process 310 and a data communication process 320. The device search / connection establishment process 310 and the data communication process 320 may be managed or controlled by a MAC layer (entity) of the electronic device.

[0132] (1) Device search / connection establishment process

[0133] In the present disclosure, the device search / connection establishment process 310 may be a previous process performed before the data communication process 320. As an example, the device discovery / connection establishment process 310 may be performed on OOB communication (channel), NB communication (channel), and / or UWB communication (channel).

[0134] The device search / connection establishment process 310 may include at least one of the following operations.

[0135] Device discovery operation: an operation in which an electronic device searches for (discovers) another UWB device. The device discovery operation may include an operation for sending / receiving an announcement message. In the present disclosure, the device discovery operation may be referred to as a discovery operation or an announcement operation.

[0136] Connection setup operation: An operation in which two electronic devices establish a connection. The connection establishment operation may include operations for sending / receiving a connection request message and a connection confirmation message. The connection (channel) established by the connection establishment operation may be used to configure and control a UWB session for data communication. For example, parameters (e.g., UWB performance parameters (controller performance parameters), UWB configuration parameters, session key related parameters) for configuring a UWB session through a secure channel established via the connection establishment operation may be negotiated between two electronic devices.

[0137] (2) Data communication process

[0138] In the present disclosure, the data communication process 320 may be a process for transmitting and receiving data using UWB communication. As an embodiment, the data communication process may be performed by UWB communication or NB communication.

[0139] The data communication process 320 may include at least one of the following operations.

[0140] -UWB ranging operation: an operation in which an electronic device performs UWB ranging with other electronic devices in a preset UWB ranging scheme (eg, OWR, SS-TWR, DS-TWR scheme). As an embodiment, the UWB ranging operation may include a ToF measurement operation and / or an AoA measurement operation.

[0141] For example, the DS-TWR scheme may include some or all of the following steps:

[0142] Ranging Control Phase (RCP): The step in which the UWB controller sends a UWB control message (e.g., a Ranging Control Message (RCM)) to the UWB controller. In this way, the controller can control the ranging and define the ranging parameters.

[0143] Ranging Initiation Phase (RIP): A step in which a UWB initiator sends a UWB Initiation Message (RIM) to a UWB responder. The ranging initiation message may be the first message sent to start a ranging exchange. As an embodiment, a UWB controller / initiator may send a ranging control message and a ranging initiation message in one message. For example, a UWB controller / initiator may send a ranging initiation message including a ranging control message.

[0144] Ranging Response Phase (RRP): a step in which the UWB responder sends a UWB response message (eg, Ranging Response Message (RRM)) corresponding to the UWB Initiation message to the UWB Initiator.

[0145] Ranging Final Phase (RFP): The step where the UWB Initiator sends a UWB final message (e.g., Ranging Final Message (RFM)) to the UWB Responder. RFP can only be used in the case of dual-side two-way ranging (DS-TWR).

[0146] As an embodiment, the UWB TWR process may further include a measurement report phase (MRP). The measurement report phase may be a phase in which electronic devices participating in UWB ranging exchange ranging information (e.g., ToF information / AoA information, etc.) and / or related service information. As an embodiment, the UWB message used in the measurement report phase may be a measurement report message (MRM), a ranging result report message (RRRM), or a control update message (CUM). As an embodiment, the MRM may be sent by being included in the RRM or RFM.

[0147] Transaction operation: An operation in which an electronic device exchanges service data with another electronic device.

[0148] Figure 4 The structure of a UWB MAC frame according to an embodiment of the present disclosure is shown.

[0149] exist Figure 4In an embodiment, the UWB MAC frame may follow, for example, a MAC frame structure of IEEE 802.15.4z. In the present disclosure, the UWB MAC frame may be simply referred to as a MAC frame or a frame. As an embodiment, the UWB MAC frame may be used to transmit UWB data (e.g., UWB messages, ranging messages, control information, service data, application data, transaction data, etc.).

[0150] refer to Figure 4 , a UWB MAC frame may include a MAC header (MHR), a MAC payload and / or a MAC frame tail (MFR).

[0151] (1) MAC header

[0152] The MAC header may include a frame control field, a sequence number field, a destination address field, a source address field, an auxiliary security header field, and / or at least one header IE field. Depending on the embodiment, some fields may not be included in the MAC header.

[0153] As an embodiment, the frame control field may include a frame type field, a security enable field, a frame suspension field, an AR field, a PAN ID compression field, a sequence number suppression field, an IE current field, a target addressing mode field, a frame version field and / or a source addressing mode field. Each field is described below.

[0154] The frame type field may indicate a frame type. As an embodiment, the frame type may include a data type and / or a multi-purpose type.

[0155] The Security Enabled field may indicate whether there is an Auxiliary Security Header field. The Auxiliary Security Header field may include information required for security processing.

[0156] The frame pending field may indicate whether the device sending the frame has more data for the recipient. In other words, the frame pending field may indicate whether there is a pending frame for the recipient.

[0157] The AR field may indicate whether confirmation of frame reception is required from the receiving side.

[0158] The PAN ID Compression field may indicate whether the PAN ID field exists.

[0159] The Sequence Number Suppression field may indicate whether the Sequence Number field is present. The Sequence Number field may indicate a sequence identifier for the frame.

[0160] The IE presence field may indicate whether a header IE field and a payload IE field are included in a frame.

[0161] The target addressing mode field may indicate whether the target address field may include a short address (eg, 16 bits) or an extended address (eg, 64 bits).The target address field may indicate the address of the receiver of the frame.

[0162] The frame version field may indicate a frame version. For example, the frame version field may be set to a value indicating IEEE std802.15.4z-2020.

[0163] The source addressing mode field may indicate whether a source address field is present, and if so, whether the source address field includes a short address (eg, 16 bits) or an extended address (eg, 64 bits).

[0164] (2) MAC payload

[0165] The MAC payload may include at least one payload IE field. As an embodiment, the payload IE field may include a vendor specific nested IE. As an embodiment, the payload IE field may include a payload IE field of a UWB message, a ranging message, or a control message.

[0166] (3) MAC frame tail

[0167] The MAC frame tail may include an FCS field. The FCS field may include a 16-bit CRC or a 32-bit CRC.

[0168] Figure 5A and Figure 5B The structure of a UWB PHY packet according to an embodiment of the present disclosure is shown.

[0169] Figure 5(a) shows an example structure of a UWB PHY packet without applying the STS packet configuration, and Figure 5(b) shows an example structure of a UWB PHY packet with applying the STS packet configuration. In the present disclosure, a UWB PHY packet may be referred to as a PHY packet, a PHY PDU (PPDU), or a frame.

[0170] Referring to FIG. 5( a ), the PPDU may include a synchronization header (SHR), a PHY header (PHR), and a PHY payload (PSDU). The PSDU may include a MAC frame. Figure 4 As shown, the MAC frame may include a MAC header (MHR), a MAC payload and / or a MAC frame tail (MFR). In the present disclosure, the synchronization header portion may be referred to as a preamble, and the portion including the PHY header and the PHY payload may be referred to as a data portion.

[0171] The synchronization header may be used for synchronization of signal reception and may include a SYNC field and a start frame delimiter (SFD).

[0172] The SYNC field may be a field including a plurality of preamble symbols for synchronization between transmitting / receiving devices.

[0173] The SFD field may be a field indicating the end of the SHR and the start of the data field.

[0174] The PHY header may provide information about the configuration of the PHY payload. For example, the PHY header may include information about the length of the PSDU, information indicating whether the current frame is an RFRAME, and the like.

[0175] At the same time, the PHY layer of the UWB device may include an optional mode to provide reduced air time for high-density / low-power operation. In this case, the UWB PHY packet may include an encryption sequence (i.e., STS) to increase the integrity and accuracy of the ranging measurement time stamp. The STS may be included in the STS field of the UWB PHY packet and used for secure ranging.

[0176] Referring to Figure 5(b), in the case where the STS packet (SP) is set to 0 (SP0), the STS field is not included in the PPDU (SP0 packet). In the case where the SP is set to 1 (SP1), the STS field is immediately after the frame start delimiter (SFD) field and before the PHR field (SP1 packet). In the case where the SP is set to 2 (SP2), the STS field is located after the PHY payload (SP2 packet). In the case where the SP is set to 3 (SP3), the STS field is immediately after the SFD field, and the PPDU does not include the PHR and data fields (PHY payload) (SP3 packet). In other words, in the case of SP3, the PPDU does not include the PHR and PHY payload.

[0177] In the embodiment of Fig. 5(b), each UWB PHY packet may include a RMARKER for defining a reference time. The RMARKER may be used to obtain the transmission time, reception time and / or time range of a ranging message (frame) during the UWB ranging process.

[0178] Figure 6 An example of the structure of a ranging block and a loop for UWB ranging according to an embodiment of the present disclosure is shown.

[0179] In the present disclosure, a ranging block refers to a time period used for ranging. A ranging cycle may be a period of sufficient duration for completing an entire ranging cycle (ranging time period) in which a group of UWB devices participating in a ranging exchange are involved. A ranging slot may be a period of sufficient duration for transmitting at least one ranging frame (RFRAME) (e.g., ranging initiation / response / final message, etc.).

[0180] like Figure 6 As shown, a ranging block may include at least one ranging cycle. Each ranging cycle may include at least one ranging slot.

[0181] When the ranging mode is a block-based mode, the average time between adjacent ranging cycles can be constant. Alternatively, when the ranging mode is an interval-based mode, the time between adjacent ranging cycles can be dynamically changed. In other words, the interval-based mode can adopt a time structure with adaptive intervals.

[0182] The number and duration of time slots included in a ranging cycle may vary between ranging cycles.

[0183] In the present disclosure, ranging blocks, ranging cycles and ranging slots may be abbreviated as blocks, cycles and slots.

[0184] Hereinafter, a method for providing service initiation using UWB OWR and user gesture input will be described.

[0185] In the present disclosure, UWB OWR may be performed by using a UWB announce message (AoA measurement message) as a UWB OWR message, and service initiation (activation) and user gesture input may be provided by using AoA information obtained using the UWB announce message.

[0186] [UWB system architecture of the UWB OWR disclosed in this disclosure]

[0187] Figure 7 A system for providing service initiation using UWB OWR and user gesture input according to an embodiment of the present disclosure is shown.

[0188] refer to Figure 7 , a system for providing service initiation and user gesture input using UWB OWR (hereinafter referred to as UWB system) may include a first device 710, a second device 720, and / or a third device 730. In the present disclosure, the first device 710 may be referred to as a first electronic device and a first UWB device, the second device 720 may be referred to as a second electronic device and a second UWB device, and the third device 730 may be referred to as a third electronic device and a third UWB device.

[0189] exist Figure 7 In the embodiment of the present invention, it is assumed that the second device 720 operates as a UWB announcer device that sends a UWB announcement message, and the first device 710 and / or the third device 730 operates as a UWB observer device that receives the UWB announcement message. Examples of UWB announcement messages may be similar to those described later. Fig.23 and Figures 1 to 3 The message is the same as the one illustrated in .

[0190] <Operation of the Second Device>

[0191] The second device 720 may send (or broadcast) a UWB announcement message. As an embodiment, the second device 720 may send the UWB announcement message during a preconfigured period (announcement period).

[0192] As an embodiment, the UWB announcement message may include information about the announcement period (announcement period information). For example, the announcement period information may be information that explicitly indicates the announcement period or information for obtaining the announcement period. For example, the announcement period information may be the inter-frame spacing information / field of Table 2 described later. The announcement period may be related to the AoA sampling rate. In the present disclosure, the announcement period may be referred to as the announcement message transmission period, and the announcement period information may be referred to as the announcement message transmission period information.

[0193] As an embodiment, the UWB announcement message may include application data (application payload data). For example, as an embodiment, the application data may include the context (e.g., redirect address or content) of the service to be announced via the UWB announcement message. The application data may be used to identify / initiate related services.

[0194] As an embodiment, the UWB announcement message may be used by a UWB observer device to observe / estimate the AoA information of the received UWB announcement message. The AoA information may include AoA elevation information indicating an AoA elevation value and / or AoA azimuth information indicating an AoA azimuth value. The AoA information thus obtained may be used to identify / provide initiation of a corresponding service and / or a user gesture input associated with the corresponding service.

[0195] <Operation of the First Device>

[0196] The first device 710 may receive the UWB announcement message, and may perform an operation of service initiation and / or user gesture input based on the UWB announcement message.

[0197] As an embodiment, the first device 710 may obtain AoA information based on the UWB announcement message. For example, the first device 710 may measure the AoA elevation value and / or the AoA azimuth value based on the UWB announcement message.

[0198] As an embodiment, the first device 710 may also obtain a received signal strength indication (RSSI) of the UWB announcement message.

[0199] As an embodiment, the first device 710 may determine a scheme for recognizing a user gesture (motion) based on the UWB announcement message. For example, the first device 710 may determine a scheme for recognizing a user gesture (user gesture input) based on the announcement period information included in the UWB announcement message.

[0200] The scheme for recognizing user gesture input may be a first scheme (option 1) that recognizes user gesture input using only UWB OWR based on UWB announcement messages, or a second scheme (option 2) that recognizes user gesture input using UWB TWR with another device (e.g., third device 730) together with UWB OWR based on UWB announcement messages. Compared to the first scheme, the second scheme may be a scheme that also uses auxiliary measurement using UWB TWR.

[0201] In the case of the first scheme, the AoA information (first AoA information) obtained based on the UWB announcement message can be used to identify the user gesture input. Meanwhile, in the case of the second scheme, the AoA information (first AoA information) obtained based on the UWB announcement message can be used together with the distance information and / or AoA information (second AoA information) obtained based on the UWB TWR with another electronic device to identify the user gesture input. In the present disclosure, the first AoA information may be referred to as an announcement (Adv.). The AoA information and the second AoA information may be referred to as TWR AoA information.

[0202] As an embodiment, the first device 710 may identify the announcement period (or interval) based on the announcement period information included in the UWB announcement message and compare the announcement period with a preconfigured threshold. As an embodiment, the threshold may be related to the sampling rate (or period) required for user gesture sensing.

[0203] As an embodiment, when the announcement period is less than a preconfigured threshold (for example, when the announcement period is faster than the sampling rate), the first device 710 may select the first scheme as the scheme for recognizing user gesture input. When the announcement period is greater than the preconfigured threshold (for example, when the announcement period is slower than the sampling rate), the first device 710 may select the second scheme as the scheme for recognizing user gesture input.

[0204] As an embodiment, the first device 710 may recognize a user gesture input according to the first scheme or the second scheme, and perform an operation corresponding to the user gesture input.

[0205] <Operation of the Third Device>

[0206] Like the first device 710, the third device 730 can operate as a UWB observer device. In this case, like the first device 710, the third device 730 can obtain AoA information based on the UWB announcement message received by the third device 730.

[0207] In addition, the third device 730 can perform UWB TWR with the first device 710 to help identify the user gesture input of the first device 710. As an example, the UWB TWR (UWB TWR session) between the first device 710 and the third device 730 can be started and terminated by the first device 710, but the example is not limited thereto.

[0208] [Embodiment using the first scheme (Option 1) of the present disclosure]

[0209] Fig. 8A Illustrated is a method for an electronic device to identify a user gesture input by using the first scheme according to an embodiment of the present disclosure.

[0210] As described above, the first scheme can be a scheme that identifies a user gesture input only by using UWB OWR based on a UWB announcement message. The first scheme can be different from the second scheme, which uses UWB OWR based on a UWB announcement message and UWB TWR with another device to identify a user gesture input.

[0211] In Fig. 8A the embodiment of, the first device (Device #1) 810, the second device (Device #2) 820, and the third device (Device #3) 830 can be respectively Figure 7 the first device 710, the second device 720, and the third device 830 of

[0212] The first device 810 is an electronic device that operates as a UWB observer device and can be, for example, a wearable device of a user, but the embodiment is not limited thereto.

[0213] The second device 820 is an electronic device that operates as a UWB observer device and can be, for example, a fixed device (e.g., a self-service terminal), but the embodiment is not limited thereto.

[0214] The third device 830 is an electronic device that operates as a UWB observer device and can be, for example, a mobile phone of a user, but the embodiment is not limited thereto.

[0215] <UWB Announcer Device>

[0216] Refer to Fig. 8A, the second device 820 may send (or broadcast) a UWB announcement message. For example, the second device 820 may send a UWB announcement message during a preconfigured period (transmission period). As an example, the UWB announcement message may include application data.

[0217] <UWB Observer Device>

[0218] The first device 810 and the third device 830 may receive one or more UWB announcement messages.

[0219] The first device 810 may obtain AoA information (AoA azimuth / AoA elevation) of the received one or more UWB announcement messages. Additionally, the first device 810 may determine user movement (gesture) by using an AoA trajectory obtained based on the AoA information. The first device 810 may identify a user gesture input by using the AoA trajectory. An example of a method for the first device 810 to obtain AoA information based on the received UWB announcement message and identify a user gesture input based on the obtained AoA information according to the first scheme will be described below with reference to FIG. 9.

[0220] The first device 810 may communicate with the third device 830 via OOB communication (e.g., Wi-Fi, BLE, etc.). For example, the first device 810 may send application data and / or motion input data to the third device 830. The motion input data may include data of a user gesture input identified by the first device 810. The first device 810 may receive service data from the third device 830. The service data may include service data related to the user gesture input (e.g., service display data).

[0221] Fig. 8A Embodiments describe an example in which the first device 810 and the third device 830 exchange data with each other via OOB communication. In this case, power consumption may be reduced compared to the case of exchanging data via in-band signals. However, the above embodiments are not limited thereto. For example, if necessary, the first device 810 and the third device 830 may exchange all or part of the above data via in-band communication.

[0222] [Embodiments of Using the Second Scheme (Option 2) of the Present Disclosure]

[0223] Figure 8B Illustrates a method for an electronic device to identify a user gesture input by using a second scheme according to an embodiment of the present disclosure.

[0224] As described above, the second solution may be a solution that uses UWB OWR based on UWB announcement messages and UWB TWR with another device to identify user gesture inputs. The second solution may be different from the first solution, which only uses UWB OWR based on UWB announcement messages to identify user gesture inputs.

[0225] In Figure 8B the embodiment of, the first device (Device #1) 810, the second device (Device #2) 820, and the third device (Device #3) 830 may be respectively Figure 7 the first device 710, the second device 720, and the third device 830 of

[0226] The first device 810 is an electronic device that operates as a UWB observer device, and may be, for example, a wearable device of a user, but the embodiment is not limited thereto.

[0227] The second device 820 is an electronic device that operates as a UWB observer device, and may be, for example, a fixed device (e.g., a self-service terminal), but the embodiment is not limited thereto.

[0228] The third device 830 is an electronic device that operates as a UWB observer device, and may be, for example, a mobile phone of a user, but the embodiment is not limited thereto.

[0229] <UWB Announcer Device>

[0230] Referring to Figure 8B , the second device 820 may send (or broadcast) UWB announcement messages. For example, the second device 820 may send UWB announcement messages during a pre-configured period (transmission period). As an embodiment, the UWB announcement messages may include application data.

[0231] <UWB Observer Device>

[0232] The first device 810 and the third device 830 may receive one or more UWB announcement messages.

[0233] The first device 810 may obtain AoA information (AoA azimuth / AoA elevation angle) of the received one or more UWB announcement messages.

[0234] The first device 810 may communicate with the third device 830 through in-band communication. For example, the first device 810 may perform UWB TWR with the third device 830. Through UWB TWR, the first device 810 may obtain distance information and / or second AoA information (AoA azimuth / AoA elevation angle). The distance information may provide information about the distance between the first device 810 and the third device 830.

[0235] As an embodiment, when the first device 810 is an initiator (or controller) of TWR, the AoA azimuth and AoA elevation of RRM may be measured. Alternatively, when the third device 830 is a responder (or controller) of TWR, the AoA azimuth and AoA elevation of the RIM message may be measured, and information about the AoA azimuth and AoA elevation measured by RRRM may be sent to the first device 810.

[0236] As another embodiment, when the first device 810 is a responder (or controller) of the TWR, the AoA azimuth and AoA elevation of the RIM message may be measured.

[0237] The first device 810 may determine a user motion (gesture) by using a trajectory obtained based on the first AoA information, the second AoA information, and / or the distance information. The first device 810 may recognize a user gesture input by using the obtained trajectory.

[0238] An example of a method in which the first device 810 obtains first AoA information, second AoA information, and distance information based on a received UWB announcement message according to the second scheme and recognizes a user gesture input based on the obtained information will be described below with reference to FIG. 10 .

[0239] The first device 810 may transmit the motion input data to the third device 830 through in-band communication. For example, the first device 810 may transmit the motion input data to the third device 830 through a UWB message (e.g., RFM, etc.). The motion input data may include data of a user gesture input recognized by the first device 810.

[0240] The first device 810 may receive service data from the third device 830 through in-band communication. For example, the first device 810 may receive service data from the third device 830 through a UWB message. The service data may include service data related to a user gesture input (eg, service display data).

[0241] [Example of the first solution (option 1)]

[0242] Fig. 9A , Fig. 9B and Fig. 9C A method for an electronic device to recognize a user gesture input based on AoA information according to a first solution according to an embodiment of the present disclosure is shown.

[0243] As described above, the first scheme may be a scheme for recognizing a user gesture input using only UWB OWR based on a UWB announcement message. The first scheme may be distinguished from a second scheme for recognizing a user gesture input using UWB OWR based on a UWB announcement message and UWB TWR with another device.

[0244] exist Fig. 9A , Fig. 9B and Fig. 9C In the embodiment of the present invention, the first device (device #1) 910, the second device (device #2) 920 and the third device (device #3) 930 may be Fig. 8A A first device 810, a second device 820 and a third device 830.

[0245] exist Fig. 9A , Fig. 9B and Fig. 9C In the embodiment, for ease of explanation, it is assumed that the gaze direction (reference direction) of the user wearing the first device 910 is the X-axis, the horizontal axis of the first device is assumed to be the Y-axis, and the vertical axis of the first device is assumed to be the Z-axis.

[0246] Fig. 9A An example of a signal pattern on the XY plane according to the first scheme is shown.

[0247] refer to Fig. 9A , the coordinates on the XY plane of the first electronic device 910 may be expressed as (Xw, Yw), the coordinates on the XY plane of the second electronic device 920 may be expressed as (Xm, Ym), and the coordinates on the XY plane of the third electronic device 930 may be expressed as (Xa, Ya). The UWB announcement message (input signal) is transmitted from the second electronic device 920 in the direction of the first electronic device 910.

[0248] Fig. 9B An example of the AoA azimuth angle value obtained according to the first scheme is shown.

[0249] refer to Fig. 9B , the first device 910 as a UWB observer device may measure / calculate the AoA azimuth value θ of the UWB announcement message received from the second device 920 as a UWB observer device a2w . AoA azimuth value θ a2w It can be the relative angle between the gaze direction (X axis) of the user wearing the first device 910 and the direction in which the UWB announcement message (input signal) projected on the XY plane is received. Meanwhile, in the present disclosure, when the signal transmitting device is located on the left side relative to the reference direction, the AoA azimuth angle can be expressed as a (+) sign, and when located on the right side, as a (-) sign, but the opposite is also possible.

[0250] Fig. 9C An example of the AoA elevation angle value obtained according to the first scheme is shown.

[0251] refer to Fig. 9C, the first device 910 as a UWB observer device may measure / calculate the AoA elevation angle value Φ of the UWB announcement message received from the second device 920 as a UWB observer device a2w . AoA elevation angle value Φ a2w It may be the relative angle between the XY plane of the first device 910 and the direction in which the UWB announcement message (input signal) is received. Meanwhile, in the present disclosure, when the signal transmitting device is located above the XY plane, the AoA elevation angle may be expressed as a (+) sign, and when located below the XY plane, as a (-) sign, but the opposite is also possible.

[0252] The first device 910 may analyze the AoA azimuth value and the AoA horizontal value (θ a2w , Φ a2w ) and recognize the user gesture input based on the analysis result. For example, when the change pattern of the AoA azimuth angle value and the AoA elevation angle value matches (or maps) the pattern of the predefined user gesture input, the first device 910 can recognize that the user's movement corresponds to the user gesture input.

[0253] When the user gesture input is recognized, the first device 910 may transmit the data of the user gesture input to the third device 930. As an embodiment, the first device 910 may transmit the data of the user gesture input to the third device 930 through OOB.

[0254] In the above embodiment of Figure 9, the first scheme can be used to recognize user gesture input. In this case, since UWB TWR is not used to recognize user gesture input but only UWB OWR based on UWB announcement message is used, the electronic device can recognize user gesture input faster and with less power compared to the second scheme.

[0255] [Example of the second solution (option 2)]

[0256] Fig. 10A and Fig. 10B A method for an electronic device to recognize a user gesture input based on AoA information according to a second solution according to an embodiment of the present disclosure is shown.

[0257] As described above, the second scheme may be a scheme for recognizing user gesture input using UWB OWR based on UWB announcement messages and UWB TWR with another device. The second scheme may be different from the first scheme which only uses UWB OWR based on UWB announcement messages to recognize user gesture input.

[0258] exist Fig. 10A and Fig. 10BIn the embodiment of the present invention, the first device (device #1) 1010, the second device (device #2) 1020 and the third device (device #3) 1030 may be Figure 8B A first device 810, a second device 820 and a third device 830.

[0259] exist Fig. 10A and Fig. 10B In the embodiment, for ease of explanation, it is assumed that the gaze direction (reference direction) of the user wearing the first device 1010 is the X-axis, the horizontal axis of the first device is assumed to be the Y-axis, and the vertical axis of the first device is assumed to be the Z-axis.

[0260] Fig. 10A An example of a signal pattern on the XY plane according to the second scheme is shown.

[0261] refer to Fig. 10A , the coordinates on the XY plane of the first electronic device 1010 may be expressed as (Xw, Yw), the coordinates on the XY plane of the second electronic device 1020 may be expressed as (Xm, Ym), and the coordinates on the XY plane of the third electronic device 1030 may be expressed as (Xa, Ya). A UWB announcement message (input signal) is sent from the second electronic device 1020 in the direction of the first electronic device 1010 and from the second electronic device 1020 in the direction of the third electronic device 1030. UWB messages (e.g., RIM, RRM, RFM, etc.) for UWB TWR may be exchanged between the first electronic device 1010 and the third electronic device 1030.

[0262] Fig. 10B An example of AoA information and distance information obtained according to the second scheme is shown.

[0263] refer to Fig. 10B , the first device 1010 as a UWB observer device may measure / calculate the AoA azimuth value θ of the first UWB announcement message received from the second device 1020 as a UWB observer device a2w . AoA azimuth value θ a2w It can be the relative angle between the gaze direction (X axis) of the user wearing the first device 1010 and the direction in which the first UWB announcement message (input signal) projected on the XY plane is received. AoA azimuth angle value θ a2w An example of a measurement can be made with Fig. 9B Same as shown.

[0264] In addition, the first device 1010 as a UWB observer device may measure / calculate the AoA elevation angle value Φ of the UWB announcement message received from the second device 1020 as a UWB announcer device. a2w . AoA elevation angle value Φa2w It can be the relative angle between the XY plane and the direction from which the UWB announcement message (incoming signal) is received. AoA elevation angle value Φ a2w An example of a measurement can be made with Fig. 9C Same as shown.

[0265] In addition, the third device 1030 as a UWB observer device may measure / calculate the AoA azimuth value θ of the second UWB announcement message received from the second device 1020 as a UWB announcer device. a2w . AoA azimuth value θ a2w The AoA azimuth value θ may be a relative angle between a reference direction of the third device 1030 (e.g., an axis orthogonal to the display of the third device 1030) and a direction in which the second UWB announcement message (second input signal) projected on the XY plane is received. a2w It can be included in the UWB message and sent to the first device 1010.

[0266] In addition, the first device 1010 may exchange a UWB message (UWB TWR message) of UWB TWR with the third device 1030 .

[0267] In this case, the first device 1010 may measure / calculate the AoA azimuth value θ of the UWB TWR message (eg, RIM or RRM) received from the third device 1030. a2w . AoA azimuth value θ a2w It may be the relative angle between the gaze direction (X axis) of the user wearing the first device 1010 and the direction in which the UWB TWR message (input signal) projected on the XY plane is received. In addition, the first device 1010 may measure / calculate the AoA elevation angle value Φ of the UWB TWR message (e.g., RIM or RRM) received from the third device 1030. a2w . AoA elevation angle value Φ a2w It may be the relative angle between the XY plane and the direction in which the UWB TWR message is received.

[0268] The third device 1030 may measure / calculate an AoA azimuth value θ of a UWB TWR message (eg, RIM or RRM) received from the first device 1010. a2w . AoA azimuth value θ a2w It can be the relative angle between the reference direction of the third device 1030 (e.g., the axis orthogonal to the display of the third device 1030) and the direction in which the UWB TWR message (input signal) projected on the XY plane is received. The AoA azimuth angle value θ measured in this way is a2wThe RRRM message may be included in a UWB TWR message (eg, RRRM) and transmitted to the first device 1010 .

[0269] The first device 910 may analyze the first AoA information (θ a2w , Φ a2w ) and the second AoA information (θ a2w , Φ a2w ) and recognizes a user gesture input based on the analysis result. For example, when the change pattern of the first AoA information and the second AoA information matches the pattern of the predefined user gesture input, the first device 1010 can recognize that the user's movement corresponds to the user gesture input.

[0270] When the user gesture input is recognized, the first device 1010 may transmit the data of the user gesture input to the third device 1030. As an embodiment, the first device 910 may transmit the data of the user gesture input to the third device 930 through in-band.

[0271] In the above embodiment of Figure 10, the second scheme can be used to identify the user gesture input. In this case, since UWB TWR is used together with UWR OWR to identify the user gesture input, the announcement period of UWR OWR is slower than the speed required for user gesture sensing, making it difficult to accurately identify the user gesture input using only UWR OWR.

[0272] Meanwhile, when the second scheme is used, the mobility of the first device 1010 and the third device 1030 may be estimated based on the result of the OWR and the result of the TWR.

[0273] For example, Fig. 10B As shown, the positions of the first device 1010, the second device 1020, and the third device 1030 form a triangle on the same plane (reference plane (XY plane)). In this case, a represents the distance between the first device 1010 and the third device 1030 on the reference plane, b represents the distance between the third device 1030 and the second device 1020 on the reference plane, and c represents the distance between the second device 1020 and the first device 1010 on the reference plane.

[0274] At the same time, the inner angle of the corresponding triangle can be obtained by using the AoA azimuth value obtained based on the UWR OWR and the AoA elevation value obtained based on the UWB TWR. This can be shown in the following equation 1.

[0275] [Equation 1]

[0276] |θ m2w -θ a2w|+|θ w2m -θ a2m |+λ=180

[0277] Meanwhile, a may be obtained by a result of UWB TWR (eg, a ToF value obtained by DS-TWR), and b and c may be obtained by Equation 2 below.

[0278] [Equation 2]

[0279] 1.a=b·cos∠(|∠θ w2m -∠θ a2m |)+c·cos∠(|∠θ m2w -∠θ a2w |)…①[First Cosine Theorem]

[0280] 2.b 2 =a 2 +c 2 -2ac·cos∠(|∠θ m2w -∠θ a2w |)…②[Second cosine theorem]

[0281] c 2 =b 2 +c 2 -2bc·cos∠(|∠θ w2m -∠θ a2m |)…③[Second cosine theorem]

[0282] 3. According to the two equations in 2, ②-③ are as follows

[0283] b 2 -c 2 =c 2 -b 2 -2a(b·cos∠(|∠θ w2m -∠θ a2m |)-c·cos∠(|∠θ

[0284] m2w -∠θ a2w |))…④

[0285] b 2 -c 2 -a(b·cos∠(|∠θ w2m -∠θ a2m |)-c·cos∠(|∠θ m2w -∠θ a2w |))=0…⑤

[0286] 4. When equation ① is replaced by equation ⑤,

[0287] b 2 -c2 -(b·cos∠(|∠θ w2m -∠θ a2m |)+c·cos∠(|∠θ m2w -∠θ a2w |))(b·cos∠(|∠θ w2m -∠θ a2m |)-c·cos∠(|∠θ m2w -∠θ a2w |))=0…⑥

[0288] b 2( 1-cos 2 ∠(|∠θ w2m -∠θ a2m |))-c 2 (1-cos 2 ∠(|∠θ m2w -∠θ a2w |))=0…⑦

[0289] 5. In equation ⑦, the relevant formulas for b and c are obtained as follows

[0290]

[0291] 6. The values ​​of b and c can be obtained because ∠(|∠θ m2w -∠θ a2w |)、∠(|∠θ w2m -∠θ a2m |) and a.

[0292] In this case, based on the values ​​(or relative ratios) of b and c and the UWB TWR result, whether the first device 1010 and the third device 1030 are moving and / or the relative positions can be estimated. Meanwhile, it is assumed that the position of the second device 1020 is fixed.

[0293] Fig.11 An exemplary process of a method for an electronic device to recognize a user gesture input based on AoA information according to a second solution according to an embodiment of the present disclosure is shown.

[0294] As described above, the second scheme may be a scheme for recognizing user gesture input using UWB OWR based on UWB announcement messages and UWB TWR with another device. The second scheme may be different from the first scheme which only uses UWB OWR based on UWB announcement messages to recognize user gesture input.

[0295] exist Fig.11In the embodiment of the present invention, the first device (wearable device #1) 1110, the second device (announcer device #2) 1120 and the third device (mobile device #3) 1130 can be respectively Figure 8B A first device 810, a second device 820 and a third device 830.

[0296] <First UWB Announcement (Announcement #1)>

[0297] refer to Fig.11 , in operation 1101-1, the second device 1120 may broadcast a first UWB announcement message, and the first device 1110 and the third device 1130 may receive the first UWB announcement message. The first UWB announcement message may be a first received UWB announcement message.

[0298] In operations 1102a-1 and 1102b-1, the first device 1110 and the third device 1130 may calculate AoA values ​​based on the received first UWB announcement message, respectively. The calculation of the AoA values ​​of the first device 1110 and the third device 1130 may involve the description of FIGS. 9 and 10.

[0299] In operation 1103, the first device 1110 may determine whether to use the second solution for user gesture recognition. As an embodiment, the first device 1110 may determine whether to use the second solution based on the announcement interval (or announcement period) of the UWB announcement message. For example, the first device 1110 may compare the announcement interval and the sampling rate (speed) of the UWB announcement message, and determine to use the second solution when the announcement interval is greater than the sampling rate.

[0300] When the second scheme is used, UWB TWR between the first device 1110 and the third device 1130 may be performed.

[0301] The UWB TWR session start request may be started when the UWB TWR session start request is transmitted from the first device 1110 to the third device 1130. As an embodiment, when it is identified in operation 1103 that the second scheme is used, the first device 1110 may transmit the UWB TWR session start request.

[0302] When the UWB TWR session stop request is transmitted from the first device 1110 to the third device 1130, the UWB TWR may be terminated.

[0303] In the above embodiment, it is disclosed that the first device 1110 sends the UWB TWR session start request and the UWB TWR session stop request, but the embodiment is not limited thereto. For example, the third device 1130 may send the UWB TWR session start request and / or the UWB TWR session stop request.

[0304] As an embodiment, the UWB TWR used in the second scheme may be a hybrid ranging scheme. The hybrid ranging scheme may be a scheme using scheduling-based ranging and contention-based ranging together.

[0305] As an embodiment, the UWB TWR used in the second scheme may be a DS-TWR scheme.

[0306] In operation 1104-1, the first device 1110 may sense a user's motion (Movement #1) based on a result of the UWR OWR and a result of the UWB TWR. In this way, the first device 1110 may recognize a user gesture input.

[0307] <Second UWB Announcement (Announcement #2)>

[0308] In operation 1101 - 2 , the second device 1120 may broadcast a second UWB announcement message, and the first device 1110 and the third device 1130 may receive the second UWB announcement message.

[0309] In operations 1102a-2 and 1102b-2, the first device 1110 and the third device 1130 may calculate AoA values ​​based on the received second UWB announcement message, respectively. The calculation of the AoA values ​​of the first device 1110 and the third device 1130 may involve the description of FIG.

[0310] As described above, UWB TWR may continue until a UWB TWR session stop request is sent from the first device 1110 to the third device 1130. Meanwhile, since the UWB announce message is received when the UWB TWR is not terminated, the first device 1110 does not need to determine again whether to use the second scheme to recognize a user gesture input.

[0311] In operation 1104-2, the first device 1110 may sense a user's motion (motion #2) based on the result of the UWR OWR and the result of the UWB TWR. In this way, the first device 1110 may recognize a user gesture input.

[0312] <Third UWB Announcement (Announcement #3)>

[0313] In operation 1101 - 3 , the second device 1120 may broadcast a third UWB announcement message, and the first device 1110 and the third device 1130 may receive the third UWB announcement message.

[0314] In operations 1102a-3 and 1102b-3, the first device 1110 and the third device 1130 may calculate AoA values ​​based on the received third UWB announcement message, respectively. The calculation of the AoA values ​​of the first device 1110 and the third device 1130 may involve the description of FIG.

[0315] Meanwhile, since the UWB announcement message is received when the UWB TWR is terminated, the first device 1110 may again determine whether to use the first scheme or the second scheme to recognize the user gesture input, and perform an operation for recognizing the user gesture input according to the determined scheme.

[0316] [Flow and exemplary operation of the first solution]

[0317] Fig.12 A flowchart of a method for an electronic device to recognize a user gesture input based on AoA information according to a first solution according to an embodiment of the present disclosure is shown. Fig.13 Shown according to Fig.12 An exemplary operation of the method.

[0318] As described above, the first scheme may be a scheme for recognizing a user gesture input using only UWB OWR based on a UWB announcement message. The first scheme may be distinguished from a second scheme for recognizing a user gesture input using UWB OWR based on a UWB announcement message and UWB TWR with another device.

[0319] exist Fig.12 and Fig.13 In the embodiment of the present invention, the wearable device, the announcer device and the mobile phone may be Fig. 8A A first device 810, a second device 820 and a third device 830.

[0320] refer to Fig.12 and Fig.13 In operation 1201, the first device (wearable device) may receive a UWB announcement message from a second device (announcement device) and measure a received signal strength indication (RSSI) and / or an AoA value of the received UWB announcement message. For example, as shown in operation 1301, the first device may receive a UWB announcement message from a second device.

[0321] At the same time, the first device may obtain the announcement period information included in the UWB announcement message (or control message), and determine to execute the first scheme (option 1) for recognizing the user gesture input based on the announcement period information. The determination of the scheme for recognizing the user gesture input may be performed before or after measuring the AoA value.

[0322] The first device may identify whether there is a user intention to initiate a service related to the UWB announcement message. For example, the first device may continue to measure the AoA value based on the periodically received UWB announcement message, and if the AoA value is still within a specific range for a specific period of time or longer, the first device may identify that there is a user intention to initiate a service. An example of such an operation for identifying a user intention may be as shown in operations 1202 and 1203 below.

[0323] In operation 1202, the first device may identify whether the AoA value is less than a preconfigured threshold value (θ) and whether the received signal strength is less than a preconfigured strength threshold value (strengthThreshold). When the AoA value is less than the preconfigured threshold value (θ) and the received signal strength is less than the preconfigured strength threshold value (strengthThreshold), the first device may configure the start time to be the current time. Otherwise, the first device may perform operation 1201 again.

[0324] In operation 1203, the first device may determine whether a value obtained by subtracting the start time from the current time is greater than a time threshold (timeThreshold). When the value obtained by subtracting the start time from the current time is not greater than the time threshold, the first device may update the current time and perform operation 1203 again. That is, the operation may still stay at operation 1203. When the value obtained by subtracting the start time from the current time is not greater than the time threshold, 1204 may continue.

[0325] For example, as shown in operations 1302 and 1303, the user wearing the first device can gaze at the second device up to a preconfigured time threshold (e.g., 3 seconds). In this case, both conditions of operations 1202 and 1203 can be met, and operation 1204 can continue.

[0326] In operation 1204, the first device may parse the received UWB announcement message and provide a notification (eg, voice, text notification) related to the UWB announcement message to the user. For example, as shown in operation 1304, the first device may parse the context of the UWB announcement message.

[0327] In operation 1205, the first device may send a request to obtain the announcement content to the third device (mobile phone). For example, as shown in operation 1305, the first device may send application data in a UWB announcement message to the third device.

[0328] In operation 1206, the third device may obtain the announcement content through the mobile network and send the obtained announcement content to the first device. For example, as shown in operation 1306-1, the third device may obtain service data from a server (online server) by using the received application data, and as shown in operation 1306-2, the third device may send the obtained service data to the first device.

[0329] In operation 1207, the first device may initiate a service (announcement service) related to the announcement content and start a user hands-free interaction (user gesture interaction). The user hands-free interaction may be performed by using the AoA information obtained based on the UWB announcement message. For example, as shown in operation 1307, the first device may start a hands-free interaction.

[0330] In operation 1208, the first device may perform motion sensing and user interaction. For example, the first device may recognize a user gesture input and perform an operation corresponding to the user gesture input. As an embodiment, the user gesture input may include a "yes" input (nod gesture), a "no" input (shaking head gesture), and / or a user-defined input (user-defined #1, #2, ... #3). For example, as shown in operation 1308, the first device may recognize a user gesture input and transmit data of the user gesture input to a third device.

[0331] [Flow and exemplary operation of the second solution]

[0332] Fig.14 A flowchart of a method for an electronic device to recognize a user gesture input based on AoA information according to a second solution according to an embodiment of the present disclosure is shown. Fig.15 Shown according to Fig.14 An exemplary operation of the method.

[0333] As described above, the second scheme may be a scheme for recognizing user gesture input based on UWB OWR of UWB announcement message and UWB TWR with another device. The second scheme may be different from the first scheme which only uses UWB OWR based on UWB announcement message to recognize user gesture input.

[0334] exist Fig.14 and Fig.15 In the embodiment of the present invention, the wearable device, the announcer device and the mobile phone may be Figure 8B A first device 810, a second device 820 and a third device 830.

[0335] refer to Fig.14 and Fig.15In operation 1401, the first device (wearable device) may receive a UWB announcement message from a second device (announcement device) and measure a received signal strength indication (RSSI) and / or an AoA value of the received UWB announcement message. For example, as shown in operation 1501, the first device may receive a UWB announcement message from a second device.

[0336] At the same time, the first device may obtain the announcement period information included in the UWB announcement message, and determine to execute the second scheme for recognizing the user gesture input (option 1) based on the announcement period information. The determination of the scheme for recognizing the user gesture input may be performed before or after measuring the AoA value.

[0337] In operation 1401a, UWB TWR may start from the first device and the third device (mobile phone). As an embodiment, UWB TWR may start according to a UWB TWR session start request from the first device.

[0338] The first device may identify whether there is a user intention to initiate a service related to the UWB announcement message. For example, the first device may continue to measure the AoA value based on the periodically received UWB announcement message, and if the AoA value is still within a specific range for a specific period of time or longer, the first device may identify that there is a user intention to initiate a service. An example of such an operation for identifying a user intention may be as shown in operations 1402 and 1403 below.

[0339] In operation 1402, the first device may identify whether the AoA value is less than a preconfigured threshold value (θ) and whether the received signal strength is less than a preconfigured strength threshold value (strengthThreshold). When the AoA value is less than the preconfigured threshold value (θ) and the received signal strength is less than the preconfigured strength threshold value (strengthThreshold), the first device may configure the start time to be the current time. Otherwise, the first device may perform operation 1401 again.

[0340] In operation 1403, the first device may determine whether a value obtained by subtracting the start time from the current time is greater than a time threshold (timeThreshold). When the value obtained by subtracting the start time from the current time is not greater than the time threshold, the first device may update the current time and perform operation 1403 again. That is, the operation may still stay at operation 1403. When the value obtained by subtracting the start time from the current time is not greater than the time threshold, 1404 may continue.

[0341] For example, as shown in operations 1502 and 1503, the user wearing the first device can gaze at the second device for a preconfigured time threshold (e.g., 3 seconds). In this case, both conditions of operations 1402 and 1403 can be met, and operation 1404 can continue.

[0342] In operation 1404, the first device may parse the received UWB announcement message and provide a notification (eg, voice, text notification) related to the UWB announcement message to the user. For example, as shown in operation 1504, the first device may parse the context of the UWB announcement message.

[0343] In operation 1405, the first device may send a request to obtain the announcement content to the third device (mobile phone). For example, as shown in operation 1505, the first device may send application data in a UWB announcement message to the third device.

[0344] In operation 1406, the second device may obtain the announcement content through the mobile network and send the obtained announcement content to the first device. For example, as shown in operation 1506-1, the third device may obtain service data from the server (online server) by using the received application data, and as shown in operation 1506-2, the third device may send the obtained service data to the first device.

[0345] In operation 1407, the first device may initiate a service (announcement service) related to the announcement content and start a user hands-free interaction (user gesture interaction). The user hands-free interaction may be performed by using the AoA information obtained based on the UWB announcement message and the AoA information obtained through the UWB TWR. For example, as shown in operation 1507, the first device may start a hands-free interaction.

[0346] In operation 1408, the first device may perform motion sensing and user interaction. For example, the first device may recognize a user gesture input and perform an operation corresponding to the user gesture input. As an embodiment, the user gesture input may include a "yes" input (nod gesture), a "no" input (shaking head gesture) and / or a user-defined input (user-defined #1, #2, ... #3). For example, as shown in operation 1508, the first device may recognize a user gesture input and transmit data of the user gesture input to a third device.

[0347] [Example of registering user gestures]

[0348] Fig.16 A method for an electronic device to register a user-defined gesture according to an embodiment of the present disclosure is shown. Fig.17 Shown according to Fig.16A graph of the AOA information obtained by the method for registering user-defined gestures.

[0349] exist Fig.16 In the embodiment of the present invention, a method of registering a user-defined gesture (custom gesture) by using the first device 1610 as a wearable device and the third device 1630 as a mobile device is exemplarily described. However, the embodiment is not limited thereto, and the user-defined gesture may be registered by using another type of device. For example, user-defined gesture registration using the first device 1610 as a wearable device and the second device as a UWB announcer device is also possible.

[0350] refer to Fig.16 , the first device 1610 can register the user gesture using UWB TWR with the third device 1630.

[0351] An exemplary process for registering a user gesture using UWB TWR may include at least one of the following steps:

[0352] Step 1: The third device 1630 may enter a mode for registering a user gesture (user gesture registration mode).

[0353] Step 2: A UWB TWR session may be started between the first device 1610 and the third device 1630. That is, a UWB TWR may be started.

[0354] Step 3: The user of the first device 1610 may wear the first device 1610 and be located at a specific distance based on the third device 1630 fixed at an arbitrary position. That is, the first device 1610 may be located at a specific distance from the third device 1630.

[0355] Step 4: When the specific distance condition is met, the third device 1630 may continue the process of registering the user gesture through a pre-configured scheme (e.g., a voice service scheme). For example, the third device 1630 may provide a voice notification such as "specify a gesture name", "specify a gesture action", "start recording gestures. 321 Start!", "n times completed", etc.

[0356] Step 5: The third device 1630 may record the AoA information obtained from the first device 1610 based on the UWB TWR. For example, when recording a gesture, the third device 1630 may continuously record the AoA information based on the UWB TWR received from the first device 1610.

[0357] An example of UWB TWR based AoA information recorded according to a pre-configured TWR sampling period (rate) may be as follows: Fig.17 As shown.

[0358] exist Fig.17 In the embodiment of FIG. 1 , it is assumed that the user gesture input to be registered is a shaking head gesture input (“no” input). Fig.17 , the AoA information (e.g., AoA azimuth value) corresponding to the user gesture input to be registered can be continuously recorded according to a pre-configured TWR sampling period (rate). Fig.17 As shown, when the user wearing the wearable device shakes his or her head to the left from the reference direction, a (+) AoA azimuth value may be recorded, and when shaking the head to the right from the reference direction, a (-) AoA azimuth value may be recorded.

[0359] Step 6: The recorded AoA information (or the graph (trajectory) of the AoA information) may be used as a reference for identifying a user gesture input. For example, when a user motion corresponding to the graph of the registered AoA information is identified, the electronic device may recognize that the corresponding user gesture input has been input. The recorded AoA information (or the graph of the AoA information) may be stored in a mapping table of user gestures.

[0360] [Embodiment of Multiple UWB Announcers]

[0361] Fig.18 A method for an electronic device to recognize a user gesture input by using AoA information obtained based on OWRs received from a plurality of UWB advertising devices according to an embodiment of the present disclosure is illustrated. Fig.19 Shown according to Fig.18 A graph of AOA information obtained by the method for recognizing user gestures.

[0362] Fig.18 The embodiment may be an extended embodiment of the above-mentioned first solution for identifying user input.

[0363] exist Fig.18 In the embodiment of the present invention, for convenience of explanation, a method is exemplarily described in which a first UWB device (or first device) 1810 as a UWB observer device recognizes a user gesture input by using AoA information obtained based on OWR messages (e.g., UWB announcement messages) received from a plurality of UWB announcer devices, the plurality of UWB announcer devices being 2-1 UWB device (or 2-1 device) 1820-1, 2-2 UWB device (or 2-2 device) 1820-2, and 2-3 UWB device (or 2-3 device) 1820-3. However, the embodiment is not limited thereto, and the UWB observer device may also recognize a user gesture input by using AoA information obtained from OWR messages (e.g., UWB announcement messages) received from different numbers (e.g., 2, 4, etc.) of UWB announcer devices.

[0364] An exemplary process of using UWB OWR to recognize a user gesture may include at least one of the following steps:

[0365] Step 1: The first device 1810 may receive OWR messages from a plurality of second devices (2-1 device 1820-1 to 2-3 device 1820-3), respectively.

[0366] Step 2: The first device 1810 may obtain and record AoA information based on each received OWB message.

[0367] Step 3: The first device 1810 may use the OWR message (or AoA measurement message) received from each second device of the ranging block (or ranging cycle) at a specific time point to chronologically record the amount of change in the AoA information of each second device based on the AoA information of each second device. An example of a graph representing the amount of change in the AoA information of each second device obtained from the ranging block at a specific time point may be as follows: Fig.19 shown.

[0368] exist Fig.19 In the embodiment of FIG. 1 , it is assumed that the user gesture input is a shaking head gesture input (“no” input). Fig.19 , the change amount of the AoA information of each second device in the ranging block (or loop) at a specific time point can be recorded in chronological order.

[0369] Step 4: The first device 1810 may identify a user gesture input corresponding to the sampled data by using the amount of change in the AoA information according to the recorded event as the sampled data. For example, if a curve graph (such as Fig.19 The electronic device can recognize the user gesture input corresponding to the shaking head input if the user gesture input is similar to the curve graph shown in the figure.

[0370] Step 5: The first device 1810 may send the data of the user gesture input to a third device via OOB, where the third device is a mobile device.

[0371] [Exemplary Motion Sensing Scenario for Multiple Mobile Devices]

[0372] Fig. 20 A motion sensing scenario using UWB OWR according to an embodiment of the present disclosure is shown. Fig.21 Shows the use of Fig. 20 A graph of AoA information collected for a motion sensing scenario.

[0373] exist Fig. 20In the embodiment of , it is assumed that OWR messages are sent from multiple mobile devices (e.g., wearable devices) to a single fixed device (e.g., a gaming device). In addition, it is assumed that the first mobile device 2010a is a wearable device (e.g., wearable glasses) worn on the user's head, and it is assumed that the multiple second mobile devices 2010b-1 and 2010b-2 are ring-type or wrist-type wearable devices worn on both wrists or two fingers of the user.

[0374] refer to Fig. 20 , each of the first mobile device 2010a and the plurality of second mobile devices 2010b-1 and 2010b-2 may send an OWB message (AoA measurement message). For example, the first mobile device 2010a may broadcast a second OWR message OWR#2, the 2-1 mobile device 2010b-1 may broadcast a first OWR message OWR#1, and the 2-2 mobile device 2010b-2 may broadcast a third OWR message OWR#3.

[0375] The fixed device (eg, gaming device) 2020 may receive the first OWB message, the second OWB message, and the third OWB message.

[0376] For example, in a scenario of recognizing hand motions of a virtual reality (VR) game, when both hands wearing the second mobile devices 2010b-1 and 2010b-2 move together to draw a single gesture (e.g., a heart-shaped gesture), the second mobile devices 2010b-1 and 2010b-2 may respectively send OWR information for AoA measurement to the fixed device 2020. In this case, the fixed device 2020 may use the AoA information collected in a specific ranging block (or cycle) (e.g., a UWB AoA measurement ranging block (or cycle)) for two-dimensional motion sensing. An example of a graph representing the AoA information collected in each UWB AoA measurement ranging block (or cycle) may be as follows: Fig.21 shown.

[0377] Fig.21 It may be a graph showing the relative positions of the second mobile devices 2010b-1 and 2010b-2 estimated in a 2D space by using the values ​​of the AoA information calculated using the OWB messages transmitted from the second mobile devices 2010b-1 and 2010b-2 respectively worn on both hands for each UWB AoA measurement ranging block (or cycle). Specifically, Fig.21 The left figure of corresponds to a graph showing the relative position of the wearable device 2010b-1 in the 2D space by using the AoA value obtained based on the OWR message (OWR#1) transmitted from the wearable device 2010b-1 worn on the right hand for each ranging block, and Fig.21The right figure of corresponds to a graph showing the relative position of the wearable device 2010b-1 in the 2D space by using the AoA value obtained based on the OWR message (OWR#2) transmitted from the wearable device 2010b-2 worn on the left hand for each ranging block. Fig. 20 and Fig.21 In the embodiment of the present invention, the structures of the ranging blocks and / or ranging cycles used to send the OWR message in the two second mobile devices 2010b-1 and 2010b-2 are the same and can be synchronized with each other. Examples of the ranging blocks and / or ranging cycles used to send the OWR message can be as described later. Fig.23 shown.

[0378] Fig.22A and Fig. 22B A graph of AoA information obtained based on a motion sensor and a graph of AoA information obtained based on an OWR according to an embodiment of the present disclosure are shown.

[0379] exist Fig.22A and Fig. 22B In an embodiment of the present invention, it is assumed that multiple wearable devices are worn on each hand (e.g., two fingers or two wrists) of the user, and the user wearing the multiple wearable devices moves both hands together to draw a single gesture (e.g., a heart-shaped gesture).

[0380] Fig.22A A graph of relative position estimation obtained when motion is sensed by using a motion sensor (eg, an IMU sensor) is shown.

[0381] When a motion sensor is used, motion data can be collected from each wearable device worn on both hands, and after the motion data is synchronized, motion sensing can be performed. In this case, the subject that synchronizes the motion data may be one of the wearable device or another device. However, since it is difficult to accurately synchronize the motion data, such as Fig.22A As shown, the entire graph combining the estimated position graphs has a relatively large error.

[0382] Fig. 22B A graph showing relative position estimation obtained when sensing motion by using UWB OWR is shown.

[0383] When using UWB OWR, the structures of the ranging blocks and / or ranging loops used to transmit OWR messages in the relevant devices are identical to each other and synchronized with each other, so no separate synchronization operation is required. In addition, as shown in FIG. 22 b, since the ranging blocks synchronized with each other of the same structure are used for UWB OWR, the entire graph combining the estimated position graphs has a smaller error than when using motion sensing. In this way, it is possible to accurately recognize user gesture input. An example of a ranging block / loop structure for sending an OWR message can be as described later. Fig.23 shown.

[0384] [Example of the structure of the ranging block / cycle of OWR and the format of the OWR message for AoA measurement]

[0385] Fig.23 An example of a structure of a ranging block for UWB OWR according to an embodiment of the present disclosure is shown.

[0386] Fig.23 The structure of the ranging block for UWB OWR can be as described above in Figures 1 to 23 An example of the structure of the ranging block for UWBOWR described in . At the same time, the structures of the ranging blocks used in multiple related devices (e.g., a pair of wearable devices (e.g., finger rings 1, 2), a pair of wearable devices (e.g., finger rings 1, 2) and another wearable device (e.g., glasses) can be the same and can be synchronized with each other.

[0387] exist Fig.23 In the present invention, for ease of description, it is assumed that the minimum number of RFRAMEs per ranging cycle (AoA measurement ranging cycle) for AoA measurement is 4 (MIN_FRAMES_PER_RR=4), but the embodiment is not limited thereto, and a different number of RFRAMEs may be transmitted in the AoA measurement ranging cycle.

[0388] refer to Fig.23 , multiple RFRAMEs may be sent by a single UWB announcer device during a ranging block.

[0389] As an embodiment, one ranging block may include only one AoA measurement ranging cycle.

[0390] As an embodiment, in an AoA measurement ranging cycle, the first RFRAME may be sent at the beginning of the ranging cycle.

[0391] As an embodiment, the UWB announcer device may configure the AoA measurement message (UWB announcer message) based on the configuration information of the minimum frame of the ranging cycle (MIN_FRAMES_PER_RR) and the inter-frame space configuration information.

[0392] MIN_FRAMES_PER_RR configuration information may indicate the minimum number of AoA measurement messages (i.e., RFRAMEs) sent by a UWB advertising device in a ranging block. Information on the number of AoA measurement messages (i.e., RFRAMEs) sent by a UWB advertising device in a ranging cycle (AoA measurement ranging cycle) may be included in the AoA measurement message.

[0393] When one or more AoA measurement messages are sent by the UWB advertising device in a ranging cycle, the sending interval between two consecutive AoA measurement messages may be the same as the value indicated by the interframe spacing configuration information. The interframe spacing configuration information may be included in the AoA measurement message.

[0394] When the UWB observer device receives an AoA measurement message in a ranging cycle, the UWB observer device may identify how many AoA measurement messages the UWB announcer device has sent in the corresponding ranging cycle and transmission interval based on the number of RRAMEs (NUM of RFRAMEs) and the inter-frame spacing configuration information included in the AoA measurement message.

[0395] The UWB advertising device may include the application data in the AoA measurement message and send the message. As an embodiment, the application data may include the context of the service to be advertised (eg, redirect address or content).

[0396] The application data may be included in one or more data message IEs. The data message IE may be included in the AoA measurement message. The UWB advertising device may set the maximum size of the data message IE in the AoA measurement message. The first data message IE may be included in the first RFRAME. The last RFRAME (multiple RFRAMEs) may not include a data message IE.

[0397] like Fig.23 As shown, when receiving the last data message IE of the application data, the UWB observer device can switch the value of the frame pending (FramePending) field of the MAC header (MHR) to 0.

[0398] An example of the AoA measurement message (ie, OWR message for AoA measurement) may be shown in Table 1 below.

[0399] [Table 1]

[0400]

[0401] Referring to Table 1, the AoA measurement message (such as another OWR message) may include three common fields (vendor OUI field, UWB message ID field, and OWR message type field), and may include a payload IE field (OWR message type related payload) configured according to the OWR message type field. An example of the payload IE field of the AoA measurement message may be shown in Table 2 below.

[0402] [Table 2]

[0403]

[0404] Referring to Table 2, the payload IE field of the AoA measurement message may be a message control field indicating the configuration of the message, an interframe spacing field indicating the interval between RFRAMEs transmitted in a ranging block, a block index field indicating a block index of a current ranging block (i.e., a ranging block in which the AOA measurement message or the RFRAME of the AoA measurement message is transmitted), and / or a block duration field indicating a block duration. The RFRAMEs transmitted in the ranging block may have the same value of the block index field. An example of the message control field within the payload IE field of the AoA measurement message may be as shown in Table 3 below.

[0405] [Table 3]

[0406]

[0407] Referring to Table 3, the message control field may include an RFRAME number field. The RFRAME number field may indicate the number of RFRAMEs sent in the same ranging cycle. The value of the RFRAME number field may be equal to or greater than the value of MIN_FRAMES_PER_RR. The UWB announcer device may send as many RFRAMEs as indicated by the RFRAME number field. In this case, two consecutive RFRAME number fields may be determined by the interframe spacing field. The UWB observer device may identify the number of RFRAMEs in the corresponding ranging cycle based on the value of the RFRAME number field included in the first AoA message of the ranging cycle.

[0408] Multiple RFRAMEs in a ranging cycle may be used to reduce the bias in the AoA measurements measured by the UWB device.

[0409] Fig.24 is a flowchart illustrating a method for a UWB device to recognize a user gesture input by using OWR according to an embodiment of the present disclosure.

[0410] exist Fig.24 In an embodiment, the UWB device may be Fig. 8A or Figure 8BThe first device (UWB observer device).

[0411] refer to Fig.24 In operation 2410, the UWB device may receive a UWB announcement message (AoA measurement message) for AoA measurement. As an embodiment, the UWB device may receive a UWB announcement message periodically broadcast from a UWB announcer device. As an embodiment, the UWB announcement message is a message for a UWB OWR and may include information about a transmission period of the UWB announcement message.

[0412] In operation 2420, the UWB device may determine a scheme for recognizing a user gesture input based on information about a transmission period in the UWB announcement message. As an embodiment, the scheme for recognizing a user gesture input may be a first scheme (option 1) of recognizing a user gesture input using only a UWB OWR based on a UWB announcement message, or a second scheme (option 2) of recognizing a user gesture input using a UWB TWR with another device (e.g., a third device 730) together with a UWB OWR based on a UWB announcement message.

[0413] When the scheme for recognizing the user gesture input is the first scheme, operation 2430 may continue. In operation 2430, the UWB device may recognize the user gesture input based on the AoA information of the plurality of received UWB announcement messages. As an embodiment, the AoA information may include information indicating the AoA azimuth and information indicating the AoA elevation.

[0414] When the scheme for recognizing the user gesture input is the second scheme, operation 2440 may continue. In operation 2440, the UWB device may initiate a TWR with another UWB device. As an embodiment, the another UWB device may be a UWB observer device.

[0415] In operation 2450, the UWB device may recognize a user gesture input based on AoA information of a plurality of received UWB announcement messages, second AoA information of a plurality of UWB messages obtained through TWR, and distance information to another UWB device.

[0416] As an embodiment, the UWB device may identify whether there is a user intention to initiate a service related to the UWB announcement message based on the received AoA information of the plurality of UWB announcement messages.

[0417] As an example, UWB announcement messages may be broadcast periodically from fixed UWB devices.

[0418] As an embodiment, the UWB announcement message may include application data related to the service to be initiated through the UWB announcement message.When the scheme for recognizing the user gesture input is the first scheme, the UWB device may send the application data to another UWB device.

[0419] As an example, the UWB announcement message may be sent in a single ranging cycle in a ranging block configured for AoA measurements.

[0420] Fig.25 is a device diagram of a UWB device according to an embodiment of the present disclosure.

[0421] exist Fig.25 In an embodiment of the present invention, the UWB device may perform the functions of a UWB announcer device or a UWB observer device.

[0422] refer to Fig.25 , the UWB device may include a transceiver 2510, a controller 2520, and a storage unit 2530. In the present disclosure, the controller may be defined as a circuit, an application specific integrated circuit, or at least one processor.

[0423] The transceiver 2510 may transmit and receive signals to and from another entity. The transceiver 2510 may transmit and receive data to and from another UWB device by using, for example, UWB communication or OOB communication (eg, BLE communication).

[0424] The controller 2520 may control the overall operation of the electronic device according to the embodiment proposed in the present disclosure. For example, the controller 2520 may control the signal flow between the corresponding blocks to perform the operation according to the above flowchart. Specifically, the controller 2520 may control, for example, the reference Figures 1 to 24 Operations are described for providing service initiation and user gesture input methods using UWB OWR.

[0425] The storage unit 2530 may store at least one of information transmitted and received via the transceiver 2510 and information generated via the controller 2520. Figures 1 to 24 The storage unit 2530 may store information and data necessary to provide a service initiation and a user gesture input method using, for example, UWB OWR.

[0426] In the above-mentioned specific embodiments, the components included in the present disclosure are expressed in singular or plural form according to the specific embodiment proposed. However, for the convenience of explanation, the singular or plural expression is selected to suit the presented situation, and the present disclosure is not limited to singular or plural components, and even if the components are expressed in plural form, they may also be composed of singular forms, or even if the components are expressed in singular form, they may also be composed of plural forms.

[0427] Although the detailed description of the present disclosure has described specific embodiments, it is apparent that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined by the scope of the appended patent claims and the equivalents of the scope of the patent claims.

Claims

1. A method of a first ultra-wideband (UWB) device, comprising: receiving, from the second UWB device, a first UWB announcement message for measuring an angle of arrival AoA with a third UWB device, wherein the UWB announcement message is a message for UWB one-way ranging (OWR) and includes information about a transmission period of the UWB announcement message; and determining a scheme for identifying a user gesture input of the first UWB device based on the information related to the transmission period, The scheme for identifying the user gesture input is one of a first scheme for identifying the user gesture input using the UWB OWR and a second scheme for identifying the user gesture input using both the UWB OWR and a UWB two-way ranging TWR with the third UWB device.

2. The method according to claim 1, in, Determining a scheme for identifying the user gesture input of the first UWB device includes: In a case where the transmission period of the UWB announcement message is greater than a sampling rate, the second scheme is determined as a scheme for recognizing the user gesture input of the first UWB device.

3. The method according to claim 1, further comprising: In a case where the scheme for recognizing the user gesture input is the second scheme, the user gesture input is recognized based on first AoA information for multiple received UWB announcement messages, second AoA information for multiple UWB messages obtained through the TWR, and information about the distance to the third UWB device.

4. The method according to claim 1, further comprising: In a case where the scheme for recognizing the user gesture input is the second scheme, a UWB TWR session start request is sent to the third UWB device.

5. The method according to claim 1, wherein: The UWB announcement message is broadcast periodically from a fixed UWB device.

6. The method according to claim 1, wherein: The UWB announce message includes application data related to a service to be initiated via the UWB announce message.

7. The method according to claim 3, further comprising: receiving, from the second device, a second UWB announcement message for performing angle of arrival AoA measurement with a third UWB device; as well as In a case where the UWB TWR session is not terminated, the second scheme is determined as a scheme for recognizing the user gesture input of the first UWB device.

8. The method according to claim 1, wherein: The UWB announcement message is sent within a single ranging cycle configured for AoA measurements within a ranging block.

9. A first ultra-wideband (UWB) device, comprising: Transceiver; as well as Controller, Wherein, the controller is configured as: receiving, from the second UWB device, a first UWB announcement message for measuring an angle of arrival AoA with a third UWB device, wherein the UWB announcement message is a message for UWB one-way ranging (OWR) and includes information about a transmission period of the UWB announcement message; and determining a scheme for identifying a user gesture input of the first UWB device based on the information related to the transmission period, and The scheme for identifying the user gesture input is one of a first scheme for identifying the user gesture input using the UWB OWR and a second scheme for identifying the user gesture input using both the UWB OWR and a UWB two-way ranging TWR with the third UWB device.

10. The first UWB device according to claim 9, wherein: Determining a scheme for identifying the user gesture input of the first UWB device includes: In a case where the transmission period of the UWB announcement message is greater than a sampling rate, the second scheme is determined as a scheme for recognizing the user gesture input of the first UWB device.

11. The first UWB device according to claim 9, wherein: The controller is configured to, when the scheme for recognizing the user gesture input is the second scheme, recognize the user gesture input based on first AoA information for multiple received UWB announcement messages, second AoA information for multiple UWB messages obtained through the TWR, and information about the distance to the third UWB device.

12. The first UWB device according to claim 9, wherein: The controller is configured to: In a case where the scheme for recognizing the user gesture input is the second scheme, a UWB TWR session start request is sent to the third UWB device.

13. The first UWB device according to claim 9, wherein: The UWB announcement message is broadcast periodically from a fixed UWB device.

14. The first UWB device according to claim 9, in, The UWB announce message includes application data related to a service to be initiated via the UWB announce message, and The UWB announcement message is sent within a single ranging cycle configured for the AoA measurement within a ranging block.

15. The first UWB device according to claim 11, wherein: The controller is configured to: receiving, from the second device, a second UWB announcement message for performing angle of arrival AoA measurement with a third UWB device; as well as In a case where the UWB TWR session is not terminated, the second scheme is determined as a scheme for determining the user gesture input of the first UWB device.

Images