Method and apparatus for providing ultra wideband service by using bluetooth low power communication

Abstract

A method for operating a plurality of UWB channels is disclosed. According to various embodiments of the disclosure, a method for a first electronic device includes the steps of: receiving information about an announcement interval related to a second electronic device from the second electronic device; receiving an input for instructing a search for the second electronic device from a user; in response to the input, scanning a Bluetooth low energy (BLE) announcement message of the second electronic device related to ultra-wideband (UWB) multi-millisecond (MMS) ranging; and when the BLE announcement message is not received from the second electronic device for a time corresponding to an integer multiple of the announcement interval, stopping the operation of scanning the BLE announcement message.

Description

Technical Field

[0001] This disclosure relates to UWB communication, and more specifically to methods and apparatus for providing UWB services using BLE communication. Background Technology

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

[0003] In the IoT environment, intelligent internet technology (IT) services can be provided, which collect and analyze data generated by connected things to create new value for human life. IoT can have a variety of applications through the convergence or integration of conventional information technology (IT) technologies with various industries, such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare or smart appliances, or state-of-the-art medical services.

[0004] As wireless communication systems evolve to provide a variety of services, a method for efficiently delivering such services is needed. For example, ranging techniques can be used to measure the distance between electronic devices using ultra-wideband (UWB). UWB is a wireless communication technology that uses a very wide frequency band of several GHz or more in the baseband without using a wireless carrier. Summary of the Invention

[0005] Technical issues This disclosure presents a scheme for providing ultra-wideband (UWB) services. More specifically, this disclosure relates to methods and apparatus for providing ultra-wideband (UWB) multi-millisecond (MMS) ranging services using Bluetooth Low Energy (BLE) communication.

[0006] Technical solution According to embodiments of this disclosure, a method for a first electronic device includes: receiving information from a second electronic device regarding an announcement interval associated with the second electronic device; receiving input from a user indicating a search for the second electronic device; in response to the input, scanning Bluetooth Low Energy (BLE) announcement messages associated with Ultra Wideband (UWB) Multi-Millisecond (MMS) ranging of the second electronic device; and stopping the scanning of BLE announcement messages when no BLE announcement message is received from the second electronic device within a time period corresponding to a real multiple of the announcement interval.

[0007] According to embodiments of this disclosure, a method for a second electronic device includes: sending information to a first electronic device about an announcement interval associated with the second electronic device; and sending a Bluetooth Low Energy (BLE) announcement message associated with Ultra Wideband (UWB) Multi-Millisecond (MMS) ranging to the first electronic device, wherein scanning of the BLE announcement message is stopped when a time exceeding a real multiple of the announcement interval has elapsed.

[0008] According to embodiments of this disclosure, a first electronic device includes a transceiver and at least one processor, and the at least one processor is configured to: receive information from a second electronic device regarding an announcement interval associated with the second electronic device; receive input from a user indicating a search for the second electronic device; in response to the input, scan the second electronic device for Bluetooth Low Energy (BLE) announcement messages associated with Ultra Wideband (UWB) Multi-Millisecond (MMS) ranging; and stop scanning BLE announcement messages when no BLE announcement message is received from the second electronic device within a time period corresponding to a real multiple of the announcement interval.

[0009] According to embodiments of this disclosure, a second electronic device includes a transceiver and at least one processor, and the at least one processor is configured to: send information to a first electronic device about an announcement interval associated with the second electronic device; and send Bluetooth Low Energy (BLE) announcement messages associated with Ultra Wideband (UWB) Multi-Millisecond (MMS) ranging to the first electronic device, and stop scanning of BLE announcement messages when a time exceeding a real multiple of the announcement interval has elapsed.

[0010] Beneficial effects of the invention The service can be provided efficiently through a scheme that uses BLE communication to provide ultra-wideband (UWB) MMS ranging services. Attached Figure Description

[0011] Figure 1a An exemplary architecture for a UWB device is shown.

[0012] Figure 1b An exemplary configuration of a communication system including UWB devices is shown.

[0013] Figure 2 An exemplary structure for a frame used for UWB communication is shown.

[0014] Figure 3 The method for two of the UWB devices to perform UWB communication is shown.

[0015] Figure 4 A method for performing UWB ranging by two UWB devices is shown.

[0016] Figure 5 The structure of the ranging block and the cycle used for UWB ranging is shown.

[0017] Figure 6a This is a view illustrating multi-millisecond (MMS) ranging operations according to an embodiment of the present disclosure.

[0018] Figure 6b The operation of performing MMS ranging using BLE and UWB channels according to embodiments of the present disclosure is illustrated.

[0019] Figure 7 This is a view illustrating a central device and peripheral devices performing BLE-based UWB MMS ranging according to an embodiment of the present disclosure.

[0020] Figure 8 This is a view illustrating MMS ranging operation according to an embodiment of the present disclosure.

[0021] Figure 9 The present disclosure illustrates establishing a connection between devices for reporting operations in a BLE channel and performing the reporting operation after UWB MMS ranging, according to an embodiment of the present disclosure.

[0022] Figure 10 The present disclosure illustrates establishing a connection between devices in a BLE channel and performing repeated UWB MMS ranging operations according to an embodiment of the present disclosure.

[0023] Figure 11 This illustrates an embodiment of the present disclosure of performing UWB MMS ranging operations without creating a connection between devices for reporting operations in a BLE channel.

[0024] Figure 12 An implicit termination operation in BLE-based MMS ranging is illustrated according to an embodiment of this disclosure.

[0025] Figure 13a and Figure 13b This is a flowchart illustrating the operation of a central device according to an embodiment of the present disclosure.

[0026] Figure 14a and Figure 14b A BLE-encoded PHY used in BLE-based MMS ranging according to an embodiment of the present disclosure is shown.

[0027] Figure 15 A structural diagram illustrating a first electronic device according to an embodiment of the present disclosure is shown.

[0028] Figure 16 A structural diagram illustrating a second electronic device according to an embodiment of the present disclosure is shown. Detailed Implementation

[0029] In the following, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

[0030] In describing the embodiments, descriptions of techniques known in the art and not directly related to the present invention have been omitted. This is to further clarify the spirit of this disclosure without making it unclear.

[0031] For the same reason, some elements may be shown enlarged or schematically. The size of each element does not necessarily reflect its actual size. Throughout the figures, the same reference numerals are used to refer to the same elements.

[0032] The advantages and features of this disclosure, as well as the methods for implementing these advantages and features, can be understood from the embodiments described below in conjunction with the accompanying drawings. However, the invention is not limited to the embodiments disclosed herein, and various modifications can be made thereto. The embodiments disclosed herein are provided merely to inform those skilled in the art of the category of this disclosure. The invention is defined only by the appended claims. Throughout the specification, the same reference numerals denote the same parts.

[0033] In this context, it can be understood that each block of the flowchart and combinations of flowcharts can be executed by computer program instructions. Since the computer program instructions can be located in the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate means for performing the functions described in the block(s) of each flowchart. Since the computer program instructions can be stored in a computer-usable or computer-readable storage medium that is oriented toward the computer or other programmable data processing apparatus to implement the functions in a specified manner, the instructions stored in the computer-usable or computer-readable storage medium can produce an product comprising instruction means for performing the functions described in the block(s) of each flowchart. Since the computer program instructions can be located in a computer or other programmable data processing apparatus, the instructions that generate the process to be executed by the computer as a series of operational steps are executed on the computer or other programmable data processing apparatus, and operating the computer or other programmable data processing apparatus can provide steps for performing the functions described in the block(s) of each flowchart.

[0034] Furthermore, each box may represent a module, segment, or portion of code comprising one or more executable instructions for performing a specified logical function. It should also be noted that in some alternative embodiments, the functions mentioned in the boxes may occur in different orders. For example, depending on the respective function, two boxes shown consecutively may execute substantially simultaneously or in reverse order.

[0035] As used herein, the term "unit" refers to a software element or hardware element, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). A unit plays a specific role. However, a unit is not limited to software or hardware. A unit can be configured in a storage medium that can be addressed or configured to execute one or more processors. Thus, by way of example, a unit includes elements such as software elements, object-oriented software elements, class elements and task elements, procedures, functions, attributes, processes, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data schemas, tables, arrays, and variables. The functionality provided within components and units can be combined into a smaller number of components and units, or further divided into additional components and units. Furthermore, components and units can be implemented as one or more CPUs in an execution device or secure multimedia card. According to embodiments of this disclosure, "...unit" can include one or more processors.

