UWB device for transmitting and receiving multiple data packet and

Abstract

A method for UWB multiplexing transmission is disclosed. A method performed by a first UWB device according to an embodiment disclosed herein may comprise the steps of: transmitting a ranging control message for UWB multiplexed transmission, the ranging control message being transmitted by UWB or NB in a first time slot within a ranging cycle; transmitting a trigger data packet for triggering UWB multiplexing transmission, the trigger data packet being transmitted by UWB or NB in a second time slot within the ranging cycle; receiving, by the UWB, a first data packet transmitted by the second UWB device in a third time slot within the ranging cycle based on the ranging control message; and receiving, by the UWB, a second data packet transmitted by the third UWB device in a third time slot within the ranging cycle based on the ranging control message.

Description

Technical Field

[0001] The present disclosure relates to ultra-wideband (UWB) communication, and more particularly, to a UWB device configured to transmit / receive multiple data packets and a method for operating the device. Background Art

[0002] The Internet, a human-centric connectivity network in which humans generate and consume information, is now evolving into the Internet of Things (IoT), in which distributed entities such as things exchange and process information. The Internet of Everything (IoE) has emerged, which is a combination of IoT technology and big data processing technology through connection with a cloud server or the like. IoT implementations require technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology", and "security technology". In recent years, sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), etc. have been widely studied.

[0003] Such an IoT environment can provide intelligent Internet technology (IT) services that create new value for human life by collecting and analyzing data generated between connected things. IoT can be applied to various fields through the fusion and combined application between existing information technology (IT) and various industrial applications, including smart home, smart building, smart city, smart car or connected car, smart grid, healthcare, smart appliances, and advanced medical services.

[0004] With the development of wireless communication systems, various services can be provided, and thus a way to effectively provide these services is required. For example, a ranging technique that measures the distance between electronic devices by using ultra-wideband (UWB) can be used. Summary of the Invention

[0005] Technical Problem

[0006] The present disclosure proposes a method that can reduce the power consumption when an ultra-wideband (UWB) device receives a UWB data packet from another UWB device.

[0007] Technical Solution

[0008] According to one aspect of the present disclosure, a method for operating a first ultra-wideband (UWB) device may include: transmitting, in a first time slot within a ranging cycle, a ranging control message for UWB multiple transmissions via UWB or narrowband (NB); transmitting, in a second time slot within the ranging cycle, a trigger packet for triggering UWB multiple transmissions via UWB or NB; receiving, based on the ranging control message, a first data packet transmitted by a second UWB device in a third time slot within the ranging cycle via UWB; and receiving, based on the ranging control message, a second data packet transmitted by a third UWB device in the third time slot within the ranging cycle via UWB.

[0009] According to one aspect of the present disclosure, a method for operating a second ultra-wideband (UWB) device may include: receiving, in a first time slot within a ranging cycle, a ranging control message for UWB multiple transmissions from a first UWB device via UWB or narrowband (NB); receiving, in a second time slot within the ranging cycle, a trigger packet for triggering UWB multiple transmissions from the first UWB device via UWB or NB; and transmitting, based on the ranging control message, a first data packet in a third time slot within the ranging cycle via UWB, wherein the third time slot within the ranging cycle is for a second data packet to be transmitted by a third UWB device based on the ranging control message.

[0010] According to one aspect of the present disclosure, a first ultra-wideband (UWB) device may include a transceiver and a controller connected to the transceiver and configured to control the transceiver. The first UWB device may be configured to: transmit, in a first time slot within a ranging cycle, a ranging control message for UWB multiple transmissions via UWB or narrowband (NB); transmit, in a second time slot within the ranging cycle, a trigger packet for triggering UWB multiple transmissions via UWB or NB; receive, based on the ranging control message, a first data packet transmitted by a second UWB device in a third time slot within the ranging cycle via UWB; and receive, based on the ranging control message, a second data packet transmitted by a third UWB device in the third time slot within the ranging cycle via UWB.

[0011] According to one aspect of the present disclosure, a second ultra-wideband (UWB) device may include a transceiver and a controller connected to the transceiver and configured to control the transceiver. The second UWB device may be configured to: receive, in a first time slot within a ranging cycle, a ranging control message for UWB multiple transmissions from a first UWB device via UWB or narrowband (NB); receive, in a second time slot within the ranging cycle, a trigger packet for triggering UWB multiple transmissions from the first UWB device via UWB or NB; and transmit, based on the ranging control message, a first data packet in a third time slot within the ranging cycle via UWB. The third time slot within the ranging cycle may be for a second data packet to be transmitted by a third UWB device based on the ranging control message.

[0012] A method for operating a first ultra-wideband (UWB) device may include: transmitting a ranging control message for UWB communication in a first time slot within a ranging cycle; receiving, based on the ranging control message, a first data packet transmitted by a second UWB device in a second time slot within the ranging cycle; and receiving, based on the ranging control message, a second data packet transmitted by a third UWB device in the second time slot within the ranging cycle.

[0013] According to various embodiments of the present disclosure, a method for operating a second ultra-wideband (UWB) device may include: receiving, in a first time slot within a ranging cycle, a ranging control message for UWB communication from a first UWB device; and transmitting, based on the ranging control message, a first data packet in a second time slot within the ranging cycle. In the second time slot within the ranging cycle, a second data packet may be transmitted by a third UWB device based on the ranging control message.

[0014] According to various embodiments of the present disclosure, a first ultra-wideband (UWB) device may include a transceiver and a controller connected to the transceiver and configured to control the transceiver. The controller may control, in a first time slot within a ranging cycle, the transmission of a ranging control message for UWB communication; control, based on the ranging control message, the reception of a first data packet transmitted by a second UWB device in a second time slot within the ranging cycle; and control, based on the ranging control message, the reception of a second data packet transmitted by a third UWB device in the second time slot within the ranging cycle.

[0015] According to various embodiments of the present disclosure, a second ultra-wideband (UWB) device may include a transceiver and a controller connected to the transceiver and configured to control the transceiver. The controller may control, in a first time slot within a ranging cycle, the reception of a ranging control message for UWB communication from a first UWB device; and control, based on the ranging control message, the transmission of a first data packet in a second time slot within the ranging cycle. In the second time slot within the ranging cycle, a second data packet may be transmitted by a third UWB device based on the ranging control message.

[0016] Beneficial Effects

[0017] The UWB device according to an embodiment of the present disclosure may minimize and / or optimize the time required to receive UWB data packets from other UWB devices, thereby reducing power consumption.

[0018] The UWB device according to an embodiment of the present disclosure may effectively receive multiple data packets from multiple UWB devices. Brief Description of the Drawings

[0019] Figure 1 An exemplary architecture of an electronic device according to an embodiment of the present disclosure is shown.

[0020] Figure 2 Shows a communication system including a plurality of electronic devices according to an embodiment of the present disclosure.

[0021] Figure 3 Shows a method for a plurality of electronic devices to perform communication according to an embodiment of the present disclosure.

[0022] Figure 4 Shows the structure of a UWB MAC frame according to an embodiment of the present disclosure.

[0023] Figure 5 Shows the structure of a UWB PHY data packet according to an embodiment of the present disclosure.

[0024] Figure 6 Shows an example of the structure of a ranging block and a cycle for UWB ranging according to an embodiment of the present disclosure.

[0025] Figure 7 Shows an example of the structure of a ranging cycle for UWB ranging according to an embodiment of the present disclosure.

[0026] Figure 8 Shows a ranging message exchange process according to a ranging scheme according to an embodiment of the present disclosure.

[0027] Figure 9 Shows the structure of a synchronization header (SHR) for UWB ranging according to an embodiment of the present disclosure.

[0028] Figure 10A Is a schematic diagram for describing a data packet transmission method through a UWB device according to an embodiment of the present disclosure.

[0029] Figure 10B Shows the RDM list field in the RDM IE according to an embodiment of the present disclosure.

[0030] Figure 11A Is a schematic diagram for describing a data packet transmission method through a UWB device according to another embodiment of the present disclosure.

[0031] Figure 11B Shows the RDM list field in the RDM IE according to another embodiment of the present disclosure.

[0032] Figure 12 Shows a multi-transmission mode process according to an embodiment of the present disclosure.

[0033] Figure 13 Shows an example of a scheduling IE for multi-transmission according to an embodiment of the present disclosure.

[0034] Figure 14Shows an example of a multi - transmission method using UWB according to an embodiment of the present disclosure.

[0035] Figure 15 Shows an example of a multi - transmission method using NB assistance according to an embodiment of the present disclosure.

[0036] Figure 16 Shows an example of a method for performing ranging through multi - transmission using NB assistance according to an embodiment of the present disclosure.

[0037] Figure 17 Shows the structure of a first UWB device according to an embodiment of the present disclosure.

[0038] Figure 18 Shows the structure of a second UWB device according to an embodiment of the present disclosure.

[0039] Figure 19 Shows another example of a multi - transmission method using NB assistance according to an embodiment of the present disclosure.

[0040] Figure 20 Shows the data packet format of an NB control data packet according to an embodiment of the present disclosure.

[0041] Figure 21 Shows the data packet format of an NB polling data packet according to an embodiment of the present disclosure. Detailed Description of the Invention

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

[0043] In the process of describing the embodiments, descriptions related to technical content that is well - known in the relevant art and not directly related to the present disclosure will be omitted. Omitting such unnecessary descriptions is to prevent obscuring the main idea of the present disclosure and to more clearly convey the main idea.

[0044] For the same reason, in the drawings, some elements may be exaggerated, omitted, or schematically shown. Additionally, the size of each element does not exactly reflect the actual size. In the corresponding drawings, the same or corresponding elements are assigned the same reference numerals.

[0045] By referring to the embodiments described in detail below in conjunction with the accompanying drawings, the advantages and features of the present disclosure and the manner of its implementation will become apparent. However, the present disclosure is not limited to the embodiments stated below, but can be implemented in various different forms. The following embodiments are provided only to completely disclose the present disclosure and to inform those skilled in the art of the scope of the present disclosure, and the present disclosure is defined only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals indicate the same or similar elements.

[0046] In this document, it should be understood that each block of the flowchart illustration and combinations of blocks in the flowchart illustration can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, such that the instructions executed via the processor of the computer or other programmable data processing device create means for implementing the functions specified in one or more flowchart blocks. These computer program instructions can also be stored in a computer-usable or computer-readable memory, which can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-usable or computer-readable memory produce an article of manufacture including instruction means that implement the functions specified in the one or more flowchart blocks. Instructions executed on a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus to produce a computer-implemented process can provide steps for implementing the functions specified in the flowchart blocks.

[0047] In addition, each block in the flowchart illustration can represent a module, a segment of code, or a portion of code that includes one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions recited in the blocks may occur out of order. For example, depending on the functionality involved, two blocks shown in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order.

[0048] As used in the embodiments of the present disclosure, the term "unit" refers to a software element or a hardware element that performs a predetermined function, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), and a "unit" can perform certain functions. However, the meaning of "unit" is not always limited to software or hardware. A "unit" can be constructed to be stored in an addressable storage medium or to execute on one or more processors. Thus, a "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. The elements and functions provided by a "unit" can be combined into a smaller number of elements or "units" or divided into a larger number of elements or "units". In addition, the elements and "units" can be implemented as one or more CPUs within a reproducing apparatus or a secure multimedia card. In addition, according to some embodiments, a "unit" can include one or more processors.

[0049] As used herein, the terms "terminal" or "device" may also be referred to as mobile station (MS), user equipment (UE), user terminal (UT), wireless terminal, access terminal (AT), terminal, subscriber unit, subscriber station (SS), wireless device, wireless communication device, wireless transmit / receive unit (WTRU), mobile node, mobile device, or other terms. Various examples of terminals may include: cellular phones, smart phones with wireless communication capabilities, personal digital assistants (PDAs) with wireless communication capabilities, wireless modems, portable computers with wireless communication capabilities, image capture devices (such as digital cameras) with wireless communication capabilities, game devices with wireless communication capabilities, music storage and playback household appliances with wireless communication capabilities, Internet household appliances capable of wireless Internet access and browsing, and portable units or terminals that combine these functions. In addition, the terminal may include machine-to-machine (M2M) terminals and machine type communication (MTC) terminals / devices, but is not limited thereto. In the specification, the terminal may be referred to as an electronic device or simply as a device.

[0050] Hereinafter, the operating principle of the present disclosure will be described in detail with reference to the accompanying drawings. In the following description of the present disclosure, when it is determined that the description may make the subject matter of the present disclosure unnecessarily unclear, the detailed description of known functions or configurations incorporated herein will be omitted. The terms described below are terms defined in consideration of the functions in the present disclosure and may vary according to the user, the user's intention, or habit. Therefore, the definitions of the terms should be determined based on the content throughout the specification.

[0051] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the following description of the embodiments of the present disclosure, a communication system using UWB will be described by way of example, but the embodiments of the present disclosure may be applied to other communication systems having a similar technical background or characteristics. Examples of such communication systems may include the communication systems Bluetooth or ZigBee. Therefore, based on the judgment of those skilled in the art, the embodiments of the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure.

[0052] In addition, when describing the present disclosure, when it is determined that the description may make the subject matter of the present disclosure unnecessarily unclear, the detailed description of known functions or configurations incorporated herein will be omitted. The terms described below are terms defined in consideration of the functions in the present disclosure and may vary according to the user, the user's intention, or habit. Therefore, the definitions of the terms should be determined based on the content throughout the specification.

[0053] Generally speaking, wireless sensor network technology is mainly divided into wireless local area network (WLAN) technology and wireless personal area network (WPAN) technology according to the recognition distance. WPAN technology is based on IEEE 802.11 and can access the backbone network within a radius of about 100 m. WPAN technology is based on IEEE 802.15 and includes Bluetooth, ZigBee, ultra-wideband (UWB), etc. The wireless network implementing this wireless network technology can be configured by multiple electronic devices.

[0054] According to the definition of the Federal Communications Commission (FCC), UWB can refer to a wireless communication technology that uses a bandwidth of more than 500 MHz or a bandwidth corresponding to 20% or more of the center frequency. UWB can also refer to the frequency band itself to which UWB communication is applied. UWB can achieve secure and accurate ranging between devices. Therefore, UWB can perform relative position estimation based on the distance between two devices, or perform accurate position estimation of a device based on the distance of the device from a fixed device (whose position is known).

[0055] The following specific terms used in the description are provided to help understand the present disclosure, and the uses of these specific terms can be changed to other forms without departing from the technical idea of the present disclosure.

[0056] "Application-specific file (ADF)" can be, for example, a data structure in an application data structure that can host an application or application-specific data.

[0057] "Application protocol data unit (APDU)" can refer to the commands and responses used in the case of communicating with the application data structure in a UWB device.

[0058] "Application-specific data" can refer to, for example, a file structure having a root level and an application level, including UWB controller information and UWB session data required for a UWB session.

[0059] "Controller" can refer to a ranging device that defines and controls a ranging control message (RCM) (or control message).

[0060] "Controlled device" can refer to a ranging device that uses the ranging parameters in the RCM (or control message) received from the controller.

[0061] Different from "static STS", "dynamic scrambled timestamp sequence (STS) mode" can refer to an operating mode in which STS never repeats during a ranging session. In this mode, STS can be managed by a ranging device, and the ranging session key used to generate STS can be managed by a security component.

[0062] "Applet" may refer to, for example, an applet including UWB parameters and service data executed on a security component. In the present disclosure, the applet may be a FiRa applet defined by FiRa.

[0063] "Ranging device" may refer to a device capable of performing UWB ranging. In the present disclosure, the ranging device may refer to 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.

