Method and device for ultra-wide band communication-based transaction

Abstract

A method performed by a first ultra-wide band (UWB) device according to an embodiment of the present disclosure may comprise the operations of: estimating the location of the first UWB device on the basis of DL-TDoA; transmitting a transaction initiation message to a second UWB device through UWB communication when, according to the location estimation, the first UWB device enters a transaction area set in the second UWB device; receiving a transaction request message from the second UWB device through the UWB communication and transmitting a transaction response message corresponding to the transaction request message to the second UWB device through the UWB communication; and performing DS-TWR to determine whether the first UWB device moves out of the transaction area when the transaction between the first UWB device and the second UWB device is completed.

Description

Method and device for ultra-wideband communication-based transactions

[0001] The present disclosure relates to UWB communication, and more particularly, to a method and device for UWB communication-based transactions.

[0002] The Internet is evolving from a human-centric network where humans create and consume information to an Internet of Things (IoT) network where information is exchanged and processed between distributed components such as objects. The Internet of Everything (IoE) technology, which combines IoT technology with big data processing technology through connections to cloud servers, is also emerging. To implement the IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required. Recently, technologies such as sensor networks for connecting objects, Machine-to-Machine (M2M) communication, and Machine-Type Communication (MTC) are being researched.

[0003] In an IoT environment, intelligent IT (Internet Technology) services can be provided that collect and analyze data generated from connected objects, creating new value in human life. IoT, through the convergence and integration of existing IT (information technology) technologies with various industries, can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] As wireless communication systems advance, the ability to provide a variety of services increases, leading to a growing demand for effective solutions. For example, ranging technology can be used to measure the distance between electronic devices using Ultra Wide Band (UWB). UWB is a wireless communication technology that utilizes a very wide frequency band, from baseband to several gigahertz, without the use of a radio carrier.

[0005] The present disclosure proposes a method for a user terminal to perform payment in a gate system using UWB communication.

[0006] According to one embodiment of the present disclosure, a method of a first UWB (ultra wide band) device may include: estimating a location of the first UWB device based on downlink-TDoA (DL-TDoA); transmitting a transaction initiation message to a second UWB device via UWB communication when the first UWB device enters a transaction area set to a second UWB device based on the location estimation; receiving a transaction request message from the second UWB device via UWB communication, and transmitting a transaction response message corresponding to the transaction request message to the second UWB device via UWB communication; and performing double-sided two-way ranging (DS-TWR) to determine whether the first UWB device moves outside the transaction area when a transaction between the first UWB device and the second UWB device is completed.

[0007] According to one embodiment of the present disclosure, a method of a second UWB (ultra wide band) device may include: when a first UWB device enters a transaction area set for the second UWB device based on a location estimation based on downlink-TDoA (DL-TDoA), receiving a transaction initiation message from the first UWB device via UWB communication; transmitting a transaction request message to the first UWB device via UWB communication, and receiving a transaction response message corresponding to the transaction request message from the first UWB device via UWB communication; and performing double-sided two-way ranging (DS-TWR) to determine whether the first UWB device moves outside the transaction area when a transaction between the first UWB device and the second UWB device is completed.

[0008] According to one embodiment of the present disclosure, a first UWB (ultra wide band) device includes a transceiver; and a control unit. The control unit estimates a location of the first UWB device based on downlink-TDoA (DL-TDoA), and when the first UWB device enters a transaction area set to a second UWB device based on the location estimation, transmits a transaction initiation message to the second UWB device via UWB communication, receives a transaction request message from the second UWB device via UWB communication, transmits a transaction response message corresponding to the transaction request message to the second UWB device via UWB communication, and when a transaction between the first UWB device and the second UWB device is completed, performs DS-TWR (Double-sided two-way ranging) to determine whether the first UWB device moves outside the transaction area.

[0009] According to one embodiment of the present disclosure, a second UWB (ultra wide band) device includes a transceiver; and a control unit. When a first UWB device enters a transaction area set for the second UWB device based on a location estimation based on downlink-TDoA (DL-TDoA), the control unit may receive a transaction initiation message from the first UWB device through UWB communication, transmit a transaction request message to the first UWB device through UWB communication, receive a transaction response message corresponding to the transaction request message from the first UWB device through UWB communication, and when a transaction between the first UWB device and the second UWB device is completed, perform DS-TWR (Double-sided two-way ranging) to determine whether the first UWB device moves outside the transaction area.

[0010] Through the method for providing the UWB service of the present disclosure, a user terminal can perform efficient gate payment using UWB communication.

[0011] Figure 1 illustrates an exemplary architecture of a UWB device.

[0012] Figure 2 illustrates an exemplary configuration of a communication system including a UWB device.

[0013] Figure 3 shows an exemplary structure of a frame used for UWB communication.

[0014] Figure 4 illustrates how two UWB devices perform UWB communication.

[0015] Figure 5 illustrates how two UWB devices perform UWB ranging.

[0016] Figure 6 shows the structure of ranging blocks and rounds used for UWB ranging.

[0017] FIG. 7 illustrates an exemplary architecture of a system providing a UWB-based gate service according to one embodiment of the present disclosure.

[0018] FIG. 8 illustrates an exemplary operation scenario of a gate system according to one embodiment of the present disclosure.

[0019] FIG. 9 illustrates a gate service procedure of a gate system according to one embodiment of the present disclosure.

[0020] FIG. 10 illustrates an exemplary operation scenario of a gate system according to one embodiment of the present disclosure.

[0021] FIG. 11 is a flowchart illustrating a transaction performed in a gate system according to one embodiment of the present disclosure.

[0022] FIG. 12 illustrates an exemplary operating scenario of a unidirectional gate system according to one embodiment of the present disclosure.

[0023] FIG. 13 illustrates an exemplary operation scenario of a bidirectional gate system according to one embodiment of the present disclosure.

[0024] FIG. 14 is a diagram illustrating an example of a time interval during which a transaction is performed in a gate system according to one embodiment of the present disclosure.

[0025] FIG. 15 illustrates an exemplary operation scenario of a gate system according to one embodiment of the present disclosure.

[0026] FIG. 16 is a diagram illustrating an example of a time interval during which a transaction is performed in a gate system according to one embodiment of the present disclosure.

[0027] FIG. 17 is a diagram for explaining the point in time at which Free Pass Permission (FPP) is granted in a gate system according to one embodiment of the present disclosure.

[0028] FIG. 18 is a diagram for explaining the point in time at which FPP is recovered in a gate system according to one embodiment of the present disclosure.

[0029] FIGS. 19a, 19b, and 19c illustrate examples of FPP being used in a gate system according to one embodiment of the present disclosure.

[0030] FIG. 20 is a diagram for explaining messages for determining the authenticity of FPP in a gate system according to one embodiment of the present disclosure.

[0031] FIG. 21 is a diagram for explaining messages for determining the authenticity of FPP in a gate system according to one embodiment of the present disclosure.

[0032] FIG. 22 is a diagram illustrating the structure of a first electronic device according to one embodiment of the present disclosure.

[0033] FIG. 23 is a diagram illustrating the structure of a second electronic device according to one embodiment of the present disclosure.

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

[0035] In describing the embodiments, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to more clearly convey the gist of the present disclosure without obscuring it by omitting unnecessary explanations.

[0036] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0037] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. The embodiments of the present disclosure are provided only to make the present disclosure complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

[0038] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, so that the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also be able to provide steps for performing the functions described in the flowchart block(s).

[0039] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0040] Here, the term '~ unit' used in the present embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Accordingly, according to some embodiments, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within the device or secure multimedia card. Furthermore, according to some embodiments, the '~parts' may include one or more processors.

[0041] The term 'terminal' or 'device' used herein may refer to a mobile station (MS), user equipment (UE), user terminal (UT), wireless terminal, access terminal (AT), terminal, subscriber unit (SS), subscriber station (SS), wireless device, wireless communication device, wireless transmit / receive unit (WTRU), mobile node, mobile, or other terms. Various embodiments of the terminal may include a cellular telephone, a smart phone having a wireless communication function, a personal digital assistant (PDA) having a wireless communication function, a wireless modem, a portable computer having a wireless communication function, a photographing device such as a digital camera having a wireless communication function, a gaming device having a wireless communication function, a music storage and playback home appliance having a wireless communication function, an internet home appliance capable of wireless internet access and browsing, as well as portable units or terminals integrating combinations of such functions. In addition, the terminal may include, but is not limited to, an M2M (Machine to Machine) terminal, an MTC (Machine Type Communication) terminal / device. In this specification, the terminal may also be referred to as an electronic device or simply a device.

[0042] The operating principles of the present disclosure are described in detail below with reference to the attached drawings. In the following description of the present disclosure, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the overall content of this specification.

[0043] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. While the embodiments of the present disclosure will be described below using a communication system utilizing UWB as an example, the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or characteristics. For example, these may include communication systems utilizing Bluetooth or Zigbee. Accordingly, the embodiments of the present disclosure may be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure.