[0036] As used herein, the terms "terminal" or "device" may also be referred to as a mobile station (MS), user equipment (UE), user terminal (UT), terminal, wireless terminal, access terminal (AT), user unit, user station (SS), wireless device, wireless communication device, wireless transceiver unit (WTRU), mobile node, or mobile, or may be referred to by other terms. Various embodiments of a terminal may include a cellular phone, a smartphone with wireless communication capabilities, a personal digital assistant (PDA) with wireless communication capabilities, a wireless modem, a portable computer with wireless communication capabilities, an imaging device such as a digital camera with wireless communication capabilities, a gaming device with wireless communication capabilities, a home appliance for music storage and playback with wireless communication capabilities, an internet-connected home appliance capable of wireless internet access and browsing, and a portable unit or terminal incorporating a combination of these capabilities. Furthermore, a terminal may include, but is not limited to, machine-to-machine (M2M) terminals and machine-type communication (MTC) terminals / devices. In this disclosure, a terminal may be referred to as an electronic device or simply a device.

[0037] The operating principles of this disclosure are described in detail below with reference to the accompanying drawings. Detailed descriptions of known functions or configurations may be omitted when describing embodiments of this disclosure to avoid unnecessarily obscuring the subject matter. The terminology described below is defined in consideration of the functions in this disclosure and may vary depending on the intent or habits of the user and operator. Therefore, these terms should be defined based on the overall disclosure.

[0038] In the following, embodiments of the present invention are described in detail with reference to the accompanying drawings. Furthermore, although a communication system using UWB has been described in conjunction with embodiments of the present disclosure, by way of example, embodiments of the present disclosure can also be applied to other communication systems with similar technical background or features. For example, communication systems using Bluetooth or ZigBee may be included. Moreover, it will be determined by those skilled in the art that embodiments of the present disclosure can be modified within the scope of the present disclosure without significantly departing from it, and such modifications can be applied to other communication systems.

[0039] When it is determined that the subject matter of this disclosure is unclear, a detailed description of known techniques or functions may be skipped. The terminology described below is defined in consideration of the functions in this disclosure and may vary depending on the intent or habit of the user and operator. Therefore, these terms should be defined based on the overall disclosure.

[0040] Generally, based on the detection range, wireless sensor network technologies are mainly divided into Wireless Local Area Network (WLAN) and Wireless Personal Area Network (WPAN) technologies. In this context, WLAN is based on IEEE 802.11 technology, which enables access to the backbone network within a radius of approximately 100 meters. WPAN is based on IEEE 802.15 technology, which includes Bluetooth, ZigBee, and Ultra-Wideband (UWB). A wireless network implementing this technology can include multiple electronic devices.

[0041] UWB can refer to a short-range, high-speed wireless communication technology that uses a wide bandwidth of several GHz or higher, low spectral density, and short pulse widths (e.g., 1 nanosecond to 4 nanoseconds) in baseband mode. UWB can also refer to the frequency band itself used for UWB communication. UWB enables secure and accurate ranging between devices. Therefore, UWB makes it possible to estimate the relative position of two devices based on the distance between them, or to estimate the accurate position of a device based on its distance to a fixed device (whose position is known).

[0042] The terminology used herein is provided to better understand this disclosure and may be changed without departing from the technical spirit of this disclosure.

[0043] An "Application-Specific File (ADF)" can be a data structure, such as an application data structure, that can host application or application-specific data.

[0044] An "Application Protocol Data Unit (APDU)" can be a command or response used when communicating with application data structures in a UWB device.

[0045] "Application-specific data" can be, for example, a file structure with root and application levels, including UWB controlled party information and UWB session data required by the UWB session.

[0046] The “controller” can be the ranging device that defines and controls ranging control messages (RCM) (or control messages).

[0047] The “controlled party” can be a ranging device that uses ranging parameters from the RCM (or control message) received from the controlling party.

[0048] Unlike "Static STS", "Dynamic Scrambling Timestamp Sequence (STS) Mode" can be an operating mode where the STS does not repeat during the ranging session. In this mode, the STS can be managed by the ranging device, and the ranging session key that generates the STS can be managed by the security component.

[0049] An "applet" can be, for example, an applet that executes on a security component that includes UWB parameters and service data. In this disclosure, an applet can be a FiRa applet as defined by FiRa.

[0050] "Range measuring device" can be any device capable of performing UWB ranging. In this disclosure, the ranging device can be an Enhanced Range Measure (ERDEV) as defined in IEEE 802.15.4z or a FiRa device as defined by FiRa. The ranging device can be referred to as a UWB device.

[0051] A “UWB-enabled application” can be an application used for UWB services. For example, a UWB-enabled application can be an application that uses the framework API to configure OOB connectors, security services, and / or UWB services for UWB sessions. In this disclosure, “UWB-enabled application” can be abbreviated as application or UWB application. A UWB-enabled application can be a FiRa-enabled application as defined by FiRa.

[0052] A “framework” can be a component that provides access to profiles, individual UWB configurations, and / or notifications. A “framework” can be, for example, a collection of logical software components, including a profile manager, an OOB connector, security services, and / or UWB services. In this disclosure, a framework can be a FiRa framework as defined by FiRa.

[0053] An “OOB connector” can be a software component used to establish an out-of-band (OOB) connection (e.g., a BLE connection) between ranging devices. In this disclosure, the OOB connector can be a FiRa OOB connector as defined by FiRa.

[0054] A “profile” can be a set of previously defined UWB and OOB configuration parameters. In this disclosure, a profile can be a FiRa profile defined by FiRa.

[0055] The "profile manager" can be a software component that implements a profile available on the ranging device. In this disclosure, the profile manager can be the FiRa profile manager defined by FiRa.

[0056] A "service" can be the implementation of a use case that provides services to end users.

[0057] "Smart ranging device" can be a ranging device that can implement optional framework APIs. In this disclosure, the smart ranging device can be a FiRa smart device as defined by FiRa.

[0058] A Global Private File (GDF) can be root-level application-specific data that includes the data required to establish a USB session.

[0059] A “framework API” can be an API used by UWB-enabled applications to communicate with the framework.

[0060] The “initiator” can be the ranging device that initiates the ranging exchange.

[0061] An "Object Identifier (OID)" can be an identifier for an ADF (Application Data Function) within an application data structure.

[0062] "Out-of-band (OOB)" can refer to data communication that does not use UWB as the underlying wireless technology.

[0063] A “Ranging Data Set (RDS)” can be the data (e.g., UWB session key, session ID, etc.) required to establish a UWB session when confidentiality, authenticity, and integrity need to be protected.

[0064] A “responder” can be a ranging device that responds to the initiator in a ranging exchange.

[0065] "STS" can be an encrypted sequence used to enhance the integrity and accuracy of ranging measurement timestamps. STS can be generated from the ranging session key.

[0066] A "secure channel" can be a data channel that prevents eavesdropping and tampering.

[0067] A "security component" can be an entity with a defined security level (e.g., SE or TEE) that interfaces with UWBS for purposes such as providing RDS to UWBS when using dynamic STS.

[0068] "Secure element (SE)" can be a tamper-proof secure hardware component that can be used as a security component in a ranging device.

[0069] "Secure ranging" can be based on STS generated through strong encryption operations.

[0070] "Security services" can be software components used to interface with security components, such as secure elements or trusted execution environments (TEEs).

[0071] A "service mini-program" can be a mini-program on a security component that handles specific service transactions.

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

[0073] A "service provider" can be an entity that defines and provides the hardware and software required to provide a specific service to an end user.

[0074] "Static STS mode" is an operating mode in which STS is repeated during the session and does not need to be managed by the security component.

[0075] The "Secure UWB Service (SUS) applet" can be an applet on the SE that communicates with other applets to retrieve the data needed to enable secure UWB sessions with other ranging devices. The SUS applet can then transmit the corresponding data (information) to the UWBS.

[0076] "UWB service" can be a software component that provides access to UWBS.

[0077] A "UWB session" can be a period of time from the start of communication between the controller and the controlled party via UWB until the communication stops. A UWB session can include ranging, data transmission, or both ranging and data transmission.

[0078] The “UWB Session ID” can be an ID (e.g., a 32-bit integer) that identifies a UWB session and is shared between the controller and the controlled party.

