Method and apparatus for transmitting or receiving data based on a hyperblock structure in an ultra-wideband wireless network system

Abstract

A method and apparatus for hyperblock structure-based transmission or reception in an ultra-wideband (UWB) wireless network system is disclosed. A method performed by a first device in an ultra-wideband (UWB) wireless network system according to one embodiment of the present disclosure may include generating, by the first device, an information element (IE) including a device list associated with a ranging block, and transmitting a frame including the IE to one or more second devices. The ranging block may be one of one or more ranging blocks in a respective hyperblock.

Description

[Technical Field]

[0001] The present disclosure relates to a method and apparatus for hyperblock structure-based transmission or reception in an ultra-wideband wireless network system. [Background technology]

[0002] A low-rate (LR) wireless network can support low data rate connectivity between fixed or mobile devices with limited battery consumption requirements. For example, an LR wireless network may be applied to a wireless personal area network (WPAN). The Institute of Electrical and Electronics Engineers (IEEE) 802.15.4 standard defines various techniques for the physical layer (PHY) and radio access control (MAC) sublayer for LR wireless networks. For example, the IEEE 802.15.4 standard defines various modes that support precision ranging.

[0003] Ultra-wideband (UWB) wireless networks can transmit large amounts of information at low power over a very wide bandwidth (e.g., a frequency band from 3.1 GHz to 10.6 GHz). For example, UWB technology can convert digital code information into impulse signals with extremely short time durations of less than nanoseconds and transmit them wirelessly. The IEEE 802.15.4z standard defines ultra-wideband (UWB) technology related to ranging technology. For example, the IEEE 802.15.4z standard includes (comprises; configures; establishes; includes; encompasses; contains; has) high-rate pulse frequency (HRP) PHY technology, which supports high-speed data communication (e.g., 27-31 Mbps) and accurate two-way ranging and positioning, and high-rate pulse frequency (LRP) PHY technology, which supports various modes for low-speed data communication (e.g., RFID (Radio Frequency Identification) applications). The IEEE 802.15.4z standard includes UWB PHY technology that improves the integrity and accuracy of ranging measurements, and MAC technology that supports the exchange of ranging-related information between devices participating in ranging and the control of the time-of-flight (TOF) ranging procedure. Currently, the IEEE 802.15.4ab standard is under discussion to enhance UWB PHY / MAC, including improving IEEE 802.15.4z-based wireless network technology. Summary of the Invention [Problem to be solved by the invention]

[0004] The technical problem of the present disclosure is to provide a method and apparatus for transmitting or receiving based on a hyperblock structure in a UWB wireless network system.

[0005] A further technical object of the present disclosure is to provide a method and apparatus for transmitting or receiving a control message based on device allocation information for blocks within a hyperblock in a UWB wireless network system.

[0006] The technical problems to be solved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the following description. [Means for solving the problem]

[0007] According to one aspect of the present disclosure, a method performed by a first device in an ultra-wideband (UWB) wireless network system may include generating, by the first device, an information element (IE) including a device list associated with a ranging block, and transmitting, to one or more second devices, a frame including the IE, where the ranging block may be one of one or more ranging blocks in a respective hyperblock.

[0008] According to a further aspect of the present disclosure, a method performed by a second device in an ultra-wideband (UWB) wireless network system may include receiving, from a first device, a frame including an information element (IE) including a list of devices associated with a ranging block, and determining, based on the inclusion of the second device in the device list, that the ranging block is assigned to the second device. The ranging block may be one of one or more ranging blocks in a respective hyperblock. [Effects of the Invention]

[0009] According to the present disclosure, the technical problem of the present disclosure is to provide a method and apparatus for transmitting or receiving based on a hyperblock structure in a UWB wireless network system.

[0010] According to the present disclosure, it is possible to provide a method and apparatus for transmitting or receiving a control message based on device allocation information for a block within a hyperblock in a UWB wireless network system.

[0011] The effects obtained from the present disclosure are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those having ordinary skill in the art to which the present disclosure pertains from the following description. [Brief explanation of the drawings]

[0012] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present disclosure, provide examples for the present disclosure and, together with the detailed description, explain the technical features of the present disclosure. [Figure 1] FIG. 1 is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure. [Figure 2] 1 is a diagram for explaining an HRP UWB PPDU format to which the present disclosure can be applied. FIG. [Figure 3] 10 is a diagram for explaining the configuration of an HRP UWB PPDU STS packet structure to which the present disclosure can be applied. FIG. [Figure 4] FIG. 10 is a diagram for explaining a two-way ranging technique to which the present disclosure can be applied. [Figure 5] A figure for explaining examples of formats of RMI IE, RCPCS IE, RRMC IE, and RRTI IE to which the present disclosure can be applied. [Figure 6] 10 is an example message sequence chart for SS-TWR applying deferred response time results to which the present disclosure is applicable. [Figure 7] 10 is an example message sequence chart for SS-TWR with embedded response time results to which the present disclosure is applicable. [Figure 8] 10 is an example of a message sequence chart for SS-TWR using SP3 packets to which the present disclosure can be applied. [Figure 9] 10 is an example message sequence chart for DS-TWR with deferred response time information applicable to the present disclosure. [Figure 10] 10 is an example of a message sequence chart for DS-TWR with embedded ranging time information to which the present disclosure can be applied. [Figure 11] FIG. 10 is a diagram for explaining the roles of devices in a ranging procedure to which the present disclosure can be applied. [Figure 12] A figure showing examples of formats of ARC IE, RDM IE, RBU IE, RR IE, and SRRE IE to which the present disclosure can be applied. [Figure 13] 10A and 10B are diagrams for explaining a ranging block structure and ranging phases to which the present disclosure can be applied. [Figure 14] 10A-10C are example timing diagrams for various multiple device ranging applications of the present disclosure. [Figure 15] 1 is a timing diagram illustrating an example of a block-based mode to which the present disclosure can be applied. [Figure 16] FIG. 10 is a diagram illustrating examples of various transmission offsets to which the present disclosure can be applied. [Figure 17] 10 is an example of a message sequence chart for one-to-many SS-TWR to which the present disclosure can be applied. [Figure 18] 10 is an example of a message sequence chart for SP3 one-to-many SS-TWR to which the present disclosure can be applied. [Figure 19] FIG. 10 illustrates the difference in time structure between a single application and a combination of various applications to which the present disclosure can be applied. [Figure 20] 10A and 10B are diagrams for explaining the operation of a first device according to the present disclosure. [Figure 21] 10A and 10B are diagrams for explaining the operation of a second device according to the present disclosure. [Figure 22] FIG. 10 illustrates an example of a time structure in a hyperblock-based mode according to the present disclosure. [Figure 23] FIG. 10 illustrates an example of an HBS IE format according to the present disclosure. [Figure 24] FIG. 10 is a diagram illustrating another example of the HBS IE format according to the present disclosure. [Figure 25] 10A and 10B are diagrams illustrating examples of the actions of a controlled person based on hyperblock information according to the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0013] Preferred embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. The detailed description disclosed below together with the accompanying drawings is intended to describe exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure can be implemented. The detailed description below includes specific details to provide a complete understanding of the present disclosure. However, it will be understood by those skilled in the art that the present disclosure can be implemented without such specific details.

[0014] In some cases, in order to avoid obscuring the concepts of the present disclosure, known structures and devices may be omitted or shown in block diagram form, focusing on the core functions of each structure and device.

[0015] In this disclosure, when a component is "coupled," "coupled," or "connected" to another component, this may include a direct connection as well as an indirect connection where there is another component between them. Also, in this disclosure, the terms "comprise" or "have" specify the presence of stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0016] In this disclosure, terms such as "first" and "second" are used only to distinguish one component from another, and are not used to limit the components, and do not limit the order or importance of the components unless otherwise specified. Therefore, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0017] The terms used in this disclosure are for the purpose of describing particular embodiments and are not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular is intended to include the plural unless the context clearly dictates otherwise. The term "and / or" as used in this disclosure means that one of the associated listed items may be included, or that any and all possible combinations of two or more of them may be included. Also, in this disclosure, " / " between words has the same meaning as "and / or" unless specifically stated otherwise.

[0018] Examples of the present disclosure may be applied to various wireless communication systems. For example, examples of the present disclosure may be applied to an IEEE 802.15 standard-based wireless network (e.g., Zigbee, Bluetooth, etc.). In particular, examples of the present disclosure may be applied to an IEEE 802.15.4 standard-based wireless network, and further to a newly proposed IEEE 802.15.4ab standard-based UWB wireless network or a next-generation UWB wireless network after IEEE 802.15.4ab. The wireless communication system to which the examples of the present disclosure are applied is not limited to IEEE 802.15 series wireless networks, but may also be applied to IEEE 802.11 series wireless local area network (WLAN) technology or Wi-Fi technology, or to a cellular wireless communication system (e.g., 3GPP (3rd Generation Partnership Project: registered trademark; the same applies hereinafter) standard Long Term Evolution (LTE) series technology and 5G New Radio (NR), etc.).

[0019] The IEEE 802.15.4ab standard is under discussion and includes technologies for further enhancing the UWB PHY / MAC. For example, the IEEE 802.15.4ab standard discusses: additional coding, preambles, and modulation techniques to support increased link budget and / or reduced airtime; additional channels and operating frequencies; interference mitigation techniques to support higher device density and higher traffic use cases; improvements to accuracy, precision, reliability, and interoperability for high-integrity ranging; techniques to reduce complexity and power consumption; definition of hybrid operation with narrowband signaling to supplement UWB; improved native discovery and association setup mechanisms; sensing capabilities to support presence detection and environment mapping; mechanisms to support low-power, low-latency streaming as well as high-data-rate streaming allowing a throughput of at least 50 Mbps; and support for peer-to-peer, peer-to-multipeer, and station-to-infrastructure protocols and infrastructure synchronization mechanisms.

[0020] The following describes technical features to which examples of the present disclosure can be applied.

[0021] FIG. 1 is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure.

[0022] 1 may be referred to by various terms such as a terminal, a wireless device, a wireless transmit receive unit (WTRU), a user equipment (UE), a mobile station (MS), a user terminal (UT), a mobile subscriber station (MSS), a mobile subscriber unit (MSS), a subscriber station (SS), an advanced mobile station (AMS), a wireless terminal (WT), or simply a user. In addition, the first device 100 and the second device 200 may be referred to by various terms such as an access point (AP), a base station (BS), a fixed station, a Node B, a base transceiver system (BTS), a network, an artificial intelligence (AI) system, a road side unit (RSU), a repeater, a router, a relay, a gateway, etc.

[0023] If the devices 100 and 200 illustrated in FIG. 1 support ranging, they may be referred to as ranging-capable devices (RDEVs) or enhanced ranging-capable devices (ERDEVs). For example, the devices 100 and 200 illustrated in FIG. 1 may be referred to by various terms, such as a transmitting device, a receiving device, a transmitting RDEV, a receiving RDEV, a transmitting ERDEV, and a receiving ERDEV. For example, the devices 110 and 200 may be referred to as an initiator, a responder, an originator, a recipient, a controller, a controlee, and the like, depending on their role in the ranging operation. The role of a device is not fixed and may be determined relatively depending on its relationship with other devices. When a device interacts with multiple devices, a single device may take on various roles.

[0024] Referring to FIG. 1, a first device 100 and a second device 200 can transmit and receive wireless signals using various UWB wireless network technologies (e.g., IEEE 802.15.4 series). The first device 100 and the second device 200 may include interfaces for a medium access control (MAC) layer and a physical layer (PHY) according to the IEEE 802.15.4 standard. The IEEE 802.15.4-based PHY and MAC are included in a UWB subsystem, which may further include a UWB command interface (UCI) corresponding to an interface between a UWB controller and a host. The UWB subsystem can send and receive messages to and from a host system via the UCI.

