Method and apparatus for providing service using UWB communication

Abstract

A method for providing a service through ultra wide band (UWB) communication is provided. A method by a UWB device includes: receiving a first UWB message initiating a ranging procedure from an initiator anchor; receiving, from a plurality of responder anchors, a plurality of second UWB messages transmitted in response to the first UWB message; receiving, from the initiator anchor, a third UWB message transmitted in response to the second UWB message; receiving a plurality of fourth UWB messages transmitted in response to the third UWB message from the plurality of responder anchors; and performing downlink time difference of arrival (DL-TDoA)-based positioning on the basis of the first UWB message, the second UWB message, the third UWB message, and the fourth UWB message.

Description

Technical Field

[0001] The present disclosure relates to ultra-wideband (UWB) communication. More particularly, the present disclosure relates to a method and apparatus for providing a service using UWB communication. Background Art

[0002] The Internet is evolving from a human-centric connected network where humans create and consume information to an Internet of Things (IoT) network where information is communicated and processed between things or other distributed components. Another emerging technology is the Internet of Everything (IoE), which is a combination of big data processing technology and IoT technology through, for example, connections to cloud servers. Implementing IoT requires technology elements such as sensing technology, wired / wireless communication and network infrastructure, service interfaces, and security technology. Recent ongoing research on thing-to-thing connectivity is related to technologies for sensor networking, machine-to-machine (M2M), or machine type communications (MTC).

[0003] In the IoT environment, intelligent Internet technology (IT) services can be provided that collect and analyze data generated by things connected to each other to create new value for human life. Through the transformation or integration of traditional information technology (IT) technologies and various industries, IoT can have various applications such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare or smart home appliance industries, or state-of-the-art medical services.

[0004] As wireless communication systems continue to develop to provide various services, methods for efficiently providing these services are needed. For example, ranging technology using ultra-wideband (UWB) can be used to measure the distance between electronic devices.

[0005] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with respect to the present disclosure. Summary of the invention

[0006]

Technical issues

[0007] An aspect of the present disclosure is to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below.Accordingly, an aspect of the present disclosure is to provide a method and apparatus for providing a service (eg, a payment service) through UWB communication.

[0008] Additional aspects will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the presented embodiments.

[0009]

Technical solution

[0010] According to aspects of the present disclosure, a method performed by a UWB device is provided. The method includes: receiving a first UWB message initiating a ranging process from an initiator anchor; receiving a plurality of second UWB messages sent in response to the first UWB message from a plurality of responder anchors; receiving a third UWB message sent in response to the second UWB message from the initiator anchor; receiving a plurality of fourth UWB messages sent in response to the third UWB message from a plurality of responder anchors; and performing downlink time difference of arrival (DL-TDoA) based positioning based on the first UWB message, the second UWB message, the third UWB message, and the fourth UWB message.

[0011] According to another aspect of the present disclosure, a UWB device is provided. The UWB device includes a transceiver and a controller, the controller being connected to the transceiver and configured to: receive a first UWB message initiating a ranging process from an initiator anchor; receive a plurality of second UWB messages sent in response to the first UWB message from a plurality of responder anchors; receive a third UWB message sent in response to the second UWB message from the initiator anchor; receive a plurality of fourth UWB messages sent in response to the third UWB message from a plurality of responder anchors; and perform DL-TDoA-based positioning based on the first UWB message, the second UWB message, the third UWB message, and the fourth UWB message.

[0012] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure.

[0013] [Beneficial effects of the invention]

[0014] An aspect of the present disclosure is to provide an efficient method and apparatus for providing a service (eg, a payment service) through UWB communication. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings, in which: Figure 1 An example architecture of a UWB device according to an embodiment of the present disclosure is shown; Figure 2 An example configuration of a framework of a UWB device according to an embodiment of the present disclosure is shown; Figure 3 The structure of a UWB medium access control (MAC) frame according to an embodiment of the present disclosure is shown; Figure 4 shows the structure of a UWB physical layer (PHY) packet according to an embodiment of the present disclosure; Figure 5aAn example of a ranging block structure according to an embodiment of the present disclosure is shown; Figure 5b The structure of a ranging round according to an embodiment of the present disclosure is shown; Figure 6 Various examples of UWB ranging methods according to embodiments of the present disclosure are shown; Figure 7a A method for a UWB device to perform UWB ranging in a DL-TDoA scheme according to an embodiment of the present disclosure is shown; Figure 7b An example of a ranging block structure of a downlink TDoA scheme according to an embodiment of the present disclosure is shown; Figure 8 A payment processing method using UWB according to an embodiment of the present disclosure is shown; Fig. 9 A method for performing DL-TDoA ranging and contention-based ranging by a UWB device according to an embodiment of the present disclosure is shown; Fig.10 A method for performing DL-TDoA ranging and contention-based ranging by a UWB device according to an embodiment of the present disclosure is shown; Fig.11 The structure of a UWB message according to an embodiment of the present disclosure is shown; Fig.12a shows the payload structure of a UWB message according to an embodiment of the present disclosure; Figure 12b shows the payload structure of a UWB message according to an embodiment of the present disclosure; Fig.13a and Fig.13b An example of a payload field related to a One-Way Ranging (OWR) message type included in a UWB message according to various embodiments of the present disclosure is shown; Fig.14 shows a UWB Command Interface (UCI) command for establishing a session for an initiator anchor according to an embodiment of the present disclosure; Fig.15 A method for an anchor to transmit response time information during ranging according to an embodiment of the present disclosure is shown; Fig.16a A case where an initiator anchor sends a first UWB message and a responder anchor sends a second UWB message in response to the first UWB message according to an embodiment of the present disclosure is shown; Fig.16b is a diagram showing an equation for estimating a response time of another responder anchor previously responded to a specific responder anchor at a user equipment (UE) side according to an embodiment of the present disclosure; Fig.16cThe present invention is used for UE to utilize Fig.16b The estimated answer time between responder anchors provides an additional view of the TDoA equation; Fig.17 A payment processing method using UWB according to an embodiment of the present disclosure is shown; Fig.18 shows the structure of a first UWB device according to an embodiment of the present disclosure; and Fig.19 The structure of a second UWB device according to an embodiment of the present disclosure is shown.

[0016] Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures. DETAILED DESCRIPTION

[0017] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in understanding, but these are to be considered exemplary only. Therefore, one of ordinary skill in the art will recognize that various changes and modifications may be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and structures may be omitted for clarity and brevity.

[0018] The terms and words used in the following specification and claims are not limited to the bibliographic meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, it should be clear to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustrative purposes only and not for limiting the present disclosure as defined by the appended claims and their equivalents.

[0019] It is to be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0020] When describing the embodiments, descriptions of technologies that are well 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.

[0021] For the same reason, some elements may be shown exaggeratedly or schematically. 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.

[0022] The advantages and features of the present disclosure and the methods for realizing the advantages and features of the present disclosure can be understood by the following embodiments described in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed herein, and various changes can be made to these embodiments. The embodiments disclosed herein are only used to inform the categories of the present disclosure to those of ordinary skill in the art. The present disclosure is defined only by the attached claims. Throughout the specification, the same reference numerals represent the same elements.

[0023] It should be understood that the combination of the blocks and flow charts in each flow chart can be executed by computer program instructions. Since the computer program instructions can be equipped 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 a device for performing the functions described in the blocks in conjunction with each flow chart. Since the computer program instructions can be stored in a computer-usable or computer-readable memory, the computer-usable or computer-readable memory can be oriented to the computer or other programmable data processing device to implement the function in a specific manner, so the instructions stored in the computer-usable or computer-readable memory can produce a product including an instruction device, and the instruction device is used to perform the functions described in conjunction with the blocks in each flow chart. Since the computer program instructions can be equipped in a computer or other programmable data processing device, the instructions for generating the process run by the computer are executed on the computer or other programmable data processing device as a series of operating steps, and the operating computer or other programmable data processing device can provide steps for running the functions described in conjunction with the blocks in each flow chart.

[0024] In addition, each frame can represent a module, field or a part of code including one or more executable instructions for running a specific logic function. In addition, it should also be noted that in some alternative implementations, the functions mentioned in the frame can occur in different orders. For example, two frames shown in succession can be performed substantially simultaneously or in reverse order according to the corresponding functions.

[0025] As used herein, the term "unit" refers to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). The unit plays a certain role. However, the "unit" is not limited to software or hardware. The "unit" can be configured in a storage medium that can be addressed or configured to run one or more processors. Therefore, as an example, the "unit" includes the following elements, such as software elements, object-oriented software elements, class elements and task elements, processes, functions, attributes, procedures, subroutines, segmentation of program code, drivers, firmware, microcode, circuits, data, databases, data architectures, tables, arrays and parameters. The functions provided in the components and "units" can be combined into a smaller number of components and "units", or can be further separated into additional components and "units". In addition, the components and "units" can be implemented as one or more CPUs in a running device or a secure multimedia card. According to an embodiment of the present disclosure, the "... unit" can include one or more processors.

[0026] As used herein, the term "terminal" or "device" may also be referred to as a mobile station (MS), a user equipment (UE), a user terminal (UT), a terminal, a wireless terminal, an access terminal (AT), a user unit, a subscriber station (SS), a wireless device, a wireless communication device, a wireless transmission / reception unit (WTRU), a mobile node or a mobile phone, or may be referred to by other terms. Various embodiments of the terminal may include a cellular phone, a smart phone with wireless communication capabilities, a personal digital assistant (PDA) with wireless communication capabilities, a wireless modem, a portable computer with wireless communication capabilities, a recording / recording / shooting / photography device such as a digital camera with wireless communication capabilities, a game player with wireless communication capabilities, a music storage and playback home appliance with wireless communication capabilities, a networked home appliance capable of wireless Internet access and browsing, or a portable unit or terminal comprising a combination of these capabilities. In addition, the terminal may include a machine-to-machine (M2M) terminal and a machine type communication (MTC) terminal / device, but is not limited thereto. In the present disclosure, a terminal may be referred to as an electronic device or simply as a device.

[0027] Hereinafter, the working principle of the present disclosure will be described with reference to the accompanying drawings. When it is determined to make the subject matter of the present disclosure unnecessarily unclear, a detailed description of a well-known function or configuration may be skipped when describing the embodiments of the present disclosure. The terms as used herein are defined in consideration of 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, these terms should be defined based on the entire disclosure.

[0028] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In addition, although a communication system using UWB is described in conjunction with embodiments 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, communication systems using Bluetooth or ZigBee may be included. In addition, at the discretion 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 these modifications may be applied to other communication systems.

[0029] When it is determined that the subject matter of the present disclosure is unclear, the detailed description of the well-known technology or function can be skipped. The terms used in this article are defined in consideration of the functions 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 entire disclosure.

[0030] 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 recognition distance. In this case, WLAN is a technology based on IEEE 802.11, which can access the backbone network within a radius of about 100m. WPAN is a technology based on IEEE 802.15, which includes Bluetooth, ZigBee and ultra-wideband (UWB). A wireless network that implements this wireless network technology may include multiple electronic devices.

[0031] 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 refer to 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).

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

[0033] An "application specific file (ADF)" may be a data structure, such as within an application data structure, that may host application or application specific data.

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

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

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

[0037] A "controller" may be a ranging device that uses ranging parameters in an RCM (or control message) received from a controller. A controller may use the same ranging features as those configured via a control message from the controller.

[0038] Unlike "static STS", "dynamic scrambled timestamp 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 for generating STS may be managed by the security component.

[0039] An "applet" may be, for example, an applet running on a secure component including UWB parameters and service data. The applet may be a FiRa applet.

[0040] 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) or a FiRa device defined in IEEE802.15.4z. The ranging device may be referred to as a UWB device.

[0041] A "UWB-enabled application" may be an application for a UWB service. For example, a UWB-enabled application may be an application that uses a framework application programming interface (API) to configure an out-of-band (OOB) connector, security services, and / or UWB services for a UWB session. A "UWB-enabled application" may be abbreviated as an application or a UWB application. A UWB-enabled application may be a FiRa-enabled application.

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

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

[0044] A "profile" may be a previously defined set of UWB and OOB configuration parameters. A profile may be a FiRa profile.

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

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

[0047] A "smart ranging device" may be a ranging device that may implement an optional framework API. A smart ranging device may be a FiRa smart device.

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

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

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

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

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

[0053] 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.).

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

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

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

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

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

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

[0060] 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).

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

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

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

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

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

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

[0067] A "UWB session" may be a period from when a controller and a controlled person start communicating through UWB until the communication stops. A UWB session may include ranging, data transfer, or both ranging and data transfer.

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

[0069] The "UWB session key" may be a key for protecting a UWB session. The UWB session key may be used to generate an STS. The UWB session key may be a UWB ranging session key (URSK) and may be abbreviated as a session key.

[0070] A "UWB subsystem (UWBS)" may be 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.

[0071] A "UWB message" may be a message including a payload Information Element (IE) sent by a UWB device (eg, ERDEV).

[0072] A "payload IE" may be an IE included in a MAC payload of a UWB MAC frame. A MAC payload may include one or more payload IEs.

