Method and apparatus for transmitting or receiving hyperblock structure-based scheduling information in an ultra-wideband wireless network system

Abstract

A method and apparatus for transmitting or receiving hyperblock structure-based scheduling information in an ultra-wideband wireless network system is disclosed. A method performed by a first device in an ultra-wideband (UWB) wireless network system according to one embodiment of the present disclosure may include the steps of: generating a first information element (IE) containing information about a block structure set in one or more ranging blocks, and a second IE for scheduling in the block structure; and transmitting a frame containing the first IE and the second IE to one or more second devices. Here, the second IE may include an element for each device containing ranging block-based scheduling information within the block structure.

Description

Technical Field

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

Background Art

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

[0003] Ultra-wideband (UWB) wireless networks can help transmit large amounts of information at low power over a very wide bandwidth (e.g., a frequency band of 3.1 GHz to 10.6 GHz). For example, UWB technology can help convert digital coded information into impulse signals with very short time durations of less than nanoseconds and transmit them wirelessly. Ultra-wideband (UWB) technologies related to ranging technology are defined in the IEEE 802.15.4z standard. For example, the IEEE 802.15.4z standard includes HRP (high-rate pulse frequency) PHY technology that supports high-speed data communication (e.g., 27-31 Mbps) and accurate two-way ranging and positioning, and LRP (low-rate pulse frequency) PHY technology that supports various modes for low-speed data communication (e.g., RFID (Radio Frequency Identification) applications). The IEEE 802.15.4z standard includes UWB PHY technology to improve the integrity and accuracy of ranging measurements, and MAC technology to support the exchange of ranging-related information between devices participating in ranging and the control of the TOF (time-of-flight) ranging procedure. Currently, the IEEE 802.15.4ab standard is under discussion for further advancements to UWB PHY / MAC, including improvements to the IEEE 802.15.4z standard-based wireless network technology. [Overview of the project] [Problems that the invention aims to solve]

[0004] The technical problem addressed by this disclosure is to provide a method and apparatus for transmitting or receiving hyperblock structure-based scheduling information in a UWB wireless network system.

[0005] A further technical challenge of this disclosure is to provide a method and apparatus for defining or applying address indexing in a UWB wireless network system.

[0006] The technical challenges addressed in this disclosure are not limited to those mentioned above, and other technical challenges not mentioned will be clearly understood by those with ordinary skill in the art to which this disclosure pertains from the following description. [Means for solving the problem]

[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 the steps of: generating a first information element (IE) that includes (composes; constructs; sets up; encloses; includes; contains; has) information about a block structure set up in one or more ranging blocks, and a second IE for scheduling in the block structure; and transmitting a frame containing the first IE and the second IE to one or more second devices, wherein the second IE may include an element for each device that includes ranging block-based scheduling information within the block structure.

[0008] A method performed by a second device in an ultra-wideband (UWB) wireless network system according to a further aspect of the present disclosure may include the steps of: receiving from the first device a frame including a first information element (IE) containing information about a block structure set in one or more ranging blocks and a second IE for scheduling within the block structure; and determining, based on the first IE and the second IE, which ranging blocks to be assigned to the second device within the block structure, where the second IE may include an element for each device containing ranging block-based scheduling information within the block structure.

[0009] A method performed by a first device in an ultra-wideband (UWB) wireless network system according to a further aspect of the present disclosure may include the steps of: generating a scheduling information element (scheduling IE) for scheduling to one or more second devices; and transmitting a frame containing the scheduling IE to the one or more second devices, wherein the scheduling IE may include fields for one or more scheduling list elements for the one or more second devices. The scheduling IE may further include information indicating whether map information-based address indexing is applicable, based on the existence of map information associated with the device addresses.

[0010] A method performed by a second device in an ultra-wideband (UWB) wireless network system according to a further aspect of the present disclosure may include the steps of receiving a frame from a first device that includes a scheduling IE for scheduling the second device, and obtaining the scheduling IE based on decoding of the frame, wherein the scheduling IE may include fields for one or more scheduling list elements for one or more second devices. The scheduling IE may further include information indicating whether or not map information-based address indexing is applicable, based on the existence of map information associated with the device addresses. [Effects of the Invention]

[0011] According to this disclosure, a method and apparatus for transmitting or receiving hyperblock structure-based scheduling information in a UWB wireless network system can be provided.

[0012] This disclosure provides a method and apparatus for defining or applying address indexing in a UWB wireless network system.

[0013] The effects derived from this disclosure are not limited to those mentioned above, and any other effects not mentioned above will be clearly understood by a person with ordinary skill in the art to which this disclosure pertains from the following description. [Brief explanation of the drawing]

[0014] The accompanying drawings, included as part of the detailed description to aid in understanding this disclosure, provide examples of the disclosure and illustrate the technical features of the disclosure together with the detailed description. [Figure 1] This is a block diagram illustrating an example of a wireless communication device according to one embodiment of the present disclosure. [Figure 2] This is a diagram illustrating the HRP UWB PPDU format to which this disclosure applies. [Figure 3] This figure shows the RMARKER location based on STS packet configuration in the HRP-ERDEV PPDU format to which this disclosure can be applied. [Figure 4] This is a diagram illustrating a two-way ranging method to which this disclosure can be applied. [Figure 5] This figure illustrates examples of RMI IE, RCPCS IE, RRMC IE, and RRTI IE formats to which this disclosure applies. [Figure 6] This is an example of a message sequence chart for an SS-TWR to which deferred response time results applicable to this disclosure can be applied. [Figure 7] This is an example of a message sequence chart for an SS-TWR to which embedded response time results applicable to this disclosure are to be applied. [Figure 8] This is an example of a message sequence chart for SS-TWR using SP3 packets to which this disclosure can be applied. [Figure 9] An example of a message sequence chart for DS-TWR to which the extended response time information applicable to the present disclosure is applied. [Figure 10] An example of a message sequence chart for DS-TWR to which the embedded ranging time information applicable to the present disclosure is applied. [Figure 11] A diagram for explaining the role of a device in a ranging procedure to which the present disclosure is applicable. [Figure 12] A diagram showing an example of the formats of ARC IE, RDM IE, RBU IE, RR IE, and SRRE IE to which the present disclosure is applicable. [Figure 13] A diagram for explaining the ranging block structure and ranging phases to which the present disclosure is applicable. [Figure 14] An example of a timing diagram for various multi-device rangings to which the present disclosure is applicable. [Figure 15] A timing diagram in an example of a block-based mode to which the present disclosure is applicable. [Figure 16] A diagram for explaining examples for various transmission offsets to which the present disclosure is applicable. [Figure 17] An example of a message sequence chart for one-to-many SS-TWR to which the present disclosure is applicable. [Figure 18] An example of a message sequence chart for SP3 one-to-many SS-TWR to which the present disclosure is applicable. [Figure 19] A diagram showing the difference in time structure for the case of one application and combinations of various applications to which the present disclosure is applicable. [Figure 20] A diagram for explaining the operation of the first device according to the present disclosure. [Figure 21] A diagram for explaining the operation of the second device according to the present disclosure. [Figure 22] A diagram showing an example of the time structure in the hyper block-based mode according to the present disclosure. [Figure 23] This figure shows an example of the HBS IE format related to this disclosure. [Figure 24] This figure shows an example of the scheduling information element (IE) format related to this disclosure. [Figure 25] This figure shows an example of a scheduling list element format related to block scheduling according to an embodiment of the present disclosure. [Figure 26] This is a diagram illustrating the operation of the first device related to this disclosure. [Figure 27] This is a diagram illustrating the operation of the second device related to this disclosure. [Figure 28] This figure shows another example of the scheduling information element (IE) format related to this disclosure. [Figure 29] This figure shows an example of the address indexing-based scheduling list element format relating to this disclosure. [Figure 30] This figure shows an example of the controlled user's actions based on the hyperblock information related to this disclosure. [Figure 31] This figure illustrates HBS IE and scheduling IE transmitted within the hyperblock relating to this disclosure. [Figure 32] This figure illustrates an example of an IE included in a control message related to the hyperblock structure described herein. [Figure 33] This figure illustrates an address indexing-based scheduling IE related to this disclosure. [Modes for carrying out the invention]

[0015] Preferred embodiments relating to this disclosure will be described in detail below with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to illustrate exemplary embodiments of this disclosure and is not intended to represent the only possible embodiments of this disclosure. The detailed description below includes specific details to provide a complete understanding of this disclosure. However, those skilled in the art will understand that this disclosure is implementable without such specific details.

[0016] In some cases, to avoid ambiguity of the concepts in this disclosure, known structures and devices may be omitted, or they may be shown in the form of block diagrams focusing on the core function of each structure and device.

[0017] In this disclosure, when one component is “connected,” “joined,” or “linked” to another component, this may include not only a direct connection but also an indirect connection in which other components exist between them. Also, in this disclosure, the terms “includes” or “have” identify the presence of the referred features, stages, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, stages, operations, elements, components and / or groups thereof.

[0018] In this disclosure, terms such as "first," "second," etc., are used solely to distinguish one component from another, and are not used to limit the components, nor do they limit the order or importance of the components unless specifically mentioned. Therefore, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0019] The terms used in this disclosure are for illustrative purposes relating to specific embodiments and are not intended to limit the scope of the claims. As used in the description of the embodiments and in the attached claims, singular forms are intended to include plural forms unless otherwise specified in the context. The terms "and / or" used in this disclosure may refer to one of the related enumerated items, or to any and all possible combinations of two or more of them. In this disclosure, a " / " between words has the same meaning as "and / or" unless otherwise specified.

[0020] The examples in this disclosure may apply to a variety of wireless communication systems. For example, the examples in this disclosure may apply to IEEE 802.15 standard-based wireless networks (e.g., Zigbee, Bluetooth, etc.). In particular, the examples in this disclosure may apply to IEEE 802.15.4 standard-based wireless networks, and further, to newly proposed IEEE 802.15.4ab standard-based UWB wireless networks, or next-generation UWB wireless networks following IEEE 802.15.4ab. The wireless communication systems to which the examples in this disclosure apply are not limited to IEEE 802.15 series wireless networks, but may also apply to IEEE 802.11 series wireless local area network (WLAN) technologies or Wi-Fi technologies, and may also apply to cellular wireless communication systems (e.g., 3GPP (3rd Generation Partnership Project: registered trademark: hereinafter the same) standard LTE (Long Term Evolution) series technologies and 5G NR (New Radio), etc.).

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

[0022] The following describes the technical features to which the examples in this disclosure may apply.

[0023] Figure 1 is a block diagram illustrating an example of a wireless communication device according to one embodiment of the present disclosure.

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

[0025] When devices 100 and 200, as illustrated in Figure 1, assist in ranging, they can be called RDEVs (ranging-capable devices) or ERDEVs (enhanced ranging-capable devices). For example, devices 100 and 200, as illustrated in Figure 1, can be referred to by various terms such as transmitting device, receiving device, transmitting RDEV, receiving RDEV, transmitting ERDEV, and receiving ERDEV. For example, devices 110 and 200 can be called initiator, responder, originator, recipient, controller, or controlee depending on their role in ranging operations. The role of a single device is not fixed and may be determined relatively by its relationship with other devices. When a single device interacts with multiple devices, that single device can also assume various roles.

[0026] Referring to Figure 1, the first device 100 and the second device 200 can send and receive radio signals using various UWB wireless network technologies (e.g., the IEEE 802.15.4 series). The first device 100 and the second device 200 may include interfaces to the medium access control (MAC) layer and the physical layer (PHY) in accordance with the IEEE 802.15.4 standard. The IEEE 802.15.4-based PHY and MAC are included in the UWB subsystem, which may further include a UWB command interface (UCI) that acts as an interface between the UWB controller and the host. The UWB subsystem can exchange messages with the host system via the UCI.