[0025] The first device 100 and the second device 200 may also support various communication standards other than UWB wireless network technology (e.g., IEEE 802.15 series, IEEE 802.11 series, 3GPP LTE series, 5G NR series, etc.). The devices disclosed herein may be embodied as various devices such as mobile phones, vehicles, personal computers, augmented reality (AR) equipment, and virtual reality (VR) equipment. The devices disclosed herein may also support various communication services such as voice calls, video calls, data communications, autonomous driving, machine-type communication (MTC), machine-to-machine (M2M), device-to-device (D2D), and Internet-of-Things (IoT).

[0026] The first device 100 includes one or more processors 102 and one or more memories 104, and may additionally include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may be configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts of the present disclosure. For example, the processor 102 may process information in the memory 104 to generate first information / signals, and then transmit a wireless signal including the first information / signals via the transceiver 106. The processor 102 may also receive a wireless signal including second information / signals via the transceiver 106, and then store information obtained from signal processing of the second information / signals in the memory 104. The memory 104 may be coupled to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including instructions for executing some or all of the processes controlled by the processor 102 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts in this disclosure. Here, the processor 102 and the memory 104 may be part of a communications modem / circuit / chip designed to implement UWB wireless network technology (e.g., the IEEE 802.15.4 series). The transceiver 106 may be coupled to the processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used interchangeably with an RF (Radio Frequency) unit. In this disclosure, a device may also refer to a communications modem / circuit / chip.

[0027] The second device 200 includes one or more processors 202, one or more memories 204, and may additionally include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may be configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure. For example, the processor 202 may process information in the memory 204 to generate third information / signal, and then transmit a wireless signal including the third information / signal via the transceiver 206. The processor 202 may also receive a wireless signal including fourth information / signal via the transceiver 206, and then store information obtained from signal processing of the fourth information / signal in the memory 204. The memory 204 may be coupled to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software code including instructions for executing some or all of the processes controlled by the processor 202 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure. Here, the processor 202 and the memory 204 may be part of a communications modem / circuit / chip designed to implement UWB wireless network technology (e.g., the IEEE 802.15.4 series). The transceiver 206 may be coupled to the processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with an RF unit. In this disclosure, a device may also refer to a communications modem / circuit / chip.

[0028] The hardware elements of the devices 100, 200 are described in more detail below. Without limitation, one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY and MAC). The one or more processors 102, 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams in this disclosure. The one or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams in this disclosure. The one or more processors 102, 202 can generate and provide signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, suggestions, and / or methods of this disclosure to the one or more transceivers 106, 206. The one or more processors 102, 202 can receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts of this disclosure.

[0029] The one or more processors 102, 202 may be referred to as a controller, microcontroller, microprocessor, or microcomputer. The one or more processors 102, 202 may be implemented using hardware, firmware, software, or a combination thereof. As an example, the one or more processors 102, 202 may include one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs). The descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to execute the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure may be included in one or more processors 102, 202 or stored in one or more memories 104, 204 and executed by one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure may be embodied by firmware or software in the form of code, instructions, and / or collections of instructions.

[0030] One or more memories 104, 204 may be coupled to one or more processors 102, 202 and may store various types of data, signals, messages, information, programs, code, instructions, and / or instructions. The one or more memories 104, 204 may be comprised of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories 104, 204 may be located internal and / or external to the one or more processors 102, 202. Additionally, the one or more memories 104, 204 may be coupled to the one or more processors 102, 202 via various techniques, such as wired or wireless connections.

[0031] One or more transceivers 106, 206 may transmit user data, control information, wireless signals / channels, etc., as referred to in the methods and / or operational flowcharts of the present disclosure, to one or more other devices. One or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts of the present disclosure, from one or more other devices. For example, one or more transceivers 106, 206 may be coupled to one or more processors 102, 202 and may transmit and receive wireless signals. For example, one or more processors 102, 202 may control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Furthermore, one or more transceivers 106, 206 may be coupled to one or more antennas 108, 208, and may be configured to transmit or receive user data, control information, wireless signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure, via the one or more antennas 108, 208. In this disclosure, the one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 may convert the received user data, control information, wireless signals / channels, etc., from RF band signals to baseband signals for processing using one or more processors 102, 202. The one or more transceivers 106, 206 may convert the user data, control information, wireless signals / channels, etc., processed using one or more processors 102, 202, from baseband signals to RF band signals. To that end, one or more of the transceivers 106, 206 may include (analog) oscillators and / or filters.

[0032] For example, the transceivers 106 and 206 in FIG. 1 may perform operations of transmitting and receiving signals (e.g., packets or PPDUs (Physical Layer Protocol Data Units) conforming to IEEE 802.15.4, etc.). In the present disclosure, operations performed by various devices to generate transmission / reception signals or to perform data processing or calculations in advance for transmission / reception signals may be performed by the processors 102 and 202 in FIG. 1. For example, examples of operations to generate transmission / reception signals or to perform data processing or calculations in advance for transmission / reception signals may include: 1) an operation of determining / obtaining / configuring / calculating / decoding / encoding bit information for fields included in a PPDU; 2) an operation of determining / configuring / obtaining time resources, frequency resources, etc. to be used for fields included in a PPDU; 3) an operation of determining / configuring / obtaining a specific sequence, etc. to be used for fields included in a PPDU; 4) a power control operation and / or a power saving operation to be applied to a device; and 5) an operation related to determining / obtaining / configuring / calculating / decoding / encoding an ACK signal, etc. Also, in the following example, various information (e.g., information related to fields / subfields / control fields / parameters / power, etc.) used by various devices for determining / obtaining / configuring / calculating / decoding / encoding transmitted / received signals may be stored in memory 104, 204 of FIG. 1.

[0033] In the UWB band, devices can access the medium based on the Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) mechanism. The CSMA / CA mechanism can perform Clear Channel Assessment (CCA), in which a device senses the wireless channel or medium for a predetermined time period before starting transmission. Sensing can be performed, for example, using an energy detection (ED) method based on a predetermined threshold. If the medium is determined to be idle as a result of sensing, the device starts transmission over the medium. On the other hand, if the medium is detected to be occupied or busy, the device does not start transmission, but can wait for a delay period (e.g., a random backoff period) for medium access before attempting transmission. By applying the random backoff period, multiple devices are expected to wait for different periods of time before attempting transmission, thereby minimizing collisions.

[0034] Furthermore, when a superframe structure is applied, a slotted CSMA-CA mechanism may be applied to data transmission in the contention access period (CAP) of the active portion of the inter-beacon interval, which is divided into the active portion and the inactive portion. The CSMA-CA mechanism may not be applied to data transmission in the active portion and the contention free period (CFP). When a superframe structure is not applied, an unslotted CSMA-CA mechanism may be applied to transmission of all data frames except for ACK frames in response to data request commands.

[0035] Ranging Measurement

[0036] Ranging involves measuring the distance between two devices, and a device with ranging capability can be referred to as a ranging-capable device (RDEV) or an enhanced ranging-capable device (ERDEV).

[0037] FIG. 2 is a diagram for explaining an HRP UWB PPDU format to which the present disclosure can be applied.

[0038] 2(a) to 2(g) show an encoding process of an HRP UWB PPDU. Through the encoding process, an HRP UWB PPDU having a format including a synchronization header (SHR), a PHY header (PHR), and a PHY payload field may be generated.

[0039] 2(a) shows a PHY service data unit (PSDU) received from a MAC via a PHY service access point (SAP). The PSDU may include a MAC PDU.

[0040] In Figure 2(b), Reed-Solomon encoding may be applied to the PSDU to generate a PHY payload field. The PHY payload field in Figure 2(b) is non-spread and corresponds to the state before convolutional encoding is applied.

[0041] In FIG. 2(c), a PHR field may be added before the PHY payload field. The PHR field may have a size of 19 bits, from bit 0 to bit 18. For example, bits 0 to 1 may correspond to a data rate field, bits 2 to 8 may correspond to a frame length field, bit 9 may correspond to a ranging field, bit 10 may be reserved, bits 11 to 12 may correspond to a preamble duration field, and bits 13 to 18 may correspond to a SECDED (single error correct, double error detect) field. The data rate field may indicate a data rate value applied to the PHY payload field. The frame length field may indicate the length of the PSDU. The ranging field may indicate whether the frame is an RFRAME (ranging frame). The preamble duration field may indicate the length (in symbols) of the SYNC field of the SHR.

[0042] In FIG. 2(d), convolutional encoding is applied to generate a coded PHY payload field, and in FIG. 2(e), spreading may be applied to the PHY payload field.

[0043] In Figure 2(f), an SHR may be added before the PHR, and the SHR field may include a SYNC field (or a preamble code) and an SFD (start-of-frame delimiter) field.

[0044] In Figure 2(g), modulation is applied to the SHR, PHR, and PHY payload fields, and the PPDU encoding procedure is completed. A basic coding rate may be applied to the SHR field. BPM-BPSK (burst position modulation-binary phase shift keying) with a coding rate of 850 kb / s or 110 kb / s may be applied to the PHR field. BPM-BPSK with a coding rate indicated by the PHR may be applied to the PHY payload field. For example,

[0045] FIG. 3 is a diagram for explaining the setting of an HRP UWB PPDU STS packet structure to which the present disclosure can be applied.

[0046] The scrambled timestamp sequence (STS) field may include a sequence of pseudo-randomized pulses. For example, the STS may include an advanced encryption standard (AES)-128-based pseudo-random pulse sequence, which may be utilized for accurate positioning in spread spectrum-based positioning technology in UWB communications.

[0047] The PPDU STS packet structure may be configured differently depending on whether or not the STS field is included and its location.

[0048] 3(a) shows the format corresponding to STS packet setting 0 (i.e., no STS field is present in the PPDU), which may be defined as mandatory.

[0049] 3(b) shows a format corresponding to STS packet setting 1 (i.e., the STS field is located immediately after the SFD field and before the PHR field). This format may be defined compulsorily.

[0050] 3(c) shows a format corresponding to STS packet setting 2 (i.e., the STS field is located after the PHY payload field). This format may be optionally defined.

[0051] Figure 3(d) shows a format corresponding to STS packet setting 3 (i.e., the STS field is located immediately after the SFD field, there is no PHR field, and there is no Data field (i.e., PHY payload field)). This format may be defined compulsorily.

[0052] The PPDU format illustrated in Fig. 3 may also be referred to as an HRP-ERDEV PPDU format. In Fig. 3, the arrows indicate the RMARKER (ranging marker) reference position in each format. The RMARKER can be the reference for timestamp measurement or a ranging counter.

[0053] For example, RMARKER may be defined as the time at which the beginning of the first symbol after the SFD of RFRAME is at the local antenna. The next higher layer can estimate the relative clock offset between the remote transmitting end and the local reference clock at the receiving end based on the reported RMARKER received ranging counter value for one or more STS segments.

[0054] The ranging counter supported by the RDEV corresponds to a set of behavioral properties and capabilities of the RDEV that calculates the ranging counter value. The ranging counter value is an unsigned integer and may be defined as a minimum of 32 bits long. The unit of the ranging counter is 2 of a 499.2 MHz chipping period for the HRP UWB PHY. -7is defined as approximately 15.65 picoseconds (ps), which is 20 times the basic chip rate of 1 MHz for the LRP UWB PHY. -20 It is defined as approximately 0.9537ps.

[0055] The ranging capability may be enabled in the RDEV using the MAC common part sublayer (MCPS)-DATA.request primitive and the MAC sublayer management entity (MLME)-RX-ENABLE.request primitive. A primitive may refer to a command or a set of parameters exchanged between entities of a layer or sublayer within a device. For example, an originator may request ranging capability using the MCPS-DATA.request primitive, and the ranging capability may be activated in the recipient by the MLME-RX-ENABLE.request primitive.

[0056] Ranging and Localization Method

[0057] Ranging and localization methods supported by RDEV and ERDEV may be based on time-stamping capabilities. The time-based methods SS-TWR (single-sided two-way ranging), DS-TWR (double-sided two-way ranging), and OWR / TDOA (one-way ranging / time difference of arrival) are described below.