[0073] "Scheduled-based ranging" may be used for ranging rounds scheduled by the controller so that the controlled party sends ranging frames (RFRAME) and / or measurement reports in different ranging time slots. Scheduling-based ranging may be referred to as time-scheduled ranging. A scheduling mode in which scheduling-based ranging is used may be referred to as time-scheduled mode.

[0074] "Content-based ranging" can be used when the controller does not know the MAC address of the controlled device participating in the UWB session (ranging session). In contention-based ranging, the controller can be the initiator and can perform ranging with other unknown UWB devices. The scheduling mode in which contention-based ranging is used can be called contention-based mode.

[0075] Contention-based ranging may be used for ranging rounds in which the controller determines the size of the contention access period and indicates the contention access period (CAP) size through a ranging control message. The CAP may be referred to as a contention window or contention window period.

[0076] In contention-based mode, the UWB device may operate as a controller and an initiator, and in this case, the ranging control phase (RCP) and the ranging initiation phase (RIP) may be combined into one phase (e.g., RIP). In the ranging phase (RP), the allocation of the CAP size may determine the CAP period for responders participating in the corresponding ranging round in units of ranging slots. Each responder may randomly determine a slot in the CAP to send a ranging response message (RRM). The messages used in contention-based ranging may use SP1 as the RFRAME configuration.

[0077] "Hybrid ranging" can be used when there are known controlees and unknown controlees. As described above, a known controlee may be a controlee whose MAC address is known by the controller, and an unknown controlee may be a controlee 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 in which hybrid ranging is used may be referred to as a hybrid-based mode.

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

[0079] In the hybrid-based mode, the ranging round 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). 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).

[0080] "Downlink Time Difference of Arrival (DL-TDoA, DT)" can be a positioning method for one or more tag devices (DT-Tag) to estimate their positions based on DL-TDoA messages (DTM) received from at least one anchor device (DT-anchor). In DL-TDoA, the anchor device sends or broadcasts the DTM, and the tag device passively receives the DTM, thereby preventing the location of the tag device from being exposed.

[0081] In DL-TDoA, the anchor device can accurately measure its own DTM transmission time and the reception time of the received DTM. The anchor device can include the transmission time in the DTM it transmits or broadcasts. The tag device can measure the reception time of all received DTMs and estimate its position by using the reception timestamp and the obtained coordinates of the anchor device. DL-TDoA can be classified as a one-way measurement type like uplink TDoA. DL-TDoA can be called DL-TDoA positioning.

[0082] An "anchor device" may be a UWB device deployed at a specific location to provide positioning services. For example, an anchor device may be a UWB device installed by a service provider on a wall, ceiling, frame, or the like in a room to provide indoor positioning services. In DL-TDoA, an anchor device may be a device that sends a DTM, and a tag device may use the DTM to calculate a location based on TDoA positioning (DL-TDoA positioning). In DL-TDoA, anchor devices may be divided into initiator anchors and responder anchors according to the order and role of sending messages, and participate in ranging rounds. An anchor device may be referred to as a UWB anchor or a UWB anchor device. An anchor device of a DL-TDoA may be referred to as a DL-TDoA anchor or a DT-anchor.

[0083] The "Initiator Anchor" may notify the initiation of a TDoA ranging round (DL-TDoA ranging round). In DL-TDoA, the Initiator Anchor may initiate a DL-TDoA ranging round by sending an Initiation message, and may schedule the transmission time of (one or more) Responder Anchors. For example, the Initiator Anchor may schedule the ranging slots for (one or more) Responder Anchors running in the same ranging round to send a Response Message (Response DTM). The Initiation Message may be referred to as an Initiator DTM, a Polling Message, a Polling DTM, or a First DTM. The Initiator Anchor may be referred to as an Initiator UWB Anchor, an Initiator Anchor Device, or an Initiator DT-Anchor.

[0084] The initiator anchor may additionally transmit an end message (final DTM message) after receiving a response from (one or more) responder anchors. The initiator anchor may also send a final DTM after all responder anchors in the same cluster send response messages (response DTMs) in a DL-TDoA ranging round. The end message may be referred to as a final DTM or a third DTM.

[0085] There may be at least one reference initiator anchor in a DL-TDoA network. The reference initiator anchor serves as an initiator anchor as a global time reference for inter-cluster synchronization and may configure a common ranging block structure for DL-TDoA network operation. The reference initiator anchor may be referred to as a primary anchor or a global anchor.

[0086] A responder anchor may be a UWB anchor that responds to an initiation message of an initiator anchor. A responder anchor may respond to an initiator anchor with a response message. A response message may be referred to as a responder DTM, a response DTM, or a second DTM. A "responder anchor" may also be referred to as a responder UWB anchor, a responder UWB anchor device, a responder anchor device, etc.

[0087] A "tag device" may estimate its location (e.g., geographic coordinates) based on the DTM received from the anchor device in DL-TDoA by using TDoA measurements. The tag device may know the location of the anchor device in advance. The tag device may be referred to as a UWB tag, a user equipment (UE), or a UWB tag device, and a DL-TDoA tag device may be referred to as a DL-TDoA tag or a DT-tag.

[0088] The tag device can receive the message sent by the anchor device and measure the reception time of the message. The tag device can obtain the geographical coordinates of the anchor device through in-band or out-of-band methods. When the location update rate is lower than the rate supported by the network, the tag device can skip the ranging block.

[0089] A "cluster" may refer to a group of anchor devices covering a specific area. In DL-TDoA, a cluster may mean a group of anchor devices that exchange DTMs to provide positioning services to at least one tag device. A cluster may consist of an initiator anchor and at least one responder anchor.

[0090] An anchor device may operate in one or more clusters. In this case, an anchor device acting as an initiator anchor in some clusters may act as a responder anchor in other clusters. A cluster area may be a space formed by the anchor devices constituting the cluster. In order to support positioning services for a wide area, multiple clusters may be configured to provide positioning services to UEs. A cluster may be referred to as a cell.

[0091] When it is determined that it would make the subject matter of the present disclosure unnecessarily unclear, the detailed description of related well-known functions or features may be skipped in describing the present disclosure.

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

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

[0094] 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 enhanced ranging device (ERDEV) defined in IEEE 802.15.4z or a FiRa device.

[0095] exist Figure 1 In the implementation manner, the UWB device 100 may interact with other UWB devices via a UWB session.

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

