Logical access method and device using ultra wide band communication
The UWB-based logical access method and device facilitate efficient and secure service execution in IoT environments by using UWB communication for device discovery and ranging, addressing the need for seamless and secure connections between devices in IoT settings.
Patent Information
- Application Number
- PCT/KR2024/006653
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-17
- Filing Date
- 2024-05-16
- Publication Date
- 2024-11-21
AI Technical Summary
In IoT environments, there is a need for efficient methods to provide logical access and seamless service execution between devices, particularly in scenarios where precise distance measurement and secure authentication are required, such as in smart homes and connected devices, which existing technologies struggle to address effectively.
The implementation of a logical access method and device using Ultra-WideBand (UWB) communication, which enables device discovery, ranging, and secure service execution by determining if the distance between UWB devices is within a threshold, allowing for automatic login and service connection without user intervention through UWB ranging and secure channel establishment.
This solution simplifies the logical access procedure, enables seamless service connection based on user movement, and ensures secure authentication by using UWB communication for precise distance measurement and secure channel setup, enhancing user experience and service availability in IoT environments.
Smart Images

Figure KR2024006653_21112024_PF_FP_ABST
Abstract
Description
Logical access method and device using ultra-wideband communication
[0001] The present disclosure relates to UWB communication, and more particularly, to a logical access method and device via UWB communication.
[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, a variety of services become available, creating a need for effective solutions to deliver these services. For example, ranging technology, which measures the distance between electronic devices using Ultra Wide Band (UWB), can be used.
[0005] The present disclosure provides a method and device for logical access via UWB communication.
[0006] A method for operating a first UWB (ultra wide band) device according to one embodiment of the present disclosure may include: discovering a second UWB device through device discovery based on BLE (Bluetooth low energy) communication or UWB communication; and performing UWB ranging with the second UWB device to determine whether a distance between the first UWB device and the second UWB device is less than or equal to a threshold value. At this time, if the distance between the first UWB device and the second UWB device according to the UWB ranging result is less than or equal to the threshold value, a device login or service execution procedure supported by the second UWB device may be performed.
[0007] A method for operating a second UWB (ultra wide band) device according to one embodiment of the present disclosure may include: discovering a first UWB device through device discovery based on BLE (Bluetooth low energy) communication or UWB communication; performing UWB ranging with the first UWB device to determine whether a distance between the first UWB device and the second UWB device is less than or equal to a threshold value; and performing a device login or service execution procedure supported by the second UWB device if the distance between the first UWB device and the second UWB device according to the UWB ranging result is less than or equal to the threshold value.
[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 can discover a second UWB device through device discovery based on BLE (Bluetooth low energy) communication or UWB communication, and perform UWB ranging with the second UWB device to determine whether a distance between the first UWB device and the second UWB device is less than or equal to a threshold value. If the distance between the first UWB device and the second UWB device according to the UWB ranging result is less than or equal to the threshold value, a device login or service execution procedure supported by the second UWB device can be performed.
[0009] A second UWB (ultra wide band) device according to one embodiment of the present disclosure includes a transceiver; and a control unit. The control unit discovers a first UWB device through device discovery based on BLE (Bluetooth low energy) communication or UWB communication, performs UWB ranging with the first UWB device to determine whether a distance between the first UWB device and the second UWB device is less than or equal to a threshold value, and if the distance between the first UWB device and the second UWB device according to the UWB ranging result is less than or equal to the threshold value, performs a device login or service execution procedure supported by the second UWB device.
[0010] The method and device according to the embodiment of the present disclosure can simplify the logical access procedure using UWB communication.
[0011] The method and device according to the embodiment of the present disclosure can seamlessly connect services to nearby devices according to the movement of the user.
[0012] FIG. 1 illustrates an exemplary architecture of a UWB device according to an embodiment of the present disclosure.
[0013] FIG. 2 illustrates an exemplary configuration of a framework of a UWB device according to an embodiment of the present disclosure.
[0014] FIG. 3 illustrates a method for multiple electronic devices to perform communication according to an embodiment of the present disclosure.
[0015] FIG. 4 is a diagram for explaining a CTAP (client to authenticator protocol) of FIDO (fast identity online) according to an embodiment of the present disclosure.
[0016] FIG. 5 illustrates a system including an AC (access credential) device and an AC reader according to an embodiment of the present disclosure.
[0017] FIG. 6 is a diagram for explaining a device automatic login / logout method according to one embodiment of the present disclosure.
[0018] FIG. 7A and FIG. 7B are diagrams for explaining a website automatic login / logout method according to one embodiment of the present disclosure.
[0019] FIG. 8a, FIG. 8b, and FIG. 8c are diagrams for explaining a session transfer method according to one embodiment of the present disclosure.
[0020] FIG. 9 is a diagram for explaining a session transfer method according to another embodiment of the present disclosure.
[0021] FIG. 10 is a device diagram of a first UWB device according to one embodiment of the present disclosure.
[0022] FIG. 11 is a device diagram of a second UWB device according to one embodiment of the present disclosure.
[0023] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.
[0024] 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.
[0025] 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.
[0026] 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.
[0027] 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).
[0028] 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.
[0029] 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 in 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.
[0030] 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.
[0031] 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.
[0032] 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.
[0033] 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.
[0034] 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.
[0035] According to the FCC (Federal Communications Commission) definition, UWB can refer to a wireless communication technology that uses a bandwidth of 500 MHz or more, or a bandwidth corresponding to a center frequency of at least 20%. 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 position estimation based on the distance between two devices, or precise position estimation of a device based on the distance from a fixed device (of known location).
[0036] 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.
[0037] A "Controller" may be a Ranging Device that defines and controls Ranging Control Messages (RCM) (or control messages).
[0038] A "Controllee" may be a Ranging Device that utilizes the ranging parameters within the RCM (or control message) received from the Controller.
[0039] 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.
[0040] 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.
[0041] 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.
[0042] 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.
[0043] 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.
[0044] 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.
[0045] A "Service" can be an implementation of a use case that provides a service to an end-user.
[0046] 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.
[0047] A "Global Dedicated File (GDF)" may be the root level of application specific data containing the data required to establish a USB session.
[0048] The "Framework API" may be an API used by a UWB-enabled Application to communicate with the Framework.
[0049] An "Initiator" may be a Ranging Device that initiates a ranging exchange.
[0050] An "Object Identifier (OID)" may be an identifier for an Application Dedicated File (ADF) within an application data structure. 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.
[0051] "Out-Of-Band (OOB)" may be data communication that does not use UWB as the underlying wireless technology.
[0052] "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.
[0053] A "Responder" may be a Ranging Device that responds to an Initiator in a ranging exchange.
[0054] "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.
[0055] 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.
[0056] A "Secure Channel" may be a data channel that prevents overhearing and tampering.
[0057] 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.
[0058] A "Secure Element (SE)" may be a tamper-resistant secure hardware component that can be used as a Secure Component within a Ranging Device.
[0059] "Secure Ranging" may be ranging based on STS generated through strong cryptographic operations.
[0060] 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).
[0061] "Service Data" may be data defined by the Service Provider that needs to be passed between two ranging devices to implement the service.
[0062] 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.
[0063] "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.
[0064] A "UWB Service" may be a software component that provides access to UWBS.
[0065] 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.
[0066] "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.
[0067] 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.
[0068] The "UWB Subsystem (UWBS)" may be a hardware component that implements the UWB PHY and MAC layers (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.
[0069] A “UWB message” may be a message containing a payload IE transmitted by a UWB device (e.g., ERDEV).
[0070] A “ranging message” may be a message transmitted by a UWB device (e.g., ERDEV) in a UWB ranging procedure. For example, the ranging message may be a message such as a ranging initiation message (RIM), a ranging response message (RRM), a ranging final message (RFM), or a measurement report message (MRM) transmitted by a UWB device (e.g., ERDEV) in a specific phase of a ranging round. The ranging message may include one or more UWB messages. If necessary, multiple ranging messages may be merged into a single message. For example, in the case of non-deferred DS-TWR ranging, RFM and MRM may be merged into a single message in the ranging final phase.
[0071] “Payload IE” may be called Payload Information Element and may be included in the MAC payload of the UWB MAC frame defined in IEEE 802.15.4 / 4z. The MAC payload may include multiple Payload IEs.
[0072] "Data Transfer IE" may be an additional payload IE for transmitting application data. The application data may be data transmitted from a framework or application above the UWB MAC Layer. The Data Transfer IE may be used in a procedure in which the Initiator and the Responder range with each other. In this case, the ranging message may include at least one or both of the payload IE for ranging and the Data Transfer IE for transmitting application data. For example, the Data Transfer IE may be transmitted as part of the payload IE of the MAC payload of a Ranging Initiation Message (RIM), a Ranging Response Message (RRM), a Ranging Final Message (RFM), a Measurement Report Message (MRM), and a Ranging Result Report Message (RRRM). The Data Transfer IE can also be delivered as a payload IE in the MAC payload of a DTM. For example, the Data Transfer IE can be delivered in addition to the DTM payload IE in the MAC payload portion of a Poll DTM, Response DTM, or Final DTM.
[0073] The "UWB channel" may be one of the candidate UWB channels allocated for UWB communication. The candidate UWB channels allocated for UWB communication may be channels allocated for UWB communication defined in IEEE 802.15.4 / 4z. The UWB channel may be used for UWB ranging and / or transactions. For example, the UWB channel may be used for transmitting and receiving ranging frames (RFRAME) and / or transmitting and receiving data frames.
[0074] "One-way ranging (OWR)" may be a ranging method that utilizes the time difference of arrival (TDoA) localization method. The TDoA method is a method for locating a mobile device (tagged device) based on the relative arrival times of a single message or multiple messages. For a description of OWR (TDoA), refer to the description in IEEE 802.15.4z. An example of an OWR method may include the Uplink (UL)-TDoA method.
[0075] “Two-way ranging (TWR)” may be a ranging method that can estimate the relative distance between two devices by measuring the time of flight (ToF) through the exchange of ranging messages between the two devices. The TWR method may be either double-sided two-way ranging (DS-TWR) or single-sided two-way ranging (SS-TWR). SS-TWR may be a procedure that performs ranging through a single round-trip time measurement. DS-TWR may be a procedure that performs ranging through two round-trip time measurements. For a description of SS-TWR and DS-TWR, please refer to the description of IEEE 802.15.4z.
[0076] “DL-TDoA” may be called Downlink Time Difference of Arrival (DL-TDoA), reverse TDoA, and when multiple anchor devices broadcast messages or exchange messages with each other, the basic operation may be for a user device (tag device) to overhear the messages of the anchor devices. A user device performing DL-TDoA operation may overhear messages transmitted by two anchor devices and calculate a Time Difference of Arrival (TDoA) proportional to the difference in distance between each anchor device and the user device. The user device may use the TDoA with multiple pairs of anchor devices to calculate the relative distance to the anchor devices and use it for positioning. The operation of the anchor device for DL-TDoA may be similar to the DS-TWR (Double Side-Two Way Ranging) defined in IEEE 802.15.4z, and may further include other useful time information so that the user device can calculate the TDoA. In the present disclosure, DL-TDoA may be referred to as DL-TDoA localization.
[0077] An "Anchor device" may be called an anchor, UWB anchor, or UWB anchor device, and may be a UWB device deployed in a specific location to provide positioning services. For example, an anchor device may be a UWB device installed by a service provider on an indoor wall, ceiling, structure, etc. to provide indoor positioning services. Anchor devices may also be classified as Initiator anchors or Responder anchors depending on the order and role of message transmission.
[0078] The "Initiator anchor" may be referred to as the Initiator UWB anchor, Initiator anchor device, etc., and may signal the start of a specific ranging round. The Initiator anchor may also schedule ranging slots in which Responder anchors operating in the same ranging round respond. The initiation message of the Initiator anchor may be referred to as the Initiator DTM (Downlink TDoA Message) or Poll message. The initiator message may include a transmission timestamp. The Initiator anchor may additionally transmit a finalization message after receiving responses from Responder anchors. The finalization message of the Initiator anchor may be referred to as the Final DTM or Final message. The finalization message may include a reply time for the messages sent by Responder anchors. The finalization message may include a transmission timestamp.
[0079] A "Responder anchor" may be referred to as a Responder UWB anchor, a Responder UWB anchor device, or a Responder anchor device. A Responder anchor may be a UWB anchor that responds to an initiator anchor's initiation message. The message to which the Responder anchor responds may include a response time to the initiation message. The message to which the Responder anchor responds may be referred to as a Responder DTM, a Response message. The Responder anchor's response message may also include a transmission timestamp.
[0080] 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.
[0081] Various embodiments of the present disclosure are described below with reference to the attached drawings.
[0082] FIG. 1 illustrates an exemplary architecture of a UWB device according to an embodiment of the present disclosure.
[0083] In the present disclosure, the UWB device (100) may be an electronic device supporting UWB communication. The UWB device (100) may be, for example, a Ranging Device supporting UWB ranging. In 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.
[0084] In the embodiment of FIG. 1, a UWB device (100) can interact with another UWB device through a UWB session.
[0085] The UWB device (100) may implement a first interface (Interface #1), which is an interface between a UWB-enabled application (110) and a UWB Framework (120), and the first interface may enable the UWB-enabled application (110) on the UWB device (100) to use the UWB capabilities of the UWB device (100) in a predetermined manner. In one embodiment, the first interface may be, but is not limited to, a Framework API or a proprietary interface.
[0086] The UWB device (100) may implement a second interface (Interface #2), which is an interface between the UWB Framework (110) and the UWB subsystem (UWBS) (130). In one embodiment, the second interface may be, but is not limited to, the UWB Command Interface (UCI) or a proprietary interface.
[0087] Referring to FIG. 1, a UWB device (100) may include a UWB-enabled Application (110), a Framework (UWB Framework) (120), and / or a UWBS (130) including a UWB MAC Layer and a UWB Physical Layer. In one embodiment, some entities may not be included in the UWB device, or additional entities (e.g., a security layer) may be included.
[0088] A UWB-enabled Application (110) can trigger the establishment of a UWB session by a UWBS (130) using the first interface. In one embodiment, the UWB-enabled Application (110) can use one of the predefined profiles. For example, the UWB-enabled Application (110) can use one of the profiles defined in FiRa or a custom profile. The UWB-enabled Application (110) can use the first interface to handle relevant events such as service discovery, ranging notifications, and / or error conditions.
[0089] Framework (120) may provide access to Profile, individual UWB settings, and / or notifications. In one embodiment, Framework (120) may support at least one of the following functions: UWB ranging and transaction execution, providing an interface to an application and UWBS (130), or estimating the location of the device (100). Framework (120) may be a collection of software components. As described above, UWB-enabled Application (110) may interface with Framework (120) via a first interface, and Framework (120) may interface with UWBS (130) via a second interface.
[0090] Meanwhile, in the present disclosure, the UWB-enabled Application (110) and / or Framework (120) may be implemented by an application processor (AP) (or processor). Therefore, in the present disclosure, the operations of the UWB-enabled Application (110) and / or Framework (120) may be understood to be performed by the AP (or processor). In the present disclosure, the Framework may be referred to as an AP or a processor.
[0091] The UWBS (130) may be a hardware component including a UWB MAC Layer and a UWB Physical Layer. The UWBS (130) may perform UWB session management and communicate with the UWBS of another UWB device. The UWBS (130) may interface with the Framework (120) through a second interface and obtain secure data from the Secure Component. In one embodiment, the Framework (or application processor) (120) may transmit a command to the UWBS (130) through UCI, and the UWBS (130) may transmit a response to the command to the Framework (120). The UWBS (130) may also transmit a notification to the Framework (120) through UCI.
[0092] FIG. 2 illustrates an exemplary configuration of a framework of a UWB device according to an embodiment of the present disclosure.
[0093] The UWB device of FIG. 2 may be an example of the UWB device (100) of FIG. 1.
[0094] Referring to FIG. 2, the Framework (220) may include software components such as, for example, a Profile Manager (221), an OOB Connector(s) (222), a Secure Service (223), and / or a UWB Service (224).
[0095] The Profile Manager (221) may be responsible for managing profiles available on the UWB device. Here, a profile may be a set of parameters required to establish communication between UWB devices. For example, the profile may include parameters indicating which OOB secure channel is used, UWB / OOB configuration parameters, parameters indicating whether the use of a specific security component is mandatory, and / or parameters related to the file structure of the ADF. The UWB-enabled Application (210) may communicate with the Profile Manager (221) via a first interface (e.g., Framework API).
[0096] The OOB Connector (222) may serve to establish an OOB connection with another device. The OOB Connector (222) may handle an OOB phase, including a discovery phase and / or a connection phase. An OOB component (e.g., a BLE component) (250) may be connected to the OOB Connector (222).
[0097] Secure Service (223) can perform the role of interfacing with Secure Component (240) such as SE or TEE.
[0098] The UWB Service (224) can perform the role of managing the UWBS (230). By implementing the second interface, the UWB Service (224) can provide access from the Profile Manager (221) to the UWBS (230).
[0099] FIG. 3 illustrates a method for multiple electronic devices to perform communication according to an embodiment of the present disclosure.
[0100] The first electronic device (301) and the second electronic device (302) of FIG. 3 may be, for example, the UWB device of FIG. 1 or FIG. 2.
[0101] Referring to FIG. 3, the first electronic device (301) and the second electronic device (302) can perform a device discovery / connection establishment procedure (310) and a data communication procedure (320). The device discovery / connection establishment procedure (310) and the data communication procedure (320) can be managed or controlled by a MAC layer (entity) of the electronic device.
[0102] (1) Device search / connection setup procedure
[0103] In the present disclosure, the device discovery / connection setup procedure (310) may be a pre-procedure performed prior to the data communication procedure (320). As an example, the device discovery / connection setup procedure (310) may be performed via OOB communication (channel), NB communication (channel), and / or UWB communication (channel).
[0104] The device discovery / connection setup procedure (310) may include at least one of the following operations.
[0105] - Device discovery operation: An operation in which an electronic device searches for (discovers) another UWB device. The device discovery operation may include an operation of transmitting / receiving an Advertisement message. In the present disclosure, the device discovery operation may be a discovery operation or an advertising operation.
[0106] - Connection establishment operation: An operation in which two electronic devices establish a connection. The connection establishment operation may include an operation in which a connection request message and a connection confirmation message are transmitted / received. The connection (channel) established through the connection establishment operation may be used to establish and control a UWB session for data communication. For example, parameters for establishing a UWB session (e.g., UWB performance parameters (control performance parameters), UWB configuration parameters, session key related parameters) may be negotiated between the two electronic devices through a secure channel established through the connection establishment operation.
[0107] (2) Data communication procedures
[0108] In the present disclosure, the data communication procedure (320) may be a procedure for transmitting and receiving data using UWB communication. As an example, the data communication procedure may be performed using UWB communication or NB communication.
[0109] The data communication procedure (320) may include at least one of the following operations.
[0110] - UWB ranging operation: An operation in which an electronic device performs UWB ranging with another electronic device using a preset UWB ranging method (e.g., OWR, SS-TWR, DS-TWR method). As an example, the UWB ranging operation may include a ToF measurement operation and / or an AoA measurement operation.
[0111] - Transaction operation: An operation in which an electronic device exchanges service data with another electronic device.
[0112] Meanwhile, active research is underway into methods for automatically logging into a target device (e.g., a laptop or personal computer) through user authentication on an electronic device (e.g., a mobile device or wearable device). For example, when a user of an electronic device approaches a target device, a login operation for the device and / or services on the target device can be automatically performed. This can enhance the user experience (UX) and enable seamless and automatic connection of services based on the user's movements.
[0113] The present disclosure proposes a method for automatically logging into a device and / or service within a target device when a user (or electronic device) moves near the target device, even without separate user authorization, by utilizing the secure ranging function of UWB. In addition, embodiments of the present disclosure can provide a method for automatically logging off a device and / or service within the target device when a user (or electronic device) moves away from the target device, by utilizing the precise ranging function of UWB (static, provisioned ranging).
[0114] For example, when a user (or electronic device) moves into proximity to a target device, such as a PC, the electronic device and / or the target device can control the PC login (e.g., Windows unlock) to be performed automatically using the UWB function.
[0115] For example, when a user (or electronic device) moves into proximity to a target device, the electronic device and / or the target device can be controlled to automatically log in to a website within the target device using the UWB function.
[0116] For example, when a user (or electronic device) moves into proximity to a target device, the electronic device and / or the target device can control a service transfer between the target device and the electronic device using the UWB function.
[0117] FIG. 4 is a diagram for explaining a CTAP (client to authenticator protocol) of FIDO (fast identity online) according to an embodiment of the present disclosure.
[0118] FIDO (Fast Identity Online) is an authentication method that utilizes biometric technology in an online environment. Instead of transmitting authentication data to a server, FIDO generates an authentication result value through the client's authentication device (e.g., a USB (universal serial bus), mobile phone, or wearable device), transmits it to the server (or FIDO server), and the server (or FIDO server) verifies the authentication result value. This can be a simple and secure authentication technology.
[0119] Among the authentication standards proposed by the FIDO Alliance, a technical standards organization for FIDO, the UAF (universal authentication framework) may be an authentication standard method that authenticates users through biometric information such as fingerprints, voice, or facial recognition without using a password. Among the authentication standards proposed by the FIDO Alliance, the U2F (universal 2nd factor) may be a two-factor authentication method that uses a separate authentication device such as a USB or smart card that stores additional security information in addition to the existing ID and password authentication method.
[0120] Electronic devices can use the UAF protocol to provide security through the user's biometric information without using a password in online services.
[0121] A user of an electronic device can register the electronic device with a service (or server) by selecting a local authentication mechanism, such as swiping a finger, looking at a camera, speaking into a microphone, entering a personal identification number (PIN), or a combination thereof.
[0122] Electronic devices can use the UAF protocol to select the mechanism provided to the user by the service. Once the electronic device is registered with the service (or server), the user only needs to repeat the local authentication action each time they need to authenticate to that service, and there's no longer a need to enter a password when authenticating on the electronic device.
[0123] FIDO 2.0 is a technology that enables biometric authentication in all online environments, including PCs as well as mobile devices. In addition to the existing UAF and U2F, FIDO 2.0 proposes WebAuthn (Web Authentication) and CTAP (Client-to-Authenticator Protocol). CTAP enables the use of FIDO authentication services in web environments on PCs and mobile devices without the need for separate program installation.
[0124] Referring to FIG. 4, the system may include a target device (410) (e.g., a PC), an application server (420) that provides applications / services to the target device (410), a FIDO server (430), and an authentication device (440) (e.g., a universal serial bus (USB), a mobile phone, or a wearable device).
[0125] The authentication device (440) can perform a registration process by transmitting a first message (or makeCredential message) containing a stored user certificate to the FIDO server (430).
[0126] The authentication device (440) can perform an authentication process (or a private key signing process) by transmitting a second message (getAssertion message) containing a value signed with a user's private key within the device to the FIDO server (430). The FIDO server (430) can extract electronic signature information within the received second message (getAssertion message) and verify the electronic signature.
[0127] In this disclosure, a technology for introducing UWB technology to FIDO CTAP is proposed. When an authentication device (440) supporting UWB communication (e.g., a mobile device, a wearable device, etc.) approaches a target device (410) (e.g., a PC), the authentication device (440) can automatically be authorized to access devices and / or services (e.g., a website) within the target device (410) through a local authentication action utilizing the user's biometric information without requiring an additional plug-in to the target device (410).
[0128] According to one embodiment, the authentication device (440) may perform website credential transmission and distance measurement using a hybrid session via UWB, and control an automatic login function for a device and / or service to be performed on the target device (410) when a condition is satisfied.
[0129] FIG. 5 illustrates a system including an AC (access credential) device and an AC reader according to an embodiment of the present disclosure.
[0130] Referring to FIG. 5, the system (500) includes an access credential (AC) device (510), an access credential (AC) reader (520), and an application / web service server (530).
[0131] The AC device (510) may be implemented as any one of the UWB device (100) of FIG. 1, the UWB device of FIG. 2, the first electronic device (301) of FIG. 3, or the second electronic device (302). The AC device (510) may be an authentication device for logical access and may be a device requesting authentication.
[0132] The AC device (510) may include an AC (access credential) application (511), a FiRa CSML (common service management layer) framework (512), BLE connectivity (513), a secure component (514), and a UWB subsystem (515).
[0133] The AC application (511) can perform and / or control communication between the AC device (510) and the application / web service server (530).
[0134] The FiRa CSML framework (512) can be implemented as the UWB Framework (120) of FIG. 1 or the Framework (220) of FIG. 2. The FiRa CSML framework (512) can be a collection of logical software components for CSML defined in FiRa. The AC device (510) can support secure channel setup defined in CSML.
[0135] BLE connectivity (513) can perform the same or substantially the same function as the OOB component (250) of Fig. 2. BLE connectivity (513) can perform BLE communication with the BLE connectivity (523) of the AC reader (520) to exchange data and / or messages.
[0136] The secure component (514) can perform the same or substantially the same function as the secure component (240) of FIG. 2.
[0137] The UWB subsystem (515) may perform the same or substantially the same function as the UWBS (130) of FIG. 1 or the UWBS (230) of FIG. 2. The UWB subsystem (515) may perform UWB communication with the UWB subsystem (525) of the AC reader (520) to exchange data and / or messages.
[0138] The AC reader (520) may be implemented as any one of the UWB device (100) of FIG. 1, the UWB device of FIG. 2, the first electronic device (301) of FIG. 3, or the second electronic device (302). The AC reader (520) may be a device for logical access and may be a device that reads access credentials.
[0139] The AC reader (520) may include an access service application (521), a Logical Access Framework (522), BLE connectivity (523), an on-device authentication module (524), and a UWB subsystem (525).
[0140] The access service application (521) can perform and / or control communication between the AC reader (520) and the application / web service server (530).
[0141] The Logical Access Framework (522) can be implemented as the UWB Framework (120) of FIG. 1 or the Framework (220) of FIG. 2. The Logical Access Framework (522) can support the Logical Access Service defined in FiRa. The Logical Access Framework (522) can support the FIDO UAF (Universal Authentication Framework) to register the AC device (510) and / or AC reader (520) with the application / web service server (530) (or web service).
[0142] BLE connectivity (523) can perform the same or substantially the same function as the OOB component (250) of Fig. 2. BLE connectivity (523) can perform BLE communication with the BLE connectivity (513) of the AC device (510) to exchange data and / or messages.
[0143] An on-device authentication module (524) can perform authentication procedures for devices and / or services within the AC reader (520).
[0144] The UWB subsystem (525) may perform the same or substantially the same function as the UWBS (130) of FIG. 1 or the UWBS (230) of FIG. 2. The UWB subsystem (525) may perform UWB communication with the UWB subsystem (515) of the AC device (510) to exchange data and / or messages.
[0145] The application / web service server (530) may provide applications and / or web services to the AC device (510) or the AC reader (520). In one embodiment, the application / web service server (530) may perform authentication-related procedures for devices and / or services requested by the AC device (510) and / or the AC reader (520) through communication with the AC application (511) and / or the access service application (521).
[0146] FIG. 6 is a diagram for explaining a device automatic login / logout method according to one embodiment of the present disclosure.
[0147] Referring to FIG. 6, the AC device (610) may be implemented as any one of the UWB device (100) of FIG. 1, the UWB device of FIG. 2, the first electronic device (301), the second electronic device (302) of FIG. 3, or the AC device (510) of FIG. 5. The AC reader (620) may be implemented as any one of the UWB device (100) of FIG. 1, the UWB device of FIG. 2, the first electronic device (301), the second electronic device (302) of FIG. 3, or the AC reader (520) of FIG. 5.
[0148] In one embodiment, the AC device (610) and the AC reader (620) may support a user authentication method (e.g., fingerprint or iris recognition). In one embodiment, the AC device (610) and the AC reader (620) may support a secure channel setup defined in CSML. In one embodiment, the AC device (610) and the AC reader (620) may support DS-TWR.
[0149] In operation 601, the AC device (610) and the AC reader (620) may perform a device register procedure between the two. In one embodiment, the device register procedure between the AC device (610) and the AC reader (620) may be performed in advance.
[0150] In operation 603, the AC device (610) and the AC reader (620) may perform a device discovery procedure via BLE or contention-based UWB. In one embodiment, the AC device (610) may discover the AC reader (620) via BLE or contention-based UWB. In one embodiment, the AC reader (620) may discover the AC device (610) via BLE or contention-based UWB.
[0151] In operation 605, the AC device (610) and the AC reader (620) may establish a secure channel for communication between the two parties. In one embodiment, the secure channel may be a data channel that prevents overhearing and tampering. In one embodiment, the AC device (610) and / or the AC reader (620) may create the secure channel by utilizing a key received during device registration in operation 601 after in-device authentication (e.g., user biometric verification).
[0152] According to one embodiment, the AC device (610) and / or the AC reader (620) may use a key resulting from a device register procedure as a session key to generate an STS value of UWB secure ranging of operation 605 (secure channel setup).
[0153] In one embodiment, a secure channel can be created over a FiRa BLE generic attribute profile (GATT) service.
[0154] In one embodiment, a secure channel may be established by transmitting an Application Protocol Data Unit (APDU) command over the UWB In-band. The APDU command may be a command used when communicating with an Application Data Structure within a UWB device.
[0155] In operation 607, the AC device (610) and the AC reader (620) can determine whether the distance between the AC device (610) and the AC reader (620) is less than or equal to a threshold value based on a UWB device detection procedure through UWB ranging (user presence confirmation). In one embodiment, the AC device (610) and the AC reader (620) can determine whether the distance between the AC device (610) and the AC reader (620) is less than or equal to a threshold value by performing double-sided two-way ranging (DS-TWR). In one embodiment, the AC device (610) and the AC reader (620) can determine whether the distance between the AC device (610) and the AC reader (620) is less than or equal to a threshold value based on a provisioned STS (user presence confirmation). In one embodiment, the AC device (610) and the AC reader (620) can determine whether the distance between the AC device (610) and the AC reader (620) is less than or equal to a threshold value based on dynamic STS (user presence confirmation).
[0156] If it is determined in operation 607 that the distance between the AC device (610) and the AC reader (620) is less than or equal to a threshold value, in operation 609, the AC reader (620) may perform and / or complete a device login operation.
[0157] In operation 611, the AC leader (620) may wait until there is no input for a certain period of time.
[0158] If there is no input within the AC leader (620) for a certain period of time in operation 611, the AC leader (620) may transmit a Poll message to the AC device (610) in operation 613. In operation 615, the AC device (610) may transmit a Response message corresponding to the Poll message to the AC leader (620). In one embodiment, the AC leader (620) may wait for a certain period of time if a corresponding Response message is not received after transmitting the Poll message.
[0159] In operation 617, the AC leader (620) can calculate the distance between the AC leader (620) and the AC device (610) based on the Poll message and the Response message.
[0160] In operation 619, the AC leader (620) may perform and / or complete a device log off operation if the distance between the AC leader (620) and the AC device (610) according to the calculation result of operation 617 is greater than or equal to a threshold value, or if a corresponding Response message is not received for a set time after transmitting a Poll message.
[0161] FIG. 7A and FIG. 7B are diagrams for explaining a website automatic login / logout method according to one embodiment of the present disclosure.
[0162] Referring to FIGS. 7A and 7B, the system may include an AC device (710), an AC reader (720), a web server (730), and a FIDO server (740).
[0163] The AC device (710) may be implemented as any one of the UWB device (100) of FIG. 1, the UWB device of FIG. 2, the first electronic device (301), the second electronic device (302) of FIG. 3, or the AC device (510) of FIG. 5. The AC reader (720) may be implemented as any one of the UWB device (100) of FIG. 1, the UWB device of FIG. 2, the first electronic device (301), the second electronic device (302) of FIG. 3, or the AC reader (520) of FIG. 5.
[0164] In one embodiment, the AC device (710) and the AC reader (720) may operate according to the FIDO and CTAP standard specifications. In one embodiment, the AC device (710) and the AC reader (720) may support a user authentication method (e.g., fingerprint or iris recognition). In one embodiment, the AC device (710) and the AC reader (720) may support secure ranging using Dynamic STS or Provisioned STS. In one embodiment, secure ranging may be an alternative user authentication method depending on the security requirements of the web server (730).
[0165] In operation 701, the AC device (710) and the AC reader (720) may perform a device discovery procedure. In one embodiment, the AC device (710) and the AC reader (720) may perform the device discovery procedure via BLE or contention-based UWB.
[0166] In operation 703, the AC device (710) and the AC reader (720) may perform a user authentication procedure. According to one embodiment, the AC device (710) may transmit authentication information including at least one of biometric information, a PIN, and a password to the AC reader (720) to perform the user authentication procedure. According to one embodiment, the AC device (710) may transmit the authentication information to the AC reader (720) via FiRa BLE generic attribute profile (GATT) or BLE logical link control and adaptation protocol (L2CAP) or UWB In-band.
[0167] In one embodiment, the AC device (710) and the AC reader (720) can set up a secure channel for communication between them.
[0168] In operation 705, the AC device (710) and the AC reader (720) can determine whether the distance between the AC device (710) and the AC reader (720) is less than or equal to a threshold value based on a UWB device detection procedure through UWB ranging (user presence confirmation). In one embodiment, the AC device (710) and the AC reader (720) can determine whether the distance between the AC device (710) and the AC reader (720) is less than or equal to a threshold value by performing double-sided two-way ranging (DS-TWR). In one embodiment, the AC device (710) and the AC reader (720) can determine whether the distance between the AC device (710) and the AC reader (720) is less than or equal to a threshold value based on a provisioned STS (user presence confirmation). In one embodiment, the AC device (710) and the AC reader (720) can determine whether the distance between the AC device (710) and the AC reader (720) is less than or equal to a threshold value based on dynamic STS (user presence confirmation).
[0169] If it is determined in operation 705 that the distance between the AC device (710) and the AC reader (720) is less than or equal to a threshold value, in operation 707, the AC reader (720) may perform and / or complete a device login operation.
[0170] Thereafter, the AC device (710) and the AC reader (720) can perform at least one of user authentication method A and user authentication method B. According to one embodiment, the AC device (710) and the AC reader (720) can selectively perform user authentication method A or user authentication method B depending on the security requirements of the service. According to one embodiment, the AC device (710) and the AC reader (720) can perform both user authentication method A and user authentication method B.
[0171] <User Authentication Method A>
[0172] In operation 709, at least one of the AC device (710), the AC reader (720), the web server (730), and the FIDO server (740) may perform a register procedure. In one embodiment, the AC device (710) and / or the AC reader (720) may transmit a user certificate stored in the device to the web server (730) and / or the FIDO server (740) via a secure channel. In one embodiment, the AC device (710) and / or the AC reader (720) may transmit and receive an APDU command including the user certificate via the device UWB.
[0173] In operation 711, the AC leader (720) may transmit a user authentication request message to the AC device (710).
[0174] In operation 713, the AC device (710) may perform a user authentication procedure. For example, the AC device (710) may perform a user authentication procedure through the user's fingerprint or iris recognition.
[0175] In operation 715, the AC device (710) may transmit an authentication result value to the AC reader (720). According to one embodiment, the authentication result value may be transmitted by being included in a UWB command set within FIDO CTAP.
[0176] In operation 717, at least one of the AC device (710), the AC reader (720), the web server (730), and the FIDO server (740) may perform an authentication procedure (private key signing). In one embodiment, the AC device (710) and / or the AC reader (720) may transmit signature information (or a value signed with the user's private key) to the web server (730) and / or the FIDO server (740). In one embodiment, the FIDO server (740) may extract the received signature information (or a value signed with the user's private key) and verify the electronic signature.
[0177] <User Authentication Method B>
[0178] In operation 719, at least one of the AC device (710), the AC reader (720), and the web server (730) may register the AC device (710) as a user authentication device with the web server (730). In one embodiment, the AC device (710), the AC reader (720), and the web server (730) may share the same session key.
[0179] In operation 721, the AC device (710) and the AC reader (720) can measure the distance between themselves through UWB ranging and check whether the distance between the AC device (710) and the AC reader (720) is below a threshold value (user presence confirmation). In one embodiment, the AC device (710) and the AC reader (720) can perform secure ranging based on the STS code generated using the session key exchanged in operation 719.
[0180] In operation 723, at least one of the AC device (710), the AC reader (720), and the web server (730) may perform a user authentication procedure using the STS code.
[0181] After performing at least one of user authentication method A and user authentication method B, in operation 725, at least one of the AC device (710), the AC reader (720), the web server (730), and the FIDO server (740) may perform a related operation to use the web service in the AC device (710).
[0182] FIG. 8a, FIG. 8b, and FIG. 8c are diagrams for explaining a session transfer method according to one embodiment of the present disclosure.
[0183] Referring to FIGS. 8A, 8B, and 8C, the system may include an AC device (810), an AC reader (820), a web server (830), and a FIDO server (840).
[0184] The AC device (810) may be implemented as any one of the UWB device (100) of FIG. 1, the UWB device of FIG. 2, the first electronic device (301), the second electronic device (302) of FIG. 3, or the AC device (510) of FIG. 5. In one embodiment, the AC device (810) may be implemented as a mobile device.
[0185] The AC reader (820) may be implemented as any one of the UWB device (100) of FIG. 1, the UWB device of FIG. 2, the first electronic device (301), the second electronic device (302) of FIG. 3, or the AC reader (520) of FIG. 5. In one embodiment, the AC reader (820) may be implemented as a PC.
[0186] In one embodiment, the AC device (810) and the AC reader (820) may operate according to the FIDO and CTAP standard specifications. In one embodiment, the AC device (810) and the AC reader (820) may support a user authentication method (e.g., fingerprint or iris recognition). In one embodiment, the AC device (810) and the AC reader (820) may support secure ranging using Dynamic STS or Provisioned STS. In one embodiment, secure ranging may be an alternative user authentication method depending on the security requirements of the web server (830).
[0187] In operation 801, the AC device (810) and the AC reader (820) may perform a device discovery procedure. In one embodiment, the AC device (810) and the AC reader (820) may perform the device discovery procedure via BLE or contention-based UWB.
[0188] In operation 803, the AC device (810) and the AC reader (820) may perform a user authentication procedure. According to one embodiment, the AC device (810) may transmit authentication information including at least one of biometric information, a PIN, and a password to the AC reader (820) to perform the user authentication procedure. According to one embodiment, the AC device (810) may transmit the authentication information to the AC reader (820) via FiRa BLE generic attribute profile (GATT) or BLE logical link control and adaptation protocol (L2CAP) or UWB In-band.
[0189] In one embodiment, the AC device (810) and the AC reader (820) can set up a secure channel for communication between them.
[0190] In operation 805, the AC device (810) and the AC reader (820) can determine whether the distance between the AC device (810) and the AC reader (820) is less than or equal to a threshold value based on a UWB device detection procedure through UWB ranging (user presence confirmation). In one embodiment, the AC device (810) and the AC reader (820) can determine whether the distance between the AC device (810) and the AC reader (820) is less than or equal to a threshold value by performing double-sided two-way ranging (DS-TWR). In one embodiment, the AC device (810) and the AC reader (820) can determine whether the distance between the AC device (810) and the AC reader (820) is less than or equal to a threshold value based on a provisioned STS (user presence confirmation). In one embodiment, the AC device (810) and the AC reader (820) can determine whether the distance between the AC device (610) and the AC reader (620) is less than or equal to a threshold value based on dynamic STS (user presence confirmation).
[0191] If it is determined in operation 805 that the distance between the AC device (810) and the AC reader (820) is less than or equal to a threshold value, in operation 807, the AC reader (820) may perform and / or complete a device login operation.
[0192] Thereafter, the AC device (810) and the AC reader (820) can perform at least one of user authentication method A and user authentication method B. According to one embodiment, the AC device (810) and the AC reader (820) can selectively perform user authentication method A or user authentication method B depending on the security requirements of the service. According to one embodiment, the AC device (810) and the AC reader (820) can perform both user authentication method A and user authentication method B.
[0193] <User Authentication Method A>
[0194] In operation 809, at least one of the AC device (810), the AC reader (820), the web server (830), and the FIDO server (840) may perform a register procedure. In one embodiment, the AC device (810) and / or the AC reader (820) may transmit a user certificate stored in the device to the web server (830) and / or the FIDO server (840) via a secure channel. In one embodiment, the AC device (810) and / or the AC reader (820) may transmit and receive an APDU command including the user certificate via the device UWB.
[0195] In operation 811, the AC leader (820) may transmit a user authentication request message to the AC device (810).
[0196] In operation 813, the AC device (810) may perform a user authentication procedure. For example, the AC device (810) may perform a user authentication procedure through the user's fingerprint or iris recognition.
[0197] In operation 815, the AC device (810) may transmit an authentication result value to the AC reader (820). According to one embodiment, the authentication result value may be transmitted by being included in a UWB command set within FIDO CTAP.
[0198] In operation 817, at least one of the AC device (810), the AC reader (820), the web server (830), and the FIDO server (840) may perform an authentication procedure (private key signing). In one embodiment, the AC device (810) and / or the AC reader (820) may transmit signature information (or a value signed with the user's private key) to the web server (830) and / or the FIDO server (840). In one embodiment, the FIDO server (840) may extract the received signature information (or a value signed with the user's private key) to verify the electronic signature.
[0199] <User Authentication Method B>
[0200] In operation 819, at least one of the AC device (810), the AC reader (820), and the web server (830) may register the AC device (810) as a user authentication device with the web server (830). In one embodiment, the AC device (810), the AC reader (820), and the web server (830) may share the same session key.
[0201] In operation 821, the AC device (810) and the AC reader (820) can measure the distance between themselves through UWB ranging and check whether the distance between the AC device (810) and the AC reader (820) is below a threshold value (user presence confirmation). In one embodiment, the AC device (810) and the AC reader (820) can perform secure ranging based on the STS code generated using the session key exchanged in operation 819.
[0202] In operation 823, at least one of the AC device (810), the AC reader (820), and the web server (830) may perform a user authentication procedure using the STS code.
[0203] After performing at least one of user authentication method A and user authentication method B, in operation 825, at least one of the AC device (810), the AC reader (820), the web server (830), and the FIDO server (840) may perform a related operation to use the web service in the AC device (810).
[0204] In operation 827, the AC device (810) and the AC reader (820) can continue to perform UWB ranging (keep ranging). In operation 829, the AC reader (820) can determine that the distance between the AC device (810) and the AC reader (820) is greater than or equal to a threshold value based on the UWB ranging result.
[0205] In operation 831, the web server (830) may include at least one of a Service ID (or FiRa Logical Service ID) and an ID of an AC device (810), and may transmit a first message (FiRa_APP_message_request_service continuity) requesting service continuity to the AC device (810). The first message (FiRa_APP_message_request_service continuity) may be a message inquiring whether to continue using the web service from the AC device (810).
[0206] In operation 833, the AC device (810) may transmit a second message (FiRa_APP_message_request_service continuity) to the web server (830) that includes a flag (e.g., yes) and requests service continuity. In one embodiment, the flag may indicate whether to allow a session transfer to the AC device (810) for service continuity. The second message (FiRa_APP_message_request_service continuity) may indicate that the AC device (810) will continue to use the web service.
[0207] In operation 835, the AC leader (820) may transmit a third message (FiRa_APP_message_send_service continuity) for service continuity to the web server (830), including at least one of the ID of the AC device (810), service timestamp information, and Service ID (or FiRa Logical Service ID).
[0208] In operation 837, the AC leader (820) may perform a service log off operation.
[0209] In operation 839, the AC device (810) may turn on (or activate) a service / application.
[0210] In operation 841, at least one of the AC device (810), the AC reader (820), the web server (830), and the FIDO server (840) may optionally perform user re-authentication.
[0211] In operation 843, the web server (830) may transmit a third message (FiRa_APP_message_send_service continuity) for service continuity to the AC device (810), including at least one of the ID, service timestamp information, and Service ID (or FiRa Logical Service ID) of the AC device (810).
[0212] In operation 845, the AC device (810) may be connected to a web server (830).
[0213] FIG. 9 is a diagram for explaining a session transfer method according to another embodiment of the present disclosure.
[0214] Referring to FIG. 9, the system may include an AC device (910), a first AC reader (920), a second AC reader (930), a web server (940), and a FIDO server (950).
[0215] The AC device (910) may be implemented as any one of the UWB device (100) of FIG. 1, the UWB device of FIG. 2, the first electronic device (301), the second electronic device (302) of FIG. 3, or the AC device (510) of FIG. 5.
[0216] Each of the first AC reader (920) and the second AC reader (930) may be implemented as any one of the UWB device (100) of FIG. 1, the UWB device of FIG. 2, the first electronic device (301), the second electronic device (302) of FIG. 3, or the AC reader (520) of FIG. 5.
[0217] In one embodiment, the AC device (910), the first AC reader (920), and the second AC reader (930) may operate according to FIDO and CTAP standard specifications. In one embodiment, the AC device (910), the first AC reader (920), and the second AC reader (930) may support a user authentication method (e.g., fingerprint or iris recognition). In one embodiment, the AC device (910), the first AC reader (920), and the second AC reader (930) may support secure ranging using Dynamic STS or Provisioned STS. In one embodiment, secure ranging may be an alternative user authentication method depending on the security requirements of the web server (830).
[0218] In operation 901, the AC device (910) and the first AC reader (920) can continue to perform UWB ranging (keep ranging). In operation 903, the first AC reader (920) can determine that the distance between the AC device (890) and the first AC reader (920) is greater than or equal to a threshold value based on the UWB ranging result.
[0219] In operation 905, the first AC reader (920) may transmit a first message for service continuity (FiRa_APP_message_send_service continuity) to the web server (940), including at least one of the ID of the AC device (910), service timestamp information, and Service ID (or FiRa Logical Service ID).
[0220] In operation 907, the AC device (910) and the second AC reader (930) may perform a device discovery procedure. In one embodiment, the AC device (910) and the second AC reader (930) may perform the device discovery procedure via BLE or contention-based UWB.
[0221] In operation 909, the AC device (910) and the second AC reader (930) may perform a user authentication procedure. According to one embodiment, the AC device (910) may transmit authentication information including at least one of biometric information, a PIN, and a password to the second AC reader (930) to perform the user authentication procedure. According to one embodiment, the AC device (910) may transmit the authentication information to the second AC reader (930) via FiRa BLE generic attribute profile (GATT) or BLE logical link control and adaptation protocol (L2CAP) or UWB In-band.
[0222] In the 911 operation, the AC device (910) and the second AC reader (930) can determine whether the distance between the AC device (910) and the second AC reader (930) is less than or equal to a threshold value based on a UWB device detection procedure through UWB ranging (user presence confirmation). In one embodiment, the AC device (910) and the second AC reader (930) can perform double-sided two-way ranging (DS-TWR) to determine whether the distance between the AC device (910) and the second AC reader (930) is less than or equal to a threshold value (user presence confirmation).
[0223] In operation 913, the AC device (910) may, in response to a user input, determine that the second AC reader (930) continues to use the service (or logs into the service) after the first AC reader (920) logs off the service. In one embodiment, the AC device (910) may generate a second message (FiRa_APP_message_request_user) according to a user request that includes at least one of the ID and Service ID (or FiRa Logical Service ID) of the second AC reader (930).
[0224] In operation 914, the AC device (910) may transmit a second message (FiRa_APP_message_request_user) to the second AC reader (930) that includes at least one of the ID and Service ID (or FiRa Logical Service ID) of the second AC reader (930).
[0225] In operation 915, the first AC leader (920) may perform a service log off operation.
[0226] In operation 917, the second AC leader (930) can turn on (or activate) a service / application.
[0227] In operation 919, at least one of the AC device (910), the second AC reader (930), the web server (940), and the FIDO server (950) may optionally perform user re-authentication.
[0228] In operation 921, the web server (940) may transmit a third message (FiRa_APP_message_send_service continuity) for service continuity to the second AC reader (930), including at least one of the ID of the AC device (910), service timestamp information, and Service ID (or FiRa Logical Service ID).
[0229] In operation 923, the second AC leader (930) can be connected to a web server (940).
[0230] FIG. 10 is a device diagram of a first UWB device according to one embodiment of the present disclosure.
[0231] In the embodiment of FIG. 10, the first UWB device may be implemented as the UWB device (100) of FIG. 1, the UWB device of FIG. 2, the first electronic device (301) of FIG. 3, the second electronic device (302), or the AC device illustrated in FIGS. 5 to 9.
[0232] Referring to FIG. 10, the first UWB device may include a transceiver (1010), a control unit (1020), and a storage unit (1030). In the present disclosure, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.
[0233] The transceiver (1010) can transmit and receive signals with other devices or servers. The transceiver (1010) can transmit and receive data with other UWB devices using, for example, UWB communication or OOB communication (e.g., BLE communication).
[0234] The control unit (1020) can control the overall operation of the first UWB device according to the embodiment proposed in the present disclosure. For example, the control unit (1020) can perform the operations described with reference to FIGS. 1 to 9.
[0235] The storage unit (1030) can store at least one of the information transmitted and received through the transmission and reception unit (1010) and the information generated through the control unit (1020). For example, the storage unit (1030) can store information and data required for the method described with reference to FIGS. 1 to 9.
[0236] According to one embodiment, the control unit (1020) may discover a second UWB device through device discovery based on BLE (Bluetooth low energy) communication or UWB communication, and perform UWB ranging with the second UWB device to determine whether the distance between the first UWB device and the second UWB device is less than or equal to a threshold value. If the distance between the first UWB device and the second UWB device according to the UWB ranging result is less than or equal to the threshold value, a device login or service execution procedure supported by the second UWB device may be performed.
[0237] According to one embodiment, the control unit (1020) may receive a Poll message from the second UWB device and transmit a response message corresponding to the Poll message to the second UWB device. If the distance between the first UWB device and the second UWB device calculated based on the Poll message and the response message exceeds the threshold value, a device log off or service interruption procedure supported by the second UWB device may be performed.
[0238] According to one embodiment, the control unit (1020) may register the first UWB device as a user authentication device with a web server, share a session key with the second UWB device and the web server, and perform UWB ranging with the second UWB device based on a scrambled timestamp sequence (STS) code generated using the session key.
[0239] In one embodiment, the control unit (1020) may perform a user authentication procedure using the STS code. Upon completion of the user authentication procedure, the second UWB device may receive a web service from the web server.
[0240] According to one embodiment, the control unit (1020) performs UWB ranging with the second UWB device, and if the distance between the first UWB device and the second UWB device is greater than or equal to a threshold value as a result of the UWB ranging, the control unit (1020) may receive a first message including at least one of an ID of the first UWB device and a service ID from the web server, and in response to the first message, transmit a second message including a flag indicating that the first UWB device will continue to use the web service to the web server.
[0241] FIG. 11 is a device diagram of a second UWB device according to one embodiment of the present disclosure.
[0242] In the embodiment of FIG. 11, the second UWB device may be implemented as the UWB device (100) of FIG. 1, the UWB device of FIG. 2, the first electronic device (301) of FIG. 3, the second electronic device (302), or the AC reader illustrated in FIGS. 5 to 9.
[0243] Referring to FIG. 11, the second UWB device may include a transceiver (1110), a control unit (1120), and a storage unit (1130). In the present disclosure, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.
[0244] The transceiver (1110) can transmit and receive signals with other devices or servers. The transceiver (1110) can transmit and receive data with other UWB devices using, for example, UWB communication or OOB communication (e.g., BLE communication).
[0245] The control unit (1120) can control the overall operation of the second UWB device according to the embodiment proposed in the present disclosure. For example, the control unit (1120) can perform the operations described with reference to FIGS. 1 to 9.
[0246] The storage unit (1130) can store at least one of the information transmitted and received through the transmission and reception unit (1110) and the information generated through the control unit (1120). For example, the storage unit (1130) can store information and data required for the method described with reference to FIGS. 1 to 9.
[0247] According to one embodiment, the control unit (1120) may discover a first UWB device through device discovery based on BLE (Bluetooth low energy) communication or UWB communication, perform UWB ranging with the first UWB device to determine whether a distance between the first UWB device and the second UWB device is less than or equal to a threshold value, and if the distance between the first UWB device and the second UWB device according to the UWB ranging result is less than or equal to the threshold value, perform a device login or service execution procedure supported by the second UWB device.
[0248] According to one embodiment, the control unit (1120) may transmit a Poll message to the first UWB device, receive a response message corresponding to the Poll message from the first UWB device, and, if a distance between the first UWB device and the second UWB device calculated based on the Poll message and the response message exceeds the threshold value, perform a device log off or service interruption procedure supported by the second UWB device.
[0249] According to one embodiment, when the first UWB device is registered as a user authentication device on a web server, the control unit (1120) can share a session key with the first UWB device and the web server, and perform UWB ranging with the first UWB device based on a scrambled timestamp sequence (STS) code generated using the session key.
[0250] According to one embodiment, the control unit (1120) can receive a web service from the web server when the user authentication procedure using the STS code is completed.
[0251] According to one embodiment, the control unit (1120) may perform UWB ranging with the first UWB device, and if the distance between the first UWB device and the second UWB device is greater than or equal to a threshold value as a result of the UWB ranging, the control unit (1120) may transmit a third message including at least one of an ID of the first UWB device, service timestamp information, and a service ID to the web server. Based on the third message, the third UWB device may continue to use the web service.
[0252] 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.
[0253] 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 operating method of the first UWB (ultra wide band) device, An operation of discovering a second UWB device through device discovery based on BLE (bluetooth low energy) communication or UWB communication; and Including an operation of performing UWB ranging with the second UWB device to determine whether the distance between the first UWB device and the second UWB device is less than or equal to a threshold value; A method characterized in that, if the distance between the first UWB device and the second UWB device according to the UWB ranging result is less than or equal to the threshold value, a device login or service execution procedure supported by the second UWB device is performed.
2. In paragraph 1, An operation of receiving a Poll message from the second UWB device; and Further comprising the action of transmitting a response message corresponding to the Poll message to the second UWB device, A method characterized in that when the distance between the first UWB device and the second UWB device calculated based on the poll message and the response message exceeds the threshold value, a device log off or service interruption procedure supported by the second UWB device is performed.
3. In paragraph 1, An action of registering the first UWB device as a user authentication device on a web server; An operation of sharing a session key with the second UWB device and the web server; and A method further characterized by including an operation of performing UWB ranging with the second UWB device based on a scrambled timestamp sequence (STS) code generated using the session key.
4. In paragraph 3, Further comprising an action of performing a user authentication procedure using the above STS code, A method characterized in that, when the above user authentication procedure is completed, a web service is provided from the web server through the second UWB device.
5. In paragraph 4, An operation of performing UWB ranging with the second UWB device; If the distance between the first UWB device and the second UWB device is greater than or equal to a threshold value as a result of the UWB ranging, an operation of receiving a first message including at least one of an ID of the first UWB device and a service ID from the web server; and A method further comprising the action of transmitting a second message to the web server in response to the first message, the second message including a flag indicating that the web service will continue to be used by the first UWB device.
6. In the operating method of the second UWB (ultra wide band) device, An action of discovering a first UWB device through device discovery based on BLE (bluetooth low energy) communication or UWB communication; An operation of performing UWB ranging with the first UWB device to determine whether the distance between the first UWB device and the second UWB device is less than or equal to a threshold value; and A method characterized by including an operation of performing a device login or service execution procedure supported by the second UWB device if the distance between the first UWB device and the second UWB device according to the UWB ranging result is less than or equal to the threshold value.
7. In paragraph 6, An operation of transmitting a Poll message to the first UWB device; An operation of receiving a response message corresponding to the Poll message from the first UWB device; and A method further comprising: performing a device log off or service interruption procedure supported by the second UWB device if the distance between the first UWB device and the second UWB device calculated based on the poll message and the response message exceeds the threshold value.
8. In paragraph 6, When the first UWB device is registered as a user authentication device on the web server, an operation of sharing a session key with the first UWB device and the web server; and A method further comprising an operation of performing UWB ranging with the first UWB device based on a scrambled timestamp sequence (STS) code generated using the session key.
9. In paragraph 8, A method characterized by further including an action of receiving a web service from the web server when the user authentication procedure using the above STS code is completed.
10. In paragraph 9, An operation of performing UWB ranging with the first UWB device; If the distance between the first UWB device and the second UWB device is greater than or equal to a threshold value as a result of the UWB ranging, the method comprises transmitting a third message including at least one of an ID of the first UWB device, service timestamp information, and a service ID to the web server. A method characterized in that the third UWB device continues to use the web service based on the third message.
11. In the first UWB (ultra wide band) device, Transmitter and receiver; and comprising a control unit, said control unit comprising: Discover a second UWB device through device discovery based on BLE (Bluetooth low energy) communication or UWB communication, Perform UWB ranging with the second UWB device to determine whether the distance between the first UWB device and the second UWB device is less than or equal to a threshold value; A device characterized in that, if the distance between the first UWB device and the second UWB device according to the UWB ranging result is less than or equal to the threshold value, a device login or service execution procedure supported by the second UWB device is performed.
12. In paragraph 11, the control unit, Receive a Poll message from the second UWB device, Transmitting a response message corresponding to the Poll message to the second UWB device, A device characterized in that when the distance between the first UWB device and the second UWB device calculated based on the poll message and the response message exceeds the threshold value, a device log off or service interruption procedure supported by the second UWB device is performed.
13. In paragraph 11, the control unit, Register the above first UWB device as a user authentication device on the web server, Share the session key with the second UWB device and the web server, A device characterized by performing UWB ranging with the second UWB device based on a scrambled timestamp sequence (STS) code generated using the session key.
14. In the second UWB (ultra wide band) device, Transmitter and receiver; and comprising a control unit, said control unit comprising: Discover the first UWB device through device discovery based on BLE (Bluetooth low energy) communication or UWB communication, Perform UWB ranging with the first UWB device to determine whether the distance between the first UWB device and the second UWB device is less than or equal to a threshold value; A device characterized in that, if the distance between the first UWB device and the second UWB device according to the UWB ranging result is less than or equal to the threshold value, the device performs a device login or service execution procedure supported by the second UWB device.
15. In paragraph 14, the control unit, Transmitting a Poll message to the first UWB device, Receive a response message corresponding to the Poll message from the first UWB device, A device characterized in that, if the distance between the first UWB device and the second UWB device calculated based on the poll message and the response message exceeds the threshold value, a device log off or service interruption procedure supported by the second UWB device is performed.
Citation Information
Patent Citations
UWB ranging method and device, terminal equipment and storage medium
CN114222247A
Ranging between mobile devices
EP3834064B1
Method, device and system for verifying UWB ranging results
EP4161119A1
Method And System for Providing ID Card by using Electronic Paper
KR102493379B1
Power efficient ultra-wideband (UWB) tag for indoor positioning
US20200228943A1
