The disclosure relates to UWB communication and, more specifically, to a method and apparatus for controlling a non-UWB device using UWB.
The Internet is evolving from the human-centered connection network by which humans create and consume information to the Internet of Things (IoT) network by which information is communicated and processed between things or other distributed components. Another arising technology is the Internet of Everything (IoE), which is a combination of the Big data processing technology and the IoT technology through, e.g., a connection with a cloud server. Implementing the IoT requires technical elements, such as sensing technology, a wired/wireless communication and network infrastructure, service interface and security technologies. A recent ongoing research for thing-to-thing connection is on techniques for sensor networking, machine-to-machine (M2M), or machine-type communication (MTC).
In the IoT environment may be offered intelligent Internet Technology (IT) services that collect and analyze the data generated by the things connected with one another to create human life a new value. The IoT may have various applications, such as the smart home, smart building, smart city, smart car or connected car, smart grid, health-care, or smart appliance industry, or state-of-art medical services, through conversion or integration of conventional information technology (IT) techniques and various industries.
As wireless communication systems evolve to provide various services, a need arises for a method for effectively providing such services. For example, it is possible to use a ranging technique for measuring the distance between electronic devices using ultra-wide band (UWB).
The disclosure provides a method for identifying the position of a non-UWB device that does not support UWB ranging using UWB ranging between UWB devices. The disclosure also provides a method for recognizing and controlling a non-UWB device whose position is identified using UWB ranging between UWB devices, by using a UWB device.
According to various embodiments of the disclosure, a method by a first UWB device may comprise identifying a position of a non-UWB device with respect to a position of a second UWB device based on UWB ranging between the first UWB device and the second UWB device and recognizing the non-UWB device based on a point direction of the first UWB device and the identified position of the non-UWB device.
According to various embodiments of the disclosure, a first UWB device may comprise a memory, a transceiver, and a controller connected to the memory and the transceiver. The controller may be configured to identify a position of a non-UWB device with respect to a position of a second UWB device based on UWB ranging between the first UWB device and the second UWB device and recognize the non-UWB device based on a point direction of the first UWB device and the identified position of the non-UWB device.
According to the method of the disclosure, it is possible to identify the position of a non-UWB device not supporting UWB ranging. Further, according to the method of the disclosure, it is possible to recognize and control a non-UWB device using a UWB device.
Hereinafter, embodiments of the disclosure are described in detail with reference to the accompanying drawings.
In describing embodiments, the description of technologies that are known in the art and are not directly related to the present invention is omitted. This is for further clarifying the gist of the present disclosure without making it unclear.
For the same reasons, some elements may be exaggerated or schematically shown. The size of each element does not necessarily reflects the real size of the element. The same reference numeral is used to refer to the same element throughout the drawings.
Advantages and features of the present disclosure, and methods for achieving the same may be understood through the embodiments to be described below taken in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed herein, and various changes may be made thereto. The embodiments disclosed herein are provided only to inform one of ordinary skilled in the art of the category of the present disclosure. The present invention is defined only by the appended claims. The same reference numeral denotes the same element throughout the specification.
It should be appreciated that the blocks in each flowchart and combinations of the flowcharts may be performed by computer program instructions. Since the computer program instructions may be equipped in a processor of a general-use computer, a special-use computer or other programmable data processing devices, the instructions executed through a processor of a computer or other programmable data processing devices generate means for performing the functions described in connection with a block(s) of each flowchart. Since the computer program instructions may be stored in a computer-available or computer-readable memory that may be oriented to a computer or other programmable data processing devices to implement a function in a specified manner, the instructions stored in the computer-available or computer-readable memory may produce a product including an instruction means for performing the functions described in connection with a block(s) in each flowchart. Since the computer program instructions may be equipped in a computer or other programmable data processing devices, instructions that generate a process executed by a computer as a series of operational steps are performed over the computer or other programmable data processing devices and operate the computer or other programmable data processing devices may provide steps for executing the functions described in connection with a block(s) in each flowchart.
Further, each block may represent a module, segment, or part of a code including one or more executable instructions for executing a specified logical function(s). Further, it should also be noted that in some replacement embodiments, the functions mentioned in the blocks may occur in different orders. For example, two blocks that are consecutively shown may be performed substantially simultaneously or in a reverse order depending on corresponding functions.
As used herein, the term “unit” means a software element or a hardware element such as a field-programmable gate array (FPGA) or an application specific integrated circuit (ASIC). A unit plays a certain role. However, a ‘unit’ is not limited to software or hardware. A ‘unit’ may be configured in a storage medium that may be addressed or may be configured to execute one or more processors. Accordingly, as an example, a ‘unit’ includes elements, such as software elements, object-oriented software elements, class elements, and task elements, processes, functions, attributes, procedures, subroutines, segments of program codes, drivers, firmware, microcodes, circuits, data, databases, data architectures, tables, arrays, and variables. Functions provided within the components and the ‘units’ may be combined into smaller numbers of components and ‘units’ or further separated into additional components and ‘units’. Further, the components and ‘units’ may be implemented to execute one or more CPUs in a device or secure multimedia card. According to embodiments of the disclosure, a “ . . . unit” may include one or more processors.
As used herein, the term ‘terminal’ or ‘device’ may also be referred to as a mobile station (MS), user equipment (UE), user terminal (UT), terminal, wireless terminal, access terminal (AT), subscriber unit, subscriber station (SS), wireless device, wireless communication device, wireless transmit/receive unit (WTRU), mobile node, or mobile or may be referred to in other terms. Various embodiments of the terminal may include cellular phones, smart phones with wireless communication capabilities, personal digital assistants (PDAs) with wireless communication capabilities, wireless modems, portable computers with wireless communication capabilities, capturing/recording/shooting/filming devices, such as digital cameras, having wireless communication capabilities, game players with wireless communications capabilities, music storage and playback home appliances with wireless communications capabilities, Internet home appliances capable of wireless Internet access and browsing, or portable units or terminals incorporating combinations of those capabilities. Further, the terminal may include a machine to machine (M2M) terminal and a machine-type communication (MTC) terminal/device, but is not limited thereto. In the disclosure, the terminal may be referred to as an electronic device or simply as a device.
Hereinafter, the operational principle of the disclosure is described below with reference to the accompanying drawings. When determined to make the subject matter of the disclosure unnecessarily unclear, the detailed description of known functions or configurations may be skipped in describing embodiments of the disclosure. The terms as used herein are defined considering the functions in the present disclosure and may be replaced with other terms according to the intention or practice of the user or operator. Therefore, the terms should be defined based on the overall disclosure.
Hereinafter, embodiments of the present invention are described in detail with reference to the accompanying drawings. Further, although a communication system using UWB (e.g., the UWB communication system specified by the FiRa Consortium) is described in connection with embodiments of the present invention, as an example, embodiments of the present invention may also apply to other communication systems with similar technical background or features. For example, a communication system using Bluetooth or ZigBee may be included therein. Further, embodiments of the present invention may be modified in such a range as not to significantly depart from the scope of the present invention under the determination by one of ordinary skill in the art and such modifications may be applicable to other communication systems.
When determined to make the subject matter of the present invention unclear, the detailed description of the known art or functions may be skipped. The terms as used herein are defined considering the functions in the present disclosure and may be replaced with other terms according to the intention or practice of the user or operator. Therefore, the terms should be defined based on the overall disclosure.
In general, wireless sensor network technology is largely divided into a wireless local area network (WLAN) technology and a wireless personal area network (WPAN) technology according to the recognition 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 100 m. WPAN is a technology based on IEEE 802.15 which includes Bluetooth, ZigBee, and ultra-wide band (UWB). A wireless network in which such a wireless network technology is implemented may include a plurality of electronic devices.
According to the definitions by 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 a band itself to which UWB communication is applied. UWB may enable secure and accurate ranging between devices.
Operations of a UWB-based service may include a service initiation step for initiating the UWB-based service, a key provisioning step for providing a key for security, a discovery step for discovering a device, a connection step including secure channel creation and parameter exchange, and/or a UWB ranging step for measuring a distance/direction (angle) between devices.
Meanwhile, according to an embodiment, some steps may be omitted. For example, in an embodiment, the service initiation step and the UWB ranging step may be mandatory steps, but the key provisioning step, discovery step, and connection step may be optional steps. As another example, in another embodiment, the service initiation step, the key provisioning step, and the UWB ranging step may be mandatory steps, but the discovery step and connection step may be optional steps.
The terminology used herein is provided for a better understanding of the disclosure, and changes may be made thereto without departing from the technical spirit of the disclosure.
“Application dedicated file (ADF)” may be, e.g., a data structure capable of hosting application specific data or security data (e.g., credential, cryptographic key) used by an application or secure element (SE) (e.g., embedded SE (eSE)).
“Application protocol data unit (APDU)” may be a command and a response used when communicating with a secure element (SE) (e.g., embedded SE).
“Application specific data” may be, e.g., data used by a specific service and application regardless of the place (e.g., applet, device, etc.).
“Controller” may be a ranging device that defines and controls ranging control messages (RCM) (or control messages). In the disclosure, the ranging device may be, e.g., a ranging device (RDEV) or an enhanced ranging device (ERDEV) as defined in the IEEE Std 802.15.4/4z standard.
“Controllee” may be a ranging device using a ranging parameter in the RCM (or control message) received from the controller.
Unlike “static STS,” “dynamic STS” may be an operation mode in which the STS is not repeated during a ranging session. In an embodiment, the STS may be managed by the ranging device, and the ranging session key that generates STS may be managed by a secure component.
“Applet” may be an applet that implements an APDU interface running on a secure component and is identified by an application (applet) ID (AID). This applet may host the data needed for secure ranging. In an embodiment, the applet may be, e.g., a FiRa applet as defined in the FIRA CONSORTIUM COMMON SERVICE & MANAGEMENT LAYER (CSML) specifications.
“Ranging device” is a ranging device that may communicate with another ranging device using a pre-defined profile (e.g., UWB-enabled door lock) or a ranging device capable of supporting a pre-defined UWB ranging service for performing a ranging session with another ranging device. In this disclosure, the ranging device may be referred to as a UWB device or a UWB ranging device. In an embodiment, the ranging device may be, e.g., a FiRa device as defined in the FIRA CONSORTIUM CSML specification.
“UWB-enabled application” may be an application using a Framework API for configuring an OOB Connector, a Secure Service, and/or a UWB service for a UWB session. In this disclosure, “UWB-enabled Application” may be abbreviated as an application or a UWB application. In an embodiment, the UWB-enabled application may be, e.g., a FiRa-enabled application defined in the FIRA CONSORTIUM CSML specification.
“Framework” may be, e.g., a collection of logical software components including an OOB connector, secure Service, and/or UWB service. In an embodiment, the framework may be, e.g., FiRa Framework as defined in the FIRA CONSORTIUM CSML specification.
“OOB Connector” may be a software component for establishing out-of-band (OOB) communication (e.g., Bluetooth low energy (BLE) communication) between ranging devices. In an embodiment, the OOB connector may be, e.g., a FiRa OOB connector as defined in the FIRA CONSORTIUM CSML specification.
“Profile” may be a previously defined set of UWB and OOB configuration parameters. In an embodiment, the profile may be, e.g., a FiRa profile as defined in the FIRA CONSORTIUM CSML specification.
“Profile manager” may implement a profile available on the ranging device. In an embodiment, the profile manager may be, e.g., a FiRa profile manager as defined in the FIRA CONSORTIUM CSML specification.
“Smart ranging device” may be a ranging device (e.g., physical access reader) capable of hosting one or more UWB-enabled applications and implementing the framework or a ranging device that implements a specific screen application provided by the manufacturer. The smart ranging device may be a ranging device capable of installing multiple UWB-enabled applications to support a UWB ranging-based service to perform a ranging session with another ranging device or smart ranging device. In an embodiment, the smart ranging device may be, e.g., a FiRa smart device as defined in the FIRA CONSORTIUM CSML specification.
“Global Dedicated File (GDF)” may be a root level of application specific data including data required to establish a USB session.
“Framework API” may be an API used by a UWB-enabled Application to communicate with the Framework.
“Initiator” may be a Ranging Device that initiates a ranging exchange.
“Object identifier (OID)” may be an identifier of the ADF in the application data structure or a unique ID for identifying a service provider SP.
“Out-of-band (OOB)” may be data communication that does not use UWB as an underlying wireless technology.
“Responder” may be a ranging device that responds to the Initiator in a ranging exchange.
“Scrambled timestamp sequence (STS)” may be a ciphered sequence for increasing the integrity and accuracy of ranging measurement timestamps. In an embodiment, the STS may be generated from the ranging session key.
“Secure channel” may be a data channel that prevents overhearing and tampering.
“Secure component” may be a component that interfaces with UWBS for the purpose of providing RDS to UWBS, e.g., when dynamic STS is used. It may also host UWB-enabled application data.
“Secure Element (SE)” may be a tamper-resistant secure hardware component that may be used as a Secure Component in the Ranging Device.
“Secure service” may be a component for interfacing with the secure component of the system, such as trusted execution environment (TEE) or secure element.
“Static STS” is an operation mode in which STS is repeated during a session, and does not need to be managed by the secure component.
“SUS applet” may be an applet on the secure component operating as an end point for the secure channel between secure components, such as UWBS and SE.
“UWB Service” may be an implementation-specific software component that provides access to the UWBS.
It may be considered that the “UWB session” is established when the controller and controllee(s) may start UWB ranging. The UWB session may be a period from when the controller and the controlee start communication through UWB until the communication stops. A UWB Session may include ranging, data transfer, or both ranging and data transfer.
“UWB session ID” may be an ID (e.g., an integer) for identifying the UWB session.
“UWB session key” may be a key used to protect the UWB Session. In an embodiment, the UWB session key may be used to generate the STS. In this disclosure, the UWB session key may be a UWB ranging session key (URSK), and may be abbreviated as a session key.
“UWB Subsystem (UWBS)” may be a hardware component implementing the UWB PHY and MAC specifications. The UWBS may have an interface to the FiRa framework where the UCI logical interface layer has been implemented and an interface for the secure component to search for the RDS. In an embodiment, the UWB PHY and MAC specifications may be, e.g., the FiRa CONSORTIUM PHY and MAC specifications.
When determined to make the subject matter of the present invention unnecessarily unclear, the detailed description of related known functions or features may be skipped in describing the disclosure.
Hereinafter, various embodiments of the disclosure are described with reference to the accompanying drawings.
The electronic device (UWB device) of
Referring to
The UWB-enabled application layer 100 may be a layer of an application (e.g., FiRa-enabled application) using the framework API to constitute an OOB connector, secure service, and UWB service for, e.g., a UWB session.
The common service & management layer 110 may define a common component and procedure necessary to implement, e.g., UWB secure ranging.
The UWB MAC layer and the UWB physical layer may be collectively referred to as a UWB subsystem (UWBS) 130. The UWBS may be based on the FiRa PHY and MAC specifications referencing the IEEE 802.15.4z specifications.
Referring to
The first electronic device 210 may host, e.g., one or more UWB-enabled Applications 211, which may be installed by the user (e.g., a mobile phone). It may be based on the framework API. The second electronic device 220 does not provide a framework API, and for example, may use a proprietary interface to implement a specific UWB-enabled application 221 provided only by the manufacturer.
Unlike shown, according to an embodiment, both the first electronic device 210 and the second electronic device 220 may be smart ranging devices or ranging devices.
The first electronic device 210 and the second electronic device 220 may include UWB-enabled application layers 211 and 221, frameworks 212 and 222, OOB components/connectors 213 and 223, secure components 214 and 224, and/or UWBSs 215 and 225. According to an embodiment, some components may be omitted, and an additional component may further be included.
The first electronic device 210 and the second electronic device 220 may generate an OOB connection (channel) through the OOB connectors 213a and 223a (e.g., BLE connectors) and generate a UWB connection (channel) through the UWBSs 215 and 225 and communicate with each other.
The framework 300 of
The framework 300 may be a set of logical software components. The UWB-enabled application may interface with the framework 300 through the framework API provided by the framework.
Referring to
The profile manager component 310 may manage a profile(s) available on the ranging device. The profile may be a set of UWB and OOB configuration parameters required to establish a successful UWB session between ranging devices. The profile manager 310 may abstract the UWB and OOB configuration parameters from the UWB-enabled application.
The OOB connector 320 may be a component for establishing an OOB connection between ranging devices. The OOB connector 320 may handle the discovery phase and connection phase for providing a UWB-based service.
The secure service 330 may serve to interface with a secure component, such as a secure element (SE), eSE, or trusted execution environment (TEE). The secure component may be a component that interfaces with the UWBS to transfer UWB ranging data to the UWBS.
The SE is a safe secure module based on tamper resistant characteristics and, if no contract relationship is established between various entities, installation and driving of an application are limited.
The eSE means a fixed SE fixed and used in the electronic device. The eSE is typically manufactured exclusively for the manufacturer at the request of the terminal manufacturer, and may be manufactured including the operating system and framework. For the eSE, a service control module in the form of an applet may be remotely downloaded and installed and be used for various secure services, such as e-wallet, ticketing, e-passport, or digital key.
The TEE may be an S/W-centered secure environment that creates a virtual separated environment based on, e.g., a code supported by a specific chipset (e.g., ARM-based). The TEE has tampered resistant characteristics but has the advantages of large available memory, high speed, and low costs as compared with the SE. Further, since various service providers are immediately available within a range allowed by the mobile manufacturer, the TEE has the advantage of low complexity between entities as compared with the SE.
The UWB service 340 may be a component that provides access to the UWBS.
The UWB device of
In the embodiment of
The second electronic device (the second UWB device) corresponds to a ranging device that responds to the ranging initiation message received from the initiator. In the disclosure, the second electronic device may be referred to as a responder. In an embodiment, the responder may transmit a ranging response message 420.
In an embodiment, the first electronic device may be a controller, and the second electronic device may be a controllee. The opposite may also be met. Here, the controller may be a ranging device that defines and controls a ranging feature by transmitting a control message. The controllee may be a ranging device using a ranging feature configured through the control message from the controller.
In an embodiment, the first electronic device and the second electronic device may perform a ranging operation using a preset ranging method. In an embodiment, the ranging method may include a two-way ranging (TWR) scheme and/or a one-way ranging (OWR) scheme. In an embodiment, the TWR scheme may include single-sided two-way ranging (SS-TWR) and/or double-sided two-way ranging (DS-TWR). For the ranging methods, refer to the IEEE 802.15.4/4z standard and the description of FiRa CONSORTIUM referencing the standard.
Through the UWB ranging operation, the first electronic device and/or the second electronic device may obtain distance information and direction information, and identify a relative position of the UWB device based on the distance information and direction information.
In an embodiment, the distance information may include time-of-flight (ToF) information (ToF measurement information). The ToF corresponds to the UWB propagation time between the transmitter and the receiver. By using accurate message timestamping, the ToF may provide accurate estimation of the relative distance between the two devices. The ToF information may be measured by either or both of the ranging devices, and may be exchanged between the initiator and the responder through a predefined signaling scheme (e.g., a control message including a UWB ranging result).
In an embodiment, the direction information may include angle-of-arrival (AoA) information (AoA measurement information). AoA may be obtained by measuring the phase difference or the difference in the arrival time of the arrival signal in the antennas. The AoA information may include an AoA azimuth (horizontal angle) and an AoA elevation (vertical angle). The AoA information, together with the ToF information, may be used to determine a relative position of the UWB device. The AoA information may be measured by either or both of the ranging devices, and may be exchanged between the initiator and the responder through a predefined signaling scheme (e.g., a control message including a UWB ranging result).
In an embodiment, the PHY packet including the ranging frame (e.g., UWB initiation message/response message) may include an STS. Whether the PHY packet includes the STS, the position where the STS is included, and the structure of the packet may vary depending on the STS packet configuration. Here, the STS corresponds to an encrypted sequence used to increase integrity and accuracy of the ranging measurement timestamp. When the STS is used, the initiator and the responder should share the STS seed (e.g., ranging session key) used to generate and restore the STS in advance. The sharing of the ranging session key may be performed, e.g., through a secure channel established through BLE.
Hereinafter, various embodiments of a method for registering and recognizing a UWB-disabled device (apparatus) using UWB ranging between UWB-enabled devices (apparatuses) are described with reference to each drawing.
In the disclosure, various embodiments are described under the assumption that one of the UWB support devices is a reference device (e.g., a TV) supporting UWB ranging, and the other is a user equipment (UE) (e.g., the user's smartphone) supporting UWB ranging, and various embodiments. However, the disclosure is not limited thereto, and the UWB-enabled device may be various electronic devices supporting UWB ranging. In an embodiment, the reference device and the UE may be one of the first UWB device or the second UWB device described above with reference to
In the disclosure, the UE supporting UWB ranging may be referred to as a UWB UE, a UE, a first UWB-enabled device, a first UWB device, or a first UWB apparatus. Also, the reference device supporting UWB ranging may be referred to as a UWB reference device or a reference device, a second UWB-enabled device, a second UWB device, or a second UWB apparatus.
In the disclosure, a UWB-disabled device is a device to be controlled by a UWB-enabled device (e.g., a UE), and may be referred to as a target device, a non-UWB device, or a non-UWB apparatus.
The embodiment of
In the embodiment of
Instead, the UE 10 may register and recognize the target device 30 using the result of UWB ranging with the reference device 20. Accordingly, the UE 10 may point at and control the target device 30 even if the distance between the UE 10 and the target device 30 is not directly measured/calculated by using a ranging procedure (e.g., UWB ranging). In this case, the UE 10 may control the UWB-disabled device, thereby expanding the user experience using the UWB.
Hereinafter, various embodiments of a procedure for registering and recognizing a target device 30 are described with reference to each drawing.
In the embodiment of
Meanwhile, as compared with the third option, the first option and the second option have poor accuracy of the position of the target device 30 but has the advantage of a reduced time required for registration.
In the embodiment of
In an embodiment, the registration procedure may be performed by the plurality of UEs 10-1 and 10-2. However, the disclosure is not limited thereto, and according to an embodiment, the registration procedure may be performed by the reference device 20.
Meanwhile, in the embodiment of
In the embodiment of
The recognition procedure may include two steps, e.g., the first step illustrated in
The first step corresponds to a step of identifying (or calculating) the distance h between the straight line component in the direction pointed by the UE 10 and the target device 30. An example method of calculating the distance h is described below with reference to
The second step corresponds to a step in which the UE 10 recognizes the target device 30 by identifying (or determining) whether the distance h meets a preset threshold. In an embodiment, the second step may include determining whether the distance h is smaller than the threshold (determining whether a recognition condition is met), when the distance h is smaller than the threshold (or smaller than or equal to the threshold), recognizing that the UE 10 points at the target device 30 (recognizing the target device 30), and when the distance h is larger than or equal to the threshold (or larger than the threshold), refraining from recognizing that the UE 10 points at the target device 30.
In an embodiment, the threshold may be set to different criteria/conditions/methods according to options used in the registration procedure of the target device 30. For example, when the registration procedure of option 1 is used, the threshold may be set based on the guided distance d. For example, ½ of the distance d may be set to the threshold. As another example, when the registration procedure of option 3 is used, the threshold may be set based on the number of pointing positions. For example, when the number of pointing positions increases, the threshold may be set to decrease. For example, the threshold when the number of pointing positions is 3 may be set to a value smaller than the threshold when the number of pointing positions is 2. This is because, as the number of pointing positions increases, the position accuracy of the target device 30 increases, and thus, even if the threshold for a large number of pointing positions is set to a small value, it does not significantly affect the accuracy of recognition.
In an embodiment, the threshold may be set to differ depending on the type and/or size (or area) of the target device 30 to be registered. For example, in the case of a target device having a relatively larger size (or area) than other devices, a relatively larger threshold than those of the other devices may be set as the threshold of the target device. This may contribute to device recognition.
In an embodiment, the type and/or size (or area) of the target device 30 may be identified based on a user input received within the above-described registration procedure (step) or before the registration step. For example, before or within the registration step, the user may select the type and size (or area) of the target device 30 to be registered through a user input. As another example, before or within the registration step, the user may select only the type of the target device 30 to be registered through a user input. In this case, the area of the target device 30 may be identified based on the selected type of the target device 30.
In an embodiment, when the recognized target device 30 is present, the UE 10 may provide control information for controlling the target device 30 to the user (e.g., display a control UX).
In the embodiment of
The registration procedure of
Through the registration procedure, the position of the target device 30 may be identified with respect to the position (reference position) of the reference device 20. The identified position of the target device 30 may be stored and used in a subsequent recognition procedure.
In the embodiment of
In an embodiment, the first step (operation) may be performed using UWB ranging between the UE 10 and the reference device 20. For example, the UWB two-way ranging (TWR) scheme described with reference to
As a result of the UWB ranging, distance information (e.g., ToF information) indicating the distance between the reference device 20 and the UE 10 and direction (angle) information (e.g., angle-of-arrival (AoA) information including AoA azimuth (horizontal angle) and/or AoA elevation (vertical angle)) indicating the angle between the reference device 20 and the UE 10 may be obtained. For example, as shown in
The position (xu,yu,zu) of the UE 10 with respect to the position of the reference device 20 may be determined based on the distance information and the direction information. For example, the position of the UE 10 may be determined based on Equation 1 below.
Here, θr2u denotes the horizontal angle between the UE 10 and the reference device 20 with respect to the reference device 20. φr2u denotes the vertical angle between the reference device 20 and the UE 10 with respect to the reference device 20.
Here, dr2u cos(φr2u) denotes the two-dimensional distance between the reference device 20 and the UE 10. This may be obtained by projecting the straight line corresponding to the three-dimensional distance dr2u to the 2D (xy plane) based on θr2u. This is as illustrated in
In an embodiment, the second step (operation) may be performed using a sensor (e.g., a (gravity) acceleration sensor) of the UE 10. For example, the acceleration sensor may be used in the second step to obtain an inclination (e.g., an inclination relative to the ground) of the UE 10 pointing at the target device 30. In the disclosure, the inclination may be represented as φg. The position of the target device 30 with respect to the UE 10 may be identified through the inclination s.
In the third step (operation), the position (xt,yt,zt) of the target device 30 with respect to the position of the reference device 20 may be determined.
In an embodiment, the UE 10 may use the result of the first step and the result of the second step to determine the position of the target device 30 with respect to the position of the reference device 20. For example, the position of the target device 30 may be determined based on Equation 2 below.
Here, du2t sin(φg) denotes the two-dimensional distance between the UE 10 and the target device 30. This may be obtained by projecting the straight line corresponding to the three-dimensional distance du2t between the UE 10 and the target device 30 to the 2D (xy plane) based on the inclination φg. This is as illustrated in
Here, θr2t denotes the horizontal angle between the reference device 20 and the target device 30 with respect to the reference device 20. For example, θr2t may be determined based on Equation 3 below.
Here, θu2r denotes the horizontal angle between the UE 10 and the reference device 20 with respect to the UE 10. In an embodiment, θu2r may be obtained as the above-described UWB ranging result between the UE 10 and the reference device 20.
In the embodiment of
The embodiment of
In the embodiment of
The registration procedure of
Through the registration procedure, the position of the target device 30 may be identified with respect to the position (reference position) of the reference device 20. The identified position of the target device 30 may be stored and used in a subsequent recognition procedure.
In the embodiment of
In an embodiment, the first step (operation) may be performed using UWB ranging between the UE 10 and the reference device 20, at each position. For example, the UE 10 may perform the UWB ranging operation with the reference device 20 at a first position, and may perform the UWB ranging operation with the reference device 20 at a second position. In this case, the used ranging operation corresponds to the same operation as the ranging operation of the first step of
As a result of ranging at each position, as shown in
In an embodiment, the second step (operation) may be performed using a sensor (e.g., a (gravity) acceleration sensor) of the UE 10. For example, the acceleration sensor may be used in the second step to obtain an inclination (e.g., an inclination relative to the ground) of the UE 10 pointing at the target device 30. In the embodiment of
In the third step (operation), the position (
In an embodiment, the UE 10 may obtain the xy coordinates (
In this case, the position (first coordinates) of the target device 30 with respect to the reference, calculated with respect to the first position (xu,yu) projected to the xy plane of the UE 10 may be obtained. Further, the position (second coordinates) of the target device 30 with respect to the reference, calculated with respect to the second position (x′u,y′u) projected to the xy plane of the UE 10 may be obtained. Obtaining each of the positions (coordinates) may follow Equation 2 of
Meanwhile, although the above description assumes that the UE 10 points at the target device from two positions, an embodiment in which the UE 10 points at the target device from three or more positions is also possible as described above. In this case, two or more intersections may be present. Accordingly, it is possible to obtain the xy coordinates (
Next, the z axis
The embodiment of
In the embodiment of
The registration procedure of
Through the registration procedure, the position of the target device 30 may be identified with respect to the position (reference position) of the reference device 20. The identified position of the target device 30 may be stored and used in a subsequent recognition procedure.
In the embodiment of
In an embodiment, the first operation may be performed using UWB ranging between the first UE 10-1 and the reference device 20. For example, the UWB two-way ranging (TWR) scheme described with reference to
As a result of the UWB ranging, distance information (e.g., ToF information) indicating the distance between the reference device 20 and the first UE 10-1 and direction (angle) information (e.g., angle-of-arrival (AoA) information including AoA azimuth (horizontal angle) and/or AoA elevation (vertical angle)) indicating the angle between the reference device 20 and the UE first 10-1 may be obtained. For example, through UWB ranging, the distance dr2u between the reference device 20 and the first UE 10-1 on the 3D plane, the horizontal angle (AoA azimuth θr2u) (angle (1) of
The position (xu,yu,zu) of the first UE 10-1 with respect to the position of the reference device 20 may be determined based on the distance information and the direction information. For example, the position of the first UE 10-1 may be determined based on Equation 1 described above.
In an embodiment, the second operation may be performed using a sensor (e.g., a (gravity) acceleration sensor) of the first UE 10-1. For example, the acceleration sensor may be used in the second step to obtain an inclination (e.g., an inclination relative to the ground) of the first UE 10-1 pointing at the target device 30. In the disclosure, the inclination may be represented as φg. The position of the target device 30 with respect to the first UE 10-1 may be identified through the inclination φg.
In the third operation, the position (xt,yt,zt) of the target device 30 with respect to the position of the reference device 20 may be determined.
In an embodiment, the first UE 10-1 may use the result of the first step and the result of the second step to determine the position of the target device 30 with respect to the position of the reference device 20. For example, the first UE 10-1 may determine the position of the target device 30 based on Equations 2 and 3 described above.
As described above, θr2t in Equation 2 denotes the horizontal angle between the reference device 20 and the target device 30 with respect to the reference device 20. As in Equation 3, θr2t may be determined based on the horizontal angle θu2r (angle (8) of
In an embodiment, θu2r may be obtained directly from the result of UWB ranging between the first UE 10-1 and the reference device 20.
In another embodiment, θu2r may be obtained using data obtained from the result of UWB ranging between the first UE 10-1 and the second UE 10-2, as auxiliary information. Depending on the context, it may be difficult to obtain θu2r directly from the result of UWB ranging between the first UE 10-1 and the reference device 20. In this case, θu2r may be obtained based on, e.g., Equation 4 below, using the result of UWB ranging between the first UE 10-1 and the second UE 10-2.
Each parameter of Equation 4 is described below.
Line segment a: A line segment connecting the position of the reference device 20 and the position of the first UE 10-1
Line segment b: A line segment connecting the position of the first UE 10-1 and the position of the second UE 10-2
Line segment c: A line segment connecting the position of the second UE 10-3 and the position of the reference device 20
Angle (1): An angle between the reference device 20 and the first UE 10-1 with respect to the reference device 20
Angle (2): An angle between the reference device 20 and the second UE 10-2 with respect to the reference device 20
Angle (3): An angle between line segment c and line segment a
Angle (4): An angle between the second UE 10-2 and the reference device 20 with respect to the second UE 10-2
Angle (5): An angle between the second UE 10-2 and the first UE 10-1 with respect to the second UE 10-2
Angle (6): An angle between line segment b and line segment c
Angle (7): An angle between the first UE 10-1 and the second UE 10-2 with respect to the first UE 10-1
Angle (8): An angle between the first UE 10-1 and the reference device 20 with respect to the first UE 10-1
Angle (9): An angle between line segment a and line segment b
Referring to Equation 4, angle (8) θu2r may be obtained based on the difference between angle (7) and angle (9). Further, angle (9) may be obtained based on angle (3) and angle (6). Further, angle (3) may be obtained based on angle (1) and angle (2). Angle (6) may be obtained based on angle (4) and angle (5).
As an embodiment, angle (1) may be obtained based on the result of UWB ranging between the first UE 10-1 and the reference device 20.
As an embodiment, angles (2) and (4) may be obtained based on the result of UWB ranging between the second UE 10-2 and the reference device 20.
As an embodiment, angles (5) and (7) may be obtained based on the result of UWB ranging between the first UE 10-1 and the second UE 10-2.
In summary, in the fourth option of the registration procedure, for positioning of the target device 30, AoA information (angle (1) and angle (8)) between the reference device 20 and the first UE 10-1 is used as an AoA essential element. In this case, angle (1) and angle (8) both may be obtained only with the result of UWB ranging between the first UE 10-1 and the reference device 20 but, according to the context, angle (8) may not be obtained only with the result of UWB ranging between the reference device 20 and the first UE 10-1. In this case, the first UE 10-1 may obtain angle (8) based on, e.g., Equation 4 described above, using AoA information obtained as the result of UWB ranging between the first UE 10-1 and the second UE 10-2, as auxiliary information.
The embodiment of
In the embodiment of
The registration procedure of
Through the registration procedure, the position of the target device 30 may be identified with respect to the position (reference position) of the reference device 20. The identified position of the target device 30 may be stored and used in a subsequent recognition procedure.
In the embodiment of
In an embodiment, the first operation may be performed using the results of UWB ranging between the first UE 10-1 and the reference device 20 and UWB ranging between the second UE 10-2 and the reference device 20. For example, the UWB two-way ranging (TWR) scheme described with reference to
For example, as a result of the UWB ranging between the reference device 20 and the first UE 10-1/second UE 10-2, distance information (e.g., ToF information) indicating the distance between the reference device 20 and the first UE 10-1/second UE 10-2 and direction (angle) information (e.g., angle-of-arrival (AoA) information including AoA azimuth (horizontal angle) and/or AoA elevation (vertical angle)) indicating the angle between the reference device 20 and the first UE 10-1/second UE 10-2 may be obtained. For example, through UWB ranging, each distance (e.g., dr1 and dr2 of
Each position of the first UE 10-1/second UE 10-2 with respect to the position of the reference device 20 may be determined based on the distance information and direction information. For example, the position of the first UE 10-1/second UE 10-2 may be determined based on Equation 1 described above.
In the embodiment of
The second operation is described below with reference to
Each parameter of
dr1: Distance between the reference device 20 and the first UE 10-1 on the xy plane
dr2: Distance between the reference device 20 and the second UE 10-2 on the xy plane
d12: Distance between the first UE 10-1 and the second UE 10-2 on the xy plane
x: Distance between the intersection o and the first UE 10-1 on the xy plane
y: Distance between the intersection o and the second UE 10-2 on the xy plane
Here, the intersection o corresponds to the intersection of the normal to the line segment corresponding to d12 of the target device 30 on the xy plane.
θα: Angle between the line segment corresponding to dt2 and the line segment corresponding to d12 on the xy plane
θβ: Angle between the line segment corresponding to dt1 and the line segment corresponding to d12 on the xy plane
In an embodiment, the second operation may be performed using the results of UWB ranging (first UWB ranging) between the first UE 10-1 and the reference device 20, UWB ranging (second UWB ranging) between the second UE 10-2 and the reference device 20, and/or UWB ranging (third UWB ranging) between the first UE 10-1 and the second UE 10-2.
As an embodiment, information about the distance dr1 between the reference device 20 and the first UE 10-1 may be obtained through the result of the first UWB ranging.
As an embodiment, information about the distance dr2 between the reference device 20 and the second UE 10-2 may be obtained through the result of the first UWB ranging.
As an embodiment, information about the distance d12 between the first UWB device 10-1 and the second UWB device 10-2 and information about the angle between the first UWB device 10-1 and the second UWB device 10-2 may be obtained through the result of third UWB ranging.
As an embodiment, the information about the angle between the first UWB device 10-1 and the second UWB device 10-2 may include information about the angle θ12 between the first UWB device 10-1 and the second UWB device 10-2 with respect to the first UWB device 10-1 and/or information about the angle θ21 between the second UWB device 10-2 and the first UWB device 10-1 with respect to the second UWB device 10-2.
In an embodiment, the first UWB device 10-1 and/or the second UWB device 10-2 may obtain the distance dt1 between the first UWB device 10-1 and the target device 30 and the distance dt2 between the second UWB device 10-2 and the target device 30. For example, the first UWB device 10-1 and/or the second UWB device 10-2 may obtain the distances dt1 and dt2 using Equation 5 below.
As an embodiment, the first UWB device 10-1 and/or the second UWB device 10-2 may obtain the coordinates (xt,yt) of the target device 30 on 2D using the obtained distances dt1 and dt2.
The third operation corresponds to the operation of determining the three-dimensional coordinates of the target device 30.
As an embodiment, the third operation may be performed using a sensor (e.g., a (gravity) acceleration sensor) of each UE 10-1, 10-2. For example, the acceleration sensor may be used in the third operation to obtain an inclination (e.g., an inclination relative to the ground) of each UE 10-1, 10-2 pointing at the target device 30.
As an embodiment, the first UE 10-1 may obtain a first inclination φg for the target device 30 using the acceleration sensor at the position of the first UE 10-1, and the second UE 10-2 may obtain a second inclination φ′g for the target device 30 using the acceleration sensor at the position of the second UE 10-2.
As an embodiment, the first UE 10-1 and/or the second UE 10-2 may obtain the three-dimensional coordinates (Xt,Yt,Zt) from the two-dimensional coordinates (Xt,Yt) of the target device 30 using the first inclination φg and/or the second inclination φ′g. The operation of obtaining the three-dimensional coordinates (Xt,Yt,Zt) from the two-dimensional coordinates (Xt,Yt) using the inclination may be performed according to, e.g., the above-described procedure of
In summary, in the fifth option of the registration procedure, since there is no three-dimensional intersection between the line segments from the respective UEs 10-1, 10-2 to the target device 30, the two-dimensional coordinates of the target device may be first obtained through the two-dimensional intersection, and the two-dimensional coordinates may then be expanded to the three-dimensional coordinates based on the inclination toward the target device 30. In this case, the two-dimensional coordinates of the target device 30 may be obtained using the distance information between each UE 10-1, 10-2 and the target device 30, obtained using the result of UWB ranging between the first UE 10-1 and the second UE 10-2.
The embodiment of
In the embodiment of
The registration procedure of
Through the registration procedure, the position of the target device 30 may be identified with respect to the position (reference position) of the reference device 20. The identified position of the target device 30 may be stored and used in a subsequent recognition procedure.
In the embodiment of
In an embodiment, the first operation may be performed using the results of UWB ranging between the first UE 10-1 and the reference device 20, UWB ranging between the second UE 10-2 and the reference device 20, and UWB ranging between the third UE 10-3 and the reference device 20. For example, the UWB two-way ranging (TWR) scheme described with reference to
For example, as a result of the UWB ranging between the reference device 20 and the first UE 10-1/second UE 10-2/third UE 10-3, distance information (e.g., ToF information) indicating the distance between the reference device 20 and the first UE 10-1/second UE 10-2/third UE 10-3 and direction (angle) information (e.g., angle-of-arrival (AoA) information including AoA azimuth (horizontal angle) and/or AoA elevation (vertical angle)) indicating the angle between the reference device 20 and the first UE 10-1/second UE 10-2/third UE 10-3 may be obtained. For example, through UWB ranging, each distance between the reference device 20 and the first UE 10-1/second UE/third UE on 3D, each horizontal angle (AoA azimuth) between the reference device 20 and the first UE 10-1/second UE 10-2/third UE 10-3 with respect to the reference device 20, and each vertical angle (AoA elevation) between the reference device 20 and the first UE 10-1/second UE 10-2/third UE 10-3 with respect to the reference device 20 may be obtained.
Each position of the first UE 10-1/second UE 10-2/third UE 10-3 with respect to the position of the reference device 20 may be determined based on the distance information and direction information. For example, the position of the first UE 10-1/second UE 10-2/third UE 10-3 may be determined based on Equation 1 described above.
In the embodiment of
The second operation corresponds to the operation of determining the three-dimensional coordinates of the target device.
As an embodiment, the second operation may include obtaining the coordinates (position) of each UE 10-1, 10-2, 10-3 obtained through the first operation and the coordinates (position) of the target device to be obtained, i.e., the line segments passing through the coordinates of the two points.
For example, the line segment (straight line) passing through two points ((xu,yu,zu) and (xv,yv,zv)) may be represented by Equation 6 below.
The first UE 10-1/second UE 10-2/third UE 10-3 may obtain each of the equations for the straight lines for a first line segment (first straight line) passing through the coordinates of the first UE 10-1 and the coordinates of the target device, a second line segment (second straight line) passing through the coordinates of the second UE 10-2 and the coordinates of the target device, and a third line segment (third straight line) passing through the coordinates of the third UE 10-3 and the coordinates of the target device, using Equation 6.
The first UE 10-1, the second UE 10-2, and/or the third UE 10-3 may obtain the coordinates of the inclination of the corresponding straight lines using the obtained straight line equations. The so-obtained coordinates of the intersection of the line segments (straight lines) corresponds to the three-dimensional coordinates of the target device 30.
In summary, in the sixth option of the registration procedure, since there is a three-dimensional intersection of the line segments from the respective UEs 10-1, 10-2, 10-3 to the target device 30, the three-dimensional coordinates of the target device 30 may be directly obtained by calculating the intersection of the line segments passing through the coordinates of each UE 10-1, 10-2, 10-3 and the coordinates of the target device 30.
The embodiment of
In an embodiment, the distance h may be calculated based on Equation 7 below to obtain the distance between straight lines passing through two points.
Examples of parameters used in Equation 7 and the distance h are shown in
Here, U denotes the position of the UE 10. The coordinates of U may be denoted as U=(xu,yu,zu). In an embodiment, U may be obtained through a UWB ranging procedure between the UE 10 and the reference device 20 described above in connection with
T denotes the position of the target device 30. T may be obtained through the registration procedure described above in connection with
V may be the position of any point positioned in the direction (or straight line) in which the UE 10 points to recognize the target device 30. For example, as shown in
In the embodiment of
θr2t denotes the horizontal angle between the target device 30 and the reference device 20 with respect to the reference device 20.
θu2r denotes the horizontal angle between the UE 10 and the reference device 20 with respect to the UE 10.
θu2t denotes the horizontal angle between the UE 10 and the target device 30 with respect to the UE 10.
The UE 10 may recognize the target device 30 based on the obtained (or calculated) distance h. In an embodiment, the UE 10 may determine whether the distance h is smaller than a preset threshold. When the distance h is smaller than the preset threshold, the UE 10 may recognize that the target device 30 (is positioned in the pointing direction of the UE 10 and thus) is controlled. Or, when the distance h is larger than the preset threshold, the UE 10 may recognize that the target device 30 (is not positioned in the pointing direction of the UE 10 and thus) is not controlled.
When the target device 30 to be controlled is recognized, the UE 10 may provide (e.g., display) control information (e.g., a control UX) for controlling the target device 30. In this case, the user may control the target device 30 using the control information.
Meanwhile, as shown in
In the embodiment of
Referring to
The first UWB device may perform a recognition step for recognizing a registered non-UWB device (S1120). In an embodiment, the recognition step may include identifying whether the first UWB device points at the registered non-UWB device based on the pointing direction of the first UWB device and the position of the non-UWB device identified in the registration step. For the operations of the recognition step, refer to the description made above in connection with
The registration step of
In the embodiment of
Referring to
The first UWB device may obtain inclination information about the first UWB device that points at the non-UWB device within a preset distance (1220). Accordingly, the position of the non-UWB device with respect to the position of the first UWB device may be identified.
The first UWB device may identify the position of the non-UWB device with respect to the position of the second UWB device based on the AoA azimuth information, the preset distance, and the inclination information (1230). The identification of the position of the non-UWB device with respect to the position of the second UWB device may be based on Equations 2 and 3.
The registration step of
In the embodiment of
Referring to
The first UWB device may obtain first inclination information about the first UWB device pointing at the non-UWB device from the first position and second inclination information about the second UWB device pointing at the non-UWB device from the second position (1320). Thus, the position of the non-UWB device with respect to each of the first position and second position of the first UWB device may be identified.
The first UWB device may identify the position of the non-UWB device with respect to the position of the second UWB device based on the first AoA azimuth information, the second AoA azimuth information, the first inclination information, and the second inclination information (1330). In an embodiment, the first UWB device may identify the position of the non-UWB device with respect to the position of the second UWB device by obtaining an intersection of a first straight line pointing at the non-UWB device from the first position and a straight line pointing at the non-UWB device from the second position, based on the first AoA azimuth information, the second AoA azimuth information, the first inclination information, and the second inclination information. The identification of the position of the non-UWB device with respect to the position of the second UWB device may be based on Equations 2 and 3.
In the embodiment of
Referring to
The transceiver 1410 may transmit and receive signals to/from other network entities. The transceiver 1410 may transmit/receive data for UWB ranging using, e.g., UWB communication.
The controller 1420 may control the overall operation of the first electronic device according to an embodiment. For example, the controller 1420 may control inter-block signal flow to perform the operations according to the above-described flowchart. Specifically, the controller 1420 may control the operations of the first electronic device described above with reference to
The storage unit 1430 may store at least one of information transmitted/received via the transceiver 1410 and information generated via the controller 1420. For example, the storage unit 1430 may store information and data required to register and recognize a non-UWB device using UWB described with reference to
In the embodiment of
Referring to
The transceiver 1510 may transmit and receive a signal to and from another electronic device. The transceiver 1510 may transmit and receive data for UWB ranging to/from the second electronic device through, e.g., UWB communication.
The controller 1520 may control the overall operation of the first electronic device according to an embodiment. For example, the controller 1520 may control inter-block signal flow to perform the operations according to the above-described flowchart. Specifically, the controller 1520 may control the operations of the first electronic device described above with reference to
The storage unit 1530 may store at least one of information transmitted/received via the transceiver 1510 and information generated via the controller 1520. For example, the storage unit 1530 may store information and data required to register and recognize a non-UWB device using UWB described with reference to
The user interface 1540 includes various types of input/output means provided in the first electronic device. In other words, the user interface may receive the user's input using various input means, and the controller 1520 may control the first electronic device based on the received user input. Further, the user interface 1540 may perform output based on a command of the controller 1520 using various output means.
The display 1550 outputs an image on the display screen. The display 1550 may output various display objects, such as a user interface, based on a control command of the controller or content executed by the controller 1520. For example, the display 1550 may display a control UX for controlling the above-described recognized target device.
In the embodiment of
Referring to
The transceiver 1610 may transmit and receive a signal to and from another electronic device. The transceiver 1610 may receive a control signal for controlling the second electronic device from the first electronic device, for example.
The controller 1620 may control the overall operation of the second electronic device according to an embodiment. For example, the controller 1620 may control inter-block signal flow to perform the operations according to the above-described flowchart. Specifically, the controller 1620 may control the operations of the second electronic device described above with reference to
The storage unit 1630 may store at least one of information transmitted/received via the transceiver 1610 and information generated via the controller 1620. For example, the storage unit 1630 may store information and data required to register and recognize a non-UWB device using UWB described with reference to
The user interface 1640 includes various types of input/output means provided in the second electronic device. In other words, the user interface may receive the user's input using various input means, and the controller 1620 may control the first electronic device based on the received user input. Further, the user interface 1640 may perform output based on a command of the controller 1620 using various output means.
The display 1650 outputs an image on the display screen. The display 1650 may output various display objects, such as a user interface, based on a control command of the controller or content executed by the controller 1620.
In the above-described specific embodiments, the components included in the disclosure are represented in singular or plural forms depending on specific embodiments proposed. However, the singular or plural forms are selected to be adequate for contexts suggested for ease of description, and the disclosure is not limited to singular or plural components. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise.
Although specific embodiments of the present invention have been described above, various changes may be made thereto without departing from the scope of the present invention. Thus, the scope of the disclosure should not be limited to the above-described embodiments, and should rather be defined by the following claims and equivalents thereof.
Number | Date | Country | Kind |
---|---|---|---|
10-2021-0055998 | Apr 2021 | KR | national |
10-2021-0116464 | Sep 2021 | KR | national |
This application is a U.S. National Stage application under 35 U.S.C. § 371 of an International application number PCT/KR2022/006190, filed on Apr. 29, 2022, which is based on and claims priority of a Korean patent application number 10-2021-0055998, filed on Apr. 29, 2021, in the Korean Intellectual Property Office, and of a Korean patent application number 10-2021-0116464, filed on Sep. 1, 2021, in the Korean Intellectual Property Office, the disclosure of which is incorporated by reference herein in its entirety.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/KR2022/006190 | 4/29/2022 | WO |