[0064] "UWB-enabled application" may refer to an application for UWB services. For example, a UWB-enabled application may be an application that configures an OOB connector, security service, and / or UWB service for a UWB session using a framework API. In the present disclosure, "UWB-enabled application" may be abbreviated as application or UWB application. The UWB-enabled application may be a FiRa-enabled application defined by FiRa.

[0065] "Framework" may refer to a component that provides access to configuration files, individual UWB configurations, and / or notifications. The "framework" may be a collection of logical software components, such as including a configuration file manager, an OOB connector, a security service, and / or a UWB service. In the present disclosure, the framework may be a FiRa framework defined by FiRa.

[0066] "OOB connector" may refer to a software component for configuring an out-of-band (OOB) connection (e.g., a BLE connection) between ranging devices. In the present disclosure, the OOB connector may refer to a FiRa OOB connector defined by FiRa.

[0067] "Configuration file" may refer to a previously defined set of UWB and OOB configuration parameters. In the present disclosure, the configuration file may refer to a FiRa configuration file defined by FiRa.

[0068] "Configuration file manager" may refer to a software component that implements the configuration files available to the ranging device. In the present disclosure, the configuration file manager may refer to a FiRa configuration file manager defined by FiRa.

[0069] "Service" may refer to the implementation manner of a use case that provides services to end users.

[0070] "Intelligent ranging device" may refer to a ranging device that can implement an optional framework API. In the present disclosure, the intelligent ranging device may refer to a FiRa intelligent device defined by FiRa.

[0071] "Global Dedicated Profile (GDF)" may refer to the root level of application-specific data that contains the data required to establish a USB session.

[0072] "Framework API" may refer to the API used by a UWB-enabled application to communicate with the framework.

[0073] "Initiator" may refer to a ranging device that initiates a ranging exchange.

[0074] "Object Identifier (OID)" may refer to the identifier of an ADF within an application data structure.

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

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

[0077] "Responder" may refer to a ranging device that responds to the initiator during a ranging exchange.

[0078] "STS" may refer to an encryption sequence used to increase the integrity and accuracy of ranging measurement timestamps. The STS can be generated from a ranging session key.

[0079] "Secure Channel" may refer to a data channel that prevents eavesdropping and tampering.

[0080] For example, a "secure component" may refer to an entity (e.g., SE or TEE) that has a defined security level to interface with UWBS and provide RDS to UWBS in the case of using dynamic STS.

[0081] "Secure Element (SE)" may refer to a tamper-resistant secure hardware component that can be used as a secure component in a ranging device.

[0082] "Secure Ranging" may refer to ranging based on STS generated through strong encryption operations.

[0083] "Secure Service" may refer to a software component used to interface with a secure component, such as a secure element or a Trusted Execution Environment (TEE).

[0084] "Service Applet" may refer to an applet on a secure component that processes service-specific transactions.

[0085] "Service Data" may refer to the data defined by a service provider that needs to be transmitted between two ranging devices to enable a service.

[0086] A "service provider" may refer to an entity that defines and provides the hardware and software required to provide a specific service to an end user.

[0087] The static STS mode refers to an operation mode in which STS is repeated during a session and does not need to be managed by a security component.

[0088] A "Secure UWB Service (SUS) applet" may refer to an applet on the SE that communicates with the applet to search for data required for a secure UWB session with another ranging device. In addition, the SUS applet can transmit corresponding data (information) to the UWBS.

[0089] "UWB service" may refer to a software component that provides access to the UWBS.

[0090] "UWB session" may refer to the time period between the time point when the controller and the controlled device start communicating via UWB and the time point when the communication stops. The UWB session may include ranging, data transmission, or both ranging / data transmission.

[0091] "UWB session ID" may refer to an ID (e.g., a 32-bit integer) shared between the controller and the controlled device to identify the UWB session.

[0092] "UWB session key" may refer to a key used to protect the UWB session. The UWB session key can be used to generate STS. In this disclosure, the UWB session key may refer to the UWB ranging session key (URSK) and may be abbreviated as the session key.

[0093] "UWB subsystem (UWBS)" may refer to a hardware component that implements the UWB PHY and MAC layers (specifications). The UWBS may have an interface for frames and an interface for security components to search for RDS. In this disclosure, for example, the UWB PHY and MAC specifications may be, for example, the FiRa PHY and FiRa MAC specifications defined by FiRa with reference to IEEE 802.15.4 / 4z.

[0094] "One-way ranging (OWR)" may refer to a ranging scheme that uses the time difference of arrival (TDoA) positioning method. The TDoA method corresponds to a method of positioning a mobile device based on the relative arrival time of a single message or multiple messages. The description in IEEE802.15.4z can be referred to as the description of OWR (TDoA). Examples of the OWR scheme may include the downlink (DL)-TDoA scheme.

[0095] "DL-TDoA (DT)" may refer to a positioning method that uses TDoA measurement values from multiple DT anchors. In one embodiment, the DT anchors may exchange DT messages (DTMs) (ranging messages) with each other, and the DT tags may passively receive the DTMs. In one embodiment, the corresponding DT tags that receive the DTMs may calculate the TDoA using at least one of the reception timestamps of each DTM, the transmission timestamps of the DTMs included in the DTM, or the response times included in the DTM. In one embodiment, the DT tags may estimate their positions by using at least one of the calculated TDoA or the coordinates of the DT anchors.

[0096] "Two-Way Ranging (TWR)" may refer to a ranging scheme that can estimate the relative distance between two devices by measuring the time of flight (ToF) of the exchange of ranging messages between the two devices. The TWR scheme may be one of the Double-Sided Two-Way Ranging (DS-TWR) or the Single-Sided Two-Way Ranging (SS-TWR). The SS-TWR may refer to the process of performing ranging by measuring one round-trip time. The DS-TWR may refer to the process of performing ranging by measuring two round-trip times. The description in IEEE 802.15.4z may be referred to as the description of the SS-TWR and the DS-TWR.

[0097] "UWB message" may refer to a message that includes a payload IE transmitted by a UWB device (e.g., ERDEV).

[0098] "Ranging message" may refer to a message transmitted by a UWB device (e.g., ERDEV) during the UWB ranging process. For example, the ranging message may be a message transmitted by a UWB device (e.g., ERDEV) at a specific stage of the ranging cycle, such as a ranging initiation message (RIM), a ranging response message (RRM), a ranging final message (RFM), or a measurement report message (MRM). The ranging message may include one or more UWB messages. If necessary, multiple ranging messages may be combined into one message. For example, in the case of non-delayed DS-TWR ranging, the RFM and the MRM may be combined into one message at the ranging final stage.

[0099] "UWB channel" may refer to one of the candidate UWB channels allocated for UWB communication. The candidate UWB channels allocated for UWB communication may be the 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 to transmit / receive ranging frames (RFRAMEs) and / or transmit / receive data frames.

[0100] A "narrowband (NB) channel" may refer to a channel with a narrower bandwidth than a UWB channel. The NB channel can be used to assist UWB communication. The NB channel can be a sub-channel of one of the candidate UWB channels allocated for UWB communication, or can be a channel with a specific bandwidth using other available frequency bands (such as certain industrial, scientific, and medical (ISM) bands, etc.). The candidate UWB channels allocated for UWB communication can be the channels allocated for UWB communication defined in IEEE 802.15.4 / 4z. The NB channel can be used for connection configuration of advertisement, device discovery, and / or additional parameter negotiation / authentication. For example, the NB channel can be used to transmit / receive advertisement messages, additional advertisement messages, connection request messages, and / or connection confirmation messages. In one embodiment, one or more NB channels can operate together.

[0101] In addition, in connection with describing the present disclosure, detailed descriptions of relevant known functions or configurations will be omitted if they are considered to unnecessarily obscure the gist of the present disclosure.

[0102] Hereinafter, various embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0103] Figure 1 An exemplary architecture of an electronic device according to an embodiment of the present disclosure is shown.

[0104] In the present disclosure, the electronic device can be one of various types of electronic devices. For example, the electronic device can be a portable device (such as a UE, smartphone, wearable device, vehicle, or tag device) or a fixed device (such as a door lock, anchor device, etc.).

[0105] Referring to Figure 1 , the electronic device 100 can include a PHY layer 110, a MAC layer (MAC sub-layer) 120, and / or a higher layer 130.

[0106] (1) PHY layer

[0107] The PHY layer 110 can include a low-level control entity and at least one transceiver. In the present disclosure, the transceiver can be referred to as an RF transceiver or a radio transceiver.

[0108] In one embodiment, at least one transceiver may include: a first transceiver configured to support UWB communication (e.g., 802.15.4z-based UWB communication); a second transceiver configured to support NB communication using a bandwidth narrower than that of UWB communication; and / or a third transceiver configured to support other communication technologies (e.g., Bluetooth, BLE, etc.). In the present disclosure, the first transceiver may be referred to as a UWB transceiver, the second transceiver may be referred to as an NB transceiver, and the third transceiver may be referred to as an OOB transceiver. Meanwhile, according to one embodiment, one transceiver may support multiple communication technologies. For example, one transceiver may support UWB communication and NB communication.

[0109] In one embodiment, the PHY layer 110 may support at least one of the following functions: - Transceiver activation and deactivation function (transceiver on / off function) - Energy detection function - Channel selection function - Clear Channel Assessment (CCA) function without interference - Synchronization function - Low-level signaling function - UWB ranging, positioning, and localization function - Spectrum resource management function - Function of transmitting / receiving data packets through the physical medium (2) MAC layer The MAC layer 120 provides an interface between the upper layer 130 and the PHY layer 120.

[0110] In one embodiment, the MAC layer 120 may provide the following two services: - MAC data service: A service for enabling the transmission / reception of MAC protocol data units (PDUs) through the PHY - MAC management service: A service for interfacing with the MAC sublayer management entity (MLME) service access point (SAP) (MLME-SAP) In one embodiment, the MAC layer 120 may support at least one of the following functions: - Device discovery and connection configuration function - Channel access function (physical channel (e.g., NB channel / UWB channel / OOB channel access function)) - Synchronization function - Interference mitigation function based on energy detection - NB signaling-related function - Guaranteed Time Slot (GTS) management function - Frame delivery function - UWB ranging function -PHY Parameter Change Notification Function -Security Feature (3) High Layer The high layer 130 may include a network layer configured to provide functions such as network configuration and message routing, and / or an application layer configured to provide the expected functions of the device. In one embodiment, the application layer may be a UWB-enabled application layer for providing UWB services.

[0111] Figure 2 A communication system including a plurality of electronic devices according to an embodiment of the present disclosure is shown.

[0112] Reference Figure 2 , the communication system 200 includes a first electronic device 210 and a second electronic device 220. In one embodiment, the first electronic device 210 and / or the second electronic device 220 may be Figure 1 the electronic device 100 in

[0113] The first electronic device 210 may communicate with the second electronic device 220 for device discovery, connection configuration, ranging (e.g., UWB ranging), data communication, and / or other purposes.

[0114] The first electronic device 210 may communicate with the second electronic device 220 using a pre-configured communication scheme (technique). For example, the first electronic device 210 may wirelessly communicate with the second electronic device 220 by using a UWB communication scheme, an NB communication scheme, and / or an OOB communication scheme.

[0115] In the present disclosure, the UWB communication scheme may communicate by using at least one candidate UWB channel allocated for WB communication. Examples of candidate UWB channels allocated for UWB communication may be as shown in Table 1 below: [Table 1]

[0116] In one embodiment, at least one channel in Table 1 may be allocated to the UWB channels supported by the UWB transceivers 130b and 230b. For example, channel numbers 5 and / or 9 in Table 1 may be allocated to the UWB channel.

[0117] NB communication may support at least one NB channel with a narrower bandwidth than the UWB channel.

[0118] In one embodiment, the NB channel may be a sub-channel of one of the candidate UWB channels allocated for UWB communication. Examples of candidate UWB channels allocated for UWB communication may be as shown in Table 1 above.

[0119] In another embodiment, the NB channel can be a channel with a specific bandwidth using other available frequency bands (e.g., certain Industrial, Scientific and Medical (ISM) frequency bands, etc.).

[0120] Meanwhile, as shown in Table 1 above, the candidate UWB channels have a bandwidth mainly of 500 MHz or higher. Therefore, using this method without modification is not conducive to the power spectral density (energy detection), and thus it may be necessary to divide the channel into multiple sub-channels (NB channels) and use them. For example, the NB channel may be required for device discovery (or advertisement) and / or connection configuration.

[0121] Figure 3 A method for multiple electronic devices to perform communication according to an embodiment of the present disclosure is shown.

[0122] Figure 3 The first electronic device 301 and the second electronic device 302 in Figure 1 or Figure 2 can be electronic devices in.

[0123] Referring to Figure 3 , the first electronic device 301 and the second electronic device 302 can perform a device search / connection configuration process 310 and a data communication process 320. The device search / session configuration process 310 and the data communication process 320 can be managed or controlled by the MAC layer (entity) of the electronic device.

[0124] (1) Device search / connection configuration process

[0125] In the present disclosure, the device search / connection configuration process 310 can be a preliminary process performed before the data communication process 320. In one embodiment, the device search / connection configuration process 310 can be performed through OOB communication (channel), NB communication (channel), and / or UWB communication (channel).

[0126] The device search / connection configuration process 310 can include at least one of the following operations: - Device search operation: An operation in which an electronic device searches (discovers) another UWB device. The device search operation can include the transmission / reception of an advertisement message. In the present disclosure, the device search operation can be referred to as a discovery operation or an advertisement operation.

[0127] - Connection configuration operation: The operation of configuring the connection between two electronic devices. The connection configuration operation may include the operation of transmitting / receiving a connection request message and a connection confirmation message. The connection (channel) configured through the connection configuration operation can be used to configure and control the UWB session for data communication. For example, through the secure channel configured via the connection configuration operation, parameters for configuring the UWB session (e.g., UWB performance parameters (controller performance parameters), UWB configuration parameters, and session key-related parameters) can be negotiated between two electronic devices.

[0128] (2) Data communication process

[0129] In the present disclosure, the data communication process 320 may be a process of transmitting and receiving data by using UWB communication. In one embodiment, the data communication process may be performed by UWB communication or NB communication.

[0130] The data communication process 320 may include at least one of the following operations: - UWB ranging operation: Wherein an electronic device performs UWB ranging with another electronic device in a pre-configured UWB ranging scheme (e.g., OWR, SS-TWR, or DS-TWR scheme). In one embodiment, the UWB ranging operation may include a ToF measurement operation and / or an AoA measurement operation.

[0131] - Transaction operation: Wherein an electronic device exchanges service data with another electronic device.

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

[0133] In Figure 4 the embodiment of, for example, the UWB MAC frame may follow the structure of the MAC frame according to IEEE 802.15.4z. In the present disclosure, the UWB MAC frame may be abbreviated as the MAC frame or the frame. In one embodiment, the UWB MAC frame may be used to transmit UWB data (e.g., UWB messages, ranging messages, control messages, service data, application data, transaction data, etc.).

[0134] Referring to Figure 4 , the UWB MAC frame may include a MAC header (MHR), a MAC payload, and / or a MAC footer (MFR).

[0135] (1) MAC header

[0136] The MAC header may include a frame control field, a sequence number field, a destination address field, a source address field, an auxiliary security header field, and / or at least one header IE field. According to one embodiment, some fields may not be included in the MAC header.