[0027] Furthermore, the first device 100 and the second device 200 can also further support various communication standards other than UWB wireless network technology (e.g., IEEE 802.15 series, IEEE 802.11 series, 3GPP LTE series, 5G NR series standards, etc.). The devices of this disclosure may also be embodied in various devices such as mobile phones, vehicles, personal computers, AR (Augmented Reality) equipment, VR (Virtual Reality) equipment, etc. The devices of this specification can also support various communication services such as voice calls, video calls, data communication, autonomous driving, MTC (Machine-Type Communication), M2M (Machine-to-Machine), D2D (Device-to-Device), and IoT (Internet-of-Things).

[0028] The 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 may control the memories 104 and / or the transceivers 106 and be configured to embody the descriptions, functions, procedures, suggestions, methods and / or operation diagrams of this disclosure. For example, the processor 102 may process information in the memory 104 to generate first information / signals and then transmit a radio signal containing the first information / signals via the transceiver 106. Alternatively, the processor 102 may receive a radio signal containing second information / signals via the transceiver 106 and then store information obtained from signal processing of the second information / signals in the memory 104. The memory 104 may be linked to the processor 102 and can store various information relating to the operation of the processor 102. For example, memory 104 may store software code that executes some or all of a process controlled by processor 102, or that contains instructions for executing the descriptions, functions, procedures, suggestions, methods and / or operation sequence diagrams in this disclosure. Here, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to embody UWB wireless network technology (e.g., IEEE 802.15.4 series). Transceiver 106 may be coupled with processor 102 and can transmit and / or receive radio signals via one or more antennas 108. Transceiver 106 may include a transmitter and / or receiver. Transceiver 106 may be used synonymously with RF (Radio Frequency) unit. In this disclosure, device may also mean communication modem / circuit / chip.

[0029] 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 may control the memories 204 and / or the transceivers 206 and be configured to embody the descriptions, functions, procedures, suggestions, methods and / or operation sequence diagrams disclosed herein. For example, the processor 202 may process information in the memory 204 to generate third information / signals and then transmit a radio signal containing the third information / signals via the transceiver 206. Alternatively, the processor 202 may receive a radio signal containing fourth information / signals via the transceiver 206 and then store information obtained from signal processing of the fourth information / signals in the memory 204. The memory 204 may be linked to the processor 202 and can store various information related to the operation of the processor 202. For example, memory 204 may store software code that executes some or all of the processes controlled by processor 202, or that contains instructions for executing the descriptions, functions, procedures, suggestions, methods and / or operation sequence diagrams disclosed in this disclosure. Here, processor 202 and memory 204 may be part of a communications modem / circuit / chip designed to embody UWB wireless network technology (e.g., IEEE 802.15.4 series). Transceiver 206 may be coupled with processor 202 and can transmit and / or receive radio signals via one or more antennas 208. Transceiver 206 may include a transmitter and / or receiver. Transceiver 206 may be used synonymously with RF unit. In this disclosure, device may also mean communications modem / circuit / chip.

[0030] The hardware elements of devices 100,200 are described in more detail below. However, one or more protocol layers may be embodied by one or more processors 102,202. For example, one or more processors 102,202 can embodied one or more layers (e.g., functional layers such as PHY and MAC). One or more processors 102,202 can generate one or more PDUs (Protocol Data Units) and / or one or more SDUs (Service Data Units) by means of the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams in this disclosure. One or more processors 102,202 can generate messages, control information, data, or information by means of the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams in this disclosure. One or more processors 102,202 can generate signals (e.g., baseband signals) containing PDUs, SDUs, messages, control information, data, or information by the functions, procedures, proposals and / or methods of this disclosure and provide them 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 by the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams of this disclosure.

[0031] One or more processors 102,202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102,202 may be embodied by hardware, firmware, software, or a combination thereof. For example, one or more ASICs (Application Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field Programmable Gate Arrays) may be included in one or more processors 102,202. The descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams disclosed in this disclosure may be embodied using firmware or software, and the firmware or software may be embodied to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and / or sequence diagrams disclosed in this disclosure may be contained in 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, suggestions, methods and / or sequence diagrams disclosed in this disclosure may be embodied by firmware or software in the form of code, instructions and / or sets of instructions.

[0032] One or more memories 104,204 may be connected to one or more processors 102,202 and can store various forms of data, signals, messages, information, programs, code, instructions and / or commands. One or more memories 104,204 may consist of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media and / or combinations thereof. One or more memories 104,204 may be located inside and / or outside of one or more processors 102,202. Furthermore, one or more memories 104,204 may be connected to one or more processors 102,202 by various technologies such as wired or wireless connections.

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

[0034] For example, the transceivers 106 and 206 in Figure 1 can perform the transmission and reception of signals (e.g., packets or PPDUs (Physical Layer Protocol Data Units) conforming to IEEE 802.15.4, etc.). Furthermore, in this disclosure, the operation of various devices generating transmission and reception signals or performing data processing and calculations in advance for transmission and reception signals may be performed by the processors 102 and 202 in Figure 1. For example, an example of the operation of generating transmission and reception signals or performing data processing and calculations in advance for transmission and reception signals may include: 1) determining / acquiring / composing / calculating / decoding / encoding bit information of fields contained in a PPDU; 2) determining / composing / acquiring time resources, frequency resources, etc., used for fields contained in a PPDU; 3) determining / composing / acquiring specific sequences, etc., used for fields contained in a PPDU; 4) power control operations and / or power saving operations applied to the device; and 5) operations related to determining / acquiring / composing / calculating / decoding / encoding ACK signals, etc. Furthermore, in the following example, various pieces of information used by various devices for determining / acquiring / composing / calculating / decoding / encoding transmit and receive signals (e.g., information related to fields / subfields / control fields / parameters / power, etc.) may be stored in memories 104,204 in Figure 1.

[0035] In the UWB band, devices can access the medium based on the CSMA / CA (Carrier Sense Multiple Access with Collision Avoidance) mechanism. The CSMA / CA mechanism allows a device to perform a Clear Channel Assessment (CCA) to sense the radio channel or medium over a predetermined time interval before starting transmission. Sensing may be performed, for example, by an energy detection (ED) method based on a predetermined threshold. If the sensing results in the medium being determined to be idle, the device will start transmitting through that medium. On the other hand, if the medium is sensed to be occupied or busy, the device will not start transmitting and can set a delay period for medium access (e.g., a random backoff period) and wait before attempting to transmit. By applying a random backoff period, multiple devices are expected to attempt to transmit after waiting for different periods of time, thus minimizing collisions.

[0036] Furthermore, when the superframe structure is applied, the slotted CSMA-CA mechanism may be applied to data transmission during the contention access period (CAP) of the active portion of the interval between beacons. The CSMA-CA mechanism does not need to be applied to data transmission within the active portion and during the contention free period (CFP). When the superframe structure is not applied, the unslotted CSMA-CA mechanism may be applied to the transmission of all data frames except the ACK frame in response to a data request command.

[0037] Range measurement

[0038] Ranging includes measuring the distance between the two devices, and a device with ranging capability can be called an RDEV (ranging-capable device) or an ERDEV (enhanced ranging-capable device).

[0039] Figure 2 is a diagram illustrating the HRP UWB PPDU format to which this disclosure can be applied.

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

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

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

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

[0044] In Figure 2(d), convolutional encoding is applied to generate an encoded PHY payload field, and in Figure 2(e), spreading may be applied to the PHY payload field.

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

[0046] In Figure 2(g), modulation is applied to the SHR, PHR, and PHY payload fields, and the PPDU encoding procedure is completed. The base coding rate may be applied to the SHR field.

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

[0048] Figure 3 shows the RMARKER location based on STS packet configuration in the HRP-ERDEV PPDU format to which this disclosure can be applied.

[0049] The STS (Scrambled timestamp sequence) field may contain a sequence of pseudo-randomized pulses. For example, the STS may contain a sequence of AES (Advanced Encryption Standard)-128-based pseudo-random pulses, which may be used for accurate positioning in spread spectrum-based positioning techniques in UWB communications.

[0050] The PPDU STS packet structure may differ depending on whether or not it includes an STS field and its position.

[0051] Figure 3(a) shows the format corresponding to STS packet configuration 0 (i.e., the PPDU does not have an STS field). This format may be defined as mandatory.

[0052] Figure 3(b) shows the format corresponding to STS packet configuration 1 (i.e., the STS field is located immediately after the SFD field and before the PHR field). This format may be mandatory.

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

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

[0055] The PPDU format shown in the example in Figure 3 can also be called the HRP-ERDEV PPDU format. In Figure 3, the arrows indicate the RMARKER (ranging marker) reference position in each format. The RMARKER can serve as the basis for timestamp measurement or ranging counter.

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

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

[0058] Ranged capacity may be enabled in 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 instructions or parameters exchanged between entities in a layer or sublayer within a single device. For example, an originator may request ranging capacity using the MCPS-DATA.request primitive, and ranging capacity may be activated in the recipient using the MLME-RX-ENABLE.request primitive.

[0059] Range and localization method

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

[0061] Figure 4 is a diagram illustrating a two-way ranging method to which this disclosure may be applied.

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

[0063] Each device precisely measures the transmission and reception times of message frames, allowing T_round and T_reply to be calculated by simple subtraction. The resulting TOF can be estimated as ^T_prop using the following formula.

[0064]

number

[0065] If a device can estimate the relative clock offset between itself and a remote device, the accuracy of the Time of Flight (TOF) can be improved by the following formula:

[0066]

number

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

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

[0069] Each device precisely measures the transmission and reception times of message frames, allowing T_round and T_reply to be calculated by simple subtraction. The resulting TOF can be estimated as ^T_prop using the following formula.

[0070]

number

[0071] The example in Figure 4(c) corresponds to a DS-TWR using four messages in Figure 4(b) but reduced to three messages. That is, the response to the first round-trip time measurement may be used as the start message for the second round-trip time measurement.

[0072] Next, the TDOA method will be described. TDOA is a method for locating wireless devices (e.g., radio frequency identification (RFID) devices) based on the relative arrival times of single or multiple messages. OWR may be used for TDOA. There are two cases for TDOA. In the first case, a mobile device periodically broadcasts messages, and the arrival times of the broadcasted messages to multiple fixed nodes synchronized in a predetermined manner are compared. Generally, messages transmitted by a mobile device can be called blinks. In the second case, multiple synchronized nodes can sequentially broadcast messages according to transmission time offsets known to each other. For any pair of fixed synchronized nodes, the difference in arrival times of blinks in the first case, or the difference in arrival times of broadcast messages received by the mobile device in the second case, positions the mobile device on a hyperbolic surface. By combining the results from a number of such pairs, intersection points between sets of hyperbolic surfaces can be derived, thereby determining the location of the mobile device. In the second case, the transmission offset may be taken into consideration when calculating the difference in arrival times of messages from synchronized nodes.

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

[0074] Synchronization of fixed nodes may be performed by distributing the clock signal over a wire, or wireless synchronization techniques may be applied. Relative clock frequency offsets and drifts between fixed nodes can be calculated using UWB messages (and known / pre-measured TOF) transmitted between fixed nodes. This information may be used to correct the arrival times of blink messages on a common time base so that the TDOA data becomes meaningful.

[0075] Setup procedure before replacing the range hood