[0079] A “UWB session key” can be a key used to protect a UWB session. The UWB session key can be used to generate an STS. In this disclosure, the UWB session key can be a UWB ranging session key (URSK) and can be abbreviated as session key.

[0080] The “UWB Subsystem (UWBS)” can be a hardware component that implements the UWB PHY and MAC specifications. The UWBS can have interfaces to the framework and interfaces to security components for searching the RDS. In this disclosure, the UWB PHY and MAC specifications can be, for example, the FiRa PHY and FiRa MAC specifications defined by FiRa, which relates to IEEE 802.15.4 / 4z.

[0081] When it is determined that the subject matter of this disclosure will be unnecessarily unclear, a detailed description of the relevant known features or characteristics may be omitted when describing this disclosure.

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

[0083] Figure 1 shows an example architecture of a UWB device.

[0084] The UWB device (electronic device) in Figure 1 can be a ranging device that supports UWB ranging (e.g., UWB secure ranging). In an embodiment, the ranging device can be an Enhanced Ranging Device (ERDEV) as defined in IEEE 802.15.4z or a FiRa device as defined by FiRa.

[0085] In the embodiment shown in Figure 1, the UWB device can interact with other UWB devices through a UWB session.

[0086] UWB devices may implement a first interface (interface #1), which is an interface between UWB-enabled applications and the framework, and allows UWB-enabled applications on the UWB device to use the UWB capabilities of the UWB device in a predetermined manner. In embodiments, the first interface may be a framework API or a proprietary interface, but is not limited thereto.

[0087] UWB devices can implement a second interface (interface #2), which is the interface between the framework and the UWB subsystem (UWBS). In embodiments, the second interface can be the UWB command interface (UCI) or a proprietary interface, but is not limited to these.

[0088] Referring to Figure 1, a UWB device may include UWB-enabled applications, frameworks, and / or a UWBS containing a UWB MAC layer and a UWB physical layer. Depending on the embodiment, some entities may not be included in the UWB device, or additional entities (e.g., a security layer) may be further included.

[0089] UWB-enabled applications can trigger the establishment of a UWB session via the first interface. UWB-enabled applications can use one of the previously defined profiles. For example, a UWB-enabled application can use either a profile defined in FiRa or a custom profile. UWB-enabled applications can use the first interface to handle relevant events such as service discovery, ranging notifications, and / or error conditions.

[0090] The framework can provide access to profiles, individual UWB settings, and / or notifications. The framework can be a set of software components. As described above, UWB-enabled applications can interface with the framework through a first interface, and the framework can interface with UWBS through a second interface. The framework's software components may include, for example, a profile manager, an OOB connector, security services, and / or UWB services.

[0091] The profile manager can be used to manage the profiles available on UWB devices. A profile can be a set of parameters required to establish communication between UWB devices. For example, a profile may include parameters indicating which OOB security channel to use, UWB / OOB configuration parameters, parameters indicating whether the use of a particular security component is mandatory, and / or parameters related to the ADF file structure.

[0092] OOB connectors serve to establish OOB connections between UWB devices. OOB connectors can handle the OOB process, including discovery and connection steps. See below for reference. Figure 4 Describe the OOB steps.

[0093] Security services can interface with security components such as SE or TEE.

[0094] The UWB service can perform the role of managing UWBS. The UWB service can provide access to UWBS from the profile manager by implementing a second interface.

[0095] UWBS can be a hardware component that includes a UWB MAC layer and a UWB physical layer. UWBS can perform UWB session management and communicate with the UWBS of another UWB device. UWBS can interface with the framework through a second interface and can obtain RDS from the security component.

[0096] Figure 1b An example configuration of a communication system including UWB devices is shown.

[0097] refer to Figure 1b The communication system includes a first UWB device and a second UWB device. In an embodiment, the first UWB device and the second UWB device may be, for example, the UWB device of FIG1 or an electronic device including the UWB device of FIG1.

[0098] The first UWB can host one or more UWB-enabled applications, for example, that can be installed by a user (e.g., a mobile phone). It can be based on, for example, a framework API. The second UWB does not provide a framework API and can, for example, use proprietary interfaces to implement specific UWB-enabled applications. Contrary to what is shown, according to an embodiment, both the first and second UWB devices can be ranging devices using a framework API, or both can be ranging devices using proprietary interfaces.

[0099] The first UWB and the second UWB may include a UWB-enabled application layer, framework, OOB components, security components, and / or UWBS. In this disclosure, the OOB components and / or security components may be optional components and, according to embodiments, may not be included in the UWB device.

[0100] A framework can be used to provide access to profiles, individual UWB settings, and / or notifications. A framework can be a set of software components and may include, for example, a profile manager, an OOB connector, security services, and / or UWB services. Refer to the descriptions above for each component.

[0101] The OOB component can be a hardware component that includes a MAC layer and / or a physical layer for OOB communication (e.g., BLE communication). The OOB component can communicate with the OOB components of other devices. In an embodiment, a first UWB device and a second UWB device can use the OOB component to create an OOB connection (channel) and exchange parameters for establishing a UWB session via the OOB channel. In this disclosure, the OOB component may be referred to as an OOB subsystem.

[0102] UWBS can be a hardware component comprising a UWB MAC layer and a UWB physical layer. UWBSs 209 and 219 can perform UWB session management and communicate with the UWBS of another UWB device. In an embodiment, the first and second UWB devices can perform service data and UWB ranging transactions through a UWB session established via the UWBS using exchanged parameters.

[0103] Security components can be hardware components that interface with the framework and / or UWBS to provide RDS.

[0104] In this disclosure, the UWB-enabled application layer and / or framework can be implemented by an application processor (AP) (or processor). Therefore, it can be understood in this disclosure that the operation of the UWB-enabled application layer and / or framework is performed by the AP (or processor).

[0105] Figure 2 An example frame structure for UWB communication is shown.

[0106] Figure 2 (a) shows an example structure of a frame without STS packet configuration applied, and Figure 2 (b) illustrates an example structure of a frame with STS packet configuration applied. In an embodiment, the frame may be a ranging frame (RFRAME) for transmitting ranging data (e.g., ranging initiation / response / final message, etc.) or a data frame for transmitting other data (e.g., service data, etc.).

[0107] refer to Figure 2 (a) A frame or a PHY PDU (PPDU) used to transmit that frame may include a Synchronization Header (SHR), a PHY Header (PHR), and a PHY Payload (PSDU). A PSDU may include a MAC frame. A MAC frame may include a MAC Header (MHR), a MAC Payload, and / or a MAC Trailer (MFR). The PPDU's Synchronization Header may include a SYNC field and a Start-of-Frame Delimiter (SFD). The SFD field may be a field indicating the end of the SHR and the beginning of the data field. For a description of each element / field included in the PPDU and MAC frame, refer to the descriptions defined in IEEE 802.15.4 / 4z and / or FiRa.

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

[0109] When STS packet settings are applied (supported), the structure of the PPDU (or frame) can be as follows: Figure 3 As shown in b.

[0110] refer to Figure 2 (b) In the case of STS packet (SP) setting 0 (SP0), the STS field is not included in the PPDU (SP0 packet). In the case of SP setting 1 (SP1), the STS field immediately follows the Start of Frame Delimiter (SFD) field and precedes the PHR field (SP1 packet). In the case of SP setting 2 (SP2), the STS field is located after the PHY payload (SP2 packet). In the case of SP setting 3 (SP3), the STS field immediately follows the SFD field, and the PPDU does not include the PHR and data fields (PHY payload) (SP3 packet). In other words, in the case of SP3, the frame (or UWB message) does not include the PHR and PHY payload.

[0111] When STS group settings are supported, SP0, SP1, and SP3 can be mandatory settings that must be supported, while SP2 can be an optional setting that is supported.

[0112] Figure 3 A method for performing UWB communication by two UWB devices is shown.

[0113] exist Figure 3 In this embodiment, the first UWB device can act as a controller (or a controlled party), and the second UWB device can act as a controlled party (or a controller), which is the opposite of the role of the first UWB device. The first UWB device can act as an initiator (or a responder), and the second UWB device can act as a responder (or an initiator), which is the opposite of the role of the first UWB device.

[0114] (1)Reference Figure 3 The first UWB device and the second UWB device may optionally perform an OOB step before the UWB step. In this disclosure, the OOB step may be referred to as the OOB connection step.

[0115] The OOB step can be a step performed to discover UWB devices and establish and control UWB sessions via an OOB channel (e.g., a BLE channel).

[0116] In an embodiment, the OOB step may include at least one of the following steps.

[0117] - Discover UWB devices and profiles (Device and profile discovery) - Establish an OOB connection (channel) - Establish secure channels to protect messages and data - Exchange parameters used to establish a UWB session via a secure channel (e.g., UWB capability parameters (controlled party capability parameters), UWB configuration parameters, and / or session key related parameters) (parameter exchange step) In an embodiment, the parameter exchange step may include the step of the controlled party transmitting the controlled party's capability parameters / message (UWB_CAPABILITY) to the controlling party, the step of the controlling party transmitting the UWB configuration parameters / message (UWB_CONFIGURATION) to the controlled party, and / or the step of one UWB device transmitting session key related parameters / messages (SESSION_KEY_INFO) used to protect the UWB session to another UWB device.

[0118] In this embodiment, the controlled party (UWB) capability parameters and / or session key parameters may be included in and transmitted within a controlled party information message (CONTROLLEE_INFO), which is an OOB message transmitted from the controlled party to the controlling party. In this embodiment, the UWB configuration parameters and / or session key parameters may be included in and transmitted within a session data message (SESSION_DATA), which is an OOB message transmitted from the controlling party to the controlled party.

[0119] The controlled party performance parameter (UWB_CAPABILITY) may include at least one parameter that provides information about the controlled party's device capabilities. For example, the controlling party performance parameter may include parameters for supporting the device's role (initiator or responder), parameters for multi-node support, parameters for supporting STS configuration, parameters for supporting ranging methods, RFRAME feature performance parameters, parameters for supporting angle of arrival (AoA), and / or parameters for supporting scheduling modes.

[0120] UWB configuration parameters (UWB_CONFIGURATION) may include at least one parameter for configuring a UWB session. For example, UWB configuration parameters may include a UWB session ID parameter, ranging method parameter, multi-node configuration parameter, STS configuration parameter, scheduling mode parameter, Time-of-Flight (ToF) reporting parameter, AoA related parameter, parameter indicating the number of time slots per ranging round, time slot duration parameter, responder time slot index parameter, MAC address mode parameter, device MAC address parameter, parameter indicating the number of controlled parties, and / or destination (DST) MAC address parameter.

[0121] Session key related parameters (SESSION_KEY_INFO) can include session key related parameters for dynamic STS and / or for static STS. For example, session key related parameters for dynamic STS can include data exchanged to generate UWB session keys or data directly used as UWB session keys. For example, static STS can include the vendor ID (vendor ID) of the provider of the UWB-enabled application and any predefined values ​​selected by the UWB-enabled application for the UWB device (static STS IV). The vendor ID can be used to set the phyVupper64 parameter of the static STS, and the static STS IV can be used to set the vUpper64 parameter.

[0122] (2) The first UWB device and the second UWB device can perform UWB steps. In this disclosure, UWB steps may be referred to as UWB connection steps.

[0123] UWB steps can be steps performed to perform UWB ranging and transmit service data through a UWB session.

[0124] In an embodiment, the UWB step may include at least one of the following steps.

[0125] -Start UWB session (UWB triggered) - Perform UWB ranging to obtain the distance / location between two UWB devices. - Exchange service data (transactions) As described above, the OOB step is an optional step and can be omitted in some embodiments. For example, the OOB step can be omitted when UWB device discovery and / or UWB session establishment and control are performed via a UWB channel (in-band). For example, when performing in-band discovery, the OOB step for performing OOB discovery can be omitted. In this case, the UWB step can also perform operations for discovering UWB devices via the UWB channel and exchanging parameters for UWB session configuration.

[0126] Figure 4 A method for performing UWB ranging using two UWB devices is shown.

[0127] Figure 4 (a) illustrates an embodiment in which a first UWB device operates as a controller / initiator and a second UWB device operates as a controlled / responder. Figure 4 (b) illustrates an embodiment in which a first UWB device operates as a controller / responder and a second UWB device operates as a controlled / initiator.

[0128] refer to Figure 4In (a) and (b), the controlling party can send control messages for UWB ranging to the controlled party. The ranging control messages can be used to carry ranging parameters(s) for controlling and configuring the ranging process. In embodiments, the control messages may include information about the role of the ranging device (e.g., initiator or responder), ranging time slot index information, and / or address information about the ranging device.

[0129] The initiator can send a ranging initiation message to the responder to initiate UWB ranging. In this embodiment, the initiator can send the ranging initiation message via an SP1 packet or an SP3 packet. When sending the ranging initiation message via an SP1 packet, control messages can be included and sent in the PHY payload of the ranging initiation message. When sending the ranging initiation message via an SP3 packet, the ranging initiation message does not include the PHR and PHY payload.

[0130] The responder can send a ranging response message to the initiator in response to a ranging initiation message. In an embodiment, the responder can send the ranging response message via an SP1 packet or an SP3 packet. When sending a ranging response message via an SP1 packet, a first measurement report message can be included and sent in the PHY payload of the ranging response message. In an embodiment, the first measurement report message may include an AoA measurement, a response time and / or a round-trip time measurement of the responder, and a list of responder addresses. The response time field may indicate the time difference between the time of receipt of the ranging initiation message on the responder's side and the time of transmission of the ranging response message. Based on this, one-sided two-way ranging (SS-TWR) can be performed. The ToF calculation via SS-TWR follows the scheme defined in IEEE 802.15.4z or FiRa.

[0131] In the case of dual-sided two-way ranging (DS-TWR), the initiator can further send a final ranging message to the responder to complete the ranging exchange. When the final ranging message is sent via SP1 packets, a second measurement report message can be included and sent in the PHY payload of the final ranging message. In an embodiment, the second measurement report message may include AoA measurements, the round-trip time (first round-trip time) of the first responder and / or the response time measurement of the responder, and a list of responder addresses. When the sender of the measurement report message is the initiator, the first round-trip time field may indicate the time difference between the ranging initiation message from the initiator and the first ranging response message from the first responder. Alternatively, when the sender of the measurement report message is the responder, the first round-trip time field may indicate the time difference between the ranging response message from the responder and the final ranging message from the initiator. Based on this, DS-TWR can be performed. The time-of-flight (ToF) calculation of DS-TWR follows the scheme defined in IEEE 802.15.4z or FiRa.

[0132] According to an embodiment, the aforementioned first measurement report message and / or second measurement report message may not be included in the ranging response message and / or ranging final message, but may be sent as separate messages. For example, when applying a non-delay mode, the measurement report message may be sent via a data frame after the ranging exchange.

[0133] Simultaneously, the initiator and responder can perform UWB ranging according to preset scheduling modes. For example, in time-scheduled ranging mode, the controller knows the IDs of all controlled parties and can specify the precise scheduling of ranging transmissions. As another example, in contention-based ranging mode, the controller does not know the number and IDs of the controlled parties, and therefore UWB devices compete with each other. In this case, conflicts may occur between responding devices.

[0134] Figure 5 The structure of the ranging block and the cycle used for UWB ranging is shown.

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

[0136] like Figure 5 As shown, a ranging block may include at least one ranging cycle. Each ranging cycle may include at least one ranging time slot.

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

[0138] The number and duration of time slots included in a ranging cycle can be varied between ranging cycles. This can be configured via control messages from the controller.

[0139] The UWB protocol is suitable for use cases that handle multiple users and provide fast authentication or payment. For example, the UWB protocol is suitable for users with UWB devices (e.g., smartphones) who can process authentication or payment without interacting on the UWB device to access door services through a UWB-based door system.

[0140] This disclosure presents an example system architecture, example OOB process (e.g., BLE process), ranging process, and transaction process for providing UWB services (e.g., gate system) to multiple users.

[0141] This disclosure also proposes a method for operating multiple UWB channels to reduce service latency.

[0142] The following description of the embodiments focuses primarily on gate services (smart gate services). However, this is merely an example. The embodiments of this disclosure are also applicable to various types of services (e.g., PoS payment services) that require rapid authentication or payment processing for multiple users. In this case, for example system architectures, example OOB processes (e.g., BLE processes), ranging processes, and transaction processes used to provide the services, reference can be made to the description above in conjunction with Figures 1 to 6.

[0143] Figure 6a This is a view illustrating multi-millisecond (MMS) UWB ranging operation according to an embodiment of the present disclosure.

[0144] MMS UWB can be a mode defined in IEEE 802.15.4ab that transmits multiple segments / packets via UWB at regular intervals (e.g., 0.5ms, 1ms, etc.) to enhance link budget and time-of-flight (ToF) accuracy.

[0145] The "link budget" refers to the sum of power and loss factor required for data transmission between the transmitter and receiver. It considers all losses and gains occurring from the time the signal is transmitted until it is received at the receiver. The link budget can be calculated by taking into account factors such as transmit power, receiver sensitivity, transmission distance, transmission medium (atmosphere, obstacles, etc.), antenna gain, and loss factor. In UWB systems, considering the link budget, performance can be enhanced by selecting appropriate antennas, transmit power, receivers, and transmitters.

[0146] Here, the transmission intervals between multiple segments / packets are not limited to a specific length. For example, each segment (or a UWB packet containing each segment) can be transmitted multiple times via UWB at 1ms intervals. Such multiple segments / packets can be used for UWB ranging (e.g., SS-TWR, DS-TWR, etc.). UWB systems should comply with the maximum transmit power limits defined by regulatory agencies to avoid unnecessary interference with other wireless systems. Therefore, the data length that can be transmitted in each transmission may need to comply with 1ms.

[0147] refer to Figure 6aThe first UWB device can send OOB packets (e.g., BLE packets) 600 to the second UWB device via an OOB channel (e.g., a BLE channel) and send multiple UWB segments 601, 602, 603... to the second UWB device via a UWB channel. The OOB packet 600 can provide initial time and frequency synchronization for the UWB segments 601, 602, 603..., allowing the UWB device to combine multiple 1ms segments to enhance the link budget. Furthermore, the OOB packet 600 can send the transmission start time and period information for the UWB segments 601, 602, 603... and minimize the UWB packet length by performing data offloading.

[0148] Figure 6b Operations for communication using BLE and UWB channels according to embodiments of this disclosure are illustrated.

[0149] refer to Figure 6b As an example of an OOB channel, the first UWB device 610 and the second UWB device 620 can send / receive BLE packets 640 and 645 via the BLE channel 630. Subsequently, the first UWB device 610 and the second UWB device 620 can send / receive multiple segments / packets 650, 651, 652, 655, 656, 657... via the UWB channel 635, which is time / frequency synchronized by BLE packets 640 and 645. In this case, the reception of multiple segments / packets 650, 651, 652, 655, 656, 657... in the UWB channel can be scheduled by BLE packets 640 and 645. Afterward, the first UWB device 610 and the second UWB device 620 can perform mutual status signaling notifications.

[0150] Figure 7 This is a view illustrating a central device and peripheral devices performing BLE-based UWB MMS ranging according to an embodiment of the present disclosure.

[0151] refer to Figure 7 The central device 700 is a device currently carried by the user and may include, for example, a cellular phone, a smartphone with wireless communication capabilities, a personal digital assistant (PDA) with wireless communication capabilities, a wireless modem, a portable computer with wireless communication capabilities, an imaging device such as a digital camera with wireless communication capabilities, a gaming device with wireless communication capabilities, a music storage and playback home appliance with wireless communication capabilities, an internet home appliance capable of wireless internet access and browsing, and a portable unit or terminal that includes a combination of these functions.

[0152] In addition, peripheral device 710 is a device that the user wants to discover their location, and may include, for example, a location tracker or a separate terminal that connects to central device 700 using short-range wireless communication.

[0153] In one embodiment, the central device 700 and the peripheral device 710 may establish an initial connection. In another embodiment, the peripheral device 710 may operate as an announcer and periodically send announcement messages (ADV-IND). In yet another embodiment, the central device 700 may operate as a scanner and, when an instruction from a user to discover the peripheral device 710 is received, perform a scan and then send a CONNECT-IND to the peripheral device 710 to initiate a connection event.

[0154] In this embodiment, examples of the information included in ADV-IND are shown in Table 1 or Table 2 below. ADV-IND can be cascaded and sent with the information included in Tables 1 and 2 below, or they can be sent separately.

[0155] [Table 1]

[0156] [Table 2]

[0157] Referring to Table 1 above, the central device 700 can filter the ADV_IND to be found from the information included in the ADV_IND using a BLE-based MMS ranging service Universally Unique Identifier (UUID). In an embodiment, the central device 700 and the peripheral device 710 use random addresses (such as resolvable private addresses (RPA)) for anonymity and can use BLE pairing binding or another method to ensure a shared key that can identify each other's random addresses. Referring to Table 2 above, the peripheral device 710 can include and send the announcement interval information in the ADV_IND. In an embodiment, although the announcement interval can be included in the ADV_IND, the central device 700 can obtain the announcement interval through data communication or a General Attribute (GATT) profile after the connection is established.

[0158] The central device 700 can operate as a scanner and use the information (shared key) secured when the connection to the peripheral device was previously established to scan the ADV_IND, which includes the BLE-based MMS ranging service UUID, as described in Table 1 above, to identify the peripheral device to be found.

[0159] In this scenario, upon discovering the ADV_IND of the peripheral device 710 to be located, the central device 700 can use the CONNECT_IND message to initiate a connection. In an embodiment, if an ADV_IND including the UUID of the BLE-based MMS ranging service of the peripheral device to be located is not received even after a scan has been performed up to the notification interval value obtained before the scan or a (preset) real multiple of this value, the central device 700 can notify the user that the device is not nearby (i.e., possibly by notifying the user that the device does not exist before the scan times out).

[0160] In an embodiment, if an ADV_IND containing the UUID of the BLE-based MMS ranging service of the peripheral device to be found is not received even after a scan has been performed up to the notification interval value obtained before the scan or a (preset) real multiple of this value, the central device 700 may notify the user to move to another location to find the peripheral device.

[0161] Figure 8 This is a view illustrating MMS ranging operation according to an embodiment of the present disclosure.

[0162] refer to Figure 8 The diagram shows the initiator 800 and the responder 810 performing the UWB MMS ranging operation, and... Figure 7 The central device 700 for UWB MMS ranging shown can operate as an initiator 800, and the peripheral device 710 can operate as a responder 810. In the embodiment, Figure 7 The central device 700 of the UWB MMS ranging shown can operate as a responder 810, and the peripheral device 710 can operate as an initiator 800.

[0163] exist Figure 8 In this process, the initiator 800 and the responder 810 can perform UWS MMS ranging operations by sending / receiving ranging sequence segments (RSF) 820, 821, 822, 823... and ranging integrity segments (RIF) 830, 831, 832, 833... RSF 820, 821, 822, 823... are used for time of arrival (ToA), and RIF 830, 831, 832, 833... are designed to prevent errors in distance measurement.

[0164] Figure 9 The present disclosure illustrates the creation of a connection between devices for reporting operations in a BLE channel and the execution of the reporting operation after UWB MMS ranging, according to an embodiment of the present disclosure.

[0165] Figure 9This is a view illustrating the operation of a peripheral device 900 as a responder and a central device 910 as an initiator in operation in a BLE channel 930 for UWB MMS ranging 960 according to an embodiment of the present disclosure.

[0166] refer to Figure 9 The central device 910 is the initiator of the ranging exchange, and the peripheral device 900 can be the responder that responds to the initiator during the ranging exchange. The BLE channel 930 can be implemented as an initialization channel, discovery channel, or coordination channel for UWB MMS ranging 960. The ranging channel may include a UWB channel 935 in which UWB MMS ranging 960 is performed.

[0167] In operation 940, the central device 910 may scan for ADV_IND messages within a set time interval on the BLE channel, and may not be able to receive ADV_IND messages. In an embodiment, the central device 910 may use information from previous connections (shared key) to scan for the device's ADV_IND, including the BLE-based MMS ranging service UUID, to identify the peripheral device 900 to be located.

[0168] In operation 942, peripheral device 900 may send (or broadcast) an ADV_IND message in the BLE channel. According to an embodiment, the ADV_IND message may include information as shown in Table 1 or Table 2 above.

[0169] In operation 944, the central device 910 can scan for ADV_IND messages within a set time interval on the BLE channel. In operation 946, the peripheral device 900 can send (or broadcast) ADV_IND messages, and the central device 910 can receive the ADV_IND messages sent by the peripheral device 900 based on the scan results. In operation 948, the central device 910 can send a CONNECT_IND message corresponding to the ADV_IND message to the peripheral device 900 on the BLE channel.

[0170] In operation 950, the central device 910 may initiate the sending of a polling (POLL) message to the peripheral device 900. In an embodiment, the polling message may include at least one of the following fields.

[0171] - Time offset (4 octets): The time from the completion of receiving polling messages until the MMS ranging occurs (at a resolution of 1 / 499.2 MHz). -UWB PHY configuration (3 octets) -UWB MAC configuration (2 octets) -NB MAC configuration (4 octets) In addition, the NB MAC configuration (4 octets) included in the polling message may include the following information.

[0172] - Ranging slot duration index (3 bits): 0-8 (matches {300, 600, ..., 2400} RSTU) - Ranging cycle duration (8 bits): 0-255 ranging time slots - Ranging block duration (8 bits): 0-255 ranging time slots - Reporting Mode (2 bits): 0 - None, 1 - Initiator only, 2 - Response only, 3 - Initiator and Response - Reserved for future use (3 bits) -RSF Offset (4 bits) - Offset for MMS ranging (RpRsfOffset in the image below) -RIF Offset (4 bits) - Offset for MMS ranging (RpRifOffset in the image below) In an embodiment, in the reporting mode (2 bits), in subsequent operation 970, the peripheral device 900 and the central device 910 can instruct methods for exchanging reports 970 and 975 regarding UWB MMS ranging 960. In an embodiment, when the reporting mode is 0 ('00'), the reporting mode can instruct neither the initiator nor the responder to send a report. In an embodiment, when the reporting mode is 1 ('01'), the reporting mode can instruct only the initiator to send a report. In an embodiment, when the reporting mode is 2 ('10'), the reporting mode can instruct only the responder to send a report. In an embodiment, when the reporting mode is 3 ('11'), the reporting mode can instruct both the initiator and the responder to send reports.

[0173] In operation 955, peripheral device 900 can send a RESP message to central device 910 as a response. When central device 910 receives the RESP message during a preset time offset 957, in operation 960, central device 910 can act as initiator 920 and perform UWB MMS ranging with peripheral device 920 as responder 925 in UWB channel 935.

[0174] In operation 970, peripheral device 900 and central device 910 can exchange reports 970 and 975 regarding UWB MMS ranging 960. Afterwards, following the execution of UWB MMS ranging, the ranging results can be sent to each other via report messages. In this case, the report exchange process can be omitted based on the value indicated by the report mode field included in the polling message of operation 950, and one-way transmission between central device and peripheral device / peripheral device and central device is also possible.

[0175] In an embodiment, when subsequent BLE communication becomes available after UWB MMS ranging, a report of operation 970 can be sent.

[0176] In an embodiment, the report message may include at least one of the following information, and may be included in a list.

[0177] - Block index (2 octets): Corresponds to the block index of the current report. - Round Index (2 octets): Corresponds to the round index of the current report. - Response time count (2 octets): The number of response times included in the report. - Response time ((N+1)*5 octets): The time between RSF / RIF reception (from the initiator) and RSF / RIF transmission (from the responder) in UWB MMS ranging. Figure 10 The present disclosure illustrates the creation of a connection between devices in a BLE channel and the execution of repeated UWB MMS ranging operations according to an embodiment of the present disclosure.

[0178] Figure 10 It shows the relationship with Figure 9 A similar process is shown, but the process is as follows: after a connection is created using the CONNECT_IND sent by the central device when an ADV_IND is received from a specific peripheral device, UWB MMS ranging is repeatedly performed during each block duration.

[0179] Figure 10 This is a view illustrating the operation of a peripheral device 1000 as a responder and a central device 1010 as an initiator in operation in a BLE channel 1030 for UWB MMS ranging 1060, 1070, 1080 according to an embodiment of the present disclosure.

[0180] refer to Figure 10 The central device 1010 is the initiator of the ranging exchange, and the peripheral device 1000 can be the responder that responds to the initiator during the ranging exchange. The BLE channel 1030 can be implemented as an initialization channel, discovery channel, or coordination channel for UWB MMS ranging 1060, 1070, and 1080. The ranging channel may include a UWB channel 1035 in which UWB MMS ranging 1060 is performed.

[0181] The description of operations 1040 to 1160 can be used Figure 9 The descriptions of operations 940 to 960 are used instead.

[0182] In operation 1055, peripheral device 1000 may send a RESP message to central device 1010 as a response. When central device 1010 receives the RESP message during a preset time offset 1057, in operation 1060, central device 1010 may, as initiator 1020, perform UWB MMS ranging with peripheral device 1020 as responder 1025 in UWB channel 1035.

[0183] In this embodiment, in UWB channel 1035, the initiator 1020 and the responder 1025 can perform UWB MMS ranging 1060, 1070, and 1080 multiple times in blocks, until the termination signaling 1090 occurs. The central device 1010, operating as the initiator 1020, and the peripheral device 1000, operating as the responder 1025, can send / receive reports (1065, 1067, 1075, 1077, 1085, 1087) after completing each UWB MMS ranging 1060, 1070, and 1080.

[0184] Figure 11 This illustrates an embodiment of the present disclosure of performing UWB MMS ranging operations without creating a connection between devices for reporting operations in a BLE channel.

[0185] Figure 11 This illustrates a scenario where neither the initiator nor the responder sends a report after a UWB MMS ranging operation. In this embodiment, Figure 11 The following situation is illustrated: During the process of central device 1110 successfully searching for peripheral device 1100 in BLE channel 1130 and establishing a connection, the reporting mode set by the SCAN_REQ message indicates that neither the initiator nor the responder sends a report after UWBMMS ranging.

[0186] Figure 11 This is a view illustrating the operation of a peripheral device 1100 as a responder and a central device 110 as an initiator in operation in a BLE channel 1030 for UWB MMS ranging 1160 according to an embodiment of the present disclosure.

[0187] refer to Figure 11 Central device 1110 is the initiator of ranging exchange, and peripheral device 1100 can be the responder that responds to the initiator during ranging exchange. BLE channel 1130 can be implemented as an initialization channel, discovery channel, or coordination channel for UWB MMS ranging 1160. The ranging channel may include UWB channel 1135 in which UWB MMS ranging 1160 is performed.

[0188] The descriptions of operations 1140 to 1146 can be used Figure 9 The descriptions of operations 940 to 946 are used instead.

[0189] When an ADV_IND sent by the device to be located is detected in operation 1144, the central device 1110 can send UWB MMS ranging information using a SCAN_REQ message in operation 1150. In an embodiment, the SCAN_REQ message may include at least one piece of information from Table 3.

[0190] [Table 3]

[0191] Referring to Table 3, the SCAN_REQ message may include at least one of the UWB PHY configuration, UWB MAC configuration, and NB MAC configuration fields. Additionally, the NB MAC configuration field may include information about the reporting mode (2 bits), similar to... Figure 9 The polling message includes the NB MAC configuration field. In an embodiment, in report mode (2 bits), peripheral device 1100 and central device 1110 can indicate a method for exchanging reports about UWB MMS ranging 1160, and... Figure 11 In this embodiment, the reporting mode can be set to 0 ('00') to indicate that neither the initiator nor the responder sends a report. In operation 1155, the peripheral device 1100 can send a SCAN_RSP message. When the central device 1110 receives the SCAN_RSP message during time offset 1157, in operation 1160, the central device 1110, as the initiator 1120, can perform UWB MMS ranging with the peripheral device 1100, as the responder 1125, in UWB channel 1135. In this embodiment, if an ADV_IND is not received even after a scan has been performed for a previously obtained notification interval value or a (preset) real multiple of this value, the central device 1110 can notify the user that the device is not nearby (i.e., possibly by notifying the user that the device does not exist before the scan timeout).

[0192] In an embodiment, if the central device 1110 does not receive an ADV_IND containing the UUID of the BLE-based MMS ranging service for the peripheral device to be found, even if a scan has been performed up to the notification interval value obtained before the scan or a (preset) real multiple of this value, the central device 1110 may notify the user to move to another location to find the peripheral device.

[0193] Figure 12 An implicit termination operation is shown in BLE-based MMS ranging according to an embodiment of the present disclosure.

[0194] Figure 12 As shown Figure 11In the illustrated embodiment, there is no reporting operation after UWB MMS ranging, and the descriptions of operations 1240 to 1260 can be replaced by the descriptions of operations 1140 to 1160.

[0195] refer to Figure 12 When the central device 1210 receives a SCAN-RSP message during time offset 1257, in operation 1260, the central device 1210, as the initiator 1220, can perform UWB MMS ranging with the peripheral device 1200, as the responder 1225, in UWB channel 1235, and thereafter can perform repeated UWB MMS ranging (1270, 1280). In this case, since the central device 1210 and the peripheral device 1200 have not yet established a BLE channel connection for reporting, there is no data channel (e.g., BLE channel) to notify termination after performing UWB MMS ranging. Therefore, in UWB channel 1235, the central device 1240, as the initiator 1220, can implicitly convey the termination intention by not sending the RSF or RIF included in the MMS ranging operation.

[0196] Figure 13a and Figure 13b This is a flowchart illustrating the operation of a central device according to an embodiment of the present disclosure.

[0197] Figure 13a and Figure 13b The central equipment and peripheral equipment in the system may include Figure 7 The central device 700 and peripheral device 710 are shown.

[0198] In step 1300, the central device may begin discovering peripheral devices. In an embodiment, in step 1300, the central device may begin discovering peripheral devices when it receives device discovery input from the user.

[0199] In step 1310, the central device may begin scanning the ADV_IND sent by the peripheral device.

[0200] In step 1320, the central device may determine whether it has received the ADV_IND of the peripheral device to be found. If the central device determines in step 1320 that it has not yet received the ADV_IND of the peripheral device to be found, in step 1330, the central device may determine whether the scan time has exceeded the notification interval or a real multiple of the notification interval. In an embodiment, the notification interval information may be included in the ADV_IND received when performing the initial connection to the peripheral device to be found. In an embodiment, the notification interval information may also be obtained from the peripheral device via data communication or a GATT profile after the connection with the peripheral device to be found is established.

[0201] When the central device determines in step 1330 that the scanning time has exceeded the notification interval, in step 1333, the central device may display a device discovery failure notification. Subsequently, in step 1335, the central device may terminate the discovery of peripheral devices.

[0202] When the central device determines in step 1330 that the scanning time has not exceeded the notification interval, the central device may scan ADV_IND again in step 1310.

[0203] When the central device determines in step 1320 that it has received the ADV_IND of the peripheral device to be found, in step 1340, the central device can determine whether a report is required after MMS ranging. In this embodiment, whether a report is required can be preset, and the central device can indicate to the peripheral device whether a report is required in the "REPORT MODE" field included in the polling message to be sent to the peripheral device to be found or in the SCAN_REQ.

[0204] When the central device determines in step 1340 that a report is required after MMS ranging, it may send a CONNECT_IND message to the peripheral device in step 1350. In step 1352, the central device may determine whether the connection has been successfully established. When the central device determines in step 1352 that the connection has been successfully established, it may send a polling message in step 1354. In step 1356, the central device may determine whether a response has been received from the peripheral device. When the central device determines in step 1356 that a response has not yet been received from the peripheral device, it may send a polling message to the peripheral device in step 1354.

[0205] When the central device determines in step 1356 that it has received a response from the peripheral device, in step 1358, the central device can perform UWB MMS ranging. In step 1360, the central device can send / receive reports with the peripheral device. In step 1362, the central device can determine whether it needs to terminate UWB MMS ranging. If termination is not required in step 1362, the central device can perform UWB MMS ranging with the peripheral device in step 1358. Therefore, the central device can repeatedly perform UWB MMS ranging with the peripheral device and send / receive reports until it is determined in step 1362 that it needs to terminate UWB MMS ranging.

[0206] When the central device determines in step 1362 that UWB MMS ranging needs to be terminated, the central device can send a termination message to the peripheral device in step 1364 and end device discovery in step 1366. In this embodiment, the termination message can be sent in an OOB channel that includes a BLE channel, rather than in the channel where UWB ranging is performed.

[0207] If the central device determines in step 1352 that the connection has not yet been successful, the central device may start an ADV_IND scan and perform subsequent operations in step 1310.

[0208] When the central device determines in step 1340 that no report is needed after MMS ranging, it can send a SCAN_REQ to the peripheral device in step 1370. In step 1372, the central device can determine whether a SCAN_RSP has been received. If the central device determines in step 1372 that a SCAN_RSP has not yet been received from the peripheral device, it can start an ADV_IND scan and perform subsequent operations in step 1310.

[0209] When the central device determines in step 1372 that it has received the SCAN_RSP, in step 1374, the central device can perform UWB MMS ranging. In step 1376, the central device can determine whether it needs to terminate the UWB MMS ranging. When the central device determines in step 1376 that it does not need to terminate, the central device can perform UWB MMS ranging with the peripheral device in step 1374. Therefore, the central device can repeatedly perform UWB MMS ranging with the peripheral device until it determines in step 1376 that it needs to terminate the UWB MMS ranging. When the central device determines in step 1376 that it needs to terminate the UWB MMS ranging, in step 1378, the central device can choose not to send UWB MMS ranging-related messages and can end device discovery in step 1380.

[0210] Figure 14a and Figure 14b A BLE-encoded PHY used in BLE-based MMS ranging according to an embodiment of the present disclosure is shown.

[0211] Figure 14a and Figure 14b The description states that during BLE-based MMS ranging operations, the BLE-encoded PHY can be used to cover distances that can be detected by MMS ranging because the coverage distance of MMS ranging is farther than that of existing BLE (1M / 2M PHY).

[0212] To use the encoded PHY, peripheral devices can replace existing messages with the following messages.

[0213] -ADV_IND→AUX_ADV_IND -CONNECT_IND→AUX_CONNECT_REQ -SCAN_REQ→AUX_SCAN_REQ -SCAN_RSP→AUX_SCAN_RSP Figure 14a An example of a peripheral device sending messages using an encoded PHY is shown. In operation 1410, when an announcement event and an extended announcement event are initiated (1400), the peripheral device can send ADV_EXT_IND. In operations 1412 and 1414, the peripheral device can periodically send ADV_EXT_IND until the announcement event ends (1420). In operation 1430, the peripheral device can periodically send AUX_ADV_IND until the extended announcement event ends (1435).

[0214] Figure 14b An example of a BLE-encoded PHY packet is shown.

[0215] Figure 15 A structural diagram illustrating a first electronic device according to an embodiment of the present disclosure is shown.

[0216] exist Figure 15 In one embodiment, the first electronic device may be an electronic device corresponding to a UWB device, including a UWB device or including a part of a UWB device.

[0217] exist Figure 15 In some embodiments, the first electronic device may include Figure 7 To the central device shown in Figure 14.

[0218] refer to Figure 15 The electronic device may include a transceiver 1510, a controller 1520, and a storage unit 1530. In this disclosure, the controller may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0219] Transceiver 1510 can send and receive signals to / from another entity. Transceiver 1510 can send / receive data with another device using, for example, UWB communication and / or OOB communication (e.g., BLE).

[0220] The controller 1520 includes at least one processor and can control the overall operation of the electronic device according to the embodiments presented in this disclosure. For example, the controller 1520 can control the signal flow between each block to perform operations according to the flowchart above. Specifically, the controller 1520 can control the operation of the electronic device (e.g., the operation of the frame) described with reference to Figures 1 to 14.

[0221] At least one processor can be controlled to: receive input from a user indicating a search for a second electronic device. At least one processor can be controlled to: scan for Bluetooth Low Energy (BLE) announcement messages associated with Ultra Wideband (UWB) Multi-Millisecond (MMS) ranging from the second electronic device. At least one processor can be controlled to: determine whether a time corresponding to a real multiple of the announcement interval associated with the second electronic device has elapsed if no BLE announcement message is received from the second electronic device. At least one processor can be controlled to: stop scanning for BLE announcement messages if a time corresponding to a real multiple of the announcement interval has elapsed. In an embodiment, information about the announcement interval may have already been received from the second electronic device.

[0222] At least one processor can control itself to determine, based on predetermined settings, whether a report on UWB MMS ranging is required upon receiving a BLE notification message from a second electronic device. At least one processor can also control itself to send a CONNECT_IND message to the second electronic device when a report on UWB MMS ranging is required.

[0223] At least one processor can be controlled to: send a SCAN_REQ message to a second electronic device when no report on UWB MMS ranging is needed. At least one processor can be controlled to: send a polling message to the second electronic device after sending a CONNECT_IND message. At least one processor can be controlled to: perform UWB MMS ranging with the second electronic device upon receiving a response message from the second electronic device. At least one processor can be controlled to: perform at least one of sending a report to or receiving a report from the second electronic device in a BLE channel based on predetermined settings. In an embodiment, the polling message may include an indicator indicating a method for reporting on UWB MMS ranging.

[0224] Storage unit 1530 can store at least one of the information transmitted and received by transceiver 1510 and the information generated by controller 1520. For example, storage unit 1530 can store the information shown in Figures 1 to 1520 above. Figure 15 The information and data required for the described method. In an embodiment, the storage unit may include the aforementioned security components.

[0225] Figure 16 A structural diagram illustrating a second electronic device according to an embodiment of the present disclosure is shown.

[0226] exist Figure 16 In one embodiment, the second electronic device may be an electronic device corresponding to a UWB device, including a UWB device or including a part of a UWB device.

[0227] exist Figure 16 In some embodiments, the second electronic device may include Figure 7 To the peripheral devices shown in Figure 14.

[0228] refer to Figure 16 The electronic device may include a transceiver 1610, a controller 1620, and a storage unit 1630. In this disclosure, the controller may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0229] Transceiver 1610 can send and receive signals to / from another entity. Transceiver 1610 can send / receive data with another device using, for example, UWB communication and / or OOB communication (e.g., BLE).