[0137] In one embodiment, the frame control field may include a frame type field, a security enabled field, a frame pending field, an AR field, a PAN ID compression field, a sequence number suppression field, an IE presence field, a destination addressing mode field, a frame version field, and / or a source addressing mode field. Descriptions of the respective fields are as follows: The frame type field may indicate the frame type. In one embodiment, the frame type may include a data type and / or a multi - destination type.

[0138] The security enabled field may indicate whether there is an auxiliary security header field. The auxiliary security header field may include information required for security processing.

[0139] The frame pending field may indicate whether the device transmitting the frame has more data for the receiver. That is, the frame pending field may indicate whether there is a pending frame for the receiver.

[0140] The AR field may indicate whether the receiver is required to acknowledge frame reception.

[0141] The PDN ID compression field may indicate whether there is a PAN ID field.

[0142] The sequence number suppression field may indicate whether there is a sequence number field. The sequence number field may indicate the sequence identifier of the frame.

[0143] The IE presence field may indicate whether the frame includes a header IE field and a payload IE field.

[0144] The destination addressing mode field may indicate whether the destination address field includes a short address (e.g., 16 - bit) or an extended address (e.g., 64 - bit). The destination address field may indicate the address of the frame receiver.

[0145] The frame version field may indicate the version of the frame. For example, the frame version field may be configured to have a value indicating IEEE std 802.15.4z - 2020.

[0146] The source addressing mode field may indicate whether there is a source address field, and if there is a source address field, may indicate whether the source address field includes a short address (e.g., 16 - bit) or an extended address (e.g., 64 - bit). The source address field may indicate the address of the frame originator.

[0147] (2)MAC Payload

[0148] The MAC payload may include at least one payload IE field. In one embodiment, the payload IE field may include a vendor-specific nested IE. In one embodiment, the payload IE field may include the payload IE field of a UWB message or a control message.

[0149] (3) MAC footer

[0150] The MAC footer may include an FCS field. The FCS field may include a 16-bit CRC or a 32-bit CRC.

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

[0152] Figure 5 A shows an exemplary structure of a UWB PHY packet to which an STS packet configuration is not applied, and Figure 5 B shows an exemplary structure of a UWB PHY packet to which an STS packet configuration is applied. In the present disclosure, a UWB PHY packet may be referred to as a PHY packet, a PHY PDU (PPDU), or a frame.

[0153] Reference Figure 5 A, the PPDU may include a synchronization header (SHR), a PHY header (PHR), and a PHY payload (PSDU). The PSDU may include a MAC frame, and as Figure 4 shown, the MAC frame may include a MAC header (MHR), a MAC payload, and / or a MAC footer (MFR). In the present disclosure, the synchronization header part may be referred to as a preamble, and the part including the PHY header and the PHY payload may be referred to as a data part.

[0154] The synchronization header is used for the synchronization of signal reception and may include a SYNC field and a frame start delimiter (SFD).

[0155] The SYNC field may include a plurality of preamble symbols for synchronization between the transmitting / receiving devices. The preamble symbols may be configured by one of the predefined preambles.

[0156] The SFD field may indicate the end of the SHR and the start of the data field.

[0157] The PHY header may provide information about the configuration of the PHY payload. For example, the PHY header may include information about the length of the PSDU, information indicating whether the current frame is an RFRAME, etc.

[0158] Meanwhile, the PHY layer of the UWB device may include an optional mode to provide reduced broadcast time for high density / low power operation. In this case, the UWB PHY data packet may include an encryption sequence (i.e., STS) to increase the integrity and accuracy of the ranging measurement timestamp. The STS may be included in the STS field of the UWB PHY data packet and may be used for secure ranging.

[0159] Reference Figure 5 B, in the case where the STS packet (SP) is configured to 0 (SP0), the STS field is not included in the PPDU (SP0 packet). In the case where the SP is configured to 1 (SP1), the STS field is located immediately after the frame start delimiter (SFD) field and before the PHR field (SP1 packet). In the case where the SP is configured to 2 (SP2), the STS field is located after the PHY payload (SP2 packet). In the case where the SP is configured to 3 (SP3), the STS field is located immediately after the SFD field, and the PPDU does not include the PHR and data fields (PHY payload) (SP3 packet). In other words, in the case of SP3, the PPDU does not include the PHR and the PHY payload.

[0160] In Figure 5 an embodiment of B, each UWB PHY data packet may include an RMARKER for defining a reference time, and the RMARKER may be used to obtain the transmission time, reception time, and / or time interval of the ranging message (frame) during the UWB ranging process.

[0161] Figure 6 An example of the structure of a ranging block and a cycle for UWB ranging according to an embodiment of the present disclosure is shown.

[0162] In the present disclosure, a ranging block refers to a time period for ranging. A ranging cycle may be a time period of a duration sufficient to complete a full distance measurement cycle (ranging cycle), which involves a group of UWB devices participating in a ranging exchange. A ranging slot may be a duration long enough to transmit at least one ranging frame (RFRAME) (e.g., ranging start / response / final message, etc.).

[0163] As Figure 6 shown, one ranging block may include at least one ranging cycle, and each ranging cycle may include at least one ranging slot.

[0164] Meanwhile, in the case where the ranging mode is a block-based mode, the average time between consecutive ranging cycles can be constant. Alternatively, in the case where the ranging mode is an interval-based mode, the time between consecutive ranging cycles can be changed dynamically. That is to say, the interval-based mode can adopt a time structure with an adaptive interval.

[0165] The number and duration of time slots included in a ranging cycle can be changed between ranging cycles.

[0166] In the present disclosure, ranging blocks, ranging cycles, and ranging time slots can be abbreviated as blocks, cycles, and time slots.

[0167] Figure 7 An example of the structure of a ranging cycle for UWB ranging according to an embodiment of the present disclosure is shown.

[0168] As Figure 7 shown, one ranging cycle can include multiple ranging time slots. Within a ranging cycle, a ranging control phase (RCP), a ranging phase (RP), and a measurement reporting phase (MRP) can be executed.

[0169] The ranging control phase (RCP) can be the phase in which a controller transmits a ranging control message (RCM) within a ranging cycle. The ranging control message (RCM) can be transmitted by the controller in the first time slot of the ranging cycle (e.g., time slot 0) to configure ranging parameters.

[0170] The ranging phase (RP) can be the phase in which messages for UWB ranging are transmitted / received within a ranging cycle. The ranging phase (RP) can include at least one of a ranging initiation phase (RIP), a ranging response phase (RRP), and a ranging final phase (RFP).

[0171] As used herein, the ranging initiation phase (RIP) can be the phase in which at least one initiator transmits at least one ranging initiation message, the ranging response phase (RRP) can be the phase in which at least one responder transmits at least one response message to the initiator, and the ranging final phase (RFP) can be the phase in which the initiator transmits at least one ranging final message to at least one responder.

[0172] The measurement reporting phase (MRP) can be the phase in which ranging measurements and related service information are exchanged within a ranging cycle.

[0173] According to one embodiment, the ranging control phase (RCP) can be executed in the first ranging time slot within a ranging cycle. According to one embodiment, the ranging control phase can be executed in at least one ranging time slot.

[0174] According to one embodiment, the ranging phase (RP) may be performed in ranging time slots from the second ranging time slot to the K-th ranging time slot (K is a natural number greater than or equal to 3) within a ranging cycle. According to one embodiment, the ranging phase may be performed in at least one ranging time slot.

[0175] According to one embodiment, the measurement report phase (MRP) may be performed in ranging time slots from the (K + 1)-th ranging time slot to the L-th ranging time slot (L is a natural number greater than or equal to 5) within a ranging cycle. According to one embodiment, the measurement report phase may be performed in at least one ranging time slot.

[0176] Meanwhile, a UWB device performing UWB ranging may occupy at least one ranging time slot and transmit a UWB data packet. According to one embodiment, the ranging time slot allocation information may be included in a ranging control message (RCM) transmitted in the ranging control phase (RCP).

[0177] To ensure packet processing time and avoid interference, the length of the ranging time slot may be implemented to be greater than the packet length. The transmission time point within the ranging time slot is basically the slot start time point, but the transmission time point within the ranging time slot may be adjusted by an offset.

[0178] According to one embodiment, the ranging control message (RCM) transmitted in the ranging control phase (RCP) may include a ranging cycle (RR) IE. According to one embodiment, the ranging control message (RCM) including the RR IE may be transmitted at the start portion of a ranging time slot within the first ranging cycle of ranging message exchange.

[0179] The RR IE may be used to signal ranging cycle information. According to one embodiment, the RR IE may include information about the current ranging cycle (e.g., the ranging cycle in the current ranging block i) and / or the next ranging cycle (e.g., the ranging cycle in the next ranging block i + 1).

[0180] According to one embodiment, the RR IE may be configured in the content field format as shown in Table 2. For example, the RR IE may include a ranging block index field, a frequency hopping pattern field, a cycle index field, and a transmission offset field.

[0181] [Table 2]

[0182] Wherein the ranging block index field may specify the index of the ranging block, and the frequency hopping pattern field may specify the frequency hopping pattern regarding the ranging block (e.g., 0 indicates no frequency hopping, and 1 indicates frequency hopping).

[0183] The loop index field may specify a ranging loop index for a ranging block, and the transmit offset field may specify a transmit offset value for the ranging loop in the ranging block. According to one embodiment, the transmit offset field may be a value obtained by subtracting the data packet duration from the ranging time slot duration.

[0184] According to one embodiment, a ranging control message (RCM) transmitted in a ranging control phase (RCP) may include a ranging device management (RDM) IE. The RDM IE may allocate ranging time slots and device roles (e.g., initiator or responder) in a ranging loop.

[0185] According to one embodiment, during periodic ranging, the controller may use the RDM IE to select devices participating in ranging, specify the role of the device as an initiator or a responder, and allocate time slots for the devices.

[0186] According to one embodiment, the RDM IE may be configured in the content field format as shown in Table 3. For example, the RDM IE may include an SIU field, an address size field, an RDM list length field, and an RDM list field.

[0187] [Table 3]

[0188] Wherein, the SIU field may indicate whether to use the time slot index field of the RDM list element (e.g., when the SIU field is 1, the time slot index field is used).

[0189] The address size field may specify the size of the addresses used in the RDM list field. For example, if the address size field is "0", all addresses of the RDM list element may be short addresses, and if the address size field is "1", all addresses may be extended addresses.

[0190] The RDM list length field may indicate the number of elements in the RDM list field.

[0191] According to one embodiment, the RDM list field may be configured in the element format in Table 4. For example, the RDM list field may include a ranging role field, a ranging time slot index field, and an address field.

[0192] [Table 4]

[0193] Wherein the ranging role field may specify whether the selected device is an initiator or a responder. If the time slot index field of the RDM list element is used (e.g., when the SIU field is "1"), the ranging time slot index field may be used to allocate a time slot index for the device.

[0194] The address field can be used to identify each participating device. According to one embodiment, the size of the address field can be specified by the address size field in the RDM IE.

[0195] Figure 8 A ranging message exchange process according to a ranging scheme according to an embodiment of the present disclosure is shown.

[0196] Figure 8 The embodiments in show the operation of exchanging ranging messages in one ranging cycle (ranging cycle) according to the ranging scheme (type). The ranging scheme (type) used can be indicated by the RCM. In one embodiment, the RCM can be transmitted in the first time slot of the corresponding ranging cycle.

[0197] <owr>

[0198] Reference Figure 8 A. The ranging process using the OWR scheme (OWR process) may include at least one phase for exchanging ranging messages. In one embodiment, the OWR process may include a ranging control phase (RCP), a ranging initiation phase (RIP), a ranging response phase (RRP), a ranging final phase (RFP), a measurement report phase (MRP), and / or a ranging control update phase (RCUP). Descriptions of the corresponding phases are as follows: Ranging control phase (RCP): The phase in which the controller device transmits a ranging control message (RCM). The RCM of the OWR process may also be referred to as a polling message.

[0199] Ranging response phase (RRP): The phase in which the responder device transmits a ranging response message (RRM) to the initiator device.

[0200] Measurement report phase (MRP): The phase in which the devices participating in the ranging exchange ranging measurement values and related service information through a measurement report (MR).

[0201] Ranging control update phase (RCUP): The phase in which the controller device transmits a ranging control update message (RCUM). If present, the RCUP may be the last time slot of a set of ranging cycles specified by the RCM.

[0202] <ss-twr>

[0203] Reference Figure 8 B and Figure 8 C, the ranging process using the TWR scheme (TWR process) may include at least one phase for exchanging ranging messages.

[0204] Reference Figure 8 B, the TWR process may include a ranging control phase (RCP), a ranging initiation phase (RIP), a ranging response phase (RRP), a measurement reporting phase (MRP), and / or a ranging control update phase (RCUP).

[0205] The descriptions of the corresponding phases are as follows: Ranging control phase (RCP): The phase in which the controller device transmits a ranging control message (RCM).

[0206] Ranging initiation phase (RIP): The phase in which the initiator device transmits a ranging initiation message (RIM) to the responder device.

[0207] Ranging response phase (RRP): The phase in which the responder device transmits a ranging response message (RRM) to the initiator device.

[0208] Measurement reporting phase (MRP): The phase in which the devices participating in the ranging exchange ranging measurement values and related service information through a measurement report (MR).

[0209] Ranging control update step (RCUP): The phase in which the controller device transmits a ranging control update message (RCUM). If present, RCUP may be the last time slot in a set of ranging cycles specified by the RCM.

[0210] The phases including RIP and RRP may be referred to as the ranging phase (RP).

[0211] Meanwhile, as shown in the embodiment of Figure 8 C, in the SS-TWR process, RCP and RIP may be combined into one phase. For example, in the case where an electronic device performs both the role of the initiator device and the role of the controller device, RCP and RIP may be combined into one phase. In this case, in the combined phase, a single ranging message containing all the information included in the RCM and the RIM may be transmitted.

[0212] <ds-twr>

[0213] Reference Figure 8 D. The ranging process (TWR process) using the TWR scheme may include at least one phase for exchanging ranging messages.

[0214] Reference Figure 8 D. The TWR process may include a ranging control phase (RCP), a ranging initiation phase (RIP), a ranging response phase (RRP), a ranging final phase (RFP), a measurement report phase (MRP), and / or a ranging control update phase (RCUP).

[0215] Descriptions of the corresponding phases are as follows.

[0216] Ranging control phase (RCP): The phase in which the controller device transmits a ranging control message (RCM).

[0217] Ranging initiation phase (RIP): The phase in which the initiator device transmits a ranging initiation message (RIM) to the responder device.

[0218] Ranging response phase (RRP): The phase in which the responder device transmits a ranging response message (RRM) to the initiator device.

[0219] Ranging final phase (RFP): The phase in which the initiator device transmits a ranging final message (RFM) to the responder device.

[0220] Measurement report phase (MRP): The phase in which the devices participating in ranging exchange ranging measurement values and related service information through a measurement report (MR).

[0221] Ranging control update phase (RCUP): The phase in which the controller device transmits a ranging control update message (RCUM). If present, the RCUP may be the last time slot of a set of ranging cycles specified by the RCM.

[0222] The phases including RIP, RRP, and RFP may be referred to as the ranging phase (RP).

[0223] Meanwhile, although not shown, in the DS-TWR process, the RCP and RIP may be combined into one phase. For example, in the case where an electronic device performs both the role of the initiator device and the role of the controller device, the RCP and RIP may be combined into one phase. In this case, in the combined phase, a single ranging message containing all the information included in the RCM and RIM may be transmitted.

[0224] <Multi-to-multi SS-TWR / Multi-to-multi DS-TWR>

