Method and apparatus for transmission or reception of scheduling information based on block / round structure in ultra-wideband wireless network system

The method and device for transmitting and receiving scheduling information in ultra-wideband wireless networks using a block/round structure address the need for precise timing and resource allocation, enhancing communication efficiency and accuracy in high-data-rate applications.

WO2024232723A1PCT designated stage expired Publication Date: 2024-11-14LG ELECTRONICS INC
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2024/006378
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-11
Filing Date
2024-05-10
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

Current ultra-broadband wireless network systems lack an efficient method for transmitting and receiving scheduling information based on a block/round structure, which is essential for accurate ranging and communication in high-data-rate applications.

Method used

A method and device are developed to transmit and receive scheduling information using a block/round structure in ultra-wideband wireless networks, allowing for the solicitation and retransmission of scheduling information, incorporating scheduling information elements that include ranging round units and scheduling lists, enabling precise timing and resource allocation.

Benefits of technology

This solution enhances the accuracy and efficiency of ranging and communication processes by providing a structured framework for scheduling information exchange, improving data transmission rates and reducing power consumption in ultra-broadband wireless networks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024006378_14112024_PF_FP_ABST
    Figure KR2024006378_14112024_PF_FP_ABST
Patent Text Reader

Abstract

Disclosed are a method and apparatus for the transmission or reception of scheduling information based on a block / round structure in an ultra-wideband (UWB) wireless network system. A method performed by a first device in an ultra-wideband (UWB) wireless network system according to an embodiment of the present disclosure may comprise: a step in which the first device generates a scheduling information element (IE) for scheduling in a block structure based on one or more ranging rounds; and a step of transmitting a frame including the scheduling IE to one or more second devices. Here, the scheduling IE may include: information indicating the type of scheduling based on a ranging round unit; and scheduling list information related to scheduling based on a ranging round unit for each device.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for transmitting or receiving scheduling information based on block / round structure in an ultra-wideband wireless network system

[0001] The present disclosure relates to a method and device for transmitting or receiving scheduling information based on a block / round structure in an ultra-wideband wireless network system.

[0002] Low-rate (LR) wireless networks can support low-data-rate connectivity between fixed or mobile devices with limited battery consumption requirements. For example, LR wireless networks can be applied to wireless personal area networks (WPANs). 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 precise ranging.

[0003] Ultra-wideband (UWB) wireless networks can support transmitting large amounts of information at low power over a very wide bandwidth (e.g., frequency bands of 3.1 GHz to 10.6 GHz). For example, UWB technology can support converting digitally encoded information into impulse signals with very short time durations, such as sub-nanoseconds, and transmitting 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 high-rate pulse frequency (HRP) PHY technology, which supports high-speed data communications (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 communications (e.g., Radio Frequency Identification (RFID) applications). Furthermore, 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 time-of-flight (TOF) ranging procedures. Recently, the IEEE 802.15.4ab standard is under discussion for the advancement of UWB PHY / MAC, including improvements to wireless network technology based on the IEEE 802.15.4z standard.

[0004] The technical problem of the present disclosure is to provide a method and device for transmitting or receiving scheduling information based on a block / round structure in a UWB wireless network system.

[0005] An additional technical problem of the present disclosure is to provide a method and device for soliciting (re)transmission of scheduling information in a UWB wireless network system.

[0006] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

[0007] A method performed by a first device in an ultra-wideband (UWB) wireless network system according to one aspect of the present disclosure may include: generating, by the first device, a scheduling information element (IE) for scheduling in a block structure based on one or more ranging rounds; and transmitting a frame including the scheduling IE to one or more second devices. Here, the scheduling IE may include information indicating a type of ranging round-based scheduling and scheduling list information related to ranging round-based scheduling for each device.

[0008] A method performed by a second device in an ultra-wideband (UWB) wireless network system according to an additional aspect of the present disclosure may include: receiving, from a first device, a frame including a scheduling information element (IE) for scheduling in a block structure based on one or more ranging rounds; and identifying a ranging round allocated to the second device within the block structure based on the scheduling IE. Here, the scheduling IE may include information indicating a type of ranging round-based scheduling and scheduling list information related to ranging round-based scheduling for each device.

[0009] According to the present disclosure, a method and device for transmitting or receiving scheduling information based on a block / round structure in a UWB wireless network system can be provided.

[0010] According to the present disclosure, a method and device for soliciting (re)transmission of scheduling information in a UWB wireless network system can be provided.

[0011] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

[0012] The accompanying drawings, which are incorporated in and are part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and, together with the detailed description, describe the technical features of the present disclosure.

[0013] FIG. 1 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.

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

[0015] FIG. 3 is a diagram showing the RMARKER position according to the STS packet setting in the HRP-ERDEV PPDU format to which the present disclosure can be applied.

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

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

[0018] FIG. 6 illustrates an example message sequence chart for SS-TWR applying deferred response time results to which the present disclosure may be applied.

[0019] FIG. 7 illustrates an example message sequence chart for SS-TWR applying embedded response time results to which the present disclosure may be applied.

[0020] FIG. 8 illustrates an example of a message sequence chart for SS-TWR using SP3 packets to which the present disclosure may be applied.

[0021] FIG. 9 illustrates an example of a message sequence chart for a DS-TWR to which delayed response time information to which the present disclosure may be applied.

[0022] FIG. 10 illustrates an example of a message sequence chart for DS-TWR to which embedded ranging time information to which the present disclosure may be applied.

[0023] FIG. 11 is a diagram illustrating the role of a device in a ranging procedure to which the present disclosure can be applied.

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

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

[0026] FIG. 14 illustrates examples of timing diagrams for various multi-device ranging to which the present disclosure may be applied.

[0027] FIG. 15 shows a time diagram in an example of a block-based mode to which the present disclosure can be applied.

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

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

[0030] FIG. 18 illustrates an example of a message sequence chart for an SP3 one-to-many SS-TWR to which the present disclosure may be applied.

[0031] FIG. 19 illustrates the format of a scheduling information element (IE) to which the present disclosure can be applied.

[0032] FIG. 20 illustrates the format of a scheduling list element according to the value of the scheduling list type field to which the present disclosure can be applied.

[0033] FIG. 21 is a diagram showing the difference in time structure for a single application to which the present disclosure can be applied and a combination of various applications.

[0034] FIG. 22 is a drawing for explaining the operation of the first device according to the present disclosure.

[0035] FIG. 23 is a drawing for explaining the operation of a second device according to the present disclosure.

[0036] FIG. 24 illustrates an example of a time structure in a hyper block-based mode according to the present disclosure.

[0037] FIG. 25 is a diagram showing an example of the HBS IE format according to the present disclosure.

[0038] FIG. 26 is a diagram illustrating an example of a scheduling list element format related to block scheduling according to an embodiment of the present disclosure.

[0039] FIG. 27 is a diagram illustrating another example of a scheduling information element (IE) format according to the present disclosure.

[0040] FIG. 28 is a diagram illustrating an example of a scheduling list element format based on address indexing according to the present disclosure.

[0041] FIG. 29 is a diagram showing an example of a controllable entity's operation based on hyper block information according to the present disclosure.

[0042] FIG. 30 is a diagram illustrating an HBS IE and a scheduling IE transmitted within a hyper block according to the present disclosure.

[0043] FIG. 31 is a diagram illustrating an IE included in a control message related to a hyper block structure according to the present disclosure.

[0044] FIG. 32 is a diagram illustrating an address indexing-based scheduling IE according to the present disclosure.

[0045] FIG. 33 illustrates an example of a scheduling list element format for bitmap-based block scheduling according to the present disclosure.

[0046] FIG. 34 illustrates another example of a scheduling list element format for bitmap-based block scheduling according to the present disclosure.

[0047] FIG. 35 illustrates an example of a scheduling list element format for bitmap-based round scheduling according to the present disclosure.

[0048] FIG. 36 illustrates another example of a scheduling list element format for bitmap-based round scheduling according to the present disclosure.

[0049] FIG. 37 is a diagram illustrating an example of a scheduling list element format based on address indexing according to the present disclosure.

[0050] FIG. 38 is a diagram illustrating an example of operation of a controllable entity based on block scheduling information in a general block-based mode according to the present disclosure.

[0051] FIG. 39 is a diagram illustrating another example of the operation of a controllable entity based on block scheduling information in a general block-based mode according to the present disclosure.

[0052] FIG. 40 is a diagram illustrating another example of the operation of a controllable entity based on round scheduling information in a general block-based mode according to the present disclosure.

[0053] FIG. 41 is a diagram illustrating another example of the operation of a controllable entity based on round scheduling information in a general block-based mode according to the present disclosure.

[0054] FIG. 42 is a diagram illustrating an example of an operation based on a scheduling information request IE according to the present disclosure.

[0055] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to explain exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure may be practiced. The following detailed description includes specific details to provide a thorough understanding of the present disclosure. However, one of ordinary skill in the art will appreciate that the present disclosure may be practiced without these specific details.

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

[0057] In the present disclosure, when a component is said to be "connected," "coupled," or "connected" to another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, the terms "comprises" or "has" in the present disclosure specify the presence of the mentioned 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.

[0058] In this disclosure, terms such as “first,” “second,” etc. 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 between the components unless specifically stated otherwise. Accordingly, 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.

[0059] The terminology used herein is for the purpose of describing particular embodiments and is not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. The term "and / or" as used herein may refer to any one of the associated enumerated items, or is meant to refer to and encompass any and all possible combinations of two or more of them. Furthermore, the use of " / " between words in this disclosure has the same meaning as "and / or" unless otherwise stated.

[0060] The examples of the present disclosure can be applied to various wireless communication systems. For example, the examples of the present disclosure can be applied to a wireless network based on the IEEE 802.15 standard (e.g., Zigbee, Bluetooth, etc.). In particular, the examples of the present disclosure can be applied to a wireless network based on the IEEE 802.15.4 standard, and further, can be applied 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 a wireless network of the IEEE 802.15 series, and can be applied to a wireless local area network (WLAN) technology or Wi-Fi technology of the IEEE 802.11 series, or can be applied to a cellular wireless communication system (e.g., a technology of the Long Term Evolution (LTE) series of the 3rd Generation Partnership Project (3GPP) standard, and 5G New Radio (NR), etc.).

[0061] The IEEE 802.15.4ab standard, which includes techniques to further enhance the UWB PHY / MAC, is under discussion. For example, the IEEE 802.15.4ab standard includes: additional coding, preamble, and modulation techniques to support improved 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 the accuracy, precision, reliability, and interoperability of high-integrity ranging; techniques to reduce complexity and power consumption; definition of hybrid operation with narrowband signaling to assist UWB; improved native discovery and connection setup mechanisms; sensing capabilities to support presence detection and environment mapping; mechanisms to support high data-rate streaming, allowing throughputs of at least 50 Mbps, as well as low-power, low-latency streaming; Support for peer-to-peer, peer-to-multipeer, station-to-infrastructure protocols and infrastructure synchronization mechanisms is being discussed.

[0062] Below, technical features to which examples of the present disclosure can be applied are described.

[0063] FIG. 1 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.

[0064] The first device (100) and the second device (200) illustrated in FIG. 1 may be replaced with various terms such as a terminal, a wireless device, a WTRU (Wireless Transmit Receive Unit), a UE (User Equipment), an MS (Mobile Station), a UT (user terminal), an MSS (Mobile Subscriber Station), an MSS (Mobile Subscriber Unit), an SS (Subscriber Station), an AMS (Advanced Mobile Station), a WT (Wireless terminal), or simply a user. In addition, the first device (100) and the second device (200) may be replaced with various terms such as an access point (AP), a BS (Base Station), a fixed station, a Node B, a BTS (Base Transceiver System), a network, an AI (Artificial Intelligence) system, an RSU (road side unit), a repeater, a router, a relay, a gateway, etc.

[0065] If the devices (100, 200) illustrated in FIG. 1 support ranging, they may be referred to as RDEV (ranging-capable device) or ERDEV (enhanced ranging-capable device). For example, the devices (100, 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, 200) may be referred to as an initiator, a responder, an originator, a recipient, a controller, a controlee, and the like, depending on their roles in ranging operations. The role of a device is not fixed, but may be relatively determined based on its relationship with other devices. When a device interacts with multiple devices, the device may perform multiple roles.

[0066] Referring to FIG. 1, a first device (100) and a second device (200) can transmit and receive wireless signals through various UWB wireless network technologies (e.g., IEEE 802.15.4 series). The first device (100) and the second device (200) can include interfaces for a medium access control (MAC) layer and a physical layer (PHY) that follow the provisions of the IEEE 802.15.4 standard. The IEEE 802.15.4-based PHY and MAC are included in a UWB subsystem, and the UWB subsystem can further include a UWB command interface (UCI) corresponding to an interface between a UWB controller and a host. The UWB subsystem can exchange messages with a host system through the UCI.

[0067] In addition, the first device (100) and the second device (200) may additionally support various communication standards (e.g., standards of the IEEE 802.15 series, IEEE 802.11 series, 3GPP LTE series, 5G NR series, etc.) other than the UWB wireless network technology. In addition, the device of the present disclosure may be implemented as various devices such as a mobile phone, a vehicle, a personal computer, an AR (Augmented Reality) device, a VR (Virtual Reality) device, etc. In addition, the device of the present specification may support various communication services such as voice calls, video calls, data communications, autonomous driving, MTC (Machine-Type Communication), M2M (Machine-to-Machine), D2D (Device-to-Device), and IoT (Internet-of-Things).

[0068] A first device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. For example, the processor (102) may process information in the memories (104) to generate first information / signals, and then transmit a wireless signal including the first information / signals via the transceivers (106). Furthermore, the processor (102) may receive a wireless signal including second information / signals via the transceivers (106), and then store information obtained from signal processing of the second information / signals in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including instructions for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement UWB wireless network technology (e.g., IEEE 802.15.4 series). The transceiver (106) may be connected 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 the present disclosure, a device may also mean a communication modem / circuit / chip.

[0069] The second device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). Furthermore, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including instructions for performing the descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed in the present disclosure. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement UWB wireless network technology (e.g., IEEE 802.15.4 series). The transceiver (206) may be connected 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 the present disclosure, a device may also mean a communication modem / circuit / chip.