[0230] The controller 1620 includes at least one processor and can control the overall operation of the electronic device according to the embodiments presented in this disclosure. For example, the controller 1620 can control the signal flow between each block to perform operations according to the flowchart above. Specifically, the controller 1620 can control the operation of the electronic device (e.g., the operation of the frame) described with reference to Figures 1 to 14.

[0231] At least one processor can be controlled to send information to a first electronic device regarding the notification interval associated with a second electronic device. At least one processor can also be controlled to send Bluetooth Low Energy (BLE) notification messages associated with Ultra-Wideband (UWB) Multi-Millisecond (MMS) ranging to the first electronic device. In an embodiment, scanning for BLE notification messages can cease after a time exceeding a real multiple of the notification interval associated with the second electronic device.

[0232] At least one processor can be controlled to: receive a CONNECT_IND message from a first electronic device when a report on UWB MMS ranging is needed. At least one processor can be controlled to: receive a SCAN_REQ message from the first electronic device when a report on UWB MMS ranging is not needed. At least one processor can be controlled to: receive a polling message from the first electronic device after receiving the CONNECT_IND message. At least one processor can send a response message to the first electronic device. At least one processor can perform UWB MMS ranging with the first electronic device. In an embodiment, the polling message may include an indicator indicating a method for reporting on UWB MMS ranging. At least one processor can be controlled to: perform at least one of sending a report to or receiving a report from the first electronic device in a BLE channel based on the indicator.