[0076] Disabling ranging to reduce power consumption may be defined as the default state. Enabling ranging for all RDEVs participating in TWR exchange may be done by the upper layer. Furthermore, when selective capacity is used, it may be assumed that a predetermined coordination of preambles and channel selection takes place before TWR exchange.

[0077] Finish-up procedure after replacing the cleaning solution.

[0078] At the end of the TWR exchange, each device may hold transmit (TX) and receive (RX) ranging counter values ​​related to round-trip time measurement or response time. These values ​​are required at the node where the Time of Flight (TOF) calculation is performed. Out-of-band (OOB) signaling, custom messages, ranging measurement information (RMI) information elements (IE), etc., may be used for this purpose.

[0079] Figure 5 illustrates examples of RMI IE, RCPCS IE, RRMC IE, and RRTI IE formats to which this disclosure can be applied.

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

[0081] The RMI IE may be used to send one or more ranging-related measurements to one or more devices. The RMI IE content field may have a format as illustrated in Figure 5(a).

[0082] A value of 1 in the Reply Time Present field indicates that the RX-to-TX (or TX-to-RX) reply time field exists for each RMI list element, while a value of 0 indicates that it does not exist. The RX-to-TX (or TX-to-RX) reply time may correspond to T_reply as explained in Figure 4.

[0083] A value of 1 in the Round-Trip Time Present field indicates that the TX-to-RX round-trip time field exists for each RMI list element, while a value of 0 indicates that it does not exist. The TX-to-RX round-trip time may correspond to T_round as explained in Figure 4.

[0084] A value of 1 for the TOF existence field indicates that the TOF field exists for each RMI list element, while a value of 0 indicates that it does not exist.

[0085] A value of 1 for the AOA azimuth present field indicates that the AOA azimuth field exists for each RMI list element, while a value of 0 indicates that it does not exist.

[0086] A value of 1 for the AOA elevation present field indicates that the AOA elevation field exists for each RMI list element, while a value of 0 indicates that it does not exist.

[0087] A value of 1 in the AOA FOM (figure of merit) existence field indicates that if the AOA azimuth field exists, then the AOA azimuth FOM field exists in each RMI list element, and if the AOA altitude field exists, then the AOA altitude FOM field exists in each RMI list element. A value of 0 indicates that neither the AOA azimuth FOM field nor the AOA altitude FOM field exists.

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

[0089] A value of 0 in the deferred mode field indicates that the RMI IE is embedded in an RFRAME, while a value of 1 may indicate that the RMI IE will be included in a deferred message sent in the next measurement reporting phase.

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

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

[0092] The RCPCS (ranging channel and preamble code selection) IE may be used to signal channel selection and / or TX / RX preamble code selection for DPS (dynamic preamble code and channel selection). DPS may include modifying the long preamble to protect against attack devices intercepting the ranging. The RCPCS IE content field may have a format as illustrated in Figure 5(b).

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

[0094] A value of 1 in the DDP (DPS Duration Present) field indicates that the DPS Duration field exists, while a value of 0 indicates that it does not exist.

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

[0096] The channel number field can indicate the UWB channel number for the upcoming ranging exchange.

[0097] The CCI (channel configuration interval) field can be used to specify the channel configuration interval. The channel configuration interval may correspond to the time in RSTU (ranging scheduling time unit) units between the transmission of the IE and the reconfiguration of the identified channel.

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

[0099] The DPS duration field can identify the effective time duration of the DPS. This duration may be specified in RSTU units for ERDEVs and in symbol units for non-ERDEVs.

[0100] The TX preamble code field allows the sender of the IE to specify the DPS preamble code to use for transmission during the upcoming ranging exchange.

[0101] The RX preamble code field allows the sender of the IE to specify the DPS preamble code to be used for reception during the upcoming ranging exchange.

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

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

[0104] Basic Range Replacement

[0105] The recipient may have ranging turned on or enabled on their MAC based on the MLME-RX-ENABLE.request primitive from the next higher layer.

[0106] After ranging is enabled on the receiver's MAC (i.e., the MLME-RX-ENABLE.request primitive is received), all received RFRAMEs can generate TX / RX ranging counters.

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

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

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

[0110] A ranging report may include an issue of the MCPS-DATA.confirm primitive on the sender side (i.e., a report of the result of invoking the MCPS-DATA.request primitive) and an issue of the MCPS-DATA.indication primitive on the receiver side (i.e., an instruction to receive data from the sender, or an indication that ranging information is available due to the receipt of a packet from the sender).

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

[0112] Ranging procedure

[0113] First, we will explain ranging control and result transfer.

[0114] Measurement values ​​may be exchanged between RDEVs to complete the ToF calculation. To this end, TWR may be controlled by an information element, and ranging data may be exchanged between RDEVs.

[0115] Specifically, information elements may be used for transferring ranging data between RDEVs participating in ranging exchange and for controlling the Time of Flight (TWR). For various ranging methods, the measurement results from both devices may be combined to complete the Time of Flight (TOF) calculation between the RDEVs participating in ranging exchange, according to the required use case. That is, one device can transfer its ranging measurement results to the other device. Information elements may be specified to provide a mechanism for controlling the TWR and to support the transfer of ranging information between devices participating in ranging exchange. Secure private data communication capability may be used to ensure the integrity of such information transfer.

[0116] The following describes the ranging procedure for SS-TWRs that apply deferred response time results.

[0117] Figure 6 shows an example of a message sequence chart for an SS-TWR to which the deferred response time results applicable to this disclosure can be applied.

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

[0119] The next higher layer after the initiator may have enough information to calculate the time-of-flight between devices using the aforementioned formula at the time of receiving the RMI IE (e.g., Figure 5(a)).

[0120] The initiator can initiate a ranging exchange by activating the MCPS-DATA.request primitive to request ranging response time information and sending a ranging frame containing RRMC (Ranging Request Measurement and Control) information elements, including a ranging control information field.

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

[0122] The RRMC IE may include information that sends ranging requests and controls ranging procedures.

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

[0124] The ranging control information field indicates the following: if its value is 0, the frame is a ranging start message for the SS-TWR; if its value is 1, the frame is a response to a ranging start message for the SS-TWR; if its value is 2, the frame is a ranging start message for the DS-TWR; and if its value is 3, the frame is a continuing DS-TWR and can indicate the start of the second round-trip time measurement.

[0125] The address size field specifies the size of the addresses used in the RRMC address list field. If the value of the address size field is 0, all addresses in the RRMC address list element may be short addresses. If the value of the address size field is 1, all addresses in the RRMC address list element may be extended addresses.

[0126] The RRMC address list length field can indicate the number of addresses in the RRMC address lease field. The RRMC address list length field may be omitted if no addresses are provided (for example, in unicast ranging where the target device can be identified by the destination address in the MHR (MAC header)).

[0127] If the RRMC IE is a broadcast message, the RRMC address list length and RRMC address list field may be omitted if the sender seeks responses to the ranging request from all devices. Alternatively, if the sender seeks responses to the ranging request from a specific device (or set of devices), the RRMC address list length and RRMC address list field may be used to select the set of devices for the response.

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

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

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

[0131] The RRMC address list field may contain a list of addresses that the RRMC IE is directed to.

[0132] In connection with the ranging report (or response ranging frame), the initiator completes the round-trip time measurement, and the MCPS-DATA.confirm primitive can provide the initiator with a ranging report defining the round-trip time. On the receiver side, the MCPS-DATA.indication primitive can provide a responder ranging report defining the response time to the round-trip time measurement.

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

[0134] An RRTI IE may be included in a response frame to transmit the response time of the response frame, in association with one or more frames that contain an RRMC IE with the response time request field set to 1.

[0135] The address size identifier field may be defined as shown in the table below.

[0136] [Table 1]

[0137] The RRTI list length field can specify the number of elements in an RRTI list field. An RRTI list field may contain RRTI list elements.

[0138] The RX-to-TX reply time field in 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 in Figure 4(a)). The reference time may correspond to the reception time (RMARKER basis) of the RFRAME containing the RRMC IE with the reply time request field set to 1.

[0139] The address field in the RRTI list field may be set to the address of the device sending the RRMC IE requesting the response time. The address field may be omitted in unicast ranging. In scheduled multi-node ranging, the address field may be omitted if the response times of different RDEVs have been negotiated in advance and their order has been determined.

[0140] The following describes the ranging procedure for SS-TWR to which embedded response time results are applied.

[0141] Figure 7 shows an example of a message sequence chart for an SS-TWR to which the embedded response time results applicable to this disclosure are applied.

[0142] For an SS-TWR to which response time results are applied, the ranging exchange may be initiated by a ranging frame containing an RRMC IE with the ranging control information field set to 0, requesting ranging response time information. The responding device can complete the round-trip measurement by sending a response frame containing an embedded RRTI (ranging reply time instantaneous) IE. If the device has the capability to generate an RRTI IE, the number of messages required for the 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, such time may be known a priori in an out-of-bounds manner, and an RRTN (ranging reply time negotiation) IE can 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. When such time is known, the ranging initiating device can expect a response message after a specific time and save energy by delaying turning on the receiver until then. This may apply to either SS-TWR or DS-TWR ranging replacement.

[0143] In Figure 7, RRMC IE(0) represents an RRMC IE containing a ranging control information field with a value of 0. Communication of the RRTN IE in the dotted box may occur at any convenient time before ranging exchange is initiated, or 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 enough information to calculate the TOF between the two devices using the formula described above.

[0144] The following describes the ranging procedure for SS-TWRs to which a fixed response time is applied.

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

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

[0147] The HRP-ERDEV PPDU format SP3 may be used for cases with a fixed response time.

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

[0149] On each device, the next higher layer can use the MLME-STS.request primitive to properly configure the operation to set the SP3 packet format on all devices and set PIB (personal area network information base) attributes (e.g., phyHrpUwbStsKey, phyHrpUwbStsVCounter, phyHrpUwbStsVUpper96, etc.). Once the higher layer selects the SP3 packet configuration, subsequent MCPS-DATA primitives will be associated with SP3 packets until the higher layer modifies the packet configuration using the MLME-STS.request primitive.

[0150] The MCPS-DATA.request primitive may be used to initiate ranging exchange, in which case the PPDU does not necessarily have to carry MAC data. Although not illustrated, the activation of the MLME-RXENABLE.request primitive can be assumed to turn on the receiver at an appropriate time for receiving the PPDU. Since the PHY is configured for SP3 packets, the PHY notifies the MAC layer of the PPDU reception at the end of the STS (scrambled timestamp sequence), and MACs that similarly know the SP3 configuration can deliver the RxRangingCounter value of the RangeingReportDescriptor parameter of the MCPS-DATA.indication primitive. Also, assuming that the RangeingStsFom of the RangeingReportDescriptor is acceptable, the upper layer can initiate a response by activating the MCPS-DATA.request primitive, specifying RangeTxTime with an agreed-upon fixed response time.

[0151] Assuming that the SP3 packet response is received by the initiating device and that the RangeingStsFom parameter of the MCPS-DATA.indication primitive is acceptable, the initiating device may have enough information to calculate the Time of Flight (TOF) between devices using the aforementioned formula based on known fixed response times.

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

[0153] LRP-REDEV can once again support challenge-response ranging, which applies a fixed response time to eliminate the need for data messages to carry response times.

[0154] The following describes the DS-TWR ranging procedure to which the deferred response time information is applied.

[0155] Figure 9 shows an example of a message sequence chart for a DS-TWR to which the deferred response time information applicable to this disclosure is applied.

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

[0157] The following describes the DS-TWR ranging procedure that applies embedded ranging time information.