[0070] Hereinafter, the hardware elements of the device (100, 200) will be described in more detail. Although not limited thereto, 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, MAC). 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, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in the present disclosure, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in the present disclosure.

[0071] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, 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) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, 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. The descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0072] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as 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 internally and / or externally 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 technologies, such as wired or wireless connections.

[0073] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of the present disclosure, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of the present disclosure, from one or more other devices. For example, one or more transceivers (106, 206) can be coupled to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, 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. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure, via one or more antennas (108, 208). In the present disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0074] For example, the transceiver (106, 206) of FIG. 1 can perform transmission and reception operations of signals (e.g., packets or PPDUs (Physical layer Protocol Data Units) according to IEEE 802.15.4, etc.). In addition, in the present disclosure, operations in which various devices generate transmission and reception signals or perform data processing or calculations in advance for transmission and reception signals can be performed in the processor (102, 202) of FIG. 1. For example, an example of an operation for generating a transmission / reception signal or performing data processing or operation in advance for a transmission / reception signal may include an operation for determining / obtaining / configuring / computing / decoding / encoding bit information of field(s) included in a PPDU, an operation for determining / configuring / obtaining time resources or frequency resources, etc. used for field(s) included in a PPDU, an operation for determining / configuring / obtaining a specific sequence, etc. used for field(s) included in a PPDU, an operation for determining / configuring / obtaining a power control operation and / or a power saving operation applied to a device, and an operation for determining / obtaining / configuring / computing / decoding / encoding an ACK signal. Additionally, in the examples below, various information (e.g., information related to fields / subfields / control fields / parameters / power, etc.) used by various devices for determining / acquiring / configuring / operating / decoding / encoding transmission / reception signals can be stored in the memory (104, 204) of FIG. 1.

[0075] In the UWB band, devices can perform medium access based on the CSMA / CA (Carrier Sense Multiple Access with Collision Avoidance) mechanism. The CSMA / CA mechanism can perform CCA (Clear Channel Assessment), which senses the wireless channel or medium for a predetermined period of time before the device begins transmitting. Sensing can be performed, for example, using an energy detection (ED) method based on a predetermined threshold. If the sensing result indicates that the medium is idle, the device initiates transmission through the medium. Conversely, if the medium is detected to be occupied or busy, the device may not initiate transmission but wait for a delay period (e.g., a random backoff period) for medium access before attempting transmission. By applying a random backoff period, multiple devices are expected to wait for different periods of time before attempting transmission, thereby minimizing collisions.

[0076] In addition, when a superframe structure is applied, a slotted CSMA-CA mechanism may be applied to data transmission in the CAP (contention access period) of the active portion among the active portion and the inactive portion of the interval between beacons. The CSMA-CA mechanism may not be applied to data transmission within the active portion and in the CFP (contention free period). When a superframe structure is not applied, an unslotted CSMA-CA mechanism may be applied to transmission of all data frames except for an ACK frame for a data request command.

[0077] Ranging Measurement

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

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

[0080] Figures 2(a) to 2(g) illustrate the 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 can be generated.

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

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

[0083] 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 bits 0 to 18. For example, bits 0-1 may correspond to a data rate field, bits 2-8 may correspond to a frame length field, bit 9 may correspond to a ranging field, bit 10 may correspond to a reserved field, bits 11-12 may correspond to a preamble duration field, and bits 13-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 a PSDU. The ranging field may indicate whether the corresponding frame is a RFRAME (ranging frame). The preamble duration field may indicate the length (in symbol units) of the SYNC field of the SHR.

[0084] In Fig. 2(d), convolution encoding is applied to generate a coded PHY payload field, and in Fig. 2(e), spreading can be applied to the PHY payload field.

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

[0086] In FIG. 2(g), modulation is applied to the SHR, PHR, and PHY payload fields, and the PPDU encoding procedure is terminated. A default coding rate may be applied to the SHR field.

[0087] The PHR field may have a format including data rate (2 bits), frame length (7 bits), ranging (1 bit), reserve (1 bit), preamble duration (2 bits), and SECDED (6 bits) for base pulse repetition frequency (BRFP) mode, or may have a format including A1 (1 bit), A0 (1 bit), PHY payload length (10 bits), ranging (1 bit), and SECDED (6 bits) for higher pulse repetition frequency (HPRF) mode. The A1 and A0 fields may also indicate the size of an additional gap between the payload and the STS. For the PHR field, in the BPRF mode, BPM-BPSK (burst position modulation-binary phase shift keying) with a coding rate of 850 kb / s or 6.8 Mb / s may be applied, in the HPRF mode, modulation with a coding rate of 3.9 Mb / s, 7.8 Mb / s, 15.6 Mb / s, or 31.2 Mb / s may be applied, and in other cases, BPM-BPSK with a coding rate of 850 kb / s or 110 kb / s may be applied. For the PHY payload field, in the HPRF mode, modulation with a coding rate of 6.8 Mb / s, 7.8 Mb / s, 27.2 Mb / s, or 31.2 Mb / s may be applied, and in other cases, BPM-BPSK with a coding rate indicated in the PHR may be applied.

[0088] FIG. 3 is a diagram showing the RMARKER position according to the STS packet setting in the HRP-ERDEV PPDU format to which the present disclosure can be applied.

[0089] The STS (Scrambled Timestamp Sequence) field may contain a sequence of pseudo-randomized pulses. For example, the STS may contain a sequence of pseudo-random pulses based on AES (Advanced Encryption Standard)-128, and may be utilized for accurate positioning in spread spectrum-based positioning technology in UWB communications.

[0090] The PPDU STS packet structure settings may vary depending on whether the STS field is included and its location.

[0091] Figure 3(a) shows the format corresponding to STS packet setting 0 (i.e., no STS field exists in the PPDU). This format can be defined as mandatory.

[0092] Figure 3(b) shows the format corresponding to STS packet setup 1 (i.e., the STS field is located immediately after the SFD field and before the PHR field). This format can be defined mandatorily.

[0093] Figure 3(c) shows the format corresponding to STS packet setup 2 (i.e., the STS field is located after the PHY payload field). This format may be defined as optional.

[0094] Figure 3(d) shows the format corresponding to STS packet setup 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., the PHY payload field)). This format can be defined mandatorily.

[0095] PPDU formats such as those in the examples in Fig. 3 may also be referred to as HRP-ERDEV PPDU formats. In Fig. 3, arrows indicate the RMARKER (ranging marker) reference locations in each format. The RMARKER can be a reference for timestamp measurement or a ranging counter.

[0096] For example, RMARKER can be defined as the time at the local antenna of the start of the first symbol following the SFD of RFRAME. The next higher layer can estimate the relative clock offset between the local reference clocks of the remote transmitter and receiver based on the reporting of the SRMARKER receive ranging counter value for one or more STS segments.

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

[0098] The ranging capability can be enabled in the RDEV using the MCPS (MAC common part sublayer)-DATA.request primitive and the MLME (MAC sublayer management entity)-RX-ENABLE.request primitive. A primitive can mean a set of commands or parameters exchanged between layers or sublayer entities within a device. For example, an originator can request the ranging capability using the MCPS-DATA.request primitive, and a recipient can activate the ranging capability using the MLME-RX-ENABLE.request primitive.

[0099] Ranging and Localization Methods

[0100] The ranging and localization methods supported by RDEVs and ERDEVs can be based on time-stamping capabilities. Time-based techniques such as single-sided two-way ranging (SS-TWR), double-sided two-way ranging (DS-TWR), and one-way ranging / time difference of arrival (OWR / TDOA) are described below.

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

[0102] In the example of Figure 4(a), SS-TWR includes the measurement of the round-trip delay of a single message from one device to another and the response sent to the sending 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.

[0103] Each device precisely measures the transmission and reception times of message frames, allowing it to calculate T_round and T_reply through simple subtraction. The resulting TOF can be estimated as ^T_prop using the formula below.

[0104]

[0105] If the device can estimate the relative clock offset between itself and the remote device, the accuracy of TOF can be improved by the following formula:

[0106]

[0107] 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.

[0108] In the example of Fig. 4(b), DS-TWR corresponds to an extension of SS-TWR, and two round trip times are used and combined to produce a TOF result by reducing errors in the case where an uncorrected clock frequency offset exists 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, and device A responds to it, thereby completing the entire DS-TWR exchange. T_prop corresponds to the propagation time of the RMARKER between devices.

[0109] Each device precisely measures the transmission and reception times of message frames, allowing it to calculate T_round and T_reply through simple subtraction. The resulting TOF can be estimated as ^T_prop using the formula below.

[0110]

[0111] The example in Fig. 4(c) corresponds to reducing the DS-TWR through the four messages in Fig. 4(b) to three messages. That is, the response to the first round-trip time measurement can be used as the initiation message for the second round-trip time measurement.

[0112] Next, we describe 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 a single message or multiple messages. OWR can be used for TDOA. There are two cases for TDOA. In one case, a message is periodically broadcast by a mobile device, and the arrival times of the broadcast messages at multiple fixed nodes synchronized in a predetermined manner can be compared. Typically, the message transmitted by the mobile device can be referred to as a blink. In the other case, multiple synchronized nodes can sequentially broadcast messages according to a known transmission time offset. 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, positions the mobile device on a hyperbolic surface. By combining the results from multiple such pairs, the intersection point between the sets of hyperbolic surfaces can be derived, thereby determining the location of the mobile device. In a second case, the transmission offset can be taken into account when calculating the difference in arrival times of messages from synchronized nodes.

[0113] RFID devices typically use the shortest possible blink message (e.g., a multipurpose frame) to reduce power consumption. A multipurpose frame can be 12 octets long and include a short frame control field, a sequence number field, and may not include a destination address field, an extended source address field, or a frame check sequence (FCS).

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

[0115] Setup procedure before ranging exchange

[0116] To reduce power consumption, ranging can be defined as disabled by default. Enabling ranging on all RDEVs participating in a TWR exchange can be performed by a higher layer. Furthermore, if optional capabilities are used, some coordination of the preamble and channel selection can be assumed prior to the TWR exchange.

[0117] Finish-up procedure after ranging exchange

[0118] At the end of a TWR exchange, each device can maintain transmit (TX) and receive (RX) ranging counter values ​​related to round-trip time measurements or response times. To calculate TOF, all of these values ​​are required at the node where the calculation is performed. This can be accomplished using out-of-band (OOB) signaling, custom messages, and ranging measurement information (RMI) information elements (IEs).

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

[0120] Figure 5(a) shows an example of the RMI IE format.

[0121] The RMI IE can be used to send one or more ranging-related measurements to one or more devices. The RMI IE content field can have a format similar to the example in Figure 5(a).

[0122] A value of 1 in the reply time present field may indicate that an RX-to-TX (or TX-to-RX) reply time field is present in each RMI list element, and a value of 0 may indicate that it is not present. The RX-to-TX (or TX-to-RX) reply time may correspond to T_reply described with reference to FIG. 4.

[0123] A value of 1 in the round-trip time present field may indicate that a TX-to-RX round-trip time field exists in each RMI list element, and a value of 0 may indicate that it does not exist. The TX-to-RX round-trip time may correspond to T_round described with reference to FIG. 4.

[0124] A value of 1 in the TOF presence field may indicate that the TOF field exists in each RMI list element, and a value of 0 may indicate that it does not exist.

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

[0126] A value of 1 in the AOA elevation present field may indicate that the AOA elevation field is present in each RMI list element, and a value of 0 may indicate that it is not present.

[0127] A value of 1 in the AOA FOM (figure of merit) presence field indicates that an AOA azimuth FOM field exists in each RMI list element if an AOA azimuth field exists, and that an AOA elevation FOM field exists in each RMI list element if an AOA elevation field exists, and a value of 0 may indicate that neither an AOA azimuth FOM field nor an AOA elevation FOM field exists.

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

[0129] A value of 0 in the deferred mode field may indicate that the corresponding RMI IE is embedded in the RFRAME, and a value of 1 may indicate that the corresponding RMI IE is included in the deferred message transmitted in the next measurement report phase.

[0130] The RMI list length field can specify the number of elements in the RMI list field. The fields included in the RMI list field are as shown in Fig. 5(a).

[0131] Figure 5(b) shows an example of the RCPCS IE format.

[0132] The RCPCS (ranging channel and preamble code selection) IE can be used to indicate channel selection and / or TX / RX preamble code selection for dynamic preamble code and channel selection (DPS). DPS can include modifying the long preamble to protect against attacking devices intercepting ranging. The RCPCS IE content field can have a format similar to the example in FIG. 5(b).

[0133] A value of 1 in the CCIP (CCI present) field indicates that the CCI field exists, and a value of 0 indicates that it does not exist.

[0134] A value of 1 in the DDP (DPS Duration Present) field may indicate that the DPS duration field exists, and a value of 0 may indicate that it does not exist.

[0135] 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 may indicate that they are not present.

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

[0137] The CCI (channel configuration interval) field can specify a channel configuration interval. The channel configuration interval can correspond to the time in RSTU (ranging scheduling time units) between the transmission of the corresponding IE and the reconfiguration of the specified channel.

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

[0139] The DPS Duration field can specify the effective time duration of the DPS. The duration can be specified in RSTU units for ERDEV and in symbol units for non-ERDEV.

[0140] The TX Preamble Code field may indicate the DPS preamble code to be used for transmission during an upcoming ranging exchange by the transmitting side of the IE.