[0058] FIG. 4 is a diagram for explaining a two-way ranging technique to which the present disclosure can be applied.

[0059] In the example of Figure 4(a), SS-TWR involves measuring the round-trip delay of a single message from one device to another and the response sent to the originating device. Device A initiates the message exchange, device B sends the response, and T_prop corresponds to the propagation time of the RMARKER between the devices.

[0060] Each device precisely measures the sending and receiving times of the message frame, which allows it to calculate T_round and T_reply by simple subtraction. The resulting TOF may be estimated as ^T_prop by the following formula:

[0061]

number

[0062] If a device can estimate the relative clock offset between itself and a remote device, it can improve the TOF accuracy by the following formula:

[0063]

number

[0064] Here, C_offs corresponds to the value measured by the receiver of device A relative clock offset between itself and the transmitter of remote device B.

[0065] In the example of Figure 4(b), DS-TWR corresponds to an extension of SS-TWR, and by using and combining two round trip times, it is possible to calculate a TOF result while reducing errors in the presence of uncorrected clock frequency offsets even if the response delay is long. Device A initiates the first round trip time measurement, device B responds to it, and then device B initiates the second round trip time measurement, device A responds to it, completing the entire DS-TWR exchange. T_prop corresponds to the propagation time of the RMARKER between devices.

[0066] Each device precisely measures the sending and receiving times of the message frame, which allows it to calculate T_round and T_reply by simple subtraction. The resulting TOF may be estimated as ^T_prop by the following formula:

[0067]

number

[0068] The example in Figure 4(c) corresponds to a reduction of the four-message DS-TWR in Figure 4(b) to three messages, i.e., the response of the first round trip time measurement may be used as the initiation message for the second round trip time measurement.

[0069] Next, we will explain the TDOA method. TDOA is a technique for locating wireless devices (e.g., radio frequency identification (RFID) devices) based on the relative arrival times of single or multiple messages. OWR may be used for TDOA. There are two cases for TDOA. In the first case, a message may be periodically broadcast by a mobile device, and the arrival times of the broadcasted message may be compared at multiple fixed nodes synchronized in a predetermined manner. In general, the message transmitted by the mobile device may be referred to as a blink. In the second case, multiple synchronized nodes may broadcast messages sequentially according to known transmission time offsets relative to each other. For any pair of fixed synchronized nodes, the difference in the arrival times of the blinks in the first case, or the difference in the arrival times of the broadcast messages received by the mobile device in the second case, will locate the mobile device on a hyperbolic surface. By combining the results from many such pairs, an intersection point between a set of hyperbolic surfaces may be derived, thereby locating the mobile device. In the second case, transmission offsets may be taken into account when calculating the difference in arrival times of messages from synchronized nodes.

[0070] RFID devices generally use blink messages that are as short as possible (e.g., general-purpose frames) to reduce power consumption. A general-purpose frame may be 12 octets long and may include a short frame control field, a sequence number field, but may not include a destination address field, an extended source address field, or a frame check sequence (FCS).

[0071] Synchronization of fixed nodes may be achieved by distributing clock signals over wires, or wireless synchronization techniques may be applied. UWB messages transmitted between fixed nodes (and known / pre-measured TOFs) can be used to calculate the relative clock frequency offset and drift between fixed nodes. This information may be used to correct the arrival times of blink messages to a common time base, making the TDOA data meaningful.

[0072] Setup procedure before ranging exchange

[0073] Disabling ranging to reduce power consumption may be defined as the default state. Enabling ranging in all RDEVs participating in a TWR exchange may be performed by higher layers. Also, when selective capabilities are used, it may be assumed that pre-defined coordination for preamble and channel selection occurs before the TWR exchange.

[0074] Finish-up procedure after lens replacement

[0075] At the end of the TWR exchange, each device may have transmit (TX) and receive (RX) ranging counter values ​​related to round trip time measurements or response times. To calculate the TOF, both of these values ​​are required at the node where the calculation is performed. Out-of-band (OOB) signaling, custom messages, ranging measurement information (RMI) information elements (IEs), etc. may be used for this purpose.

[0076] FIG. 5 is a diagram for explaining examples of formats of the RMI IE, RCPCS IE, RRMC IE, and RRTI IE to which the present disclosure can be applied.

[0077] FIG. 5(a) shows an example of the RMI IE format.

[0078] The RMI IE may be used to send one or more ranging-related measurements to one or more devices. The RMI IE content field may have a format as shown in the example of FIG. 5(a).

[0079] A value of 1 in the reply time present field indicates the presence of the RX-to-TX (or TX-to-RX) response time field in the respective RMI list element, while a value of 0 indicates its absence. The RX-to-TX (or TX-to-RX) response time may correspond to T_reply as described with reference to FIG. 4.

[0080] A value of 1 in the round-trip time present field indicates the presence of the TX-to-RX round-trip time field in the respective RMI list element, while a value of 0 can indicate its absence. The TX-to-RX round-trip time may correspond to T_round as described with reference to FIG. 4.

[0081] A value of 1 in the TOF present field may indicate that the TOF field is present in the respective RMI list element, while a value of 0 may indicate that it is not present.

[0082] A value of 1 in the AOA azimuth present field may indicate that the AOA azimuth field is present in the respective RMI list element, while a value of 0 may indicate that it is not present.

[0083] A value of 1 in the AOA elevation present field indicates that the AOA elevation field is present in the respective RMI list element, while a value of 0 can indicate that it is not present.

[0084] A value of 1 in the AOA FOM (figure of merit) present field indicates that if the AOA azimuth field is present, the AOA azimuth FOM field is present in the respective RMI list element, and if the AOA altitude field is present, the AOA altitude FOM field is present in the respective RMI list element, while a value of 0 can indicate that neither the AOA azimuth FOM field nor the AOA altitude FOM field is present.

[0085] The address size specifier field can specify the size (eg, 2 or 8) of the addresses used in the RMI list field.

[0086] A value of 0 in the deferred mode field indicates that the RMI IE is embedded in the RFRAME, and a value of 1 indicates that the RMI IE is included in a deferred message sent in the next measurement reporting phase.

[0087] The RMI list length field specifies the number of elements in the RMI list field. The fields contained in the RMI list field are as shown in Figure 5(a).

[0088] FIG. 5(b) shows an example of the RCPCS IE format.

[0089] The ranging channel and preamble code selection (RCPCS) IE may be used to signal channel selection and / or TX / RX preamble code selection for dynamic preamble code and channel selection (DPS). DPS may include modifying the long preamble to protect against attacking devices eavesdropping on ranging. The RCPCS IE content field may have a format as shown in the example of FIG. 5(b).

[0090] A value of 1 in the CCIP (CCI present) field indicates that the CCI field is present, and a value of 0 indicates that it is not present.

[0091] A value of 1 in the DDP (DPS Duration Present) field indicates that the DPS duration field is present, and a value of 0 indicates that it is not present.

[0092] A value of 1 in the PSP (preamble sequence selection present) field indicates that the preamble sequence selection fields, i.e., the TX preamble code field, the RX preamble code field, and the PSR (preamble symbol repetitions) field, are present, and a value of 0 indicates that they are not present.

[0093] The channel number field may indicate the UWB channel number for the upcoming ranging exchange.

[0094] The channel configuration interval (CCI) field may specify a channel configuration interval, which may correspond to the time in ranging scheduling time units (RSTUs) between transmission of this IE and reconfiguration for the specified channel.

[0095] RSTU is 416 chips (approximately 833.33ns) for HRP UWB PHY (416 chips = 416 / 499.2*10 6 ) RSTU corresponds to 1 microsecond (us) (= 1 chip at 1MHz base chip rate) for the LRP UWB PHY.

[0096] The DPS duration field may specify the effective time duration of the DPS, which may be specified in RSTUs for ERDEVs and in symbols for non-ERDEVs.

[0097] The TX Preamble Code field allows the sender of this IE to indicate the DPS preamble code to be used for transmission during the upcoming ranging exchange.

[0098] The RX Preamble Code field allows the sender of this IE to indicate the DPS preamble code to use for reception during the upcoming ranging exchange.

[0099] The PSR field may indicate the number of preamble symbol repetitions to be used for the SYNC of each RFRAME of the upcoming ranging exchange.

[0100] The MLMR-DPS.request and MLME-DPS.confirm primitives may be applied to the selective DPS mode of ranging. The ConfigTime parameter of the MLME-DPS.request primitive can be used to specify a future time to apply the preamble code and / or channel number. The time to apply the DPS changes may be exchanged via the CCI field of the RCPCS IE.

[0101] Basic Ranging Exchange

[0102] The recipient may have ranging turned on or enabled in the recipient's MAC based on an MLME-RX-ENABLE.request primitive from the next higher layer.

[0103] After ranging is turned on in the receiver MAC (ie, MLME-RX-ENABLE.request primitive received), every received RFRAME can generate TX / RX ranging counters.

[0104] The originator can send data to the recipient based on the MCPS-DATA.request primitive.

[0105] The receiver can generate ranging reports for every RFRAME and send an ACK frame to the originator.

[0106] The sender can receive an ACK frame from the receiver and activate a Tx-to-Rx turnaround (i.e., repeat data transmission and ACK reception), without the involvement of the next higher layer.

[0107] Ranging reports may include issuing an MCPS-DATA.confirm primitive on the originator side (i.e., reporting the result of an MCPS-DATA.request primitive invoke) and an MCPS-DATA.indication primitive on the receiver side (i.e., indicating receipt of data from the originator or indicating that ranging information is available via packet receipt from the originator).

[0108] The receiver may repeatedly generate ranging reports and send ACKs to the sender, activate Tx-to-Rx turnaround based on the sender's receipt of the ACK frame, and report ranging until ranging is disabled.

[0109] Ranging Procedure

[0110] First, the control of ranging and the transfer of results will be described.

[0111] Measurements may be exchanged between the RDEVs to complete the ToF calculation, and for this purpose, information elements may be used to control the TWR and to exchange ranging data between the RDEVs.

[0112] Specifically, information elements may be used to transfer ranging data and control TWR between RDEVs participating in a ranging exchange. For various ranging methods, measurement results by both devices may be combined to complete TOF calculations between RDEVs participating in a ranging exchange according to the required use case. That is, one device can transfer its ranging measurement results to another device. Information elements may be specified to provide a mechanism for controlling TWR and to support the transfer of ranging information between devices participating in a ranging exchange. A secure private data communication capability may be used to ensure the integrity of the information transfer.

[0113] The following describes a ranging procedure for SS-TWR that applies deferred response time results.

[0114] FIG. 6 illustrates an example message sequence chart for SS-TWR applying deferred response time results to which the present disclosure is applicable.

[0115] In the message sequence chart for ranging exchange, RRMC IE(0) may represent an RRMC IE containing a ranging control information field with a value of 0 (i.e., a ranging start message for SS-TWR). The Acknowledgment Request (AR) field in the MAC header may indicate whether an ACK is requested.

[0116] The next higher layer of the initiator may have enough information to calculate the TOF between the devices using the above formula upon receiving the RMI IE (eg, FIG. 5(a)).

[0117] The initiator initiates a ranging exchange by issuing an MCPS-DATA.request primitive to request ranging response time information and can send a ranging frame including an RRMC (Ranging Request Measurement and Control) information element that includes a ranging control information field.

[0118] FIG. 5(c) shows an example of the RRMC IE format.

[0119] The RRMC IE may include information for transmitting a ranging request and controlling the ranging procedure.

[0120] The response time request, round trip time request, TOF request, AOA azimuth angle request, and AOA altitude angle request fields of the RRMC IE format can indicate that the information is requested if their value is 1, and that the information is not requested if their value is 0.