[0225] Reference Figure 8 E and Figure 8 F, SS-TWR, and DS-TWR can be performed between multiple initiators and multiple responders. In this case, different from Figure 8 B to Figure 8 D, the RIP can include ranging time slots, the number of which corresponds to the multiple initiators, for RIM transmissions by the multiple initiators. In one embodiment, the scheduling of the ranging time slots used by the respective initiators to transmit their RIMs can be guided by the RCM in the RIP.

[0226] Figure 9 Shows the structure of a synchronization header (SHR) for UWB ranging according to an embodiment of the present disclosure.

[0227] Figure 9 The shown synchronization header (SHR) can be the same as or substantially the same as Figure 5 the synchronization header (SHR) shown in A. Figure 9 The shown SYNC field and SFD can be the same as or substantially the same as Figure 5 the SYNC field and SFD shown in B.

[0228] Referring to Figure 9 , the transmission time of the synchronization header (SHR) can be configured as T pre , the transmission time of the SYNC field can be configured as T SYNC , and the transmission time of the SFD can be configured as T SFD .

[0229] The SYNC field can be configured with known codes known to UWB devices from each other and can be used to synchronize the receiving time points of UWB devices. According to one embodiment, the SYNC field can be configured based on a ternary code. According to one embodiment, when configuring the SYNC field, the respective channels can use different codes, and different code indexes can be assigned to the respective codes.

[0230] According to one embodiment, the SYNC field can be configured with a ternary code of length 31, as shown in Table 5. For example, different code indexes can be assigned to each code sequence, and the UWB channel numbers can be pre-configured for each code sequence.

[0231] [Table 5]

[0232] According to one embodiment, the SYNC field can be configured with a ternary code of length 127, as shown in Table 6.

[0233] [Table 6]

[0234] [Embodiment of Transmitting Multiple Data Packets in One Time Slot]

[0235] Meanwhile, the UWB device performing ranging can occupy the ranging time slot to transmit UWB data packets, and only one UWB device can transmit data packets in each ranging time slot. However, if only one UWB device transmits data packets in each ranging time slot, the UWB device receiving the data packets needs to ensure a longer RX time, and this may increase power consumption.

[0236] Compared with other wireless communication technologies, the transmission time of UWB is very short, so the TX power consumption is low, but the RX power consumption is high. Considering the characteristics of electronic devices using multiple wireless communication technologies, when operating UWB, the RX power consumption may become a burden, and thus a solution for reducing power consumption by minimizing / optimizing the RX time is needed. In addition, a solution is also needed in which when using multiple electronic devices, the limited time resources are efficiently used for latency-sensitive applications.

[0237] A method is proposed such that multiple UWB devices transmit multiple data packets in one ranging time slot in order to efficiently allocate power consumption and time resources by minimizing / optimizing the RX time of the UWB devices.

[0238] According to one embodiment, multiple UWB devices can transmit multiple data packets in one ranging time slot through a time division, code division, or STS parallel transmission scheme.

[0239] In the present disclosure, time division refers to a scheme in which multiple UWB devices transmit data packets at different time points (i.e., by using micro time slots) within one ranging time slot. In addition, code division refers to a scheme in which multiple UWB devices transmit data packets through different codes within one ranging time slot. In addition, STS parallel transmission refers to a scheme in which multiple UWB devices transmit data packets through different STSs (STSs configured by different codes) within one ranging time slot.

[0240] will be referred to later Figure 10A The time division according to the embodiment of the present disclosure will be described in detail. will be referred to later Figure 11A The code division will be described in detail, and will be referred to later Figure 12 The STS parallel transmission will be described in detail.

[0241] According to one embodiment, it can be pre-configured whether to apply time division or code division to each of the multiple UWB devices so that multiple UWB devices transmit multiple data packets in one ranging time slot.

[0242] According to one embodiment, transmit control information (e.g., ranging control message (RCM)) transmitted over narrowband or UWB may include an indicator for selecting time division or code division. For example, in the case of a 1-bit indicator, if the indicator is "1", time division may be configured; and if the indicator is "0", code division may be configured.

[0243] According to another embodiment, in the case of allocating multiple UWB devices to one ranging time slot, time division or code division may be configured according to the value of the transmit offset field included in the RR IE in Table 1. For example, in the case of allocating multiple UWB devices to one ranging time slot, and when the value of the transmit offset field included in the RR IE is "0", code division may be configured. For example, in the case of allocating multiple UWB devices to one ranging time slot, and when the value of the transmit offset field included in the RR IE is "1", time division may be configured.

[0244] Figure 10A is a schematic diagram for describing a method of transmitting data packets through a UWB device according to an embodiment of the present disclosure.

[0245] In Figure 10A , the first UWB device may act as the role of the initiator, the second UWB device may act as the role of the first responder, the third UWB device may act as the role of the second responder, the fourth UWB device may act as the role of the third responder, and the fifth UWB device may act as the role of the fourth responder.

[0246] Although in Figure 10A , the first UWB device is shown as acting as the role of the initiator of the transmit control information (i.e., the first UWB device acts as the role of the controller and the initiator), the first UWB device may act as the role of the controller of the transmit control information, and another UWB device may act as the role of the initiator of the transmit ranging start message.

[0247] Although for convenience of explanation, Figure 10A shows five UWB devices acting as the role of the initiator or the responder, the technical idea of the present disclosure is not limited thereto, and the number of UWB devices acting as the role of the initiator or the responder may be implemented in various ways.

[0248] Refer to Figure 10A , a ranging cycle may include a first time slot (time slot 0), a second time slot (time slot 1), and a third time slot (time slot 2). A first UWB device (initiator) may transmit transmit control information (e.g., a UWB ranging control message (RCM)) via UWB or narrowband at the start time point of the first time slot (time slot 0). The transmission offset of the transmit control information (e.g., a UWB ranging control message (RCM)) may be configured as "offset timing #0".

[0249] In response to the transmit control information (e.g., a UWB ranging control message (RCM)), a second UWB device (responder 1) may transmit a first data packet (data packet 1) at the start time point of the second time slot (time slot 1). The transmission offset of the first data packet may be configured as "offset timing #2" in the second time slot (time slot 1).

[0250] The first data packet may be a data packet containing a segment (UWB segment / MMS segment) for MMS UWB (or NBA-MMS UWB), a data packet containing a synchronization header (SHR), a data packet containing a SYNC field (i.e., a preamble) in the synchronization header, a data packet containing STS, an SP3 type data packet (SP configuration 3) containing a synchronization header and STS, or a data packet containing a preamble and STS. In one embodiment, the first data packet may be used for UWB ranging. The MMS segment may include a ranging sequence segment (RSF) or a ranging integrity segment (RIF), but is not limited thereto.

[0251] In response to the transmit control information (e.g., a UWB ranging control message (RCM)), a third UWB device (responder 2) may transmit a second data packet (data packet 2) at the mid-time point of the second time slot (time slot 1). The transmission offset of the second data packet may be configured as "offset timing #3" in the second time slot (time slot 1).

[0252] The second data packet may be a data packet containing a segment (MMS segment) for MMS UWB (or NBA-MMS UWB), a data packet containing a synchronization header (SHR), a data packet containing STS, a data packet containing a SYNC field (i.e., a preamble) in the synchronization header, an SP3 type data packet (SP configuration 3) containing a synchronization header and STS, or a data packet containing a preamble and STS. In one embodiment, the second data packet may be used for UWB ranging.

[0253] In one embodiment, multiple data packets transmitted in the same time slot (or the same cycle) may have the same format. For example, in the case where the first data packet has a data packet format including MMS fragments, the second data packet may also have a data packet format including MMS fragments. In one embodiment, in the case where the first data packet and the second data packet have a data packet format including STS, the STS included in the first data packet may be different from the STS included in the second data packet.

[0254] The second UWB device (Responder 1) and the third UWB device (Responder 2) may transmit the first data packet and the second data packet respectively with different transmission offsets in the second time slot (Time Slot 1). According to one embodiment, the transmission offset may be configured as the transmission offset field in the RR IE in Table 1.

[0255] In response to transmission control information (e.g., UWB ranging control message (RCM)), the fourth UWB device (Responder 3) may transmit a third data packet (Data Packet 3) at the start time point of the third time slot (Time Slot 2). The transmission offset of the third data packet may be configured as "Offset Timing #4" in the third time slot (Time Slot 2).

[0256] The third data packet may be a data packet including fragments (MMS fragments) for MMS UWB (or NBA-MMS UWB), a data packet including a synchronization header (SHR), a data packet including STS, a data packet including a SYNC field (i.e., preamble) in the synchronization header, an SP3 type data packet (SP Configuration 3) including a synchronization header and STS, or a data packet including a preamble and STS. In an embodiment, the third data packet may be used for UWB ranging.

[0257] In response to transmission control information (e.g., UWB ranging control message (RCM)), the fifth UWB device (Responder 4) may transmit a fourth data packet (Data Packet 4) at the middle time point of the third time slot (Time Slot 2). The transmission offset of the fourth data packet may be configured as "Offset Timing #5" in the third time slot (Time Slot 2).

[0258] The fourth data packet may be a data packet including fragments (MMS fragments) for MMS UWB (or NBA-MMS UWB), a data packet including a synchronization header (SHR), a data packet including STS, a data packet including a SYNC field (i.e., preamble) in the synchronization header, an SP3 type data packet (SP Configuration 3) including a synchronization header and STS, or a data packet including a preamble and STS. In one embodiment, the fourth data packet may be used for UWB ranging.

[0259] In one embodiment, multiple data packets transmitted in the same time slot (or the same cycle) may have the same format. For example, in the case where the third data packet has a data packet format containing an MMS segment, the fourth data packet may also have a data packet format containing an MMS segment. In one embodiment, in the case where the third data packet and the fourth data packet have a data packet format containing an STS, the STS included in the third data packet may be different from the STS included in the fourth data packet.

[0260] The fourth UWB device (Responder 3) and the fifth UWB device (Responder 4) may transmit the third data packet and the fourth data packet respectively with different transmission offsets in the third time slot (Time Slot 2). According to one embodiment, the transmission offset may be configured as the transmission offset field in the RR IE in Table 1.

[0261] According to one embodiment, the length of the micro time slots in the ranging time slot may be configured differently according to the value of the transmission offset field in the RR IE in Table 1. According to one embodiment, if the value of the transmission offset field in the RR IE is configured with different numbers, the number of micro time slots included in the ranging time slot may also be implemented in different ways.

[0262] Figure 10B The RDM list field in the RDM IE according to an embodiment of the present disclosure is shown.

[0263] Figure 10B The shown RDM list field may include a ranging role field, a ranging time slot index field, and an address field in the same way as the RDM list field in Table 4. The corresponding fields in the RDM list field have been described with reference to Table 4 above, and their repeated descriptions will be omitted herein.

[0264] Reference Figure 10B , the RDM list field may assign multiple UWB devices and multiple device addresses to one ranging time slot index. According to one embodiment, the configured number of multiple UWB devices or multiple device addresses may be less than the number of micro time slots in the ranging time slot.

[0265] According to one embodiment, the UWB devices assigned to the same ranging time slot index in the RDM list field may be assigned to the corresponding micro time slots according to their order included in the RDM list.

[0266] Reference Figure 10A and Figure 10B , the same ranging time slot index (time slot 1) can be assigned to the second UWB device (responder 1) and the third UWB device (responder 2), the first address (the address of responder 1) can be assigned to the second UWB device (responder 1), and the second address (the address of responder 2) can be assigned to the third UWB device (responder 2).

[0267] The second UWB device (responder 1) and the third UWB device (responder 2) assigned to the same ranging time slot index (time slot 1) can transmit data packets according to the order in which the data packets are included in the RDM list. For example, the second UWB device (responder 1) can transmit the first data packet in the ranging time slot index (time slot 1), and the third UWB device (responder 2) can transmit the second data packet in the ranging time slot index (time slot 1).

[0268] Figure 11A is a schematic diagram for describing a method of transmitting data packets through UWB devices according to another embodiment of the present disclosure.

[0269] In Figure 11A , the first UWB device can act as the role of the initiator, the second UWB device can act as the role of the first responder, the third UWB device can act as the role of the second responder, the fourth UWB device can act as the role of the third responder, and the fifth UWB device can act as the role of the fourth responder.

[0270] Although in Figure 11A , the first UWB device is shown as acting as the role of the initiator for transmitting control information (i.e., the first UWB device acts as the role of the controller and the initiator), the first UWB device can act as the role of the controller for transmitting control information, and another UWB device can act as the role of the initiator for transmitting a ranging start message.

[0271] Although for the sake of convenience of explanation, Figure 11A shows five UWB devices acting as the role of the initiator or the responder, the technical idea of the present disclosure is not limited thereto, and the number of UWB devices acting as the role of the initiator or the responder can be implemented in various ways.

[0272] Referring to Figure 11A , one ranging cycle can include a first time slot (time slot 0), a second time slot (time slot 1), and a third time slot (time slot 2). The first UWB device (initiator) can transmit control information (e.g., a UWB ranging control message (RCM)) through UWB or narrowband transmission at the start time point of the first time slot (time slot 0).

[0273] The first UWB device (initiator) can allocate ranging time slots to the second UWB device (responder 1) to the fifth UWB device (responder 4) respectively, and can provide information about the sequence included in the data packet. According to one embodiment, multiple responders can perform transmissions in one ranging time slot, and the sequences can be orthogonally transmitted.

[0274] In response to the transmission control information (e.g., UWB ranging control message (RCM)), the second UWB device (responder 1) can transmit a first data packet (data packet 1) at a preconfigured time point (e.g., start time point) of the second time slot (time slot 1).

[0275] The first data packet can be a data packet containing a fragment (MMS fragment) of MMS UWB (or NBA-MMS UWB), a data packet containing a synchronization header (SHR), a data packet containing a SYNC field (i.e., preamble) in the synchronization header, or a data packet containing STS.

[0276] In response to the transmission control information (e.g., UWB ranging control message (RCM)), the third UWB device (responder 2) can transmit a second data packet (data packet 2) at a preconfigured time point (e.g., start time point) of the second time slot (time slot 1).

[0277] The second data packet can be a data packet containing a fragment (MMS fragment) of MMS UWB (or NBA-MMS UWB), a data packet containing a synchronization header (SHR), a data packet containing a SYNC field (i.e., preamble) in the synchronization header, or a data packet containing STS.

[0278] In one embodiment, multiple data packets transmitted in the same time slot (or the same cycle) can have the same format. For example, in the case where the first data packet has a data packet format containing MMS fragments, the second data packet can also have a data packet format containing MMS fragments.

[0279] In one embodiment, multiple data packets transmitted in the same time slot can contain different sequences. For example, in the case where the first data packet and the second data packet have a data packet format containing MMS fragments, the MMS fragments included in the first data packet and the MMS fragments included in the second data packet can be generated based on different codes (e.g., multi-millisecond ranging sequences (MMRS) with different indexes) respectively. For example, in the case where the first data packet and the second data packet have a data packet format containing a preamble (or SHR), the preambles included in the first data packet and the preambles included in the second data packet can be generated based on different codes (e.g., different ternary codes) respectively.

[0280] The second UWB device (Responder 1) and the third UWB device (Responder 2) may respectively transmit data packets containing different sequences (e.g., sequences orthogonal to each other) in the second time slot (Time Slot 1).

[0281] In response to the transmission control information (e.g., UWB ranging control message (RCM)), the fourth UWB device (Responder 3) may transmit a third data packet (Data Packet 3) at a preconfigured time point (e.g., start time point) in the third time slot (Time Slot 2).