[0141] The RX Preamble Code field may indicate the DPS preamble code that the transmitting side of the IE will use for reception during an upcoming ranging exchange.

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

[0143] The MLMR-DPS.request and MLME-DPS.confirm primitives can be applied to the optional DPS mode of ranging. The ConfigTime parameter of the MLME-DPS.request primitive can be used to specify a future point in time at which the preamble code and / or channel number will be applied. The time at which the DPS change will be applied can be exchanged via the CCI field of the RCPCS IE.

[0144] Basic ranging exchange

[0145] The recipient may turn on or enable ranging in the MAC on the recipient side based on the MLME-RX-ENABLE.request primitive from the next higher layer.

[0146] After ranging is turned on at the receiver side MAC (i.e., by receiving the MLME-RX-ENABLE.request primitive), all received RFRAMEs can generate TX / RX ranging counters.

[0147] An originator can send data to a recipient based on the MCPS-DATA.request primitive.

[0148] The receiver can generate a ranging report for all RFRAMEs and send an ACK frame to the sender.

[0149] A sender can activate Tx-to-Rx turnaround (i.e., repeat data transmission and ACK reception) by receiving an ACK frame from the receiver. The next higher layer may not be involved in this.

[0150] Ranging reporting may include the issue of an MCPS-DATA.confirm primitive on the sender 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 the receipt of data from the sender, or indicating that ranging information is available upon receipt of a packet from the sender).

[0151] Until ranging is disabled, the receiver may generate ranging reports and transmit ACKs to the sender, activate Tx-to-Rx turnaround based on receiving the sender's ACK frame, and repeat the ranging reports.

[0152] Ranging Procedure

[0153] First, we explain the control of ranging and the transfer of results.

[0154] Measurements can be exchanged between RDEVs to complete ToF calculations. To this end, the TWR can be controlled through information elements, and ranging data can be exchanged between RDEVs.

[0155] Specifically, the information elements can be used to transmit ranging data between RDEVs participating in ranging exchange and to control TWR. For various ranging methods, depending on the required use case, the measurement results from both devices can be combined to complete the TOF calculation between RDEVs participating in ranging exchange. That is, one device can transmit its ranging measurement results to another device. The information elements can be specified to provide a mechanism for controlling TWR and to support the transmission of ranging information between devices participating in ranging exchange. To ensure the integrity of the information transmission, a secure private data communication capability can be used.

[0156] Below, we describe the ranging procedure for SS-TWR that applies the deferred response time results.

[0157] FIG. 6 illustrates an example message sequence chart for SS-TWR applying deferred response time results to which the present disclosure may be applied.

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

[0159] The next higher layer of the initiator may have sufficient information to calculate the TOF between devices using the formula described above at the time of receiving the RMI IE (e.g., FIG. 5(a)).

[0160] An initiator may initiate a ranging exchange by issuing an MCPS-DATA.request primitive to request ranging response time information and transmit a ranging frame containing a Ranging Request Measurement and Control (RRMC) information element that includes a ranging control information field.

[0161] Figure 5(c) shows an example of the RRMC IE format.

[0162] The RRMC IE transmits a ranging request and may include information that controls the ranging procedure.

[0163] The response time request, round trip time request, TOF request, AOA azimuth request, and AOA elevation request fields in the RRMC IE format can indicate that the corresponding information is requested if the value is 1, and that the corresponding information is not requested if the value is 0.

[0164] The ranging control information field may have a value of 0 to indicate that the frame is a ranging initiation message for SS-TWR, a value of 1 to indicate that the frame is a response to a ranging initiation message for SS-TWR, a value of 2 to indicate that the frame is a ranging initiation message for DS-TWR, and a value of 3 to indicate that the frame is a continuing DS-TWR and initiates a second round trip time measurement.

[0165] 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 can correspond to short addresses. If the value of the address size field is 1, all addresses in the RRMC address list element can correspond to extended addresses.

[0166] The RRMC Address List Length field can indicate the number of addresses in the RRMC Address List field. If no address is 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.

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

[0168] For SS-TWR, since the initiator generally calculates the TOF, the responder can request the TOF result by setting the TOF request field of the RRMC IE included in the response message.

[0169] For DS-TWR, since the responder typically computes the TOF, the initiator can request the TOF result by including the RRMC IE in the two messages it sends to perform the DS-TWR exchange.

[0170] If the initiator requests different information from multiple respondents, multiple RRMC IEs may be included in a single broadcast message.

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

[0172] With respect to the ranging report (or response ranging frame), the initiator side may complete the round-trip time measurement, and the MCPS-DATA.confirm primitive may provide a ranging report defining the round-trip time to the initiator side. On the receiver side, the MCPS-DATA.indication primitive may provide a response-side ranging report defining the response time for the round-trip time measurement.

[0173] Figure 5(d) shows an example of the RRTI (Ranging Reply Time Instantaneous) IE format.

[0174] In association with one or more frames containing 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.

[0175] The address size specifier field can be defined as shown in the table below.

[0176] The value of the address size specifier field is Address Size. 000 octets, address does not exist. 01 Reserved. 102 octets, short address (16 bits). 118 octets, extended address (64 bits).

[0177] The RRTI list length field can indicate the number of elements in the RRTI list field. The RRTI list field can contain RRTI list elements.

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

[0179] The address field of the RRTI list field may be set to the address of the device sending 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 other RDEVs are negotiated in advance and the order is determined.

[0180] Below, we describe the ranging procedure for SS-TWR that applies embedded response time results.

[0181] FIG. 7 illustrates an example message sequence chart for SS-TWR applying embedded response time results to which the present disclosure may be applied.

[0182] For SS-TWR that applies the response time result, the ranging exchange can be initiated by a ranging frame that requests ranging response time information and includes an RRMC IE with the Ranging Control Information field set to 0. The responding device can complete the round-trip measurement by transmitting a response frame that includes an embedded RRTI (ranging reply time instantaneous) IE. If the device has the capability to generate the RRTI IE, the number of messages required for ranging measurement can be minimized, thus 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 known a priori in an OOB manner, and the RRTN (ranging reply time negotiation) IE may provide a mechanism to indicate to the device a preferred response time, i.e., the time required to prepare a frame containing the RRTI IE. If this time is known, the ranging initiating device can expect a response message after a certain time and save energy by delaying turning on the receiver until then. This can be applied to both SS-TWR and DS-TWR ranging exchanges.

[0183] 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 be performed at any convenient time before the ranging exchange is initiated, or the preferred response time information may be known in advance or exchanged via OOB. Upon receiving the MCPS-DATA.indication primitive containing the responder's RRTI IE, the next higher layer of the initiator may have sufficient information to calculate the TOF between the two devices according to the formula described above.

[0184] Below, the ranging procedure for SS-TWR with fixed response time is described.

[0185] FIG. 8 illustrates 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 may be applied.

[0186] 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) can have a fixed, known value agreed upon among the devices participating in the ranging exchange. In this case, it may not be necessary to embed the Treply in the response message or transmit it separately in an additional message. The resulting ranging accuracy may depend on how precisely the responding device controls the transmission time of its response message. For example, in TOF, a 1 ns error may correspond to a ranging error of approximately 30 cm.

[0187] HRP-ERDEV PPDU format SP3 can be used for fixed response times.

[0188] In the example of Figure 8, the initiation message in the dotted box may represent communication for agreement and coordination on the use of SP3 packets between devices and all other parameters necessary to allow ongoing communication. While only a single message is shown in the example of Figure 8, a series of messages in each direction may exist to agree on all parameters. For example, the RRNT IE may be used to agree on a fixed response time.

[0189] In each device, the next higher layer may use the MLME-STS.request primitive to configure the SP3 packet format across all devices and to set personal area network information base (PIB) attributes (e.g., phyHrpUwbStsKey, phyHrpUwbStsVCounter, phyHrpUwbStsVUpper96, etc.) to configure the behavior appropriately. Once the upper layer has selected the SP3 packet configuration, subsequent MCPS-DATA primitives relate to SP3 packets until the upper layer changes the packet configuration using the MLME-STS.request primitive.

[0190] The MCPS-DATA.request primitive can be used to initiate a ranging exchange, in which mode the PPDU may not convey MAC data. Although not shown, it can be assumed that the invocation of the MLME-RXENABLE.request primitive turns on the receiver at the appropriate time to receive the PPDU. Since the PHY is configured for SP3 packets, the PHY notifies the MAC layer of the receipt of the PPDU at the end of the scrambled timestamp sequence (STS), and similarly, the MAC, which is aware of the SP3 configuration, can deliver the RxRangingCounter value of the RangingReportDescriptor parameter of the MCPS-DATA.indication primitive. Furthermore, assuming that the RangingStsFom of the RangingReportDescriptor is acceptable, the upper layer can initiate the response by invoking the MCPS-DATA.request primitive specifying the RangingTxTime according to an agreed-upon fixed response time.

[0191] Assuming that the SP3 packet response is received at the initiating device and that the RangingStsFom of the RangingReportDescriptor parameter of the MCPS-DATA.indication primitive is acceptable, the initiating device may have sufficient information to compute the TOF between the devices according to the aforementioned formula based on the known fixed response time.

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

[0193] LRP-REDEV may also support challenge-response ranging with fixed response times, eliminating the need for data messages carrying response times.

[0194] Below, the DS-TWR ranging procedure to which delayed response time information is applied is described.

[0195] FIG. 9 illustrates an example of a message sequence chart for a DS-TWR to which delayed response time information to which the present disclosure may be applied.

[0196] A DS-TWR may essentially include the completion of a SS-TWR exchange initiated by each device, and the combination of their results. A DS-TWR may be initiated by the next higher layer transmitting a ranging data frame carrying a RRMC IE with the Ranging Control Information field set to 2 (i.e., RRMC IE(2)). This frame and its ACK may define a first round trip time measurement. Conveying the RRMC IE in the MCPS-DATA.indication primitive may notify the next higher layer to initiate a second round trip time measurement by transmitting a data frame in the other direction. This data frame may include an RRMC IE with the Ranging Control Information field set to 3 (i.e., RRMC IE(3)) to indicate a continuation of the exchange, and may request the result of the response time and the first round trip time measurement by having both the Response Time Request and Round Trip Time Request fields set to 1. An ACK for this message may complete the second round-trip time measurement. A subsequent message from the initiator may convey the result of the first round-trip time measurement and the response time of the second round-trip time measurement via the RMI IE. When the responder receives the second MCPS-DATA.indication primitive (containing the RMI IE), it may have sufficient information to calculate the TOF between the devices according to the formula described above. Subsequent reporting of the ranging result to the initiator using the RMI IE may be performed depending on the value of the TOF request field of the initiating RRMC IE.

[0197] Below, the DS-TWR ranging procedure that applies embedded ranging time information is described.

[0198] FIG. 10 illustrates an example of a message sequence chart for DS-TWR to which embedded ranging time information to which the present disclosure may be applied.

[0199] For the 3-message DS-TWR exchange of FIG. 4(c) described above, it is required that the initiator side can embed the response time as part of the completion of the second round trip time measurement. In the example of FIG. 10, the DS-TWR can be initiated by an RFRAME carrying an RRMC IE with the TOF Request field set to 0 (i.e., the initiator side does not request ranging reporting) and the Ranging Control Information field set to 2 (i.e., RRMC IE(2)).

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

[0201] When the responder receives the second MCPS-DATA.indication primitive, it may have sufficient information to calculate the TOF between the devices according to the formula described above. If the initiator of the ranging exchange wants to know the result, the initiator may set the TOF request field of the initiating RRMC IE to a value requesting that the responder send the result in the RMI IE of a subsequent message at the end of the exchange.

[0202] Below, we describe other procedures for adjusting RDEV and ERDEV.

[0203] For successful interoperability of HRP-ERDEV when STS is used, the transmitter and receiver need to be aligned with respect to the seeds (i.e., STS key and data values ​​V) used to generate the STS at the transmitter and to generate the sequence for correlating with the received STS at the receiver. For the coordination of these values, the Secure Private Data Communication capability can be used, and the seeds can be transmitted between devices using the Ranging STS Key and Data (RKSD) IE. The counter values ​​within the RSKD IE can relate to the current packet or future packets, as indicated by the current packet (CP) field of the IE. Upper layers can use the received RSKD IE information (e.g., via PIB attributes such as phyHrpUwbStsKey, phyHrpUwbStsVUpper96, phyHrpUwbStsVCounter) and set the STS seeds appropriately for future packet transmission and reception. The header IE version of the RSKD IE can be used to synchronize the STS generator using information transmitted with the secured payload IE and data.

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

[0205] Multi-node ranging

[0206] Multi-node ranging can involve ranging between two or more devices. Each device can perform a role in multi-node ranging.

[0207] FIG. 11 is a diagram illustrating the role of a device in a ranging procedure to which the present disclosure can be applied.

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

[0209] The next higher layer of the controller can determine the ranging parameters and the role of the ERDEV participating in the ranging exchange (i.e., initiator or responder).

[0210] For example, in Fig. 11(a), an example is shown in which a controller transmitting a ranging control message (RCM) is an initiator transmitting a ranging initiation message in a ranging exchange, and a controllable receiving the RCM is a responder receiving the ranging initiation message in a ranging exchange and transmitting a ranging response message. In Fig. 11(b), an example is shown in which a controller transmitting an RCM is a responder receiving the ranging initiation message in a ranging exchange and transmitting a ranging response message, and a controllable receiving the RCM is an initiator transmitting a ranging initiation message in a ranging exchange.

[0211] A ranging session can be defined as a group of ERDEVs participating in a continuous ranging procedure established by an initial set of ranging parameters. A ranging session can include only one controller and one or more initiators. The controller can set the initial ranging parameters and update the parameters during the ranging session.

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

[0213] Figure 12(a) shows an example of the ARC IE format.