[0121] The ranging control information field may have a value of 0 indicating that the frame is a ranging start message for SS-TWR, a value of 1 indicating that the frame is a response to a ranging start message for SS-TWR, a value of 2 indicating that the frame is a ranging start message for DS-TWR, and a value of 3 indicating that the frame is a continuing DS-TWR and indicates that a second round trip time measurement is to be started.

[0122] The address size field can specify the size of the addresses used in the RRMC address list field. If the value of the address size field is 0, all addresses in the RRMC address list element may correspond to short addresses. If the value of the address size field is 1, all addresses in the RRMC address list element may correspond to extended addresses.

[0123] The RRMC Address List Length field can indicate the number of addresses in the RRMC Address Lease field. If no addresses are provided (e.g., in the case of unicast ranging where the target device can be identified by the destination address in the MHR (MAC header)), the RRMC Address List Length field can be omitted.

[0124] If the RRMC IE is a broadcast message, the RRMC Address List Length and RRMC Address List fields may be omitted if the sender wishes to receive responses to the ranging request from all devices, or the RRMC Address List Length and RRMC Address List fields may be used to select a device set for response if the sender wishes to receive responses to the ranging request from a specific device (or device set).

[0125] In the case of SS-TWR, the initiator generally calculates the TOF, so the responder can request the TOF result by setting the TOF request field of the RRMC IE included in the response message.

[0126] In the case of DS-TWR, the responder generally calculates the TOF, so the initiator can request the TOF result by including an RRMC IE in the two messages sent to perform the DS-TWR exchange.

[0127] Multiple RRMC IEs may be included in one broadcast message if the initiator requests different information from multiple responders.

[0128] The RRMC Address List field may contain a list of addresses to which the RRMC IE is directed.

[0129] In association with the ranging report (or response ranging frame), the initiator side completes the round trip time measurement and the MCPS-DATA.confirm primitive can provide the initiator side with a ranging report that defines the round trip time. On the recipient side, the MCPS-DATA.indication primitive can provide the responder side ranging report that defines the response time to the round trip time measurement.

[0130] FIG. 5(d) shows an example of a Ranging Reply Time Instantaneous (RRTI) IE format.

[0131] In association with one or more frames including an RRMC IE with the response time request field set to 1, an RRTI IE may be included in the response frame to transmit the response time of the response frame.

[0132] The address size specifier field may be defined as follows:

[0133] [Table 1]

[0134] The RRTI list length field may indicate the number of elements in the RRTI list field. The RRTI list field may contain RRTI list elements.

[0135] The RX-to-TX response time field (reply time) of the RRTI list field may be set to a value indicating the difference between the transmission time of a reply RFRAME containing an RRTI IE and the reference time specified by an upper layer (i.e., T_reply in the example of FIG. 4(a)). The reference time may correspond to the reception time (RMARKER basis) of an RFRAME containing an RRMC IE with the response time request field set to 1.

[0136] The address field of the RRTI list field may be set to the address of the device that sends the RRMC IE requesting the response time. In unicast ranging, the address field may be omitted. In scheduled multi-node ranging, the address field may be omitted if the response times of different RDEVs are negotiated and ordered in advance.

[0137] In the following, we describe the ranging procedure for SS-TWR applying the embedded response time results.

[0138] FIG. 7 shows an example message sequence chart for SS-TWR with embedded response time results to which the present disclosure is applicable.

[0139] For SS-TWRs that apply response time results, ranging exchanges may be initiated by a ranging frame requesting ranging response time information and including an RRMC IE with the ranging control information field set to 0. The responding device can complete the round-trip measurement by sending a response frame with an embedded ranging reply time instantaneous (RRTI) IE. If the device has the capability to generate the RRTI IE, the number of messages required for ranging measurement can be minimized, thereby saving power. However, it may take time to calculate the arrival time of the received ranging message and prepare the RRTI IE value. In some cases, this time may be signaled in advance in an OOB manner, and the ranging reply time negotiation (RRTN) IE can provide a mechanism to indicate to the device its preferred response time, i.e., the time required to prepare a frame including the RRTI IE. When this time is known, the ranging-initiating device can expect a response message after a specific time and save energy by postponing turning on its receiver until that time. This may apply to both SS-TWR and DS-TWR ranging exchanges.

[0140] In Figure 7, RRMC IE(0) represents an RRMC IE containing a ranging control information field with a value of 0. The communication of the RRTN IE in the dotted box may occur at any convenient time before the ranging exchange is initiated, or the preferred response time information may be known in advance or exchanged out-of-band. Upon receiving the MCPS-DATA.indication primitive containing the responder's RRTI IE, the initiator's next higher layer may have sufficient information to calculate the TOF between both devices according to the formula described above.

[0141] In the following, the ranging procedure for SS-TWR with a fixed response time is described.

[0142] FIG. 8 shows an example of a message sequence chart for SS-TWR using a scrambled timestamp sequence packet configuration option three (SP3) packet to which the present disclosure can be applied.

[0143] If the responding device has precise control over the transmission time of its response message relative to the arrival time of the ranging initiation message, the response time (i.e., Treply) may have a fixed, known value agreed upon between the devices participating in the ranging exchange. In this case, it may not be required to embed Treply in the response message or send it separately in an additional message. The accuracy of the resulting ranging may depend on how precise the responding device has control over the transmission time of its response message. For example, a 1 ns error in TOF may correspond to a ranging error of approximately 30 cm.

[0144] HRP-ERDEV PPDU format SP3 may be used for the fixed response time case.

[0145] In the example of Figure 8, the initiation message in the dotted box can represent a communication between the devices to agree on and coordinate the use of SP3 packets and all other parameters necessary to allow communication to proceed. Although only a single message is shown in the example of Figure 8, there may be a series of messages in each direction to agree on all parameters. For example, the RRNT IE may be used to agree on a fixed response time.

[0146] The next higher layer in each device can use the MLME-STS.request primitive to configure the SP3 packet format and set personal area network information base (PIB) attributes (e.g., phyHrpUwbStsKey, phyHrpUwbStsVCounter, phyHrpUwbStsVUpper96, etc.) in all of the devices to configure the appropriate behavior. If the higher layer selects the SP3 packet configuration, subsequent MCPS-DATA primitives will be associated with the SP3 packet until the higher layer changes the packet configuration using the MLME-STS.request primitive.

[0147] The MCPS-DATA.request primitive may be used to initiate a ranging exchange; in this mode, the PPDU may not carry MAC data. Although not shown, the invocation of the MLME-RXENABLE.request primitive can be assumed to turn on the receiver at the appropriate time to receive the PPDU. Since the PHY is configured for SP3 packets, the PHY informs the MAC layer of the reception of the PPDU at the end of the scrambled timestamp sequence (STS). Similarly, the MAC, knowing the SP3 configuration, can deliver the RxRangingCounter value of the RangingReportDescriptor parameter of the MCPS-DATA.indication primitive. Also, assuming the RangingStsForm of the RangeReportDescriptor is acceptable, the upper layer can initiate a response by invoking the MCPS-DATA.request primitive specifying the RangingTxTime according to the agreed-upon fixed response time.

[0148] Once the SP3 packet response is received at the initiating device, and assuming again that the RangingStsFom in the RangingReportDescriptor parameter of the MCPS-DATA.indication primitive is acceptable, the initiator may have enough information to calculate the TOF between the devices using the above formula based on the known fixed response time.

[0149] The ranging exchange may be repeated multiple times until the higher layers reach a mutual agreement. To resume PHY and MAC data interaction, the next higher layer can use the MLME-STS.request primitive to restore the STS packet settings to values ​​that allow that data interaction. This is shown in the last dotted box in Figure 8.

[0150] LRP-REDEV can again support challenge-response ranging that applies a fixed response time to eliminate the need for data messages that carry the response time.

[0151] In the following, the DS-TWR ranging procedure is described in which the deferred response time information is applied.

[0152] FIG. 9 illustrates an example message sequence chart for DS-TWR with deferred response time information to which the present disclosure is applicable.

[0153] The DS-TWR may essentially include the completion of the SS-TWR exchange initiated by each device and the resulting combination. The DS-TWR may be initiated by the next higher layer transmitting a ranging data frame carrying an RRMC IE with the value of the ranging control information field set to 2 (i.e., RRMC IE(2)). Such a frame and its ACK may define the first round-trip time measurement. The RRMC IE transmission in the MCPS-DATA.indication primitive may inform the next higher layer to initiate a second round-trip time measurement by transmitting a data frame in the other direction. Such a data frame may include an RRMC IE with the value of the ranging control information field set to 3 (i.e., RRMC IE(3)) to indicate continuation of the exchange, and the response time request and round-trip time request fields may both be set to 1 to request the response time and the result of the first round-trip time measurement. The ACK for this message may complete the second round-trip time measurement. Subsequent messages from the initiator may carry the first round trip time measurement result and the response time of the second round trip time measurement using an RMI IE. When the responder receives the second MCPS-DATA.indication primitive (containing an RMI IE), it may have enough information to calculate the TOF between the devices using the formula described above. Subsequent reporting of the ranging results to the initiator using an RMI IE may be performed according to the value of the TOF request field in the initiating RRMC IE.

[0154] In the following, the DS-TWR ranging procedure applying embedded ranging time information is described.

[0155] FIG. 10 shows an example of a message sequence chart for DS-TWR to which embedded ranging time information to which the present disclosure can be applied is applied.

[0156] For the three-message DS-TWR exchange of Figure 4(c) described above, it is required that the initiator be able to embed the response time as part of completing the second round trip time measurement. In the example of Figure 10, the DS-TWR may be initiated by an RFRAME carrying an RRMC IE with the TOF request field set to 0 (i.e., no ranging report is requested by the initiator) and the Ranging Control Information field set to 2 (i.e., RRMC IE(2)).

[0157] The responder can complete the first round trip time measurement and start the second measurement using an RFRAME carrying an RRMC IE with the Ranging Control Information field set to 3 (i.e., RRMC IE(3)) to indicate the continuation of the exchange. In this RRMC IE, the Response Time Request and Round Trip Time Request fields are both set to 1, requesting the result of the first round trip time measurement and the response time for the second round trip time measurement. The initiator can complete the exchange by sending a final RFRAME containing the first round trip time result in the RMI IE and the response time for the second round trip time measurement in the RRTI IE.

[0158] When the responder receives the second MCPS-DATA.indication primitive, it may have enough information to calculate the TOF between the devices using the formula above. If the initiator of the ranging exchange wishes to receive the results, it can set the TOF request field in the initiating RRMC IE to a value that requests the responder to send the results in the RMI IE of subsequent messages at the end of the exchange.

[0159] Below we describe another procedure for arbitration of RDEV and ERDEV.

[0160] When STS is used, successful HRP-ERDEV interoperation requires that the transmitter and receiver be aligned on the seeds (i.e., STS key and data values ​​V) used to generate the STS at the transmitter and to generate a sequence for correlation with the received STS at the receiver. Secure personal data communication capabilities may be used to reconcile these values, and the seeds may be transferred between devices using the Ranging STS Key and Data (RKSD) IE. The counter value in the RSKD IE may relate to the current packet or future packets, as indicated by the CP (current packet) field of the IE. Upper layers can use the received RSKD IE information (e.g., via PIB attributes such as phyHrpUwbStsKey, phyHrpUwbStsVUpper96, and phyHrpUwbStsVCounter) to appropriately set the STS seeds for sending and receiving future packets. The header IE version of the RSKD IE may be used to synchronize the STS generator with the information sent with the secured payload IE and data.

[0161] When a frame containing the RSKD IE header IE is received, the IE may be conveyed to the next higher layer to set attributes such as phyHrpUwbStsKey, phyHrpUwbStsVUpper96, and phyHrpUwbStsVCounter appropriately for STS generation. If the frame containing the RSKD IE header IE cannot pass the encoding security processing, for example, if the receiver does not have the key to validate the message integrity code (MIC), the RSKD IE may be conveyed to the next higher layer in the HeaderIeList parameter of the MLME-COMM-STATUS.indication primitive.

[0162] Multi-node Ranging