[0044] Additionally, when describing the present disclosure, detailed descriptions of related functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the contents of this specification.

[0045] Generally, wireless sensor network technologies are broadly categorized into Wireless Local Area Network (WLAN) and Wireless Personal Area Network (WPAN) technologies based on their sensing range. WLAN is a technology based on IEEE 802.11 that allows access to a backbone network within a radius of approximately 100 meters. WPAN, on the other hand, is a technology based on IEEE 802.15, and includes technologies such as Bluetooth, ZigBee, and ultra-wideband (UWB). A wireless network implementing these wireless network technologies may consist of multiple electronic devices.

[0046] UWB can refer to a short-range, high-speed wireless communication technology that utilizes a wide frequency band exceeding several GHz in baseband mode, low spectral density, and short pulse widths (1 to 4 nanoseconds). UWB can also refer to the band itself in which UWB communications are applied. UWB enables secure and accurate ranging between devices. This allows for relative positioning based on the distance between two devices, or precise positioning of a device based on the distance from fixed devices (whose locations are known).

[0047] Certain terms used in the following description are provided to aid in understanding the present disclosure, and the use of such specific terms may be changed to other forms without departing from the technical spirit of the present disclosure.

[0048] An "Application Dedicated File (ADF)" may be, for example, a data structure within an Application Data Structure that can host an application or application specific data.

[0049] "Application Protocol Data Unit (APDU)" may be a command and response used when communicating with the Application Data Structure within a UWB device.

[0050] The "application specific data" may be a file structure having a root level and an application level, for example, containing UWB control information and UWB session data required for a UWB session.

[0051] A "Controller" may be a Ranging Device that defines and controls Ranging Control Messages (RCM) (or control messages).

[0052] A "Controllee" may be a Ranging Device that utilizes the ranging parameters within the RCM (or control message) received from the Controller.

[0053] Unlike "Static STS," "Dynamic STS (Scrambled Timestamp Sequence) mode" can be an operating mode in which STS is not repeated during a ranging session. In this mode, STS is managed by the ranging device, and the ranging session key that generates the STS can be managed by the Secure Component.

[0054] An "Applet" may be, for example, an applet running on a Secure Component that includes UWB parameters and service data. In the present disclosure, the Applet may be a FiRa Applet defined by FiRa.

[0055] A "Ranging Device" may be a device capable of performing UWB ranging. In the present disclosure, the Ranging Device may be an Enhanced Ranging Device (ERDEV) defined in IEEE 802.15.4z or a FiRa Device defined by FiRa. The Ranging Device may be referred to as a UWB device.

[0056] A "UWB-enabled Application" may be an application for UWB services. For example, a UWB-enabled Application may be an application that utilizes a framework API for configuring an OOB Connector, a Secure Service, and / or a UWB service for a UWB session. In the present disclosure, a "UWB-enabled Application" may be abbreviated as an application or a UWB application. A UWB-enabled Application may be a FiRa-enabled Application defined by FiRa.

[0057] A "Framework" may be a component that provides access to a Profile, individual UWB settings, and / or notifications. A "Framework" may be a collection of logical software components, including, for example, a Profile Manager, an OOB Connector, a Secure Service, and / or a UWB Service. In the present disclosure, the Framework may be a FiRa Framework defined by FiRa.

[0058] An "OOB Connector" may be a software component for establishing an out-of-band (OOB) connection (e.g., a BLE connection) between Ranging Devices. In the present disclosure, the OOB Connector may be a FiRa OOB Connector defined by FiRa.

[0059] A "Profile" may be a predefined set of UWB and OOB configuration parameters. In the present disclosure, the Profile may be a FiRa Profile defined by FiRa.

[0060] A "Profile Manager" may be a software component that implements a profile available to a Ranging Device. In the present disclosure, the Profile Manager may be a FiRa Profile Manager defined by FiRa.

[0061] A "Service" could be an implementation of a use case that provides a service to the end-user.

[0062] A "Smart Ranging Device" may be a Ranging Device capable of implementing an optional Framework API. In the present disclosure, the Smart Ranging Device may be a FiRa Smart Device defined by FiRa.

[0063] A "Global Dedicated File (GDF)" may be the root level of application specific data containing the data required to establish a USB session.

[0064] The "Framework API" may be an API used by a UWB-enabled Application to communicate with the Framework.

[0065] An "Initiator" may be a Ranging Device that initiates a ranging exchange.

[0066] "Object Identifier (OID)" can be an identifier of ADF within the application data structure.

[0067] "Out-Of-Band (OOB)" may be data communication that does not use UWB as the underlying wireless technology.

[0068] "Ranging Data Set (RDS)" may be data (e.g., UWB session key, session ID, etc.) required to establish a UWB session whose confidentiality, authenticity, and integrity need to be protected.

[0069] A "Responder" may be a Ranging Device that responds to an Initiator in a ranging exchange.

[0070] "STS" may be a ciphered sequence to enhance the integrity and accuracy of ranging measurement timestamps. The STS may be generated from a ranging session key.

[0071] A "Secure Channel" may be a data channel that prevents overhearing and tampering.

[0072] A "Secure Component" may be an entity (e.g., an SE or TEE) with a defined security level that interfaces with the UWBS for the purpose of providing RDS to the UWBS, for example, when dynamic STS is used.

[0073] A "Secure Element (SE)" may be a tamper-resistant secure hardware component that can be used as a Secure Component within a Ranging Device.

[0074] "Secure Ranging" may be ranging based on STS generated through strong cryptographic operations.

[0075] A "Secure Service" may be a software component for interfacing with a Secure Component, such as a Secure Element or a Trusted Execution Environment (TEE).

[0076] A "Service Applet" may be an applet on a Secure Component that handles service-specific transactions.

[0077] "Service Data" may be data defined by the Service Provider that needs to be passed between two ranging devices to implement the service.

[0078] A "Service Provider" may be an entity that defines and provides the hardware and software required to provide a specific service to an end-user.

[0079] "Static STS mode" is an operating mode in which STS repeats during a session and does not need to be managed by the Secure Component.

[0080] The "Secure UWB Service (SUS) Applet" may be an applet on the SE that communicates with other ranging devices to retrieve the data necessary to enable a secure UWB session. The SUS Applet may also forward this data (information) to the UWBS.

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

[0082] A "UWB Session" can be the period from when the Controller and Controllee start communicating via UWB until they stop communicating. A UWB Session can include ranging, data transfer, or both ranging and data transfer.

[0083] "UWB Session ID" may be an ID (e.g., a 32-bit integer) that identifies a UWB Session shared between the controller and the controller.

[0084] The "UWB Session Key" may be a key used to protect a UWB session. The UWB Session Key may be used to generate an STS. In the present disclosure, the UWB Session Key may be a UWB Ranging Session Key (URSK), and may be abbreviated as a session key.

[0085] The "UWB Subsystem (UWBS)" may be a hardware component implementing the UWB PHY and MAC specifications. The UWBS may have an interface to the Framework and an interface to the Secure Component for discovering the RDS. In the present disclosure, the UWB PHY and MAC specifications may be, for example, the FiRa PHY and FiRa MAC specifications defined by FiRa, which references IEEE 802.15.4 / 4z.

[0086] In addition, when explaining the present disclosure, if it is determined that a specific description of a related public notice function or configuration may unnecessarily obscure the gist of the present disclosure, the detailed description is omitted.

[0087] Various embodiments of the present disclosure are described below with reference to the attached drawings.

[0088] Figure 1 illustrates an exemplary architecture of a UWB device.

[0089] The UWB device (electronic device) of FIG. 1 may be a Ranging Device that supports UWB ranging (e.g., UWB secure ranging). In one embodiment, the Ranging Device may be an Enhanced Ranging Device (ERDEV) defined in IEEE 802.15.4z or a FiRa Device defined by FiRa.

[0090] In the embodiment of FIG. 1, a UWB device can interact with another UWB device through a UWB session.