[0214] A controller can use the ARC IE to transmit ranging configuration information to a controlled entity. The ARC IE can be transmitted to a single controller via a unicast frame or to multiple controllers via a broadcast frame.

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

[0216] Each field of ARC IE can be defined as follows:

[0217] Meaning of the value of the multi-node mode field 0 Single device to single device (unicast) 1 Multi-node one-to-many 2 Multi-node many-to-many 3 Reserved

[0218] Meaning of the value of the ranging round usage field 0 OWR (one-way ranging) 1 SS-TWR (single-sided two-way ranging) 2 DS-TWR (double-sided two-way ranging) 3 Ranging ancillary information exchange

[0219] The value of the STS packet config field. The resulting STS packet configuration. 0 The STS field is not included in the PPDU (Figure 3(a)). 1 STS packet structure #1 (Figure 3(b)). 2 STS packet structure #2 (Figure 3(c)). 3 STS packet structure #3 (Figure 3(d)).

[0220] The value of the schedule mode field is the selected ranging schedule mode and behavior. 0 Contention-based ranging is used for subsequent ranging rounds, and the RDM IE and RCPS IE are used for controlled participation. 1 Scheduled-based ranging is used for subsequent ranging rounds, and participation and time slot allocation for ranging is fixed or controlled through the use of the RDM IE.

[0221] The contention-based ranging type corresponds to a method in which the controller is unaware of the presence or number of controllees, and thus ERDEVs perform contention-based ranging. Because collisions can occur, filtering of incorrect or erroneous ranging results may be required at higher layers. The initiator or responder may compete to transmit within an appropriate time slot. If the initiator and responder compete, the ranging contention phase structure (RCPS) information element is added to the ARC information element to specify different phases (e.g., distinguished by slot index) in the RCM. Upon receiving the RCM, the controllee is informed that it has been selected to participate in a ranging round. The time-scheduled ranging type corresponds to a method in which the controller is aware of all controllees and specifies a precise schedule for ranging transmissions. The controller can select devices participating in ranging, assign them ranging roles (i.e., initiator or responder), and allocate time slots through the RDM (ranging device management) IE. If the device roles and transmission schedules are pre-specified, such as through OOB signaling, the RDM IE can be omitted.

[0222] Whether deferred mode is allowed in the measurement report. 0RRTI IE is embedded in the response frame so that the round-trip measurement is completed immediately. 1Round-trip time or response time is reported in the measurement reporting phase.

[0223] The value of the time structure indicator field. The selected ranging time structure behavior. 0 The time structure is interval-based, and the RIU IE is used to control ranging interval updates. 1 The time structure is block-based, and the RR IE is used to control ranging interval updates.

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

[0225] The content control field can 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 of a ranging block duration (RBD) field (i.e., RBDP), a field indicating the presence of a ranging round duration (RRD) field (i.e., RRDP), a field indicating the presence of a ranging slot duration (RSD) field (i.e., RSDP), and a field indicating the presence of a session ID field (i.e., SIP), respectively. Bits 4-7 of the content control field may be reserved.

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

[0227] The RRD field can indicate the duration of a ranging round (in units of ranging slots, i.e., the number of ranging slots within a ranging round).

[0228] The RSD field can indicate the duration (in RSTU units) of the ranging slot.

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

[0230] If the ranging block structure is identical to 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 be used to update the corresponding ranging parameters.

[0231] Figure 12(b) shows an example of the RDM (ranging device management) IE format.

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

[0233] The SIU (slot index usage) field can indicate whether the slot index of an RDM list element is used. If the value is 0, the RDM IE can be used to assign ranging roles (i.e., initiator or responder) to controllable parties for contention-based ranging. If the value is 1, the RDM IE can be used to allocate time slots and assign ranging roles to controllable parties for scheduling-based ranging.

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

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

[0236] The ranging role field in the RDM list can indicate the initiator or responder. The ranging slot index field in the RDM list can indicate the slot index assigned to the device with the corresponding address. The address field in the RDM list can indicate the address of each device participating in ranging.

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

[0238] The RBU IE can be used by the controller to inform the controllable(s) of the updated ranging block structure.

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

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

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

[0242] The updated ranging slot duration can indicate the duration (in RSTU units) of a ranging slot within the new ranging block structure.

[0243] Figure 12(d) shows an example of the RR (Ranging Round) IE format.

[0244] The ranging block index field can indicate the index of a ranging block.

[0245] The hopping mode field can indicate whether hopping mode is supported for the ranging block.

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

[0247] The transmission offset field may indicate the transmission offset value (in RSTU units) of a ranging round within a block. The transmission offset may have a maximum value equal to the maximum slot duration minus the packet duration.

