Method and apparatus for round hopping in hyper block for ultra-wideband communication

The UWB communication method and device facilitate efficient round hopping in hyperblock structures with non-constant round lengths by using control messages with hyperblock indices and indicators, addressing the challenge of maintaining effective communication in IoT environments.

WO2024237609A1PCT designated stage expired Publication Date: 2024-11-21SAMSUNG ELECTRONICS CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

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

AI Technical Summary

Technical Problem

In IoT environments, UWB communication systems face challenges in efficiently implementing round hopping within hyperblock structures where the length of each ranging round is not constant, making it difficult to maintain effective communication and service provision.

Method used

A method and device for UWB communication that includes generating and transmitting control messages with indices of ranging rounds and hyperblocks, allowing for round hopping based on hyperblock indices and indicators, enabling flexible and efficient communication even in non-constant round length scenarios.

Benefits of technology

This approach allows for robust and efficient round hopping in hyperblock structures, improving communication reliability and service provision by adapting to varying round lengths, thereby enhancing the performance of UWB communication systems in IoT environments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024006413_21112024_PF_FP_ABST
    Figure KR2024006413_21112024_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a first ultra-wideband (UWB) device supporting a hyper block including at least one ranging block. A method of a first ultra-wideband (UWB) device according to an embodiment of the present disclosure may comprise the steps of: generating a control message including an index of a ranging round, an offset of the ranging round, and an index of a hyper block; transmitting the control message to a second UWB device; and performing round hopping between ranging rounds on the basis of the index of the hyper block. Various other embodiments may be included.
Need to check novelty before this filing date? Find Prior Art

Description

Round hopping method and device in hyperblock for ultra-wideband communication

[0001] The present disclosure relates to UWB communication, and more particularly, to a method and device for round hopping in a hyper block for UWB communication.

[0002] The Internet is evolving from a human-centric network where humans create and consume information to an Internet of Things (IoT) network where information is exchanged and processed between distributed components such as objects. The Internet of Everything (IoE) technology, which combines IoT technology with big data processing technology through connections to cloud servers, is also emerging. To implement the IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required. Recently, technologies such as sensor networks for connecting objects, Machine-to-Machine (M2M) communication, and Machine-Type Communication (MTC) are being researched.

[0003] In an IoT environment, intelligent IT (Internet Technology) services can be provided that collect and analyze data generated from connected objects, creating new value in human life. IoT, through the convergence and integration of existing IT (information technology) technologies with various industries, can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] As wireless communication systems advance, a variety of services become available, creating a need for effective solutions to deliver these services. For example, ranging technology, which measures the distance between electronic devices using Ultra Wide Band (UWB), can be used.

[0005] The present disclosure provides a method for setting up round hopping in a hyper block during UWB communication.

[0006] According to one embodiment of the present disclosure, a method of a first ultra wide band (UWB) device supporting a hyper block may include: generating a control message including an index of a ranging round, an offset of the ranging round, and an index of a hyper block; transmitting the control message to a second UWB device; and performing round hopping between ranging rounds based on the index of the hyper block.

[0007] According to one embodiment of the present disclosure, a method of a first ultra wide band (UWB) device supporting a hyper block may include the steps of: generating a control message including configuration information for a hyper block structure and an indicator regarding whether to apply round hopping; transmitting the control message to a second UWB device; and performing round hopping between ranging rounds based on the indicator regarding whether to apply round hopping.

[0008] According to one embodiment of the present disclosure, a first ultra wide band (UWB) device supporting a hyper block includes a transceiver; and a control unit. The control unit generates a control message including an index of a ranging round, an offset of the ranging round, and an index of a hyper block, controls transmission of the control message to a second UWB device, and performs round hopping between ranging rounds based on the index of the hyper block.

[0009] According to one embodiment of the present disclosure, a first ultra wide band (UWB) device supporting hyper blocks includes a transceiver; and a control unit. The control unit generates a control message including configuration information for a hyper block structure and an indicator regarding whether round hopping is applied, controls transmission of the control message to a second UWB device, and performs round hopping between ranging rounds based on the indicator regarding whether round hopping is applied.

[0010] The method and device according to the embodiment of the present disclosure can efficiently perform round hopping in a hyper block structure in which the length of each ranging round is not constant.

[0011] FIG. 1 is an exemplary architecture of a UWB device according to one embodiment of the present disclosure.

[0012] FIG. 2 illustrates the structure of a UWB MAC frame according to an embodiment of the present disclosure.

[0013] FIG. 3 illustrates the structure of a UWB PHY packet according to an embodiment of the present disclosure.

[0014] FIG. 4 illustrates an example of the structure of a ranging block and round used for UWB ranging according to one embodiment of the present disclosure.

[0015] FIG. 5 illustrates a ranging block structure to which a block-based mode is applied according to one embodiment of the present disclosure.

[0016] FIG. 6a illustrates an Advanced Ranging Control (ARC) information element (IE) that includes information for setting a time block structure according to one embodiment of the present disclosure.

[0017] FIG. 6b illustrates a Ranging Block Update (RBU) IE that includes information for updating a time block structure according to one embodiment of the present disclosure.

[0018] FIG. 7 illustrates an example of a hyper block structure according to one embodiment of the present disclosure.

[0019] FIG. 8 illustrates an example of round hopping according to one embodiment of the present disclosure.

[0020] FIG. 9 illustrates a RR (ranging round) IE according to one embodiment of the present disclosure.

[0021] FIG. 10A and FIG. 10B illustrate an example of round hopping in a hyper block according to one embodiment of the present disclosure.

[0022] Figure 11 illustrates an RR IE according to another embodiment of the present disclosure.

[0023] FIG. 12 illustrates an example of round hopping in a hyper block according to another embodiment of the present disclosure.

[0024] FIG. 13a illustrates an example of a Hyper Block Structure (HBS) IE according to one embodiment of the present disclosure.

[0025] FIG. 13b illustrates an example of round hopping in an HBS IE and hyper block according to one embodiment of the present disclosure.

[0026] FIG. 14a illustrates an example of an HBS IE according to one embodiment of the present disclosure.

[0027] FIG. 14b illustrates an example of round hopping in an HBS IE and hyper block according to one embodiment of the present disclosure.

[0028] FIG. 15a illustrates an example of round hopping, and FIG. 15b illustrates an example of block hopping according to an embodiment of the present disclosure.

[0029] FIG. 16 illustrates another example of block hopping according to one embodiment of the present disclosure.

[0030] FIG. 17 illustrates the structure of a UWB device according to one embodiment of the present disclosure.

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

[0032] In describing the embodiments, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to more clearly convey the gist of the present disclosure without obscuring it by omitting unnecessary explanations.

[0033] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0034] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. The embodiments of the present disclosure are provided only to make the present disclosure complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

[0035] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, so that the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also be able to provide steps for performing the functions described in the flowchart block(s).

[0036] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0037] Here, the term '~ unit' used in the present embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Accordingly, according to some embodiments, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within the device or secure multimedia card. Furthermore, according to some embodiments, the '~parts' may include one or more processors.