[0282] The third data packet may be a data packet containing a fragment of MMS UWB (or NBA-MMS UWB) (MMS fragment), a data packet containing a synchronization header (SHR), a data packet containing a SYNC field (i.e., preamble) in the synchronization header, or a data packet containing STS.

[0283] In response to the transmission control information (e.g., UWB ranging control message (RCM)), the fifth UWB device (Responder 2) may transmit a fourth data packet (Data Packet 4) at a preconfigured time point (e.g., start time point) in the third time slot (Time Slot 2).

[0284] The fourth data packet may be a data packet containing a fragment of MMS UWB (or NBA-MMS UWB) (MMS fragment), a data packet containing a synchronization header (SHR), a data packet containing a SYNC field (i.e., preamble) in the synchronization header, or a data packet containing STS.

[0285] In one embodiment, the third data packet and the fourth data packet transmitted in the same time slot (or the same cycle) may have the same format. For example, in the case where the third data packet has a data packet format containing an MMS fragment, the fourth data packet may also have a data packet format containing an MMS fragment.

[0286] In one embodiment, two data packets transmitted in the same time slot may contain different sequences. For example, in the case where the third data packet and the fourth data packet have a data packet format containing an MMS fragment, the MMS fragments contained in the third data packet and the fourth data packet may be generated based on different codes (e.g., multi-millisecond ranging sequences (MMRS) with different indices). For example, in the case where the third data packet and the fourth data packet have a data packet format containing a preamble, the preambles contained in the third data packet and the second data packet may be generated based on different codes (e.g., different ternary codes).

[0287] The fourth UWB device (Responder 3) and the fifth UWB device (Responder 4) may transmit data packets containing different sequences (e.g., sequences orthogonal to each other) in the third time slot (Time Slot 2), respectively.

[0288] Meanwhile, two data packets transmitted in different time slots may contain the same sequence. For example, the second data packet and the third data packet transmitted in the same time slot may contain the same sequence.

[0289] Figure 11B The RDM list field in the RDM IE according to another embodiment of the present disclosure is shown.

[0290] Figure 11B The shown RDM list field may include a ranging role field, a ranging time slot index field, and an address field in the same manner as the RDM list field in Table 4. The corresponding fields in the RDM list field have been described with reference to Table 4 above, and their repeated descriptions will be omitted herein.

[0291] Reference Figure 11B , the RDM list field may assign multiple UWB devices and multiple device addresses to one ranging time slot index. According to one embodiment, the configured number of multiple UWB devices or multiple device addresses may be less than the total number of indexes (code indexes) of the codes used to generate the sequences included in the data packets.

[0292] According to one embodiment, the UWB devices assigned to the same ranging time slot index in the RDM list field may be assigned to pre-configured code indexes respectively according to their order included in the RDM list.

[0293] Reference Figure 11A and Figure 11B , the same ranging time slot index (Time Slot 1) may be assigned to the second UWB device (Responder 1) and the third UWB device (Responder 2), the first address (the address of Responder 1) may be assigned to the second UWB device (Responder 1), and the second address (the address of Responder 2) may be assigned to the third UWB device (Responder 2).

[0294] The second UWB device (Responder 1) and the third UWB device (Responder 2) assigned to the same ranging time slot index (Time Slot 1) may transmit data packets based on the code indexes determined in advance according to the order in which the data packets are included in the RDM list.

[0295] For example, in the case of a data packet format including MMS segments, a second UWB device (responder 1) first assigned to a ranging time slot index (time slot 1) may include in a first data packet data of a sequence generated based on a code (e.g., an MMRS sequence) having "code index 1", and a third UWB device (responder 2) second assigned to the ranging time slot index (time slot 1) may include in the first data packet data of a sequence generated based on a code (e.g., an MMRS sequence) having "code index 2".

[0296] For example, in the case of a data packet format including a preamble (or SHR), a second UWB device (responder 1) first assigned to a ranging time slot index (time slot 1) may include in a first data packet data of a sequence generated based on a code (e.g., a ternary code of length 31 in Table 4) having "code index 3", and a third UWB device (responder 2) second assigned to the ranging time slot index (time slot 1) may include in the first data packet data of a sequence generated based on a code (e.g., a ternary code of length 31 in Table 4) having "code index 4".

[0297] [Multi-Millisecond (MMS) UWB]

[0298] MMS UWB may be a mode in which multiple segments / data packets are transmitted by UWB at intervals of at least 1 millisecond (ms) in order to improve the link budget and ToF accuracy. For example, each segment (or a UWB data packet including each segment) may be multiply transmitted by UWB at a certain interval or 1 ms. Such multiple segments / data packets may be used for UWB ranging (e.g., SS-TWR). In the present disclosure, the segments / data packets for MMS UWB may be referred to as MMS segments / data packets.

[0299] In one embodiment, the MMS segment / data packet may include a ranging sequence fragment (RSF) or a ranging integrity fragment (RIF), but is not limited thereto. In one embodiment, the RSF may be generated based on a preconfigured multi-millisecond ranging sequence (MMRS). In one embodiment, the RIF may be generated based on STS.

[0300] NB may be used to assist MMS UWB, and this may be referred to as narrowband assisted (NBA)-MMS UWB. In the case of NBA-MMS UWB, the synchronization information and / or configuration information of MMS UWB may be transmitted via NB instead of via UWB. The synchronization information may include frequency synchronization information and an initial time (or timing) required for MMS UWB. NBA-MMS UWB and MMS UWB may be one of the multiple transmission modes.

[0301] In the following, a method for supporting multiple transmission modes / scenarios in a time slot in the case of applying MMS UWB (or NBA-MMS UWB) will be described. In one embodiment, both NBA-UWB devices and UWB-only devices can support multiple transmission modes / scenarios.

[0302] For ease of description, it will be assumed in the following description that the MMS fragment contains an RSF, but the present disclosure is not limited thereto. For example, the MMS fragment may contain an RIF or may contain other sequences (e.g., a preamble or an SHR). Figure 12 A multiple transmission mode process according to an embodiment of the present disclosure is shown.

[0303] Referring to Figure 12 , the multiple transmission mode process may include the following four steps: (1) Scheduling step The scheduling step may be a step for scheduling the transmission timing of each device. In one embodiment, the scheduling may be performed by a starter (or a controller). In one embodiment, the scheduling may be performed through a scheduling IE (e.g., the scheduling IE in Figure 13 ) or a control message of an NB or an OOB.

[0304] (2) Triggering step

[0305] The triggering step may be a step for triggering multiple transmissions. In one embodiment, the multiple transmissions may be triggered by a starter. For example, the multiple transmissions may be triggered by transmitting a UWB data packet (e.g., a packet containing a SYNC field and an SFD field) or an NB polling message transmitted by the starter. [[ID=!23]]

[0306] (3) Multiple transmission phase

[0307] The multiple transmission step may be a step for multiple transmissions of fragments (MMS fragments). In one embodiment, the fragment may include a ranging sequence fragment (RSF), but is not limited thereto. For example, the fragment may include an STS-based ranging integrity fragment (RIF), or may include other sequences (e.g., a preamble or an SHR). In one embodiment, in the multiple transmission step, multiple transmissions of fragments may be performed between scheduled responders, but are not limited thereto. For example, in the multiple transmission step, multiple transmissions of fragments may be performed based on competition.

[0308] (4) Ranging report step

[0309] The ranging report step may be a step for transmitting a ranging report. For example, the ranging report step may be a step for the starter to transmit a ranging report to the responder. In one embodiment, the ranging report may include a ranging measurement result.

[0310] If desired, the four steps of the above multi - transmission mode process can be performed in an order different from the above order, certain steps can be omitted, additional steps can be further included, or multiple steps can be combined into one step. For example, the scheduling step and the triggering step can be combined into one step. For example, the ranging report step can be omitted. For example, in cases where scheduling information does not need to be updated, the scheduling step can be omitted in the corresponding ranging cycle.

[0311] Figure 13 An example of a scheduling IE for multi - transmission according to an embodiment of the present disclosure is shown.

[0312] Reference Figure 13 , the scheduling IE can include a control field and at least one scheduling list element.

[0313] The control field can include an address size field, a scheduling list length field, and / or a scheduling list type field.

[0314] The address size field can indicate the size of the address field. In one embodiment, the size of the address field (or the size of the address contained in the address field) can be 2 bytes or 8 bytes.

[0315] The scheduling list length field can indicate the number (or length) of scheduling list elements. For example, in the case where the value of the scheduling list length field is configured to N the scheduling IE can contain as many scheduling list elements as N shown in the figure.

[0316] The scheduling list type field can indicate the scheduling list type. As used herein, the scheduling list type can refer to the type of scheduling list element (or the data contained in the scheduling list element). In one embodiment, the scheduling list type field can be configured to have one of the following values: a first value (e.g., 0), indicating that the scheduling list type is a bitmap - based type; a second value (e.g., 1), indicating that the scheduling list type is a periodic scheduling type; or a third value (e.g., 2), indicating that the scheduling list type is a multi - transmission scheduling type. According to the value of this scheduling list type field, the format of the data (or fields) contained in the scheduling list element can change.

[0317] The scheduling list element can contain scheduling information about the corresponding device (e.g., the responder to be scheduled).

[0318] In one embodiment, when the value of the scheduling list type field is configured to a third value (e.g., 2), indicating that the scheduling list type is a multiple transmission scheduling type (i.e., when the scheduling list element is used for scheduling regarding a multiple transmission mode (e.g., MMS UWB mode / NBA - MMS UWB mode)), the scheduling list element may include a start time slot index field, a scheduling step field, a scheduling repetition field, an address field, a sequence index field, a gap number field, and / or a repetition field. That is, in the case of a scheduling IE for a multiple transmission mode, each scheduling list element may include a start time slot index field, a scheduling step field, a scheduling repetition field, an address field, a sequence index field, a gap number field, and / or a repetition field.

[0319] The address field may provide the address (e.g., a 2 - byte address or an 8 - byte address) of the device (e.g., a responder) to which the scheduling information (configuration information) included in the corresponding scheduling list element is applied. In one embodiment, the address may be the MAC address of the device.

[0320] The start time slot index field may indicate the index of the first transmission time slot in a periodic transmission mode (or multiple transmission mode). Thus, the first ranging time slot for transmitting an MMS segment / packet can be identified.

[0321] The scheduling step field may indicate the period of the periodic transmission mode (or multiple transmission mode) in terms of time slots. In one embodiment, the scheduling step field may be configured to have a value of 4, 8, 16, 32, or 64. Thus, the period for transmitting multiple MMS segments / packets can be identified.

[0322] The scheduling repetition field may indicate the number of repetitions of the periodic transmission mode (or multiple transmission mode) in terms of time slots. In one embodiment, the scheduling repetition field may be configured to have a value of 2, 4, 8, 16, or 32. Thus, the number of times of transmitting MMS segments / packets within the corresponding period can be identified.

[0323] The sequence index field, the gap number field, and the repetition field may be used to allocate MMS segments to the corresponding device (e.g., a responder).

[0324] The sequence index field may indicate the index of a multi - millisecond ranging sequence (MMRS) based on 16 complementary sets of length 128. In other words, the sequence index field may indicate the index of 16 MMRS sequences of length 128 based on 16 complementary sets of length 128.

[0325] Table 7 shows an example of an MMRS sequence of length 128.

[0326] [Table 7]

[0327] In Table 7, each of the 16 MMRS sequences of length 128 can have a separate index. For example, as shown in Table 7, each MMRS sequence can have an index from 1 to 16, but is not limited thereto.

[0328] The gap number field can indicate the size of the zero gap (Part G). In one embodiment, the gap number field can be configured to have a value from 0 to 64.

[0329] As shown in Table 7, each MMRS sequence can be divided into Part A (left part) and Part B (right part) ([A, B]), and each of Part A and the part can have a length of 64 bits. In one embodiment, Part G ([A, G, B, G]) can be added between Part A and Part B and after Part B to generate an MMRS with a zero gap. In one embodiment, Part G can be configured by zeros (e.g., 0 to 64 zeros), the number of which corresponds to the value of the zero gap field.

[0330] The repeat field can indicate the number of repetitions of the MMRS. For example, when the value of the repeat field is 2, two MMRSs (e.g., MMRSs with / without zero gaps) can be included in one MMS segment (e.g., RSF).

[0331] A device (e.g., responder) that has received the scheduling IE can generate the sequence data included in the MMS segment by using the sequence index field, gap number field, and repeat field (included in the scheduling IE) in the scheduling list element of the device.

[0332] In one embodiment, the scheduling IE can be included in a UWB data packet, NB data packet, or OOB data packet and then transmitted. For example, the scheduling IE can be included in the MAC payload of a UWB data packet, NB data packet, or OOB data packet.

[0333] Figure 14 An example of a multi-transmission method using UWB according to an embodiment of the present disclosure is shown.

[0334] Although in Figure 14 the first UWB device is shown as playing the role of an initiator that transmits control information (i.e., the first UWB device plays the roles of a controller and an initiator), the first UWB device can play the role of a controller that transmits control information, and another UWB device can play the role of an initiator.

[0335] Although for ease of explanation, Figure 14 Three UWB devices are shown as acting as initiators or responders, but the technical idea of the present disclosure is not limited thereto, and the number of UWB devices acting as initiators or responders can be implemented in various ways.

[0336] In Figure 14 the multiple transmission method (UWB multiple transmission method / MMS UWB mode) in, the scheduling for multiple transmission can be performed by using control messages / data packets transmitted via UWB (e.g., Figure 13 control messages / data packets containing scheduling IEs in), or by an OOB process. In the present disclosure, control messages / data packets containing scheduling information transmitted via the UWB channel can be referred to as UWB control messages / data packets.