[0158] Figure 10 shows an example of a message sequence chart for a DS-TWR to which embedded ranging time information applicable to this disclosure is applied.

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

[0160] The responder can complete the first round-trip time measurement and 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 continuation of the exchange. In such an RRMC IE, both the response time request and round-trip time request fields are set to 1, allowing for requests for the results of the first round-trip time measurement and the response time for the second round-trip time measurement. The initiater can complete the exchange by sending a final RFRAME to the RMI IE containing the results of the first round-trip time measurement and to the RRTI IE containing the response time for the second round-trip time measurement.

[0161] When receiving the second MCPS-DATA.indication primitive, which is a higher layer of the responder, it may have enough information to calculate the Time of Flight (TOF) between devices using the formula described above. If the initiator of the ranging exchange wishes to receive the result, the initiator may set the TOF request field of the initiating RRMC IE to a value that requests the responder to send the result in the RMI IE of the subsequent message at the end of the exchange.

[0162] The following describes other procedures for mediation in RDEV and ERDEV.

[0163] When STS is used, for successful HRP-ERDEV interaction, the transmitter and receiver must be aligned to a seed (i.e., STS key and data value V) used by the transmitter to generate the STS and by the receiver to generate a sequence for correlation with the received STS. Security personal data communication capacity may be used to arbitrate these values, and the seed may be transferred between devices using an RKSD (Ranging STS Key and Data) IE. The counter value in the RSKD IE may relate to the current packet or future packet, as indicated by the CP (current packet) field of the IE. The upper layer can use the received RSKD IE information to appropriately set the STS seed for sending and receiving future packets (e.g., by PIB attributes such as phyHrpUwbStsKey, phyHrpUwbStsVUpper96, phyHrpUwbStsVCounter). The RSKD IE header IE version may be used to synchronize the STS generator with the information transmitted along with the security-applied payload IE and data.

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

[0165] Multiple node ranging

[0166] Multiple node ranging may include ranging between two or more devices. Each device can play a role in the multiple node ranging.

[0167] Figure 11 is a diagram illustrating the role of the device in a ranging procedure to which this disclosure can be applied.

[0168] The controller may be an ERDEV that sends an RCM (ranging control message) and defines the ranging parameters. The RCM may be a data frame that includes an ARC (advanced control) IE. The controlee may be an ERDEV that uses the ranging parameters provided by the controller using the RCM. The initiator is an ERDEV that sends the first ranging message after the RCM and starts the ranging exchange; the controller or the controlee may be the initiator. The responder is an ERDEV that responds to the ranging start message received from the initiator; the controller or the controlee may be the responder.

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

[0170] For example, Figure 11(a) shows an example where the controller who sends the ranging control message (RCM) is the initiator who sends the ranging start message in the ranging exchange, and the controlled party who receives the RCM is the responder who receives the ranging start message and sends a ranging response message in the ranging exchange. Figure 11(b) shows an example where the controller who sends the RCM is the responder who receives the ranging start message and sends a ranging response message in the ranging exchange, and the controlled party who receives the RCM is the initiator who sends the ranging start message in the ranging exchange.

[0171] A ranging session may be defined as a group of ERDEVs involved in a series of ranging procedures, set by an initial set of ranging parameters. A ranging session may include only one controller and one or more initiators. The controller can set the initial ranging parameters and update them during the ranging session.

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

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

[0174] A controller can use an ARC IE to send ranging configuration information to the controlled device. The ARC IE may be sent as a unicast frame to one controller and as a broadcast frame to multiple controllers.

[0175] The controlled user can use the ARC IE to send their preferred ranging parameters to the controller along with the RCR (Ranging Change Request) IE.

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

[0177] [Table 2]

[0178] [Table 3]

[0179] [Table 4]

[0180] [Table 5]

[0181] The competition-based ranging type is a method in which the controller does not know the existence or number of controlled devices, and ERDEV performs ranging on a competition basis. Because collisions can occur, it may be required at a higher layer to filter out inaccurate or incorrect ranging results. Initiators or responders may compete to transmit within an appropriate time slot. If initiators and responders compete, an RCPS (ranging contention phase structure) IE is added to the ARC IE, and different phases (e.g., distinguished by slot indexes) may be specified in the RCM. Upon receiving the RCM, controlled devices know that they have been selected to participate in the ranging round. The time-scheduled ranging type is a method in which the controller knows all controlled devices and specifies the exact schedule for ranging transmissions. The controller can use an RDM (ranging device management) IE to select devices to participate in ranging, assign ranging roles (i.e., initiators or responders), and allocate time slots. If the device's role and transmission schedule are predetermined using an OOB signaling method, the RDM IE may be omitted.

[0182] [Table 6]

[0183] [Table 7]

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

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

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

[0187] The RRD field can specify the duration of the ranging ground (in ranging slot units, i.e., the number of ranging slots within the ranging ground).

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

[0189] The SID field can specify a unique identifier for each controller.

[0190] If the ranging block structure is the same as the previously identified duration, then the RCM's ACI IE may not currently have one or more duration fields (e.g., RBD field, RRD field, RSD field). In this case, other fields (e.g., schedule mode field, STS packet configuration field, etc.) may be used to update the corresponding ranging parameters.

[0191] Figure 12(b) shows an example of the RDM (Ranging Device Management) IE format.

[0192] RDM IE may be used to exchange scheduling information between ERDEVs for a set of range grounds specified by the controller in the same RCM.

[0193] The SIU (slot index usage) field indicates whether or not to use the slot index of the RDM list element. If its value is 0, the RDM IE may be used to assign ranging roles (i.e., initiator or responder) to controlled entities for conflict-based ranging. If its value is 1, the RDM IE may be used to assign time slots and assign ranging roles to controlled entities for scheduling-based ranging.

[0194] The address size field indicates the size of the address used in the RDM list field; 0 indicates that a short address (16 bits) will be used, and 1 indicates that an extended address (64 bits) will be used.

[0195] The RDM list length field can specify the number of RDM list elements.

[0196] The ranging role field in an RDM list can specify the initiator or responder. The ranging slot index field in an RDM list can specify the slot index to be assigned to the device at that address. The address field in an RDM list can specify the address of each device participating in the ranging.

[0197] Figure 12(c) shows an example of the RBU (Ranging Block Update) IE format.

[0198] The RBU IE may be used by the controller to inform the controlled entity of the updated ranging block structure.

[0199] The relative ranging block index field allows you to specify the number of remaining ranging blocks under the current configuration before switching to a new configuration.

[0200] The updated block duration field allows you to specify the duration (in RSTU units) of a new ranging block.

[0201] The updated ranging round duration field allows you to specify a ranging round duration value that is an integer multiple of the ranging slot duration within the new ranging block structure.

[0202] The updated ranging slot duration allows specifying the ranging slot duration (in RSTU units) within the new ranging block structure.

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

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

[0205] The hopping mode field can indicate whether or not to support hopping mode for ranging blocks.

[0206] The round index field can indicate the ranging round index within the ranging block.

[0207] The transmission offset field can specify the transmission offset value (in RSTU units) for the ranging ground within a block. The transmission offset may have a maximum value of the maximum slot duration minus the packet duration.