[0091] Additionally, the UWB device may implement a first interface (Interface #1), which is an interface between a UWB-enabled application and the Framework, wherein the first interface allows the UWB-enabled application on the UWB device to use the UWB capabilities of the UWB device in a predetermined manner. In one embodiment, the first interface may be, but is not limited to, a Framework API or a proprietary interface.

[0092] Additionally, the UWB device may implement a second interface (Interface #2), which is an interface between the Framework and the UWB subsystem (UWBS). In one embodiment, the second interface may be, but is not limited to, the UWB Command Interface (UCI) or a proprietary interface.

[0093] Referring to FIG. 1, a UWB device may include a UWB-enabled Application, Framework, and / or UWBS 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 (e.g., a security layer) may be included.

[0094] A UWB-enabled application can use the first interface to trigger the establishment of a UWB session by a UWBS. Furthermore, the UWB-enabled application can use one of the predefined profiles. For example, the UWB-enabled application can use one of the profiles defined in FiRa or a custom profile. The UWB-enabled application can use the first interface to handle relevant events such as service discovery, ranging notifications, and / or error conditions.

[0095] The Framework may provide access to Profiles, individual UWB configurations, and / or notifications. The Framework may be a collection of software components. As described above, a UWB-enabled Application may interface with the Framework via a first interface, and the Framework may interface with the UWB via a second interface. The software components of the Framework may include, for example, a Profile Manager, an OOB Connector, a Secure Service, and / or a UWB Service.

[0096] The Profile Manager may be responsible for managing profiles available on a UWB device. 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 is used, UWB / OOB configuration parameters, parameters indicating whether the use of a particular security component is mandatory, and / or parameters related to the file structure of the ADF.

[0097] The OOB Connector can be used to establish an OOB connection between UWB devices. The OOB Connector can handle the OOB phase, including the discovery phase and the connection phase. The OOB phase is described below with reference to FIG. 4.

[0098] A Secure Service may interface with a Secure Component such as an SE or TEE.

[0099] The UWB Service can manage UWBS. By implementing a second interface, the UWB Service can provide access to UWBS from the Profile Manager.

[0100] A UWBS may be a hardware component that includes a UWB MAC Layer and a UWB Physical Layer. It can perform UWB session management and communicate with UWBSs of other UWB devices. It can interface with the Framework through a second interface and obtain RDS from the Secure Component.

[0101] Figure 2 illustrates an exemplary configuration of a communication system including a UWB device.

[0102] Referring to FIG. 2, a communication system includes a first UWB device and a second UWB device. In one embodiment, the first UWB device and the second UWB device may be, for example, the UWB device of FIG. 1 or an electronic device including the UWB device of FIG. 1.

[0103] A first UWB device may host one or more UWB-enabled Applications that can be installed, for example, by a user (e.g., a mobile phone). These may be based on, for example, a Framework API. A second UWB device may not provide a Framework API, but may, for example, utilize a proprietary interface to implement a specific UWB-enabled Application. Alternatively, and not as depicted, depending on the embodiment, both the first UWB device and the second UWB device may be Ranging Devices utilizing the Framework API, or both the first UWB device and the second UWB device may be Ranging Devices utilizing a proprietary interface.

[0104] The first UWB device and the second UWB device may include a UWB-enabled Application Layer, a Framework, an OOB component, a Secure Component, and / or a UWBS. Meanwhile, in the present disclosure, the OOB component and / or the Secure Component are optional components and may not be included in the UWB device depending on the embodiment.

[0105] The Framework may provide access to profiles, individual UWB settings, and / or notifications. The Framework is a collection of software components, including, for example, a Profile Manager, an OOB Connector, a Secure Service, and / or a UWB Service. For a description of each component, see the preceding description.

[0106] The OOB component may be a hardware component including a MAC Layer and / or Physical Layer for OOB communication (e.g., BLE communication). The OOB component may communicate with an OOB component of another device. In one embodiment, the first UWB device and the second UWB device may create an OOB connection (channel) using the OOB component and exchange parameters for establishing a UWB session through the OOB channel. In the present disclosure, the OOB component may be referred to as an OOB subsystem.

[0107] The UWBS may be a hardware component including a UWB MAC Layer and a UWB Physical Layer. It may perform UWB session management and communicate with the UWBS of another UWB device. In one embodiment, the first UWB device and the second UWB device may perform UWB ranging and service data transactions through a UWB session established via the UWBS using parameters exchanged with each other.

[0108] A Secure Component may be a hardware component that interfaces with the framework and / or UWBS to provide RDS.

[0109] In the present disclosure, the UWB-enabled Application Layer and / or Framework may be implemented by an application processor (AP) (or processor). Therefore, in the present disclosure, the operation of the UWB-enabled Application Layer and / or Framework may be understood to be performed by the AP (or processor).

[0110] Figure 3 shows an exemplary structure of a frame used for UWB communication.

[0111] Fig. 3a illustrates an exemplary structure of a frame to which the STS packet setting is not applied, and Fig. 3b illustrates an exemplary structure of a frame to which the STS packet setting is applied. In one embodiment, the frame may be a ranging frame (RFRAME) for transmitting ranging data (e.g., ranging initiation / response / final message, etc.) or a data frame for transmitting other data (e.g., service data, etc.).

[0112] Referring to FIG. 3A, a frame or a PHY PDU (PPDU) for transmitting a frame may include a synchronization header (SHR), a PHY header (PHR), and a PHY payload (PSDU). The PSDU includes a MAC frame, and the MAC frame may include a MAC header (MHR), a MAC payload, and / or a MAC footer (MFR). The synchronization header of the PPDU may include a SYNC field and a start-of-frame delimiter (SFD). The SFD field may be a field indicating the end of the SHR and the start of the data field. For a description of each element / field included in the PPDU and the MAC frame, refer to the description defined in IEEE 802.15.4 / 4z and / or FiRa.

[0113] Meanwhile, the PHY layer of a UWB device may include an optional mode to provide reduced on-air time for high-density / low-power operation. In this case, the frame may include an encrypted sequence (i.e., STS) to increase the integrity and accuracy of the ranging measurement timestamp. This STS can be used for secure ranging.

[0114] The structure of a PPDU (or frame) when the STS packet setting is applied (supported) may be as shown in Fig. 3b.

[0115] Referring to FIG. 3b, when the STS packet (SP) setting is 0 (SP0), the STS field is not included in the PPDU (SP0 packet). When the SP setting is 1 (SP1), the STS field is located immediately after the Start of Frame Delimiter (SFD) field and before the PHR field (SP1 packet). When the SP setting is 2 (SP2), the STS field is located after the PHY payload (SP2 packet). When the SP setting is 3 (SP3), the STS field is located immediately after the SFD field, and the PPDU does not include the PHR and data fields (PHY payload) (SP3 packet). That is, in the case of SP3, the frame (or, UWB message) does not include the PHR and PHY payload.

[0116] Meanwhile, SP0, SP1, and SP3 are mandatory settings that must be supported when STS packet settings are supported, and SP2 may be optionally supported.

[0117] Figure 4 illustrates how two UWB devices perform UWB communication.

[0118] In the embodiment of FIG. 4, the first UWB device can perform the role of a controller (or controllery), and the second UWB device can perform the role of a controller (or controller), which is the opposite role of the first UWB device. Additionally, the first UWB device can perform the role of an initiator (or responder), and the second UWB device can perform the role of a responder (or initiator), which is the opposite role of the first UWB device.

[0119] (1) Referring to FIG. 4, the first UWB device and the second UWB device may optionally perform an OOB step prior to the UWB step. In the present disclosure, the OOB step may be referred to as an OOB connection step.

[0120] The OOB phase may be a phase performed to discover a UWB device through an OOB channel (e.g., a BLE channel) and establish and control a UWB session.

[0121] In one embodiment, the OOB step may include at least one of the following steps:

[0122] - Steps for discovering UWB devices and profiles (device and profile discovery)

[0123] - Steps to set up OOB connection (channel)

[0124] - Steps to establish a secure channel to secure messages and data

[0125] - A step for exchanging parameters for establishing a UWB session through a secure channel (e.g., UWB performance parameters (controller performance parameters), UWB configuration parameters, and / or session key related parameters) (parameter exchange step)

[0126] In one embodiment, the parameter exchange step may include a step for the controller to pass a controller performance parameter / message (UWB_CAPABILITY), a step for the controller to pass a UWB configuration parameter / message (UWB_CONFIGURATION) to the controller, and / or a step for one UWB device to pass a session key related parameter / message (SESSION_KEY_INFO) for securing a UWB session to another UWB device.

[0127] In one embodiment, the controller (UWB) performance parameters and / or session key parameters may be transmitted in a controller information message (CONTROLEE_INFO), which is an OOB message transmitted from the controller to the controller. In one embodiment, the UWB configuration parameters and / or session key parameters may be transmitted in a session data message (SESSION_DATA), which is an OOB message transmitted from the controller to the controller.

[0128] The controller performance parameter (UWB_CAPABILITY) may include at least one parameter that provides information about the device performance of the controller. For example, the controller performance parameter may include a parameter for support of the device's role (Initiator or Responder), a parameter for multi-node support, a parameter for support of STS configuration, a parameter for support of ranging methods, a RFRAME feature performance parameter, a parameter for support of Angle of Arrival (AoA), and / or a parameter for support of Scheduled Mode.

[0129] The UWB configuration parameter (UWB_CONFIGURATION) may include at least one parameter used for establishing a UWB session. For example, the UWB configuration parameter may include a UWB session ID parameter, a ranging method parameter, a multi-node configuration parameter, an STS configuration parameter, a Scheduled Mode parameter, a time-of-flight (ToF) report parameter, an AoA-related parameter, a parameter indicating the number of slots per ranging round, a slot duration parameter, a responder slot index parameter, a MAC address mode parameter, a device MAC address parameter, a parameter indicating the number of controllers, and / or a destination (DST) MAC address parameter.

[0130] The session key related parameters (SESSION_KEY_INFO) may include session key related parameters for Dynamic STS and / or session key related parameters for Static STS. For example, the session key related parameters for Dynamic STS may include data exchanged to generate a UWB session key or data directly used as a UWB session key. For example, the Static STS may include the ID of the vendor that provides the UWB-enabled application (Vendor ID) and a predefined random value (Static STS IV) selected by the UWB-enabled application for the UWB device. The Vendor ID may be used to set the phyVupper64 parameter for Static STS, and the Static STS IV may be used to set the vUpper64 parameter.

[0131] (2) The first UWB device and the second UWB device can perform a UWB step. In the present disclosure, the UWB step may be referred to as a UWB connection step.

[0132] The UWB phase may be a phase performed to perform UWB ranging and transmit service data through a UWB session.

[0133] In one embodiment, the UWB step may include at least one of the following steps:

[0134] - Steps to start a UWB session (UWB Trigger)

[0135] - A step for performing UWB ranging to obtain the distance / location between two UWB devices.

[0136] - Step for exchanging service data (transaction)

[0137] Meanwhile, as described above, the OOB step is an optional step and may be omitted depending on the embodiment. For example, if the discovery of a UWB device and / or the establishment and control of a UWB session are performed via a UWB channel (in-band), the OOB step may be omitted. For example, if in-band discovery is performed, the OOB step for performing OOB discovery may be omitted. In this case, the UWB step may further perform operations for discovering a UWB device via a UWB channel and exchanging parameters for UWB session establishment.

[0138] Figure 5 illustrates how two UWB devices perform UWB ranging.

[0139] Fig. 5 (a) shows an embodiment in which a first UWB device operates as a controller / initiator and a second UWB device operates as a controller / responder, and Fig. 5 (b) shows an embodiment in which a first UWB device operates as a controller / responder and a second UWB device operates as a controller / initiator.

[0140] Referring to (a) and (b) of FIG. 5, the controller can transmit a control message for UWB ranging to the controller. The ranging control message can be used to carry ranging parameter(s) for controlling and setting the ranging procedure. In one embodiment, the control message can include information about the role of the ranging device (e.g., initiator or responder), ranging slot index information, and / or address information of the ranging device.

[0141] The initiator can transmit a ranging initiation message to the responder to initiate UWB ranging. In one embodiment, the initiator can transmit the ranging initiation message via an SP1 packet or an SP3 packet. When transmitting the ranging initiation message via an SP1 packet, a control message can be transmitted as included in the PHY payload of the ranging initiation message. When transmitting the ranging initiation message via an SP3 packet, the ranging initiation message does not include a PHR and a PHY payload.

[0142] The responder may transmit a ranging response message to the initiator in response to the ranging initiation message. In one embodiment, the responder may transmit the ranging response message via an SP1 packet or an SP3 packet. When transmitting the ranging response message via an SP1 packet, a first Measurement Report Message may be transmitted in the PHY payload of the ranging response message. In one embodiment, the first Measurement Report Message may include an AoA measurement, a reply time measured by the responder, and / or a list of responder addresses and round-trip time measurements for the responders. The reply time field may indicate a time difference between the reception time of the ranging initiation message and the transmission time of the ranging response message on the responder side. Based on this, single-sided two-way ranging (SS-TWR) may be performed. The calculation of ToF via SS-TWR follows the method defined in IEEE 802.15.4z or FiRa.

[0143] For DS-TWR (Double-sided two-way ranging), the initiator may further transmit a Ranging Final Message to the responder to complete the ranging exchange. When transmitting the Ranging Final Message via an SP1 packet, a second Measurement Report Message may be transmitted in the PHY payload of the Ranging Final Message. In one embodiment, the second Measurement Report Message may include an AoA measurement, a round-trip time for the first responder, and / or a list of responder addresses and reply time measurements for the responders. When the sender of the Measurement Report Message is the initiator, the First round-trip time field may indicate the time difference between the Ranging Initiation message from the initiator and the first Ranging Response message from the first responder. Alternatively, if the sender of the Measurement Report Message is a responder, the First round-trip time field may indicate the time difference between the ranging response message from the responder and the ranging final message from the initiator. Based on this, DS-TWR can be performed. The calculation of time-of-flight (ToF) through DS-TWR follows the method defined in IEEE 802.15.4z or FiRa.

[0144] Meanwhile, depending on the embodiment, the first measurement report message and / or the second measurement report message described above may not be included in the ranging response message and / or the ranging final message, but may be transmitted via a separate message. For example, if the non-deferred mode is applied, the measurement report message may be transmitted via a data frame after the ranging exchange.

[0145] Meanwhile, the initiator and responder can perform UWB ranging according to a predefined schedule mode. For example, in time-scheduled ranging mode, the controller knows the IDs of all controllers and can precisely schedule ranging transmissions. In another example, in contention-based ranging mode, the controller does not know the number or IDs of the controllers, and thus UWB devices compete with each other. This can lead to collisions between responding devices.

[0146] Figure 6 shows the structure of ranging blocks and rounds used for UWB ranging.

[0147] In the present disclosure, a ranging block refers to a time period for ranging. A ranging round may be a period of sufficient duration to complete one entire ranging-measurement cycle involving a set of UWB devices participating in a ranging exchange. A ranging slot may be a period of sufficient duration to transmit at least one ranging frame (RFRAME) (e.g., ranging initiation / response / final message, etc.).

[0148] As in FIG. 6, one ranging block may include at least one ranging round, and each ranging round may include at least one ranging slot.

[0149] When the ranging mode is block-based, the mean time between consecutive ranging rounds can be constant. Alternatively, when the ranging mode is interval-based, the time between consecutive ranging rounds can be dynamically changed. That is, the interval-based mode can adopt a time structure with adaptive spacing.

[0150] The number and duration of slots included in a ranging round can be changed between ranging rounds. This can be set via control messages from the controller.

[0151] The UWB protocol is applicable to use cases that handle multiple users and provide high-speed authentication or payment. For example, the UWB protocol can be applied to gate services, allowing users with UWB devices (e.g., smartphones) to pass through a UWB-based gate system for authentication or payment without interacting with the UWB device.

[0152] The present disclosure presents an exemplary system architecture, exemplary OOB procedures (e.g., BLE procedures), ranging procedures, and transaction procedures for providing UWB services for multiple users, such as this gate service.

[0153] Below, each embodiment is described with a focus on a gate service (or smart gate service). However, this is merely an example, and the embodiments of the present disclosure can also be applied to various types of services (e.g., PoS payment services) that require high-speed authentication or payment processing for multiple users. In this case, the exemplary system architecture, exemplary OOB procedures (e.g., BLE procedures), ranging procedures, and transaction procedures for providing such services can be referenced from the descriptions above in FIGS. 1 to 6.

[0154] FIG. 7 illustrates an exemplary architecture of a system providing a UWB-based gate service according to one embodiment of the present disclosure.

[0155] In the present disclosure, a UWB-based gate service may be referred to as a gate service or a smart gate service (SGS), and a system providing a UWB-based gate service may be referred to as a gate system or a smart gate system.

[0156] Referring to FIG. 7, the gate system may include a mobile device, a smart station, and / or an SGS operator server. In the present disclosure, the mobile device may be referred to as a first UWB device, and the smart station may be referred to as a second UWB device.

[0157] (1) The mobile device may include a framework (U-Pass framework), an SGS application, an SGS applet, a BLE component (subsystem), and / or a UWB component (subsystem). In one embodiment, the framework, the SGS application, the SGS applet, the BLE component, and / or the UWB component of the mobile device may be examples of the framework, the UWB-enabled application, the applet, the OOB component, and the UWB component of the UWB device, respectively, as described above in FIG. 1 .

[0158] A framework may support at least one of the following features:

[0159] - Position estimation of mobile devices during Downlink-TDoA (DL-TDoA) rounds

[0160] - Implement procedures for UWB ranging and transaction execution.

[0161] - Provides a set of APIs for SGS operator applications (SGS applications) and provides an interface between the framework and UWB components.

[0162] - Trigger UWB communication (component) when a BLE advertisement is received from a smart station.

[0163] The SGS application may support at least one of the following features:

[0164] - Provides deployment information of anchor and UWB block structures when requested by the framework.

[0165] - Provides the AID of the SGS applet and the version of the SGS applet protocol to the framework.

[0166] - Communicate with the SGS operator server to initiate service applet installation, retrieve station-specific information (e.g., a map of anchors), or initiate a token retrieval or renewal process.

[0167] SGS Applet can support at least one of the following features:

[0168] - Hosted in a secure component (e.g. SE or TEE) that can communicate via a UWB interface.

[0169] - Implementing a transaction protocol for gate services

[0170] - Supports APDU commands

[0171] The BLE component can be used to receive at least one BLE message from a smart station when a mobile device enters the service area of ​​the gate system.

[0172] The UWB component may be used, for example, to estimate the location of a mobile device using DL-TDoA, and / or to communicate with specific gateways to perform UWB ranging and transactions.

[0173] (2) A smart station may include at least one BLE anchor, at least one TDoA anchor, and / or at least one gate (gate device). In the present disclosure, a TDoA anchor may be referred to as a DL-TDoA anchor.

[0174] BLE anchors can be used to notify mobile devices that they have entered the service area of ​​a gate system, and to provide general station information to the mobile devices.

[0175] In one embodiment, a BLE anchor may support a GAP broadcaster role, a GATT server role, and / or Broadcast advertising physical channel PDUs.

[0176] DL-TDoA anchors can be deployed within the service area of ​​the gateway system. DL-TDoA anchors can broadcast UWB messages at specific times. These UWB messages can be used by mobile devices to estimate their location.

[0177] The gate device may include at least one UWB component (subsystem) and / or a security authentication module. The UWB component may be an example of the UWB subsystem described above, such as in FIG. 1. In one embodiment, the gate device may include at least one anchor, and each anchor may include at least one UWB component.

[0178] The UWB component may be used to communicate with a mobile device for gate access and gate ranging, for example, to identify whether the mobile device is within a valid range to perform a transaction procedure and pass through a gate.

[0179] In one embodiment, the UWB component may support at least one of the following features:

[0180] - DS-TWR performance

[0181] - Perform gate access and gate ranging

[0182] - Provides an interface to the security authentication module.

[0183] A security authentication module can be used to verify that a mobile device is authorized to use the gate system.

[0184] In one embodiment, the security authentication module may support at least one of the following features:

[0185] - Provides interfaces to UWB components

[0186] - Communication capability via UWB interface

[0187] - Ability to synchronize with SGS operator servers

[0188] (3) The SGS operator server can manage the entire gate system. To this end, the SGS operator server can communicate with mobile devices and smart stations.

[0189] FIG. 8 illustrates an exemplary operation scenario of a gate system according to one embodiment of the present disclosure.

[0190] The gate system of Fig. 8 may be the gate system of Fig. 7.

[0191] Referring to FIG. 8, in operation 1, when a mobile device (or a user having a mobile device) enters the BLE area of ​​the gate system, the mobile device may receive a BLE advertising message (packet) from at least one BLE anchor of the smart station. At least one BLE anchor may be located in the BLE area.

[0192] In operation 2, if a BLE advertising message is received, prerequisite procedures for the gate system can be performed, i.e., the gate system can be prepared. In one embodiment, the prerequisite procedures can be activated by the UWB component of the mobile device and used to obtain authentication-related information and / or UWB-related information from the SGS operator server.

[0193] In operation 3, when the mobile device enters the location estimation area, the mobile device can estimate its location to determine the nearest gate to pass through. In one embodiment, the mobile device can receive a TDoA message from at least one TDoA anchor of the smart station and estimate its location using the DL-TDoA method. Meanwhile, the application (SGS application) on the mobile device can provide or utilize the locations of the gate(s).

[0194] In step 4, the mobile device may select the nearest gate. In one embodiment, the mobile device may select the nearest gate based on the location of the gate(s) and the results of the location estimation.

[0195] In step 5, the mobile device can perform a UWB ranging procedure with the selected gate. First, after selecting the nearest gate, the mobile device can compete for a specific slot to perform UWB ranging with that gate. The available slots (contention periods) for competing can be announced by the gate via UWB messages. If the mobile device obtains an opportunity to transmit, UWB ranging and service protocols (transactions) can be performed with the gate. After the appropriate authentication or payment capability is verified through UWB ranging and message exchanges, the user can pass through the gate.

[0196] FIG. 9 illustrates a smart gate service procedure of a gate system according to one embodiment of the present disclosure.

[0197] The gate system of Fig. 9 may be the gate system of Fig. 7.

[0198] Referring to FIG. 9, a smart gate service procedure can be performed between a smart station including at least one gate device and at least one mobile device.

[0199] The smart gate service procedure may include a smart gate service initiation step (phase 1), a gate discovery and location estimation step using DL-TDoA (phase 2), a gate access step for UWB slot reservation (phase 3), and / or a transaction step via UWB (phase 4). Upon completion of a transaction (transaction step) according to this smart gate service procedure, a specific gate may be opened. This allows a user to enter or exit the specific gate.

[0200] In one embodiment, the smart gate service initiation step may include, for example, operations 1 and 2 of FIG. 8.

[0201] In one embodiment, the gate discovery and position estimation step may include, for example, operation 3 of FIG. 8.

[0202] In one embodiment, the gate access step for UWB slot reservation may include, for example, the access operations (contention participation) of operations 4 and 5 of FIG. 8.

[0203] In one embodiment, the transaction steps via UWB may include, for example, the UWB ranging and service protocol (transaction) operations of operation 5 of FIG. 8.

[0204] FIG. 10 illustrates an exemplary operation scenario of a gate system according to one embodiment of the present disclosure.

[0205] Referring to FIG. 10, the gate device and mobile device included in the gate system can perform a transaction using a tagless gate transaction protocol.

[0206] Transactions can be pre-processed based on the distance between the mobile device and the gate device before the mobile device passes through the gate device. When multiple mobile devices approach the gate device, transactions can be pre-processed based on the distance between the mobile device and the gate device to minimize delay.

[0207] However, when applying the NFC (near field communication) payment protocol to a gate system, the transaction process must proceed without interruption, making it impossible to perform transactions step-by-step based on distance. Furthermore, when applying the NFC payment protocol to a gate system, it is necessary to consider the characteristics of whether the circuit breaker is open or closed (e.g., whether the circuit breaker is open).

[0208] FIG. 11 is a flowchart illustrating a transaction performed in a gate system according to one embodiment of the present disclosure.

[0209] Referring to FIG. 11, the gate device (1110) may include a Secure Application Module (SAM) (1120) and a UWB module (1130), and the mobile device (1140) may include a SAM (1150) and a UWB module (1160).

[0210] In operation 1101, the UWB module (1160) of the mobile device (1140) may transmit a payment initiation message (m[0]: initiation) to the UWB module (1130) of the gate device (1110). The SAM (1150) of the mobile device (1140) may transmit t m[0]At this point, a payment initiation message (m[0]: initiation) can be generated and transmitted to the UWB module (1160).

[0211] In operation 1103, the UWB module (1130) of the gate device (1110) may transmit a payment method information request message (m[1]: Request card info.) to the UWB module (1160) of the mobile device (1140). The SAM (1120) of the gate device (1110) may transmit t m[1] At this point, a payment method information request message (m[1]: Request card info.) can be generated and transmitted to the UWB module (1130).

[0212] In operation 1105, the UWB module (1160) of the mobile device (1140) may transmit a payment method information response message (m[2]: Reply card info.) to the UWB module (1130) of the gate device (1110). The SAM (1150) of the mobile device (1140) may transmit t m[2] At this point, a payment method information response message (m[2]: Reply card info.) can be generated and transmitted to the UWB module (1160).

[0213] In operation 1107, the UWB module (1130) of the gate device (1110) may transmit a first payment request message (m[3]: Request pay. #1) to the UWB module (1160) of the mobile device (1140). The SAM (1120) of the gate device (1110) may transmit t m[3] At this point, a first payment request message (m[3]: Request pay. #1) can be generated and transmitted to the UWB module (1130).

[0214] In operation 1109, the UWB module (1160) of the mobile device (1140) may transmit a first payment response message (m[4]: Reply pay. #1) to the UWB module (1130) of the gate device (1110). The SAM (1150) of the mobile device (1140) may transmit tm[4] At this point, a first payment response message (m[4]: Reply pay. #1) can be generated and transmitted to the UWB module (1160).

[0215] In operation 1111, the UWB module (1130) of the gate device (1110) may transmit a second payment request message (m[5]: Request pay. #2) to the UWB module (1160) of the mobile device (1140). The SAM (1120) of the gate device (1110) may transmit t m[5] At this point, a second payment request message (m[5]: Request pay. #2) can be generated and transmitted to the UWB module (1130).

[0216] In operation 1113, the UWB module (1160) of the mobile device (1140) may transmit a second payment response message (m[6]: Reply pay. #2) to the UWB module (1130) of the gate device (1110). The SAM (1150) of the mobile device (1140) may transmit t m[6] At this point, a second payment response message (m[6]: Reply pay. #2) can be generated and transmitted to the UWB module (1160).

[0217] In a gate system, operations 1101 to 1113 for a transaction can be performed sequentially at once without interruption. m[0] point in time t m[6] A point in time can be a continuous time interval.

[0218] FIG. 12 illustrates an exemplary operating scenario of a unidirectional gate system according to one embodiment of the present disclosure.

[0219] Referring to FIG. 12, in a unidirectional gate system, a gate device may include a first UWB module (1210) and a second UWB module (1220). For convenience of explanation, FIG. 12 illustrates the first UWB module (1210) and the second UWB module (1220) included in the gate device, but the technical idea of ​​the present disclosure is not limited thereto, and the number and positions of UWB modules within the gate device may be implemented in various ways.

[0220] In Fig. 12, a Gate Access Area that can check whether a mobile device has accessed a gate device and a Transaction Area for transactions between a mobile device and a gate device can be separately set.

[0221] In the Gate Access Area, it can be determined whether the mobile device has entered the vicinity of the gate device based on the DL-TDoA location of the mobile device and the distance between the mobile device and the gate device.

[0222] In the Transaction Area, the location of the mobile device can be determined based on a first distance (d1) between the first UWB module (1210) of the gate device and the mobile device, and a second distance (d2) between the second UWB module (1220) of the gate device and the mobile device. In the Transaction Area, the mobile device can perform a transaction (e.g., a payment procedure) with the first UWB module (1210) and the second UWB module (1220) of the gate device.

[0223] FIG. 13 illustrates an exemplary operation scenario of a bidirectional gate system according to one embodiment of the present disclosure.

[0224] Referring to FIG. 13, in a two-way gate system, a gate device may include a first UWB module (1310), a second UWB module (1320), a third UWB module (1330), and a fourth UWB module (1340). For convenience of explanation, FIG. 12 illustrates the first UWB module (1310), the second UWB module (1320), the third UWB module (1330), and the fourth UWB module (1340) included in the gate device; however, the technical idea of ​​the present disclosure is not limited thereto, and the number and positions of UWB modules within the gate device may be implemented in various ways.

[0225] In Fig. 13, a Gate Access Area that can check whether a mobile device has accessed a gate device and a Transaction Area for transactions between a mobile device and a gate device can be separately set.

[0226] In the Gate Access Area, based on the DL-TDoA location of the mobile device and the distance between the mobile device and the gate device, it can be determined whether the mobile device has entered the vicinity of the gate device. To utilize the DL-TDoA signal as a reference, a first wireless channel (e.g., channel 5) may be set for DL-TDoA in the gate in direction, and a second wireless channel (e.g., channel 9) may be set for DL-TDoA in the gate out direction.

[0227] In the Transaction Area in the gate in direction, the location of the mobile device can be identified based on a first distance (d1) between the first UWB module (1310) of the gate device and the mobile device, and a second distance (d2) between the second UWB module (1320) of the gate device and the mobile device. In the Transaction Area in the gate in direction, the mobile device can perform a transaction (e.g., a payment procedure) with the first UWB module (1310) and the second UWB module (1320) of the gate device.

[0228] In the Transaction Area in the gate out direction, the location of the mobile device can be determined based on a third distance (d3) between the third UWB module (1330) of the gate device and the mobile device, and a fourth distance (d4) between the fourth UWB module (1340) of the gate device and the mobile device. In the Transaction Area in the gate out direction, the mobile device can perform a transaction (e.g., a payment procedure) with the third UWB module (1330) and the fourth UWB module (1340) of the gate device.

[0229] FIG. 14 is a diagram illustrating an example of a time interval during which a transaction is performed in a gate system according to one embodiment of the present disclosure.

[0230] Referring to FIG. 14, DL-TDOA anchors may use a first wireless channel (e.g., channel 5) for gate-in side DL-TDoA and a second wireless channel (e.g., channel 9) for gate-out side DL-TDoA. The DL-TDOA anchors may be placed in a gate access area (GA) on the gate-in side and / or a gate access area on the gate-out side of the gate device. In one embodiment, the DL-TDOA anchors may be included in the gate device. In another embodiment, the DL-TDOA anchors may be implemented outside the gate device. At least one DL-TDoA anchor may broadcast an UWB message at a specific time. The UWB message may be used by a mobile device to estimate its own location.

[0231] A gate in module within a gate device can perform a UWB communication-based transaction in a hybrid UWB session (HUS) with a mobile device entering or exiting from the gate in side via a first wireless channel (e.g., channel 5). In a transaction area, the mobile device can perform a UWB communication-based transaction with the gate in module.

[0232] A gate out module within a gate device can perform UWB communication-based transactions in a hybrid UWB session (HUS) with a mobile device entering or exiting from the gate out side through a second wireless channel (e.g., channel 9). In a transaction area, a mobile device can perform UWB communication-based transactions with the gate out module.

[0233] By having the gate in module and the gate out module within the gate device operate different wireless channels, communication on the gate in side and communication on the gate out side can be performed in parallel.

[0234] FIG. 15 illustrates an exemplary operation scenario of a gate system according to one embodiment of the present disclosure.

[0235] Referring to FIG. 15, a gate device in a gate system may include a first UWB module (1510) and a second UWB module (1520). For convenience of explanation, FIG. 15 illustrates the first UWB module (1510) and the second UWB module (1520) included in the gate device, but the technical idea of ​​the present disclosure is not limited thereto, and the number and positions of UWB modules within the gate device may be implemented in various ways.

[0236] In Fig. 15, a Gate Access Area that can check whether a mobile device has accessed a gate device and a Transaction Area for transactions between a mobile device and a gate device can be separately set.

[0237] When a mobile device enters a gate device, in the Gate Access Area, the mobile device can receive a message broadcast from a DL-TDoA located inside or near the gate device and estimate its location based on the message.

[0238] When a mobile device passes through a Gate Access Area and enters a Transaction Area, the mobile device may perform a transaction (e.g., a payment procedure) with the first UWB module (1510) of the gate device and / or the second UWB module (1520) of the gate device based on a first distance (d1) between the first UWB module (1510) of the gate device and the mobile device, and a second distance (d2) between the second UWB module (1520) of the gate device and the mobile device. For example, as the mobile device passes through the Gate Access Area, the first distance (d1) according to the ranging result may increase and the second distance (d2) may decrease. For example, the mobile device may determine the difference between the first distance (d1) and the second distance (d2) according to the ranging result, and estimate the location of the mobile device within the Gate Access Area.

[0239] FIG. 16 is a diagram illustrating an example of a time interval during which a transaction is performed in a gate system according to one embodiment of the present disclosure.

[0240] Referring to (a) of FIG. 16, a time interval (1610) for DL-TDoA and a time interval (1620) for HUS can be set between a mobile device and a gate device. The time interval (1620) for HUS can include a time interval (1630) for CBR (contention based ranging), a time interval (1640) for transaction (or data transmission), and a time interval (1650) for DS-TWR.

[0241] In the time interval for DL-TDoA (1610), the mobile device can determine that the mobile device has entered the transaction area through DL-TDoA (DL-TDoA Localization).

[0242] Referring to (b) of FIG. 16, in the time interval (1630) for CBR, a mobile device can participate in a competition at a specific slot to perform UWB ranging with a gate device. Available slots (contention periods) for participating in the competition can be announced by the gate device via UWB messages. If the mobile device acquires an opportunity to transmit, UWB ranging and service protocols (transactions) can be performed with the gate device. After proper authentication or payment capabilities are verified through UWB ranging and message exchanges, the mobile device can pass through the gate device.

[0243] In one embodiment, in a time interval (1630) for CBR, the gate device may transmit a first UWB message (1631) to the mobile device, which includes possible slots (contention period) for participating in the contention. The mobile device may transmit a second UWB message (1632) to the gate device in response to the first UWB message (1631) during the contention period.

[0244] In the time interval (1640) for a transaction (or data transfer), the mobile device and the gateway device can perform a UWB communication-based transaction (or data transfer). A mobile device located within the transaction area can immediately initiate a transaction (or data transfer) and complete the payment.

[0245] In the time interval (1640) for a transaction (or data transmission), the mobile device may transmit a payment initiation message (1641) (e.g., m[0]: initiation in FIG. 11) to the gate device. Thereafter, the gate device may transmit a payment method information request message (1642) (e.g., m[1]: Request card info. in FIG. 11) to the mobile device. Thereafter, the mobile device may transmit a payment method information response message (1643) (e.g., m[2]: Reply card info. in FIG. 11) to the gate device. Thereafter, the gate device may transmit a first payment request message (1644) (e.g., m[3]: Request pay. #1 in FIG. 11) to the mobile device. Thereafter, the mobile device may transmit a first payment response message (1645) (e.g., m[4]: Reply pay. #1 in FIG. 11) to the gate device. Thereafter, the gate device can transmit a second payment request message (1646) (e.g., m[5]: Request pay. #2 in FIG. 11) to the mobile device. Thereafter, the mobile device can transmit a second payment response message (1647) (e.g., m[6]: Reply pay. #2 in FIG. 11) to the gate device. The mobile device and the gate device can complete the transaction (or data transfer) through the continuous transmission and reception of messages 1641 to 1647.

[0246] Referring to (c) of FIG. 16, the gate device can grant FFP (free pass permission) to a mobile device that has completed a transaction (or data transmission). The gate device can perform DS-TWR with the mobile device during a time interval (1650) for DS-TWR. In one embodiment, when there are at least two UWB modules (or gate modules) in the gate device, the mobile device can perform DS-TWR with all of the at least two UWB modules (or gate modules).

[0247] As a result of performing DS-TWR, if it is determined that the mobile device has completely passed through the gate device, the gate device can retrieve the FFP granted to the mobile device and perform UWB channel switching. According to one embodiment, based on a first distance (d1) between a first UWB module (e.g., 1510 of FIG. 15) of the gate device and the mobile device, and a second distance (d2) between a second UWB module (e.g., 1520 of FIG. 15) of the gate device and the mobile device, the mobile device and / or the gate device can determine whether the mobile device has completely passed through the gate device (or transaction area).

[0248] FIG. 17 is a diagram for explaining the point in time at which Free Pass Permission (FPP) is granted in a gate system according to one embodiment of the present disclosure.

[0249] Referring to FIG. 17, a time interval (1710) for DL-TDoA between a mobile device and a gate device, a time interval (1720) for CBR, a time interval (1730) for transaction (or data transmission), and a time interval (1740) for DS-TWR can be set.

[0250] In a time interval (1730) for a transaction (or data transmission), the mobile device and the gateway device may exchange multiple messages for the transaction. Thereafter, the gateway device may transmit a message (1750) containing a Free Pass Permission (FFP) to at least one mobile device that has completed the transaction.

[0251] In one embodiment, a message (1750) including an FFP may include a message transmission time (Message Tx Time) (1751) and a random number (Random number) (1752) for the message. For example, the message transmission time (1751) included in the message (1750) including an FFP may be indicated in units of microseconds (us) and implemented in a size of 4 octets. For example, the random number (1752) included in the message (1750) including an FFP may be implemented in a size of 1 octet.

[0252] In one embodiment, a server that manages and / or operates at least one gate device can manage an FFP table for at least one gate device. For example, the FFP table can include information about a first gate device, and the information about the first gate can include a gate number (e.g., 1), a MAC address (e.g., AD:EE), a Message Tx Time for a message containing an FFP (e.g., 151,684,218,676 us), and a random number (e.g., 215). For example, the FFP table can include information about a second gate device, and the information about the second gate can include a gate number (e.g., 2), a MAC address (e.g., E1:10), a Message Tx Time for a message containing an FFP (e.g., 151,684,418,872 us), and a random number (e.g., 3).

[0253] FIG. 18 is a diagram for explaining the point in time at which FPP is recovered in a gate system according to one embodiment of the present disclosure.

[0254] Referring to FIG. 18, a time interval (1810) for DL-TDoA between a mobile device and a gate device, a time interval (1820) for CBR, a time interval (1830) for transaction (or data transmission), and a time interval (1840) for DS-TWR can be set.

[0255] In the time section (1840) for DS-TWR, if it is determined that the mobile device has completely passed through the gate device as a result of performing the DS-TWR, the gate device may retrieve the FFP granted to the mobile device. In one embodiment, based on a first distance (d1) between a first UWB module (e.g., 1510 of FIG. 15) of the gate device and the mobile device, and a second distance (d2) between a second UWB module (e.g., 1520 of FIG. 15) of the gate device and the mobile device, the mobile device and / or the gate device may determine whether the mobile device has completely passed through the gate device (or transaction area).

[0256] In the time interval (1840) for DS-TWR, the mobile device may transmit information for FPP return to the gateway device by data piggybacking it onto the DS-TWR message. The gateway device may transmit the DS-TWR message containing information for FPP recovery to the mobile device.

[0257] According to one embodiment, the information for the FPP return and the information for the FPP recovery may include an FPP indicator (1851) (e.g., set to 7 bits) and a flag (1852) (e.g., set to 1 bit). According to one embodiment, if the flag in the information for the FPP return is a first value (e.g., 1) and the flag in the information for the FPP recovery is the same first value (e.g., 1), the mobile device and the gate device determine that the mobile device has passed through the gate device, and the FPP for the mobile device may be recovered. According to one embodiment, the recovered FPP may be deleted from the FPP table managed by the server.

[0258] FIGS. 19a, 19b, and 19c illustrate examples of FPP being used in a gate system according to one embodiment of the present disclosure.

[0259] Key examples of scenarios requiring Free Pass Permission (FPP) in this disclosure include:

[0260] 1) When a transaction is completed due to the movement of users (or mobile devices) that are difficult to respond to and DL-TDoA errors (Fig. 19a);

[0261] 2) If the transaction is completed but the mobile device does not pass through the gate device (Fig. 19b);

[0262] 3) When a transaction is completed at a gate device but passes through another gate device (Fig. 19c);

[0263] Referring to FIG. 19a, if a mobile device located in a gate access area remains in the transaction area for a certain period of time unintentionally and a transaction is completed, the gate device may grant an FFP to the mobile device to prevent the mobile device from performing a transaction again in the future.

[0264] Referring to FIG. 19b, if a mobile device located in a gate access area performs a transaction during a moving process, the gate device may grant an FFP to the mobile device to prevent the mobile device from performing a transaction again in the future.

[0265] Referring to FIG. 19c, if a mobile device located in a gate access area completes a transaction in a transaction area of ​​a first gate device but passes through a second gate device, the first gate device and / or the second gate device may grant FFP to the mobile device so that the mobile device does not perform a transaction again at the second gate device.

[0266] FIG. 20 is a diagram for explaining messages for determining the authenticity of FPP in a gate system according to one embodiment of the present disclosure.

[0267] Referring to FIG. 20, a time interval (2010) for DL-TDoA between a mobile device and a gate device, a time interval (2020) for CBR, a time interval (2030) for transaction (or data transmission), and a time interval (2040) for DS-TWR can be set.

[0268] In the time interval for the transaction (2030), the mobile device may transmit a message (Request FPP confirm) (2050) requesting confirmation of the authenticity of the FPP to the gate device. In response to the request message (Request FPP confirm), the gate device may transmit a message (FPP accept) (2060) indicating the authenticity of the FPP to the mobile device.

[0269] In one embodiment, a message requesting confirmation of the authenticity of an FPP (Request FPP confirm) (2050) may include a transmission time (Message Tx Time) (2051) and a random number (Random number) (2052) for the message. For example, the transmission time (2051) for the message may be indicated in microseconds (us) and may be implemented in a size of 4 octets. For example, the random number (2052) may be implemented in a size of 1 octet.

[0270] According to one embodiment, a message (FPP accept) (2060) indicating whether FFP is true or false may include Accept / Deny information (2061) indicating whether FFP is true or false. For example, the Accept / Deny information (2061) may be implemented in a size of 1 octet.

[0271] In one embodiment, if a transaction is completed but the mobile device does not pass through the gate device, a cancellation request may be made after the FPP is discarded when the FPP lifetime expires (e.g., lifetime: 1 min). In one embodiment, the SAM may be configured to perform the cancellation.

[0272] In one embodiment, when a mobile device passes through a gate device other than the gate device through which the transaction was completed, a message regarding FPP may be defined. In one embodiment, the gate device and / or the mobile device may transmit a previously received Message Tx Time and a Random number to the other gate device through which the mobile device passes. In one embodiment, the message including the received Message Tx Time and the Random number may be processed (transmitted and / or received) via UWB-based communication without going through the SAM. In one embodiment, the gate device receiving the Request FPP confirm message may refer to the FPP Table. In one embodiment, the gate device may perform a Gate open / close operation after determining whether the corresponding FPP is authentic.

[0273] FIG. 21 is a diagram for explaining messages for determining the authenticity of FPP in a gate system according to one embodiment of the present disclosure.

[0274] Referring to FIG. 21, the gate device (2110) may include a Secure Application Module (SAM) (2120) and a UWB module (2130), and the mobile device (2140) may include a SAM (2150) and a UWB module (2160).

[0275] In operation 2101, the UWB module (2160) of the mobile device (2140) may transmit a message requesting FPP confirmation (Request FPP confirm) to the UWB module (1230) of the gate device (1210).

[0276] In operation 2103, the UWB module (2130) of the gate device (2110) can transmit a message (FPP accept) indicating the authenticity of the FPP to the UWB module (2160) of the mobile device (2140).

[0277] For example, a mobile device located in a gate access area may complete a transaction in the transaction area of ​​a first gate device but may pass through a second gate device. At this time, the UWB module (2130) within the second gate device may receive a message requesting FPP confirmation (Request FPP confirm) from the mobile device and transmit a response message thereto to the mobile device.

[0278] In the present disclosure, the mobile device may be implemented as a first UWB device, and the gate device may be implemented as a second UWB device.

[0279] According to one embodiment, a method of a first UWB device may include: estimating a location of the first UWB device based on downlink-TDoA (DL-TDoA); transmitting a transaction initiation message to a second UWB device via UWB communication when the first UWB device enters a transaction area set to a second UWB device based on the location estimation; receiving a transaction request message from the second UWB device via UWB communication, and transmitting a transaction response message corresponding to the transaction request message to the second UWB device via UWB communication; and performing double-sided two-way ranging (DS-TWR) to determine whether the first UWB device moves outside the transaction area when a transaction between the first UWB device and the second UWB device is completed.

[0280] According to one embodiment, the method of the first UWB device may further include receiving a first message including information regarding a free pass permission (FFP) from the second UWB device when a transaction between the first UWB device and the second UWB device is completed.

[0281] According to one embodiment, the information about the FFP may include a transmission time (Message Tx Time) and a random number for the first message.

[0282] In one embodiment, the method of the first UWB device may further include: determining that the first UWB device has moved outside the transaction area based on the DS-TWR; and transmitting a second message to the second UWB device, the second message including a flag indicating that the first UWB device has moved outside the transaction area.

[0283] According to one embodiment, the method of the first UWB device may further include: transmitting a third message (Request FPP confirm) to the second UWB device for confirming whether the FFP is authentic; and receiving a fourth message (FPP accept / Deny) including information regarding whether the FFP is authentic from the second UWB device.

[0284] In one embodiment, the third message may include a transmission time (Message Tx Time) and a random number for the first message.

[0285] FIG. 22 is a diagram illustrating the structure of a first electronic device according to one embodiment of the present disclosure.

[0286] In the embodiment of FIG. 22, the first electronic device may be an electronic device corresponding to a UWB device, including a UWB device, or including a part of a UWB device. The first electronic device may be implemented as a mobile device as illustrated in FIGS. 1 to 21.

[0287] Referring to FIG. 22, the electronic device may include a transceiver (2210), a control unit (2220), and a storage unit (2230). In the present disclosure, the control unit (2220) may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0288] The transceiver (2210) can transmit and receive signals with other entities. The transceiver (2210) can transmit and receive data with other devices using, for example, UWB communication and / or OOB communication (e.g., BLE). The transceiver (2210) includes a transmitter and a receiver, and may also be referred to as a transceiver.

[0289] The control unit (2220) can control the overall operation of the mobile device according to the embodiment proposed in the present disclosure. For example, the control unit (2220) can control the signal flow between each block to perform operations according to the flowchart described above. Specifically, the control unit (2220) can control the operations of the mobile device (e.g., the operation of the framework) described with reference to FIGS. 1 to 21, for example.

[0290] The storage unit (2230) can store at least one of the information transmitted and received through the transmission and reception unit (2210) and the information generated through the control unit (2220). For example, the storage unit (2230) can store information and data required for the method described with reference to FIGS. 1 to 21. In one embodiment, the storage unit can include the security component described above.

[0291] FIG. 23 is a diagram illustrating the structure of a second electronic device according to one embodiment of the present disclosure.

[0292] In the embodiment of FIG. 23, the second electronic device may be an electronic device corresponding to a UWB device, including a UWB device, or including a part of a UWB device. The second electronic device may be implemented as a gate device as illustrated in FIGS. 1 to 21.

[0293] Referring to FIG. 23, the electronic device may include a transceiver (2310), a control unit (2320), and a storage unit (2330). In the present disclosure, the control unit (2320) may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0294] The transceiver (2310) can transmit and receive signals with other entities. The transceiver (2310) can transmit and receive data with other devices using, for example, UWB communication and / or OOB communication (e.g., BLE). The transceiver (2310) includes a transmitter and a receiver, and may also be referred to as a transceiver.

[0295] The control unit (2320) can control the overall operation of the gate device according to the embodiment proposed in the present disclosure. For example, the control unit (2320) can control the signal flow between each block to perform operations according to the flowchart described above. Specifically, the control unit (2320) can control the operation of the gate device (e.g., the operation of the framework) described with reference to FIGS. 1 to 21, for example.

[0296] The storage unit (2330) can store at least one of the information transmitted and received through the transmission and reception unit (2310) and the information generated through the control unit (2320). For example, the storage unit (2330) can store information and data required for the method described with reference to FIGS. 1 to 21. In one embodiment, the storage unit can include the security component described above.

[0297] In the specific embodiments of the present disclosure described above, components included in the present disclosure are expressed in the singular or plural form, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.

[0298] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims

1. In the method of the first UWB (ultra wide band) device, An operation of estimating the location of the first UWB device based on DL-TDoA (downlink-TDoA); An operation of transmitting a transaction initiation message to the second UWB device via UWB communication when the first UWB device enters a transaction area set to the second UWB device according to the position estimation; An operation of receiving a transaction request message from the second UWB device via UWB communication and transmitting a transaction response message corresponding to the transaction request message to the second UWB device via UWB communication; and A method characterized by comprising an operation of performing double-sided two-way ranging (DS-TWR) to determine whether the first UWB device moves outside the transaction area when a transaction between the first UWB device and the second UWB device is completed.

2. In paragraph 1, A method characterized in that, when a transaction between the first UWB device and the second UWB device is completed, the method further comprises the action of receiving a first message including information regarding free pass permission (FFP) from the second UWB device.

3. In paragraph 2, the information regarding the FFP is: A method characterized by including a transmission time (Message Tx Time) and a random number (Random number) for the first message.

4. In paragraph 2, An operation for determining that the first UWB device has moved out of the transaction area based on the DS-TWR; and A method further comprising the action of transmitting a second message to the second UWB device, the second message including a flag indicating that the first UWB device has moved out of the transaction area.

5. In paragraph 2, An operation of transmitting a third message (Request FPP confirm) to the second UWB device to confirm the authenticity of the FFP; and A method further comprising the action of receiving a fourth message (FPP accept / Deny) including information regarding the authenticity of the FFP from the second UWB device.

6. In paragraph 5, the third message is, A method characterized by including a transmission time (Message Tx Time) and a random number (Random number) for the first message.

7. In paragraph 1, A method characterized in that the first UWB device is implemented as a mobile device and the second UWB device is implemented as a gate device.

8. In the method of the second UWB (ultra wide band) device, An operation of receiving a transaction initiation message from the first UWB device via UWB communication when the first UWB device enters a transaction area set to the second UWB device based on location estimation based on DL-TDoA (downlink-TDoA); An operation of transmitting a transaction request message to the first UWB device via UWB communication and receiving a transaction response message corresponding to the transaction request message from the first UWB device via UWB communication; and A method characterized by comprising an operation of performing double-sided two-way ranging (DS-TWR) to determine whether the first UWB device moves outside the transaction area when a transaction between the first UWB device and the second UWB device is completed.

9. In paragraph 8, A method characterized in that when a transaction between the first UWB device and the second UWB device is completed, the method further comprises the action of transmitting a first message including information regarding free pass permission (FFP) to the first UWB device.

10. In paragraph 9, the information regarding the FFP is: A method characterized by including a transmission time (Message Tx Time) and a random number (Random number) for the first message.

11. In paragraph 9, An operation for determining that the first UWB device has moved out of the transaction area based on the DS-TWR; and A method further comprising receiving a second message from the first UWB device, the second message including a flag indicating that the first UWB device has moved out of the transaction area.

12. In paragraph 9, An operation of receiving a third message (Request FPP confirm) for confirming the authenticity of the FFP from the first UWB device; and A method further comprising the action of transmitting a fourth message (FPP accept / Deny) including information regarding the authenticity of the FFP to the first UWB device.

13. In paragraph 12, the third message is, A method characterized by including a transmission time (Message Tx Time) and a random number (Random number) for the first message.

14. In the first UWB (ultra wide band) device, Transmitter and receiver; and comprising a control unit, said control unit comprising: Estimate the location of the first UWB device based on DL-TDoA (downlink-TDoA), When the first UWB device enters a transaction area set to the second UWB device based on the above location estimation, a transaction initiation message is transmitted to the second UWB device via UWB communication, Receive a transaction request message from the second UWB device via UWB communication, and transmit a transaction response message corresponding to the transaction request message to the second UWB device via UWB communication; A device characterized in that, when a transaction between the first UWB device and the second UWB device is completed, it performs DS-TWR (Double-sided two-way ranging) to determine whether the first UWB device moves outside the transaction area.

15. In the second UWB (ultra wide band) device, Transmitter and receiver; and comprising a control unit, said control unit comprising: When the first UWB device enters a transaction area set to the second UWB device based on location estimation based on DL-TDoA (downlink-TDoA), a transaction initiation message is received from the first UWB device via UWB communication, Transmitting a transaction request message to the first UWB device via UWB communication, and receiving a transaction response message corresponding to the transaction request message from the first UWB device via UWB communication, A device characterized in that, when a transaction between the first UWB device and the second UWB device is completed, it performs DS-TWR (Double-sided two-way ranging) to determine whether the first UWB device moves outside the transaction area.

Images