[0233] Storage unit 1630 can store at least one of the information transmitted and received by transceiver 1610 and the information generated by controller 1620. For example, storage unit 1630 can store the information shown in Figures 1 to 1620 above. Figure 16 The information and data required for the described method. In an embodiment, the storage unit may include the aforementioned security components.

[0234] In the specific embodiments described above, depending on the proposed specific embodiments, the components included in this disclosure are represented in a singular or plural form. However, the singular or plural forms are chosen to be sufficient to satisfy the context suggested for ease of description, and this disclosure is not limited to singular or plural components. As used herein, the singular forms “a,” “an,” and “the” are intended to also include the plural forms, unless the context clearly indicates otherwise.

[0235] Furthermore, although specific embodiments of this disclosure have been described above, various modifications can be made thereto without departing from the scope of this disclosure. Therefore, the scope of this invention should not be limited to the above embodiments, but should be defined by the appended claims and their equivalents.

Claims

1. A method for using a first electronic device, the method comprising: Receive information from the second electronic device regarding the notification interval associated with the second electronic device; Receive input from the user instructing them to search for the second electronic device; In response to the input, scan the second electronic device for Bluetooth Low Energy (BLE) announcement messages associated with UWB multi-millisecond (MMS) ranging; and If no BLE notification message is received from the second electronic device within a time period corresponding to a real multiple of the notification interval, the operation of scanning the BLE notification message is stopped.