[0097] The UWB device 100 may implement a second interface (Interface #2) as an interface between the UWB framework 120 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.

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

[0099] The UWB enabled application 110 may trigger the establishment of a UWB session by the UWBS 130 via the first interface. The UWB enabled application 110 may use one of the previously defined profiles. The UWB enabled application 110 may use the first interface to handle related events, such as service discovery, ranging notifications, and / or error conditions.

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

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

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

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

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

[0105] refer to 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 .

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

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

[0108] The security service 223 may function to interface with a security component 240 such as a SE or TEE.

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

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

[0111] exist Figure 3 In an embodiment, 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 related data (eg, UWB messages, ranging messages, control information, service data, application data, etc.).

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

[0113] (1) MAC frame header

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

[0115] In an embodiment, the frame control field may include a frame type field, a security enabled field, a frame pending field, an acknowledgement request (AR) field, a PAN ID compression field (PAN ID present field), a sequence number suppression field, an IE present field, a destination address mode field, a frame version field, and / or a source address mode field. Depending on the embodiment, some of the above fields may not be included in the frame control field. One or more additional fields may be further included in the frame control field.

[0116] Each field is described below.

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

[0118] The security enable field may indicate whether a secondary security frame header field exists. The secondary security frame header field may include information required for security processing.

[0119] 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 are pending frames for the recipient.

[0120] The Acknowledgement Request (AR) field may indicate whether an acknowledgement of frame reception is required from the receiver.

[0121] The PAN ID Compression field (PAN ID Existence field) may indicate whether the PAN ID field exists.

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

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

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

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

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

[0127] (2) MAC payload

[0128] The MAC payload may include at least one Payload IE field. In an embodiment, the Payload IE field may include a Vendor Specific Nested IE.

[0129] (3) MAC frame tail

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

[0131] Figure 4 The structure of a UWB PHY packet according to an embodiment of the present disclosure is shown.

[0132] Figure 4 Part (a) shows an example architecture of a UWB PHY packet to which the STS packet configuration is not applied, while Figure 4 Part (b) of illustrative examples shows an example architecture of a UWB PHY packet to which an STS packet configuration is applied. The UWB PHY packet may be referred to as a PHY packet, a PHY PDU physical protocol data unit (PPDU), or a frame.

[0133] refer to Figure 4 In part (a), the PPDU may include a synchronization frame header (SHR), a PHY frame header (PHR), and a PHY payload (PSDU). The PSDU may include a MAC frame. Figure 2 , a MAC frame may include a MAC frame header (MHR), a MAC payload, and / or a MAC frame tail (MFR). The synchronization frame header portion may be referred to as a preamble, and the portion including the PHY frame header and the PHY payload may be referred to as a data portion.

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

[0135] The SYNC field may be a field including a plurality of preamble symbols for synchronization between transmitting / receiving devices. The preamble symbol may be set by one of the previously defined preambles.

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

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

[0138] 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 timestamp. The STS may be included in the STS field of the UWB PHY packet and used for secure ranging.

[0139] refer to Figure 4 (b), in the case of STS packet (SP) setting 0 (SP0), the STS field is not included in the PPDU (SP0 packet). In the case of SP setting 1 (SP1), the STS field is immediately after the frame start delimiter (SFD) field and before the PHR field (SP1 packet). In the case of SP setting 2 (SP2), the STS field is located after the PHY payload (SP2 packet). In the case of SP setting 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 the PHY payload.

[0140] refer to Figure 4 In part (b), each UWB PHY packet may include a RMARKER for defining a reference time. The RMARKER may be used to obtain a transmission time, a reception time and / or a time range of a ranging message (frame) during a UWB ranging process.

[0141] Figure 5a An example of a ranging block structure according to an embodiment of the present disclosure is shown. Figure 5b The structure of a ranging round according to an embodiment of the present disclosure is shown.

[0142] refer to Figure 5a , a ranging block may include at least one ranging round. Each ranging round may include at least one ranging slot. For example, as shown in the figure, a ranging block includes N ranging rounds (e.g., ranging round index 0 to ranging round index N-1), and ranging round #0 includes M ranging slots (e.g., ranging slot 0 to ranging slot M).

[0143] A ranging block refers to a time period used for ranging. A ranging round may be a duration period sufficient to complete a whole ranging measurement cycle (ranging cycle) involving a group of ranging devices participating in a ranging exchange. A ranging slot may be a period sufficient to send at least one ranging frame (RFRAME) (e.g., ranging initiation / response / final message, etc.).

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

[0145] A ranging block may be abbreviated as a block, a ranging round may be abbreviated as a round, and a ranging slot may be abbreviated as a slot.

[0146] refer to Figure 5b , a ranging round may include a ranging control phase (RCP), a ranging phase (RP) and / or a measurement report phase (MRP). For example, a ranging round may include one time slot for RCP, at least one time slot for RP and / or at least one time slot for MRP.

[0147] According to an embodiment, some of the above phases may not be included in the ranging round, or additional phases may be further included in the ranging round. For example, RCP may not be included in the ranging round. In this case, the ranging control message (RCM) may be combined with the ranging initiation message (RIM). For example, the ranging control update phase (RCUP) and / or the ranging interval update phase (RIUP) may be further included in the ranging round.

[0148] RCP may be a phase in which the controller sends RCM. RCM may be a message sent by the controller to set ranging parameters. In an embodiment, RCM may be sent in the first time slot (time slot #0) of the ranging round. RCM may be abbreviated as control message (CM).

[0149] The RP may include a ranging initiation phase (RIP), a ranging response phase (RRP), and / or a ranging final phase (RFP).

[0150] RIP may be the stage where initiator(s) send(s) RIM(s) to responder(s).

[0151] RRP may be the stage where the responder(s) send their ranging response message(s) (RRM) to the initiator(s).

[0152] RFP may be the phase where the initiator sends (one or more) ranging final messages (RFMs) to (one or more) responders. The ranging final phase can only be used for DS-TWR.

[0153] MRP may be a stage in which the participating ranging devices exchange service information related to ranging measurements. In MRP, a measurement report message (MRM), a ranging result report message (RRRM) and / or a control update message (CUM) may be sent. MRM may be a message sent by a UWB device to exchange measurement information. RRRM may be a message sent by a UWB device to report ranging results. CUM may be a message sent by a controller to update control information. CUM may be referred to as a ranging control update message (RCUM).

[0154] RCUP may be a phase in which the controller sends a ranging control update message (RCUM). The ranging control update phase may be included in the last time slot of a set of ranging rounds specified by an RCM. RCUM may be a message sent by the controller to update the ranging parameters for the next ranging round. RCM may be sent in the last time slot of (one or more) ranging rounds specified by the RCM. RCUM may include some or all information elements (IEs) used by the RCM to update parameter values.

[0155] The ranging interval update phase (RIUP) may be a phase in which the controller sends a ranging interval update message (RIUM). The RIUM may be a message sent by the controller to help synchronize the devices involved in ranging or to update the interval between ranging blocks. The RIUM includes the scheduled time of the first RIUM. The RIUM may include the scheduled time of the next RIUM before the start of the next ranging block.

[0156] If desired, multiple predetermined UWB messages may be combined into one message. For example, an RCM may be combined with a RIM and transmitted in a RIP. For example, in the case of non-delayed DS-TWR ranging, an RFM may be combined with an MRM and sent in an RFP.

[0157] Figure 6 Various examples of UWB ranging methods according to embodiments of the present disclosure are shown.

[0158] Figure 6 Part (a) shows an example of a two-way ranging (TWR) scheme, Figure 6 Part (b) shows an example of an uplink TDoA (UL-TDoA) scheme as an OWR type, and Figure 6 Part (c) of FIG. 4 shows an example of a downlink TDoA (DL-TDoA) scheme as an OWR type.

[0159] refer to Figure 6In part (a), the user's UWB device 620a may perform ranging with at least one UWB anchor 610a through ranging exchanges using a plurality of ranging messages. Through the ranging exchanges, a time of flight (ToF) may be calculated, and the distance between the two devices may be estimated.

[0160] The UWB device 620a may perform single-sided two-way ranging (SS-TWR) or dual-sided two-way ranging (DS-TWR) with the UWB anchor 610a. When performing TWR, the UWB device 620a may function as an initiator or a responder.

[0161] In an embodiment, TWR may be performed according to a contention-based mode and / or a scheduling-based mode.

[0162] refer to Figure 6 In part (b), the user's UWB device (UWB tag) 620a may transmit (broadcast) a ranging message to at least one UWB anchor 610b, and the at least one UWB anchor 610b may obtain a TDoA based on the received ranging message and estimate the position of the UWB device 620b based on the TDoA. Figure 6 The TDoA scheme of the embodiment of part (b) may be referred to as an uplink TDoA (UL-TDoA) scheme.

[0163] refer to Figure 6 In part (c), the user's UWB device (UWB tag or DT-tag) 620c can estimate its position by receiving ranging messages sent / received by at least one UWB anchor 610c. Figure 7a and Figure 7b An example of such a DL-TDoA scheme is described below.

[0164] Figure 7a A method for a UWB device to perform UWB ranging in a DL-TDoA scheme according to an embodiment of the present disclosure is shown.

[0165] Figure 7a The embodiment assumes that one initiator anchor (initiator DT-anchor) 710 and n responder anchors 730a...730n operate as UWB anchors (DT-anchors). However, the embodiment is not limited thereto, and the number of initiator anchors and responder anchors may be changed according to the embodiment.

[0166] In operation S702, the initiator anchor 710 may initiate a DL-TDoA round by sending or broadcasting a polling DTM received by responder anchors in the cluster. The polling DTM may include scheduling information for each responder anchor to send a response DTM in an allocated ranging slot.

[0167] In an embodiment, all responder anchors 730a, ..., 730n may refer to the scheduling information in the polling DTM to know whether to send a response DTM and a time slot (time slot index) for sending the response DTM.

[0168] In operations S704a, ..., S704n, all responder anchors 730a, ..., 730n receiving the polling DTM may respond to the initiator anchor 710 using the response DTM in the ranging slot allocated by the polling DTM. For example, each responder anchor 730a, ..., 730n may send or broadcast the response DTM in the ranging slot allocated by the polling DTM.

[0169] In operation S706, the initiator anchor 710 receiving the response DTM may additionally transmit the final DTM to the responder anchors 730a, ..., 730n. For example, the initiator anchor 710 may transmit or broadcast the final DTM after receiving the response DTM from the responder anchors 730a, ..., 730n.

[0170] In operation S708, the tag device (DT-Tag) 720 may receive (or listen to) the polling DTM, the response DTM, and the final DTM, and calculate the TDoA value through the information included in the message and the reception timestamp. The tag device 720 may obtain (or estimate) its position based on the calculated TDoA value. Therefore, the tag device 720 may estimate its own position without exposing its own position.

[0171] Figure 7b An example of a ranging block structure of a downlink TDoA scheme according to an embodiment of the present disclosure is shown.

[0172] Figure 7b The ranging block structure can be used to perform Figure 7a An example of a ranging block structure for a ranging scheme.

[0173] refer to Figure 7b , a ranging block may include multiple ranging rounds.

[0174] As an embodiment, a ranging block may include a plurality of ranging rounds allocated to each of a plurality of clusters. For example, when n clusters are deployed, a ranging block may include a first ranging round allocated to a first cluster, a second ranging round allocated to a second cluster, and an nth ranging round allocated to an nth cluster. Figure 7b Although not shown in the figure, a plurality of ranging rounds may be allocated to one cluster, or one ranging round may be allocated to a plurality of clusters according to an embodiment.

[0175] In an embodiment, a ranging round may include a plurality of ranging slots. A ranging round may include a plurality of ranging slots allocated for respective ranging messages sent by anchor devices belonging to a cluster associated with the ranging round. For example, if a first cluster includes one initiator anchor and three responder anchors, a ranging round for the first cluster may include a first ranging slot (e.g., ranging slot index 0) allocated for sending / receiving a polling message of an initiator anchor included in the first cluster, a second ranging slot allocated for sending / receiving a response message of the first responder anchor, a third ranging slot allocated for sending / receiving a response message of the second responder anchor, a fourth ranging slot allocated for sending / receiving a response message of the third responder anchor, and a fifth ranging slot allocated for sending / receiving a final message of the initiator anchor.

[0176] In this scheme, a ranging slot may be allocated for the ranging round of each cluster.

[0177] Through Figure 7b In the ranging block structure of the embodiment, the anchor devices of each cluster can exchange ranging messages in one cycle through their own ranging rounds in one ranging block, and the UE (tag device) can receive these ranging messages and calculate its position. Such an operation can be repeated for each ranging block. Therefore, the position of the UE can be updated within the period of the ranging block.

[0178] Figure 8 A payment processing method using UWB according to an embodiment of the present disclosure is shown.

[0179] refer to Figure 8 , payment processing using UWB can be performed by payment terminal 801, UE 802 and / or payment server 803.

[0180] The payment terminal 801 may be an electronic device that communicates with the UE (or a UWB-enabled payment application of the UE) to perform an electronic funds transfer. The payment terminal 801 may be, for example, a point of service (PoS) terminal or a smartphone that supports payment processing functions. In an embodiment, the payment terminal 801 may serve as a controller / initiator of a TWR and / or a DT-anchor of a DL-TDoA. For example, the payment terminal 801 may have Figure 1 All or some components of a UWB device or Figure 2 all or some components of an electronic device (eg, a first electronic device or a second electronic device).

[0181] UE 802 may be an electronic device of a user including a UWB enabled payment application. UE 802 may be, for example, a smartphone of the user. In an embodiment, UE 802 may be used as a controller / responder of TWR and / or as a DT-tag of DL-TDoA. For example, UE 802 may have Figure 1 All or some components of a UWB device or Figure 2 all or some components of an electronic device (eg, a first electronic device or a second electronic device).

[0182] The payment server 803 , such as an acquirer and an issuer, may be a backend server (system) that supports payment to the payment terminal 801 and / or the UE 802 .

[0183] refer to Figure 8 , the payment processing method using UWB includes a UWB / BLE-based device discovery operation 810, a payment terminal information sending operation 820, a user information sending operation 830, a transaction information sending operation 840, a UWB secure ranging operation 850 and / or a payment operation 860. However, depending on the implementation, some steps may be omitted, multiple steps may be combined into one step, or additional steps may be further performed. In addition, the steps may be performed in an order different from the order shown. For example, the transaction information sending operation 840 may be performed after the UWB secure ranging operation 850. For example, the UWB secure ranging operation 850 may be omitted.

[0184] Device discovery operation based on UWB / BLE 810

[0185] In an embodiment, the UWB / BLE based device discovery operation 810 may include a BLE advertising operation.

[0186] As an embodiment, the BLE advertising operation may include an operation in which the payment terminal 801 sends a BLE advertising packet to the UE as a BLE advertiser. As an embodiment, the BLE advertising packet may include at least one piece of information that enables the UE 802 to initiate at least one UWB operation. For example, the BLE advertising packet may include a UWB payment identifier for identifying a supported payment service (or payment application). As an embodiment, at least one UWB operation that may be initiated based on the reception of the BLE advertising packet may include at least one of the DL-TDoA positioning process 811, the UWB advertising process 812, and the contention-based ranging (UWB contention-based ranging) process 813.

[0187] In an embodiment, the DL-TDoA positioning process 811 may be initiated upon receipt of a BLE advertising packet or execution of a UWB enabled payment application through user input.

[0188] The DL-TDoA positioning process 811 may provide a DL-TDoA based positioning service to the UE 802. Therefore, the UE 802 may estimate its location and perform proximity-based payment transactions without exposing the location to the payment terminal 801.

[0189] As an embodiment, the DL-TDoA positioning process 811 may include an operation for the payment terminal 801 to send a UWB message for DL-TDoA (eg, a polling DTM, a response DTM, or a final DTM).

[0190] In an embodiment, the contention-based ranging process 813 may be initiated upon receipt of a BLE advertising packet or execution of a UWB-enabled payment application through user input.

[0191] When the payment terminal 801 and the UE 802 are unaware of each other, the UE 802 is not suitable for performing scheduling-based ranging to respond to the UWB message (e.g., RIM) sent by the payment terminal 801. Therefore, in order for the UE 802 to respond to the UWB message sent by the payment terminal 801, it is necessary to perform contention-based ranging.

[0192] As an embodiment, the contention-based ranging process 813 may include an operation for the payment terminal 801 to send a control message for contention-based ranging. The control message may include information on a CAP for contention-based access of the UE 802.

[0193] As an embodiment, a control message (information) for contention-based ranging together with a message (information) for DL-TDoA may be transmitted through one combined UWB message.

[0194] As an embodiment, in the contention-based ranging process 813, when a preset condition is met, the UE 802 may respond to the UWB message sent by the payment terminal 801. For example, when the distance between the UE 802 and the payment terminal 801 is identified as being less than or equal to a preset distance based on the result obtained by the DL-TDoA positioning process 811, the UE 802 may send a response message (e.g., RRM) to the payment terminal 801. As an embodiment, the UE 802 may send the response message in any time slot within the CAP set by the payment terminal 801.

[0195] In an embodiment, the UWB advertising process 812 may be initiated based on the reception of a BLE advertising packet or the operation of a UWB-enabled payment application through user input. In the UWB advertising process 812, the payment terminal 801 may send a UWB advertising message (signal). The UE 802 may measure the AoA value of the received UWB advertising message. Based on the measured AoA value, the user's intention for payment processing may be detected. For example, the user's posture (tilting UX) of pointing the UE 802 toward the payment terminal 801 may be preset as a posture for indicating the user's intention to start payment processing. When this posture is taken, the AoA value of the UWB advertising message received from the payment terminal 801 may be measured to be almost zero. Therefore, in this case, when the AoA value is measured to be close to zero, the UE 802 may recognize that there is an intention for the user to initiate a payment process.

[0196] Payment terminal information sending operation 820

[0197] In an embodiment, the payment terminal information sending operation 820 may include an operation for the payment terminal 801 to send the payment terminal information to the UE 802. The payment terminal information may be referred to as PoS information.

[0198] As an embodiment, the payment terminal information may be included in a control message for contention-based ranging and transmitted from the payment terminal 801 to the UE 802. As an embodiment, the payment terminal information may be included in a message for DL-TDoA (e.g., polling DTM, response DTM, or final DTM) and transmitted from the payment terminal 801 to the UE 802. As an embodiment, the payment terminal information may be included in a UWB message, in which the control message for contention-based ranging and the message for DL-TDoA are combined and transmitted from the payment terminal 801 to the UE 802. Therefore, the payment terminal information may be transmitted in-band through UWB.

[0199] As an embodiment, the payment terminal information may include identification information (e.g., identifier) ​​about the payment terminal 901 (or a store associated with the payment terminal 901), name information (e.g., nickname) about the payment terminal 901 (or a store associated with the payment terminal 901), and / or random challenge information (posChallenge) about the payment terminal 901 for mutual authentication. The identification information about the payment terminal may be a string based on an object identifier (OID) or a universal unique identifier (UUID). The identification information about the payment terminal may be an identification number of a store managed by a server that interacts with the store, or identification information about a PoS device or terminal in a specific store. The random challenge information (posChallenge) about the payment terminal 901 may be a random value (e.g., a random number) generated by the payment terminal 901 for mutual authentication of a random challenge scheme.

[0200] User information sending operation 830

[0201] In an embodiment, the user information sending operation 830 may include an operation for the UE 802 to send the user information to the payment terminal 801 .

[0202] As an embodiment, in the contention-based ranging process 813, the user information may be included in and transmitted in a response message (eg, RRM of SS-TWR) transmitted from the UE 802 to the payment terminal 801. Therefore, the user information may be transmitted in-band through UWB.

[0203] As an embodiment, the user information may include identification information (e.g., an identifier) ​​about the UE 902 (or a user of the UE 902), name information (e.g., a nickname) about the UE 902 (or a user of the UE 902), and / or random challenge information (userChallenge) about the UE 902 for mutual authentication. The identification information about the UE may be a string based on an object identifier (OID) or a universally unique identifier (UUID). The identification information of the UE may be a user-specific number managed by a payment-related application (e.g., a third-party application such as a Samsung payment application, a Coupang application, a Baedal Minjok, or an SSG). The user identification information may be an identifier of a subscriber identity module (SIM) managed by a communication company. The random challenge information (userChallenge) about the UE 902 may be a random value (e.g., a random number) generated by the UE 902 for mutual authentication of a random challenge scheme.

[0204] Transaction information sending operation 840

[0205] In an embodiment, the transaction information sending operation 840 may include an operation for the payment terminal 801 to send the transaction information to the UE (or the UWB-enabled payment application of the UE 802 ).

[0206] As an implementation method, the transaction information may be sent via a UWB data message (data frame).

[0207] As an embodiment, the transaction information may be payment-related private information, such as the store name and transaction amount sent from the payment terminal 801 to the UE 802. The transaction information may include transaction-related information (transaction date, bank card name, bank card number, approval number) entered in a typical bank card transaction statement.

[0208] As an embodiment, the transaction information sending operation 840 may be performed after a secure channel (session) is established. For example, the transaction information sending operation 840 may be performed after a secure session is established through the UWB secure ranging process 850 .

[0209] UWB secure ranging operation 850

[0210] In an embodiment, the UWB secure ranging operation 850 may include a process of performing secure ranging between the payment terminal 801 and the UE 802 using an STS (eg, a dynamic STS). Thus, a secure session may be configured between the payment terminal 801 and the UE 802.

[0211] As an embodiment, the UWB secure ranging operation 850 may be an optional step.

[0212] Payment Operation 860

[0213] In an embodiment, the payment operation 860 may include a process 861 in which the UE 802 and the payment terminal 801 exchange UWB secure data including payment information.

[0214] As an implementation, the payment information may be sent via a UWB data message (data frame).

[0215] As an embodiment, the payment information may be payment-related private information, such as a bank card number sent from UE 802 to payment terminal 801. Transaction information may include transaction-related information (transaction date, bank card name, bank card number, approval number) entered in a typical bank card transaction statement. As an embodiment, in the process 861 of exchanging UWB security data, the payment information may be encrypted and sent over a secure channel.

[0216] In an embodiment, the payment operation 860 may include a process 862 in which the UE 802 and the payment terminal 801 perform an online payment.

[0217] Payment terminal 801 and / or UE 802 may use the information exchanged through payment operation 860 to perform backend interactions with payment server 803 to complete the transaction.

[0218] Hereinafter, a method for performing both a contention-based ranging procedure and a DL-TDoA procedure and a UWB message format for the method are described.

[0219] Fig. 9 A method for performing DL-TDoA ranging and contention-based ranging by a UWB device according to an embodiment of the present disclosure is shown.

[0220] Fig. 9 The ranging process of the embodiment may be a ranging process in which DL-TDoA ranging and contention-based ranging are performed together.

[0221] and Figure 7a Compared with the DL-TDoA process, Fig. 9 During the ranging process of the implementation scheme, each responder anchor may send two response DTMs (second DTMs) in one ranging cycle (DL-TDoA ranging cycle).

[0222] and Figure 7a Compared with DL-TDoA, Fig. 9 The UWB message used in the ranging process of the embodiment may include both a payload IE for contention-based ranging and a payload IE for DL-TDoA.

[0223] exist Fig. 9 In the embodiment, for ease of description, it is assumed that five anchors including one initiator anchor 901 and four responder anchors 902-1 to 902-4 and two UEs 903-1 and 903-2 perform the ranging process, but the embodiment is not limited thereto. For example, a different number of anchors and UEs than shown may participate in the ranging process.

[0224] In an embodiment, the initiator anchor 901 may be a payment terminal (eg, Figure 8 As an embodiment, the initiator anchor 901 may serve as a controller / initiator of contention-based ranging (TWR) and a DT-anchor (eg, initiator DT-anchor) of DL-TDoA (OWR).

[0225] In an embodiment, responder anchors 902-1, 902-2, 902-3, and 902-4 may be payment terminals for UWB-based payment services (e.g., Figure 8As an embodiment, the responder anchors 902-1, 902-2, 902-3, and 902-4 may serve as controllers / initiators of contention-based ranging (TWR) and DT-anchors (eg, responder DT-anchors) of DL-TDoA (OWR).

[0226] In an embodiment, UEs 903-1 and 903-2 may be UEs for UWB-based payment services (eg, Figure 8 As an embodiment, UE 903-1 and 903-2 may be used as a controller / responder of contention-based ranging (TWR) and a DT-tag of DL-TDoA (OWR).

[0227] In an embodiment, Fig. 9 The ranging process of the embodiment of can be performed in one ranging round. In example, Fig. 9 Operations 910 to 940 may be performed in one ranging round.

[0228] refer to Fig. 9 In operation 910, the initiator anchor 901 may send or broadcast a first UWB message to initiate a ranging process. The first UWB message may be used to provide both a RIM function for contention-based ranging and a polling DTM function for DL-TDoA. In addition, the first UWB message may be used for UWB advertising for tilted UX. In addition, the first UWB message may be used to send payment terminal information. The first UWB message may be referred to as an initiation message, a first DTM, or a polling DTM.

[0229] In an embodiment, the first UWB message may include both a payload IE for contention-based ranging and a payload IE for DL-TDoA.

[0230] In an embodiment, the payload IE for contention-based ranging in the first UWB message may include data of a control message for contention-based ranging. As an embodiment, the control message for contention-based ranging may be a control message type 2. As an embodiment, the control message may include information indicating the size of the CAP (CAP size information).

[0231] In an embodiment, the payload IE for DL-TDoA in the first UWB message may include data for polling DTM.As an embodiment, the payload IE for DL-TDoA in the first UWB message may include scheduling information for each responder anchor 902-1, 902-2, 902-3, and 902-4.

[0232] In operation 920, each of responder anchors 902-1, 902-2, 902-3, and 902-4 may send or broadcast a second UWB message in response to the first UWB message. The first UWB message may be used to provide both RIM functionality for contention-based ranging and response DTM functionality for DL-TDoA. In addition, the second UWB message may be used for UWB advertising for tilted UX. In addition, the second UWB message may be used to send payment terminal information. The second UWB message may be referred to as a first response message, a second DTM, or a response DTM.

[0233] In an embodiment, each responder anchor 902-1, 902-2, 902-3, and 902-4 may send or broadcast a second UWB message in its own ranging slot based on the first scheduling information in the first UWB message.

[0234] In an embodiment, the second UWB message may include both a payload IE for contention-based ranging and a payload IE for DL-TDoA.

[0235] In an embodiment, the payload IE for contention-based ranging in the second DTM message may include data of a control message for contention-based ranging. As an embodiment, the control message (CM) for contention-based ranging may be a control message type 2. As an embodiment, the control message for contention-based ranging in the second DTM may be synchronized control information.

[0236] As an embodiment, in operation 910 , the synchronized control information may be a control message synchronized with a control message included in the first UWB message transmitted by the initiator anchor 901 .

[0237] As an embodiment, the synchronized control information may set the CAP for contention-based ranging to the same duration. In other words, the synchronization of control messages with each other may mean that the CAP configured by the synchronized control information has the same duration. For example, when the CAP set by the control message included in the first control message is set to a period corresponding to ranging slot #11 to ranging slot #20, the control message synchronized with the control message included in the first control message may also set the CAP to a period corresponding to ranging slot #11 to ranging slot #20. Through the synchronized control information, the CAP set by the control messages may be set to the same duration without conflicting with each other.

[0238] Hereinafter, synchronization of control messages is described as an example.

[0239] The control message included in the first UWB message may include CAP size information. The CAP size information may specify the size of the CAP by which the UEs 903-1 and 903-2 may make a contention-based response.

[0240] The CAP having the CAP size may be set to a time after the time when the initiator anchor 901 and the responder anchors 902 - 1 to 902 - 4 transmit all UWB messages for DL-TDoA, that is, the time when operation 940 is completed.

[0241] When it is assumed that operation 940 ends at ranging slot #10 and the size of the CAP specified by the CAP size information about the control message in the first UWB message is 10, the CAP set by the control message in the first UWB message can be set to include the duration of 10 ranging slots after ranging slot #10 (e.g., the period from ranging slot #11 to ranging slot #20). In this case, the CAP set by the second UWB message having a control message synchronized with the control message in the first UWB message should also be set to include the duration of 10 ranging slots after ranging slot #10 (e.g., the ranging slot period from ranging slot #11 to ranging slot #20). Therefore, the value of the size of the CAP set by the control message in the first UWB message and the index value of the ranging slot included in the CAP should be equal to the value of the size of the CAP set by the synchronized control information in the second UWB message and the index value of the ranging slot included in the CAP. Through these synchronized control information, the durations during which UEs 903-1 and 903-2 can perform contention-based responses can all be set to have the same time period without conflict.

[0242] Hereinafter, a method for setting synchronized control information is described as an example.

[0243] For example, when assuming there is one initiator anchor and three responder anchors, each of the four anchors sends two UWB messages (DTM) (ref. Fig. 9 ), and the CAP size is 5, the method for configuring the synchronization control information is as follows.

[0244] In ranging slot #0, the initiator anchor sends the first UWB message (Origination message).

[0245] In ranging slots #1, #2, and #3, the responder anchors each transmit a second UWB message (first response message).

[0246] In ranging slot #4, the initiator anchor sends the third UWB message (final message).

[0247] In ranging slots #5, #6, and #7, the responder anchors each transmit a fourth UWB message (second response message).

[0248] The UE may attempt a contention-based response by randomly selecting one of ranging slots #8, #9, #10, #11, and #12.

[0249] In this case, when the initiator anchor transmits the first UWB message in ranging slot #0, the initiator anchor may set the value of the CAP size information in the control message to 5, and set the value of the responder management list size (RML size) information to 7. Therefore, the UE may skip 7 ranging slots corresponding to the value 7 specified by the RML size information in ranging slot #0 in which the initiator anchor transmits the first UWB message, and then perform contention-based response in 5 ranging slots corresponding to the value 5 specified by the CAP size information starting from ranging slot #8. In other words, based on the CAP size information (=5) and the RML size information (=7) of the control message in the first UWB message, the UE may recognize that the periods corresponding to ranging slots #8, #9, #10, #11, and #12 are CAPs, and transmit a response message in any slot within the CAP.

[0250] Then, when the first responder anchor sends the second message in ranging slot #1, the first responder anchor may similarly set the value of the CAP size information in the control message to 5, and set the value of the RML size information to 6. Therefore, the UE may skip 6 ranging slots corresponding to the value 6 specified by the RML size information from ranging slot #1 in which the first responder anchor sends the second UWB message, and then perform contention-based response in 5 ranging slots corresponding to the value 5 specified by the CAP size information starting from ranging slot #8. In other words, the same CAP may be set by the control message of the initiator anchor and the synchronized control information of the first responder anchor.

[0251] Likewise, control messages in UWB messages transmitted by all other anchors may be set to specify cycles corresponding to the same ranging slots #8, #9, #10, #11, and #12 as the above-mentioned CAP so that the control messages may be synchronized with each other.

[0252] In an embodiment, the payload IE of the DL-TDoA in the second UWB message may include data of the response DTM. As an embodiment, the payload IE of the DL-TDoA in the second UWB message may include first response time information. The first response time information about the corresponding responder anchor may include a first responder response time, which indicates the time elapsed between the time when the corresponding responder anchor receives the first UWB message and the time when the second UWB message is sent. In addition, the second UWB message may also include information about additional response times. Fig.15 An example of a response time included in the second UWB message is described below.

[0253] In operation 930, the initiator anchor 901 may send or broadcast a third UWB message in response to the second UWB message from the responder anchors 902-1, 902-2, 902-3, and 902-4. The third UWB message may be used to provide both the RIM function for contention-based ranging and the final DTM function for DL-TDoA. In addition, the third UWB message may be used for UWB advertising for tilted UX. In addition, the third UWB message may be used to send payment terminal information. The third UWB message may be referred to as a final message, a third DTM, or a final DTM.

[0254] In an embodiment, the third UWB message may include both a payload IE for contention-based ranging and a payload IE for DL-TDoA.

[0255] In an embodiment, the payload IE for contention-based ranging in the third UWB message may include data of a control message for contention-based ranging. As an embodiment, the control message for contention-based ranging in the third DTM may be synchronized control information. The synchronization of the control message may refer to the description of operation 920.

[0256] In an embodiment, the payload IE for DL-TDoA in the third UWB message may include data of the final DTM. As an embodiment, the payload IE for DL-TDoA in the third UWB message may include second response time information. The second response time information may include a list of response times for second UWB messages from responder anchors 902-1, 902-2, 902-3, and 902-4, respectively. The response time of the second UWB message may be the time elapsed between the time when the initiator anchor 901 receives the second UWB message from the corresponding responder anchor and the time when the third UWB message is sent. In addition, the third UWB message may also include information about additional response times. Refer to the following Fig.15 An example of the response time included in the third UWB message will be described.

[0257] In operation 940, each of responder anchors 902-3, 902-4, 902-3 and 902-4 may send or broadcast a fourth UWB message in response to the third UWB message. The fourth UWB message may be used to provide both RIM functionality for contention-based ranging and response DTM functionality for DL-TDoA. In addition, the fourth UWB message may be used for UWB advertising for tilted UX. In addition, the fourth UWB message may be used to send payment terminal information. As an embodiment, the message format of the fourth UWB message may be the same as the message format of the second UWB message. The fourth UWB message may be referred to as a second response message, a second DTM, or a response DTM.

[0258] In an embodiment, each responder anchor 902-1, 902-4, 902-3, and 902-4 may send or broadcast a second UWB message in its own ranging slot based on the second scheduling information in the first UWB message.

[0259] In an embodiment, the fourth UWB message may include both a payload IE for contention-based ranging and a payload IE for DL-TDoA.

[0260] In an embodiment, the payload IE for contention-based ranging in the fourth UWB message may include data of a control message for contention-based ranging. As an embodiment, the control message (CM) for contention-based ranging may be a control message type 2. As an embodiment, the control message for contention-based ranging in the fourth DTM may be synchronized control information. The synchronization of the control message may refer to the description of operation 920.

[0261] In an embodiment, the payload IE of the DL-TDoA in the fourth UWB message may include data of the response DTM. As an embodiment, the payload IE of the DL-TDoA in the fourth UWB message may include third response time information. The third response time information about the corresponding responder anchor may include a second responder response time, which indicates the time elapsed between the time when the corresponding responder anchor receives the third UWB message and the time when the fourth UWB message is sent. In addition, the fourth UWB message may also include information about additional response times. Fig.15 An example of a response time included in the fourth UWB message will be described.

[0262] In an embodiment, UEs 903-1 and 903-2 may receive a first UWB message, a second UWB message, a third UWB message, and a fourth UWB message, calculate TDoA based on a payload IE for DL-TDoA in each UWB message, and estimate their locations based on the calculated TDoA.

[0263] At the same time, Figure 7a In the case of the embodiment of , in one DL-TDoA ranging cycle, the initiator anchor sends two DTMs, but the responder anchor may only send one DTM. Figure 7a In the case of the implementation scheme, it is difficult for the UE to estimate the CFO of the responder anchor.

[0264] However, in Fig. 9 In the case of an embodiment of the present invention, all anchors send two or more DTMs (UWB messages) in one DL-TDoA ranging cycle. Therefore, the UE can receive two or more DTMs from each anchor. As a result, the UE can estimate the clock frequency offset (CFO) for any anchor based on the two or more DTMs received from each anchor. In addition, since each anchor sends two or more DTMs, the possibility of the UE obtaining TDoA can be increased.

[0265] In addition, Fig. 9 In the case of the implementation mode of the present invention, the UWB message used in the ranging process includes a payload IE for contention-based ranging and a payload IE for DL-TDoA. Therefore, in one ranging cycle (ranging round), DL-TDoA ranging and contention-based ranging can be performed together. This can improve the efficiency of resource usage.

[0266] Fig.10 A method for performing DL-TDoA ranging and contention-based ranging by a UWB device according to an embodiment of the present disclosure is shown.

[0267] Fig.10 The ranging process of the embodiment may be a ranging process in which DL-TDoA ranging and contention-based ranging are performed together.

[0268] and Figure 7a Compared with the DL-TDoA process, Fig.10 During the ranging process of the implementation scheme, each responder anchor may send two response DTMs (second DTMs) in one ranging cycle (DL-TDoA ranging cycle).

[0269] and Figure 7a Compared with DL-TDoA, Fig.10 The UWB message used in the ranging process of the embodiment may include both a payload IE for contention-based ranging and a payload IE for DL-TDoA.

[0270] exist Fig.10In the embodiment, for ease of description, it is assumed that five anchors including one initiator anchor 1001 and four responder anchors 1002-1 to 1002-4 and two UEs 1003-1 and 1003-2 perform the ranging process, but the embodiment is not limited thereto. For example, a different number of anchors and UEs than shown may participate in the ranging process.

[0271] In an embodiment, the initiator anchor 1001 may be a payment terminal for a UWB-based payment service (eg, Figure 8 As an embodiment, the initiator anchor 1001 may serve as a controller / initiator of contention-based ranging (TWR) and a DT-anchor (eg, initiator DT-anchor) of DL-TDoA (OWR).

[0272] In an embodiment, responder anchors 1002-1, 1002-2, 1002-3, and 1002-4 may be payment terminals for UWB-based payment services (e.g., Figure 8 As an embodiment, the responder anchors 1002-1, 1002-2, 1002-3, and 1002-4 may serve as controllers / initiators of contention-based ranging (TWR) and DT-anchors (eg, responder DT-anchors) of DL-TDoA (OWR).

[0273] In an embodiment, UE 1003-1 and 1003-2 may be UEs for UWB-based payment services (eg, Figure 8 As an embodiment, UE 1003-1 and 1003-2 may be used as a controller / responder of contention-based ranging (TWR) and a DT-tag of DL-TDoA (OWR).

[0274] In an embodiment, Fig.10 The ranging process of the embodiment of can be performed in one ranging round. For example, Fig.10 Operations 1010 to 1050 can be performed in one ranging round. Fig.10 Operations 1010 to 1040 may correspond to Fig. 9 Operations 9010 to 9040. Therefore, Fig.10 The description of operations 1010 to 1040 can be referred to Fig. 9 Description of operations 9010 to 9040.

[0275] refer to Fig.10In operation 1010, the initiator anchor 1001 may send or broadcast a first UWB message to initiate a ranging process. The first UWB message may be used to provide both a RIM function for contention-based ranging and a polling DTM function for DL-TDoA. The first UWB message may be referred to as an initiation message, a first DTM, or a polling DTM.

[0276] In an embodiment, the first UWB message may include a payload IE for contention-based ranging and a payload IE for DL-TDoA.

[0277] In an embodiment, the payload IE for contention-based ranging in the first UWB message may include data of a control message for contention-based ranging. As an embodiment, the control message for contention-based ranging may be a control message type 2. As an embodiment, the control message may include information indicating the size of the CAP (CAP size information).

[0278] In an embodiment, the payload IE for DL-TDoA in the first UWB message may include data for polling DTM.As an embodiment, the payload IE for DL-TDoA in the first UWB message may include scheduling information for each responder anchor 1002-1, 1002-2, 1002-3, and 1002-4.

[0279] In operation 1020, each of responder anchors 1002-1, 1002-2, 1002-3, and 1002-4 may transmit or broadcast a second UWB message in response to the first UWB message. The first UWB message may be used to provide both a RIM function for contention-based ranging and a response DTM function for DL-TDoA. The second UWB message may be referred to as a first response message, a second DTM, or a response DTM.

[0280] In an embodiment, each responder anchor 1002-1, 1002-2, 1002-3, and 1002-4 may send or broadcast a second UWB message in its own ranging time slot based on the first scheduling information in the first UWB message.

[0281] In an embodiment, the second UWB message may include a payload IE for contention-based ranging and a payload IE for DL-TDoA.

[0282] In an embodiment, the payload IE for contention-based ranging in the second DTM message may include data of a control message for contention-based ranging. As an embodiment, the control message (CM) for contention-based ranging may be a control message type 2. As an embodiment, the control message for contention-based ranging in the second DTM may be synchronized control information.

[0283] As an embodiment, in operation 1010 , the synchronized control information may be a control message synchronized with a control message included in the first UWB message transmitted by the initiator anchor 1001 .

[0284] As an embodiment, the synchronized control information may set the CAP used for contention-based ranging to the same duration. In other words, the synchronization of control messages with each other may mean that the CAP configured by the synchronized control messages have the same duration. For example, when the CAP set by the control message included in the first control message is set to a period corresponding to ranging slot #11 to ranging slot #20, the control message synchronized with the control message included in the first control message may also set the CAP to a period corresponding to ranging slot #11 to ranging slot #20. Through the synchronized control messages, the CAP set by the control messages may be set to the same duration without conflicting with each other. The synchronization of control messages may refer to Fig. 9 Description of operation 920.

[0285] In an embodiment, the payload IE for DL-TDoA in the second UWB message may include data of the response DTM. As an embodiment, the payload IE for DL-TDoA in the second UWB message may include first response time information. The first response time information about the corresponding responder anchor may include a first responder response time, which indicates the time elapsed between the time when the corresponding responder anchor receives the first DTM and the time when the second DTM is sent. In addition, the second UWB message may also include information about additional response times. Fig.15 An example of a response time included in the second UWB message is described below.

[0286] In operation 1030, the initiator anchor 1001 may send or broadcast a third UWB message in response to the second UWB messages from the responder anchors 1002-1, 1002-2, 1002-3, and 1002-4. The third UWB message may be used to provide both the RIM function for contention-based ranging and the final DTM function for DL-TDoA. The third UWB message may be referred to as a final message, a third DTM, or a final DTM.

[0287] In an embodiment, the third UWB message may include both a payload IE for contention-based ranging and a payload IE for DL-TDoA.

[0288] In an embodiment, the payload IE for contention-based ranging in the third UWB message may include data of a control message for contention-based ranging. As an embodiment, the control message for contention-based ranging in the third DTM may be synchronized control information. The synchronization of the control message may refer to Fig. 9 Description of operation 920.

[0289] In an embodiment, the payload IE for DL-TDoA in the third UWB message may include data of the final DTM. As an embodiment, the payload IE for DL-TDoA in the third UWB message may include second response time information. The second response time information may include a list of response times for second DTMs from responder anchors 1002-1, 1002-2, 1002-3, and 1002-4, respectively. The response time of the second DTM may be the elapsed time between the time when the initiator anchor 1001 receives the second DTM from the corresponding responder anchor and the time when the third DTM is sent. In addition, the third UWB message may also include information about additional response times. Refer to the following Fig.15 An example of the response time included in the third UWB message will be described.

[0290] In operation 1040, each of responder anchors 1002-3, 1002-4, 1002-3, and 1002-4 may send or broadcast a second UWB message in response to the first UWB message. The fourth UWB message may be used to provide both a RIM function for contention-based ranging and a response DTM function for DL-TDoA. As an embodiment, the message format of the fourth UWB message may be the same as the message format of the second UWB message. The fourth UWB message may be referred to as a second response message, a second DTM, or a response DTM.

[0291] In an embodiment, each responder anchor 1002-1, 1002-4, 1002-3, and 1002-4 may send or broadcast a second UWB message in its own ranging time slot based on the second scheduling information in the first UWB message.

[0292] In an embodiment, the fourth UWB message may include both a payload IE for contention-based ranging and a payload IE for DL-TDoA.

[0293] In an embodiment, the payload IE for contention-based ranging in the fourth UWB message may include data of a control message for contention-based ranging. As an embodiment, the control message (CM) for contention-based ranging may be a control message type 2. As an embodiment, the control message for contention-based ranging in the fourth UWB message may be synchronized control information. The synchronization of the control message may refer to the description of operation 920.

[0294] In an embodiment, the payload IE for DL-TDoA in the fourth UWB message may include data of the response DTM. As an embodiment, the payload IE for DL-TDoA in the fourth UWB message may include third response time information. The third response time information about the corresponding responder anchor may include a second responder response time, which indicates the time elapsed between the time when the corresponding responder anchor receives the third DTM and the time when the fourth DTM is sent. In addition, the fourth UWB message may also include information about additional response times. Fig.15 An example of a response time included in the fourth UWB message will be described.

[0295] In an embodiment, UEs 1003-1 and 1003-2 may receive a first UWB message, a second UWB message, a third UWB message, and a fourth UWB message, calculate TDoA based on a payload IE for DL-TDoA in each UWB message, and estimate their locations based on the calculated TDoA.

[0296] In operation 1050, each UE 1003-1 and 1003-2 may send a ranging response message for contention-based ranging (e.g., RRM for SS-TWR) to the selected anchor. Upon receiving the response message from the UE, the anchor may perform an SS-TWR operation based on the ranging response message. Thus, the anchor may obtain an accurate distance to the UE. The ranging response message may be referred to as a fifth UWB message or an extended ranging response message (extended RRM).

[0297] In an embodiment, UE 1003-1 and 1003-2 may select anchor 1001 and one of 1002-1 to 1002-4 based on a preset criterion. For example, based on the DL-TDoA result, UE 1003-1 or 1003-2 may select an anchor within a preset distance (e.g., 2 meters) from its location. When there are multiple anchors within the preset distance, the UE may select an anchor with the closest distance among the multiple anchors.

[0298] In an embodiment, UE 1003-1 and 1003-2 may send a ranging response message in any ranging time slot within the CAP. As an embodiment, the CAP may be set by a control message in a first UWB message, synchronized control information in a second UWB message, synchronized control information in a third UWB message, and synchronized control information in a fourth UWB message. The CAPs set by synchronized control information may have the same duration.

[0299] In an embodiment, the ranging response message may include user information. Therefore, the user information may be sent within the UWB band. For example, the ranging response message may include inquiry information (user inquiry) about the UE.

[0300] In an embodiment, the ranging response message may include two pieces of response time information for the selected anchor. The two pieces of response time information may be used to correct the CFO in the corresponding anchor.

[0301] At the same time, Figure 7a In the case of the embodiment of , in one DL-TDoA ranging cycle, the initiator anchor sends two DTMs, but the responder anchor may only send one DTM. Figure 7a In the case of the implementation scheme, it is difficult for the UE to estimate the CFO of the responder anchor.

[0302] However, in Fig.10 In the case of an embodiment of the present invention, all anchors send two or more DTMs (UWB messages) in one DL-TDoA ranging cycle. Therefore, the UE can receive two or more DTMs from each anchor. As a result, the UE can estimate the clock frequency offset (CFO) for any anchor based on the two or more DTMs received from each anchor. In addition, since each anchor sends two or more DTMs, the possibility of the UE obtaining TDoA can be increased.

[0303] In addition, Fig.10 In the case of the implementation mode of the present invention, the UWB message used in the ranging process includes a payload IE for contention-based ranging and a payload IE for DL-TDoA. Therefore, in one ranging cycle (ranging round), DL-TDoA ranging and contention-based ranging can be performed together. This can improve the efficiency of resource usage.

[0304] Fig.11 The structure of a UWB message according to an embodiment of the present disclosure is shown.

[0305] exist Fig.11 In an embodiment of the present invention, the UWB message may be Fig. 9 and Fig.10 Example of UWB messages used in the ranging process. Fig.11 The UWB message can be, for example, Fig. 9 and Fig.10 Examples of first to fourth UWB messages used in a ranging process.

[0306] refer to Fig.11 The UWB message includes a MAC frame header 1110, a MAC payload including a payload IE 1120-1 for contention-based ranging and a payload IE 1120-2 for DL-TDoA, and a MAC frame trailer 1130 including an FCS.

[0307] In an embodiment, the MAC frame header 1110 may include Figure 3 All or some fields in the MAC frame header.

[0308] In an embodiment, the payload IE 1120-1 for contention-based ranging may include data of a control message for contention-based ranging. As an embodiment, the control message for contention-based ranging may include information indicating the size of the CAP, information about a transmit (Tx) offset, and / or configuration information related to a responder management list (RML).

[0309] In an embodiment, the Payload IE 1120 - 2 for DL-TDoA may include all or some fields contained in any one of the Payload IE of the Polling DTM, the Payload IE of the Responder DTM, or the Payload IE of the Final DTM.

[0310] Reference below Fig.12a and Figure 12b An example of a payload (MAC payload) including a payload IE 1120 - 1 for contention-based ranging and a payload IE 1120 - 2 for DL-TDoA is described.

[0311] Fig.12a The payload structure of a UWB message according to an embodiment of the present disclosure is shown.

[0312] exist Fig.12a In an embodiment, the payload of the UWB message may be Fig.11 An example of the payload (MAC payload) of a UWB message.

[0313] refer to Fig.12a , the UWB message (or the payload of the UWB message) may include a payload IE 1220-1 for contention-based ranging and a payload IE 1220-2 for DL-TDoA. The payload IE 1220-1 for contention-based ranging may be Fig.11An example of a payload IE 1120-1 for contention-based ranging in FIG. 1220-2 for DL-TDoA may be Fig.11 Example of Payload IE 1120-2 for DL-TDoA.

[0314] exist Fig.12a In an embodiment, the payload IE 1220-1 for contention-based ranging may precede the payload IE 1220-2 for DL-TDoA.

[0315] Payload IE 1220-1 for contention-based ranging

[0316] The payload IE 1220-1 for contention-based ranging may include a control message for contention-based ranging. As an embodiment, the control message for contention-based ranging may be a control message type 2.

[0317] In an embodiment, the payload IE 1220-1 for contention based ranging (or a control message for contention based ranging) may include a UWB message ID field, a message control field, a span length field, an RML size field, and / or an RML field.

[0318] The UWB message ID field may identify a UWB message. In the case of a payload IE 1210a for contention-based ranging, the UWB ID field may be set to a value that specifies the control message.

[0319] The message control field may set parameters for contention-based ranging with responders participating in contention-based ranging. As an embodiment, the message control field may include CAP size information (field) that specifies the size of the contention period used in the CAP in units of ranging slots. Through the CAP size information, the number of ranging slots in which the UE can make a contention-based response may be specified. Table 1 below may show an example of the message control field.

[0320] Table 1

[0321] The Span Length field may specify the number of ranging blocks to skip.

[0322] The RML size field may specify the size of the RML.

[0323] The RML field may be a list of device MAC addresses including known responders. The RML field may include the number of RML elements corresponding to the size of the RML. Table 2 below shows an example of RML elements included in the RML field. Referring to Table 2, each RML element may specify the MAC address of the corresponding responder.

[0324] Table 2

[0325] For example, when a two-byte short MAC address is used and 5 responders are managed by RML, the value of the RML size field may be set to 5, and the RML field may be data having a length of 10 bytes.

[0326] refer to Fig. 9 , the CAP in which the UE can perform a contention-based response can be configured by including a CAP size field and an RML size field in the payload IE 1210a for contention-based ranging. In addition, when the control messages for contention-based ranging are synchronized with each other, the value of the CAP size field and the value of the RML size field can be set so that they all set the same CAP. In this case, the value of the CAP size field can be the same in all synchronized control messages.

[0327] Payload IE 1220-2 for DL-TDOA

[0328] In an embodiment, the Payload IE 1220 - 2 for DL-TDoA may include a UWB message ID field, an OWR message type field, and an OWR message type-related payload field.

[0329] The UWB message ID field may identify a UWB message. In the case of the Payload IE 1220-2 for DL-TDoA, the UWB ID field may be set to a value specifying an OWR message.

[0330] The OWR Message Type field may specify the type of the OWR message. In the case of Payload IE 1220-2 for DL-TDoA, the OWR Message Type field may be set to a value specifying one of Polling DTM, Response DTM, or Final DTM.

[0331] The payload field associated with the OWR message type may include payload data according to the value specified by the OWR message type field. When the value set in the OWR message type field specifies a polling DTM, a responding DTM, or a final DTM, that is, when a DTM is specified, the following reference Fig.13a and Fig.13b To describe examples of payload fields related to the OWR message type.

[0332] Figure 12b The payload structure of a UWB message according to an embodiment of the present disclosure is shown.

[0333] exist Figure 12b In an embodiment, the payload of the UWB message may be Fig.11 An example of the payload (MAC payload) of a UWB message.

[0334] refer to Figure 12b , the UWB message (or the payload of the UWB message) may include a payload IE 1220-1 for contention-based ranging and a payload IE 1220-2 for DL-TDoA. The payload IE 1220-1 for contention-based ranging may be Fig.11 An example of a payload IE 1120-1 for contention-based ranging in FIG. 1220-2 for DL-TDoA may be Fig.11 Example of Payload IE 1120-2 for DL-TDoA.

[0335] and Fig.12a The implementation methods are different. Figure 12b In an embodiment, the payload IE 1220-1 for contention-based ranging may follow the payload IE 1220-2 for DL-TDoA.

[0336] At the same time, Figure 12b In an embodiment of the present invention, each field (information) included in the payload IE 1220-1 for contention-based ranging is consistent with the Fig.12a Each field included in the payload IE 1220-1 for contention-based ranging is the same as in FIG. Fig.12a Description.

[0337] In addition, included in Figure 12b Each field (information) in the payload IE 1220-2 for DL-TDoA of the embodiment is the same as that included in Fig.12a Each field (information) in the payload IE 1220-2 for DL-TDoA is the same. Therefore, you can refer to Fig.12a Description.

[0338] Fig.13a and 13b An example of a payload field related to an OWR message type included in a UWB message according to various embodiments of the present disclosure is shown.

[0339] exist Fig.13a and Fig.13bIn the implementation manner, the payload field associated with the OWR message type of the UWB message may be Fig.12a and Figure 12b Example of payload fields associated with the OWR message type of the Payload IE 1220-2 for DL-TDoA.

[0340] refer to Fig.13a , when the value set in the OWR message type field specifies a polling DTM, a responding DTM, or a final DTM, the payload fields associated with the OWR message type may include a message control field, a round index field, a block index field, a transmit (Tx) timestamp field, and / or a responder DT-anchor management list field.

[0341] The message control field may include settings for the corresponding DTM.

[0342] The round index field may specify the round index of the current ranging round.

[0343] The block index field may specify the block index of the current ranging block.

[0344] The transmit timestamp field may specify the transmit timestamp of the DTM expressed as a local or public time base.

[0345] The Responder DT-Anchor Management List field may include N Responder DT-Anchor Management List elements.

[0346] N may be determined by the value of the Responder DT-Anchor Management List Length field in the Message Control field. Each Responder DT-Anchor Management List element may include a Responder Address field, a Ranging Slot Index field, a Second Ranging Slot Index field, and / or a ToF Result field for the corresponding Responder DT-Anchor. Fig.13b To describe an example of a responder DT-anchor management list element.

[0347] refer to Fig.13b , the responder DT-anchor management list element may include a responder address field, a ranging slot index field, a second ranging slot index field and / or a ToF result field.

[0348] The Responder Address field may specify the address (eg, MAC address) of the responder DT-Anchor (Responder Anchor).

[0349] The Ranging Slot Index field may specify a ranging slot allocated to the responder DT-anchor (responder anchor) identified by the Responder Address field. As an embodiment, the ranging slot specified by the Ranging Slot Index field may be used by the responder DT-anchor to respond to an initiation message (e.g., Fig. 9 and Fig.10The first UWB message) is sent while the first response message (for example, Fig. 9 and Fig.10 In other words, the second ranging slot index field may be used by the responder anchor to send the first response message.

[0350] The second ranging slot index field may specify a second ranging slot allocated to the responder DT-anchor (responder anchor) identified by the responder address field. As an embodiment, the ranging slot specified by the second ranging slot index field may be used by the responder DT-anchor to respond to a final message (e.g., Fig. 9 and Fig.10 A third UWB message) is sent while a second response message (eg, Fig. 9 and Fig.10 In other words, the second ranging slot index field may be used by the responder anchor to send the second response message.

[0351] The ToF Result field may include the ToF as a result of the SS-TWR with the responder DT-Anchor identified by the Responder Address field.

[0352] In an embodiment, the payload fields associated with the OWR message type may further include a clock frequency offset (CFO) field specifying the CFO relative to the initiator anchor and / or a reply time field (e.g., a reply time list field or a responder reply time field) including information about at least one reply time.

[0353] Fig.14 A UCI command for establishing a session for an initiator anchor according to an embodiment of the present disclosure is shown.

[0354] According to an embodiment, the initiator anchor (initiator DT-anchor) may use the DST_MAC_ADDRESS list specified using the UCI command.

[0355] Fig.14 The SESSION_SET_INITIATOR_DT_ANCHOR_RR_RDM_LIST_CMD command may be an example of a UCI command for specifying a DST_MAC_ADDRESS list. The SESSION_SET_INITIATOR_DT_ANCHOR_RR_RDM_LIST_CMD command may be transmitted to the UWBS in the framework of the initiator anchor.

[0356] refer to Fig.14 , the UCI command may include a session ID field, a RR_RDM count field in the RR_RDM_LIST field, and / or a RR_RDM_LIST field.

[0357] The Session ID field may specify the session ID of the DL-TDoA session to be configured for the ranging round given the RDM list of the initiator DT-Anchor.

[0358] The RR_RDM count field may specify the number of RR_RDMs in the RR_RDM_LIST field including a ranging round index and a corresponding DST_MAC_ADDRESS list.

[0359] The RR_RDM_LIST field may include a ranging round index field, a destination MAC address count field, a responder slot field, and a DST_MAC_ADDRESS field.

[0360] The Ranging Round Index field may specify the ranging round index that the DT-Anchor runs as the initiator and the DST_MAC_ADDRESS list shall be set.

[0361] For a specified ranging round index, the Destination MAC Address Count field may specify the number N of destination MAC addresses.

[0362] The responder slot field may specify the responder slot index allocated for responder transmission. The responder slot field may have a size of 1 byte or N+1 bytes or 2N+1 bytes.

[0363] When the Responder Slot field has a size of 2N+1 bytes, Byte 0 may specify the presence of a responder slot, Bytes 1 to Byte N may specify an allocated slot for a responder DT-anchor (Responder Anchor) in the DST_MAC_ADDRESS list, and Bytes N+1 to Byte 2N+1 may specify a second allocated slot for a responder DT-anchor (Responder Anchor) in the DST_MAC_ADDRESS list. In this case, the slots specified in Bytes 1 to Byte N may be used for the responder anchor to send the first response message (e.g., Fig. 9 and Fig.10 The time slots specified in Byte N+1 to Byte 2N+1 may be used by the responder anchor to send a second response message (e.g., Fig. 9 and Fig.10 4th UWB message in ).

[0364] For a specified ranging round, the DST_MAC_ADDRESS field may include a DST_MAC_ADDRESS list. The DST_MAC_ADDRESS list may include MAC addresses of anchors participating as responder anchors in the specified ranging round.

[0365] Fig.15A method for an anchor to transmit response time information during ranging according to an embodiment of the present disclosure is shown.

[0366] Fig.15 The ranging process of the implementation method can be Fig. 9 and Fig.10 An example of the ranging process. Fig.15 The description of the ranging process of the implementation method can be referred to Fig. 9 and Fig.10 Description of the ranging process.

[0367] exist Fig.15 In an embodiment, each anchor may send two UWB messages (DTM).

[0368] exist Fig.15 In the embodiment, for ease of description, it is assumed that four anchors including one initiator anchor 1501 and three responder anchors 1502-1 to 1502-3 perform the ranging process, but the embodiment is not limited thereto. For example, a different number of anchors than shown may participate in the ranging process.

[0369] refer to Fig.15 In operation 1510, the initiator anchor 1501 may send or broadcast a first UWB message (I) (eg, Fig. 9 and Fig.10 The first UWB message) is used to initiate the ranging process.

[0370] In operation 1520-1, the first responder anchor 1502-1 may transmit or broadcast a second UWB message R1 (eg, Fig. 9 and Fig.10 The second UWB message R1 of the first responder anchor 1502-1 may include the following response time information (RT(I, R1)).

[0371] - RT(I, R1): indicates the time that has passed between the time when the first UWB message I is received and the time when the second UWB message R1 is sent.

[0372] As an embodiment, RT(I, R1) may include a payload IE (eg, Fig.11 Payload IE 1120-2 or Fig.12a and Figure 12b The payload of IE 1120-2).

[0373] In operation 1520-2, the second responder anchor 1502-2 may transmit or broadcast a second UWB message R2 (eg, Fig. 9 and Fig.10 The second UWB message R2 of the second responder anchor 1502-2 may include the following two pieces of response time information (RT(I, R1) and RT(R1, R2)): - RT(I, R2): indicates the time that has passed between the time when the first UWB message I is received and the time when the second UWB message R2 is sent.

[0374] -RT(R1, R2): indicates the time that has passed between the time when the second UWB message R1 of the first responder anchor 1502-1 is received and the time when the second UWB message R2 is sent.

[0375] As an embodiment, RT(1, R1) and / or RT(R1, R2) may include a payload IE (eg, Fig.11 Payload IE 1120-2 or Fig.12a and Figure 12b The payload of IE1120-2).

[0376] In operation 1520-3, the third responder anchor 1502-3 may transmit or broadcast a second UWB message R3 (eg, Fig. 9 and Fig.10 The second UWB message R3 of the second responder anchor 1502-2 may include the following three pieces of response time information (RT(I, R3), RT(R1, R3) and RT(R2, R3)).

[0377] - RT(I, R3): indicates the time that has passed between the time when the first UWB message I is received and the time when the second UWB message R3 is sent.

[0378] -RT(R1, R3): indicates the time that has passed between the time when the second UWB message R1 of the first responder anchor 1502-1 is received and the time when the second UWB message R3 is sent

[0379] -RT(R2, R3): indicates the time that has passed between the time when the second UWB message R2 of the second responder anchor 1502-2 is received and the time when the second UWB message R3 is sent.

[0380] As an embodiment, RT(I, R3), RT(R1, R3) and / or RT(R2, R3) may include a payload IE (e.g., Fig.11 Payload IE 1120-2 or Fig.12a and Figure 12b The payload of IE 1120-2).

[0381] In operation 1530, initiator anchor 1501 may transmit or broadcast a third UWB message (eg, Fig. 9 and Fig.10 The third UWB message of the initiator anchor 1501 may include the following three pieces of response time information A1, A2 and A3.

[0382] - A1: indicates the time that has passed between the time when the second UWB message R1 of the first responder anchor 1502-1 is received and the time when its third UWB message is sent.

[0383] - A2: indicates the time that has passed between the time when the second UWB message R2 of the second responder anchor 1502-2 is received and the time when its third UWB message is sent.

[0384] - A3: indicates the time that has passed between the time when the second UWB message R3 of the third responder anchor 1502-3 is received and the time when its third UWB message is sent.

[0385] As an embodiment, A1, A2 and / or A3 may include a payload IE (eg, Fig.11 Payload IE 1120-2 or Fig.12a and Figure 12b The payload of IE 1220-2).

[0386] In operation 1540-1, the first responder anchor 1502-1 may transmit or broadcast a fourth UWB message (eg, Fig. 9 and Fig.10 The fourth UWB message of the first responder anchor 1502-1 may include the following three pieces of response time information A1, A2, and A3.

[0387] - B1: indicates the time that has passed between the time when the second UWB message R2 of the second responder anchor 1502-2 is received and the time when its fourth UWB message is sent.

[0388] - B2: indicates the time that elapsed between the time when the second UWB message R3 of the third responder anchor 1502-3 was received and the time when its fourth UWB message was sent.

[0389] - B3: Indicates the time that elapsed between the time when the third UWB message was received and the time when the fourth UWB message was sent.

[0390] As an embodiment, B1, B2 and / or B3 may include a payload IE (eg, Fig.11 Payload IE 1120-2 or Fig.12a and Figure 12b The payload of IE 1220-2).

[0391] In operation 1540-2, the second responder anchor 1502-2 may transmit or broadcast a fourth UWB message (eg, Fig. 9 and Fig.10 The fourth UWB message of the second responder anchor 1502-2 may include the following three pieces of response time information C1, C2, and C3.

[0392] - C1: indicates the time that elapsed between the time when the second UWB message R3 of the third responder anchor 1502-3 was received and the time when its fourth UWB message was sent.

[0393] - C2: Indicates the time elapsed between the time when the third UWB message is received and the time when the fourth UWB message is sent.

[0394] - C3: indicates the time that elapsed between the time when the first responder anchor 1502-1's fourth UWB message was received and the time when its fourth UWB message was sent.

[0395] As an embodiment, C1, C2 and / or C3 may include a payload IE (eg, Fig.11 Payload IE 1120-2 or Fig.12a and Figure 12b The payload of IE 1220-2).

[0396] In operation 1540-3, the third responder anchor 1502-3 may transmit or broadcast a fourth UWB message (eg, Fig. 9 and Fig.10 The fourth UWB message of the third responder anchor 1502-3 may include the following three pieces of response time information D1, D2, and D3.

[0397] - D1: indicates the time elapsed between the time when the third UWB message is received and the time when the fourth UWB message is sent.

[0398] - D2: indicates the time that elapsed between the time when the first responder anchor 1502-1's third UWB message was received and the time when its fourth UWB message was sent.

[0399] - D3: indicates the time that elapsed between the time when the second responder anchor 1502-2's third UWB message was received and the time when its fourth UWB message was sent.

[0400] As an embodiment, D1, D2 and / or D3 may include a payload IE (eg, Fig.11 Payload IE 1120-2 or Fig.12a and Figure 12b The payload of IE 1220-2).

[0401] Thus, each anchor may include and transmit in its UWB message all or part of the response time information for each UWB received before its UWB message was received. The response time information thus transmitted may be used for CFO correction. Figures 16a to 16c An example of CFO correction using response time information is described.

[0402] Fig.16a A case is shown in which an initiator anchor according to an embodiment of the present disclosure sends a first UWB message and a responder anchor sends a second UWB message in response to the first UWB message.

[0403] refer to Figures 16a to 16c , each responder anchor (Rk, Rn) receiving the first UWB message (polling DTM, first DTM) from the initiator anchor I can send a second UWB message (response DTM, second DTM) in its allocated ranging time slot obtained based on the first UWB message.

[0404] As shown in the figure, since the distance between the initiator anchor I and the Rk responder anchor is different from the distance between the initiator anchor I and the Rn responder anchor, the time (propagation time) for the first DTM to arrive at the two responder anchors can be different. The arrival time can be expressed as tprop(I, Rk) and tprop(I, Rn), respectively.

[0405] -tprop(I, Rk): the time when the first DTM of the initiator anchor (I) arrives at the Rk anchor

[0406] -tprop(I, Rn): the time when the first DTM of the initiator anchor (I) arrives at the Rn anchor

[0407] Taking this into consideration, the following embodiment relates to a method for synchronizing the start time of the first ranging slot of a ranging round between the responder anchor and the initiator anchor. <Embodiment for synchronizing the start time of the first ranging slot of a ranging round>

[0408] First embodiment: A method in which the responder DT-anchor (Rk, Rn) adjusts the start time of the ranging slot 0 by subtracting tprop from the reception time of the polling DTM (first DTM) sent by the initiator DT-anchor (I).

[0409] However, even when the responder anchor adjusts the start time of ranging slot 0 according to the above method, each anchor may determine the start time of ranging slot 1 and ranging slot 2 differently due to the clock drift effect of the crystal oscillator of the UWB chip (UWBS) in the two anchors.

[0410] Fig.16b : is a diagram showing an equation for estimating a response time of another responder anchor previously responded to a specific responder anchor at a UE side according to an embodiment of the present disclosure.

[0411] Equation 1 below is an equivalent expression of two equations that enable estimation of the start time of ranging slot 2 (i.e., the time when the Rn responder anchor sends the second DTM) in the UE when the initiator anchor sends the first UWB message (first DTM, polling DTM) in ranging slot 0 and the Rn responder anchor sends its second UWB message (second DTM, response DTM) in ranging slot 2.

[0412]

[0413] The left term of equation 1 above represents t prop (I, R n ) and t reply (I, R n ), t prop (I, R n ) is the time taken for the first DTM sent by the initiator anchor to reach the Rn responder anchor, t reply (I, R n ) is the answer time that the responder anchor will include in its second DTM. This can be expressed as the first DTM sent by the initiator anchor and the second DTM sent by R n The transmission time difference between the second DTM sent by the responder anchor, or theoretically represents the time difference between two ranging slots.

[0414] The right side of equation 1 above is t prop (I, R k ) and t reply (I, R k ) and t prop (R k , R n ) and t reply (R k ,R n ), tprop (I, R k ) is the first DTM sent by the initiator anchor to reach R k The time spent by the responder anchor, t reply (I, R k ) is the answer time that the responder anchor will include in its second DTM, t prop (R k , R n ) is R k The second DTM of the responder anchor arrives at R n The time spent by the responder anchor, t reply (R k , R n ) can be R n Responder anchors can respond to R k The time when the responder anchor sends the second DTM. In this case, since t reply (I, R k ) is composed of R k The responder anchor calculates the value, so it is necessary to multiply it by R k Responder Anchor and R n The CFO ratio of the clock frequency offset between the responder and the anchor (R k , R n ), and converts it to a value measured by the clock of the Rn responder anchor so that Equation 1 and Equation 2 above can be considered the same.

[0415] By moving the terms in the above equation, we can calculate t reply (R k , R n ), which may be the time when the Rn responder anchor may respond to the second DTM sent by the Rk responder anchor.

[0416] In an embodiment, t reply (R k , R n ) may be a value that the responder anchors can directly calculate the reply times for other responder anchors that transmitted in the ranging slots before their responder anchors and include in the second DTM they transmit. However, in this case, since additional implementation is required for the responder anchors for this calculation, the implementation complexity for the responder anchors may increase.

[0417] In an embodiment, t may be estimated by the UE (tag) reply (R k , R n ). In this case, no additional implementation is required in the responder anchor for this calculation, thereby not increasing the implementation complexity of the responder anchor.

[0418]

[0419] t as the propagation time between anchors prop It can be obtained by obtaining the distance from the coordinates of the two anchors and dividing the distance by the speed of light, or by using the distance between the anchors if the first DTM or the second DTM includes the distance. reply (I, R n ) and t reply (I, R k ) are values ​​included in the second DTM, so these values ​​can be obtained by receiving the second DTM. CFO (R k , R n ) can use CFO (I, R n ) and CFO (I, R k ) is used to obtain the clock drift offset between the two responder anchors, and these two values ​​are also included in the second DTM. In addition, CFO (R k , R n ) can be used by the UE through the R n The CFO (terminal, R n ) and from R k The CFO (terminal, R k ) to obtain.

[0420] Fig.16c The present invention is used for UE to utilize Fig.16b The estimated answer time between responder anchors provides additional insight into the TDoA equation.

[0421] refer to Fig.16c , the UE (tag) can obtain the TDoA of the second message from the R1 responder anchor and the R2 responder anchor as follows.

[0422]

[0423] Table 3

[0424] According to Equation 5 above, the TDoA for two arbitrary responder anchors can be obtained. In this case, it can be obtained by Fig.16b Equation 2 is used to calculate the response time of the responder anchor of the second DTM for another responder anchor.

[0425] Meanwhile, in the conventional DL-TDoA positioning scheme, the UE can obtain TDoA for only the signal of the initiator anchor and the signal of another responder anchor. Fig. 9 and Fig.10 During the ranging process, the TDoA for two arbitrary responder anchors can also be calculated by referring to Fig.16c The UE can obtain the position by using more TDoA guarantees, thereby increasing the chance of successful positioning.

[0426] Fig.17 A payment processing method using UWB according to an embodiment of the present disclosure is shown.

[0427] Fig.17 Payment processing methods using UWB can be Figure 8 An example of a payment processing method using UWB. Fig.17 In, omitted Figure 8 of the above description.

[0428] refer to Fig.17 , the payment processing method using UWB may include a first operation 1710, a second operation 1720, a third operation 1730, and / or a fourth operation 1740. However, according to the implementation, some steps (or some operations in the steps) may be omitted, multiple steps may be combined into one step, or additional steps may be further performed. In addition, multiple steps (or operations in each step) may be performed in an order different from the order shown.

[0429] First Operation 1710

[0430] The first step is an initiation step and may include an operation in which the first payment terminal 1701 sends a BLE advertising packet. When the BLE advertising packet is received, the UE 1703 may start a UWB-enabled payment application.

[0431] Second Operation 1720

[0432] The second step may include performing UWB DL-TDoA / UWB contention-based ranging (e.g., Figure 8 811 / 813) and / or perform AoA measurements (e.g. Figure 8 of 813).

[0433] In the second step, the payment terminals 1701 and 1702 may send UWB messages for UWB DL-TDoA and UWB contention-based ranging. As an embodiment, the UWB messages for UWB DL-TDoA and UWB contention-based ranging may include payment terminal information (eg, PoS information).

[0434] In step 2, UE 1703 may receive a UWB message, perform DL-TDoA based positioning based on the received UWB message, and perform AoA measurement. Through the AoA measurement, UE 1703 may identify the user's intention.

[0435] Third Operation 1730

[0436] The third step may be a step for determining a payment terminal.

[0437] In the third step, the UE 1703 may determine the payment terminal 1702 and send a response message for UWB contention-based ranging to the determined payment terminal 1702. As an embodiment, the response message may include information about the UE 1703.

[0438] In the third step, the payment terminal 1702 may perform SS-TWR-based ranging based on the response message of the UE 1703. The payment terminal 1702 may send a matching result to the UE 1703 based on the ranging.

[0439] Fourth Operation 1740

[0440] The fourth step may be a step for protecting and transmitting payment related data between the payment terminal 1702 and the UE 1703 matched / connected through the third operation 1730 .

[0441] In a fourth step, a secure channel may be established between the payment terminal 1702 and the UE 1703 .

[0442] In a fourth step, secure ranging may be performed between the payment terminal 1702 and the UE 1703 .

[0443] In the fourth step, UE 1703 may identify the user intention based on the result of the safety ranging.

[0444] In a fourth step, the payment terminal 1702 and the UE 1703 may perform a secure payment transaction through a payment network 1704 that provides online payment and backend communications.

[0445] Fig.18 The structure of a first UWB device according to an embodiment of the present disclosure is shown.

[0446] exist Fig.18 In an embodiment of the present invention, the first UWB device may correspond to Figure 1 The UWB device may include a UWB device, or may be an electronic device that may include a portion of a UWB device. The first UWB device may be, for example, an anchor (eg, an initiator anchor / responder anchor) for a UWB-based payment service.

[0447] refer to Fig.18 , the first UWB device may include a transceiver 1810, a controller 1820, and a storage unit 1830. In the present disclosure, the controller may be defined as a circuit or an application specific integrated circuit or at least one processor.

[0448] The transceiver 1810 may transmit and receive a signal to and from another entity.

[0449] According to an embodiment, the controller 1820 may control the overall operation of the electronic device. For example, the controller 1820 may control the inter-block signal flow to perform the operation according to the above flowchart. Specifically, the controller 1820 may control, for example, the above reference Figures 1 to 4 , Figure 5a , Figure 5b , Figure 6 , Figure 7a , Figure 7b , Figures 8 to 11 , Fig.12a , Figure 12b , Fig.13a , Fig.13b , Fig.14 , Fig.15 , Figures 16a to 16c and Fig.17 Operation of a first UWB device (eg, operation of an anchor for a UWB-based payment service) is described.

[0450] The storage unit 1830 may store at least one of information transmitted / received via the transceiver 1810 and information generated via the controller 1820. For example, the storage unit 1830 may store the above-referenced Figures 1 to 4 , Figure 5a , Figure 5b , Figure 6 , Figure 7a , Figure 7b , Figures 8 to 11 , Fig.12a , Figure 12b , Fig.13a , Fig.13b , Fig.14 , Fig.15 , Figures 16a to 16c and Fig.17 Describe the information and data required for the method.

[0451] Fig.19 The structure of a second UWB device according to an embodiment of the present disclosure is shown.

[0452] exist Fig.19 In an embodiment of the present invention, the first UWB device may correspond to Figure 2The UWB device of the present invention may include a UWB device, or may be an electronic device that may include a part of a UWB device. The second UWB device may be, for example, a UE for a UWB-based payment service.

[0453] refer to Fig.19 , the second UWB device may include a transceiver 1910, a controller 1920, and a storage unit 1930. In the present disclosure, the controller may be defined as a circuit or an application specific integrated circuit or at least one processor.

[0454] The transceiver 1910 can send signals to another entity and receive signals from another entity. The controller 1920 can be implemented as one or more of various processing devices, such as a coprocessor, a microprocessor, a digital signal processor (DSP), a processing circuit with or without an accompanying DSP, or various other processing devices (including a microcontroller unit (MCU), a hardware accelerator, a dedicated computer chip, etc.). The storage unit 1930 may include one or more volatile or non-volatile memories or a combination thereof. For example, the storage unit 1930 can be implemented as a semiconductor memory, such as a flash memory, a mask read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), a random access memory (RAM), etc.

[0455] According to an embodiment, the controller 1920 may control the overall operation of the electronic device. For example, the controller 1920 may control the inter-block signal flow to perform the operation according to the above flowchart. Specifically, the controller 1920 may control, for example, the above reference Figures 1 to 4 , Figure 5a , Figure 5b , Figure 6 , Figure 7a , Figure 7b , Figures 8 to 11 , Fig.12a , Figure 12b , Fig.13a , Fig.13b , Fig.14 , Fig.15 , Figures 16a to 16c and Fig.17 The operation of a second UWB device (eg, operation of a UE for a UWB-based payment service) is described.

[0456] As an embodiment, the controller 1920 may be configured to receive a first UWB message initiating a ranging process from an initiator anchor, receive a plurality of second UWB messages sent in response to the first UWB message from a plurality of responder anchors, receive a third UWB message sent in response to the second UWB message from the initiator anchor, and receive a plurality of fourth UWB messages sent in response to the third UWB message from a plurality of responder anchors.

[0457] As an implementation, the controller 1920 may perform DL-TDoA-based positioning based on the sliced ​​transmission of the first UWB message, the second UWB message, the third UWB message, and the fourth UWB message.

[0458] As an embodiment, the first UWB message may include first information for DL-TDoA and second information for contention-based ranging.

[0459] As an embodiment, the first information for DL-TDoA may include first scheduling information and second scheduling information for each of the plurality of responder anchors. The first scheduling information may specify a ranging time slot in which the corresponding responder anchor sends its second UWB message. The second scheduling information may specify a ranging time slot in which the corresponding responder anchor sends its fourth UWB message.

[0460] As an embodiment, the second information for contention-based ranging may include information specifying a size of a contention access period.

[0461] As an embodiment, the controller may be further configured to select an anchor from the initiator anchor and the plurality of responder anchors according to the result of the DL-TDoA based positioning.

[0462] As an embodiment, the controller may be further configured to send a ranging response message for SS-TWR to an anchor selected from the initiator anchor and the plurality of responder anchors in any time slot within the contention access period.

[0463] As an embodiment, the SS-TWR may include information for mutual authentication between the UWB device and the selected anchor.

[0464] As an embodiment, the fourth UWB message may include third information for DL-TDoA and fourth information for contention-based ranging. The third information of DL-TDoA may include first response time information specifying a response time between a reception time of the third UWB message and a transmission time of the fourth UWB message, and second response time information specifying a response time between a reception time of a second UWB message from another responder anchor and a transmission time of the fourth UWB message.

[0465] The storage unit 1930 may store at least one of information transmitted / received via the transceiver 1910 and information generated via the controller 1920. For example, the storage unit 1930 may store the above-mentioned Figures 1 to 4 , Figure 5a , Figure 5b , Figure 6 , Figure 7a , Figure 7b , Figures 8 to 11 , Fig.12a, Figure 12b , Fig.13a , Fig.13b , Fig.14 , Fig.15 , Figures 16a to 16c and Fig.17 Describe the information and data required for the method.

[0466] In the above specific embodiments, the components included in the present disclosure are expressed in singular or plural forms according to the specific embodiments proposed. However, the singular or plural forms are selected to be sufficient for the content proposed for ease of description, and the present disclosure is not limited to singular or plural components.

[0467] While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents.

Claims

1. A method performed by an ultra-wideband (UWB) device, the method comprising: receiving a first UWB message initiating a ranging process from an initiator anchor; receiving, from a plurality of responder anchors, a plurality of second UWB messages sent in response to the first UWB message; receiving, from the initiator anchor, a third UWB message sent in response to the second UWB message; receiving, from the plurality of responder anchors, a plurality of fourth UWB messages sent in response to the third UWB message; and Downlink time difference of arrival DL-TDoA based positioning is performed based on the first UWB message, the second UWB message, the third UWB message, and the fourth UWB message.

2. The method according to claim 1, in, The first UWB message includes first information for DL-TDoA and second information for contention-based ranging.

3. The method according to claim 2, in, The first information for DL-TDOA includes first scheduling information and second scheduling information for each of the plurality of responder anchors, wherein the first scheduling information specifies a ranging time slot used by the corresponding responder anchor to send its second UWB message, and The second scheduling information specifies a ranging time slot used by the corresponding responder anchor to send its fourth UWB message.

4. The method according to claim 2, in, The second information for contention-based ranging includes information specifying a size of a contention access period.

5. The method according to claim 4, further comprising: Based on the result of the DL-TDoA based positioning, one anchor is selected from the initiator anchor and the plurality of responder anchors.

6. The method according to claim 5, further comprising: sending a ranging response message for single-sided two-way ranging SS-TWR to an anchor selected from the initiator anchor and the plurality of responder anchors in a time slot within the contention access period, The ranging response message for the SS-TWR includes information for mutual authentication between the UWB device and the selected anchor.

7. The method according to claim 1, in, The fourth UWB message includes third information for DL-TDoA and fourth information for contention-based ranging, and Wherein, the third information used for DL-TDoA includes first response time information and second response time information, the first response time information specifies the response time between the reception time of the third UWB message and the sending time of the fourth UWB message, and the second response time information specifies the response time between the reception time of the second UWB message from another responder anchor and the sending time of the fourth UWB message.

8. An ultra-wideband (UWB) device, comprising: Transceiver; as well as A controller, coupled to the transceiver and configured to control: receiving a first UWB message initiating a ranging process from an initiator anchor, receiving a plurality of second UWB messages sent in response to the first UWB message from a plurality of responder anchors, receiving, from the initiator anchor, a third UWB message sent in response to the second UWB message, receiving a plurality of fourth UWB messages sent in response to the third UWB message from the plurality of responder anchors, and Downlink time difference of arrival DL-TDoA based positioning is performed based on the first UWB message, the second UWB message, the third UWB message, and the fourth UWB message.

9. The UWB device according to claim 8, in, The first UWB message includes first information for DL-TDoA and second information for contention-based ranging.

10. The UWB device according to claim 9, in, The first information for DL-TDoA includes first scheduling information and second scheduling information for each of the plurality of responder anchors, wherein the first scheduling information specifies a ranging time slot used by the corresponding responder anchor to send its second UWB message, and The second scheduling information specifies a ranging time slot used by the corresponding responder anchor to send its fourth UWB message.

11. The UWB device according to claim 9, in, The second information for contention-based ranging includes information specifying a size of a contention access period.

12. The UWB device according to claim 11, in, The controller is configured to select an anchor from among the initiator anchor and the plurality of responder anchors based on a result of the DL-TDoA based positioning.

13. The UWB device according to claim 12, in, The controller is configured to: send a ranging response message for SS-TWR to an anchor selected from the initiator anchor and the plurality of responder anchors in a time slot within the contention access period, The ranging response message for the SS-TWR includes information for mutual authentication between the UWB device and the selected anchor.

14. The UWB device according to claim 8, in, The fourth UWB message includes third information for DL-TDoA and fourth information for contention-based ranging, and Wherein, the third information used for DL-TDoA includes first response time information and second response time information, the first response time information specifies the response time between the reception time of the third UWB message and the sending time of the fourth UWB message, and the second response time information specifies the response time between the reception time of the second UWB message from another responder anchor and the sending time of the fourth UWB message.

15. A non-transitory computer-readable storage medium having an executable program stored thereon, wherein: The program instructs the microprocessor of the ultra-wideband UWB device to perform the following steps: receiving a first UWB message initiating a ranging process from an initiator anchor; receiving, from a plurality of responder anchors, a plurality of second UWB messages sent in response to the first UWB message; receiving, from the initiator anchor, a third UWB message sent in response to the second UWB message; receiving, from the plurality of responder anchors, a plurality of fourth UWB messages sent in response to the third UWB message; and Downlink time difference of arrival DL-TDoA based positioning is performed based on the first UWB message, the second UWB message, the third UWB message, and the fourth UWB message.

Images