[0163] Multi-node ranging may involve ranging between two or more devices, each of which may play a role in multi-node ranging.

[0164] FIG. 11 is a diagram for explaining the roles of devices in a ranging procedure to which the present disclosure can be applied.

[0165] A controller may correspond to an ERDEV that transmits a ranging control message (RCM) and defines ranging parameters. The RCM may correspond to a data frame including an advanced control (ARC) IE. A controlee may correspond to an ERDEV that uses ranging parameters provided by the controller using the RCM. An initiator corresponds to an ERDEV that sends the first ranging message after the RCM and starts a ranging exchange, and the controller or the controlee may be the initiator. A responder corresponds to an ERDEV that responds to a ranging initiation message received from the initiator, and the controller or the controlee may be the responder.

[0166] The next layer above the controller can determine the ranging parameters and the role of the ERDEV participating in the ranging exchange (ie, initiator or responder).

[0167] For example, Figure 11(a) shows an example in which a controller that transmits a ranging control message (RCM) is an initiator that transmits a ranging initiation message in a ranging exchange, and a controllee that receives the RCM is a responder that receives the ranging initiation message in a ranging exchange and transmits a ranging response message. Figure 11(b) shows an example in which a controller that transmits an RCM is a responder that receives the ranging initiation message in a ranging exchange and transmits a ranging response message, and a controllee that receives the RCM is an initiator that transmits a ranging initiation message in a ranging exchange.

[0168] A ranging session may be defined as a group of ERDEVs participating in a consecutive ranging procedure configured by an initial set of ranging parameters. A ranging session may include a single controller and one or more initiators. The controller can set the initial ranging parameters and can update the parameters during the ranging session.

[0169] FIG. 12 shows examples of formats of the ARC IE, RDM IE, RBU IE, RR IE, and SRRE IE to which the present disclosure can be applied.

[0170] FIG. 12(a) shows an example of the ARC IE format.

[0171] The controller can use the ARC IE to transmit ranging configuration information to the controllee. The ARC IE may be transmitted to one controller via a unicast frame and to multiple controllers via a broadcast frame.

[0172] The controllee can use the ARC IE to send its preferred ranging parameters to the controller along with a Ranging Change Request (RCR) IE.

[0173] Each field of the ARC IE may be defined as follows:

[0174] [Table 2]

[0175] [Table 3]

[0176] [Table 4]

[0177] [Table 5]

[0178] The contention-based ranging type corresponds to a method in which the controller does not know the existence or number of controlees, and therefore the ERDEV performs contention-based ranging. Because collisions may occur, higher layers may be required to filter inaccurate or erroneous ranging results. The initiator or responder may compete to transmit within the appropriate time slot. If the initiator and responder compete, a ranging contention phase structure (RCPS) IE may be added to the ARC IE, and different phases (e.g., distinguished by slot index) may be specified in the RCM. Upon receiving the RCM, the controlee knows that it has been selected to participate in the ranging round. The time-scheduled ranging type corresponds to a method in which the controller knows all controlees and specifies the exact schedule for ranging transmission. The controller can select devices to participate in ranging, assign ranging roles (i.e., initiator or responder), and allocate time slots using the ranging device management (RDM) IE. If the device role and transmission schedule are specified in advance by an OOB signaling method, the RDM IE may be omitted.

[0179] [Table 6]

[0180] [Table 7]

[0181] The RCM validity rounds field indicates the number of consecutive ranging rounds controlled by the RCM, which may be used to define a ranging round set. The MMRCR (multiple message receipt confirmation request) field may indicate whether multiple message receipt confirmation is requested.

[0182] The content control field may indicate whether other fields are present in the ARC IE. Bits 0, 1, 2, and 3 of the content control field correspond to a field indicating the presence or absence of a ranging block duration (RBD) field (i.e., RBDP), a field indicating the presence or absence of a ranging round duration (RRD) field (i.e., RRDP), a field indicating the presence or absence of a ranging slot duration (RSD) field (i.e., RSDP), and a field indicating the presence or absence of a session ID field (i.e., SIP), respectively. Bits 4 to 7 of the content control field may be reserved.

[0183] The RBD field may indicate the duration (in RSTU units) of the ranging block.

[0184] The RRD field can indicate the duration of the ranging round (ranging slot unit, ie, the number of ranging slots in the ranging round).

[0185] The RSD field may indicate the duration (in RSTUs) of the ranging slot.

[0186] The SID field can indicate a unique identifier for each controller.

[0187] If the ranging block structure is the same as the previously specified duration, one or more of the duration fields (e.g., RBD field, RRD field, RSD field) may not be present in the ACI IE of the current RCM. In this case, other fields (e.g., Schedule Mode field, STS Packet Configuration field, etc.) may still be used to update the corresponding ranging parameters.

[0188] FIG. 12(b) shows an example of a ranging device management (RDM) IE format.

[0189] The RDM IE may be used by the controller to exchange scheduling information between ERDEVs for a set of ranging rounds specified in the same RCM.

[0190] The SIU (slot index usage) field can indicate whether to use the slot index of the RDM list element. If its value is 0, the RDM IE can be used to assign a ranging role (i.e., initiator or responder) to the controllee for contention-based ranging. If its value is 1, the RDM IE can be used to allocate a time slot and assign a ranging role to the controllee for scheduling-based ranging.

[0191] The Address Size field indicates the size of the address used in the RDM list field, where 0 indicates that a short address (16 bits) is used and 1 indicates that an extended address (64 bits) is used.

[0192] The RDM list length field can indicate the number of RDM list elements.

[0193] The ranging role field of the RDM list can indicate the initiator or responder, the ranging slot index field of the RDM list can indicate the slot index assigned to the device at that address, and the address field of the RDM list can indicate the address of each device participating in ranging.

[0194] FIG. 12(c) shows an example of the RBU (ranging block update) IE format.

[0195] The RBU IE may be used by the controller to inform the controlee of an updated ranging block structure.

[0196] The relative ranging block index field may indicate the number of remaining ranging blocks in the current configuration before switching to the new configuration.

[0197] The updated block duration field may indicate the duration (in RSTU units) of the new ranging block.

[0198] The updated ranging round duration field can indicate a ranging round duration value that is an integer multiple of the ranging slot duration within the new ranging block structure.

[0199] The updated ranging slot duration can indicate the duration (in RSTUs) of the ranging slot within the new ranging block structure.

[0200] FIG. 12(d) shows an example of a Ranging Round (RR) IE format.

[0201] The ranging block index field may indicate the index of the ranging block.

[0202] The hopping mode field may indicate whether or not a hopping mode for a ranging block is supported.

[0203] The round index field can indicate a ranging round index within a ranging block.

[0204] The transmission offset field may indicate the value (in RSTUs) of the transmission offset of the ranging round within the block. The transmission offset may have a maximum value of the maximum slot duration minus the packet duration.

[0205] For the current ranging round (i.e., ranging round in the ranging block with block index i), the RR IE may be included in the RCM of the ranging block with block index i. In this case, the RR IE may correspond to information that helps the ERDEV synchronize with the block structure.

[0206] When the last message of the current ranging round (i.e., ranging block with block index i) is sent from the controller to the controllee for the next ranging round (i.e., ranging round at the next ranging block with block index i+1), an RR IE may be sent in the final message to inform ranging round information for the ranging block with block index i+1.

[0207] When the last message in the current ranging round (i.e., ranging block with block index i) is sent from the controlled party, the controller can send an RR IE in the RCM of the next ranging block with block index i+1 to inform ranging round information for the ranging block with block index i+2.

[0208] In this case, the RCM for the ranging block with block index i+1 may include two RR IEs: one RR IE applies to the ranging round of the ranging block with block index i+1, and the other RR IE applies to the ranging round of the ranging block with block index i+2.

[0209] FIG. 12(e) shows an example of the SRRR (SP3 ranging request reports) IE format.

[0210] The SRRR IE may be used to request reporting of AOA and / or response time and / or round trip time measurements from a requestor to a provider.

[0211] The requestor address size specifier field and the provider address size specifier field may each have a value of 00, 01, 10, or 11 as shown in Table 1 above, indicating that no address exists, or that a short address (16 bits) or an extended address (64 bits) is to be used.

[0212] The RAOA (report of AOA) field can indicate whether or not to request a report to the AOA.

[0213] The RRT (report of reply time) field can indicate whether or not to request a report on the response time.

[0214] The RRTT (report of round-trip time) field can indicate whether or not to request a report on the round-trip time.

[0215] The RTOF (report of TOF) field can indicate whether to request a report for TOF.

[0216] The requestor address field may be set to the address of the device that transmits the signal to be measured or initiates ranging for the AOA.

[0217] The provider address field may be set to the address of the device measuring the AOA.

[0218] Ranging blocks and round structures

[0219] FIG. 13 is a diagram for explaining a ranging block structure and ranging phases to which the present disclosure can be applied.

[0220] In FIG. 13(a), a ranging block is a time interval for performing ranging, and one ranging block may include N ranging rounds.

[0221] A ranging round corresponds to a time sufficient for ERDEVs participating in a ranging exchange to complete a ranging measurement cycle, and one ranging round may include M ranging slots.

[0222] A ranging slot may correspond to a time sufficient for the transmission of one or more RFRAMEs.

[0223] The slot duration and the number of slots included in the ranging round may be different between ranging rounds. To this end, the controller can send an RCM to the controllee to change the ranging round settings.

[0224] A ranging control message (RCM) is the first message sent by a controller and may be sent in the first slot of a ranging round. The RCM may include configuration information for ranging parameters.

[0225] The ranging control update message (RCUM) corresponds to a message sent by the controller in the last slot of the ranging round specified by the RCM to update the ranging parameters for the next ranging round. The IE included in the RCM for the ranging parameter update may be included in the RCUM.

[0226] A ranging interval update message (RIUM) corresponds to a message sent by a controller to update the interval between ranging blocks and to help synchronize participating ERDEVs. The RIUM contains the scheduled time of the first RIUM, and the RIUM may contain the scheduled time of the next RIUM (if used) before the start of the next ranging block.

[0227] FIG. 13(b) explains the phases in the ranging procedure.

[0228] The RCP (ranging control phase) corresponds to the phase in which the controller transmits the RCM.

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

[0230] RIP corresponds to the phase in which an initiator sends a ranging start message to a responder.

[0231] The RRP corresponds to the phase in which the responder sends a response message to the initiator.

[0232] The RFP corresponds to the phase in which the initiator sends a ranging final message to the responder, and may be used only in DS-TWR.

[0233] The MRP (measurement report phase) corresponds to a phase in which participating ERDEVs exchange service information related to ranging measurements.

[0234] The ranging control update phase (RCUP) corresponds to the phase in which the controller sends an RCUM, and if an RCUP exists, the phase may be located in the last slot of the ranging round set specified by the RCM.

[0235] The RIUP (ranging interval update phase) corresponds to the phase in which the controller transmits the RIUM.

[0236] FIG. 14 is an example timing diagram for various multiple device ranging applications to which the present disclosure is applicable.

[0237] Figure 14(a) corresponds to an example of OWR, Figure 14(b) corresponds to an example of SS-TWR, Figure 14(c) corresponds to an example of a combination of RCP and RIP in SS-TWR, Figure 14(d) corresponds to an example of DS-TWR, Figure 14(e) corresponds to an example of many-to-many SS-TWR, and Figure 14(b) corresponds to an example of many-to-many DS-TWR.

[0238] The ranging mode will be described below.

[0239] In interval-based mode, the average time of the ranging round is variable and a time structure may be applied along with adaptive spacing.

[0240] In the block-based mode, the average time of the ranging round is constant, i.e., ranging blocks with the same duration may be repeated in the block-based mode.

[0241] The ranging mode selection may be based on the OOB mechanism or the time structure indicator field in the ARC IE.

[0242] FIG. 15 shows a timing diagram for one example of a block-based mode to which the present disclosure can be applied.