2. The method according to claim 1, further comprising: Upon receiving the BLE notification message from the second electronic device, determine whether a report on the UWB MMS ranging is required based on predetermined settings; as well as If a report on the UWB MMS ranging is required, a CONNECT_IND message is sent to the second electronic device.

3. The method according to claim 2, further comprising: If no report on the UWB MMS ranging is required, a SCAN_REQ message is sent to the second electronic device.

4. The method according to claim 2, further comprising: After sending the CONNECT_IND message, a polling message is sent to the second electronic device; Upon receiving a response message from the second electronic device, perform UWBMMS ranging with the second electronic device; and Based on predetermined settings, at least one of the following is performed in the BLE channel: sending a report to or receiving a report from the second electronic device, wherein the polling message includes an indicator indicating a scheme for reporting on the UWB MMS ranging.

5. A method for using a second electronic device, the method comprising: Send information to the first electronic device about the notification interval associated with the second electronic device; as well as Send a Bluetooth Low Energy (BLE) notification message associated with UWB multi-millisecond (MMS) ranging to the first electronic device. Specifically, scanning of the BLE notification message is stopped if the time exceeds a real multiple of the notification interval.

6. The method according to claim 5, further comprising: When a report on the UWB MMS ranging is required, a CONNECT_IND message is received from the first electronic device.