[0038] The term 'terminal' or 'device' used herein may refer to a mobile station (MS), user equipment (UE), user terminal (UT), wireless terminal, access terminal (AT), terminal, subscriber unit (SS), subscriber station (SS), wireless device, wireless communication device, wireless transmit / receive unit (WTRU), mobile node, mobile, or other terms. Various embodiments of the terminal may include a cellular telephone, a smart phone having a wireless communication function, a personal digital assistant (PDA) having a wireless communication function, a wireless modem, a portable computer having a wireless communication function, a photographing device such as a digital camera having a wireless communication function, a gaming device having a wireless communication function, a music storage and playback home appliance having a wireless communication function, an internet home appliance capable of wireless internet access and browsing, as well as portable units or terminals integrating combinations of such functions. In addition, the terminal may include, but is not limited to, an M2M (Machine to Machine) terminal, an MTC (Machine Type Communication) terminal / device. In this specification, the terminal may also be referred to as an electronic device or simply a device.

[0039] The operating principles of the present disclosure are described in detail below with reference to the attached drawings. In the following description of the present disclosure, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the overall content of this specification.

[0040] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. While the embodiments of the present disclosure will be described below using a communication system utilizing UWB as an example, the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or characteristics. For example, these may include communication systems utilizing Bluetooth or Zigbee. Accordingly, the embodiments of the present disclosure may be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure.

[0041] Additionally, when describing the present disclosure, detailed descriptions of related functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the contents of this specification.

[0042] Generally, wireless sensor network technologies are broadly categorized into Wireless Local Area Network (WLAN) and Wireless Personal Area Network (WPAN) technologies based on their sensing range. WLAN is a technology based on IEEE 802.11 that allows access to a backbone network within a radius of approximately 100 meters. WPAN, on the other hand, is a technology based on IEEE 802.15, and includes technologies such as Bluetooth, ZigBee, and ultra-wideband (UWB). A wireless network implementing these wireless network technologies may consist of multiple electronic devices.

[0043] According to the FCC (Federal Communications Commission) definition, UWB can refer to a wireless communication technology that uses a bandwidth of 500 MHz or more, or a bandwidth corresponding to a center frequency of at least 20%. UWB can also refer to the band itself in which UWB communications are applied. UWB enables secure and accurate ranging between devices. This allows for relative position estimation based on the distance between two devices, or precise position estimation of a device based on the distance from a fixed device (of known location).

[0044] Certain terms used in the following description are provided to aid in understanding the present disclosure, and the use of such specific terms may be changed to other forms without departing from the technical spirit of the present disclosure.

[0045] A "Ranging Device" may be a device capable of performing UWB ranging. In the present disclosure, the Ranging Device may be, for example, a Ranging Device (RDEV) or an Enhanced Ranging Device (ERDEV) defined in IEEE 802.15.4 / 4z. In the present disclosure, the Ranging Device may be referred to as a UWB device.

[0046] An "Advertiser" may be a device (e.g., a Ranging Device) that transmits (or broadcasts) an Advertisement message via an Advertisement channel.

[0047] A "Scanner" may be a device (e.g., a Ranging Device) that scans an Advertisement channel to receive an Advertisement message. In the present disclosure, a scanner may also be referred to as an observer.

[0048] A "Controller" may be a device (e.g., a Ranging Device) that defines and controls a Ranging Control Message (RCM) (or control message). The Controller may define and control ranging features by transmitting the control message.

[0049] A "Controlee" may be a device (e.g., a Ranging Device) that utilizes ranging parameters within an RCM (or control message) received from a Controller. The Controlee may utilize the same ranging characteristics as those set via the control message from the Controller.

[0050] An "Initiator" may be a device (e.g., a Ranging Device) that initiates a ranging exchange. The Initiator may initiate a ranging exchange by transmitting the first RFRAME (Ranging Exchange Message).

[0051] A "Responder" may be a device (e.g., a Ranging Device) that responds to an Initiator in a ranging exchange. The Responder may respond to a ranging exchange message received from the Initiator.

[0052] "In-Band" may be data communication using UWB as the underlying wireless technology.

[0053] "Out-Of-Band (OOB)" may be data communication that does not use UWB as a lower-level wireless technology.

[0054] A "UWB Session" can be the period from when a Controller and a Controlee start communicating via UWB until they stop communicating. In a UWB Session, either a ranging frame (RFRAME) or a data frame can be transmitted, or both a ranging frame and a data frame can be transmitted.

[0055] "UWB Session ID" may be an ID (e.g., a 32-bit integer) that identifies a UWB Session shared between the Controller and the Controlee.

[0056] The "UWB Session Key" may be a key used to protect a UWB session. The UWB Session Key may be used to generate a Scrambled Timestamp Sequence (STS). In the present disclosure, the UWB Session Key may be a UWB Ranging Session Key (URSK), and may be abbreviated as a session key.

[0057] A "UWB Subsystem (UWBS)" may be a hardware component that implements the UWB PHY and MAC specifications included in a UWB device. In the present disclosure, the UWB PHY and MAC specifications may be, for example, the PHY and MAC specifications defined in IEEE 802.15.4 / 4z. In the present disclosure, the UWBS may be referred to as a UWB component.

[0058] A "UWB-enabled Application" may be an application for a service (UWB service). In this disclosure, "UWB-enabled Application" may be abbreviated as an application or UWB application.

[0059] A "Service" may be an implementation of a use case that provides a service to an end-user. In this disclosure, a Service may be referred to as a UWB service.

[0060] "Service Data" may be data defined by the Service Provider that needs to be passed between two ranging devices to implement the service.

[0061] A "Service Provider" may be an entity that defines and provides the hardware and software required to provide a specific service to an end-user.

[0062] "STS" may be a ciphered sequence to increase the integrity and accuracy of ranging measurement timestamps.

[0063] "Dynamic STS mode" may be an operating mode in which, unlike "Static STS," STS is not repeated during a ranging session. In this mode, STS is managed by the ranging device, and the ranging session key used to generate STS can be managed by the Secure Component.

[0064] "Static STS mode" is an operating mode in which STS repeats during a session and does not need to be managed by the Secure Component.

[0065] A "Secure Channel" may be a data channel that prevents overhearing and tampering.

[0066] A "Secure Component" may be an entity with a defined security level (e.g., a Secure Element (SE) or a Trusted Execution Environment (TEE)) that interfaces with the UWBS for the purpose of providing RDS to the UWBS, for example, when dynamic STS is used.

[0067] "Secure Ranging" may be ranging based on STS generated through strong cryptographic operations.

[0068] In addition, when explaining the present disclosure, if it is determined that a specific description of a related public notice function or configuration may unnecessarily obscure the gist of the present disclosure, the detailed description is omitted.

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

[0070] FIG. 1 is an exemplary architecture of a UWB device according to one embodiment of the present disclosure.

[0071] Referring to FIG. 1, a UWB device (100) may include at least one PHY layer (110), a MAC layer (MAC sublayer) (120), and / or a higher layer (130). In the present disclosure, a configuration including a PHY layer (110) and a MAC layer (120) may be referred to as UWBS.

[0072] (1) PHY layer

[0073] At least one PHY layer (110) may include a transceiver together with a low-level control mechanism. In the present disclosure, the transceiver may be referred to as an RF transceiver or a radio transceiver.

[0074] In one embodiment, the PHY layer (110) may support at least one of the following functions:

[0075] - Transceiver activation and deactivation functions (transceiver on / off function)

[0076] - Energy detection function

[0077] - Channel selection function

[0078] - CCA (Clear Channel Assessment) function

[0079] - synchronization function

[0080] - Low-level signaling function

[0081] - UWB ranging, positioning and localization functions

[0082] - Spectrum resource management function

[0083] - Ability to send / receive packets through a physical medium

[0084] (2) MAC layer

[0085] The MAC layer (120) provides an interface between the upper layer (130) and the PHY layer (110).

[0086] In one embodiment, the MAC layer (120) may provide the following two services.

[0087] - MAC data service: A service that enables transmission and reception of MAC PDUs (protocol data units) through PHY.

[0088] - MAC Management Service: A service that interfaces to the MLME-SAP (MAC sublayer management entity (MLME) service access point (SAP)).

[0089] In one embodiment, the MAC layer (120) may support at least one of the following functions:

[0090] - Device discovery and connection setup function

[0091] - Channel access function (access function for physical channels)

[0092] - synchronization function

[0093] - Interference mitigation function based on energy detection

[0094] - Functions related to narrowband signaling

[0095] - GTS (guaranteed timeslot) management function

[0096] - Frame delivery function

[0097] - UWB ranging function

[0098] - PHY parameter change notification function

[0099] - Security features

[0100] (3) Upper layer

[0101] The upper layer (130) may include a network layer that provides functions such as network configuration and message routing, and / or an application layer that provides the intended functions of the device.

[0102] In one embodiment, the application layer may be a UWB-enabled Application Layer for providing UWB services.

[0103] FIG. 2 illustrates the structure of a UWB MAC frame according to an embodiment of the present disclosure.

[0104] In the embodiment of FIG. 2, the UWB MAC frame may be abbreviated as a MAC frame or frame. As an example, the UWB MAC frame may be used to convey UWB data (e.g., a UWB message, a ranging message, control information, service data, application data, transaction data, etc.).

[0105] Referring to FIG. 2, a UWB MAC frame may include a MAC header (MHR), a MAC payload, and / or a MAC footer (MFR).

[0106] (1) MAC header

[0107] The MAC header may include a Frame Control field, a Sequence Number field, a Destination Address field, a Source Address field, an Auxiliary Security Header field, and / or at least one Header IE field. Depending on the embodiment, some of the above-described fields may not be included in the MAC header, and additional field(s) may be further included in the MAC header.

[0108] In one embodiment, the Frame Control field may include a Frame Type field, a Security Enabled field, a Frame Pending field, an AR field, a PAN ID Compression field, a Sequence Number Suppression field, an IE Present field, a Destination Addressing Mode field, a Frame Version field, and / or a Source Addressing Mode field. Depending on the embodiment, some of the above-described fields may not be included in the Frame Control field, and additional field(s) may be further included in the Frame Control field.

[0109] A description of each field follows:

[0110] The Frame Type field may indicate the type of the frame. In an embodiment, the type of the frame may include a data type and / or a Multipurpose type.

[0111] The Security Enabled field may indicate whether an Auxiliary Security Header field exists. The Auxiliary Security Header field may contain information required for security processing.

[0112] The Frame Pending field can indicate whether the device transmitting the frame has more data for the recipient. In other words, the Frame Pending field can indicate whether there are pending frames for the recipient.

[0113] The AR field may indicate whether acknowledgment of reception of the frame is required from the receiver.

[0114] The PAN ID Compression field may indicate whether a PAN ID field is present.

[0115] The Sequence Number Suppression field can indicate whether a Sequence Number field exists. The Sequence Number field can indicate a sequence identifier for the frame.

[0116] The IE Present field can indicate whether the Header IE field and the Payload IE field are included in the frame.

[0117] The Destination Addressing Mode field may indicate whether the Destination Address field contains a short address (e.g., 16 bits) or an extended address (e.g., 64 bits). The Destination Address field may indicate the address of the recipient of the frame.

[0118] The Frame Version field can indicate the frame version. For example, the Frame Version field can be set to a value indicating IEEE std 802.15.4z-2020.

[0119] The Source Addressing Mode field may indicate whether a Source Address field is present, and if present, whether the Source Address field contains a short address (e.g., 16 bits) or an extended address (e.g., 64 bits). The Source Address field may indicate the address of the originator of the frame.

[0120] (2) MAC payload

[0121] The MAC payload may include at least one Payload IE field. In one embodiment, the Payload IE field may include a Vendor Specific Nested IE. In one embodiment, the Payload IE field may include at least one IE for setting or changing (updating) the time block structure.

[0122] (3) MAC footer

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

[0124] FIG. 3 illustrates the structure of a UWB PHY packet according to an embodiment of the present disclosure.

[0125] Fig. 3(a) illustrates an exemplary structure of a UWB PHY packet to which STS packet settings are not applied, and Fig. 3(b) illustrates an exemplary structure of a UWB PHY packet to which STS packet settings are applied. In the present disclosure, a UWB PHY packet may be referred to as a PHY packet, a PHY PDU (PPDU), or a frame.

[0126] Referring to FIG. 3(a), a PPDU may include a synchronization header (SHR), a PHY header (PHR), and a PHY payload (PSDU). A PSDU includes a MAC frame, and as in FIG. 2, the MAC frame may include a MAC header (MHR), a MAC payload, and / or a MAC footer (MFR). In the present disclosure, the synchronization header part may be referred to as a preamble, and the part including the PHY header and PHY payload may be referred to as a data part.

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

[0128] The SYNC field may be a field containing multiple preamble symbols used for synchronization between transmitting and receiving devices. The preamble symbols may be set using one of the predefined preamble codes.

[0129] The SFD field may be a field indicating the end of the SHR and the start of the data field.

[0130] The PHY header can provide information about the structure of the PHY payload. For example, the PHY header can include information about the length of the PSDU, information indicating whether the current frame is an RFRAME (or a Data Frame), etc.

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

[0132] Referring to FIG. 3(b), when the STS packet (SP) setting is 0 (SP0), the STS field is not included in the PPDU (SP0 packet). When the SP setting is 1 (SP1), the STS field is located immediately after the Start of Frame Delimiter (SFD) field and before the PHR field (SP1 packet). When the SP setting is 2 (SP2), the STS field is located after the PHY payload (SP2 packet). When the SP setting is 3 (SP3), the STS field is located immediately after the SFD field, and the PPDU does not include the PHR and data fields (PHY payload) (SP3 packet). That is, in the case of SP3, the PPDU does not include the PHR and PHY payload.

[0133] In the embodiment of FIG. 3(b), each UWB PHY packet may include an RMARKER for defining a reference time, and the RMARKER may be used to obtain a transmission time, reception time, and / or time interval of a ranging message (frame) in a UWB ranging procedure.

[0134] FIG. 4 illustrates an example of the structure of a ranging block and round used for UWB ranging according to one embodiment of the present disclosure.

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

[0136] Meanwhile, if the ranging mode is block-based, the mean time between consecutive ranging rounds can be constant. Alternatively, if the ranging mode is interval-based, the time between consecutive ranging rounds can be dynamically changed. That is, the interval-based mode can adopt a time structure with adaptive spacing.