[0208] For the current ranging ground (i.e., the ranging ground 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 be information that helps ERDEV synchronize with the block structure.

[0209] For the next ranging ground (i.e., the ranging ground in the next ranging block at block index i+1), an RR IE may be sent in the final message to inform the controlled user of the ranging ground information for the current ranging ground (i.e., the ranging block at block index i) when the last message for the current ranging ground is sent from the controlled user to the controlled user.

[0210] When the last message in the currently ranging ground (i.e., the ranging block at block index i) is sent by the controlled party, the controller may send an RR IE in the RCM of the next ranging block at block index i+1 to inform the controlling party of the ranging ground information for the ranging block at block index i+2.

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

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

[0213] SRRR IE may be used to request the provider to report AOA and / or response time and / or round-trip time measurements from the requestor.

[0214] The requester address size specifier field and the provider address size specifier field may each have values ​​of 00, 01, 10, or 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.

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

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

[0217] The RRTT (report of round-trip time) field can be used to indicate whether or not to request a report of round-trip time.

[0218] The RTOF (report of TOF) field can indicate whether or not a report regarding TOF should be requested.

[0219] The requester address field may be set to the address of the device that transmits or initiates ranging of the signal on which AOA is measured.

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

[0221] Ranging block and round structure

[0222] Figure 13 is a diagram illustrating the ranging block structure and ranging phase to which this disclosure can be applied.

[0223] In Figure 13(a), a ranging block is a time interval in which ranging is performed, and one ranging block may contain N ranging grounds.

[0224] A ranging ground corresponds to a sufficient amount of time for the ERDEVs participating in the ranging exchange to complete the ranging measurement cycle, and one ranging ground may contain M ranging slots.

[0225] A ranging slot may correspond to a sufficient amount of time for transmitting one or more RFRAMEs.

[0226] The slot duration and the number of slots included in a renting ground may differ between renting grounds. Therefore, the controller can send an RCM to the controlled system to change the renting ground settings.

[0227] The RCM (ranging control message) is the first message sent by the controller and may be sent in the first slot of the ranging ground. The RCM may contain setting information for the ranging parameters.

[0228] An RCUM (ranging control update message) is a message sent by the controller in the last slot of a ranging ground specified by the RCM to update the ranging parameters for the next ranging ground. IEs included in the RCM for ranging parameter updates may be included in the RCUM.

[0229] A RIUM (ranging interval update message) is a message sent by the controller to update the interval between ranging blocks and to help synchronize the participating ERDEVs. An RCUM includes the scheduled time for the first RIUM, and a RIUM may include the scheduled time for the next RIUM (if used) before the start of the next ranging block.

[0230] Figure 13(b) illustrates the phases in the ranging procedure.

[0231] RCP (Ranging Control Phase) is the phase in which the controller transmits RCMs.

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

[0233] RIP corresponds to the phase in which the initiator sends a ranging commencement message to the responder.

[0234] RRP corresponds to the phase where the responder sends a response message to the initiator.

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

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

[0237] RCUP (ranging control update phase) is the phase in which the controller sends an RCUM, and if an RCUP exists, this phase may be located in the last slot of the set of ranging grounds specified by the RCM.

[0238] RIUP (Ranging Interval Update Phase) is the phase in which the controller sends a RIUM.

[0239] Figure 14 shows examples of timing diagrams for various multiple device rangings to which this disclosure can be applied.

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

[0241] The ranging mode will be explained below.

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

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

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

[0245] Figure 15 shows a timing diagram in an example of a block-based mode to which this disclosure can be applied.

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

[0247] The number of ranging grounds corresponds to the ranging block duration divided by the ranging ground duration.

[0248] The number of ranging slots corresponds to the ranging round duration divided by the ranging slot duration.

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

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

[0251] The following explains indexing.

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

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

[0254] For ranging slots, if a ranging ground contains M ranging slots, the first ranging slot in the current ranging ground is assigned a slot index of 0, and relative slot indices (e.g., 1, ..., M-1) are determined for the remaining M-1 slots using slot index 0 as a reference.

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

[0256] FIG. 16 is a diagram for explaining an illustration for various transmission offsets to which the present disclosure is applicable.

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

[0258] The transmission offset may be applied to a ranging round. That is, the same transmission offset may be applied to all packet transmissions included in the same ranging round. The controller can select a transmission offset in the next upper layer and communicate this to all other devices using the RR IE. The controller can also change the transmission offset for each ranging round based on the power for reducing interference.

[0259] One-to-many ranging procedure

[0260] FIG. 17 shows an example of a message sequence chart for one-to-many SS-TWR to which the present disclosure is applicable.

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

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

[0263] The RRMC IE, transmitted via the MCPS-DATA.indication primitive by each of the responders-1 through N, can signal the next higher layer that should perform the ranging response. Each responder can insert the RequestRrtiTxList parameter into the RRTI IE (as a response to the RRMC IE's response time request) and send an RRMC IE (i.e., RRMC IE(1)) with the ranging control information field set to 1 to the initiator. Here, the response RFRAME may be sent to the initiator in a unicast manner.

[0264] When the initiator receives each ranging response frame, the initiator may have enough information to calculate the responder's Time of Flight (TOF).

[0265] The initiator's final message broadcast may include one or more RMI IEs for measurement reporting (if requested by an 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 their RRMC IE to 1, and responder-N may set the round-trip time request field in their RRMC IE to 1. If multiple responders request the same set of information, such as TOF, the initiator's measurement reporting may be done by a single RMI IE in the final data message.

[0266] Figure 18 shows an example of a message sequence chart for an SP3 one-to-many SS-TWR to which this disclosure can be applied.

[0267] At the start of a ranging ground, the RCM may send ranging configuration information and associated IE. The SRRR IE(I,R_1) may have the RAOA and RRTT fields set to 1 if responder-1 requests AOA and round-trip time from the initiator.

[0268] Multi-node SP3 ranging may be based on scheduling specified by the next higher layer of the controller (i.e., each time slot is allocated to be used in a particular ERDEV).

[0269] The RDM IE within the RCM may include information for assigning time slots and device roles within the ranging ground. The ARC IE specifies the ranging procedure and SP3 packet format so that the next higher layer of ERDEV recognizes the start and end of the SP3 ranging phase and can invoke MLME-STS primitives to enable / disable SP3 packets before / after the ranging phase.

[0270] The RCM may include an RSKD IE for exchanging the STS seed portion to initialize STS generation between participating ERDEVs. The STS counter values ​​of the participating ERDEVs may be appropriately set for sending and receiving SP3 packets based on the ranging transmission scheduling information.

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

[0272] During the measurement reporting phase, the initiator can send the AOA and round-trip time to responder-1 using the RMI IE. Responders-1 through N can each embed their requested response times within the RMI IE they send to the initiator.

[0273] As another example, in the SP3 ranging phase of a message sequence for an SP3 one-to-many DS-TWR, after the initiator receives SP3 frames as ranging response messages from each responder, it may send an SP3 frame to each responder as a ranging completion message, thereby transmitting the local value of the initiator's TxRangingCounter to each responder. In the measurement reporting phase, the initiator may send an RMI IE including response time and round-trip time to the responders, to which each responder may send an RMI IE including AOA to the initiator.

[0274] Methods for defining and applying hyperblock structure-based scheduling information

[0275] Figure 19 shows the difference in time structure between a single application to which this disclosure can be applied and a combination of various applications.

[0276] In the existing ranging block structure described with reference to FIGS. 13 and 15, etc., ranging blocks of the same length are repeated. In order to support various applications, a new time structure in a form where blocks different from each other are mixed is required. For example, for ranging and DL-TDOA, a new time structure in which ranging methods based on different numbers of slots are mixed can be considered. In order to define a flexible time slot that can accept this, it is necessary to allow the ranging block and the ranging round to have different durations from each other.

[0277] The illustration of FIG. 19(a) corresponds to an illustration of an indoor location measurement use case, and blocks of the same structure may be repeated.

[0278] In the case of a public transportation use case such as the illustration of FIG. 19(b), when the user approaches a subway gate, DL-TDOA operation is required for location measurement, ranging operation is required when the user selects a specific gate, and when the user first approaches the gate, contention for access is required.

[0279] In the illustration of FIG. 19(a), the ranging time structure for a single application (e.g., indoor location measurement) has the same block duration, and in the public transportation use case where a combination of multiple applications (e.g., DL-TDOA, ranging, contention) is required in the illustration of FIG. 19(b), location measurement and ranging can be performed more efficiently by supporting different block durations from each other. For each ranging time structure (e.g., scheduling information such as the duration for the ranging block / ranging round / ranging slot for setting, etc.) for each application included in the illustration of FIG. 19(b) may be different from each other, and it is necessary to define a higher-level time structure for accepting this as one service.

[0280] Thus, unlike existing UWB wireless networks where only time structures of fixed length are defined, there is a need to define a new time structure that supports various block durations with flexible lengths, i.e., a flexible time structure.

[0281] In connection with this, there is a need to define new scheduling information that takes flexible time structures into account, and various examples of such scheduling information in this disclosure are described below.

[0282] Figure 20 is a diagram illustrating the operation of the first device relating to this disclosure.

[0283] In the example shown in Figure 20, the first device may correspond to the controller, and the second device may correspond to the controlled person. Furthermore, both the first and second devices may correspond to ERDEVs.

[0284] In step S2010, a first information element (IE) (e.g., an HBS IE, described later) containing information about the block structure (e.g., the structure of a hyperblock) set in one or more ranging blocks, and a second IE for scheduling in the block structure (e.g., within a hyperblock) (e.g., a scheduling IE for scheduling for a hyperblock, described later) can be generated.

[0285] The second IE may include, for each device, an element (e.g., a scheduling list element) that contains ranging block-based scheduling information within the aforementioned block structure (e.g., a hyperblock).

[0286] For example, the ranging block-based scheduling information within the aforementioned block structure (e.g., hyperblock) may be based on a bitmap that shows the pattern of scheduled ranging blocks. Specifically, each bit constituting the bitmap may correspond to the index of each ranging block within the aforementioned block structure (e.g., hyperblock). Here, the information regarding the ranging block index may be set / indicated by the first IE described above.

[0287] In connection with this, the element containing ranging block-based scheduling information within the aforementioned block structure (e.g., hyperblock) may include information indicating the length of the bitmap. For example, the length of the bitmap may be 8 bits, 16 bits, 32 bits, or 64 bits.

[0288] As an addition or alternative, the second IE may include a length field for a scheduling list field that contains elements containing ranging block-based scheduling information within the aforementioned block structure (e.g., hyperblock). In this case, the scheduling list field may contain elements for a number of devices based on the value of the length field.

[0289] As an addition or alternative, the element containing ranging block-based scheduling information within the aforementioned block structure (e.g., hyperblock) may include address information for the devices to which the ranging block-based scheduling information within the aforementioned block structure (e.g., hyperblock) applies. In connection with this, when an address map is generated for the devices to be assigned within the aforementioned block structure (e.g., hyperblock), the second IE may further include information (e.g., 1-bit information / field) indicating whether or not address map-based address indexing is used. As an example, when address map-based address indexing is used, the address information included in the aforementioned element may be set using a one-octet address index.

[0290] In stage S2020, the first device can send the frame containing the generated first IE and second IE to one or more second devices.

[0291] The time at which the message / frame containing the first IE and the second IE is transmitted (hereinafter referred to as the block allocation schedule information transmission time) may be predetermined (or fixed), or it may be determined by negotiation between the controller and the controlled. The block allocation schedule information transmission time may include the following examples.

[0292] The frame containing the first IE and the second IE may be included in and transmitted (or advertised) within each of the RCMs in the aforementioned block structure (e.g., each hyperblock). Additionally or alternatively, the frame containing the first IE and the second IE may be included in and transmitted (or advertised) within some of the RCMs in the aforementioned block structure (e.g., each hyperblock). The time at which the RCM is transmitted within the hyperblock may be part or all of the ranging grounds included in part or all of the ranging blocks in the aforementioned block structure (e.g., hyperblock), and the RCM may be transmitted in the first slot of the ranging grounds. In connection with this, the transmission period of the second IE may be the same as that of the first IE.

[0293] The method illustrated in the example in Figure 20 may be performed by the first device 100 in Figure 1. For example, one or more processors 102 of the first device 100 in Figure 1 may be configured to generate a first information element (IE) containing information about a block structure set in one or more ranging blocks and a second IE for scheduling within the block structure, and to send a frame containing the first IE and the second IE to one or more second devices. Furthermore, one or more memories 104 of the first device 100 may store instructions for performing the method illustrated in Figure 20 or in the examples described later, when executed by one or more processors 102.

[0294] Figure 21 is a diagram illustrating the operation of the second device relating to this disclosure.

[0295] In step S2110, the second device can receive from the first device a frame that includes a first information element (IE) containing information about a block structure (e.g., a hyperblock) set in one or more ranging blocks, and a second IE for scheduling within the block structure.

[0296] The first IE and second IE, the ranging block-based scheduling information within the aforementioned block structure (e.g., hyperblock) and the elements containing it, the frame containing the first IE and second IE, the address map, and the specific details of the address indexing based thereon are as illustrated in Figure 20, and any redundant explanation will be omitted.

[0297] In step S2120, the second device can determine the ranging block to be assigned to the second device within the block structure (e.g., hyperblock) based on the first IE and the second IE.

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

[0299] The method illustrated in the example in Figure 21 may be performed by the second device 200 in Figure 1. For example, one or more processors 202 of the second device 200 in Figure 1 may be configured to receive a frame from the first device that includes a first information element (IE) containing information about a block structure set in one or more ranging blocks and a second IE for scheduling in the block structure, and to determine which ranging blocks to be allocated to the second device within the block structure based on the first and second IEs. Furthermore, one or more memories 204 of the second device 200 may store instructions for performing the method illustrated in Figure 21 or the example described later, when executed by one or more processors 202.

[0300] The examples in Figures 20 and 21 may correspond to some of the various examples in this disclosure. The various examples in this disclosure, including those in Figures 20 and 21, will be described in more detail below.

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

[0302] In addition, in the embodiments described later, a hyperblock structure is explained as a representative example in relation to block-unit scheduling for a structure composed of multiple blocks. However, the embodiments of this disclosure can be extended and applied to other types of structures composed of multiple blocks, in addition to hyperblock structures.

[0303] (Example 1)

[0304] This embodiment relates to a method for defining / configuring scheduling information elements (IEs) for scheduling hyperblock structures.

[0305] Figure 22 shows an example of the time structure in the hyperblock-based mode according to this disclosure.

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

[0307] As illustrated in Figure 22(b), information regarding the settings for the hyperblock structure may be repeatedly transmitted by the controller in an RCM (or frame containing the block assignment schedule information mentioned above). For this purpose, an HBS (hyperblock structure) IE may be defined. For example, the HBS IE may include the index of the block, the block duration for each of the blocks included in the hyperblock, and a list of controlled entities corresponding to each block. A controlled entity that receives the HBS IE included in the RCM (or frame containing the block assignment schedule information mentioned above) will know that the hyperblock structure is being applied / proceeding and will know which block it will operate in.

[0308] To perform hyperblock-based mode, the controller may send an RCM (or a frame containing the aforementioned block assignment schedule information) containing an HBS IE for hyperblock configuration for the controlled entity. The message / frame containing the HBS IE may be sent at the same time as the aforementioned block assignment schedule information is sent. For block configuration, the RCM (or the frame containing the aforementioned block assignment schedule information) for that block may further include an ARC IE.

[0309] As mentioned above, the hyperblock-based mode may be based on the block-based mode or the interval-based mode. When based on the interval-based mode, the controller can use the RIU IE to specify the interval between the start times of blocks with the same index within each hyperblock. For example, the controller can send an RCM (or a frame containing the block allocation schedule information mentioned above) containing the RIU IE at the start of the first block in each hyperblock (i.e., block 0) (i.e., the start of slot 0 of round 0 of block 0). Since the RCM (or a frame containing the block allocation schedule information mentioned above) is sent at the start of block 0 in hyperblock K containing the RIU IE, the block interval field of the RIU IE can indicate the remaining time until the start of block 0 in hyperblock K+1 containing the RIU IE.

[0310] Figure 23 is a diagram illustrating an example of the HBS IE format related to this disclosure.

[0311] The scope of this disclosure is not limited by the name of HBS IE, and includes examples of other named IEs transmitted in RCM (or the frame containing the aforementioned block allocation schedule information) that include some or all of the information fields described below.

[0312] The HBS IE in Figure 23(a) may include information about the duration of each block within the hyperblock and information about the controlled user assigned to that block. The HBS IE may include a related block index field, a block description list field for all blocks within the hyperblock, and a content field. A controlled user receiving the HBS IE in an RCM (or a frame containing the aforementioned block assignment schedule information) can recognize the existence of the hyperblock. Furthermore, the controlled user can determine which block within the hyperblock they belong to and to perform ranging, based on the controlled user list field included in the block description list field.

[0313] In the example in Figure 23(a), the hyperblock index field can indicate the index of a hyperblock.

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

[0315] The block duration unit field in the content control field can specify the size of the block duration field as follows:

[0316] [Table 8]

[0317] The round duration presence field of a 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.

[0318] The slot duration existence field of a content control field can indicate that a 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.

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

[0320] The block description list field may contain a list of descriptions for each of the overall blocks that belong to the hyperblock.

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

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

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

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

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

[0326] To enable the controlled party to understand the hyperblock scheduling information, the controller can include scheduling IEs related to the scheduling of the hyperblock structure, along with the HBS IE, in the control message (e.g., RCM) and send them to the controlled party.

[0327] Figure 24 shows an example of the scheduling information element (IE) format related to this disclosure.

[0328] Referring to Figure 24, the scheduling IE format (for example, 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 scheduling list field of variable size / length.

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

[0330] The scheduling list type field can specify the formatting method for the scheduling list field, and this scheduling list type field can indicate one of the values ​​specified in Table 9 below.

[0331] [Table 9]

[0332] Referring to Table 9, in order to schedule the aforementioned hyperblock structure proposed in this disclosure (i.e., hyperblock-based mode), in addition to the existing scheduling list types (i.e., scheduling list types 0 to 4) as shown in Table 9 below, a new scheduling list type (i.e., scheduling list type 5) for block scheduling in a structure like the hyperblock proposed in this disclosure may be defined. For example, scheduling information by scheduling list type 5 may relate to scheduling for one or more blocks within a hyperblock (e.g., bitmap-based hyperblock scheduling).

[0333] When the scheduling list type field in the scheduling IE is set to a value of 5, the scheduling list element format may be configured as shown in Figure 25.

[0334] Figure 25 shows an example of a scheduling list element format related to block scheduling according to an embodiment of the present disclosure.

[0335] Referring to Figure 25, 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.

[0336] For example, the scheduling list element format may be for block scheduling related to a structure such as a hyperblock. In this case, the block scheduling bitmap length field and the block scheduling bitmap field may be called the hyperblock scheduling bitmap length field and the hyperblock scheduling bitmap field.

[0337] Specifically, the block scheduling bitmap length field indicates the size / length of the block scheduling bitmap field, and this may be set to one of the values ​​specified in Table 10 below.

[0338] [Table 10]

[0339] A block scheduling bitmap may be used to set / instruct a device using a single scheduling list element to perform block-level scheduling for a structure composed of one or more blocks (e.g., a hyperblock structure). That is, a controller can use the block scheduling bitmap to provide a controlled device with information about one or more blocks assigned to that controlled device within the block structure.

[0340] Specifically, the bitmap within each scheduling list element can indicate a pattern of blocks scheduled for a single device. In connection with this, the block description list element index of the HBS IE, as shown in Figure 23, may be matched with each bit of the 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 bitmap information. Based on this, the HBS IE and the device receiving the scheduling IE (e.g., a scheduling IE according to scheduling list type 5) can determine the block index and block duration for the block to which it is activated.

[0341] The sender address can indicate each participating device.

[0342] As a further example, a scheduling IE by scheduling list type 5 or a container for block scheduling purposes within a structure such as a hyperblock with similar characteristics may be transmitted in the RCM (or the frame containing the aforementioned block allocation schedule information) at the same frequency as the transmission of the HBS IE. If a scheduling IE (e.g., a scheduling IE by scheduling list type 5) is not transmitted together with the HBS IE, it may mean that it does not contain information regarding block scheduling within a structure such as a hyperblock. Additionally or alternatively, if such a scheduling IE is not transmitted together with the HBS IE, it may also mean that the scheduling IE most recently received by the device (e.g., a scheduling IE by scheduling list type 5) has been maintained without modification. In connection with this, a scheduling IE (e.g., a scheduling IE by 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.

[0343] As a further example, in hyperblock-based mode, the block structure may be scheduled based on the RBD (ranging block duration) field, RRD (ranging round duration) field, and RSD (ranging slot duration) field contained in the ARC IE within the RCM (or the frame containing the aforementioned block allocation schedule information). In this case, the block duration of blocks within the hyperblock can be specified based on the block description list information contained in the HBS IE, thus reducing overhead by omitting the RBD field of the ARC IE contained in the RCM (or the frame containing the aforementioned block allocation schedule information) transmitted for each block. When a controller sets scheduling to hyperblock-based mode and transmits an RCM (or a frame containing the aforementioned block allocation schedule information) that includes an HBS IE containing a ranging block duration field and / or ranging ground duration and / or ranging slot duration field, the RBDP (RBD present) bit and / or RRDP (RRD present) bit and / or RSDP (RSD present) bit of the content control field in the ARC IE format of Figure 12(a) may be set to 0, and an ARC IE in which the RBD field and / or RRD field and / or RSD field are omitted may be included in the RCM (or a frame containing the aforementioned block allocation schedule information).

[0344] Methods for defining and applying efficient address indexing

[0345] In the case of an existing scheduling IE, the addresses included in the scheduling IE may be represented based on a 2-octet short address or an 8-octet extended address.

[0346] In connection with this, for efficient address indexing, the Disclosure provides various examples below of new addressing schemes based on address maps generated / managed by specific devices (e.g., controllers).

[0347] Figure 26 is a diagram illustrating the operation of the first device relating to this disclosure.

[0348] In the example shown in Figure 26, the first device may correspond to the controller, and the second device may correspond to the controlled person. Furthermore, both the first and second devices may correspond to ERDEVs.

[0349] In step S2610, the first device can generate scheduling information elements (scheduling IE) for scheduling to one or more second devices.

[0350] In connection with this, the scheduling IE may include fields for one or more scheduling list elements for the one or more second devices. Additionally, if map information related to the device addresses exists, the scheduling IE may further include information indicating whether the aforementioned map information-based address indexing is applicable.

[0351] For example, when map-based address indexing is applied, address information (e.g., sender address information) included in one or more scheduling list elements as described above may be set using the address index obtained by that address indexing. Here, the address index may correspond to a one-octet-based index that represents an address. In other words, one-byte optimization may be performed when transmitting address information.

[0352] As an addition or alternative, the aforementioned map information may be based on address information included in the scheduling IE for scheduling hyperblocks.

[0353] For example, the aforementioned map information is based on the address information of devices operating within a hyperblock, and this address information may be included in the scheduling IE related to scheduling for the hyperblock. The map information may also be updated based on the scheduling cycle for the hyperblock. When information about a new device is added to the map information (for example, when a new controlled device is associated), the largest address index among the unreserved address indices may be assigned to the new device. When information about an existing device is removed from the map information (for example, when an existing controlled device is deassociated), the address index for the removed device may be maintained at an address index reserved for a certain period of time based on a pre-set timer.

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

[0355] The time at which the message / frame containing the scheduling IE is sent (hereinafter referred to as the block allocation schedule information transmission time) may be predetermined (or fixed) or determined by negotiation between the controller and the controlled. The block allocation schedule information transmission time may include the following examples.

[0356] The frame containing the scheduling IE may be included in and transmitted (or advertised) within each of the RCMs within each hyperblock. Additionally or alternatively, the frame containing the scheduling IE may be included in and transmitted (or advertised) within some of the RCMs within each hyperblock. The timing of transmission of an RCM within a hyperblock may be part or all of a ranging ground that is part or all of a ranging block within the hyperblock, and the RCM may be transmitted in the first slot of that ranging ground.

[0357] As an additional or alternative, the frame containing the scheduling IE may be transmitted (or advertised) at the first ranging ground of each ranging block within each hyperblock (i.e., at the start of each ranging block).

[0358] The method illustrated in the example in Figure 26 may be performed by the first device 100 in Figure 1. For example, one or more processors 102 of the first device 100 in Figure 1 may be configured to generate scheduling information elements (scheduling IEs) for scheduling to one or more second devices and to send frames containing the scheduling IEs to the second devices. Furthermore, one or more memories 104 of the first device 100 may store instructions for performing the method illustrated in Figure 26 or the examples described later, when executed by one or more processors 102.

[0359] Figure 27 is a diagram illustrating the operation of the second device relating to this disclosure.

[0360] In step S2710, the second device can receive a frame from the first device that includes scheduling information elements (scheduling IE) for scheduling the second device.

[0361] The specific details related to scheduling IE, scheduling list elements, and address indexing based on map information are as explained in the example in Figure 26, and any redundant explanations will be omitted.

[0362] In step S2720, the second device can obtain the scheduling IE based on the decoding of the frame.

[0363] For example, a second device can operate in active mode during a time interval allocated to it (e.g., a block (or one or more rounds within that block)) and in sleep mode (or inactive mode) during a time interval not allocated to it (e.g., a block (or one or more rounds within that block)).

[0364] The method illustrated in the example in Figure 27 may be performed by the second device 200 in Figure 1. For example, one or more processors 202 of the second device 200 in Figure 1 may be configured to receive a frame containing scheduling information elements (scheduling IE) for scheduling the second device from the first device and to obtain the scheduling IE based on decoding of the frame. Furthermore, one or more memories 204 of the second device 200 may store instructions for performing the method illustrated in Figure 27 or the example described later, when executed by one or more processors 202.

[0365] The examples in Figures 26 and 27 may correspond to some of the various illustrative examples in this disclosure. The various illustrative examples in this disclosure, including those in Figures 26 and 27, will be described in more detail below.

[0366] The address indexing method described in the embodiments below may be applied identically not only to the hyperblock-based mode and the scheduling type associated with it (e.g., scheduling list type 5), but also to all scheduling types that can be indicated by the scheduling list type field.

[0367] (Example 2)

[0368] As described above in this disclosure, scheduling IEs of scheduling list type 5 may be transmitted together with HBS IEs on a hyperblock basis. In this case, the scheduling list elements of the scheduling IE may include address information for all devices operating in the hyperblock. Based on this information, the controller can generate an address map for devices belonging to the hyperblock (e.g., controlled devices scheduled within the hyperblock).

[0369] In this case, the index of the address map may be assigned based on the list index of the scheduling list elements. Therefore, the order of the scheduling list elements should be maintained so that the results transmitted by the controller are not altered on the controlled side. Using this address map, the sender address field in the scheduling list elements included in scheduling IEs of other types (e.g., scheduling list types other than scheduling list type 5) that may be transmitted in each rangering can be optimized.

[0370] The scheduling IE format for applying the aforementioned address map (for example, the scheduling IE content field format) may be configured as shown in Figure 28.

[0371] Figure 28 shows another example of the scheduling information element (IE) format relating to this disclosure.

[0372] Referring to Figure 28, the scheduling IE format for address indexing according to this disclosure may be defined to further include an address index field / bit compared to the scheduling IE format in Figure 24.

[0373] For example, the address index field / bit can 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.

[0374] If the value of the address index field / bit is 1, the sender addresses in the scheduling list elements included in the scheduling IE may be applied based on a sender address index that is not an existing address format (e.g., a 2-octet / 8-octet address).

[0375] Figure 29 is a diagram illustrating an example of an address indexing-based scheduling list element format according to this disclosure.

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

[0377] For example, when address map-based address indexing is applied, Figure 29(a) illustrates the scheduling list element format for scheduling list type 0 (e.g., per-slot scheduling), Figure 29(b) illustrates the scheduling list element format for scheduling list type 2 (e.g., bitmap-based scheduling), and Figure 29(c) illustrates the scheduling list element format for scheduling list type 5 (e.g., bitmap-based hyperblock scheduling).

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

[0379] As a further example, if a controller sends a scheduling IE (according to scheduling list type 5) to a controlled party, and after the address map has been shared, the address map (generated based on scheduling list type 5) must be modified due to further association or deassociation of the controlled party in a personal area network (PAN) managed by the controller, then one or more of the following rules may apply:

[0380] - Rule 1. Information regarding the address map and / or related information may be updated when a subsequent scheduling IE (according to scheduling list type 5) is sent (e.g., a subsequent hyperblock).

[0381] - Rule 2. If a new controlled entity joins before the information regarding the address map and / or related information is updated, the largest index among the unreserved indexes may be selected and assigned to the new controlled entity.

[0382] - Rule 3. If a controlled entity belonging to a PAN is uncoupled before information regarding the address map and / or related information is updated, the reserved index may be kept reserved for a certain period of time. In connection with this, the reserved index may be kept for a certain period of time by setting a timer (e.g., a uncoupled lifetime cycle timer), and after the timer expires, the index may be released and reused later.

[0383] - Rule 4. If information regarding the address map and / or related information has been changed before it is updated, the controller may apply Rules 2 and 3 to manage the address map, then apply this to subsequent scheduling IEs (according to scheduling list type 5), and share the updated information with the controlled party.

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

[0385] How to use Hyperblock Base Mode

[0386] (Example 3)

[0387] This embodiment illustrates the use of the hyperblock-based mode described above.

[0388] The examples in this embodiment describe block scheduling for a hyperblock structure as a representative example, but they may be applied identically to other types of structures composed of multiple blocks. For example, in the following description, the hyperblock scheduling bitmap length field and the hyperblock scheduling bitmap field may be replaced with the (other type) block scheduling bitmap length field and the (other type) block scheduling bitmap field.

[0389] Figure 30 is a diagram illustrating an example of the controlled user's actions based on the hyperblock information relating to this disclosure.

[0390] In hyperblock-based mode, a hyperblock belonging to a group of blocks may include ranging blocks for ranging exchange with multiple controlled entities. A controlled entity can use the information in the HBS IE contained in the hyperblock's first RCM (or the frame containing the aforementioned block assignment schedule information) to obtain the block index, block duration information, etc., within the hyperblock to which it belongs. Based on this, each controlled entity can determine how long it will operate in active mode. Figure 25 illustrates an example in which three controlled entities use the RCM (or the frame containing the aforementioned block assignment schedule information) to obtain information contained in the HBS IE and the scheduling IE (by scheduling list type 5) and apply it to their duty cycle operation.

[0391] In the example shown in Figure 25, the controller can broadcast an RCM (or a frame containing the aforementioned block assignment schedule information) containing an HBS IE (e.g., block duration (or description) list, controlled list, etc.) and a scheduling IE (by scheduling list type 5) at the start of the first block (block 0) in the hyperblock on RAN (ranging area network) 1.

[0392] Figure 31 illustrates the HBS IE and scheduling IE transmitted within the hyperblock according to this disclosure.

[0393] Referring to Figure 31, the HBS IE may include block duration information for all ranging blocks within the hyperblock, and round duration information for the ranging grounds belonging to each ranging block. Additionally, a scheduling IE for scheduling a hyperblock structure (e.g., a scheduling list type 5-based one) may include a plurality of controlled list(essentially a scheduling list), each controlled list may contain information about the block to which the controlled entity belongs / is assigned in bitmap form (e.g., a hyperblock scheduling bitmap).

[0394] The controller may include an ARC IE in the RCM (or the frame containing the aforementioned block assignment schedule information) to transmit additional scheduling information within a block. Here, since the HBS IE includes a block duration list (or 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.

[0395] In relation to the hyperblock structure, HBS IE and scheduling IE for scheduling multiple controlled entities will be explained with specific examples shown in Figure 32.

[0396] Figure 32 is a diagram illustrating an example of an IE included in a control message related to the hyperblock structure according to this disclosure.

[0397] Referring to Figure 32, we will explain this assuming that scheduling is performed for five controlled entities within the hyperblock.

[0398] In connection with this, the RCM (or the frame containing the aforementioned block assignment schedule information) transmitted from the controller to the controlled in hyperblock n-1 may include an HBS IE as shown in Figure 32(a) and a scheduling IE as shown in Figure 32(b).

[0399] Referring to Figure 32(b), a scheduling IE set to a bitmap-based hyperblock scheduling type (e.g., scheduling list type 5) may include hyperblock scheduling information for each controlled entity, i.e., scheduling list elements. In this regard, the example in Figure 32(b) is a case where the aforementioned address indexing (e.g., related to Example 2) is not applied in this disclosure (i.e., the value of the address index field is 0), so the address information included in each scheduling list element is based on an existing addressing scheme.

[0400] The RCM (or the frame containing the aforementioned block allocation schedule information) receives information within the HBS IE and scheduling IE (according to scheduling list type 5), and each controlled entity can find out the index of the block to which it belongs within the hyperblock, the duration of that block and other blocks, etc.

[0401] For example, controlled user 1 (AA:AA) can be determined from the scheduling IE's hyperblock scheduling bitmap to belong to the first block (Block 0) and the second block (Block 1). Furthermore, controlled user 1 can determine the block duration for each block from the HBS IE's block description list (for example, since the block duration unit is 00, it is in ranging rounds), and by matching the first index (block index 0) and the second index (block index 1), it can determine that its block duration is 2 rounds and 5 rounds, respectively. Based on this, a duty cycle can be set for controlled user 1 to remain active during the time corresponding to the first and second blocks, and to remain in a sleep state during the time corresponding to the third block.

[0402] The controlled entity can obtain the ranging round duration in the ARC IE and / or the round / slot duration information in the block description list of the HBS IE in order to calculate the block duration of the RCM (or the frame containing the aforementioned block allocation schedule information).

[0403] This allows the controlled entity 1 to understand that it belongs to block 0 and block 1, and to schedule itself to maintain a sleep (or deep sleep) mode during the time corresponding to block 2.

[0404] Controlled entity 2 is found to belong to block 0, block 1, and block 2, and can always maintain the active mode.

[0405] Controlled persons 3 and 4 are identified as belonging to block 1 and can be scheduled to maintain a sleep (or deep sleep) mode during the time periods corresponding to block 0 and block 2.

[0406] It is determined that the controlled entity 5 belongs to Block 1 and Block 2, and it can be scheduled to maintain a sleep (or deep sleep) mode during the time corresponding to Block 0.

[0407] To check if there are updates to control information (e.g., HBS IE via RCM (or the frame containing the aforementioned block allocation schedule information), scheduling IE (by scheduling list type 5), ARC IE, etc.) in the next hyperblock, the controlled entities can remain active for a specific period of time (e.g., the first round of the first block in each hyperblock) to receive the RCM (or the frame containing the aforementioned block allocation schedule information) at the start of each hyperblock. Subsequently, the controlled entities (e.g., controlled entity 1 to controlled entity 5) can repeat the scheduling operation described above.

[0408] As an addition or alternative, a scheduling IE transmitted with the HBS IE (e.g., a scheduling IE by scheduling list type 5) may include address information for all devices belonging to the hyperblock. In connection with this, it may be possible to generate an address map using such address information and perform address indexing based on the address map. For example, a controller can generate / manage an address map for all devices belonging to the hyperblock.

[0409] Figure 33 illustrates an address indexing-based scheduling IE related to this disclosure.

[0410] Referring to Figure 33, this address map-based address indexing may be applied not only to scheduling IEs of the scheduling list type associated with the hyperblock structure, but also to address information for other types of scheduling IEs.

[0411] For example, the address index field of a scheduling IE (e.g., a scheduling IE based on scheduling list type 0) transmitted in each round within a hyperblock structure may be set to 1. In this case, the address information contained in the scheduling list elements within the scheduling IE may be constructed based on the sender address index. In this case, a method may be applied to obtain the address by referring to an address map based on a scheduling IE (e.g., a scheduling IE based on scheduling list type 5) transmitted together with the HBS IE in the first round of the first block within the hyperblock, in relation to the address information. Thus, the method of transmitting the aforementioned address map-based sender address index (e.g., 1 octet / byte information) has the technical effect of optimizing by 1 byte compared to the existing method of transmitting the sender address (e.g., 2 / 8 octets / byte information).

[0412] As an addition or alternative, the RCM (or the frame containing the block allocation schedule information described above) including the HBS IE and scheduling IE (e.g., scheduling list type 5 based scheduling IE related to the hyperblock structure) according to this disclosure may be transmitted at the first ranging ground for each ranging block of each hyperblock, as illustrated in the locations of the RCM (or the frame containing the block allocation schedule information described above) in Figures 31 and 33. Alternatively, the RCM (or the frame containing the block allocation schedule information described above) including the HBS IE and scheduling IE according to this disclosure may be transmitted at a specific (e.g., first) ranging ground for each of some ranging blocks of each hyperblock.

[0413] The RCM (or frame containing the aforementioned block allocation schedule information) including the HBS IE and scheduling IE relating to this disclosure may have a narrowband PPDU format based on O-QPSK (offset quadrature phase-shift keying) PHY (for example, a PPDU format including the SHR, PHR, and PHY payload fields in Figure 2(g)). The SHR may include a preamble and an SFD. The PHR may include a frame length field.

[0414] The RCM (or the frame containing the aforementioned block allocation schedule information) including the HBS IE and scheduling IE relating to this disclosure may have a UWB PPDU format (for example, a format as illustrated in Figure 3). The location and function of the SYNC, SFD, PHR, STS, and PHY payloads are described with reference to Figure 3.

[0415] Messages such as ADV-POLL (advertisement-poll) and ADV-RESP (advertisement response) may be included in the PHY payload field of the PPDU format. Additionally, RCMs including HBS IE (or frames containing the aforementioned block allocation schedule information) may also be included in the PHY payload field of the PPDU format.

[0416] Unlike scheduling methods in existing UWB wireless network systems, this disclosure proposes a block-based scheduling method for structures such as hyperblocks. This has the technical effect of enabling controllers to efficiently schedule controlled devices, and controlled devices to efficiently switch to and maintain slot mode or active mode by being able to confirm the block assigned / specified to them within the structure.

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

[0418] It will be obvious to those skilled in the art that this disclosure can be embodied in other specific forms, provided that the essential features of this disclosure are not deviated from. Therefore, the above-mentioned detailed description should not be constrained in any way and should be considered illustrative. The scope of this disclosure should be determined by a reasonable interpretation of the attached claims, and any modifications within the equivalent scope of this disclosure are included within the scope of this disclosure.

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

[0420] [Industrial applicability] Although the method proposed in this disclosure has been primarily described in terms of its application to IEEE 802.15.4-based systems, it can also be applied to various other UWB wireless networks or wireless communication systems.

[0421] [Claims when filing an international application] [Claim 1] A method performed by a first device in an ultra-wideband (UWB) wireless network system, The first device generates a first information element (IE) containing information about a block structure set in one or more ranging blocks, and a second IE for scheduling in the block structure; The process includes the step of transmitting a frame containing the first IE and the second IE to one or more second devices; The second IE is a method comprising an element that includes, for each device, ranging block-based scheduling information within the block structure. [Claim 2] The ranging block-based scheduling information within the aforementioned block structure is based on a bitmap that shows the pattern of the scheduled ranging blocks. The method according to claim 1, wherein each bit constituting the bitmap corresponds to the index of each ranging block in the block structure. [Claim 3] The aforementioned element includes information indicating the length of the bitmap, The method according to claim 2, wherein the length of the bitmap is one of 8 bits, 16 bits, 32 bits, or 64 bits. [Claim 4] The frame including the first IE and the second IE is A part or all of the RCM (ranging control message) within the aforementioned block structure, The first ranging ground of each ranging block within the aforementioned block structure, or The method according to claim 1, transmitted in one or more of the first ranging grounds of the first ranging block in the block structure. [Claim 5] The method according to claim 4, wherein the transmission period of the second IE is the same as the transmission period of the first IE. [Claim 6] The second IE includes a length field for the scheduling list field containing the element, The method according to claim 1, wherein the scheduling list field includes a number of elements for devices based on the value of the length field. [Claim 7] The method according to claim 1, wherein the element includes address information for a device subject to ranging block-based scheduling information within the block structure. [Claim 8] The method according to claim 7, wherein the second IE further includes information indicating whether or not the address map-based address indexing is used, based on the generation of an address map for devices assigned within the block structure. [Claim 9] The method according to claim 8, wherein, based on the use of the address map-based address indexing, the address information is set using a one-octet address index. [Claim 10] The first device corresponds to the controller, The method according to claim 1, wherein the second device corresponds to the controlled person (controlee). [Claim 11] A first device in an ultra-wideband (UWB) wireless network system, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: The first device generates a first information element (IE) containing information about the block structure set in one or more ranging blocks, and a second IE for scheduling in the block structure; It is configured to send a frame containing the first IE and the second IE to one or more second devices; The second IE is an apparatus comprising an element that includes, for each device, ranging block unit-based scheduling information within the block structure. [Claim 12] A method performed by a second device in an ultra-wideband (UWB) wireless network system, The steps include receiving a frame from the first device that includes a first information element (IE) containing information about a block structure set in one or more ranging blocks, and a second IE for scheduling in the block structure; The step of determining the ranging block to be assigned to the second device within the block structure based on the first IE and the second IE; The second IE is a method comprising an element that includes, for each device, ranging block-based scheduling information within the block structure. [Claim 13] A second device in an ultra-wideband (UWB) wireless network system, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: The first device receives a frame containing a first information element (IE) containing information about a block structure set in one or more ranging blocks, and a second IE for scheduling in the block structure; Based on the first IE and the second IE, the ranging block to be assigned to the second device within the block structure is determined; The second IE is an apparatus comprising an element that includes, for each device, ranging block unit-based scheduling information within the block structure. [Claim 14] A method performed by a first device in an ultra-wideband (UWB) wireless network system, The first device generates scheduling information elements (scheduling IE) for scheduling to one or more second devices; The step of transmitting a frame including the scheduling IE to one or more second devices; The scheduling IE includes fields for one or more scheduling list elements for one or more second devices, A method wherein, based on the existence of map information associated with the device address, the scheduling IE further includes information indicating whether or not map information-based address indexing is applicable. [Claim 15] The method according to claim 14, wherein, based on the application of the map information-based address indexing, the address information included in one or more scheduling list elements is set using the address index obtained by the address indexing. [Claim 16] The method according to claim 14, wherein the address index corresponds to a one-octet-based index indicating an address. [Claim 17] The aforementioned map information is based on the address information of devices operating within the hyperblock. The method according to claim 14, wherein the address information is included in a scheduling IE related to scheduling for the hyperblock. [Claim 18] The method according to claim 14, wherein the map information is updated based on the scheduling period for hyperblocks. [Claim 19] The method according to claim 18, wherein, based on the addition of information about a new device to the map information, the largest address index among the unreserved address indices is assigned to the new device. [Claim 20] The method according to claim 18, wherein, based on the removal of information about existing devices from the map information, the address index for the device to be removed is maintained in an address index that has been reserved for a certain period of time based on a preset timer. [Claim 21] A first device in an ultra-wideband (UWB) wireless network system, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: The first device generates scheduling information elements (scheduling IE) for scheduling to one or more second devices; The system is configured to send the frame containing the scheduling IE to one or more of the second devices. The scheduling IE includes fields for one or more scheduling list elements for one or more second devices, The scheduling IE further includes information indicating whether map information-based address indexing is applied to the device, based on the existence of map information associated with the device's address. [Claim 22] A method performed by a second device in an ultra-wideband (UWB) wireless network system, The steps include receiving a frame from the first device that includes scheduling information elements (scheduling IE) for scheduling to the second device; The process includes the step of obtaining the scheduling IE based on decoding of the frame; The scheduling IE includes fields for one or more scheduling list elements for one or more second devices, A method wherein, based on the existence of map information associated with the device address, the scheduling IE further includes information indicating whether or not map information-based address indexing is applicable. [Claim 23] A second device in an ultra-wideband (UWB) wireless network system, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: A frame containing scheduling information elements (scheduling IE) for scheduling to the second device is received from the first device; The system is configured to obtain the scheduling IE based on the decoding of the frame; The scheduling IE includes fields for one or more scheduling list elements for one or more second devices, A second device device, wherein the scheduling IE further includes information indicating whether or not map information-based address indexing is applied, based on the existence of map information associated with the device's address.

Claims

1. A method performed by a first device in an ultra-wideband (UWB) wireless network system, The first device generates a first information element (IE) containing information about a block structure set in one or more ranging blocks, and a second IE for scheduling in the block structure; The process includes: transmitting a frame containing the first IE and the second IE to one or more second devices; The second IE is a method comprising an element that includes, for each device, ranging block-based scheduling information within the block structure.

2. The ranging block-based scheduling information within the aforementioned block structure is based on a bitmap that shows the pattern of the scheduled ranging blocks. The method according to claim 1, wherein each bit constituting the bitmap corresponds to the index of each ranging block in the block structure.

3. The aforementioned element includes information indicating the length of the bitmap, The method according to claim 2, wherein the length of the bitmap is one of 8 bits, 16 bits, 32 bits, or 64 bits.

4. The frame, including the first IE and the second IE, A part or all of the RCM (ranging control message) within the aforementioned block structure, The first ranging ground of each ranging block within the aforementioned block structure, or The method according to claim 1, transmitted in one or more of the first ranging grounds of the first ranging block in the block structure.

5. The method according to claim 4, wherein the transmission period of the second IE is the same as the transmission period of the first IE.

6. The second IE includes a length field for the scheduling list field containing the element, The method according to claim 1, wherein the scheduling list field includes a number of elements for devices based on the value of the length field.

7. The method according to claim 1, wherein the element includes address information for a device subject to ranging block-based scheduling information within the block structure.

8. The method according to claim 7, wherein, based on the generation of an address map for devices to be assigned within the block structure, the second IE further includes information indicating whether or not the address map-based address indexing is used.

9. The method according to claim 8, wherein, based on the use of the address map-based address indexing, the address information is set using a one-octet address index.

10. The first device corresponds to the controller, The method according to claim 1, wherein the second device corresponds to the controlled entity.

11. A first device in an ultra-wideband (UWB) wireless network system, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: The first device generates a first information element (IE) containing information about a block structure set in one or more ranging blocks, and a second IE for scheduling in the block structure; It is configured to transmit a frame containing the first IE and the second IE to one or more second devices; The second IE is an apparatus comprising an element that includes, for each device, ranging block-based scheduling information within the block structure.

12. A method performed by a second device in an ultra-wideband (UWB) wireless network system, The steps include receiving a frame from the first device that includes a first information element (IE) containing information about a block structure set in one or more ranging blocks, and a second IE for scheduling in the block structure; The process includes: a step of determining the ranging block to be assigned to the second device within the block structure based on the first IE and the second IE; The second IE is a method comprising an element that includes, for each device, ranging block-based scheduling information within the block structure.

13. A second device in an ultra-wideband (UWB) wireless network system, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: The first device receives a frame containing a first information element (IE) containing information about a block structure set in one or more ranging blocks, and a second IE for scheduling in the block structure; Based on the first IE and the second IE, the ranging block to be assigned to the second device within the block structure is determined; The second IE is an apparatus comprising an element that includes, for each device, ranging block-based scheduling information within the block structure.

14. A method performed by a first device in an ultra-wideband (UWB) wireless network system, The first device generates scheduling information elements (scheduling IE) for scheduling to one or more second devices; The step of transmitting a frame including the scheduling IE to one or more second devices; The scheduling IE includes fields for one or more scheduling list elements for one or more second devices, A method wherein, based on the existence of map information associated with the device address, the scheduling IE further includes information indicating whether or not map information-based address indexing is applicable.

15. The method according to claim 14, wherein, based on the application of the map information-based address indexing, the address information included in one or more scheduling list elements is set using the address index obtained by the address indexing.

16. The method according to claim 14, wherein the address index corresponds to a one-octet-based index indicating an address.

17. The aforementioned map information is based on the address information of devices operating within the hyperblock. The method according to claim 14, wherein the address information is included in a scheduling IE related to scheduling for the hyperblock.

18. The method according to claim 14, wherein the map information is updated based on the scheduling period for the hyperblock.

19. The method according to claim 18, wherein, based on the addition of information about a new device to the map information, the largest address index among the unreserved address indices is assigned to the new device.

20. The method according to claim 18, wherein, based on the removal of information about existing devices from the map information, the address index for the device to be removed is maintained in an address index that has been reserved for a certain period of time based on a preset timer.

21. A first device in an ultra-wideband (UWB) wireless network system, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: The first device generates scheduling information elements (scheduling IE) for scheduling to one or more second devices; The system is configured to transmit a frame including the scheduling IE to one or more of the second devices. The scheduling IE includes fields for one or more scheduling list elements for one or more second devices, A device in which, based on the existence of map information associated with the device's address, the scheduling IE further includes information indicating whether or not map information-based address indexing is applicable.

22. A method performed by a second device in an ultra-wideband (UWB) wireless network system, The steps include receiving a frame from the first device that includes scheduling information elements (scheduling IE) for scheduling to the second device; The step of obtaining the scheduling IE based on decoding of the frame; The scheduling IE includes fields for one or more scheduling list elements for one or more second devices, A method wherein, based on the existence of map information associated with the device address, the scheduling IE further includes information indicating whether or not map information-based address indexing is applicable.

23. A second device in an ultra-wideband (UWB) wireless network system, One or more transceivers, The system comprises one or more processors connected to one or more of the aforementioned transceivers, The one or more processors described above are: A frame containing scheduling information elements (scheduling IE) for scheduling the second device is received from the first device; The system is configured to acquire the scheduling IE based on decoding of the frame; The scheduling IE includes fields for one or more scheduling list elements for one or more second devices, A second device device, wherein the scheduling IE further includes information indicating whether or not the map information-based address indexing is applicable, based on the existence of map information related to the device's address.

Images