7. The method according to claim 6, further comprising: If no report on the UWB MMS ranging is required, a SCAN_REQ message is received from the first electronic device.

8. The method according to claim 6, further comprising: After receiving the CONNECT_IND message, a polling message is received from the first electronic device, the polling message including an indicator indicating a scheme for reporting on the UWB MMS ranging; Send a response message to the first electronic device; Perform UWB MMS ranging with the first electronic device; and Based on the indicator, at least one of the following is performed in the BLE channel: sending a report to the first electronic device or receiving a report from the first electronic device.

9. A first electronic device, the first electronic device comprising: transceiver; as well as At least one processor, wherein the at least one processor is configured to: Receive information from the second electronic device regarding the notification interval associated with the second electronic device; Receive input from the user instructing them to search for the second electronic device; In response to the input, scan the second electronic device for Bluetooth Low Energy (BLE) announcement messages associated with UWB multi-millisecond (MMS) ranging; and If no BLE notification message is received from the second electronic device within a time period corresponding to a real multiple of the notification interval, the operation of scanning the BLE notification message is stopped.

10. The first electronic device according to claim 11, wherein, The at least one processor is further configured to: Upon receiving a BLE notification message from the second electronic device, it is determined, based on predetermined settings, whether a report regarding the UWB MMS ranging is required; as well as If a report on the UWB MMS ranging is required, a CONNECT_IND message is sent to the second electronic device.