[0337] Referring to Figure 14 , in the scheduling step / operation 1411, the first UWB device (initiator) can transmit a UWB control data packet containing scheduling information (e.g., Figure 13 the scheduling IE in) via UWB. For example, the initiator can transmit a UWB control data packet containing the scheduling IE in the first time slot (e.g., time slot index #0 (time slot 0)) of the first ranging cycle (cycle 0) 1410. In one embodiment, the UWB control data packet can be transmitted at the starting time point of time slot 0.

[0338] In the triggering step / operation 1412, the initiator can transmit a data packet containing synchronization information (e.g., SYNC field and SFD field) via UWB to trigger multiple transmission. For example, the initiator can transmit a data packet configured by the SYNC field and SFD field in the second time slot of the first ranging cycle 1410 (e.g., in the time slot immediately following the time slot allocated for scheduling (e.g., the second time slot (time slot index #1 (time slot 1))). In one embodiment, the data packet containing the SYNC field and SFD field can be transmitted at the starting time point of time slot 1.

[0339] In the multiple transmission step / operation 1413, the second UWB device (responder 1) and the third UWB device (responder 2) can transmit multiple segments (MMS segments) based on the scheduling information contained in the UWB control data packet. In one embodiment, each MMS segment / data packet can be transmitted at the starting time point of the corresponding ranging time slot. Each MMS segment transmitted by a responder in the corresponding ranging cycle can contain the same sequence data.

[0340] In one embodiment, these segments can be RSFs.

[0341] In one embodiment, the responder may identify a scheduling list element for the responder in the scheduling IE, and may obtain sequence data (e.g., MMRS sequence data) to be included in the RSF by using the sequence index field, gap number field, and / or repetition field included in the scheduling list element. The MMRS sequence data may be sequence data generated based on an MMRS sequence (e.g., the MMRS sequence in Table 7).

[0342] In one embodiment, the responder may identify a scheduling list element for the responder in the scheduling IE, and may transmit multiple RSFs (or transmit the RSF repetitively) by using the starting time slot index field, scheduling step field, and / or scheduling repetition field included in the scheduling list element.

[0343] For example, as shown in the figure, Responder 1 may obtain the MMRS sequence data (first MMRS sequence data) included in its RSF (first RSF) by using the sequence index field, gap number field, and / or repetition field included in its scheduling list element (first scheduling list element). In addition, Responder 1 may repetitively transmit the first RSF three times during a time period of three time slots corresponding to the third time slot from the first ranging cycle 1410 by using the starting time slot index field, scheduling step field, and / or scheduling repetition field included in the first scheduling list element.

[0344] For example, as shown in the figure, Responder 2 may obtain the MMRS sequence data (second MMRS sequence data) included in its RSF (second RSF) by using the sequence index field, gap number field, and / or repetition field included in its scheduling list element (second scheduling list element). In addition, Responder 2 may repetitively transmit the first RSF three times during a time period of three time slots corresponding to the third time slot from the second ranging cycle 1410 by using the starting time slot index field, scheduling step field, and / or scheduling repetition field included in the second scheduling list element.

[0345] As shown in the figure, MMS segments (e.g., RSFs) of multiple devices (e.g., responders) can be transmitted in the same time slot (or at the same time point). For example, the RSFs of multiple responders can be transmitted simultaneously in the same time slot (e.g., simultaneously at the start time point of the time slot). In this case, the first MMRS sequence data included in the first RSF transmitted by responder 1 can be configured differently from the second MMRS sequence data included in the second RSF transmitted by responder 2. For example, the index of the MMRS sequence used to generate the first MMRS sequence data can be configured to have a value different from the index of the MMRS sequence used to generate the second MMRS sequence data. For example, the sequence index field in the scheduling list element for responder 1 in the scheduling IE can be configured to have a value different from the sequence index field in the scheduling list element for responder 2 in the scheduling IE. Therefore, even if multiple devices transmit RSFs together within the same time slot, each RSF has a different sequence (or code), and the device receiving the RSFs can thus accurately acquire the RSF of each device (code division scheme).

[0346] In the ranging report step / operation 1414, the initiator can transmit a ranging report to the responder via UWB. For example, as shown in the figure, the initiator can transmit a ranging report for responder 1 (ranging report 1) to responder 1, and the initiator can transmit a ranging report for responder 2 (ranging report 2) to responder 2.

[0347] The above scheduling step 1411, triggering step 1412, multiple transmission step 1413, and ranging report step 1414 can be executed within one ranging cycle 1410.

[0348] Meanwhile, scheduling information (e.g., scheduling IE) can be transmitted only when it is necessary to schedule a device (e.g., responder). For example, when there is no need to update the scheduling information, it is possible not to transmit the scheduling information (or the UWB control data packet containing the scheduling information) in the corresponding ranging cycle. In this case, the transmission of the corresponding control data packet (or the scheduling step for transmitting the corresponding control data packet) can be omitted. For example, as shown in the figure, when there is no need to update the scheduling information transmitted in the first ranging cycle 1410, the transmission of the scheduling information (or the scheduling step) in the second ranging cycle (cycle 1) 1420 can be omitted. In this case, the initiator can skip the scheduling step and immediately execute the trigger step 1242 to trigger multiple transmissions in the first time slot (e.g., time slot index #0) of the second ranging cycle 1420. Thereafter, each responder can execute the multiple transmission step 1423, and the initiator can execute the ranging report step 1424. The operations in the trigger step 1422, multiple transmission step 1423, and ranging report step 1424 of the second ranging cycle 1420 can be the same as the operations in the trigger step 1412, multiple transmission step 1413, and ranging report step 1414 of the first ranging cycle 1410.

[0349] Figure 15 An example of a NB-assisted multiple transmission method according to an embodiment of the present disclosure is shown.

[0350] Although in Figure 15 , the first UWB device is shown as acting as the initiator for transmitting control information (i.e., the first UWB device acts as the role of the controller and the initiator), the first UWB device can act as the controller for transmitting control information, and another UWB device can act as the initiator.

[0351] Although for ease of explanation, Figure 15 shows three UWB devices acting as the initiator or responder, the technical idea of the present disclosure is not limited thereto, and the number of UWB devices acting as the initiator or responder can be implemented in various ways.

[0352] Unlike the multiple transmission method in Figure 14 , in the multiple transmission method (NBA multiple transmission method / NBA-MMS mode) in Figure 15 , the scheduling for multiple transmissions can be performed by using control messages / data packets transmitted via NB (e.g., Figure 13 the control message / data packet containing the scheduling IE in

[0353] Reference Figure 15 , in scheduling step / operation 1511, the first UWB device (initiator) may transmit an NB control message including scheduling information (e.g., scheduling IE in [[ID=lo8]]Figure 13 ) via NB. For example, the initiator may transmit an NB control message including a scheduling IE in the first time slot (e.g., time slot index #0 (time slot 0)) of the first ranging cycle (cycle 0) 1510. In one embodiment, the NB control message may be transmitted at the start time point of time slot 0.

[0354] In triggering step / operation 1412, the initiator may transmit a polling message via NB to trigger multiple transmissions. For example, the initiator may transmit a polling message in the second time slot of the first ranging cycle 1510 (e.g., in the time slot immediately following the time slot allocated for scheduling (e.g., the second time slot (time slot index #1 (time slot 1))). The polling message may include the address of the initiator and / or the address of the responder for multiple transmissions (e.g., 2-byte address or 8-byte address). The responder having the address included in the polling message may initiate multiple transmissions regarding fragments (MMS fragments) to the initiator having the address included in the polling message by using the information included in the NB control message.

[0355] In multiple transmission step / operation 1513, the second UWB device (responder 1) and the third UWB device (responder 2) may transmit multiple fragments based on the scheduling information included in the NB control message. In one embodiment, each MMS fragment / data packet may be transmitted at the start time point of the corresponding ranging time slot. Each MMS fragment transmitted by a responder in the corresponding ranging cycle may include the same sequence data.

[0356] In one embodiment, these fragments may be RSFs.

[0357] In one embodiment, the responder may identify a scheduling list element for the responder in the scheduling IE, and may obtain the sequence data (e.g., MMRS sequence data) to be included in the RSF by using the sequence index field, gap number field, and / or repeat field included in the scheduling list element. The MMRS sequence data may be sequence data generated based on an MMRS sequence (e.g., the MMRS sequence in Table 7).

[0358] In one embodiment, the responder may identify a scheduling list element for the responder in the scheduling IE, and may transmit multiple RSFs (or repeatedly transmit RSFs) by using the start time slot index field, scheduling step field, and / or scheduling repeat field included in the scheduling list element.

[0359] For example, as shown in the figure, responder 1 can obtain the MMRS sequence data (first MMRS sequence data) included in its RSF (first RSF) by using the sequence index field, gap number field, and / or repetition field included in its scheduling list element (first scheduling list element). In addition, responder 1 can repeat the transmission of the first RSF three times within a time period of three time slots corresponding to the third time slot from the first ranging cycle 1410 by using the start time slot index field, scheduling step field, and / or scheduling repetition field included in the first scheduling list element.

[0360] For example, as shown in the figure, responder 2 can obtain the MMRS sequence data (second MMRS sequence data) included in its RSF (second RSF) by using the sequence index field, gap number field, and / or repetition field included in its scheduling list element (second scheduling list element). In addition, responder 2 can repeat the transmission of the first RSF three times within a time period of three time slots corresponding to the third time slot from the second ranging cycle 1410 by using the start time slot index field, scheduling step field, and / or scheduling repetition field included in the second scheduling list element.

[0361] As shown in the figure, MMS fragments (e.g., RSFs) of multiple devices (e.g., responders) can be transmitted in the same time slot (or at the same time point). For example, the RSFs of multiple responders can be transmitted simultaneously in the same time slot (e.g., simultaneously at the start time point of the time slot). In this case, the first MMRS sequence data included in the first RSF transmitted by responder 1 can be different from the second MMRS sequence data included in the second RSF transmitted by responder 2. For example, the index of the MMRS sequence used to generate the first MMRS sequence data can be configured to have a value different from the index of the MMRS sequence used to generate the second MMRS sequence data. For example, the sequence index field in the scheduling list element for responder 1 in the scheduling IE can be configured to have a value different from the sequence index field in the scheduling list element for responder 2 in the scheduling IE. Therefore, even if multiple devices transmit RSFs together within the same time slot, each RSF has a different sequence (or code), and the device receiving the RSFs can thus accurately obtain the RSF of each device (code division scheme).

[0362] In the ranging report step / operation 1514, the initiator can transmit a ranging report to the responder via NB. For example, as shown in the figure, the initiator can transmit a ranging report (ranging report 1) regarding responder 1 to responder 1, and the initiator can transmit a ranging report (ranging report 2) regarding responder 2 to responder 2.

[0363] The above scheduling step 1511, triggering step 1512, multiple transmission step 1513, and ranging report step 1514 can be executed within one ranging cycle 1510.

[0364] Meanwhile, scheduling information (e.g., scheduling IE) can be transmitted only when it is necessary to schedule a device (e.g., responder). For example, when there is no need to update the scheduling information, it may not be necessary to transmit the scheduling information (or the NB control data packet containing the scheduling information) in the corresponding ranging cycle. In this case, the transmission of the corresponding control data packet (or the scheduling step for transmitting the corresponding control data packet) can be omitted. For example, as shown in the figure, when there is no need to update the scheduling information transmitted in the first-round ranging cycle 1510, the transmission of the scheduling information (or the scheduling step) in the second-round ranging cycle (cycle 1) 1520 can be omitted. In this case, the initiator may not execute the scheduling step and can immediately execute the triggering step 1522 to trigger multiple transmissions in the first time slot (e.g., time slot index #0) of the second ranging cycle 1520. Thereafter, each responder can execute the multiple transmission step 1523, and the initiator can execute the ranging report step 1524. The operations in the triggering step 1522, multiple transmission step 1523, and ranging report step 1524 of the second ranging cycle 1520 can be the same as the operations in the triggering step 1512, multiple transmission step 1513, and ranging report step 1514 of the first ranging cycle 1510.

[0365] Figure 16 An example of a method for performing ranging by using NB-assisted multiple transmissions according to an embodiment of the present disclosure is shown.

[0366] Although in Figure 16 the first UWB device is shown as playing the role of an initiator that transmits control information (i.e., the first UWB device plays the roles of a controller and an initiator), the first UWB device can play the role of a controller that transmits control information, and another UWB device can play the role of an initiator.

[0367] Although for convenience of explanation, Figure 16 shows three UWB devices playing the roles of an initiator or a responder, the technical idea of the present disclosure is not limited thereto, and the number of UWB devices playing the roles of an initiator or a responder can be implemented in various ways.

[0368] UWB ranging can be performed by using the above multiple transmission method (NBA-MMS UWB mode). For example, as Figure 16 shown, one-to-many ranging can be performed by using the multiple transmission method. Such UWB ranging can be optimized by using the multiple transmission method.

[0369] In Figure 16 's embodiment, different from the embodiment of Figure 15 , an NB message can be transmitted through NB, and this message can perform the functions of both the NB control message for multiple transmissions (e.g., the NB control message in Figure 14 ) and the polling message (e.g., the polling message in Figure 14 ). That is to say, in Figure 16 's embodiment, the message for scheduling and the message for triggering can be integrated into one message and transmitted. Therefore, in Figure 16 , the scheduling step and the triggering step can be combined into one step.

[0370] Referring to Figure 16 , in the scheduling and triggering step / operation 1611, the first UWB device (initiator) can transmit an NB message containing scheduling information (e.g., the scheduling IE in Figure 13 ) through NB. In addition, the NB message can also perform the function of a polling message for triggering UWB multiple transmissions. In one embodiment, the initiator can transmit an NB message containing the scheduling IE in the first time slot (e.g., time slot index #0 (time slot 0)) of the first ranging cycle (cycle 0) 1610. In one embodiment, the NB message can be transmitted at the starting time point of time slot 0.

[0371] The second UWB device (responder 1) and the third UWB device (responder 2) can respond to the NB message and then transmit a response message to the initiator through NB. For example, each responder can transmit its response message in the time slot after the time slot allocated for the scheduling of the first ranging cycle 1610 (the first time slot (time slot 0)). For example, responder 1 can transmit its response message in the second time slot (e.g., in the time slot immediately following the time slot allocated for the scheduling of the first ranging 1610 (time slot 1)), and responder 2 can transmit its response message in the third time slot (e.g., in the time slot immediately following the second time slot (time slot 2)). In one embodiment, each responder can identify the time slot for transmitting its response message based on the information contained in the scheduling IE. In one embodiment, each response message can be transmitted at the starting time point of the corresponding time slot. After receiving the response messages from responder 1 and responder 2, the initiator can confirm that responder 1 and responder 2 have successfully received the NB message and can perform subsequent steps.

[0372] In the multiple transmission step / operation 1613, the initiator and each responder can transmit multiple data packets based on the scheduling information.

[0373] In one embodiment, the initiator may transmit its MMS packet (initiation MMS packet) at the start time point of each time slot allocated for multiple transmissions. In the present disclosure, the MMS packet may also be referred to as a multiple transmission (MT) packet.

[0374] In one embodiment, each responder may receive the initiation MMS packet in each time slot allocated for multiple transmissions and may transmit its MMS packet (response MMS packet) in response to the initiation MMS packet. In one embodiment, each responder may transmit the response MMS packet at a time point offset by a predetermined offset from the start time point of each time slot allocated for multiple transmissions. Each MMS packet / fragment transmitted by a UWB device (initiator or responder) in a corresponding ranging cycle may contain the same sequence data.

[0375] In one embodiment, the initiation MMS packet of the initiator and / or the response MMS packet of each responder may contain an RSF. In this case, the responder may identify the scheduling list element for the responder in the scheduling IE and may obtain the sequence data (e.g., MMRS sequence) to be included in the RSF by using the sequence index field, gap number field, and / or repetition field included in the scheduling list element. The MMRS sequence data may be sequence data generated based on the MMRS sequence (e.g., the MMRS sequence in Table 7).

[0376] In one embodiment, the responder may identify the scheduling list element for the responder in the scheduling IE and may identify the time slots for transmitting (or repeatedly transmitting) multiple packets by using the start time slot index field, scheduling step field, and / or scheduling repetition field included in the scheduling list element. For example, as shown in the figure, the responder may identify that the fourth time slot of ranging cycle 1510 is the start time slot for multiple transmissions and may transmit the packet four times within a period of four time slots.

[0377] As shown in the figure, the MMS packets (e.g., MMS packets containing RSF) of multiple devices (e.g., responders) may be transmitted in the same time slot. For example, the MMS packets of multiple responders may be simultaneously transmitted in the same time slot (e.g., simultaneously transmitted at a time point offset from the start time point of the corresponding time slot by a certain offset). In this case, a scheme for avoiding conflicts between the corresponding packets needs to be considered.

[0378] For example, in the case where the data packet contains an RSF, the first MMRS sequence data included in the first RSF of the first data packet transmitted by responder 1 can be configured differently from the second MMRS sequence data included in the second RSF of the second data packet transmitted by a second device (e.g., responder 2) to avoid conflicts between data packets. For example, the index of the MMRS sequence used to generate the first MMRS sequence data can be configured to have a value different from the index value of the MMRS sequence used to generate the second MMRS sequence data. In this case, the sequence index field in the scheduling list element for responder 1 in the scheduling IE can be configured to have a value different from the sequence index field in the scheduling list element for responder 2 in the scheduling IE. Thus, even if multiple responders transmit RSFs simultaneously in the same time slot, each RSF has a different sequence (or code), and the initiator receiving the RSFs can accurately acquire the RSFs of each responder.

[0379] Now, reference will be made to Figure 16 Describe the transmission sequence of each time slot in the multiple transmission step 1613 as an example.

[0380] The initiator can transmit and start an MMS data packet via UWB at the start time point of the corresponding time slot in the multiple transmission step / operation 1613, and each of responder 1 and responder 2 can receive the start MMS data packet via UWB.

[0381] Responder 1 can transmit a first response MMS data packet (first data packet) via UWB in the corresponding time slot as a response to the start MMS data packet, responder 2 can transmit a second response MMS data packet (second data packet) via UWB in the corresponding time slot as a response to the start MMS data packet, and the initiator can receive the first response MMS data packet and the second response MMS data packet via UWB. The first response MMS data packet and the second response MMS data packet can be transmitted simultaneously at a time point offset from the start time point of the corresponding time slot by a preconfigured offset. However, as described above, the first RSF included in the first response MMS data packet and the second RSF included in the second response MMS data packet are configured by MMRS sequences (e.g., the MMRS sequences in Table 7) (codes) with different indexes, and the initiator can thus accurately receive the first data packet and the second data packet without conflicts.

[0382] The initiator can perform ranging measurements based on paired initiating MMS packets and response MMS packets. For example, the initiator can calculate a first ToF based on SS-TWR by using the paired initiating MMS packet and the first response MMS packet, and can obtain distance information between the initiator and responder 1 based on the ToF. For example, the initiator can calculate a second ToF based on SS-TWR by using the paired initiating MMS packet and the second response MMS packet, and can obtain distance information between the initiator and responder 2 based on the second ToF.

[0383] In the ranging reporting step / operation 1614, the initiator can transmit a ranging report to the responder via NB. For example, as shown in the figure, the initiator can transmit a ranging report regarding responder 1 (ranging report 1) to responder 1, and the initiator can transmit a ranging report regarding responder 2 (ranging report 2) to responder 2. The ranging report 1 can include the first ToF and / or the distance information between the initiator and responder 1 obtained by using the first ToF, and the ranging report 2 can include the second ToF and / or the distance information between the initiator and responder 2 obtained by using the second ToF.

[0384] The above scheduling step 1611, triggering step 1612, multiple transmission step 1613, and ranging reporting step 1614 can be executed within one ranging cycle 1610.

[0385] Although Figure 16 the embodiments have been described with reference to an example where the MMS packet (MT packet) used in the multiple transmission step 1613 contains RSF, the embodiments are not limited thereto. For example, the MMS packet can include SHR, preamble, STS, or RIF. In this case, the scheduling information included in the NB control message can include information for generating the sequence data included in the corresponding packet. For example, the scheduling information can include the code index information of the ternary code with a length of 31 in Table 4. In one embodiment, the scheduling information can be transmitted through Figure 13 the scheduling IE in Figure 11B or the RDM IE in

[0386] Figure 17 shows the structure of a first UWB device according to an embodiment of the present disclosure.

[0387] In Figure 17 the embodiment of Figure 1 the first UWB device can be an electronic device corresponding to the UWB device in

[0388] In Figure 17 In the embodiments herein, the first UWB device may be a UWB device operating as a controller and / or initiator.

[0389] Referring Figure 17 , the first UWB device may include a transceiver 1710, a controller 1720, and a storage unit 1730. In the present disclosure, the controller may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0390] The transceiver 1710 may transmit / receive signals with other entities.

[0391] The controller 1720 may control the overall operation of the electronic device according to the embodiments proposed in the present disclosure. For example, the controller 1720 may control the signal flow between corresponding blocks to perform operations according to the above flowchart. Specifically, the controller 1720 may control, for example, the operation of the first UWB device described with reference to Figures 1 to 16 and Figures 19 to 21 .

[0392] The storage unit 1730 may store at least one of the information transmitted / received through the transceiver 1710 and the information generated through the controller 1720. For example, the storage unit 1730 may store the information and data required for the method described with reference to Figures 1 to 16 and Figures 19 to 21 .

[0393] The first UWB device or the controller 1720 may transmit a ranging control message for UWB multiple transmission through UWB or NB in the first time slot of the ranging cycle.

[0394] The first UWB device or the controller 1720 may transmit a trigger data packet for triggering UWB multiple transmission through UWB or NB in the second time slot of the ranging cycle.

[0395] The first UWB device or the controller 1720 may receive a first data packet transmitted by the second UWB device through UWB in the third time slot of the ranging cycle based on the ranging control message.

[0396] The first UWB device or the controller 1720 may receive a second data packet transmitted by the third UWB device through UWB in the third time slot of the ranging cycle based on the ranging control message.

[0397] According to one embodiment, in the case where the trigger data packet is transmitted through the UWB channel, the trigger data packet may include a synchronization header, and the synchronization header may include a SYNC field and an SFD field.

[0398] According to one embodiment, in the case of triggering a data packet to be transmitted through an NB channel, the triggering data packet may include a polling message, and the polling message may include address information of a second UWB device and a third UWB device.

[0399] According to one embodiment, a first data packet may include a first ranging sequence fragment (first RSF), a second data packet may include a second ranging sequence fragment (second RSF), and the first RSF may be generated based on a MMRS sequence different from the second RSF.

[0400] According to one embodiment, a ranging control message may include a first scheduling list element regarding a second UWB device and a second scheduling list element regarding a third UWB device. The first scheduling list element may include a first sequence index field indicating an index of a first MMRS sequence for the first RSF. The second scheduling list element may include a second sequence index field indicating an index of a second MMRS sequence for the second RSF. The first sequence index field may be configured to have a value different from the value of the second sequence index field.

[0401] According to one embodiment, the first scheduling list element may further include: a first gap number field indicating the size of a zero gap regarding the first RSF; and a first repetition field indicating the number of repetitions of the first MMRS. The second scheduling list element may further include: a second gap number field indicating the size of a zero gap regarding the second RSF; and a second repetition field indicating the number of repetitions of the second MMRS.

[0402] According to one embodiment, the first data packet and the second data packet may be transmitted at the same time point in a third time slot.

[0403] According to one embodiment, the method may further include the step of transmitting a third data packet in a third time slot within a ranging cycle. The third data packet may be transmitted before the first data packet and the second data packet. The third data packet, the first data packet, and the second data packet may be used for ranging measurement.

[0404] Figure 18 The structure of a second UWB device according to an embodiment of the present disclosure is shown.

[0405] In Figure 18 's embodiment, the second UWB device may be an electronic device corresponding to the UWB device in Figure 1 , including a UWB device, or including a part of a UWB device.

[0406] In Figure 18 's embodiment, the second UWB device may be a UWB device operated as a controller and / or a responder.

[0407] Reference Figure 18 The second UWB device may include a transceiver 1810, a controller 1820, and a storage unit 1830. In the present disclosure, the controller may be defined as a circuit or an application specific integrated circuit or at least one processor.

[0408] The transceiver 1810 may transmit / receive signals with other entities.

[0409] The controller 1820 may control the overall operation of the electronic device according to the embodiments proposed in the present disclosure. For example, the controller 1820 may control the signal flow between the corresponding blocks in order to perform operations according to the above flowchart. Specifically, the controller 1820 may control, for example, the operation of the second UWB device described with reference to Figures 1 to 16 and Figures 19 to 21 The description of the second UWB device.

[0410] The storage unit 1830 may store at least one of the information transmitted / received through the transceiver 1810 and the information generated through the controller 1820. For example, the storage unit 1830 may store the information and data required for the method described with reference to Figures 1 to 16 and Figures 19 to 21 The description of the method.

[0411] The second UWB device or the controller 1820 may receive a ranging control message for UWB multiple transmissions from the first UWB device through UWB or NB in the first time slot within the ranging cycle.

[0412] The second UWB device or the controller 1820 may receive a trigger data packet for triggering UWB multiple transmissions from the first UWB device through UWB or NB in the second time slot within the ranging cycle.

[0413] The second UWB device or the controller 1820 may transmit a first data packet through UWB based on the ranging control message in the third time slot within the ranging cycle.

[0414] According to one embodiment, the third time slot within the ranging cycle may be used by a third UWB device to transmit a second data packet based on the ranging control message.

[0415] According to one embodiment, in the case where the trigger data packet is received through the UWB channel, the trigger data packet may include a synchronization header, and the synchronization header may include a SYNC field and an SFD field.

[0416] According to one embodiment, in the case where the trigger data packet is received through the NB channel, the trigger data packet may include a polling message, and the polling message may include the address information of the second UWB device and the third UWB device.

[0417] According to one embodiment, the first data packet may include a first ranging sequence fragment (first RSF), the second data packet may include a second ranging sequence fragment (second RSF), and the first RSF may be generated based on a MMRS sequence different from the second RSF.

[0418] According to one embodiment, the ranging control message may include a first scheduling list element regarding a second UWB device and a second scheduling list element regarding a third UWB device. The first scheduling list element may include a first sequence index field that indicates an index of a first MMRS sequence for the first RSF. The second scheduling list element may include a second sequence index field that indicates an index of a second MMRS sequence for the second RSF. The first sequence index field may be configured to have a value different from the value of the second sequence index field.

[0419] According to one embodiment, the first scheduling list element may further include: a first gap number field to indicate the size of a zero gap regarding the first RSF; and a first repetition field to indicate the number of repetitions of the first MMRS. The second scheduling list element may further include: a second gap number field to indicate the size of a zero gap regarding the second RSF; and a second repetition field to indicate the number of repetitions of the second MMRS.

[0420] According to one embodiment, the first data packet and the second data packet may be transmitted at the same time point in a third time slot. According to one embodiment, the method may further include the step of transmitting a third data packet in the third time slot within a ranging cycle. The third data packet may be transmitted before the first data packet and the second data packet. The third data packet, the first data packet, and the second data packet may be used for ranging measurements.

[0421] Figure 19 Another example of a NB-assisted multiple transmission method according to an embodiment of the present disclosure is shown.

[0422] Although in Figure 19 the first UWB device is shown as playing the role of an initiator that transmits control information (i.e., the first UWB device plays the role of a controller and an initiator), the first UWB device may play the role of a controller that transmits control information, and another UWB device may play the role of an initiator.

[0423] Although for convenience of explanation, Figure 19 three UWB devices are shown as playing the role of an initiator or a responder in

[0424] where the scheduling step / operation 1511 and the triggering step / operation 1512 are executed separately Figure 15 different from the multiple transmission method in Figure 19 in the multiple transmission method in, the scheduling and / or triggering can be performed by a scheduling / triggering step / operation 1911.

[0425] According to one embodiment, in Figure 15 in the multiple transmission method in, the first UWB device can transmit a control message for scheduling and a polling message for triggering at different time intervals (e.g., different slot indices), respectively. According to one embodiment, in Figure 19 in the multiple transmission method in, the first UWB device can transmit a control message for scheduling and / or triggering at a configured time interval (e.g., a configured slot index).

[0426] Referring to Figure 19 , in the scheduling / triggering step / operation 1911, the first UWB device (initiator) can transmit an NB control message (or an NB control data packet) via NB, which contains at least one of scheduling information and information for triggering multiple transmissions. For example, the initiator can transmit an NB control message (or an NB control data packet) in the first slot (e.g., slot index #0) of the first ranging cycle (cycle 0). In one embodiment, the NB control message can be transmitted at the starting time point of slot 0.

[0427] According to one embodiment, the information for triggering multiple transmissions can include the address of the initiator and / or the address of the responder for multiple transmissions (e.g., a 2-byte address or an 8-byte address). The responder having the address included in the information for triggering multiple transmissions can initiate and / or perform multiple transmissions regarding fragments (MMS fragments) to the corresponding initiator by using the information included in the NB control message.

[0428] In the multiple transmission step / operation 1912, the second UWB device (responder 1) and the third UWB device (responder 2) can transmit multiple fragments based on the scheduling information included in the NB control message. In one embodiment, each MMS fragment / data packet can be transmitted at the starting time point of the corresponding ranging slot. Each MMS fragment transmitted by a responder in the corresponding ranging cycle can contain the same sequence data.

[0429] According to one embodiment, these fragments can be RSFs. According to one embodiment, the second UWB device (responder 1) and / or the third UWB device (responder 2) can transmit multiple RSFs (or repeatedly transmit RSFs) by using the slot index included in the NB control message (or the NB control data packet) transmitted in the scheduling / triggering step / operation 1911.

[0430] According to one embodiment, the second UWB device (Responder 1) and / or the third UWB device (Responder 2) may obtain sequence data (e.g., MMRS sequence data) to be included in the RSF by using the UWB PHYCONFIG field included in the NB control message (or NB control data packet) transmitted in the scheduling / triggering step / operation 1911. The MMRS sequence data may be sequence data generated based on an MMRS sequence (e.g., the MMRS sequence in Table 7).

[0431] In the ranging report step / operation 1913, the first UWB device (Initiator) may transmit a ranging report to the second UWB device (Responder 1) and / or the third UWB device (Responder 2) via NB. According to one embodiment, the first UWB device (Initiator) may transmit a ranging report (ranging report 1) regarding the second UWB device (Responder 1) to the second UWB device (Responder 1). According to one embodiment, the first UWB device (Initiator) may transmit a ranging report (ranging report 2) regarding the third UWB device (Responder 2) to the third UWB device (Responder 2).

[0432] The above scheduling / triggering step 1911, multiple transmission step 1912, and ranging report step 1913 may be performed within one ranging cycle (e.g., the first ranging cycle).

[0433] Meanwhile, scheduling information (e.g., the scheduling information included in the NB control message (or NB control data packet) transmitted in the scheduling / triggering step / operation 1911) may be transmitted only when scheduling of a device (e.g., a responder) is required. For example, when there is no need to update the scheduling information, there may be no need to transmit the scheduling information in the corresponding ranging cycle. In this case, the first UWB device (Initiator) may transmit, via NB, an NB control message including information (excluding scheduling information) for multiple transmission triggering in the triggering step 1921. Thereafter, the second UWB device (Responder 1) and / or the third UWB device (Responder 2) may perform the multiple transmission step 1922, and the first UWB device (Initiator) may perform the ranging report step 1524.

[0434] The above triggering step 1921, multiple transmission step 1922, and ranging report step 1923 may be performed within one ranging cycle (e.g., the second ranging cycle).

[0435] Figure 20 The packet format of the NB control data packet according to an embodiment of the present disclosure is shown.

[0436] According to one embodiment, the NB control data packet may include Figure 19 the NB control message transmitted in the scheduling / triggering step 1911 in []. According to one embodiment, the NB control data packet may include the one in Figure 19 the NB control message transmitted in the triggering step 1921 in []. According to one embodiment, the NB control data packet may include the one in Figure 15 the NB control message transmitted in the scheduling step 1511 in [].

[0437] Refer to Figure 20 , the NB control data packet may include at least one of an ID field, a hash field, a prand field, a MessageControl field, and a MessageContents field. The hash field and the prand field may constitute a resolvable private address (RPA).

[0438] The ID field may be configured by a configured octet (e.g., 1 octet), and may indicate an ID for distinguishing the NB control message from other messages. According to one embodiment, the UWB device may distinguish the NB control message from other messages based on the ID field.

[0439] Each of the hash field and the prand field that constitute the resolvable private address (RPA) may be configured by a configured octet (e.g., 3 octets).

[0440] The hash field may contain RPA_hash configured by the result value of the Advanced Encryption Standard (AES)-128-Electronic Codebook (ECB) ([Key = IdentityResolvingKey, Data = RPA_prand]). The IdentityResolvingKey known only to two devices (e.g., the first UWB device and the second UWB device) may be used as the key value, and RPA_prand (the prand field value) may be used as the data value.

[0441] The prand field may be configured to have a static value of at least one ranging block. The prand field may contain RPA_prand.

[0442] According to one embodiment, the UWB device may identify the RPA by using the key (=IdentityResolvingKey) and the data (=RPA_prand). According to one embodiment, the UWB device may identify the RPA by using the data (=RPA_prand) included in the NB control data packet (or the NB control message) and the key (=IdentityResolvingKey) saved thereby.

[0443] The MessageControl field can be configured by a configured octet (e.g., 1 octet).

[0444] The size of the MessageContents field can be configured differently according to the MessageControl field. The information contained in the MessageContents field can vary according to the MessageControl field.

[0445] In the present disclosure, the NB control data packet can be implemented in various ways according to the configurations of the MessageControl field and the MessageContents field.

[0446] According to one embodiment, the MessageControl field and the MessageContents field contained in the NB control data packet can be configured as shown in Table 8: [Table 8]

[0447] For example, if the MessageControl field is 0x00, the MessageContents field can be configured by a list of the number of responders in 1 octet, the responder address in 3 octets, the slot index in 1 octet, and the UWB PHY configuration in 3 octets. The number of responders can indicate the number of list elements configured by the following {responder address, slot index, UWB PHY configuration}. For example, when the value of the number of responders field is 2, the following list elements {responder address, slot index, UWB PHY configuration} can be repeated twice.

[0448] For example, if the MessageControl field is 0x01, the MessageContents field can be configured by a list of the number of responders in 1 octet, the responder address in 3 octets, and the slot index in 1 octet. For example, if the MessageControl field is 0x02, the MessageContents field can be configured by a list of the number of responders in 1 octet, the responder address in 3 octets, and the UWB PHY configuration in 3 octets.

[0449] According to one embodiment, the description of the MessageContents field listed in Table 8 can be configured as shown in Table 9: [Table 9]

[0450] For example, bits 0 to 5 of the UWB PHY configuration indicate the preamble code index. For example, when 9 ≤ preamble code index ≤ 32, bits 6 to 12 can be configured to be reserved. For example, when 33 ≤ preamble code index ≤ 48, bits 6 to 12 can indicate the MMRS complementary set zero, bits 13 to 15 can indicate the number of MSRs, bits 16 to 19 can indicate the UWB channel, and bits 20 to 23 can be configured to be reserved.

[0451] Each MMRS can be divided into part A (left part) and part B (right part) ([A, B]), one MMRS symbol can be configured by [A, Z, B, Z], and one RSF can be configured by the repetition of MMRS symbols. Z can indicate the 0s filled between A and B, and the number of 0s can be the value of the MMRS complementary set zero field. The number of MSRs (MMRS symbol repetition) field can indicate the MMRS symbol value for repeating to configure one RSF, and the number of MSRs can be configured as one of {32, 40, 48, 64, 128, 256}.

[0452] According to one embodiment, the MessageControl field and the MessageContents field included in the NB control data packet can be configured as shown in Table 10: [Table 10]

[0453] For example, if the MessageControl field is 0x03, the configuration of the MessageContents field can be the same as the configuration of the MessageContents field when the MessageControl field in Tables 8 and 9 is 0x00, but the polling message may not be transmitted. For example, if the MessageControl field is 0x04, the configuration of the MessageContents field can be the same as the configuration of the MessageContents field when the MessageControl field in Tables 8 and 9 is 0x01, but the polling message may not be transmitted. For example, if the MessageControl field is 0x05, the configuration of the MessageContents field can be the same as the configuration of the MessageContents field when the MessageControl field in Tables 8 and 9 is 0x02, but the polling message may not be transmitted. For example, if the MessageControl field is set to 0x06, the MessageContents field can be configured to 0x00, but the polling message may not be transmitted.

[0454] According to one embodiment, if the MessageContents field of the NB control data packet is configured to 0x00, the corresponding part can be filled with 0x00 and then transmitted, or can be transmitted in an empty state.

[0455] According to one embodiment, the MessageControl field and the MessageContents field included in the NB control data packet can be configured as shown in Table 11: [Table 11]

[0456] For example, if the MessageControl field is 0x10, the configuration of the MessageContents field can be the same as the configuration of the MessageContents field when the MessageControl field in Tables 8 and 9 is 0x00, but only the initiator can transmit measurement reports.

[0457] For example, if the MessageControl field is 0x13, the configuration of the MessageContents field can be the same as the configuration of the MessageContents field when the MessageControl field in Tables 8 and 9 is 0x00, but polling messages will not be transmitted, and only the initiator can transmit measurement reports.

[0458] For example, if the MessageControl field is 0x06, the MessageContents field can be configured to 0x00, but polling messages may not be transmitted, and only the initiator can transmit measurement reports. According to one embodiment, if the MessageContents field of the NB control data packet is configured to 0x00, the corresponding part can be filled with 0x00 and then transmitted, or can be transmitted in an empty state.

[0459] According to one embodiment, the MessageControl field and the MessageContents field included in the NB control data packet can be configured as shown in Table 12: [Table 12]

[0460] For example, when the MessageControl field is 0x20, the configuration of the MessageContents field can be the same as the configuration of the MessageContents field when the MessageControl field in Tables 8 and 9 is 0x00, but only the responder can transmit measurement reports.

[0461] For example, if the MessageControl field is 0x23, the configuration of the MessageContents field can be the same as that of the MessageContents field when the MessageControl field in Tables 8 and 9 is 0x00, but no polling message will be transmitted, and only the responder can transmit measurement reports.

[0462] For example, if the MessageControl field is 0x26, the MessageContents field can be configured to 0x00, but no polling message may be transmitted, and only the responder can transmit measurement reports. According to one embodiment, if the MessageContents field of the NB control data packet is configured to 0x00, the corresponding part can be filled with 0x00 and then transmitted, or it can be transmitted in an empty state.

[0463] According to one embodiment, the MessageControl field and the MessageContents field included in the NB control data packet can be configured as shown in Table 13: [Table 13]

[0464] For example, when the MessageControl field is 0x30, the configuration of the MessageContents field can be the same as that of the MessageContents field when the MessageControl field in Tables 8 and 9 is 0x00, but both the initiator and the responder can transmit measurement reports.

[0465] For example, if the MessageControl field is 0x33, the configuration of the MessageContents field can be the same as that of the MessageContents field when the MessageControl field in Tables 8 and 9 is 0x00, but no polling message will be transmitted, and both the initiator and the responder can transmit measurement reports.

[0466] For example, if the MessageControl field is 0x36, the MessageContents field can be configured to 0x00, but no polling message may be transmitted, and both the initiator and the responder can transmit measurement reports. According to one embodiment, if the MessageContents field of the NB control data packet is configured to 0x00, the corresponding part can be filled with 0x00 and then transmitted, or it can be transmitted in an empty state.

[0467] According to one embodiment, the MessageControl field and the MessageContents field included in the NB control data packet can be configured based on a combination of at least one of Tables 8 to 13.

[0468] Figure 21 FIG. shows a data packet format of an NB polling data packet according to an embodiment of the present disclosure.

[0469] According to one embodiment, the NB polling data packet can include an NB control message transmitted in the scheduling / triggering step 1911 in Figure 19 According to one embodiment, the NB polling data packet can include an NB control message transmitted in the triggering step 1921 in Figure 19 According to one embodiment, the NB polling data packet can include an NB message transmitted in the triggering step 1512 in Figure 15 According to one embodiment, the NB polling data packet can include at least one of an ID field, a hash field, a MessageControl field, and a MessageContents field.

[0470] Refer to Figure 21 The NB polling data packet can include at least one of an ID field, a hash field, a MessageControl field, and a MessageContents field.

[0471] The ID field can be configured by a configured octet (e.g., 1 octet) and can indicate an ID for distinguishing an NB control message regarding the NB polling data packet from other messages. According to one embodiment, the UWB device can distinguish an NB control message regarding the NB polling data packet from other messages based on the ID field.

[0472] The hash field can include an RPA_hash configured by the Advanced Encryption Standard (AES)-128-Electronic Codebook (ECB) ([Key = IdentityResolvingKey, Data = RPA_prand]).

[0473] The MessageControl field can be configured by a configured octet (e.g., 1 octet).

[0474] The size of the MessageContents field can be configured differently according to the MessageControl field. The information included in the MessageContents field can vary according to the MessageControl field.

[0475] According to one embodiment, if the MessageContents field of the NB polling data packet is configured to 0x00, the corresponding part can be filled with 0x00 and then transmitted, or can be transmitted in an empty state.

[0476] In the present disclosure, the NB polling data packet can be implemented in various ways according to the configurations of the MessageControl field and the MessageContents field.

[0477] According to one embodiment, the MessageControl field and the MessageContents field included in the NB polling data packet can be configured as shown in Table 14.

[0478] [Table 14]

[0479] For example, if the MessageControl field is 0x00, the MessageContents field can be configured as 0x00. According to one embodiment, if the MessageContents field of the NB polling data packet is configured as 0x00, the corresponding part can be filled with 0x00 and then transmitted, or it can be transmitted in an empty state.

[0480] For example, if the MessageControl field is 0x01, the MessageContents field can be configured by a list of the number of 1-byte responders, the 3-byte responder address, and the 3-byte UWB PHY configuration. According to one embodiment, the descriptions of the MessageContents field listed in Table 14 can be configured as shown in Table 9.

[0481] The number of responders can indicate the number of list elements configured by the following {responder address, UWB PHY configuration}. For example, when the value of the number of responders field is 2, the following list elements {responder address, UWB PHY configuration} can be repeated twice.

[0482] In the above detailed embodiments of the present disclosure, according to the presented detailed embodiments, the elements included in the present disclosure are expressed in singular or plural. However, for ease of description, the singular form or the plural form is appropriately selected for the presented situation, and the present disclosure is not limited to the elements expressed in singular or plural. Therefore, the elements expressed in plural may also include a single element, or the elements expressed in singular may also include multiple elements.

[0483] Although specific embodiments have been described in the detailed description of the present disclosure, various modifications and changes can be made without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be defined as limited to the embodiments described herein, but should be defined by the appended claims and their equivalents. < / owr>

Claims

1. A method for operating a first ultra-wideband (UWB) device, the method comprising: In a first time slot within a ranging cycle, transmitting a ranging control message for UWB multiple transmissions via UWB or narrowband (NB); In a second time slot within the ranging cycle, transmitting a trigger data packet for triggering the UWB multiple transmissions via the UWB or the NB; Based on the ranging control message, receiving, via the UWB, a first data packet transmitted by a second UWB device in a third time slot within the ranging cycle; and Based on the ranging control message, receiving, via the UWB, a second data packet transmitted by a third UWB device in the third time slot within the ranging cycle.

2. The method according to claim 1, wherein Based on the trigger data packet transmitted via a UWB channel, the trigger data packet includes a synchronization header, and the synchronization header includes a SYNC field and an SFD field.

3. The method according to claim 1, wherein, Based on the trigger data packet transmitted via an NB channel, the trigger data packet includes a polling message, and the polling message includes address information of the first UWB device and at least one of address information of the second UWB device and the third UWB device.

4. The method according to claim 1, wherein, The first data packet includes a first ranging sequence fragment (first RSF), wherein the second data packet includes a second ranging sequence fragment (second RSF), and wherein the first RSF is generated based on a MMRS sequence different from the second RSF.

5. The method according to claim 4, wherein, The ranging control message includes a first scheduling list element regarding the second UWB device and a second scheduling list element regarding the third UWB device, wherein the first scheduling list element includes a first sequence index field that indicates an index of a first MMRS sequence for the first RSF, wherein the second scheduling list element includes a second sequence index field that indicates an index of a second MMRS sequence for the second RSF, and wherein a value of the first sequence index field is configured to be different from a value of the second sequence index field.

6. The method according to claim 5, wherein, The first scheduling list element further includes: a first gap number field that indicates a size of a zero gap regarding the first RSF; and a first repetition field that indicates a repetition number of the first MMRS, and wherein the second scheduling list element further includes: a second gap number field that indicates a size of a zero gap regarding the second RSF; and a second repetition field that indicates a repetition number of the second MMRS.

7. The method according to claim 4, wherein, The first data packet and the second data packet are transmitted at the same time point in the third time slot.

8. The method according to claim 1, further comprising transmitting a third data packet in a third time slot within the ranging cycle, Among them, wherein the third data packet is transmitted before the first data packet and the second data packet, and the third data packet, the first data packet, and the second data packet are used for ranging measurements.

9. A method for operating a second Ultra - Wideband (UWB) device, the method comprising: In a first time slot within a ranging cycle, receiving, via UWB or narrowband (NB), a ranging control message for UWB multiple transmissions from a first UWB device; In a second time slot within the ranging cycle, receiving, via the UWB or the NB, a trigger data packet for triggering the UWB multiple transmissions from the first UWB device; and Based on the ranging control message, transmitting a first data packet via the UWB in a third time slot within the ranging cycle, wherein the third time slot within the ranging cycle is for a second data packet to be transmitted by a third UWB device based on the ranging control message.

10. The method according to claim 9, wherein, Based on the trigger data packet received via a UWB channel, the trigger data packet includes a synchronization header, and the synchronization header includes a SYNC field and an SFD field.

11. The method according to claim 10, wherein, Based on the trigger data packet received via an NB channel, the trigger data packet includes a polling message, and the polling message includes the address information of the first UWB device and at least one of the address information of the second UWB device and the third UWB device.

12. The method according to claim 9, wherein, The first data packet includes a first ranging sequence fragment (first RSF), wherein the second data packet includes a second ranging sequence fragment (second RSF), and wherein the first RSF is generated based on a MMRS sequence different from the second RSF.

13. The method according to claim 12, wherein, The ranging control message includes a first scheduling list element regarding the second UWB device and a second scheduling list element regarding the third UWB device, wherein the first scheduling list element includes a first sequence index field, and the first sequence index field indicates the index of the first MMRS sequence for the first RSF, wherein the second scheduling list element includes a second sequence index field, and the second sequence index field indicates the index of the second MMRS sequence for the second RSF, and wherein the value of the first sequence index field is configured to be different from the value of the second sequence index field.

14. A first Ultra - Wideband (UWB) device, comprising: A transceiver; And A controller, connected to the transceiver and configured to control the transceiver, wherein the UWB device is configured to: In a first time slot within a ranging cycle, transmit, via UWB or narrowband (NB), a ranging control message for UWB multiple transmissions; In a second time slot of the ranging cycle, transmit, via the UWB or the NB, a trigger data packet for triggering the UWB multiple transmissions; Based on the ranging control message, receive, via the UWB, a first data packet transmitted by a second UWB device in a third time slot within the ranging cycle; and Based on the ranging control message, receive, via the UWB, a second data packet transmitted by a third UWB device in the third time slot within the ranging cycle.

15. A second Ultra - Wideband (UWB) device, comprising: A transceiver; And A controller, connected to the transceiver and configured to control the transceiver, wherein the UWB device is configured to: In a first time slot within a ranging cycle, receive a ranging control message for UWB multiple transmissions from a first UWB device via UWB or narrowband NB; In a second time slot of the ranging cycle, receive a trigger data packet for triggering the UWB multiple transmissions from the first UWB device via the UWB or the NB; and Based on the ranging control message, transmit a first data packet via the UWB in a third time slot within the ranging cycle, wherein the third time slot within the ranging cycle is for a second data packet to be transmitted by a third UWB device based on the ranging control message.

Images