[0243] In the block-based mode, the ranging block structure can use a structured timeline. The ranging block structure setup may include specifying the ranging block duration (RBD), ranging round duration (RRD), and ranging slot duration (RSD) based on the corresponding fields of the ARC IE.

[0244] The number of ranging rounds corresponds to the value obtained by dividing the ranging block duration by the ranging round duration.

[0245] The number of ranging slots corresponds to the value obtained by dividing the ranging round duration by the ranging slot duration.

[0246] Upon receiving the RCM, the ERDEV can set the associated timeline for ranging based on the initial ranging block structure and the values ​​of the fields in the ARC IE. The ranging block structure may be set up and / or fixed by the next higher layer.

[0247] The ranging block structure may be repeatedly transmitted by the controller in every RCM (e.g., by an ARC IE). If a change or update to the ranging block structure (i.e., a new ranging block duration, ranging round duration, and / or ranging slot duration) is required, the controller may transmit an RBU IE for the new configuration. The RBU IE may be transmitted in the final data frame of an RCM or ranging message sequence. Each time an RBU IE is transmitted, the controller may decrement the Relative Ranging Block Index by 1 until it reaches 0. This may indicate whether the next block will use the new configuration and whether the RCM ARC IE of the next block will include the new configuration.

[0248] The following describes indexing.

[0249] For ranging blocks, the first ranging block is given a block index of 0, and relative block indexes for the remaining blocks are determined using block index 0 as a reference.

[0250] For ranging rounds, if one ranging block contains N ranging rounds, the round index for the first ranging round in the current ranging block is given as 0, and relative round indices (e.g., 1, ..., M-1) for the remaining N-1 rounds are determined using round index 0 as a reference.

[0251] For ranging slots, if one ranging round contains M ranging slots, the slot index for the first ranging slot in the current ranging round is given as 0, and the slot index (e.g., 1,...,M-1) relative to the remaining M-1 slots is determined using slot index 0 as a reference.

[0252] A new ranging message exchange may be sent / received as the first RCM in the ranging slot with index 0 of the ranging round with index 0 of the ranging block with index 0. That is, an RCM packet may be sent at the start of the first ranging slot of the first ranging round. The RCM may include an RR IE to inform information related to the ranging round in the current ranging block.

[0253] FIG. 16 is a diagram illustrating examples of various transmission offsets to which the present disclosure can be applied.

[0254] The RR IE included in the RCM may include transmission offset information as information related to the ranging round in the current ranging block. In subsequent ranging rounds, the controller may start transmission in each slot based on different transmission offsets. The transmission offset may have a value smaller than the value obtained by subtracting the UWB packet duration from the ranging slot duration. The transmission offset may be expressed as a multiple of RSTU.

[0255] The transmit offset may be applied to the ranging round, i.e., the same transmit offset may be applied to all packet transmissions included in the same ranging round. The next higher layer of the controller may select the transmit offset and communicate this to all other devices using the RR IE. The controller may also change the transmit offset for each ranging round based on power to reduce interference.

[0256] One-to-Many Ranging Procedure

[0257] FIG. 17 shows an example of a message sequence chart for one-to-many SS-TWR to which the present disclosure can be applied.

[0258] In the ranging procedure for one-to-many TWR, the ranging exchange is initiated by an initiator sending an RRMC IE, which may be included in a ranging initiation message broadcast to multiple responders.

[0259] An RRMC IE with the ranging control information field set to 0 (i.e., RRMC IE(0)) may be sent as an SS-TWR ranging start message. To request a response time from the responding ERDEV, the response time request field of the RRMC IE may be set to 1.

[0260] The RRMC IE carried in the MCPS-DATA.indication primitive in each of Responder-1 to Responder-N can signal the next higher layer to perform a ranging response. Each of the Responders can insert the RequestRrtiTxList parameter into the RRTI IE (as a response to the response time request of the RRMC IE) and send an RRMC IE with the ranging control information field set to 1 (i.e., RRMC IE(1)) to the initiator. Here, the response RFRAME can be sent to the initiator in a unicast manner.

[0261] Once the initiator receives each ranging response frame, it may have enough information to be able to calculate the TOF of that responder.

[0262] The Final Message Broadcast by the initiator may include one or more RMI IEs for measurement reporting (if requested by the RRMC IE). Multiple RMI IEs may distinguish associated devices by their address fields. For example, Responder-1 may set the TOF Request field in the RRMC IE to 1, and Responder-N may set the Round Trip Time Request field in the RRMC IE to 1. When multiple Responders request the same information set, such as TOF, measurement reporting from the initiator may be performed by one RMI IE in the Final Data message.

[0263] FIG. 18 shows an example of a message sequence chart for SP3 point-to-multipoint SS-TWR to which the present disclosure can be applied.

[0264] At the initiation of a ranging round, the RCM can send ranging configuration information and related IEs. The SRRR IE(I,R_1) can have the RAOA and RRTT fields set to 1 if the Responder-1 requests the AOA and round trip time from the initiator side.

[0265] Multi-node SP3 ranging may be based on scheduling (ie, each time slot is assigned for use in a particular ERDEV) specified by the next higher layer of the controller.

[0266] The RDM IE in the RCM may include information that assigns time slots and device roles within the ranging round. The ARC IE specifies the ranging procedure and the SP3 packet format so that the next higher layer above the ERDEV can recognize the start and end of the SP3 ranging phase and invoke the MLME-STS primitive to enable / disable SP3 packets before / after the ranging phase.

[0267] The RCM may include an RSKD IE for exchanging portions of the STS seed for initializing STS generation between participating ERDEVs. According to the scheduling information of the ranging transmission, the STS counter values ​​of the participating ERDEVs may be set appropriately for sending and receiving SP3 packets.

[0268] During the SP3 ranging phase, the next higher layer can use MLME-STS.request to configure both sides appropriately to select the SP3 packet format and set the correct values ​​for the phyHrpUwbStsKey, phyHrpUwbStsVUpper96, and phyHrpUwbStsVCounter attributes. Because ranging scheduling is specified by the RCM preceding SP3 ranging, the devices already know the participants. Each time slot may be assigned to a specific (E)RDEV.

[0269] In the measurement reporting phase, the initiator can send the AOA and round trip time to responder-1 using RMI IEs. Responder-1 to responder-N can each embed the requested response time in the RMI IE sent to the initiator.

[0270] As another example, in the SP3 ranging phase of the message sequence for SP3 point-to-multipoint DS-TWR, after the initiator receives an SP3 frame as a ranging response message from each responder, it can send an SP3 frame as a ranging complete message to each responder, thereby conveying the local value of the initiator's TxRangingCounter to each responder. In the measurement reporting phase, the initiator can send an RMI IE including the response time and round trip time to the responder, and in response, each responder can send an RMI IE including the AOA to the initiator.

[0271] Improved ranging block structure

[0272] FIG. 19 is a diagram illustrating the difference in time structure between a single application and a combination of various applications to which the present disclosure can be applied.

[0273] In the existing ranging block structures described with reference to Figures 13 and 15, ranging blocks of the same length are repeated. To support various applications, a new time structure in which different blocks are mixed is required. For example, for ranging and DL-TDOA, a new time structure in which ranging methods based on different numbers of slots are mixed can be considered. To define a flexible time slot that can accommodate this, it is necessary to allow ranging blocks and ranging rounds to have different durations.

[0274] The example in FIG. 19(a) corresponds to an example of an indoor localization use case, and blocks of the same structure may be repeated.

[0275] In the case of a public transportation use case such as the example in Figure 19(b), DL-TDOA operation is required for positioning when the user approaches a subway gate, ranging operation is required when the user selects a particular gate, and contention for access is required when the user first approaches the gate.

[0276] In the example of Figure 19(a), the ranging time structure for a single application (e.g., indoor positioning) has the same block duration, while in the example of Figure 19(b), in a public transportation use case requiring a combination of multiple applications (e.g., DL-TDOA, ranging, contention), supporting different block durations enables more efficient positioning and ranging. The ranging time structure (e.g., scheduling information such as duration for ranging block / ranging round / ranging slot for configuration) for each application included in the example of Figure 19(b) may be different, and it is necessary to define a higher-level time structure to accommodate this as a single service.

[0277] Thus, unlike existing UWB wireless networks, which only define time structures with fixed lengths, it is necessary to define a new time structure that supports various block durations with flexible lengths.

[0278] Various examples of the present disclosure for flexible time structures are described below.

[0279] FIG. 20 is a diagram for explaining the operation of the first device according to the present disclosure.

[0280] 20, the first device may correspond to a controller, and the second device may correspond to a controlee, and the first device and the second device may correspond to ERDEVs.

[0281] In step S2010, the first device may generate an IE including a list of devices associated with the ranging block.

[0282] A ranging block may be one of one or more ranging blocks in each hyperblock. As described below, a hyperblock may represent a time structure including blocks of different durations. For example, each hyperblock may include multiple ranging blocks of different durations. A ranging block may include multiple ranging rounds of the same duration. A ranging round may include multiple slots of the same duration.

[0283] The generated IE may further include a ranging block index field set to a value specifying / identifying an index of a ranging block within a hyperblock. The device list (or device list field in the IE) may include addresses for one or more devices assigned to the ranging block (e.g., one or more ranging rounds within the ranging block) identified by the ranging block index field included in the IE. That is, the device list may also be referred to as an address list field.

[0284] Additionally, the generated IE may further include a length field for the address list field, which may be set to a value indicating the number of addresses (or devices) included in the address list field.

[0285] In this way, the block index field and the device list (or address list field) may be associated within one IE. For example, an IE may include multiple sets (or elements) of a block index field, an address length field, and an address list field. For example, an IE may include a first element including a first ranging block index field, a first address length field, and a first address list field, and a second element including a second ranging block index field, a second address length field, and a second address list field. The first address list field in the first element may indicate the address of a device assigned to the block indicated by the first ranging block index field. The second address list field in the second element may indicate the address of a device assigned to the block indicated by the second ranging block index field.

[0286] In step S2020, the first device may transmit a frame including the generated IE to one or more second devices.

[0287] The time point at which a message / frame including the IE is transmitted (hereinafter referred to as the block allocation schedule information transmission time point) may be predefined (or fixed) or may be determined through negotiation between the controller and the controlee. Examples of the block allocation schedule information transmission time point include the following:

[0288] A frame including the IE may be included in all RCMs in each hyperblock and transmitted (or advertised). Additionally or alternatively, a frame including the IE may be included in part of all RCMs in each hyperblock and transmitted (or advertised). The time at which an RCM is transmitted within a hyperblock may be part or all of a ranging round included in part or all of the ranging blocks in the hyperblock, and the RCM may be transmitted in the first slot of the ranging round.

[0289] Additionally or alternatively, a frame containing the IE may be transmitted (or advertised) in the first ranging round of each ranging block within each hyperblock (i.e., at the start of each ranging block). Additionally or alternatively, a frame containing the IE may be transmitted (or advertised) in the first ranging round of the first ranging block within each hyperblock (i.e., at the start of each hyperblock).

[0290] The durations of the ranging blocks within each hyperblock may differ from one another, and therefore the time intervals between the times at which frames containing the IE are transmitted may differ. From a hyperblock-based perspective, the set of intervals between the times at which the frames are transmitted may be repeated.

[0291] In the above example, some or all of the values ​​of the fields of the IE transmitted at different times may be the same or different.

[0292] The method described in the example of Figure 20 may be performed by the first device 100 of Figure 1. For example, one or more processors 102 of the first device 100 of Figure 1 may be configured to generate an IE including a device list associated with a ranging block and transmit a frame including the IE to one or more second devices. Note that one or more memories 104 of the first device 100 may store instructions for performing the method described in the example of Figure 20 or in the examples described below when executed by the one or more processors 102.

[0293] FIG. 21 is a diagram for explaining the operation of the second device according to the present disclosure.

[0294] In step S2110, the second device may receive a frame from the first device that includes an IE that includes a list of devices associated with the ranging block.