11. The first electronic device according to claim 12, wherein, The at least one processor is further configured to: If no report on the UWB MMS ranging is required, a SCAN_REQ message is sent to the second electronic device.

12. The first electronic device according to claim 12, wherein, The at least one processor is configured to: After sending the CONNECT_IND message, a polling message is sent to the second electronic device; Upon receiving a response message from the second electronic device, perform UWBMMS ranging with the second electronic device; and Based on predetermined settings, at least one of the following is performed in the BLE channel: sending a report to or receiving a report from the second electronic device, wherein the polling message includes an indicator indicating a scheme for reporting on the UWB MMS ranging.

13. A second electronic device, the second electronic device comprising: transceiver; as well as At least one processor, wherein the at least one processor is configured to: Sending information to the first electronic device about the notification interval associated with the second electronic device; and Send a Bluetooth Low Energy (BLE) notification message associated with UWB multi-millisecond (MMS) ranging to the first electronic device. Specifically, scanning of the BLE notification message is stopped if the time exceeds a real multiple of the notification interval.

14. The second electronic device according to claim 13, wherein, The at least one processor is configured to: Receive a CONNECT_IND message from the first electronic device if a report on the UWB MMS ranging is required; and If no report on the UWB MMS ranging is required, a SCAN_REQ message is received from the first electronic device.

15. The second electronic device according to claim 14, wherein, The at least one processor is configured to: After receiving the CONNECT_IND message, a polling message is received from the first electronic device, the polling message including an indicator indicating a scheme for reporting on the UWB MMS ranging; Send a response message to the first electronic device; Perform UWB MMS ranging with the first electronic device; and Based on the indicator, at least one of the following is performed in the BLE channel: sending a report to the first electronic device or receiving a report from the first electronic device.

Images