[0137] Referring to (a) of FIG. 4, one ranging block may include at least one ranging round, and each ranging round may include at least one ranging slot. For example, as illustrated, one ranging block may include N ranging rounds, and ranging round #0 may include M ranging slots.

[0138] In the present disclosure, a ranging block may be abbreviated as a block, a ranging round may be abbreviated as a round, and a ranging slot may be abbreviated as a slot.

[0139] Referring to (b) of FIG. 4, one ranging round may include a ranging control phase, a ranging phase, and / or a measurement report phase. For example, as illustrated, one ranging round may include one slot for a ranging control phase, at least one slot for a ranging phase, and / or at least one slot for a measurement report phase. Depending on the embodiment, some of the above-described phases may not be included in a ranging round, and additional phases (e.g., a ranging control update phase or a ranging interval update phase) may be further included in the ranging round.

[0140] The Ranging Control Phase (RCP) may be a phase in which the controller transmits a Ranging Control Message (RCM). The RCM may be a message transmitted by the controller to configure ranging parameters. The RCM may be transmitted in the first slot (slot #0) of a ranging round.

[0141] The ranging phase (RP) may include a ranging initiation phase, a ranging response phase, and / or a ranging final phase.

[0142] The ranging initiation phase (RIP) may be a phase where the initiator(s) sends ranging initiation message(s) to the responder(s).

[0143] The ranging response phase (RRP) may be the phase where the responder(s) transmit their response message(s) to the initiator.

[0144] The Ranging Termination Phase (RFP) may be the phase where the initiator sends termination message(s) to the responder(s). The Ranging Termination Phase may only be used for DS-TWR.

[0145] The Measurement Report Phase (MRP) may be the phase where participating ranging devices exchange service information related to ranging measurements.

[0146] The ranging control update phase (RCUP) may be a phase in which the controller transmits a ranging control update message (RCUM). The ranging control update phase may be included in the last slot of a set of ranging rounds specified by the RCM. The RCUM may be a message transmitted by the controller to update ranging parameters for the next ranging round(s). The RCUM may be transmitted in the last slot of the ranging round(s) specified by the RCM. The RCUM may include some or all of the information elements (IEs) employed by the RCM to update the values ​​of the parameters.

[0147] The Ranging Interval Update (RIUP) phase may be a phase in which the controller transmits a Ranging Interval Update Message (RIUM). The RIUM may be a message transmitted by the controller to facilitate synchronization between participating ranging devices or to update the interval between ranging blocks. The RIUM includes the scheduled time of the first RIUM. The RIUM may also include the scheduled time of the next RIUM before the start of the next ranging block.

[0148] In one embodiment, the controller can transmit an RCM including information for setting up a time block structure (block setting information), and the controller can set up the time block structure based on the block setting information included in the RCM.

[0149] In one embodiment, the RCM may include the duration of a ranging block, the length of a ranging round, and / or the length of a ranging slot. The RCM may include information about the device role of the ranging device.

[0150] In one embodiment, the controller may transmit RCMs on a round-by-round basis. For example, the controller may transmit RCMs in all or some of the ranging rounds within a ranging block. For example, the controller may transmit RCMs in ranging rounds #0 and #2 within a ranging block.

[0151] In one embodiment, the controller may transmit the RCM in the first slot (slot index 0) of that ranging round.

[0152] In one embodiment, the information (parameters) included in the RCM can be applied to the round(s) following the round in which the RCM was received (the current round) (e.g., one or more subsequent rounds).

[0153] FIG. 5 illustrates a ranging block structure to which a block-based mode is applied according to one embodiment of the present disclosure.

[0154] As shown in Figure 5, block-based mode uses a structured timeline in which the ranging block structure is essentially periodic. In block-based mode, the mean time between consecutive ranging rounds can be constant. Furthermore, in block-based mode, the same block structure can be repeated.

[0155] In one embodiment, in block-based mode, the ranging block structure can be set by specifying a ranging block duration field, a ranging round length field, and a ranging slot length field in an Advanced Ranging Control (ARC) IE.

[0156] In one embodiment, in block-based mode, the number of ranging rounds can be obtained by dividing the ranging block duration by the ranging round length, and the number of ranging slots can be obtained by dividing the ranging round length by the ranging slot length.

[0157] FIG. 6a illustrates an ARC IE including information for setting a time block structure according to one embodiment of the present disclosure.

[0158] In one embodiment, the ARC IE may be used by the controller to transmit ranging configuration information to one controller (in a unicast case) or multiple controllers (in a broadcast case). In this case, the ACE IE may be transmitted in the RCM.

[0159] In one embodiment, the ARC IE may be used by the controller to transmit preferred ranging parameters to the controller. In this case, the ARC IE may be transmitted along with a Ranging Change Request (RCR) IE.

[0160] In one embodiment, the ARC IE may be transmitted via the payload IE field of a MAC frame.

[0161] In one embodiment, the ARC IE may be included in the RCM.

[0162] In one embodiment, the ARC IE may be used for initial setup of the time block structure (block / round / slot structure).

[0163] Referring to FIG. 6a, the ARC IE (or the content field of the ARC IE) may include a Multi Node Mode field, a Ranging Round Usage field, an STS Packet Config field, a Schedule Mode field, a Deferred Mode field, a Time Structure Indicator field, an RCM Validity Rounds field, an MMRCR (Multiple Message Receipt Confirmation Request) field, a Content Control field, a Ranging Block Duration field, a Ranging Round Duration field, a Ranging Slot Duration field, and / or a Session ID field. Depending on the embodiment, some of the above-described fields may not be included in the ARC IE, and additional fields may be further included in the ARC IE.

[0164] The Multi Node Mode field can specify whether ranging is performed between a single pair of devices or is multi-node ranging involving multiple devices.

[0165] The Ranging Round Usage field can specify the usage of a consecutive number of ranging rounds following the current ranging round and the RCM, as specified in the RCM Validity Rounds field of the ARC IE.

[0166] The STS Packet Config field can specify the STS packet format to be used in the ranging round(s) following the ARC IE.

[0167] The Schedule Mode field can specify whether scheduling-based ranging or contention-based ranging is performed.

[0168] The Deferred Mode field can specify whether Deferred frames are allowed for measurement reports. If the value of the Deferred Mode field is 1, the Deferred Mode field can indicate that the ranging slot is scheduled for the exchange of Deferred data frame(s) after the ranging cycle. The Deferred data frame(s) can be used to report measurement information such as ToF, reply time, and AoA. If the value of the Deferred Mode field is 0, the Deferred Mode field can indicate that the ranging slot is not scheduled for the exchange of data frame(s) for the requested information.

[0169] The Time Structure Indicator field can specify the ranging time structure behavior in subsequent ranging rounds.

[0170] The RCM Validity Rounds field can specify the number of consecutive ranging rounds controlled by the RCM. The value of the RCM Validity Rounds field cannot be greater than the number of remaining ranging blocks within the current ranging block.

[0171] The MMRCR field can specify whether multiple message receipt acknowledgments are requested. If the value of the MMRCR field is 1, multiple message receipt acknowledgments are requested; otherwise, multiple message receipt acknowledgments are not requested.

[0172] The Content Control field can indicate the presence of other fields within the ARC IE.

[0173] The Ranging Block Duration field can specify the duration of a ranging block in RSTU units.

[0174] The Ranging Round Duration field can specify the duration of a ranging round in units of ranging slots.

[0175] The Ranging Slot Duration field can specify the duration of the ranging slot in RSTU units.

[0176] The Session ID field can specify an identifier for a ranging session. The Session ID field can contain a 4-octet session identifier that is unique to each controller session. A ranging session can include one controller and at least one initiator.

[0177] FIG. 6b illustrates a Ranging Block Update (RBU) IE that includes information for updating a time block structure according to one embodiment of the present disclosure.

[0178] In one embodiment, the RBU IE may be transmitted by the controller to the controller to signal an update to the ranging block structure. If the final message in a ranging message sequence is transmitted by the controller, the RBU IE may be included in that final message. However, if the final message in a ranging message sequence is transmitted by the controller, the RBU IE may be transmitted by the controller in the next RCM.

[0179] In one embodiment, the RBU IE may be transmitted via the payload IE field of a MAC frame. In one embodiment, the RBU IE may be included in the RCM. In one embodiment, the RBU IE may be used to update or change the time block structure (block / round / slot structure).

[0180] Referring to FIG. 6b, the RBU IE may include a Relative Ranging Block Index field, an Updated Block Duration field, an Updated Ranging Round Duration field, and / or an Updated Slot Duration field. Depending on the embodiment, some of the fields described above may not be included in the RBU IE, and additional fields may be included in the RBU IE.

[0181] The Relative Ranging Block Index field can indicate the number of ranging blocks with the current ranging block structure before switching to a new ranging block structure.

[0182] The Updated Block Duration field can indicate the new ranging block duration in RTSU units. The RBU IE can signal the end of the ranging message exchange. In this case, the Updated Block Duration field in the RBU IE can be set to zero.

[0183] The Updated Ranging Round Duration field can specify a value for the ranging round duration within the new ranging block structure as an integer multiple of the ranging slot duration.

[0184] The Updated Slot Duration field can specify the value of the ranging slot duration within the new ranging block structure in RTSU units.

[0185] Meanwhile, as UWB communication technology advances, it can expand and provide additional functions beyond ranging, such as device discovery, high-capacity data transmission, and sensing. In this case, the number of slots required to operate each additional function can vary from block to block / round. If all blocks were to have the same length, this would inevitably result in highly inefficient slot usage.

[0186] Embodiments of the present disclosure may support a hyper-block structure as an example of a flexible block structure capable of supporting various services / modes, such as ranging, sensing, and high-capacity data transmission. The hyper-block structure may support a block structure that can be set to various durations, for example, rather than a repetition of blocks with a fixed duration. In one embodiment, the hyper-block structure may support a block, round, and / or slot structure that can be set to various durations.

[0187] FIG. 7 illustrates an example of a hyper block structure according to one embodiment of the present disclosure.

[0188] Referring to FIG. 7, consecutive hyper blocks can be configured. For example, as illustrated in FIG. 7, hyper block #0 and hyper block #1 can be arranged consecutively.

[0189] Each hyper block can include at least one block. For example, as illustrated in FIG. 7, hyper block #0 can include blocks #0, #1, ..., and #N, and hyper block #1 can include blocks #0, ..., and #N. According to one embodiment, the durations between blocks within a hyper block can be the same or different. That is, the duration of each block can be freely set according to the configuration. For example, the durations of blocks #0 and #1 of hyper block #0 can be set differently.

[0190] In one embodiment, blocks in the same position of hyperblock #0 and hyperblock #1 may be configured with the same structure and settings. For example, the duration of block #0 of hyperblock #0 and block #0 of hyperblock #1 may be set to be the same. For example, the duration of block #1 of hyperblock #0 and block #1 of hyperblock #1 may be set to be the same.

[0191] Each block can include at least one round. For example, as illustrated in FIG. 7, in hyperblock #0, block #0 can include rounds #0 and #1, block #1 can include rounds #0, #1, #2, and #3, and block #N can include round #0. The durations between rounds within a block or between blocks can be the same or different. That is, the duration of each round can be freely set according to the configuration. For example, rounds #0 and #1 of block #0 can be set differently from each other, and round #0 of block #0 and round #0 of block #1 can be set differently from each other.

[0192] Each round can contain at least one slot. For example, round #0 of block #0 can contain at least one slot. The durations of slots within or between rounds can be the same or different. That is, the duration of each slot can be freely set according to the configuration.

[0193] In this way, in the case of the hyper block structure, the duration between hyper blocks, blocks, rounds, and slots can be freely set according to the settings. In other words, a high degree of freedom can be achieved.

[0194] FIG. 8 illustrates an example of round hopping according to one embodiment of the present disclosure.

[0195] According to one embodiment, round hopping may be used to hop the rounds (or ranging rounds) in which transmission operations are performed without making the transmission timing constant during transmission operations of a UWB device in order to be robust to adjacent interference, etc.

[0196] Referring to (a) of FIG. 8, a UWB device may be configured not to use round hopping (No Hopping). In this case, the UWB device may transmit a message (or packet) based on a first transmission offset (transmission offset s) in a first ranging round (ranging round j) within a first ranging block (ranging block N). Thereafter, the UWB device may transmit a message (or packet) based on a first transmission offset (transmission offset s) in a first ranging round (ranging round j) within a second ranging block (ranging block N+1) (which is a block following the first ranging block (ranging block N). That is, when the UWB device does not use round hopping, it may transmit a message (or packet) in the same ranging round for each ranging block.

[0197] Referring to (b) of FIG. 8, a UWB device may be configured to use a round hopping scheme (Hopping). In this case, the UWB device may transmit a message (or packet) based on a first transmission offset (transmission offset s) in a first ranging round (ranging round j) within a first ranging block (ranging block N). Thereafter, the UWB device may transmit a message (or packet) based on a second transmission offset (transmission offset 0) in a second ranging round (ranging round k) within a second ranging block (ranging block N+1) (which is the next block after the first ranging block (ranging block N). That is, when the UWB device uses a round hopping scheme, it may transmit a message (or packet) based on a different ranging round and / or transmission offset for each ranging block.

[0198] However, in the hyperblock illustrated in FIG. 7, the length of rounds (or ranging rounds) between consecutive adjacent blocks may not be constant, and shuffling may be required between rounds with different durations. In other words, there may be aspects in which the round hopping method is difficult to utilize in the hyperblock structure.

[0199] FIG. 9 illustrates a RR (ranging round) IE according to one embodiment of the present disclosure.

[0200] Referring to FIG. 9, the RR (ranging round) IE may include a ranging block index field, a hopping mode field, a round index field, and a transmission offset field.

[0201] The RR IE may indicate scheduling of a ranging round. In one embodiment, the RR IE may be included in the RCM, the last RFRAME, or the final data message of a ranging message sequence.

[0202] In one embodiment, when in block-based mode, the ranging block index field may indicate the index of a ranging block.

[0203] In one embodiment, in Hyper Block-based Mode, the Ranging Block Index field may indicate the index of a Hyper Block rather than the index of a Ranging Block. In this case, the controlee may assume that it uses the same block index as the previous Hyper Block.

[0204] In one embodiment, by utilizing the characteristic that adjacent hyper blocks have the same structure in a hyper block structure, a UWB device can perform round hopping between ranging blocks in the same location within adjacent hyper blocks rather than between adjacent blocks. In this case, since the index of the ranging block remains constant in the next hyper block, the controller does not need to signal the index of the ranging block to the controlee.

[0205] In one embodiment, the RR IE is transmitted to all UWB devices participating in the ranging session, so that the UWB devices can perform actual transmissions in the rounds for which hopping is determined. In one embodiment, the individual slots used by each UWB device for transmission can be determined based on the ranging device management (RDM) IE.

[0206] The Hopping Mode field can indicate the hop mode for the corresponding ranging block. For example, a value of 0 in this field can indicate no hopping, while a value of 1 can indicate that hopping is applied.

[0207] The Round Index field can specify the ranging round index for the corresponding ranging block.

[0208] The Transmission Offset field may indicate the transmission offset value of a ranging round within a block in RSTU units. For example, the transmission offset may be a value obtained by subtracting the packet duration from the ranging slot duration.

[0209] FIG. 10A and FIG. 10B illustrate an example of round hopping in a hyper block according to one embodiment of the present disclosure.

[0210] Referring to FIGS. 10A and 10B , hyper block #K may include block #0, block #1, and block #2. According to one embodiment, the duration of each block within hyper block #K may be set to various settings. For example, the durations of block #0 and block #1 may be set to be different from each other, and the durations of block #0 and block #2 may be set to be different from each other. Block #0 may include round #0 and round #1, block #1 may include round #0, round #1, round #2, …, round #5, and block #2 may include round #0. According to one embodiment, the duration of each round within each block may be set to various settings. For example, round #0 of block #0 and round #0 of block #1 may be set to be different from each other.

[0211] In FIG. 10a, when setting up round hopping between adjacent blocks with different durations (e.g., round #0 of block #0 and round #0 of block #1), the UWB device may not successfully perform round hopping.

[0212] Referring to FIG. 10b, each of the adjacent hyper blocks #K-1, #K, and #K+1 may include block #0, block #1, and block #2. In one embodiment, each of the adjacent hyper blocks #K-1, #K, and #K+1 may include the same block structure.

[0213] In FIG. 10b, the UWB device can perform round hopping within a block of the same location in an adjacent hyper block by utilizing the characteristic that the same block structure is repeated in adjacent hyper blocks. According to one embodiment, the UWB device can perform round hopping within a block of the same location in an adjacent hyper block based on the RR IE illustrated in FIG. 9.

[0214] For example, a UWB device can only perform round hopping between block #0 of hyperblock #K-1 and block #0 of hyperblock #K. For example, a UWB device can only perform round hopping between block #2 of hyperblock #K-1 and block #2 of hyperblock #K. For example, a UWB device can only perform round hopping between block #1 of hyperblock #K and block #1 of hyperblock #K+1.

[0215] When using the round hopping method according to the embodiment of the present disclosure, a UWB device (or terminal) can know when the next round assigned to it is (e.g., the block in the same location of the next hyper block). This allows the UWB device (or terminal) to enter hibernation mode, for example, and save power.

[0216] Figure 11 illustrates an RR IE according to another embodiment of the present disclosure.

[0217] Referring to FIG. 11, the RR IE may include a Hyper Block Index field, a Ranging Block Index field, a Hopping Mode field, a Round Index field, and a Transmission Offset field.

[0218] The Hyper Block Index field can indicate the index of the hyper block where the next assigned block is located.

[0219] The Ranging Block Index field can indicate the index of a ranging block.

[0220] The Hopping Mode field can indicate the hop mode for the corresponding ranging block. For example, a value of 0 in this field can indicate no hopping, while a value of 1 can indicate that hopping is applied.

[0221] The Round Index field can specify the ranging round index for the corresponding ranging block.

[0222] The Transmission Offset field may indicate the transmission offset value of a ranging round within a block in RSTU units. For example, the transmission offset may be a value obtained by subtracting the packet duration from the ranging slot duration.

[0223] FIG. 12 illustrates an example of round hopping in a hyper block according to another embodiment of the present disclosure.

[0224] Referring to FIG. 12, hyper block #K may include block #0, block #n, and block #N. According to one embodiment, the duration of each block in hyper block #K may be set variously according to the setting. In hyper block #K, block #0 may include round #0 and round #1, block #n may include round #0, round #1, round #m,…, round #M, and block #N may include round #0. According to one embodiment, the duration of each round in each block may be set variously according to the setting.

[0225] Adjacent hyperblocks #K, hyperblock #K+1, and hyperblock #K+2 may contain identical block and / or round structures.

[0226] UWB devices can perform round hopping between different rounds within blocks in the same location of adjacent hyperblocks by taking advantage of the characteristic that the same block structure is repeated in adjacent hyperblocks. According to one embodiment, UWB devices can perform round hopping between different rounds within blocks in the same location of adjacent hyperblocks based on the RR IE illustrated in FIG. 9 or the RR IE illustrated in FIG. 10.

[0227] For example, a UWB device can perform round hopping between round #m within block #n of hyperblock #K and round #p within block #n of hyperblock #K+1. For example, a UWB device can perform round hopping between round #p within block #n of hyperblock #K+1 and round #0 within block #n of hyperblock #K+2.

[0228] FIG. 13a illustrates an example of a Hyper Block Structure (HBS) IE according to one embodiment of the present disclosure.

[0229] Although the HBS IE is described as an example of an IE that sets up a hyper block structure in this disclosure, the technical idea of ​​the present disclosure is not limited to the HBS IE and can be applied identically or similarly to an IE that sets up a hyper block structure.

[0230] Furthermore, the technical concept of the present disclosure is not limited to the names of each field included in the HBS IE, and the names of each field may be implemented in various ways. The technical concept of the present disclosure may also be applied to fields indicating the same or substantially the same information as the fields described above.

[0231] Referring to FIG. 13a, the HBS (Hyper Block Structure) IE may include a Hyper Block Index field, a Content Control field, a Ranging Block Description List Length field, and a Ranging Block Description List field.

[0232] In one embodiment, the HBS IE may be included in the RCM message to allow the controller to convey the hyper block structure configuration to the controlee.

[0233] The Hyper Block Index field can indicate the index of a hyper block.

[0234] The Content Control field may include a Ranging Block Duration Units field, a Ranging Round Duration Presence field, a Ranging Slot Duration Presence field, and a Reserved field.

[0235] The Ranging Block Duration Units field can indicate the unit of the Block Duration field. The unit of the Block Duration field can be a round number, a slot number, or RSTU. The Ranging Round Duration Presence field can indicate whether the Round Duration field exists. The Ranging Slot Duration Presence field can indicate whether the Slot Duration field exists.

[0236] The Ranging Block Description List Length field can indicate the number of Block List elements in the Ranging Block Description List field.

[0237] The Ranging Block Description List field may contain Block List elements.

[0238] FIG. 13b illustrates an example of round hopping in an HBS IE and hyper block according to one embodiment of the present disclosure.

[0239] Referring to FIG. 13b, hyper block #K may include block #0, block #n, and block #N. According to one embodiment, the duration of each block in hyper block #K may be set variously according to the configuration. In hyper block #K, block #0 may include round #0 and round #1, block #n may include round #0, round #1, round #m,…, round #M, and block #N may include round #0. According to one embodiment, the duration of each round in each block may be set variously according to the configuration.

[0240] Adjacent hyperblocks #K and hyperblock #K+1 may contain the same block and / or round structure.

[0241] UWB devices can perform round hopping between different rounds within blocks in the same location of adjacent hyperblocks by taking advantage of the characteristic that the same block structure is repeated in adjacent hyperblocks. For example, a UWB device can perform round hopping between round #m within block #n of hyperblock #K and round #p within block #n of hyperblock #K+1. For example, a UWB device can perform round hopping between round #M within block #n of hyperblock #K and round #1 within block #n of hyperblock #K+1.

[0242] In FIG. 13b, the Content Control field in the HBS IE may include a Ranging Block Duration Units field, a Ranging Round Duration Presence field, a Ranging Slot Duration Presence field, a Hyper Block Hopping Mode field, and a Reserved field.

[0243] Compared to the Content Control field within the HBS IE illustrated in FIG. 13a, the Content Control field within the HBS IE illustrated in FIG. 13b may further include a Hyper Block Hopping Mode field. The description of the remaining fields within the Content Control field within the HBS IE illustrated in FIG. 13b is identical to that described above with reference to FIG. 13a.

[0244] The Hyper Block Hopping Mode field may be an indicator (or flag) indicating whether round hopping is applied. For example, if the Hyper Block Hopping Mode field is 0, it may indicate that round hopping is not applied, and if the Hyper Block Hopping Mode field is 1, it may indicate that round hopping is applied.

[0245] FIG. 14a illustrates an example of an HBS IE according to one embodiment of the present disclosure.

[0246] Referring to FIG. 14a, the HBS IE may include a Hyper Block Index field, a Content Control field, a Ranging Block Description List Length field, and a Ranging Block Description List field. The description of each field in the HBS IE illustrated in FIG. 14a, except for the Ranging Block Description List field, is the same as that described above in FIG. 13a.

[0247] The Ranging Block Description List field may include a Block Index field, a Block Duration field, a Round Duration field, and a Slot Duration field.

[0248] The Block Index field can indicate the index of a block within a hyperblock. The Block Duration field can indicate the Block Duration. In one embodiment, the size and unit of the Block Duration field can be determined by the Ranging Block Duration Units field. The Round Duration field can indicate the number of slots per round. The Slot Duration field can indicate the Slot Duration in RSTU units.

[0249] FIG. 14b illustrates an example of round hopping in an HBS IE and hyper block according to one embodiment of the present disclosure.

[0250] Referring to FIG. 14b, hyper block #K may include block #0, block #n, and block #N. According to one embodiment, the duration of each block in hyper block #K may be set variously according to the configuration. In hyper block #K, block #0 may include round #0 and round #1, block #n may include round #0, round #1, round #m,…, round #M, and block #N may include round #0. According to one embodiment, the duration of each round in each block may be set variously according to the configuration.

[0251] Adjacent hyperblocks #K and hyperblock #K+1 may contain the same block and / or round structure.

[0252] UWB devices can perform round hopping between different rounds within blocks in the same location of adjacent hyperblocks by taking advantage of the characteristic that the same block structure is repeated in adjacent hyperblocks. For example, a UWB device can perform round hopping between round #m within block #n of hyperblock #K and round #p within block #n of hyperblock #K+1.

[0253] In FIG. 14b, the Ranging Block Description List field in the HBS IE may include a Block Index field, a Block Duration field, a Round Duration field, a Slot Duration field, and a Hopping Mode field.

[0254] Compared to the Ranging Block Description List field in the HBS IE illustrated in FIG. 14a, the Ranging Block Description List field in the HBS IE illustrated in FIG. 14b may further include a Hopping Mode field. The description of the remaining fields in the Ranging Block Description List field in the HBS IE illustrated in FIG. 14b is the same as that described above in FIG. 14a.

[0255] The Hopping Mode field can be an indicator (or flag) indicating whether round hopping is applied. The Hopping Mode field can be displayed at the individual block level. For example, if the Hopping Mode field is 0, it indicates that round hopping is not applied compared to the previous hyper block, and if the Hopping Mode field is 1, it indicates that round hopping is applied compared to the previous hyper block.

[0256] FIG. 15a illustrates an example of round hopping, and FIG. 15b illustrates an example of block hopping according to an embodiment of the present disclosure.

[0257] Referring to FIG. 15A, the first hyper block may include block #K-1, block #K, and block #K+1. Each of block #K-1, block #K, and block #K+1 within the first hyper block may include round #0, round #1, round #2, and round #3.

[0258] The second hyper block may include block #K-1, block #K, and block #K+1. Each of block #K-1, block #K, and block #K+1 within the second hyper block may include round #0, round #1, round #2, and round #3.

[0259] For example, a UWB device can perform round hopping between round #0 within block #K of a first hyperblock and round #3 within block #K of a second hyperblock. For example, a UWB device can perform round hopping between round #1 within block #K of a first hyperblock and round #2 within block #K of a second hyperblock. For example, a UWB device can perform round hopping between round #2 within block #K of a first hyperblock and round #0 within block #K of a second hyperblock. For example, a UWB device can perform round hopping between round #3 within block #K of a first hyperblock and round #1 within block #K of a second hyperblock.

[0260] While Figure 15a illustrates round-by-round hopping, Figure 15b illustrates block-by-block hopping.

[0261] Referring to FIG. 15b, hyper block #K-1 may include block #0, block #1, and block #2, hyper block #K may include block #0, block #1, and block #2, and hyper block #K+1 may include block #0, block #1, and block #2. In one embodiment, the duration of each of block #0, block #1, and block #2 may be implemented differently.

[0262] Hyper block #K'-1 may include block #0, block #1, and block #2, hyper block #K' may include block #0, block #1, and block #2, and hyper block #K'+1 may include block #0, block #1, and block #2. In one embodiment, the duration of each of block #0, block #1, and block #2 may be implemented differently.

[0263] In one embodiment, a UWB device may perform block hopping between a first block within a first hyper block and a second block within a second hyper block. The durations of the first block and the second block may be configured to be identical.

[0264] For example, a UWB device can perform block hopping between block #0 within hyperblock #K and block #1 within hyperblock #K'. For example, a UWB device can perform block hopping between block #1 within hyperblock #K and block #0 within hyperblock #K'. For example, a UWB device can perform block hopping between block #2 within hyperblock #K and block #2 within hyperblock #K'.

[0265] FIG. 16 illustrates another example of block hopping according to one embodiment of the present disclosure.

[0266] Referring to FIG. 16, hyper block #K may include blocks #0,…, block #n,…, block #N, hyper block #K+1 may include blocks #0,…, block #p,…, block #N, and hyper block #K+2 may include blocks #0, block #1,…, block #N.

[0267] In one embodiment, a UWB device can perform block hopping between block #n within hyper block #K and block #p within hyper block #K+1. The durations of block #n within the hyper block #K and block #p within the hyper block #K+1 can be configured to be the same.

[0268] According to one embodiment, a UWB device can perform block hopping between block #p within hyper block #K+1 and block #0 within hyper block #K+2. The durations of block #0 within the hyper block #K+2 and block #p within the hyper block #K+1 can be configured to be the same.

[0269] In Fig. 16, for the purpose of explanation, hopping is performed using round #m included in block #n within hyper block #K and round #m included in block #p within hyper block #K+1, but the technical idea of ​​the present invention is not limited thereto. When performing block hopping, the UWB device can perform hopping using the first round (or multiple first rounds) included in block #n within hyper block #K and the second round (or multiple second rounds) included in block #p within hyper block #K+1.

[0270] FIG. 17 illustrates the structure of a UWB device according to one embodiment of the present disclosure.

[0271] In the embodiment of FIG. 17, the UWB device may be an electronic device corresponding to the UWB device of FIG. 1, or including a UWB device, or including a part of a UWB device.

[0272] Referring to FIG. 17, a UWB device may include a transceiver (1710), a control unit (1720), and a storage unit (1730). In the present disclosure, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0273] The transceiver (1710) can transmit and receive messages, information, or packets with other UWB devices. The transceiver (1710) may also be referred to as a transceiver or a transceiver.

[0274] The control unit (1720) can control the overall operation of the UWB device according to the embodiments proposed in the present disclosure. Specifically, the control unit (1720) can control the operation of the UWB device described with reference to FIGS. 1 to 16, for example.

[0275] The storage unit (1730) can store at least one of the information transmitted and received through the transmission and reception unit (1710) and the information generated through the control unit (1720). For example, the storage unit (1730) can store information and data required for the method described with reference to FIGS. 1 to 16.

[0276] In one embodiment, the control unit (1720) may generate a control message including an index of a ranging round, an offset of the ranging round, and an index of a hyper block. In one embodiment, the control unit (1720) may control transmission of the control message to another UWB device. In one embodiment, the control unit (1720) may perform round hopping between ranging rounds based on the index of the hyper block.

[0277] In one embodiment, the index of the hyper block may be indicated by a ranging block index field included in a RR (ranging round) IE.

[0278] In one embodiment, the index of the hyper block may be indicated by a hyper block index field included in the RR (ranging round) IE.

[0279] In one embodiment, the control message may be a ranging control message (RCM) defining ranging features.

[0280] According to one embodiment, the control unit (1720) may perform round hopping between a first ranging round included in a first ranging block of a first hyper block and a second ranging round included in a second ranging block of a second hyper block. The first ranging block and the second ranging block may be configured with the same duration.

[0281] In one embodiment, the control unit (1720) may generate a control message including configuration information for the hyper block structure and an indicator regarding whether round hopping is applied. In one embodiment, the control unit (1720) may control transmission of the control message to the second UWB device. In one embodiment, the control unit (1720) may perform round hopping between ranging rounds based on the indicator regarding whether round hopping is applied.

[0282] According to one embodiment, the indicator regarding whether to apply the round hopping may be included in the Content Control field of the HBS (Hyper Block Structure) IE.

[0283] According to one embodiment, the indicator regarding whether to apply the round hopping may be included in the Ranging Block Description List field of the HBS (Hyper Block Structure) IE.

[0284] In one embodiment, the control message may be a ranging control message (RCM) defining ranging features.

[0285] In the specific embodiments of the present disclosure described above, components included in the present disclosure are expressed in the singular or plural form, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.

[0286] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims

1. A method of a first ultra wide band (UWB) device supporting a hyper block including at least one ranging block, A step of generating a ranging round (RR) IE including an index field of a ranging block, a hopping mode field indicating a hop mode for the ranging block, an index field of a ranging round for the ranging block, and a transmission offset field of the ranging round; and Comprising the step of transmitting a control message including the above RR IE to a second UWB device, A method characterized in that, in a hyper block-based mode, the index field of the ranging block indicates an index of a hyper block.

2. A method according to claim 1, characterized in that when in block-based mode, the index field of the ranging block indicates an index of the ranging block.

3. In paragraph 1, A method characterized in that the above control message is a ranging control message (RCM) defining ranging features.

4. In paragraph 1, A step of performing round hopping between a first ranging round included in a first ranging block of a first hyper block and a second ranging round included in a second ranging block of a second hyper block, The above second hyper block is a block immediately following the above first hyper block, A method, characterized in that the first ranging block and the second ranging block are in the same position within each hyper block.

5. A method of a first ultra wide band (UWB) device supporting a hyper block including at least one ranging block, A step for generating a control message including configuration information for a hyper block structure and an indicator on whether round hopping is applied; a step of transmitting the above control message to a second UWB device; and A method characterized by comprising a step of performing round hopping between ranging rounds based on the indicator as to whether or not to apply the round hopping.

6. In paragraph 5, the indicator regarding whether or not to apply the round hopping is: A method characterized in that it is included in a field regarding the content of IE regarding a hyper block.

7. In paragraph 5, the indicator regarding whether or not to apply the round hopping is: A method characterized in that it includes a field regarding the setting of a ranging block of IE with respect to a hyper block.

8. In paragraph 5, A method characterized in that the above control message is a ranging control message (RCM) defining ranging features.

9. In paragraph 6, A step of performing round hopping between a first ranging round included in a first ranging block of a first hyper block and a second ranging round included in a second ranging block of a second hyper block, The above second hyper block is a block immediately following the above first hyper block, A method, characterized in that the first ranging block and the second ranging block are in the same position within each hyper block.

10. In a first ultra wide band (UWB) device supporting a hyper block including at least one ranging block, Transmitter and receiver; and comprising a control unit, said control unit comprising: Generating a ranging round (RR) IE including an index field of a ranging block, a hopping mode field indicating a hop mode for the ranging block, an index field of a ranging round for the ranging block, and a transmission offset field of the ranging round, Controlling to transmit a control message including the above RR IE to the second UWB device, A device characterized in that, in a hyper block-based mode, the index field of the ranging block indicates an index of a hyper block.

11. A method according to claim 10, characterized in that when in block-based mode, the index field of the ranging block indicates an index of the ranging block.

12. In paragraph 10, A device characterized in that the above control message is a ranging control message (RCM) that defines ranging features.

13. In paragraph 10, the control unit, Perform round hopping between the first ranging round included in the first ranging block of the first hyper block and the second ranging round included in the second ranging block of the second hyper block, The above second hyper block is a block immediately following the above first hyper block, A device characterized in that the first ranging block and the second ranging block are in the same position within each hyper block.

14. In a first ultra wide band (UWB) device supporting a hyper block including at least one ranging block, Transmitter and receiver; and comprising a control unit, said control unit comprising: Generate a control message containing configuration information for the hyperblock structure and an indicator as to whether round hopping should be applied; Controlling to transmit the above control message to the second UWB device, A device characterized by performing round hopping between ranging rounds based on the indicator regarding whether to apply the above round hopping.

15. In paragraph 14, A device characterized in that the above control message is a ranging control message (RCM) that defines ranging features.

Citation Information

Patent Citations

  • Electronic device for performing ranging by using ultra wide band communication and operating method thereof

    US20220345178A1

  • Power saving for in-device coexistence between wi-fi and ultra-wide band communication

    US20220417856A1