[0248] For the current ranging round (i.e., the 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 supports ERDEV synchronization for the block structure.

[0249] For the next ranging round (i.e., the ranging round in the next ranging block with block index i+1), when the last message of the current ranging round (i.e., the ranging block with block index i) is transmitted from the controller to the controlled party(ies), the RR IE may be transmitted within the final message to inform the ranging round information for the ranging block with block index i+1.

[0250] If the last message within the current ranging round (i.e., ranging block with block index i) is transmitted from the controllable, the controllable can transmit a RR IE in the RCM of the next ranging block with block index i+1 to inform the ranging round information for the ranging block with block index i+2.

[0251] In this case, the RCM in the ranging block with block index i+1 may contain two RR IEs. One RR IE may be applied to the ranging round of the ranging block with block index i+1, and the other RR IE may be applied to the ranging round of the ranging block with block index i+2.

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

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

[0254] Each of the requester address size specifier field and the provider address size specifier field can have values ​​of 00, 01, 10, and 11 as shown in Table 1 above, and can indicate that the address does not exist, or that a short address (16 bits) or an extended address (64 bits) is used.

[0255] The RAOA (report of AOA) field can indicate whether a report on AOA is requested.

[0256] The RRT (report of reply time) field can indicate whether a report on the response time is requested.

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

[0258] The RTOF (report of TOF) field can indicate whether a report on TOF is requested.

[0259] The Requester Address field may be set to the address of the device transmitting the signal for which AOA is being measured or initiating ranging.

[0260] The Provider Address field can be set to the address of the device measuring AOA.

[0261] Ranging block and round structure

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

[0263] In Fig. 13(a), a ranging block is a time interval for performing ranging, and one ranging block can include N ranging rounds.

[0264] A ranging round is 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.

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

[0266] The slot duration, or the number of slots included in a ranging round, may vary between ranging rounds. To achieve this, the controller can send an RCM to the controlled party(ies) that changes the ranging round settings.

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

[0268] RCUM (ranging control update message) is a message transmitted by the controller in the last slot of the ranging round(s) specified by the RCM to update ranging parameters for the next ranging round(s). The IE(s) included in the RCM for updating ranging parameters may be included in the RCUM.

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

[0270] Figure 13(b) describes the phases in the ranging procedure.

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

[0272] RP (ranging phase) can include RIP (ranging initiation phase), RRP (ranging response phase), and RFP (ranging final phase).

[0273] RIP corresponds to the phase where the initiator sends ranging initiation message(s) to the responder(s).

[0274] RRP corresponds to the phase in which the responder(s) send response message(s) to the initiator.

[0275] RFP corresponds to the phase in which the initiator sends ranging final message(s) to the responder, and can only be used in DS-TWR.

[0276] MRP (measurement report phase) is the phase in which participating ERDEVs exchange service information related to ranging measurements.

[0277] RCUP (ranging control update phase) corresponds to the phase in which the controller transmits RCUM, and if RCUP exists, the phase can be located in the last slot of the set of ranging rounds specified by RCM.

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

[0279] FIG. 14 illustrates examples of timing diagrams for various multi-device ranging to which the present disclosure may be applied.

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

[0281] Below we will explain the ranging mode.

[0282] In interval-based mode, the average time of ranging rounds is variable, and a time structure can be applied with adaptive spacing.

[0283] In block-based mode, the average duration of ranging rounds is constant. That is, ranging blocks with the same duration can be repeated in block-based mode.

[0284] Ranging mode selection can be determined based on the OOB mechanism or the time structure indicator field within the ARC IE.

[0285] FIG. 15 shows a time diagram in an example of a block-based mode to which the present disclosure can be applied.

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

[0287] The number of ranging rounds is equal to the ranging block duration divided by the ranging round duration.

[0288] The number of ranging slots is equal to the ranging round duration divided by the ranging slot duration.

[0289] An ERDEV receiving an RCM can set up an associated timeline for ranging based on the initial ranging block structure and the values ​​of fields within the ARC IE. The ranging block structure can be set up and / or fixed by the next higher layer.

[0290] The ranging block structure can be repeatedly transmitted by the controller in every RCM (e.g., via the ARC IE). When a change or update of the ranging block structure (i.e., a new ranging block duration, ranging round duration, and / or ranging slot duration) is required, the controller can transmit an RBU IE for the new configuration. The RBU IE can be transmitted via the RCM or the final data frame in the ranging message sequence. Each time an RBU IE is transmitted, the controller can decrement the Relative Ranging Block Index by one until it becomes 0. This can indicate whether the new configuration is to be used in the next block and whether the RCM ARC IE of the next block includes the new configuration.

[0291] Below we will explain indexing.

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

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

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

[0295] A new ranging message exchange can 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, the RCM packet can be sent at the beginning of the first ranging slot of the first ranging round. The RCM can include a RR IE to inform information related to the ranging rounds within the current ranging block.

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

[0297] The RR IE included in the RCM may include transmission offset information as information associated with the ranging round within the current ranging block. In subsequent ranging rounds, the controller may initiate transmission in each slot based on a different transmission offset. The transmission offset may have a value less than the ranging slot duration minus the UWB packet duration. The transmission offset may be expressed as a multiple of the RSTU.

[0298] Transmit offsets can be applied across ranging rounds. That is, the same transmit offset can be applied to all packet transmissions within the same ranging round. The next higher layer of the controller can select the transmit offset and communicate it to all other devices via the RR IE. The controller can also vary the transmit offset for each ranging round based on the power required to reduce interference.

[0299] One-to-many ranging procedure

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

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

[0302] 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 Initiation message. The Response Time Request field of the RRMC IE may be set to 1 to request a response time from the response ERDEV.

[0303] The RRMC IE transmitted via the MCPS-DATA.indication primitive from each of Responder-1 to Responder-N may signal to the next higher layer that a ranging response should be performed. Each responder may insert the RequestRrtiTxList parameter into the RRTI IE (as a response to the response time request in the RRMC IE) and transmit an RRMC IE with the Ranging Control Information field set to 1 (i.e., RRMC IE(1)) to the initiator. Here, the response RFRAMEs may be transmitted in a unicast manner to the initiator.

[0304] When the initiator receives each ranging response frame, the initiator has enough information to compute the TOF of that responder.

[0305] The final message broadcast by the initiator may include one or more RMI IE(s) for measurement reporting (if requested by the RRMC IE). Multiple RMI IEs may be distinguished by their 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. If multiple responders request the same set of information, such as TOF, measurement reporting from the initiator may be performed via a single RMI IE in the final data message.

[0306] FIG. 18 illustrates an example of a message sequence chart for an SP3 one-to-many SS-TWR to which the present disclosure may be applied.

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

[0308] Multi-node SP3 ranging can be based on scheduling specified by the next higher layer of the controller (i.e. each time slot is assigned to be used by a specific ERDEV).

[0309] The RDM IE within the RCM may contain information for allocating time slots and device roles within a ranging round. The ARC IE specifies the ranging procedure and the SP3 packet format so that the next upper layer of the ERDEV can recognize the start and end of the SP3 ranging phase and issue the MLME-STS primitive to enable / disable SP3 packets before / after the ranging phase.

[0310] An RSKD IE may be included to exchange portions of the STS seed to initiate STS generation between participating ERDEVs in RCM. Based on the scheduling information of the ranging transmission, the STS counter values ​​of the participating ERDEVs may be appropriately set for transmitting and receiving SP3 packets.

[0311] In the SP3 ranging phase, the next higher layer can use MLME-STS.request to select the SP3 packet format, configure the operation on both sides appropriately, and set the phyHrpUwbStsKey, phyHrpUwbStsVUpper96, and phyHrpUwbStsVCounter properties to the correct values. Since the ranging schedule is specified by the RCM preceding the SP3 ranging, the devices already know the participants. Each time slot can be assigned to a specific (E)RDEV.

[0312] In the measurement reporting phase, the initiator may send the AOA and round-trip time to Responder-1 via the RMI IE. Responder-1 to Responder-N may each embed the requested response time in the RMI IE they send to the initiator.

[0313] As another example, in the SP3 ranging phase of a message sequence for an SP3 one-to-many DS-TWR, after the initiator receives an SP3 frame as a ranging response message from each responder, the initiator may transmit an SP3 frame as a ranging complete message to each responder, through which the local value of the initiator's TxRangingCounter may be conveyed to each responder. In the measurement reporting phase, the initiator may transmit an RMI IE including the response time and round trip time to the responders, and in response, each responder may transmit an RMI IE including an AOA to the initiator.

[0314] How to define / apply scheduling information on a block / round basis

[0315] The ranging time structure described with reference to FIGS. 13 and 15 has a hierarchical structure of blocks / rounds / slots. Here, each duration is initially set using the ARC IE and can be updated using the RBU IE. In the existing ranging block structure (i.e., block-based mode), ranging blocks of the same length are repeated.

[0316] Additionally, the previously discussed scheduling IE is designed only for slot-level scheduling (i.e., slot scheduling). The scheduling IE can be included in a control message (e.g., an RCM IE) and transmitted by the controller to each controlee (or responder) participating in the UWB session.

[0317] FIG. 19 illustrates the format of a scheduling information element (IE) to which the present disclosure can be applied.

[0318] Referring to FIG. 19, the existing scheduling IE format (e.g., the scheduling IE content field format) may include a scheduling list length field, a scheduling list type field, an address size field, a receiver address present field, and a variable-size scheduling list field.

[0319] Specifically, the scheduling list length field can indicate the number of elements in the scheduling list field.

[0320] The scheduling list type field can specify how the format of the scheduling list field is structured, and the scheduling list type field can indicate one of the values ​​specified in Table 8.

[0321] Scheduling List Type Field Values ​​Scheduling List Field Types 0 Per-slot Scheduling 1 Consecutive slot scheduling 2 Bitmap-based slot scheduling 3 Periodic scheduling 4 RSF scheduling 5-7 Reserved

[0322] Specifically, when per-slot scheduling is used, each scheduling list element can schedule one slot for a device.

[0323] When sequential slot scheduling is used, each scheduling list element can schedule one slot for a device. Since scheduling list elements do not have a slot index field, slots can be scheduled in sequential order. For example, a slot following a slot in which a control message is transmitted can be scheduled for the device specified in the first scheduling list element. There can be no empty slots between scheduled slots.

[0324] When bitmap-based slot scheduling is used, multiple slots can be scheduled for a device using a single scheduling list element. The bitmap in each scheduling list element can represent the pattern of slots scheduled for a single device.

[0325] When periodic scheduling is used, multiple slots can be scheduled for a device using a single scheduling list element. The pattern of scheduled slots can be expressed by the number of scheduling repetitions and the size of the scheduling step.

[0326] When RSF scheduling is used, multiple slots can be scheduled for a device using a single scheduling list element. In a slot, devices must transmit an RSF according to the scheduling list element, and the composition of the RSF can be determined by the scheduling list element.

[0327] The address size field can specify the size of the sender address field and the receiver address field. For the sender address field and the receiver address field, if the address size is 0 (zero), a short address must be used, and if the address size is 1, an extended address must be used. Here, a short address means a 2-octet-based, i.e., 2-byte-based address, and an extended address can mean an 8-octet-based, i.e., 8-byte-based address.

[0328] The recipient address presence field can be 1 if it means the recipient address field exists, or 0 if it means the recipient address field does not exist.

[0329] The format of the scheduling list field may be determined by the scheduling list type.

[0330] FIG. 20 illustrates the format of a scheduling list element according to the value of the scheduling list type field to which the present disclosure can be applied.

[0331] Referring to FIG. 20, FIG. 20(a) illustrates the format of scheduling list element(s) when the value of the scheduling list type field is 0. The format may include a slot index field and a sender address field.

[0332] Figure 20(b) illustrates the format of scheduling list element(s) when the value of the scheduling list type field is 1. The format may include a sender address.

[0333] Figure 20(c) illustrates the format of scheduling list element(s) when the value of the scheduling list type field is 2. The format may include a scheduling bitmap length field, a bitmap offset presence field, a scheduling bitmap field, a sender address field, a receiver address field, and a bitmap offset field.

[0334] Figure 20(d) illustrates the format of scheduling list element(s) when the value of the scheduling list type field is 3. The format may include a start slot index field, a scheduling step field, a scheduling repetition field, a sender address field, and a receiver address field.

[0335] Figure 20(e) illustrates the format of scheduling list element(s) when the value of the scheduling list type field is 4. The format may include a start slot index field, a scheduling step field, a scheduling repetition field, a sender address field, a receiver address field, a sequence index field, a gap count field, and a sequence repetition field.

[0336] As mentioned above, with respect to the aforementioned scheduling IE, multiple types of scheduling lists can be provided to the devices configuring each slot based on the scheduling list type field.

[0337] FIG. 21 is a diagram showing the difference in time structure for a single application to which the present disclosure can be applied and a combination of various applications.

[0338] For example, to support diverse applications, a new time structure that mixes different blocks is required. For example, a new time structure that mixes ranging techniques based on different slot counts for ranging and DL-TDOA could be considered. To define a flexible time slot structure that accommodates this, it is necessary to allow ranging blocks and ranging rounds to have different durations.

[0339] The example in Fig. 21(a) is an example of an indoor localization use case, and blocks of the same structure may be repeated.

[0340] For a public transportation use case such as the example in Figure 21(b), DL-TDOA operation is required for position measurement when a user approaches a subway gate, ranging operation is required when the user selects a specific gate, and competition for access is required when the user first approaches the gate.

[0341] In the example of Fig. 21(a), the ranging time structure for a single application (e.g., indoor positioning) has the same block duration, and in the example of Fig. 21(b), in a public transportation use case that requires a combination of multiple applications (e.g., DL-TDOA, ranging, and competition), positioning and ranging can be performed more efficiently by supporting different block durations. For each application included in the example of Fig. 21(b), the respective ranging time structures (e.g., scheduling information such as durations for ranging blocks / ranging rounds / ranging slots for configuration) may be different, and it is necessary to define a higher-level time structure to accommodate this as a single service.

[0342] Unlike existing UWB wireless networks where only fixed-length time structures are defined, it is required to define a new time structure, i.e., a flexible time structure, that supports various block durations with flexible lengths.

[0343] Additionally, with respect to the aforementioned scheduling IE, to further enhance the gains, such as power consumption, achievable through scheduling, scheduling may require round / block scheduling, corresponding to longer time periods, in addition to slot-by-slot scheduling. This enables scheduling that is suitable and efficient for the entire UWB time structure.

[0344] That is, there is a need to newly define scheduling information that takes into account a flexible time structure and scheduling information based on units (e.g., rounds, blocks) corresponding to a longer time than slots, and various examples of the present disclosure for the scheduling information are described below.

[0345] FIG. 22 is a drawing for explaining the operation of the first device according to the present disclosure.

[0346] In the example of Fig. 22, the first device may correspond to a controller, and the second device may correspond to a controlee. Additionally, the first device and the second device may correspond to ERDEVs.

[0347] In step S2210, the first device may generate a scheduling information element (IE) for scheduling in a block structure based on one or more ranging rounds.

[0348] For example, the block structure may correspond to a general block-based structure or a hyper block-based structure. As a specific example, if the block structure is based on a hyper block unit composed of one or more ranging blocks, each hyper block includes multiple ranging blocks, and the durations of the multiple ranging blocks may be different. In this case, if one ranging block includes multiple ranging rounds, the durations of the multiple ranging rounds may be the same.

[0349] The scheduling IE may include information indicating the type of scheduling based on ranging round units and scheduling list information related to ranging round unit-based scheduling for each device.

[0350] In this regard, the scheduling list information may include first information indicating the number of rounds scheduled by the scheduling IE. In this case, if the information indicating the number of rounds scheduled is not included in the scheduling list information, the number of rounds scheduled may be recognized / interpreted / considered to be 1. If the number of rounds scheduled is 1, the scheduling IE may be defined / configured to be transmitted for each ranging round.

[0351] Additionally or alternatively, the scheduling list information may include second information in the form of a bitmap representing a pattern of scheduled ranging rounds. Each bit constituting the bitmap may correspond to an index of each ranging round within the block structure.

[0352] In this regard, the scheduling list information may include third information indicating the length of the bitmap. Here, the length of the bitmap may be set to one of 8 bits, 16 bits, 32 bits, or 64 bits. If the number of ranging rounds scheduled by the scheduling IE is smaller than the number of bits constituting the bitmap, bits constituting the bitmap that exceed the number of ranging rounds scheduled may be ignored in the interpretation of the second information.

[0353] Additionally or alternatively, the scheduling list information may include fourth information regarding the device's address. If address indexing based on map information related to the device's address is applied, the fourth information may be set to an index (e.g., a 1-byte-based address index) according to the address indexing. In this case, information indicating whether address indexing is applied may be included in the scheduling IE.

[0354] In step S2220, the first device can transmit a frame including the generated scheduling IE to one or more second devices.

[0355] The time at which a message / frame containing the corresponding scheduling IE is transmitted may be predefined (or fixed) or may be determined by negotiation between the controller and the controlled party.

[0356] For example, the frame including the scheduling IE may be transmitted in one or more of a part or all of a ranging control message (RCM) within the block structure, each ranging round within the block structure, or a ranging round according to the number of ranging rounds scheduled by the scheduling IE within the block structure.

[0357] Additionally, the first device may receive a frame from the second device that includes a specific IE (e.g., an SIR IE, as described below) for soliciting information related to the block structure. Furthermore, in response to the frame that includes the specific IE, the first device may transmit to the second device one or more of information about the block structure (e.g., an HBS IE, as described below) or information for scheduling in the block structure (e.g., block / round / slot-based scheduling information, as described below).

[0358] The method described in the example of FIG. 22 may be performed by the first device (100) of FIG. 1. For example, one or more processors (102) of the first device (100) of FIG. 1 may be configured to generate a scheduling IE for scheduling in a block structure based on one or more ranging rounds and transmit a frame including the scheduling IE to one or more second devices. Furthermore, one or more memories (104) of the first device (100) may store commands for performing the method described in the example of FIG. 22 or the examples described below when executed by one or more processors (102).

[0359] FIG. 23 is a drawing for explaining the operation of a second device according to the present disclosure.

[0360] In step S2310, the second device may receive a frame from the first device including a scheduling IE for scheduling in a block structure based on one or more ranging rounds.

[0361] The specific details of the scheduling IE, block structure (e.g., general block-based structure, hyper block-based structure, etc.), scheduling list information related to ranging round-based scheduling, the frame including the corresponding scheduling IE, the address map and address indexing based thereon, and the specific IE for soliciting scheduling information are the same as those described in the example of FIG. 22, and therefore, redundant descriptions are omitted.

[0362] In step S2320, the second device can determine the ranging round allocated to the second device within the block structure based on the scheduling IE.

[0363] For example, the second device may operate in active mode in rounds allocated to it, and in sleep mode (or inactive mode) in rounds not allocated to it, within the aforementioned block structure (e.g., general block-based structure, hyper block-based structure, etc.).

[0364] The method described in the example of FIG. 23 may be performed by the second device (200) of FIG. 1. For example, one or more processors (202) of the second device (200) of FIG. 1 may be configured to receive a frame from the first device including a scheduling IE for scheduling in a block structure based on one or more ranging rounds, and to determine a ranging round allocated to the second device within the block structure based on the scheduling IE. Furthermore, one or more memories (204) of the second device (200) may store commands for performing the method described in the example of FIG. 23 or the examples described below when executed by one or more processors (202).

[0365] The examples of FIGS. 22 and 23 may correspond to some of the various examples of the present disclosure. Below, various examples of the present disclosure, including the examples of FIGS. 22 and 23, are described in more detail.

[0366] Specifically, the scheduling list types supported by existing scheduling IEs based on FIG. 19 (e.g., see Table 8) correspond to methods for slot-based scheduling, which may be difficult to utilize for round-based and / or block-based scheduling. Furthermore, a procedure for a controlee (or responder) to request and receive such scheduling information at a desired time has not been previously defined.

[0367] To solve these problems, the present disclosure proposes a scheduling method applicable to a flexible time structure / general block time structure (e.g., round scheduling, block scheduling, etc.), and a method / procedure for a controllable entity to solicit and obtain scheduling information.

[0368] In the embodiments described below, HBS IE is used as a representative example as a name of an information element that supports a flexible time structure, but the embodiments described below can be equally applied even when some or all of the various pieces of information described in the present disclosure are included in an IE of a name other than HBS IE.

[0369] Example 1

[0370] This embodiment relates to a method for defining / configuring a scheduling information element (IE) for scheduling for a hyper block structure.

[0371] FIG. 24 illustrates an example of a time structure in a hyper block-based mode according to the present disclosure.

[0372] In the example of Figure 24(a), a hyper block may correspond to a group of blocks. A hyper block-based mode may allow groups of blocks with different settings (e.g., block duration, round duration, slot duration, etc.). A hyper block may be executed based on an interval-based mode or a block-based mode. Different hyper blocks may have the same or different settings.

[0373] As in the example of Fig. 24(b), information about the settings for the hyper block structure can be repeatedly transmitted by the controller via the RCM (or the frame including the block allocation schedule information described above). For this purpose, an HBS (hyper block structure) IE can be defined. For example, the HBS IE can include an index of the corresponding block, a block duration for each of all blocks included in the hyper block, a list of controllables corresponding to each block, etc. A controllable that receives the HBS IE included in the RCM (or the frame including the block allocation schedule information described above) can know that the hyper block structure is applied / progressing, and can know in which block it is performing an operation.

[0374] For hyper block-based mode execution, the controller may transmit an RCM containing an HBS IE (or a frame containing the aforementioned block allocation schedule information) to the controllable(ies) to configure a hyper block. The message / frame containing the HBS IE may be transmitted at the time of transmitting the aforementioned block allocation schedule information. For block configuration, the RCM (or the frame containing the aforementioned block allocation schedule information) of the corresponding block may further include an ARC IE.

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

[0376] FIG. 25 is a diagram showing an example of the HBS IE format according to the present disclosure.

[0377] The scope of the present disclosure is not limited by the name of the HBS IE, and examples of other named IEs transmitted via RCM (or a frame including the block allocation schedule information described above) that include some or all of the information fields described below are included in the scope of the present disclosure.

[0378] The HBS IE of FIG. 25(a) may include information about the duration of each block within a hyperblock and information about the controllee(s) assigned to the corresponding block. The HBS IE may include an associated hyperblock index field, a block description list field for all blocks within the hyperblock, and a content field. A controllee receiving the HBS IE through the RCM (or a frame including the block allocation schedule information described above) can recognize the existence of a hyperblock. In addition, the controllee can know which block within the hyperblock it belongs to and perform ranging through the controllee list field included in the block description list field.

[0379] In the example of Fig. 25(a), the hyper block index field can indicate the index of the hyper block.

[0380] The content control field may include a block duration unit field, a round duration presence field within a block description list element, and a slot duration presence field within a block description list element, as shown in FIG. 25(b).

[0381] The block duration unit field of the content control field can indicate the size of the block duration field as follows.

[0382] Meaning of the value of the block duration unit field 00 The size of the block duration field is 1 octet, and the unit of the block duration field is the number of rounds 01 The size of the block duration field is 2 octets, and the unit of the block duration field is the number of slots 10 The size of the block duration field is 3 octets, and the unit of the block duration field is the number of RSTUs 11 Reserved

[0383] The round duration presence field of the content control field can indicate that a round duration field exists in the block description list element if its value is 1, and that it does not exist if its value is 0.

[0384] The slot duration presence field of the content control field can indicate that the slot duration field exists in the block description list element if its value is 1, and that it does not exist if its value is 0.

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

[0386] The block description list field may contain a list of description(s) for each of the entire blocks belonging to the hyperblock.

[0387] Figure 25(c) shows an example of the format of each of one or more elements included in the block description list.

[0388] The block index field may indicate the index of a block within a hyperblock. The block index may correspond to the index of a block associated with a controllist field within the block description list (i.e., a device belonging to the controllist is allocated).

[0389] The size of the block duration field is determined based on the value of the block duration unit field of the aforementioned content field, and can be set to an unsigned integer value indicating a block duration value based on the unit.

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

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

[0392] To enable the controllable to know the scheduling information of the hyper block, the controller can send a control message (e.g., RCM) to the controllable, including a scheduling IE related to the scheduling of the hyper block structure, together with the HBS IE.

[0393] The scheduling IE format (e.g., scheduling IE content field format) may include a scheduling list length field, a scheduling list type field, an address size field, a receiver address present field, and a scheduling list field of variable size / length.

[0394] Specifically, the scheduling list length field may indicate the number of elements in the scheduling list field. For example, the scheduling list field may include scheduling list elements for the number of devices indicated by the length field. That is, each scheduling list element may include scheduling information for one controllable device.

[0395] The scheduling list type field can specify how the format of the scheduling list field is structured, and the scheduling list type field can indicate one of the values ​​specified in Table 10 below.

[0396] Scheduling List Type Field Values ​​Scheduling List Field Types 0 Per-slot Scheduling 1 Consecutive Slot Scheduling 2 Bitmap-based Slot Scheduling 3 Periodic Scheduling 4 RSF Scheduling 5 Bitmap-based Block Scheduling 6-7 Reserved

[0397] Referring to Table 10, for scheduling of the aforementioned hyper block structure (i.e., hyper block-based mode) proposed in the present disclosure, in addition to the previously defined scheduling list types (i.e., scheduling list types 0 to 4), a scheduling list type (i.e., scheduling list type 5) for block scheduling in a flexible time structure such as the hyper block proposed in the present disclosure can be newly defined. For example, scheduling information according to scheduling list type 5 can be related to scheduling of one or more blocks within a hyper block (e.g., bitmap-based hyper block scheduling).

[0398] When the scheduling list type field in the scheduling IE is set to a value of 5, the scheduling list element format can be configured as shown in FIG. 26.

[0399] FIG. 26 is a diagram illustrating an example of a scheduling list element format related to block scheduling according to an embodiment of the present disclosure.

[0400] Referring to FIG. 26, the scheduling list element format according to scheduling list type 5 may include a block scheduling bitmap length field, a block scheduling bitmap field, and a sender address field.

[0401] For example, the corresponding scheduling list element format may be for block scheduling associated with a structure such as a hyper block. In this case, for example, the block scheduling bitmap length field and the block scheduling bitmap field may also be referred to as a hyper block scheduling bitmap length field and a hyper block scheduling bitmap field.

[0402] Specifically, the Block Scheduling Bitmap Length field indicates the size / length of the Block Scheduling Bitmap field, which may be set to one of the values ​​specified in Table 11 below.

[0403] Block Scheduling Bitmap Length Field Value Size of the Block Scheduling Bitmap Field 08-bit bitmap 116-bit bitmap 232-bit bitmap 364-bit bitmap

[0404] A block scheduling bitmap may be used to set / instruct block-level scheduling for a structure composed of one or more blocks (e.g., a hyper block structure) to a device using a single scheduling list element. That is, a controller can provide a controlee with information about one or more blocks allocated to the controlee within the block structure through the block scheduling bitmap.

[0405] Specifically, a bitmap within each scheduling list element may indicate a pattern of blocks scheduled to a device. In this regard, the block description list element index of the HBS IE, such as in FIG. 25, may be matched with each bit of the corresponding bitmap. For example, the first element of the block description list field of the HBS IE may indicate the same block as the first bit of the corresponding bitmap information. Based on this, a device that receives the HBS IE and the corresponding scheduling IE (e.g., a scheduling IE according to scheduling list type 5) may know the block index and block duration for the block in which it will be active.

[0406] The sender address can represent each participating device.

[0407] As a further example, a scheduling IE according to scheduling list type 5 or a container for block scheduling purposes within a structure such as a hyper block of similar characteristics may be transmitted in an RCM (or a frame including the block allocation schedule information described above) with the same period as the transmission of the HBS IE. If the scheduling IE (e.g., the scheduling IE according to scheduling list type 5) is not transmitted together with the HBS IE, this may mean that it does not contain information for block scheduling within a structure such as a hyper block. Additionally or alternatively, if the scheduling IE is not transmitted together with the HBS IE, this may mean that the recently received scheduling IE (e.g., the scheduling IE according to scheduling list type 5) by the device remains unchanged. In this regard, scheduling IEs (e.g. scheduling IEs according to scheduling list type 5) may be reused and may be set / defined to have an expired time for the scheduling IE and / or the information contained in the scheduling IE.

[0408] As an additional example, in the hyper block-based mode, the block structure may be scheduled based on the RBD (ranging block duration) field, the RRD (ranging round duration) field, and the RSD (ranging slot duration) field included in the ARC IE within the RCM (or the frame including the aforementioned block allocation schedule information). In this case, since the block duration of the blocks within the hyper block can be indicated based on the block description list information included in the HBS IE, the RBD field of the ARC IE included in the RCM (or the frame including the aforementioned block allocation schedule information) transmitted for each block can be omitted, thereby reducing overhead. When the controller sets scheduling to hyper block-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 a ranging round duration and / or a ranging slot duration field, in the ARC IE format of FIG. 12(a), the RBDP (RBD present) bit and / or RRDP (RRD present) bit and / or RSDP (RSD present) bit of the content control field are set to 0, and an ARC IE in which the RBD field and / or the RRD field and / or the RSD field is omitted may be included in the RCM (or a frame including the aforementioned block allocation schedule information).

[0409] Example 1-1

[0410] This embodiment is about a method for defining / applying efficient address indexing.

[0411] For existing scheduling IEs, the address included in the scheduling IE can be expressed based on a 2-octet short address or an 8-octet extended address.

[0412] In this regard, for efficient address indexing, the present disclosure describes various examples of a new addressing scheme based on an address map generated / managed by a specific device (e.g., a controller).

[0413] The address indexing scheme described in this embodiment can be equally applied to all scheduling types that can be indicated by the scheduling list type field, as well as to scheduling types associated with the aforementioned hyper block-based mode (e.g., scheduling list type 5).

[0414] As described above in the present disclosure, a scheduling IE according to scheduling list type 5 may be transmitted in units of hyper blocks together with an HBS IE. In this case, the scheduling list element of the scheduling IE may include address information for all devices operating in the hyper block. Based on this information, the controller may generate an address map for the devices (e.g., controllables scheduled within the hyper block) belonging to the hyper block.

[0415] At this time, the index of the corresponding address map may be assigned based on the list index of the scheduling list element. Therefore, the order of the scheduling list elements may be maintained without being changed on the controllable side when the results transmitted by the controller are transmitted. Using the corresponding address map, the sender address field in the scheduling list element included in the scheduling IE of other types (e.g., types other than scheduling list type 5) that can be transmitted in each ranging round can be optimized.

[0416] A scheduling IE format (e.g., scheduling IE content field format) for applying the above-described address map can be configured as shown in FIG. 27.

[0417] FIG. 27 is a diagram illustrating another example of a scheduling information element (IE) format according to the present disclosure.

[0418] Referring to FIG. 27, the scheduling IE format for address indexing according to the present disclosure can be defined to additionally include an address index field / bit, compared to the scheduling IE format in FIG. 19.

[0419] For example, the address index field / bit may indicate that address indexing using an address map is not used if its value is 0, and that address indexing using an address map is used if its value is 1.

[0420] If the value of the Address Index field / bit is 1, the sender address within the scheduling list element included in the corresponding scheduling IE may be applied based on the sender address index rather than the existing address format (e.g., 2-octet / 8-octet address).

[0421] FIG. 28 is a diagram illustrating an example of a scheduling list element format based on address indexing according to the present disclosure.

[0422] Referring to FIG. 28, compared to the existing scheduling list element format, the 2-octet / 8-octet based sender address can be replaced with a 1-octet based sender address index.

[0423] For example, in the case where address map-based address indexing is applied, FIG. 28(a) illustrates a scheduling list element format according to scheduling list type 0 (e.g., per-slot scheduling), FIG. 28(b) illustrates a scheduling list element format according to scheduling list type 2 (e.g., bitmap-based scheduling), and FIG. 28(c) illustrates a scheduling list element format according to scheduling list type 5 (e.g., bitmap-based hyper block scheduling).

[0424] As mentioned above, with respect to address map-based address indexing, the address index may be applicable to all scheduling list types, not just the scheduling list types associated with the hyperblock-based mode (e.g., scheduling list type 5).

[0425] As a further example, if the controller sends a scheduling IE (based on scheduling list type 5) to the controlee and the address map is shared, and the controlee is further associated with or de-associates from a personal area network (PAN) managed by the controller, and the address map (generated based on scheduling list type 5) needs to be changed, one or more of the following rules may apply:

[0426] - Rule 1. Information about the address map and / or related information may be updated when a subsequent scheduling IE (according to scheduling list type 5) is transmitted (e.g., a subsequent hyper block).

[0427] - Rule 2. If a new controllable is combined before the information about the address map and / or related information is updated, the largest index among the unreserved indexes may be selected and assigned to the new controllable.

[0428] - Rule 3. If a Controlled Party belonging to a PAN is decoupled before the address map and / or related information is updated, the corresponding reserved index may be maintained for a certain period of time. In this regard, the reserved index may be maintained for a certain period of time by setting a timer (e.g., a decoupled lifecycle timer). After the timer expires, the index may be released and reused later.

[0429] - Rule 4. For changes made before the information on the address map and / or related information is updated, the controller may manage the address map by applying rules 2 and 3, and then apply it to subsequent scheduling IEs (according to scheduling list type 5) to share the updated information with the controlled party(ies).

[0430] - Rule 5. The list order of scheduling list elements included in a scheduling IE (according to scheduling list type 5) generated by the controller cannot be arbitrarily changed.

[0431] Example 1-2

[0432] This embodiment is an example of the use of the hyper-block based mode described above.

[0433] Although the examples in this embodiment are described using block scheduling for a hyper-block structure as a representative example, the same can be applied to other types of structures composed of multiple blocks. For example, in the following description, the hyper-block scheduling bitmap length field and the hyper-block scheduling bitmap field can be replaced with (another type of) block scheduling bitmap length field and (another type of) block scheduling bitmap field and applied.

[0434] FIG. 29 is a diagram showing an example of a controllable entity's operation based on hyper block information according to the present disclosure.

[0435] In the hyper block-based mode, a hyper block corresponding to a group of blocks may include ranging blocks for ranging exchange with multiple controllees. The controllees can obtain block indexes, block duration information, etc. within the hyper block to which they belong through information in the HBS IE included in the first RCM (or the frame including the aforementioned block allocation schedule information) of the hyper block. Based on this, each controllee can determine the time for which it operates in the active mode. The example of Fig. 29 shows an example in which five controllees obtain information included in the HBS IE and the scheduling IE (according to scheduling list type 5) through the RCM (or the frame including the aforementioned block allocation schedule information) and apply it to their duty cycle operations.

[0436] In the example of Figure 29, the controller may broadcast an RCM (or a frame including the block allocation schedule information described above) containing an HBS IE (e.g., a block duration (or description) list, a controllee list, etc.) and a scheduling IE (according to scheduling list type 5) at the beginning of the first block (block 0) within a hyperblock in a ranging area network (RAN) 1.

[0437] FIG. 30 is a diagram illustrating an HBS IE and a scheduling IE transmitted within a hyper block according to the present disclosure.

[0438] Referring to FIG. 30, the HBS IE may include block duration information for all ranging blocks within a hyper block, and round duration information for ranging rounds belonging to each ranging block. Additionally, a scheduling IE for scheduling for a hyper block structure (e.g., based on scheduling list type 5) may include multiple controllee lists (e.g., scheduling lists), and each controllee list may include information about the blocks to which the controllee belongs / is allocated in the form of a bitmap (e.g., hyper block scheduling bitmap).

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

[0440] In relation to the hyper block structure, the HBS IE and scheduling IE for performing scheduling for multiple controllable entities are described through a specific example in Fig. 31.

[0441] FIG. 31 is a diagram illustrating an IE included in a control message related to a hyper block structure according to the present disclosure.

[0442] Referring to Figure 31, a case is described assuming that scheduling is performed for five controllable entities within a hyper block.

[0443] In this regard, the RCM (or frame including the block allocation schedule information described above) transmitted by the controller to the controllable in hyper block n-1 may include an HBS IE such as FIG. 31(a) and a scheduling IE such as FIG. 31(b).

[0444] Referring to Fig. 31(b), a scheduling IE set to a bitmap-based hyper-block scheduling type (e.g., scheduling list type 5) may include hyper-block scheduling information for each controllable entity, i.e., scheduling list elements. In this regard, since the example of Fig. 31(b) is a case where the address indexing described above in the present disclosure is not applied (i.e., the value of the address index field is 0), the address information included in each scheduling list element is based on the existing address method.

[0445] By receiving information in the HBS IE and the scheduling IE (according to scheduling list type 5) included in the RCM (or the frame including the block allocation schedule information described above), each controllable entity can know the index of the block to which it belongs within the hyper block, the duration of the block and other block(s), etc.

[0446] For example, Controllee 1 (AA:AA) can know that it belongs to the first block (Block 0) and the second block (Block 1) in the hyper block scheduling bitmap of the scheduling IE. Additionally, Controllee 1 can know the block duration for each block in the block description list of the HBS IE (e.g., the block duration unit is 00, so it is in ranging round units), and can know that its block duration is 2 rounds and 5 rounds by matching the first index (block index 0) and the second index (block index 1). Based on this, the duty cycle can be set for Controllee 1 to remain active during the time corresponding to the first and second blocks, and to remain sleep during the time corresponding to the third block.

[0447] The controllable entity may obtain the ranging round duration information in the ARC IE and / or the round / slot duration information in the block description list of the HBS IE to calculate the time of the block duration of the RCM (or the frame including the block allocation schedule information described above).

[0448] Accordingly, controllable 1 can know that it belongs to block 0 and block 1, and can schedule itself to remain in sleep (or deep sleep) mode during the time corresponding to block 2.

[0449] Controlee 2 can know that it belongs to block 0, block 1, and block 2, and can always maintain the active mode.

[0450] Controllee 3 and Controllee 4 can be known to belong to block 1 and can be scheduled to remain in sleep (or deep sleep) mode during the time corresponding to block 0 block 2.

[0451] Controllee 5 can be known to belong to block 1 and block 2, and can be scheduled to remain in sleep (or deep sleep) mode during the time corresponding to block 0.

[0452] In order to check for updates of control information (e.g., HBS IE via RCM (or a frame including the aforementioned block allocation schedule information), scheduling IE (according to scheduling list type 5), ARC IE, etc.) in the next hyper block, the controllees may remain active for a certain period of time (e.g., the first round of the first block of each hyper block) to receive RCM (or a frame including the aforementioned block allocation schedule information) at the beginning of each hyper block. After that, the controllees (e.g., controllee 1 to controllee 5) may repeatedly perform the aforementioned scheduling operation.

[0453] Additionally or alternatively, a scheduling IE transmitted along with the HBS IE (e.g., a scheduling IE according to scheduling list type 5) may include address information for all devices belonging to the hyper block. In this regard, a method may be possible to generate an address map using the address information and perform address indexing based on the address map. For example, the controller may generate / manage an address map for all devices belonging to the hyper block.

[0454] FIG. 32 is a diagram illustrating an address indexing-based scheduling IE according to the present disclosure.

[0455] Referring to FIG. 32, the address indexing based on the address map can be applied not only to scheduling IEs of the scheduling list type related to the hyper block structure, but also to address information for other types of scheduling IEs.

[0456] For example, the address index field of the scheduling IE (e.g., the scheduling IE according to scheduling list type 0) transmitted in each round within the hyper block structure may be set to 1. In this case, the address information included in the scheduling list element within the corresponding scheduling IE may be configured based on the sender address index. At this time, with respect to the address information, a method of obtaining an address by referencing an address map based on the scheduling IE (e.g., the scheduling IE according to scheduling list type 5) transmitted together with the HBS IE in the first round of the first block within the hyper block may be applied. In this way, the method of transmitting including the sender address index (e.g., 1-octet / byte information) based on the above-described address map has the technical effect of being 1-byte optimized compared to the method of transmitting the existing sender address (e.g., 2 / 8-octet / byte information).

[0457] Additionally or alternatively, as in the examples of the locations of the RCM (or the frame including the block allocation schedule information described above) of FIGS. 30 and 32, the RCM (or the frame including the block allocation schedule information described above) including the HBS IE and the scheduling IE (e.g., the scheduling IE based on the scheduling list type 5 associated with the hyper block structure) according to the present disclosure may be transmitted in the first ranging round for each ranging block of each hyper block. Alternatively, the RCM (or the frame including the block allocation schedule information described above) including the HBS IE and the scheduling IE according to the present disclosure may be transmitted in a specific (e.g., first) ranging round in each of some ranging blocks among the ranging block(s) of each hyper block.

[0458] Example 2

[0459] The scheduling IE in the aforementioned embodiment 1 may be an improved scheduling IE for scheduling in a flexible time structure other than slots, i.e., a hyper block-based mode.

[0460] This embodiment is about a method for improving / defining / applying a scheduling IE to enable scheduling in units of slots, rounds, and blocks, which are UWB time structures, in terms of generalizing it.

[0461] To support block-based scheduling and round-based scheduling, the value of the scheduling list type field included in the scheduling IE can be defined as shown in Table 12.

[0462] Scheduling List Type Field Values ​​Scheduling List Field Types 0 Per-slot Scheduling 1 Consecutive slot scheduling 2 Bitmap-based slot scheduling 3 Periodic scheduling 4 RSF scheduling 5 Bitmap-based block scheduling 6 Bitmap-based round scheduling 7 Reserved

[0463] Referring to Table 12, in addition to the existing scheduling list types 0 to 4 (e.g., see Table 8), bitmap-based block scheduling (scheduling list type 5) and bitmap-based round scheduling (scheduling list type 6) can be additionally defined.

[0464] When the scheduling list type field is 5, the scheduling list format can be configured as shown in FIG. 33.

[0465] FIG. 33 illustrates an example of a scheduling list element format for bitmap-based block scheduling according to the present disclosure.

[0466] Referring to FIG. 33, the scheduling list element format according to scheduling list type 5 of Table 12 may include a block scheduling bitmap length field, a scheduled block length field, a block scheduling bitmap field, and a sender address field.

[0467] The block scheduling bitmap length field indicates the length of the block scheduling bitmap and can be set / defined based on Table 13.

[0468] Block Scheduling Bitmap Length Field Value Size of the Block Scheduling Bitmap Field 08-bit bitmap 116-bit bitmap 232-bit bitmap 364-bit bitmap

[0469] The Scheduled Block Length field indicates the number of blocks scheduled by the corresponding scheduling IE. For example, setting the Scheduled Block Length to 6 may mean that the corresponding scheduling IE schedules 6 blocks based on the current block.

[0470] A block scheduling bitmap can enable a device to schedule one or more blocks using a single scheduling list element.

[0471] Specifically, the bitmap within each scheduling list element may represent a pattern of blocks scheduled to a device. For example, the first block (e.g., Block 0) may correspond to the first bit of the bitmap, the second block (e.g., Block 1) may correspond to the second bit of the bitmap, and the Nth block (e.g., Block N-1) may correspond to the Nth bit of the bitmap.

[0472] By combining the bitmap information with the information about the scheduled block length, a device receiving a scheduling IE according to scheduling list type 5 can determine the block index and block duration to be activated. If the bitmap length is greater than the scheduled block length, the bit(s) exceeding the scheduled block length may be ignored.

[0473] The sender address can represent each participating device.

[0474] Additionally or alternatively, if a flexible time structure (e.g., a hyper-block-based structure) is supported, information related to the scheduled block length can be obtained through another IE (e.g., an HBS IE). Taking this into account, a scheduling list element format such as that shown in FIG. 34 can be configured.

[0475] FIG. 34 illustrates another example of a scheduling list element format for bitmap-based block scheduling according to the present disclosure.

[0476] Referring to FIG. 34, compared to the scheduling list element format in FIG. 33, the scheduled block length field is omitted, and the meaning / definition of other fields is the same as in FIG. 33.

[0477] As mentioned above, the scheduled block length can be obtained through another IE (e.g., HBS IE).

[0478] If the block-related information such as HBS IE is not known because it does not support a flexible time structure (e.g., hyper-block-based structure), the scheduled block length can be determined / considered / set to 1.

[0479] A block scheduling bitmap can enable a device to schedule one or more blocks using a single scheduling list element.

[0480] Specifically, the bitmap within each scheduling list element may represent a pattern of blocks scheduled to a device. For example, the first block (e.g., Block 0) may correspond to the first bit of the bitmap, the second block (e.g., Block 1) may correspond to the second bit of the bitmap, and the Nth block (e.g., Block N-1) may correspond to the Nth bit of the bitmap.

[0481] By combining the bitmap information with the information about the scheduled block length, a device receiving a scheduling IE according to scheduling list type 5 can know the block index and block duration for which it will be activated. If the bitmap length is greater than the scheduled block length, the bit(s) exceeding the scheduled block length may be ignored.

[0482] For example, if there are 5 blocks based on the HBS IE, the block scheduling bitmap length is set to 0 and the block scheduling bitmap can be composed of 8 bits. At this time, the scheduling information is set by matching / mapping the block index within the hyper block for the first 5 bits of the bitmap, and the remaining 3 bits can be ignored. Conversely, if the hyper block-based structure is not supported, the scheduled block length can be 1, and only the first bit of the block scheduling bitmap is used for scheduling, and the remaining bits can be ignored.

[0483] When the scheduling list type field is 6, the scheduling list format can be configured as shown in Fig. 35.

[0484] FIG. 35 illustrates an example of a scheduling list element format for bitmap-based round scheduling according to the present disclosure.

[0485] Referring to FIG. 35, the scheduling list element format according to scheduling list type 6 of Table 12 may include a round scheduling bitmap length field, a scheduled round length field, a round scheduling bitmap field, and a sender address field.

[0486] The Round Scheduling Bitmap Length field indicates the length of the round scheduling bitmap and can be set / defined based on Table 14.

[0487] Round Scheduling Bitmap Length Field Value Size of the Round Scheduling Bitmap Field 08-bit bitmap 116-bit bitmap 232-bit bitmap 364-bit bitmap

[0488] The Scheduled Round Length field indicates the number of rounds scheduled by the corresponding scheduling IE. For example, setting the Scheduled Round Length to 6 may mean that the corresponding scheduling IE performs scheduling for 6 rounds based on the current round.

[0489] A round scheduling bitmap can enable a device to schedule more than one round using a single scheduling (round) list element.

[0490] Specifically, the bitmap within each scheduling list element may represent a pattern of rounds scheduled to a device. For example, the first round (e.g., Round 0) may correspond to the first bit of the bitmap, the second round (e.g., Round 1) may correspond to the second bit of the bitmap, and the Nth round (e.g., Round N-1) may correspond to the Nth bit of the bitmap.

[0491] By combining the bitmap information with the information about the scheduled round length, a device receiving a scheduling IE according to scheduling list type 6 can know the round index in which it will be activated. If the bitmap length is greater than the scheduled round length, the bit(s) exceeding the scheduled round length may be ignored.

[0492] The sender address can represent each participating device.

[0493] Additionally or alternatively, a scheduling list element format, such as that shown in FIG. 36, may be configured, similarly or identically to the aforementioned bitmap-based block scheduling, with the scheduled block length field omitted. Based on this, scheduling may be possible based on whether the device is operating in the current round.

[0494] FIG. 36 illustrates another example of a scheduling list element format for bitmap-based round scheduling according to the present disclosure.

[0495] Referring to FIG. 36, compared to the scheduling list element format in FIG. 35, the scheduled round length field is omitted, and the meaning / definition of other fields is the same as in FIG. 35.

[0496] When a scheduling list element format such as Fig. 36 is applied, the scheduled round length may be determined / considered / set to 1. The round scheduling bitmap may enable a device using a single scheduling list element to schedule the current round. In this case, only the first bit of the round scheduling bitmap is used, and the remaining bits may be ignored.

[0497] Additionally, in relation to the bitmap-based block scheduling and / or bitmap-based round scheduling described above, the address indexing method described above in the present disclosure (e.g., the address indexing method in Example 1-1) may be applied.

[0498] Specifically, when a scheduling IE according to scheduling list type 5 is transmitted, the scheduling list element of the scheduling IE may include address information of all devices operating in blocks equal to the scheduled block length specified in the scheduling list. Additionally or alternatively, when a scheduling IE according to scheduling list type 6 is transmitted, the scheduling list element of the scheduling IE may include address information of all devices operating in rounds equal to the scheduled round length specified in the scheduling list. Using the information, an address map for device(s) belonging to the scheduled block / round may be generated.

[0499] At this time, the index of the corresponding address map can be assigned based on the list index of the scheduling list element. Therefore, the order of the scheduling list elements may be maintained without being changed on the controllable side when the results transmitted by the controller are transmitted. Using the corresponding address map, the sender address field in the scheduling list element included in the scheduling IE of other types that can be transmitted in each block / round (e.g., types other than scheduling list types 5 / 6) can be optimized.

[0500] For example, in the case of a scheduling IE format for applying an address map, an address index field / bit may be added compared to the scheduling IE format illustrated in Fig. 19. The address index field / bit may indicate that address indexing using the address map is not used if its value is 0, and may indicate that address indexing using the address map is used if its value is 1.

[0501] As a concrete example, if the value of the address index field / bit is 1, the sender address in the scheduling list element included in the corresponding scheduling IE may be applied based on the sender address index rather than the existing address format (e.g., 2-octet / 8-octet address).

[0502] FIG. 37 is a diagram illustrating an example of a scheduling list element format based on address indexing according to the present disclosure.

[0503] Referring to Figure 37, compared to the existing scheduling list element format, the 2-octet / 8-octet based sender address can be replaced with a 1-octet based sender address index.

[0504] Fig. 37(a) illustrates the scheduling list element format in the case of scheduling list type 5, and compared to Fig. 33, a sender address index field may be additionally applicable.

[0505] Fig. 37(b) illustrates the scheduling list element format in the case of scheduling list type 6, and compared to Fig. 35, a sender address index field may be additionally applicable.

[0506] Example 2-1

[0507] This embodiment is an example of the use of block / round scheduling in the general block-based mode described above.

[0508] First, examples of the use of block scheduling are described through FIGS. 38 and 39. Although FIGS. 38 and 39 illustrate blocks with different lengths, the proposed method of the present disclosure and the descriptions in the drawings can be equally applied even when the lengths of all blocks are set to be the same.

[0509] FIG. 38 is a diagram illustrating an example of operation of a controllable entity based on block scheduling information in a general block-based mode according to the present disclosure.

[0510] Referring to FIG. 38, if a scheduled block length field does not exist in a scheduling list element format according to scheduling list type 5 related to block scheduling, the controller may transmit a scheduling IE according to scheduling list type 5 for each block. The scheduling IE may have a scheduling list related to scheduling for the block. Based on the received scheduling list, the controllable entity(ies) may determine whether it belongs to the block and perform an active / sleep operation.

[0511] For example, based on the scheduling list element format illustrated in FIG. 38, the controllees operating in block 0 may be AA:AA and BB:BB, the controllees operating in block 1 may be AA:AA, BB:BB, CC:CC, DD:DD, and EE:EE, and the controllees operating in block 2 may be BB:BB and EE:EE.

[0512] FIG. 39 is a diagram illustrating another example of the operation of a controllable entity based on block scheduling information in a general block-based mode according to the present disclosure.

[0513] Referring to FIG. 39, if a scheduled block length field exists in a scheduling list element format according to scheduling list type 5 related to block scheduling, the controller can transmit a scheduling IE according to scheduling list type 5 for each block as many as the set number of blocks to be scheduled. The scheduling IE can have a scheduling list related to scheduling for the corresponding block(s). Based on the received scheduling list, the controllable(s) can determine / confirm the block(s) to which it belongs among the corresponding block(s) and perform an active / sleep operation.

[0514] For example, based on the scheduling list element format illustrated in FIG. 39, for blocks 0 through 2, controllee AA:AA can operate in blocks 0 and 1, controllee BB:BB can operate in blocks 0, 1, and 2, controllee CC:CC can operate in block 1, controllee DD:DD can operate in block 1, and controllee EE:EE can operate in blocks 1 and 2.

[0515] Next, examples of the use of round scheduling are described with reference to FIGS. 40 and 41. Although the lengths of the blocks in FIGS. 40 and 41 are shown to be somewhat different, the proposed method of the present disclosure and the descriptions in the drawings can be equally applied even when the lengths of all rounds are set to be the same.

[0516] FIG. 40 is a diagram illustrating another example of the operation of a controllable entity based on round scheduling information in a general block-based mode according to the present disclosure.

[0517] Referring to FIG. 40, if a scheduled round length field does not exist in a scheduling list element format according to scheduling list type 6 related to round scheduling, the controller may transmit a scheduling IE according to scheduling list type 6 for each round. The scheduling IE may have a scheduling list related to scheduling for the round. Based on the received scheduling list, the controllable entity(ies) may determine whether it belongs to the round and perform an active / sleep operation.

[0518] For example, based on the scheduling list element format illustrated in FIG. 40, the controllees operating in round 0 may be AA:AA and BB:BB, the controllees operating in round 1 may be AA:AA, BB:BB, CC:CC, DD:DD, and EE:EE, and the controllees operating in round 2 may be BB:BB and EE:EE.

[0519] FIG. 41 is a diagram illustrating another example of the operation of a controllable entity based on round scheduling information in a general block-based mode according to the present disclosure.

[0520] Referring to FIG. 41, if a scheduled round length field exists in a scheduling list element format according to scheduling list type 6 related to round scheduling, the controller can transmit a scheduling IE according to scheduling list type 6 for each round unit as many as the set number of rounds to be scheduled. The scheduling IE can have a scheduling list related to scheduling for the round(s). Based on the received scheduling list, the controllable(s) can determine / confirm the round(s) to which it belongs among the round(s) and perform an active / sleep operation.

[0521] For example, based on the scheduling list element format illustrated in FIG. 41, for rounds 0 to 2, controlee AA:AA can operate in rounds 0 and 1, controlee BB:BB can operate in rounds 0, 1, and 2, controlee CC:CC can operate in round 1, controlee DD:DD can operate in round 1, and controlee EE:EE can operate in rounds 1 and 2.

[0522] Example 3

[0523] This embodiment relates to a method in which a controllable entity requests scheduling information and a controller transmits relevant information in response to the request.

[0524] Scheduling IEs can be transmitted round by round in the UWB control phase. For scheduling IEs according to scheduling list type 5 (i.e., bitmap-based round scheduling type) and / or scheduling list type 6 (i.e., bitmap-based round scheduling type) in Table 12, the scheduling IE may be transmitted only once across multiple blocks depending on the scheduled round length. Additionally, when operating in hyper block-based mode, the HBS IE and the scheduling IE (i.e., scheduling IE according to scheduling list type 5 in Table 10) may be transmitted in the first round of the first block of a hyper block.

[0525] In this case, during the scheduling operation for slot(s) / block(s) / round(s) or the scheduling operation for hyperblock(s), there may be a newly joining controlee (or responder) or a controlee that fails to receive the scheduling IE. In this case, the controlee may not be able to obtain slot / block / round scheduling information until the next scheduling is established. In addition, there may be a case where information such as an address map that can be obtained based on the slot / block / round scheduling information is not obtained.

[0526] Therefore, a method is needed in which the controllable requests (solcits) slot / block / round scheduling information and / or information on the hyper block structure (e.g., HBS IE) to the controller to obtain related information.

[0527] In this regard, in the present disclosure, an IE for the controlled entity to request the corresponding information (hereinafter, referred to as SIR (scheduling information request) IE for clarity of explanation) may be defined.

[0528] Specifically, the controllable entity requests scheduling information from the controller via the SIR IE, and the controller, upon receiving the request, can be configured / defined to transmit information about time structures (e.g., hyper block-based structures, general block-based structures, etc.) and device scheduling, etc., to the controllable entity. At this time, the controller can transmit / provide the information via the HBS IE, scheduling IE, ARC IE, RDM IE, RR IE, etc. The controllable entity, upon receiving the information from the controller, can obtain its own scheduling information, information related to an address map for address indexing, etc., based on the information. Through this, the controllable entity can actively obtain and utilize information before the controller announces the next configuration.

[0529] FIG. 42 is a diagram showing an example of an operation based on SIR IE according to the present disclosure.

[0530] Referring to FIG. 42, it is assumed that in a hyper block-based structure, a controller transmits an HBS IE and a scheduling IE (e.g., a scheduling IE according to scheduling list type 5 of Table 10) to the controllable(s) in the first round of the first block within each hyper block.

[0531] For example, the controller may send the HBS IE and the scheduling IE to the controllees via the first control message (e.g., RCM, etc.) in the hyper block. At this time, if a specific controllee (e.g., controllee CC:CC) fails to receive the HBS IE and / or the scheduling IE, the controllee may fail to interpret the address (index) information included in / based on the scheduling IE, and the operation may fail (S4210).

[0532] At this time, the controllable entity recognizes that it needs scheduling information, and based on this, can request scheduling information from the controller through the SIR IE (S4220).

[0533] The controller that receives the SIR IE can transmit a control message (e.g., RCM, etc.) including the HBS IE and / or the scheduling IE to the controlee in the control phase of the next round (S4230).

[0534] The controlee that receives the control message obtains scheduling information and address map-related information and can recover the operation (S4240).

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

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

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

[0538] Unlike the scheduling methods in existing UWB wireless network systems, the present disclosure proposes a block-based scheduling method for a flexible time structure such as a hyper block, a block / round-based scheduling method for a general block structure, and a solicitation procedure for scheduling information. Through this, the controller can efficiently schedule the controlee, and the controlee can check the blocks / rounds assigned / designated to it within the structure, thereby achieving the technical effect of efficiently performing transitions to and maintaining slotted mode or active mode.

[0539] The embodiments described above are combinations of components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form embodiments of the present disclosure by combining some components and / or features. 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 self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form embodiments or incorporated as new claims through post-application amendments.

[0540] It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential characteristics thereof. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present disclosure are intended to be included within the scope of the present disclosure.

[0541] The scope of the present disclosure includes software or machine-executable instructions (e.g., an operating system, an application, firmware, a program, etc.) that cause operations according to the methods of various embodiments to be executed on a device or a computer, and a non-transitory computer-readable medium having such software or instructions stored thereon and executable on the device or computer. Instructions that can be used to program a processing system to perform the features described in the present disclosure can be stored on / in a storage medium or a computer-readable storage medium, and a computer program product including such a storage medium can be used to implement the features described in the present disclosure. The storage medium can 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 can 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. The memory optionally includes one or more storage devices remotely located from the processor(s). The memory or, alternatively, the non-volatile memory device(s) within the memory comprise a non-transitory computer-readable storage medium. The features described in this disclosure may be incorporated into software and / or firmware stored on any of the machine-readable media, which may control the hardware of the processing system and allow the processing system to interact with other mechanisms that utilize results according to 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.

[0542] The method proposed in this disclosure has been described with a focus on examples applied to IEEE 802.15.4-based systems, but can be applied to various UWB wireless networks or wireless communication systems in addition to IEEE 802.15.4-based systems.

Claims

1. A method performed by a first device in an ultra-wideband (UWB) wireless network system, the method comprising: A step of generating, by the first device, a scheduling information element (IE) for scheduling in a block structure based on one or more ranging rounds; and A step of transmitting a frame including the above scheduling IE to one or more second devices, A method wherein the above scheduling IE includes information indicating a type of scheduling based on ranging round units and scheduling list information related to scheduling based on ranging round units for each device.

2. In paragraph 1, A method wherein the scheduling list information includes first information indicating the number of ranging rounds scheduled by the scheduling IE.

3. In paragraph 2, Based on the fact that the first information is not included in the scheduling list information, the number of scheduled ranging rounds is 1, A method wherein the above scheduling IE is defined to be transmitted by the first device in every ranging round.

4. In paragraph 1, The above scheduling list information includes second information in the form of a bitmap representing a pattern of scheduled ranging rounds, A method wherein each bit constituting the bitmap corresponds to an index of each ranging round within the block structure.

5. In paragraph 4, The above scheduling list information includes third information indicating the length of the bitmap, A method wherein the length of the above bitmap is one of 8-bits, 16-bits, 32-bits, or 64-bits.

6. In paragraph 4, A method in which, based on the fact that the number of ranging rounds scheduled by the scheduling IE is less than the number of bits constituting the bitmap, bits constituting the bitmap that exceed the number of ranging rounds scheduled are ignored in the interpretation of the second information.

7. In paragraph 1, The above scheduling list information includes fourth information about the address of the device, A method in which the fourth information is set as an index according to the address indexing, based on address indexing based on map information related to the address of the device.

8. In paragraph 7, A method in which information indicating whether the above address indexing is applied is included in the above scheduling IE.

9. In paragraph 1, After transmitting the frame, receiving a frame including a specific IE for soliciting information related to the block structure from a second device; and A method further comprising the step of transmitting, in response to a frame including the specific IE, at least one of information about the block structure and information for scheduling in the block structure to the second device.

10. In paragraph 1, The above block structure is based on a hyper block unit consisting of one or more ranging blocks, A method wherein each hyper block includes multiple ranging blocks, wherein the durations of the multiple ranging blocks are different.

11. In paragraph 10, A method wherein a single ranging block includes multiple ranging rounds, wherein the durations of the multiple ranging rounds are the same.

12. In paragraph 1, The frame including the above scheduling IE: Part or all of the RCM (ranging control message) within the above block structure, Each ranging round within the above block structure, or Ranging rounds according to the number of ranging rounds scheduled by the scheduling IE within the block structure A method in which one or more of the following are transmitted:

13. In paragraph 1, The above first device corresponds to a controller, The above second device corresponds to a controlee, method.

14. In a first device device in an ultra-wideband (UWB) wireless network system, the device: one or more transmitters and receivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Generating, by the first device, a scheduling information element (IE) for scheduling in a block structure based on one or more ranging rounds; Set to transmit a frame including the above scheduling IE to one or more second devices, The above scheduling IE is a device including information indicating a type of scheduling based on ranging round units and scheduling list information related to scheduling based on ranging round units for each device.

15. A method performed by a second device in an ultra-wideband (UWB) wireless network system, the method comprising: A step of receiving, from a first device, a frame including a scheduling information element (IE) for scheduling in a block structure based on one or more ranging rounds; and A step of checking a ranging round allocated to the second device within the block structure based on the scheduling IE, A method wherein the above scheduling IE includes information indicating a type of scheduling based on ranging round units and scheduling list information related to scheduling based on ranging round units for each device.

16. In a second device device in an ultra-wideband (UWB) wireless network system, the device: one or more transmitters and receivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Receive, from a first device, a frame including a scheduling information element (IE) for scheduling in a block structure based on one or more ranging rounds; Based on the above scheduling IE, a ranging round allocated to the second device within the block structure is set to be confirmed, The above scheduling IE is a device including information indicating a type of scheduling based on ranging round units and scheduling list information related to scheduling based on ranging round units for each device.

17. A processing device configured to control a device in an ultra-wideband (UWB) wireless network system, wherein the processing device: one or more processors; and A processing device comprising one or more computer memories operatively connected to said one or more processors and storing instructions for performing a method according to any one of claims 1 to 13 based on execution by said one or more processors.

18. One or more non-transitory computer-readable media storing one or more instructions, A computer-readable medium, wherein the one or more commands are executed by one or more processors to control a device in an ultra-wideband (UWB) wireless network system to perform a method according to any one of claims 1 to 13.

Citation Information

Patent Citations

  • Control of ranging initiators and responders in an UWB network

    US20200200862A1

  • Electronic device for performing ranging by using ultra-wide band and operation method thereof

    US20210173066A1