[0295] The device list, the IE containing it, and the specific contents of the frame containing the IE are the same as those explained in the example of FIG. 20, and therefore a duplicated explanation will be omitted.

[0296] In step S2120, the second device may determine that the ranging block is to be allocated to the second device based on the second device being included in the device list.

[0297] Alternatively, if the second device is not included in the device list, it can be determined that the ranging block is not allocated to the second device.

[0298] For example, the second device may operate in an active mode in a block (or one or more rounds within that block) assigned to it within a hyperblock, and may operate in a sleep mode (or in an inactive mode) in a block (or one or more rounds within that block) not assigned to it.

[0299] The method described in the example of Figure 21 may be performed by the second device 200 of Figure 1. For example, one or more processors 202 of the second device 200 of Figure 1 may be configured to receive a frame from a first device that includes an IE containing a list of devices associated with a ranging block, and determine that the ranging block is allocated to the second device based on the second device being included in the device list. Note that one or more memories 204 of the second device 200 may store instructions for performing the method described in the example of Figure 21 or in the examples described below when executed by the one or more processors 202.

[0300] 20 and 21 may correspond to some of various examples of the present disclosure. Various examples of the present disclosure, including the examples of Fig. 20 and 21, will be described in more detail below.

[0301] [Embodiment] In the embodiments described below, HBS IE will be used as a representative name of an information element that supports a flexible time structure, but the embodiments described below may also be applied in the same way when an IE with a name other than HBS IE includes some or all of the various information described in this disclosure.

[0302] Example 1

[0303] FIG. 22 shows an example of a time structure in the hyperblock-based mode according to the present disclosure.

[0304] In the example of FIG. 22(a), a hyperblock may correspond to a group of blocks. The hyperblock-based mode may allow a group of blocks having different settings (e.g., block duration, round duration, slot duration, etc.). The hyperblock may be based on an interval-based mode or a block-based mode. Different hyperblocks may have the same settings or different settings.

[0305] As shown in the example of FIG. 22(b), information regarding the settings for the hyperblock structure may be repeatedly transmitted by the controller in the RCM (or the frame including the block allocation schedule information described above). For this purpose, a hyperblock structure (HBS) IE may be defined. For example, the HBS IE may include an index of the block, a block duration for each of all blocks included in the hyperblock, a list of controlees corresponding to each block, etc. A controlee that receives the HBS IE included in the RCM (or the frame including the block allocation schedule information described above) knows that the hyperblock structure is applied / progresses and knows which block it will operate on.

[0306] To implement the hyperblock-based mode, the controller can transmit an RCM including an HBS IE (or a frame including the block allocation schedule information described above) to configure a hyperblock for the controllee. The message / frame including the HBS IE may be transmitted at the time of transmitting the block allocation schedule information described above. For block configuration, an ARC IE may be further included in the RCM (or a frame including the block allocation schedule information described above) for the block.

[0307] As described above, the hyperblock-based mode may be implemented based on the block-based mode or the interval-based mode. When implemented based on the interval-based mode, the controller can use the RIU IE to specify the interval between the start points of blocks having the same index in each hyperblock. For example, the controller can transmit an RCM including an RIU IE (or a frame including the block allocation schedule information described above) at the start point of the first block (i.e., block 0) of each hyperblock (i.e., the start point of slot 0 of round 0 of block 0). Since an RCM (or a frame including the block allocation schedule information described above) is transmitted at the start point of block 0 in hyperblock K including the RIU IE, the block interval field of the RIU IE can indicate the remaining time until the start point of block 0 in hyperblock K+1 including the RIU IE.

[0308] Example 1-1

[0309] FIG. 23 is a diagram illustrating an example of an HBS IE format according to the present disclosure.

[0310] The scope of the present disclosure is not limited by the name of the HBS IE, and examples in which IEs of other names transmitted in the RCM (or in the frame containing the block allocation schedule information described above) include some or all of the information fields described below are included within the scope of the present disclosure.

[0311] The HBS IE in Figure 23(a) may include information about the duration of each block in the hyperblock and information about the controlees assigned to the blocks. The HBS IE may include an associated block index field, a block duration list field for all blocks in the hyperblock, and a list field for the controlee devices belonging to each block. A controlee receiving the HBS IE in an RCM (or a frame containing the block allocation schedule information described above) can recognize the existence of a hyperblock. Furthermore, the controlee can determine which block in the hyperblock it belongs to and perform ranging on by using the controlee list field included in the block duration list field.

[0312] In the example of FIG. 23(a), the block index field can indicate the index of the hyperblock.

[0313] The block duration list length field can indicate the total number of blocks belonging to the hyperblock.

[0314] The block duration list field may include a list of durations for each of the whole blocks belonging to the hyperblock.

[0315] Figure 23(b) shows an example of the format of each of one or more elements included in the block duration list. The element index may correspond to the block index. Although Figure 23(b) does not show the element index or block index, information indicating the block index associated with the controlee list field in the block duration list (i.e., to which devices belonging to the controlee list are assigned) may be included in the IE.

[0316] A block duration field may indicate a value corresponding to the duration of the block to which the index is assigned.

[0317] The address size field can have a value of 0 to indicate that short addresses (16-bit size) are used, or a value of 1 to indicate that extended addresses (64-bit size) are used.

[0318] The controlee list field may include a list of controlee devices operating in (i.e., belonging to / assigned to) the block whose block index corresponds to the element index.

[0319] 23(c) shows an example of the format of each of one or more elements included in the controlee list. That is, the controlee list may include one or more elements, and each element may include a controlee address. Therefore, the controlee list may include one or more device addresses.

[0320] As a further example, in the hyperblock-based mode, the block structure may be scheduled based on the ranging block duration (RBD) field, ranging round duration (RRD) field, and ranging slot duration (RSD) field included in the ARC IE in the RCM (or the frame including the block allocation schedule information described above). In this case, the block duration of a block in a hyperblock can be indicated based on the block duration list information included in the HBS IE. Therefore, overhead can be reduced by omitting the RBD field of the ARC IE included in the RCM (or the frame including the block allocation schedule information described above) transmitted for each block. When the controller sets scheduling to the hyperblock-based mode and the RCM (or the frame including the block allocation schedule information described above) transmitted in the first block of the hyperblock includes the HBS IE, the RBDP (RBD present) bit of the content control field in the ARC IE format of FIG. 12(a) may be set to 0, and the ARC IE with the RBD field omitted may be included in the RCM (or the frame including the block allocation schedule information described above).

[0321] Example 1-2

[0322] FIG. 24 is a diagram illustrating another example of the HBS IE format according to the present disclosure.

[0323] The scope of the present disclosure is not limited by the name of the HBS IE, and examples in which IEs of other names transmitted in the RCM (or in the frame containing the block allocation schedule information described above) include some or all of the information fields described below are included within the scope of the present disclosure.

[0324] The HBS IE in Figure 24(a) may include information about the duration of each block in the hyperblock and information about the controlees assigned to the blocks. The HBS IE may also include an associated block index field, a block description list field for all blocks in the hyperblock, and a list field for the controlee devices belonging to each block. A controlee receiving the HBS IE in an RCM (or a frame containing the block allocation schedule information described above) can recognize the existence of a hyperblock. Furthermore, the controlee can determine which block in the hyperblock it belongs to and perform ranging on by using the controlee list field included in the block description list field.

[0325] In the example of FIG. 24(a), a hyperblock index field can indicate the index of the hyperblock.

[0326] The content control field may include a block duration unit field, a round duration presence field in block description list elements, and a slot duration presence field in block description list elements, as shown in Figure 24(b).

[0327] The Block Duration Unit field of the Content Control field may indicate the size of the Block Duration field as follows:

[0328] [Table 8]

[0329] The round duration present field of the content control field may indicate the presence of a round duration field in the block description list element if its value is 1, or its absence if its value is 0. The slot duration present field of the content control field may indicate the presence of a slot duration field in the block description list element if its value is 1, or its absence if its value is 0.

[0330] Referring again to FIG. 24(a), a block description list length field can indicate the total number of blocks belonging to a hyperblock.

[0331] The block description list field may include a list of descriptions for each of the entire blocks belonging to the hyperblock.

[0332] FIG. 24(c) shows an example of the format of each of one or more elements included in the block description list.

[0333] The block index field may indicate the index of the block within the hyperblock, which may correspond to the index of the block associated with the controlee list field in the block description list (i.e., the block to which the device belonging to the controlee list is assigned).

[0334] The size of the block duration field is determined by the value of the block duration unit field of the content field described above, and may be set to an unsigned integer value indicating the block duration value based on the unit.

[0335] The round duration field may be set to an unsigned integer value corresponding to the number of slots per round.

[0336] The slot duration field may be set to an unsigned integer value corresponding to the slot duration in RSTU units.

[0337] The controlee list length field may indicate the number of device addresses included in the controlee list.

[0338] The address size field can have a value of 0 to indicate that short addresses (16-bit size) are used, or a value of 1 to indicate that extended addresses (64-bit size) are used.

[0339] The controlee list field may include a list of controlee devices that operate in (i.e., belong to / are assigned to) the block corresponding to the value in the block index field.

[0340] 24(d) shows an example of the format of each of one or more elements included in the controlee list. That is, the controlee list may include one or more elements, and each element may include a controlee address. Therefore, the controlee list may include one or more device addresses.

[0341] As a further example, in the hyperblock-based mode, the block structure may be scheduled based on the ranging block duration (RBD) field, ranging round duration (RRD) field, and ranging slot duration (RSD) field included in the ARC IE in the RCM (or the frame including the block allocation schedule information described above). In this case, since the block duration of a block in a hyperblock can be indicated based on the block description list information included in the HBS IE, overhead can be reduced by omitting the RBD field of the ARC IE included in the RCM (or the frame including the block allocation schedule information described above) transmitted for each block. When a controller sets scheduling to hyperblock-based mode and transmits an RCM (or a frame including the aforementioned block allocation schedule information) including an HBS IE including a ranging block duration field and / or ranging round duration and / or ranging slot duration field, the RBDP (RBD present) bit and / or RRDP (RRD present) bit and / or RSDP (RSD present) bit of the content control field in the ARC IE format of Figure 12(a) may be set to 0, and an ARC IE with the RBD field and / or RRD field and / or RSD field omitted may be included in the RCM (or a frame including the aforementioned block allocation schedule information).

[0342] Example 2

[0343] This embodiment relates to an example of using the hyperblock-based mode.

[0344] FIG. 25 is a diagram illustrating an example of the actions of a controlled person based on hyperblock information according to the present disclosure.

[0345] In the hyperblock-based mode, a hyperblock corresponding to a group of blocks may include ranging blocks for ranging exchange with multiple controllees. A controllee can obtain block indexes, block duration information, etc. within its own hyperblock using information in the HBS IE included in the first RCM (or the frame including the block allocation schedule information described above) of the hyperblock. Based on this, each controllee can determine the time for which it will operate in active mode. The example in Figure 25 shows an example in which three controllees obtain information included in the HBS IE using the RCM (or the frame including the block allocation schedule information described above) and apply it to their duty cycle operations.

[0346] In the example of Figure 25, the controller can broadcast an RCM (or a frame containing the block allocation schedule information described above) containing an HBS IE (e.g., a block duration (or description) list, a controlee list, etc.) at the start of the first block (block 0) in a hyperblock in RAN (ranging area network) 1.

[0347] The controller can include an ARC IE in the RCM (or the frame including the block allocation schedule information described above) to transmit additional scheduling information within the block. Here, the HBS IE includes a block duration list (or a block description list), and the block duration list (or a block description list) may include block duration information (or block duration / round duration / slot duration information), so the block duration (or block duration / round duration / slot duration) field may be omitted in the ARC IE.

[0348] By receiving the information in the HBS IE included in the RCM (or the frame containing the block allocation schedule information mentioned above), each controlled party knows the index of the block to which it belongs within the hyperblock, the duration of that block and other blocks, etc.

[0349] The controlled party can obtain the ranging round duration information in the ARC IE of the RCM (or the frame containing the block allocation schedule information mentioned above) (or the round duration information in the block description list of the HBS IE).

[0350] This allows the controlled person 1 to know that he / she belongs to block 2, and he / she can be scheduled to remain in sleep (or deep sleep) mode during the times corresponding to blocks 0 and 1.

[0351] Controlled party 2 is found to belong to block 0 and can be scheduled to remain in sleep (or deep sleep) mode during the times that fall under blocks 1 and 2.

[0352] Controlled person 3 is found to belong to block 1 and can be scheduled to remain in sleep (or deep sleep) mode during the times that fall under blocks 0 and 2.

[0353] In order to check whether there is an update of control information (e.g., HBS IE, ARC IE, etc. using RCM (or the frame including the block allocation schedule information described above)) in the next hyperblock, the controllable devices can maintain an active state for a specific time (e.g., the first round of the first block of each hyperblock) to receive an RCM (or the frame including the block allocation schedule information described above) at the beginning of each hyperblock. After completing the reception of the RCM (or the frame including the block allocation schedule information described above), the controllable devices not assigned to the block (e.g., controllable devices 1 and 3) operate in a sleep mode, but may switch to an active mode in the block to which they are assigned.

[0354] Additionally or alternatively, as shown in the example of the position of the RCM (or the frame including the block allocation schedule information) in Figure 25, the RCM including the HBS IE according to the present disclosure (or the frame including the block allocation schedule information) may be transmitted in the first ranging round for each ranging block of each hyperblock. Alternatively, the RCM including the HBS IE according to the present disclosure (or the frame including the block allocation schedule information) may be transmitted in a specific (e.g., first) ranging round for each of some of the ranging blocks of each hyperblock.

[0355] The RCM including the HBS IE according to the present disclosure (or the frame including the block allocation schedule information described above) may have a narrowband PPDU format based on O-QPSK (offset quadrature phase-shift keying) PHY (e.g., a PPDU format including the SHR, PHR, and PHY payload fields in FIG. 2(g)). The SHR may include a preamble and an SFD. The PHR may include a frame length field.

[0356] The RCM including the HBS IE according to the present disclosure (or the frame including the block allocation schedule information described above) may have a UWB PPDU format (e.g., a format as illustrated in FIG. 3). The locations and functions of the SYNC, SFD, PHR, STS, and PHY payload are as described with reference to FIG. 3.

[0357] Messages such as ADV-POLL (advertisement-poll) and ADV-RESP (advertisement response) may be included in the PHY payload field of the PPDU format. Also, an RCM including an HBS IE (or a frame including the block allocation schedule information described above) may be included in the PHY payload field of the PPDU format.

[0358] Unlike the time structure of fixed block duration in existing UWB wireless network systems, the time structure supporting the hyperblock-based mode according to the example of the present disclosure can provide a flexible time structure having a sufficient time length for necessary packet transmission as well as support rapid ranging / location measurement based on various durations to meet the requirements of various applications, as described above. Furthermore, based on a list of controlled devices assigned to each block index in a hyperblock, it can support power saving of controlled devices in the block (e.g., operating in active mode in assigned blocks or operating in sleep mode in unassigned blocks).

[0359] The embodiments described above are combinations of the components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless otherwise explicitly stated. Each component or feature may be implemented without being combined with other components or features. It is also possible to combine some components and / or features to form embodiments of the present disclosure. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment, or may be replaced with corresponding components or features of another embodiment. It is clear that claims that do not have an explicit reference relationship in the claims may be combined to form embodiments, or may be included as new claims by amendment after filing.

[0360] It is obvious to those skilled in the art that the present disclosure can be embodied in other specific forms without departing from the essential features of the present disclosure. Therefore, the above detailed description should not be interpreted as limiting in any respect, but should be considered as illustrative. The scope of the present disclosure should be determined by reasonable interpretation of the appended claims, and any modifications within the equivalent scope of the present disclosure are included in the scope of the present disclosure.

[0361] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that cause a device or computer to perform operations according to the methods of various embodiments, as well as non-transitory computer-readable media on which such software or instructions are stored and executable on a device or computer. Instructions usable for programming a processing system to perform features described in this disclosure may be stored on or in a storage medium or computer-readable storage medium, and computer program products including such storage media may be used to embody features described in this disclosure. The storage medium may include, but is not limited to, high-speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, and may include non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory optionally includes one or more storage devices located remotely from the processor. The memory, or alternatively, a non-volatile memory device within the memory, comprises a non-transitory computer-readable storage medium. The features described in this disclosure may be embodied in software and / or firmware stored on any one of a number of machine-readable media and capable of controlling the hardware of a processing system and allowing the processing system to interact with other mechanisms that utilize the results of embodiments of the present disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0362] [Industrial Applicability] Although the method proposed in this disclosure has been described mainly as being applied to an IEEE 802.15.4-based system, it is also applicable to various UWB wireless networks or wireless communication systems in addition to the IEEE 802.15.4-based system.

[0363] [Claims at the time of international application] [Claim 1] 1. A method performed by a first device in an ultra-wideband (UWB) wireless network system, comprising: generating, by the first device, an information element (IE) including a list of devices associated with a ranging block; transmitting a frame including the IE to one or more second devices; The method, wherein the ranging block is one of one or more ranging blocks within a respective hyperblock. [Claim 2] The IE includes a ranging block index field; The method of claim 1 , wherein the ranging block index field identifies an index of the ranging block within a respective hyperblock. [Claim 3] 2. The method of claim 1, wherein the field for the device list is an address list field containing addresses for one or more devices assigned to one or more ranging rounds within a ranging block identified by a ranging block index field included in the IE. [Claim 4] The method of claim 3 , wherein the IE includes a length field for the address list field. [Claim 5] The method of claim 4 , wherein the field for the address list includes addresses for a number of devices based on the value of the length field. [Claim 6] The IE is a first element including a first ranging block index field, a first address length field, and a first address list field; and 6. The method of claim 5, further comprising a second element including a second ranging block index field, a second address length field, and a second address list field. [Claim 7] The method of claim 1 , wherein each hyperblock includes multiple ranging blocks, and the durations of the multiple ranging blocks are different from each other. [Claim 8] One ranging block includes one or more ranging rounds, The method of claim 7 , wherein the ranging block includes multiple ranging rounds, and the durations of the multiple ranging rounds are the same. [Claim 9] The frame including the IE is A part or all of the RCM (ranging control message) in each hyperblock, the first ranging round of each ranging block within said each hyperblock; or 10. The method of claim 1, wherein the first ranging round of the first ranging block in the respective hyperblock is transmitted in any one or more of the following: [Claim 10] The first device corresponds to a controller, The method of claim 1 , wherein the second device corresponds to a controlee. [Claim 11] The method of claim 1 , wherein the first device and the second device are enhanced ranging-capable devices (ERDEVs). [Claim 12] A first device in an ultra-wideband (UWB) wireless network system, one or more transceivers; one or more processors coupled to the one or more transceivers; The one or more processors: Generate an information element (IE) containing a list of devices associated with the ranging block; and transmitting a frame including the IE to one or more second devices via the one or more transceivers; The first device, wherein the ranging block is one of one or more ranging blocks in a respective hyperblock. [Claim 13] 1. A method performed by a second device in an ultra-wideband (UWB) wireless network system, comprising: receiving a frame from a first device that includes an information element (IE) that includes a list of devices associated with a ranging block; determining, based on inclusion of the second device in the device list, that the ranging block is to be assigned to the second device; The method, wherein the ranging block is one of one or more ranging blocks within a respective hyperblock. [Claim 14] A second device in an ultra-wideband (UWB) wireless network system, one or more transceivers; one or more processors coupled to the one or more transceivers; The one or more processors: receiving, via the one or more transceivers, a frame from a first device, the frame including an information element (IE) including a list of devices associated with a ranging block; and determining that the ranging block is to be assigned to the second device based on the second device being included in the device list; The ranging block is one of one or more ranging blocks in each hyperblock. [Claim 15] 1. A processing apparatus configured to control devices in an ultra-wideband (UWB) wireless network system, comprising: one or more processors; A processing device comprising: one or more computer memories operably coupled to the one or more processors and storing instructions that, when executed by the one or more processors, perform the method of any one of claims 1 to 11. [Claim 16] one or more non-transitory computer-readable media storing one or more instructions, A non-transitory computer-readable medium, the one or more instructions being executed by one or more processors to control a device in an ultra-wideband (UWB) wireless network system to perform the method of any one of claims 1 to 11.

Claims

1. 1. A method performed by a first device in an ultra-wideband (UWB) wireless network system, comprising: generating, by the first device, an information element (IE) including a list of devices associated with a ranging block; transmitting a frame including the IE to one or more second devices; The method, wherein the ranging block is one of one or more ranging blocks within a respective hyperblock.

2. The IE includes a ranging block index field, The method of claim 1 , wherein the ranging block index field identifies an index of the ranging block within a respective hyperblock.

3. 2. The method of claim 1, wherein the field for the device list is an address list field that includes addresses for one or more devices that are assigned to one or more ranging rounds within a ranging block identified by a ranging block index field included in the IE.

4. The method of claim 3 , wherein the IE includes a length field for the address list field.

5. 5. The method of claim 4, wherein the field for the address list includes addresses for a number of devices based on the value of the length field.

6. The IE is a first element including a first ranging block index field, a first address length field, and a first address list field; and 6. The method of claim 5, further comprising a second element including a second ranging block index field, a second address length field, and a second address list field.

7. The method of claim 1 , wherein each hyperblock includes multiple ranging blocks, and the durations of the multiple ranging blocks are different from each other.

8. One ranging block includes one or more ranging rounds, The method of claim 7 , wherein the ranging block includes multiple ranging rounds, and the durations of the multiple ranging rounds are the same.

9. The frame including the IE is A part or all of the RCM (ranging control message) in each of the hyperblocks, the first ranging round of each ranging block within said each hyperblock; or 3. The method of claim 1, wherein the first ranging round of the first ranging block in the respective hyperblock is transmitted in any one or more of the following:

10. The first device corresponds to a controller, The method of claim 1 , wherein the second device corresponds to a controlee.

11. The method of claim 1 , wherein the first device and the second device are enhanced ranging-capable devices (ERDEVs).

12. A first device in an ultra-wideband (UWB) wireless network system, comprising: one or more transceivers; one or more processors coupled to the one or more transceivers; The one or more processors: Generate an information element (IE) containing a list of devices associated with the ranging block; and transmitting a frame including the IE to one or more second devices via the one or more transceivers; The first device, wherein the ranging block is one of one or more ranging blocks in each hyperblock.

13. 1. A method performed by a second device in an ultra-wideband (UWB) wireless network system, comprising: receiving a frame from a first device that includes an information element (IE) that includes a list of devices associated with a ranging block; determining, based on the inclusion of the second device in the device list, that the ranging block is to be assigned to the second device; The method, wherein the ranging block is one of one or more ranging blocks within a respective hyperblock.

14. A second device in an ultra-wideband (UWB) wireless network system, comprising: one or more transceivers; one or more processors coupled to the one or more transceivers; The one or more processors: receiving, via the one or more transceivers, a frame from a first device, the frame including an information element (IE) including a list of devices associated with a ranging block; and determining that the ranging block is to be assigned to the second device based on the second device being included in the device list; The ranging block is one of one or more ranging blocks in each hyperblock.

15. 1. A processing apparatus configured to control devices in an ultra-wideband (UWB) wireless network system, comprising: one or more processors; and one or more computer memories operably coupled to the one or more processors and storing instructions that, when executed by the one or more processors, perform the method of any one of claims 1 to 11.

16. one or more non-transitory computer-readable media storing one or more instructions, A non-transitory computer-readable medium, the one or more instructions being executed by one or more processors to control devices in an Ultra Wideband (UWB) wireless network system to perform the method of any one of claims 1 to 11.

Images