Various advertising methods and devices in ultra-wideband wireless network systems

Abstract

Various advertising methods and apparatus in ultra-wideband wireless network systems are disclosed. A method performed by a first device in an ultra-wideband (UWB) wireless network system according to one embodiment of this disclosure may include the steps of: generating an advertising pole frame including a frame identifier field; and transmitting the advertising pole frame to one or more second devices. Based on the fact that multiple advertising pole frames are defined in relation to whether or not a public address is used for session initialization, the frame identifier field may be set to different values ​​for the multiple advertising pole frames.

Description

Technical Field

[0001] The present disclosure relates to various advertising methods and apparatuses in an ultra-wideband wireless network system.

Background Art

[0002] A low-rate (LR) wireless network can assist in 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 support 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 challenge of this disclosure is to provide various advertising methods and apparatus for UWB wireless network systems.

[0005] A further technical challenge of this disclosure is to provide a method and apparatus for transmitting or receiving in the discovery / initialization and setup process based on secured / private advertising messages or unsecured / public advertising messages 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 an advertising pole frame having a frame identifier field (including; configuring; constructing; setting; encompassing; including; containing; having); and transmitting the advertising pole frame to one or more second devices. Based on the definition of multiple advertising pole frames in relation to the use of a public address for session initialization, the frame identifier field may be set to different values ​​for the multiple advertising pole frames.

[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 an advertising pole frame including a frame identifier field from a first device, and performing a session initialization process based on the information contained in the advertising pole frame. Based on the fact that a plurality of advertising pole frames are defined in relation to whether or not a public address is used for the session initialization, the frame identifier field may be set to different values ​​for the plurality of advertising pole frames. [Effects of the Invention]

[0009] This disclosure provides various advertising methods and devices for UWB wireless network systems.

[0010] This disclosure provides a method and apparatus for transmitting or receiving secure / private advertising messages or unsecured / public advertising messages during the discovery / initialization and setup process in a UWB wireless network system.

[0011] 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]

[0012] 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] This is an example of a message sequence chart for a DS-TWR to which the deferred response time information applicable to this disclosure is to be applied. [Figure 10] This is an example of a message sequence chart for a DS-TWR to which embedded ranging time information applicable to this disclosure is to be applied. [Figure 11] This figure illustrates the role of the device in the ranging procedure to which this disclosure can be applied. [Figure 12] This figure shows examples of ARC IE, RDM IE, RBU IE, RR IE, and SRRE IE formats to which this disclosure applies. [Figure 13] This figure illustrates the ranging block structure and ranging phase to which this disclosure can be applied. [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 an example of an MMS packet to which the present disclosure is applicable. [Figure 20] A diagram showing a further example of an MMS packet to which the present disclosure is applicable. [Figure 21] A diagram showing a further example of an MMS packet to which the present disclosure is applicable. [Figure 22] A diagram showing an example of an NBA-MMS-UWB ranging control phase, a ranging phase, and a measurement report phase to which the present disclosure is applicable. [Figure 23] A diagram for explaining ranging session initialization and setup to which the present disclosure is applicable. [Figure 24] A diagram showing an example of an AP transmission / reception operation to which the present disclosure is applicable. [Figure 25-26] A diagram showing an example of an AP transmission / reception operation in a plurality of RANs to which the present disclosure is applicable. [Figure 27] A diagram showing an example of an advertising message format and a response message format according to the present disclosure. [Figure 28] A diagram showing an example of message exchange between an originator and a responder according to the present disclosure. [Figure 29]This figure illustrates an example of concurrent ranging sessions and the exchange of channel usage coordination information between devices belonging to different RANs as described in this disclosure. [Figure 30] This is a diagram illustrating the operation of the first device related to this disclosure. [Figure 31] This is a diagram illustrating the operation of the second device related to this disclosure. [Figure 32] This figure shows an example of the advertising packet format related to this disclosure. [Figure 33] This figure shows other examples of advertising packet formats related to this disclosure. [Figure 34] This figure shows yet another example of the advertising packet format relating to this disclosure. [Figure 35] This figure shows an example of peripheral device discovery based on secure advertising related to this disclosure. [Figure 36] This figure shows an example of access control for multiple devices based on unsecured advertising as described in this disclosure. [Figure 37] This figure shows an example of a purchasing process using any device based on unsecured advertising related to this disclosure. [Modes for carrying out the invention]

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

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

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

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

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

[0018] 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.).

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

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

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

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

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

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

[0025] 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).

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

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

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

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

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

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

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

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

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

[0035] Range measurement

[0036] 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).

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

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

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

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

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

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

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

[0044] 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. 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 by the PHR may be applied in other cases.

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

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

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

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

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

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

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

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

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

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

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

[0056] Range and localization method

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

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

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

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

[0061]

number

[0062] 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:

[0063]

number

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

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

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

[0067]

number

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

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

[0070] 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).

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

[0072] Setup procedure before replacing the range hood

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0087] 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).

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

[0089] 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).

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

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

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

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

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

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

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

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

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

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

[0100] The MLMR-DPS.request and MLME-DPS.confirm primitives may be applied to the selective DPS mode of ranging. The ConfigTime parameter of the MLME-DPS.request primitive can be used to specify a future 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.

[0101] Basic Range Replacement

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

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

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

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

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

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

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

[0109] Ranging procedure

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

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

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

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

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

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

[0116] 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)).

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

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

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

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

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

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

[0123] 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)).

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

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

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

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

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

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

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

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

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

[0133] [Table 1]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0162] Multiple node ranging

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

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

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

[0166] 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).

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

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

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

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

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

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

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

[0174] [Table 2]

[0175] [Table 3]

[0176] [Table 4]

[0177] [Table 5]

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

[0179] [Table 6]

[0180] [Table 7]

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

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

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

[0184] 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0218] Ranging block and round structure

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0238] The ranging mode will be explained below.

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

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

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

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

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

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

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

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

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

[0248] The following explains indexing.

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

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

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

[0252] The new ranging message exchange may be transmitted / received as the first RCM in the ranging slot with index 0 of the ranging round with index 0 of the ranging block with index 0. That is, an RCM packet may be 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.

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

[0254] 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 at their respective slots based on different transmission offsets for each. The transmission offset may have a value smaller than the value obtained by subtracting the UWB packet duration from the ranging slot duration. The transmission offset may be expressed as a multiple of RSTU.

[0255] The 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 the 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 of the ranging rounds based on the power for reducing interference.

[0256] One-to-many ranging procedure

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

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

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

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

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

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

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

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

[0265] 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).

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

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

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

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

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

[0271] Narrowband-assisted (NBA) - UWB

[0272] From a MAC perspective, NBA-UWB can be viewed as an umbrella feature encompassing various semi-independent features. All such features share some common principles, the most important of which is the existence of tight clock synchronization between narrowband (NB) and UWB. The NB PHY and UWB PHY should be driven by the same clock, thereby eliminating the need for further work to determine relative accuracy. If the same clock is not applied to the NB PHY and UWB PHY, explicit requirements for relative clock drift / accuracy between different PHYs / radios may be required. Based on the tight coupling between NB and UWB, various features may be considered for UWB, such as the following:

[0273] - Initialization Channel: The initialization channel may correspond to the NB channel used for UWB channel discovery. NB radio technology may be used as a pilot for providing an additional CCA mode for UWB to the IEEE 802.15.4 series standard. The control channel, on the other hand, is separate from the initialization channel, and approximately 300 NB channels may be defined for the control channel.

[0274] - MMS (multi-millisecond) UWB (including security MMS): In MMS-UWB, data exchange and acquisition of CFO (carrier frequency offset) / SFO (sampling frequency offset) may be offloaded to the NB PHY. This can enable improved ToF accuracy and link budget.

[0275] - NBA-TDOA: Link budget improvements and energy savings should also be applied to NBA-TDOA.

[0276] - NBA-sensing: NB may be applied to the data exchange required for multi-static sensing.

[0277] There may be some common elements that can be reused for such features, and there may also be specific requirements for each feature. Considering that the NBA-UWB system can operate in a dense multi-user scenario, it is important to support coexistence / interference for both NB and UWB. Relevant matters for NB wireless technology may include duty cycle optimization, channelization, frequency hopping and blocked channel list agreement, and LBT (listen-before-talk) techniques. Ranging session definition and PHY level parameters also need to be specified. The MAC service can provide an open interface to transmit scheduling, initial timing, and frequency synchronization, and also transmit the configuration information obtained from the auxiliary NB to the UWB operation. The MAC may be defined to provide clear and generic criteria for various use cases. Since each application may have different requirements, instead of seeking a solution that meets all cases, it is preferable to focus on the common elements between specific applications.

[0278] The PHY may include additional and / or improved technologies to enable the NBA-UWB-based features defined by the MAC. In particular, the content for O-QPSK (offset-quadrature phase shift keying) of the IEEE 802.15.4 series standard, UWB, etc. may include some modifications and improvements to the PHY aspect of NBA-UWB. Alternatively, a PHY different from O-QPSK can also assist UWB by leveraging the open interface provided by the MAC service.

[0279] O-QPSK provides a very good baseline for the NB side of UWB because it supports a good link budget and efficient implementation. The 250kbps mode (or 250k mode) may be applied as a primary element in a relatively optimized airtime. Exemplary improvements to O-QPSK are as follows:

[0280] - In addition to the 2450MHz band defined by the existing IEEE 802.15.4 standard, newer bands such as UNII (Unlicensed National Information Infrastructure)-3 and UNII-5 may be used.

[0281] - Channeling of such bandwidth can enable frequency hopping and reduce airtime for other services. This can lead to a reduction in preamble length and an increase in data rates.

[0282] - Requirements for clock accuracy may be defined.

[0283] - Convolution channel coding using predefined generator polynomials is applied, and LDPC (low-density parity-check code) coding may also be applied selectively.

[0284] For clock accuracy, further NB modes may be aligned with UWB. The carrier frequency and chip rate frequency of HRP UWB should be derived from the same reference oscillator and must have an accuracy in the range of +20ppm to -20ppm or better. To take advantage of the features of NBA-UWB, similar selective modes to O-QPSK may be defined.

[0285] As O-QPSK-based PPDU formats, PPDU configuration-1, PPDU configuration-2, and PPDU configuration-3 may be applied. As explained with reference to Figures 2 and 3, a PPDU may basically include a preamble, SFD, PHR, and payload. PPDU configuration-1 provides a baseline for a data rate of 250 kbps, and the other PPDU configurations may be selectively defined for an optimized trade-off between airtime and link budget. Also, one chip has a duration of 0.5 us, and one symbol can carry 4 bits (for example, if FEC (forward error correction) is applied, the 4 bits may correspond to coded bits). On the other hand, the number of chips in one symbol may be called the SF (spreading factor).

[0286] For example, for a 10-byte PSDU payload, the data rate and the length of each field according to the PPDU settings are as follows:

[0287] - PPDU Settings-1: Data Rate = 250kbps, Preamble Length = 128us, SFD Length = 32us, PHR Length = 32us, Payload Length = 320us, Total Packet Duration = 512us

[0288] - PPDU Settings-2: Data rate = 500kbps, Preamble length = 64us, SFD length = 32us, PHR length = 28us, Payload length = 172us, Total packet duration = 296us (Rate -1 / 2 convolution code is applied to both PHR and payload, PHR carries 28 (=(8+6)*2) coded bits, payload carries 172 (=(80+6)*2) coded bits)

[0289] - PPDU Settings-3: Data Rate = 1000kbps, Preamble Length = 64us, SFD Length = 32us, PHR Length = 28us, Payload Length = 80us, Total Packet Duration = 204us

[0290] Both out-of-band (OOB) and in-band signaling may be used to instruct NB settings. In the case of OOB signaling, the SFD may have the format shown in the table below.

[0291] [Table 8]

[0292] For in-band signaling, SFD may be used to indicate different NB settings as shown in the table below.

[0293] [Table 9]

[0294] The starting point for NBA-UWB PHY can be UWB PHY. For example, a no-data packet format has already been defined to improve link budget. MMS UWB may include extensions to the no-data packet to further improve link budget and ToF accuracy. In this packet format, there may be short fragments with minimum millisecond start-to-start spacing, and the overall packet may have a length spanning multiple fragments. One millisecond may correspond to 499200 chips.

[0295] An MMS UWB packet may contain multiple fragments, which are classified into two types: ranging sequence fragments (RSFs) and ranging integrity fragments (RIFs).

[0296] First, let me explain RSF.

[0297] - Each RSF may contain repeats of a selected MMS ranging sequence (MMRS). One common MMRS may be used across all RSFs.

[0298] - Sixteen MMRS sequences based on complementary sets of length 128 may be defined. Each element of the sequence may be represented by + or -. Code indices 33, 34, ..., 48 may be assigned to each of the sixteen MMRS sequences. Each MMRS sequence may be separated into two parts [A, B]. A and B may each have a length of 64. A gap G consisting of 0 to 64 zero values ​​may be added to construct an MMRS with a gap, such as [A, G, B, G].

[0299] - As MMRS, ternary codes of length 91 and length 127 (e.g., codes defined in the IEEE 802.15.4z standard) may be selectively applied. The use of such ternary codes may induce more interference to surrounding legacy devices compared to the aforementioned length 128 MMRS.

[0300] - A diffusion factor L=4 may be applied to MMRS that contain or do not contain gaps before being repeated within a single RSF.

[0301] Next, I will explain RIF.

[0302] Each RIF can carry a pulse waveform modulated in a pseudo-random manner for ranging completeness. An existing STS may be applied as a reference line for such a waveform.

[0303] - The RIF may include one STS segment to which a diffusion factor L=4 is applied. Each STS segment may have the same length.

[0304] - In all RIFs within a single MMS UWB packet, the polarity of all STS pulses may be generated using a deterministic random bit generator (DRBG) based on AES-128 in counter mode.

[0305] Figure 19 shows an example of an MMS packet to which this disclosure can be applied.

[0306] Figure 19 illustrates an example of a generic MMS packet to which NB assistance may or may not be applied. The acceptable settings for X, Y, and Z shown in Figure 19 are described in detail below.

[0307] In each RSF, an MMRS symbol is first generated, and then that MMRS symbol may be repeated N_MSR times. A single MMRS symbol may be generated as follows:

[0308] When MMRS is used based on a complementary set, in step 1, the MMRS without gaps, i.e., [A,B] (where A and B are sequences of length 64 each), is determined; in step 2, the gap G is determined to obtain the MMRS with gaps, i.e., S=[A,G,B,G]; and in step 3, diffusion with diffusion factor L=4 can be applied to obtain the MMRS symbol S'=[A',G',B',G'].

[0309] When using heterogeneous tow and Ipatov sequences for MMRS, in step 1, the Ipatov sequence S is determined; and in step 2, the MMRS symbol S' can be obtained by applying diffusion with a diffusion factor L=4.

[0310] Within each RSF, the MMRS iteration count N_MSR may be set to one of the values ​​in the set {32, 40, 48, 64, 128, 256}. A small N_MSR value is advantageous for coexistence through short active transmissions, while a large N_MSR value facilitates overall energy utilization even without a high-performance PA (power amplifier). The N_MSR value may be the same for all RSFs within a single MMS packet.

[0311] Figure 20 shows further examples of MMS packets to which this disclosure can be applied.

[0312] The RSF-only MMS packet format in Figure 20(a) can enable efficient and rapid channel impulse response (CIR) generation using MMS coherent combining. In the mixed MMS packet format for ranging integrity in Figure 20(b), the RIF may follow the RSF.

[0313] For the RSF-only MMS packet in Figure 20(a), the following numerology may be applied to increase the processing gain.

[0314] The number of preamble fragments X may be set to any one value in the set {1, 2, 4, 8, 16}. RSF-RMARKER may be defined as the peak of the first pulse of the first RSF.

[0315] In the mixed MMS packet for ranging integrity shown in Figure 20(b), if the NB is used to assist in timing / frequency synchronization, the following numerology may be applied:

[0316] Further RIF-RMARKERs may be defined as the peaks of the first and last pulses of each RSF. RIF-RMARKER y corresponds to the peak of the first pulse of RIF-y, and RIF-RMARKER y' corresponds to the peak of the last pulse of RIF-y. To increase the gain, the number of RFS X may be set to any value in the set {0, 1, 2, 4, 8}, and the number of RIF Y may be set to any value in the set {1, 2, 4, 8}. X=0 implies an RIF-only MMS packet.

[0317] For example, a first mode where X=Y=1, 2, 4, 8 and a second mode where X=1 and Y=2, 4, 8 may be defined as baselines. Other combinations of X and Y values ​​may also be selectively applied.

[0318] When Z=2, an additional 1ms gap between the RSF and RIF can provide an additional time budget before starting to process the fragments for integrity verification.

[0319] Figure 21 shows further examples of MMS packets to which this disclosure can be applied.

[0320] Figure 21(a) shows an example of a UWB-only mixed MMS packet containing RSF when X > 0, and Figure 21(b) shows an example of a UWB-only mixed MMS packet containing only RIF when X = 0 and Y > 0.

[0321] If the NB is not used to report timing / frequency synchronization, the following numerology may be applied to mixed MMS packets for ranging integrity:

[0322] As illustrated in Figure 21, SYNC and SFD may be included in the MMS packet.

[0323] Further RIF-RMARKERs may be defined as the peaks of the first and last pulses in each RIF.

[0324] X may be set to any value in the set {0, 1, 2, 4, 8}, and Y may be set to any value in the set {0, 1, 2, 4, 8}, where Y=0 is acceptable if it does not provide ranging completeness. X=0 and Y=1 may be defined as default settings to facilitate interoperability. When X>0 and Z=2, an additional 1ms gap between the RSF and RIF can provide an additional time budget before starting to process fragments for completeness verification.

[0325] Further improvements to the NBA-UWB method for better interference detection and ranging performance, as well as methods utilizing only UWB wireless technology to achieve improved link budget compared to existing MMS ranging, may be applied.

[0326] NBA-UWB Range

[0327] First, let's explain the NBA-MMS-UWB ranging measurement cycle.

[0328] In NBA-MMS-UWB ranging, the role of ERDEV can be described as either an initiator or a responder. For example, during an NBA-MMS-UWB ranging cycle, the initiator can act as the controller, and the responder can act as the controlled. However, this does not exclude cases where the initiator is the controlled and the responder is the controller.

[0329] In NBA-MMS-UWB ranging, ranging block and ranging ground structures as described in Figures 13 and 15 may be applied, and a block-based mode may be applied. The ranging block structure for NBA-MMS-UWB may be set up by specifying the ranging block duration, ranging ground duration, and ranging slot duration.

[0330] The unit of time for determining the duration of ranging blocks and ranging grounds is RSTU. A ranging device can implement a ranging block structure such that the tolerance for the ranging block duration relative to the PHY clock is within the range of +100 ppm to -100 ppm. A ranging ground corresponds to a period of duration sufficient to complete one complete ranging measurement cycle. The initiator and responder may use one or more ranging grounds from the first ranging block of a ranging session, and the same ranging ground usage pattern may be repeated in subsequent ranging blocks. Round hopping may be applied in an NBA-MMS-UWB ranging session, and a transmit offset may not be applied.

[0331] As an extension of existing slot-based ranging modes, MMS multiplexed continuous ranging slots may be allocated for a single packet transmission. The ranging slot duration, ranging ground duration, and ranging block duration may be selected as integer multiples of 300 RSTU (i.e., 250 us).

[0332] The ranging measurement cycle may be uniquely identified by the ranging block index and the ranging ground index. In NBA-MMS-UWB ranging, the ranging measurement cycle may include a ranging control phase, a ranging phase, and a measurement reporting phase (in-band / out-of-band).

[0333] Of the ranging control phase, ranging phase, and measurement reporting phase included in the ranging ground in Figure 13(b), the ranging control phase and ranging phase are mandatory requirements in the NBA-MMS-UWB ranging measurement cycle. The measurement reporting phase may be selectively supported by in-band wireless technology (e.g., NB, UWB) or by OOB. If provided in-band, the ranging ground length may be set to include the ranging control phase, ranging phase, and measurement reporting phase. If provided OOB, the ranging ground length may be set to include the ranging control phase and ranging phase.

[0334] This section describes the control and reporting messages used in the NBA-MMS-UWB ranging measurement cycle.

[0335] - A poll message is an NB message sent by the initiator in the first slot of a ranging ground to start a ranging measurement cycle within the ranging ground.

[0336] - A Responder (RESP) message is an NB message sent by the Responder in response to a received pole message at the start of a subsequent ranging slot after the first ranging slot.

[0337] - A Reporting Test (RPRT) message is an NB message sent by either the initiator or the responder to report ranging measurements to the peer.

[0338] For the transmission of control and reporting messages, the NB O-QPSK 250kbps PHY may be applied as the default. Other NB and UWB PHYs may be supported selectively.

[0339] Figure 22 shows examples of the NBA-MMS-UWB ranging control phase, ranging phase, and measurement reporting phase to which this disclosure can be applied.

[0340] Figure 22(a) shows an example of the NBA-MMS-UWB ranging control phase.

[0341] The NBA-MMS-UWB ranging control phase is performed at the start of the NBA-MMS-UWB ranging measurement cycle and may include two or more ranging control slots.

[0342] The initiator can start the NBA-MMS-UWB ranging control phase by sending a pole message to the responder at the start of the first ranging slot in the ranging ground. If LBT is not enabled, or if it is not, the NBA LBT may extend the initiator's pole transmission for up to the duration of RcpPollSlot. A responder who successfully receives the pole message may send a response message to the initiator in the ranging slot after RcpPollSlot from the start of the ranging control phase. If LBT is not enabled, or if it is not, the NBA LBT may extend the responder's response transmission for up to the duration of RcpResponseSlot. A responder who successfully sends a response message may continue the NBA-MMS-UWB ranging measurement cycle and enter the ranging phase. An initiator who successfully receives a response message may also continue the NBA-MMS-UWB ranging measurement cycle and enter the ranging phase.

[0343] A pole message can provide carrier frequency coherence from the initiator to the responder device. Control information may also be transmitted from the initiator to the responder via the pole message. For example, the pole message may include information requesting the responder to report the RNF (recommended number of fragments) during the measurement reporting phase.

[0344] The response message can provide carrier frequency coherence from the responder to the initiator device. Control information may also be transmitted from the responder to the initiator via the response message.

[0345] If LBT is enabled before transmission in the applicable operating bandwidth, the transmitting device may perform LBT before the expected start of transmission. If the performed LBT does not allow transmission at the start of the ranging slot, the transmitting device does not need to initiate further transmission for the remainder of the ranging ground.

[0346] The initiator may discontinue the NBA-MMS-UWB ranging measurement cycle if one or more of the following conditions are met:

[0347] - If LBT does not allow sending pole messages;

[0348] - If the initiator fails to receive a response message within the expected range slot; or

[0349] - If all ERDEVs request to skip ranging for the currently ranging block during the ranging control phase.

[0350] The responder may interrupt the NBA-MMS-UWB ranging measurement cycle if one or more of the following conditions are met:

[0351] - If a pole message is not received at the expected start of the ranged ground;

[0352] - If LBT does not allow sending a response message; or

[0353] - If all ERDEVs request to skip ranging for the currently ranging block during the ranging control phase.

[0354] If a ranging measurement cycle is terminated before completion, the ERDEV involved may stop transmitting NB and UWB until the next ranging measurement cycle.

[0355] Figure 22(b) shows an example of the NBA-MMS-UWB ranging phase.

[0356] The NBA-MMS-UWB ranging phase may begin when the NBA-MMS-UWB ranging control phase has finished.

[0357] The initiator can enter the ranging phase and begin transmitting the first UWB RSF fragment after RpInitiatorRsfOffset slots. The initiator can then transmit up to X UWB RSF fragments in succession at regular intervals of 1200 RSTUs. The initiator can enter the ranging phase and begin transmitting the first UWB RIF fragment after RpInitiatorRifOffset slots. The initiator can then transmit up to Y UWB RSF fragments in succession at regular intervals of 1200 RSTUs.

[0358] The initiator enters the ranging phase and can begin transmitting the first UWB RSF fragment after RpResponderRsfOffset slots. The initiator can then transmit up to X UWB RSF fragments in succession at regular intervals of 1200 RTUs. The initiator enters the ranging phase and can begin transmitting the first UWB RIF fragment after RpResponderRifOffset slots. The initiator can then transmit up to Y UWB RSF fragments in succession at regular intervals of 1200 RTUs.

[0359] The total duration of the ranging phase may correspond to RpDuration slots.

[0360] A ranging measurement report can be generated if one of the initiators or responders, an ERDEV, has completed receiving all UWB fragments during the ranging phase and is required to send a measurement report to its peer. In this case, the RpDuration value may be set to allow sufficient time until the subsequent measurement reporting phase.

[0361] When the in-band NBA-MMS-UWB measurement reporting phase is enabled for a ranging measurement cycle, an ERDEV that has completed the ranging phase can enter the measurement reporting phase based on the following conditions:

[0362] - If it is required to send a measurement report to the other party during the measurement reporting phase, and the measurement report is successfully generated; or

[0363] - When you anticipate receiving a measurement report from the other party during the measurement reporting phase.

[0364] If the NBA-MMS-UWB measurement reporting phase is not included in the NBA-MMS-UWB ranging measurement cycle, the ERDEVs involved may end the ranging measurement cycle after completing the ranging phase. ERDEVs required to send measurement reports to others may transmit the measurement reports to the next higher level, or the next higher level may request that the measurement reports be sent to others.

[0365] Figure 22(c) shows an example of the NBA-MMS-UWB measurement reporting phase.

[0366] In-band measurement reports may be transmitted during a selective measurement reporting phase. If enabled, the in-band measurement reporting phase may be initiated during the ranging phase.

[0367] In the following description, the in-band measurement reporting phase can be referred to as the reporting phase.

[0368] The reporting phase may include one or more packet slots. The duration of the first slot in the reporting phase may have the duration of MrpFirstSlot slots. The duration of the second slot in the reporting phase may have the duration of MrpSecondSlot slots.

[0369] If the reporting phase includes only one packet slot, the initiator or responder may send a measurement report packet in that slot. Whether a device sends a report packet and whether it is the initiator or responder may be determined by the reporting mode.

[0370] If the reporting phase includes two packet slots, the responder may send the reporting packet in the first slot, and the initiator may send the reporting packet in the second slot.

[0371] The measurement reporting phase may include unidirectional or bidirectional report exchange. The transmission of report packets may be scheduled in the first two ranging slots of the measurement reporting phase, according to the following configuration modes:

[0372] [Table 10]

[0373] For bidirectional reporting, the transmission of reports may be carried out independently in the first and second slots of the measurement reporting phase. In particular, the responder may transmit their own measurement report in the second slot, independently of whether or not they received the initiator's report in the first slot.

[0374] The reporting message can primarily provide ranging metric results obtained during the ranging phase. The reporting message may also be used for other purposes. For example, if the responder receives a recommended number of fragments (RNF) request from the initiator during the control phase, the reporting message sent by the responder may include an RNF report. The initiator can use the RNF to determine the updated number of fragments to be used in subsequent rounds.

[0375] If an ERDEV is unable to transmit a measurement report during its assigned slot in the measurement reporting phase, it may defer or attempt to retransmit it using higher layers or OOB radio technology operations. If an ERDEV is unable to receive a measurement report during its assigned slot in the measurement reporting phase, it may request retransmission using higher layers or OOB radio technology operations in a subsequent ranging block until the start of the next MMS ranging cycle.

[0376] NBA-MMS-UWB Initialization and Setup

[0377] An NBA-MMS-UWB ranging session may be configured by a set of parameters for the PHY and MAC. The set of PHY parameters may include NB and UWB channels, modulation, and data rate, used in the control phase, ranging phase, and measurement reporting phase. The set of MAC parameters may include slot, round, and block settings for the control phase, ranging phase, and measurement reporting phase.

[0378] To initiate an NBA-MMS-UWB ranging session, the initiator and responder device pair may engage in negotiations during the initialization and setup phases regarding ranging settings different from the default parameter set. Out-of-bounds (OOB) communication may be used to set up session parameters or to change the initialization channel and modulation, and this may also be done before the initialization and setup phases.

[0379] Figure 23 illustrates the ranging session initialization and setup to which this disclosure can be applied.

[0380] First, let's explain ranging session initialization.

[0381] Before entering the ranging control phase, the ERDEV may participate in the initialization and setup phase. The initialization and setup phase can provide time synchronization for the first pole packet transmitted by the initiator during the ranging control phase that occurs. Alternatively, the ranging session configuration may be modified by two-way handshake packet exchange between ERDEVs. Unless otherwise agreed upon during initialization and setup, default ranging configuration parameters may be used for the ranging session. Alternatively, the ranging session configuration may be set up by OOB radio technology.

[0382] To establish in-band initialization, ERDEV can opportunistically transmit and receive on a dedicated initialization channel and PHY modulation based on the ranging session configuration. The initiator can opportunistically transmit advertising pole (ADV-POLL) packets at times and intervals that it deems appropriate, based on its own judgment and supported by higher-layer functions. Similarly, the responder can attempt to listen for incoming ADV-POLL packets.

[0383] After sending an ADV-POLL on the initialization channel, the initiator can attempt to receive an incoming advertising response packet (ADV-RESP) in a subsequent ranging slot. If the responder receives the ADV-POLL, they can send an ADV-RESP in a subsequent ranging slot. If the responder sends an ADV-RESP, they can attempt to receive a start of ranging (SOR) packet in a ranging slot following the ADV-RESP packet. If the initiator receives the ADV-RESP packet, they can send an SOR packet in a ranging slot following the ADV-RESP packet.

[0384] After sending the SOR packet, the initiator may enter the ranging control phase. During the ranging control phase, if the initiator confirms receipt of the RESP from the responder, and unless further ERDEV initialization is requested, the initiator may interrupt ranging initialization and stop sending ADV-POLL packets.

[0385] In response to the initialization setup handshake, the responder (or controlled party) can request ranging session configuration via ADV-RESP. The initiator (or controller) can receive the request from the responder via ADV-RESP, configure the session settings, and send those settings to the responder via SOR.

[0386] For ranging session settings, the ranging block structure and ranging measurement cycle may be configured before the NBA-MMS-UWB ranging session begins. During ranging setup, the ranging parameters may not be changed, or the next higher layer may apply default parameters to the ranging session settings. During the NBA-MMS-UWB ranging session, some parameters for the ranging block structure and ranging measurement cycle may be updated by the next higher layer. For each parameter update, the next higher layer may indicate the index of the ranging block in which the new parameter becomes effective.

[0387] The initiator and responder can use parameters set or updated by their respective next-level counterparts as long-term operating parameters.

[0388] The initiator may overwrite the long-term operating parameters for a ranging measurement cycle by instructing a new set of short-term parameters during the ranging control phase. The short-term parameters may be valid only for the immediate ranging measurement cycle. The long-term operating parameters may be valid again for the next ranging measurement cycle unless they are overwritten again during the ranging control phase.

[0389] The responder may request short-term operating parameters for the next ranging measurement during the ranging control phase. The initiator may also provide or ignore parameters at the responder's request in the next ranging cycle.

[0390] General parameters for an NBA-MMS-UWB ranging session may include default values ​​and configurable ranges or options for initialization channels, allowable lists of control and reporting channels, UWB control channels and preambles, PHY rate, NB LBT channels, whether round hopping is applied, and channel switching method. Block structure parameters may include default values ​​and configurable ranges or options for ranging block duration, ranging ground duration, ranging slot duration, etc. The ranging measurement cycle parameters may include RcpPollSlot, RcpResponseSlot for the ranging control phase; the number of RSF fragments (X), the number of RIF fragments (Y), RpDuration, RpInitiatorRsfOffset, RpResponderRsfOffset, RpInitiatorRifOffset, RpResponderRifOffset, RSF code index, RSF complementation set, RIF fragment length in 512-chip units, N_MSR; default values ​​for in-band reporting, reporting mode, MrpFirstSlot, MrpSecondSlot, etc., and a range of configurable values ​​or options.

[0391] NBA-MMS-UWB control channel messages

[0392] Existing PSDU formats defined for each of the various PHYs may be applied to NBA-MMS-UWB control channel messages. A compressed PSDU format may be used when NB is used for control messages, reporting messages, and initialization messages.

[0393] A compressed PSDU format may be defined as containing only a one-octet header with a message ID. The remaining PSDU content may be determined solely by the message ID. Examples of compressed PSDU formats for messages used during the initialization, setup, control, and reporting phases are shown in the table below. Compressed PSDU messages may be encapsulated in headers IE of specific data field types.

[0394] [Table 11]

[0395] In the control phase messages, POLL messages may correspond to qualifying pole messages, and RESP messages may correspond to qualifying response messages. After receiving an NbaChannelMap from the initiator, the responder must be able to determine an NbaChannelAllowList, which can then be applied to assign NB channels to each ranging. Various other pole messages may be further defined.

[0396] In the measurement reporting phase messages, RPRT messages from the responder and RPRT messages from the initiator are defined to have a message ID that distinguishes them, and RPRT2 messages may be messages used in the session control process. Message ID values ​​0x04 to 0x1f may be reserved for the session control and reporting phases.

[0397] In the initialization phase messages, message ID values ​​0x23 to 0x2f may be reserved for out-of-session use.

[0398] Other message ID values, from 0x7f to 0xff, are defined for vendor-specific message content and may correspond to a 128x256 PSDU with a 2-byte message ID.

[0399] In the compressed PSDU message fields, the CRC16 field is defined as 16 bits long and may correspond to a 2-octet frame check sequence (FCS). The ADDR field may correspond to the address field. The compressed PSDU message may further include various other fields.

[0400] UWB channel usage adjustment

[0401] To reduce mutual interference between adjacent UWB transmitters and support good coexistence, UWB channel (CH) usage coordination may be applied. UWB transceiver types may include NBA-UWB transceiver types and standalone UWB transceiver types. For example, coordination of UWB channel usage between NBA UWB transceivers may be performed via a mirroring (or initialization) channel. The following describes UWB channel usage coordination methods applicable to all standalone UWB transceivers, not just NBA UWB transceivers.

[0402] Unless otherwise specified in the following description, UWB transceivers refer to NBA UWB transceivers, standalone UWB transceivers, or both types. Signaling for coordinating UWB channel usage may be required to be decoupled from other UWB sessions on the UWB transceiver. Such UWB channel usage coordination may be required or optional by the UWB transceiver. For example, transmitting coordination signaling may be required / optional, and operating based on information received by coordination signaling may also be required / optional.

[0403] Figure 24 shows an example of AP transmission / reception operation to which this disclosure can be applied.

[0404] As illustrated in Figure 24(a), an initiator, which is a UWB transceiver, can periodically transmit UWB-APs (acquisition packets) on a predefined UWB discovery channel. The UWB-APs may contain information that can be used to determine all future UWB channel usage by the initiator. The UWB transceiver can discover the initiator by receiving the UWB-APs. The UWB-AP interval may be set to an appropriate value (e.g., depending on the use case). Some of the periodically transmitted UWB-APs may be skipped by ranging overlap. In the example in Figure 24(a), n, n+1, n+2, ... may correspond to NBA-UWB ranging block indices.

[0405] As illustrated in Figure 24(b), UWB-AP scanning by a UWB receiver (Rx) may be optimized for an NBA UWB transceiver. An NBA UWB initiator may periodically transmit NB-APs on a predefined NB discovery channel. An NB-AP may contain information that can be used to determine the occurrence of the next UWB-AP. An NB-AP may contain information that can be used to determine all future UWB channel usage by the initiator. An NB-AP interval may be associated with a UWB-AP interval. For example, the NB-AP interval may be the same as the UWB-AP interval, and the time interval between the NB-AP transmission time and the UWB-AP transmission time may be dT1. Some of the periodically transmitted NB-APs may be skipped due to ranging overlap.

[0406] Figures 25 and 26 illustrate examples of AP transmission and reception operations in multiple RANs to which this disclosure can be applied.

[0407] In the examples in Figures 25 and 26, RAN (ranging area network) 1 is assumed to include one initiator (RAN1 initiator) and one or more responders (RAN1 responder), and is currently in ranging operation. RAN2 is assumed to include one initiator (RAN2 initiator) and one or more responders (RAN2 responder), and is in startup or operation.

[0408] In the example shown in Figure 25, the RAN1 initiator can periodically transmit NB-APs and UWB-APs on the NB discovery channel and UWB discovery channel. This allows the RAN1 responder to be activated on the UWB channel, determined based on the information contained in the NB-APs and UWB-APs, at the first ranging ground of each ranging block, and perform ranging operations.

[0409] The RAN2 initiator can receive NB-APs and UWB-APs transmitted by the RAN1 initiator. For example, the RAN2 initiator can receive NB-APs transmitted by the RAN1 initiator in the NB scanning window (NB ScanWin), and then receive UWB-APs transmitted by the RAN1 initiator in the UWB ScanWin. This allows the RAN2 initiator to acquire / extract RAN1 information (e.g., information per UWB session). For example, RAN1 information may include information on ranging blocks, rounds, and slot durations, information on RF channel and preamble usage, and information on synchronization parameters. Based on such RAN1 information, the RAN2 initiator can start its ranging and advertising sessions at a time that does not overlap with RAN1. This allows the RAN2 initiator to periodically transmit NB-APs and UWB-APs.

[0410] In the example shown in Figure 26, the RAN1 initiator can periodically transmit NB-APs on NB discovery. This allows the RAN1 responder to be activated on the UWB channel determined based on the information contained in the NB-AP, at the first ranging ground of each ranging block, and perform ranging operations.

[0411] The RAN2 initiator can receive NB-APs transmitted by the RAN1 initiator. For example, the RAN2 initiator can receive NB-APs transmitted by the RAN1 initiator in the NB Scanning Window (NB ScanWin). This allows the RAN2 initiator to obtain / extract RAN1 information (e.g., information about the RAN's active intervals). For example, information about the RAN1's ​​active intervals may include information about the time remaining until the start of the active interval (or active round) (e.g., dT2), information about the duration of the active round, etc. Based on such RAN1 information, the RAN2 initiator can select an idle interval that does not overlap with the RAN1's ​​active interval and start its own new session. This allows the RAN2 initiator to periodically transmit NB-APs.

[0412] The NB-AP format and UWB-AP format are described below.

[0413] Both the NB-AP format and the UWB-AP format may include an SHR field, a PHR field, and a PHY payload field (i.e., PSDU), as described with reference to Figure 2. The PHR field can indicate the length of the PSDU, for example, with a value in the range of 0 to 127 bytes. The PSDU may include an MHR (MAC header) field, a MAC payload field, and an MFR (MAC footer) field. The NB-AP packet type may be O-QPSK, and the UWB-AP packet type may be BPRF.

[0414] An NB-AP may have a compact frame format corresponding to a compressed PSDU. The compact frame may include a 3-bit frame type field, a 5-bit compact frame ID field, and a variable-size compact frame content field. The compact frame (or acquisition compact frame) format for the AP may include a 3-octet address field, a 1-octet message control field, a variable-size message content field, and a 2-octet FCS field.

[0415] The AP's MHR field may contain the following information:

[0416] [Table 12]

[0417] The MAC payload field of a UWB-AP may contain the following information:

[0418] [Table 13]

[0419] The per-session info field may exist in a single coordinated UWB-AP. A new RAN initiator can minimize conflicts with existing RANs by selecting one or more parameters in the per-session info field to other values.

[0420] The MAC payload field of NB-AP may contain the following information:

[0421] [Table 14]

[0422] Compressed tuned NB-AP packets do not include session-specific information fields. Tuned NB-AP packets may include session-specific information fields. Session-specific information fields may overlap with those in tuned UWB-AP packets. UWB-AP information fields are included in NB-AP packets if the value of the UWB-AP existence field is 1, and not included in NB-AP packets if its value is 0.

[0423] Referring again to Figure 25, the time interval (dT1) from the start of the NB-AP to the start of the UWB-AP may be indicated by the value of the Delta T parameter in the UWB-AP information field of the NB-AP. Furthermore, the UWB channel on which the UWB-AP is transmitted after dT1 may be indicated by the value of the UWB channel parameter in the UWB-AP information field.

[0424] NB-AP may or may not include a UWB session information field. Whether or not an NB-AP includes a UWB session information field, and what information is included in the UWB session information field, may be indicated by the UWB per session info type field of the NB-AP. The UWB session information field may exist in the NB-AP regardless of whether or not a UWB-AP is transmitted. Four types may be applied to the UWB session information field.

[0425] If the value of the information type field for each UWB session is 0, then the UWB session information field does not exist in NB-AP.

[0426] If the value of the Information Type field for each UWB session is 1, then the NB-AP has a UWB session information field, which may contain a minimum set of session information such as the following:

[0427] [Table 15]

[0428] If the value of the information type field for each UWB session is 2, the NB-AP may contain a UWB session information field that includes information about the start time and duration of the active period.

[0429] [Table 16]

[0430] Referring again to Figure 25, the time length (dT2) from the start of NB-AP to the start of the active interval may be indicated by the value of the Delta T parameter in the session-specific information field of NB-AP. The duration from the start to the end of the active interval may be indicated by the value of the active interval duration field in the session-specific information field of NB-AP.

[0431] If the value of the Information Type field for each UWB session is 3, the NB-AP may contain a UWB session information field that includes information about the start time and duration of the active rounds in the block.

[0432] [Table 17]

[0433] Referring again to Figure 25, the time length (dT2) from the start of NB-AP to the start of a block may be indicated by the value of the Delta T parameter in the session-specific information field of NB-AP. Furthermore, the position and duration of an active round may be indicated by the index of the active round in a bitmap of length determined by the number of rounds in a block (number of rounds in a block parameter) (active rounds parameter), and the active round may be revealed after a duration equal to the number of inactive rounds (0 in the example in Figure 25) has elapsed from the start of the block to the start of the active round (Round duration parameter).

[0434] Initial setup and channel usage adjustment

[0435] As mentioned above, NBA-UWB can provide technologies such as mirroring (or initialization) channels, NBA-MMS-UWB, NBA TDoA, and NBA-sensing. NBA-UWB can use NB channels (e.g., 2.5 MHz bandwidth) in bandwidths such as UNII-3 and UNII-5 to assist UWB operation. Specific characteristics of NB may correspond to in-band technologies defined by the IEEE 802.15.4 series of standards.

[0436] As previously mentioned regarding NBA-MMS-UWB, NB channels can be used to improve the UWB link budget. In an NBA-MMS-UWB ranging ground, the In-Band Measurement Reporting Phase (MRP) may be defined as an optional configuration, and the ranging ground may include the Ranging Control Phase (RCP) and Ranging Phase (RP) as mandatory configurations. The frames / packets and durations exchanged between devices in the RCP, RP, and MRP are as described with reference to Figure 22.

[0437] As previously mentioned with reference to Figure 23, time synchronization information may be provided in the first pole packet sent by the initiator via RCP during NBA-MMS-UWB initialization and setup. In addition, to initiate an NBA-MMS-UWB ranging session, the initiator and responder are required to perform a discovery (or initialization) and setup process to discuss ranging settings different from the default parameter set.

[0438] For the UWB native discovery (or initialization) and setup process, as described above, the initiator may periodically broadcast ADV-POLL packets on the discovery (or initialization) channel. The discovery (or initialization) channel on which ADV-POLL is broadcast may be an NB channel if the device has NBA-UWB capability, or a UWB channel if the device does not support NBA-UWB.

[0439] Furthermore, in the UWB channel usage adjustment described with reference to Figures 24 to 26, acquisition packets (APs) containing network scheduling information may be periodically broadcast on the discovery (or initialization) channel, similar to the NBA-MMS-UWB discovery (or initialization) and setup process.

[0440] As illustrated in the examples in Figures 24 and 25, the UWB-AP may be advertised after the NB-AP containing the UWB Info field has been transmitted. The UWB Info field may include information such as the UWB channel on which the UWB-AP operates, delta T (i.e., the remaining time until the next UWB-AP advertisement based on the current packet), and the preamble code used by the UWB-AP. The UWB-AP may also include a per-session info field to inform other controllers (e.g., UWB channel usage coordination information).

[0441] Unlike the examples in Figures 24 and 25 for UWB channel usage coordination using UWB-AP, in the example in Figure 26 which uses only NB-AP without UWB-AP, the UWB-AP is not broadcast, so the NB-AP does not include the UWB-AP Info field and may include a per-session info field (e.g., UWB channel usage coordination information) to inform other controllers.

[0442] The ADV-POLL used for discovery (or initialization) and setup, and the AP used for channel usage adjustment, as described above, have different uses, but they are both broadcast on the discovery (or initialization) channel. Because the number of NB discovery (or initialization) channels and / or UWB discovery (or initialization) channels is limited (e.g., one or two), the likelihood of broadcast packet collisions increases as the number of UWB devices performing discovery (or initialization) and setup operations and channel usage adjustment operations simultaneously increases. If broadcast packets are not accurately transmitted to the necessary receiving devices due to collisions, the performance of discovery (or initialization) and setup operations and / or channel usage adjustment operations may degrade. A new approach is needed to prevent such performance degradation problems.

[0443] Various examples of how this disclosure optimizes discovery (or initialization) and setup operations and channel usage adjustment operations are described below.

[0444] In some embodiments of this disclosure, a new response message (e.g., an ADV-RESP message) may be defined to assist in requesting channel usage information (CUI) during the discovery (or initialization) and setup process. The new response message may correspond to an advertising message (e.g., an ADV-POLL message).

[0445] Figure 27 shows examples of advertising message formats and response message formats related to this disclosure.

[0446] Figure 27(a) shows an example of an ADV-POLL payload (PSDU) packet format (e.g., NB O-QPSK case). The ADV-POLL packet format may include a one-octet ID field (e.g., ID=0x20 (see Table 11)), a two-octet address (ADDR) field, a one-octet RFU (i.e., reservation) field, and a two-octet CRC field. The ADV-POLL message may include the address (ADDR) field to indicate the presence of the device broadcasting it. If the address information of the device sending the ADV-POLL is included in the header, the ADDR field may be omitted in the PSDU, thereby reducing the ADV-POLL size.

[0447] Figure 27(b) shows an example of the ADV-POLL IE format (e.g., UWB case). The UWB header IE packet format may include a 7-bit length field, an 8-bit element ID field, a 1-bit type field, a 2-octet ADDR field, and a 1-octet RFU field. For example, the element ID may be set to a value corresponding to ADV-POLL (e.g., one value between 0x80 and 0xFF, e.g., 0x80). The type field may be set to 0.

[0448] ADV-POLL messages / packets during such discovery / initialization and setup may be broadcast on the NB discovery / initialization channel or the UWB discovery / initialization channel. Acquisition packets (APs) during channel usage adjustment may also be broadcast on the NB / UWB discovery / initialization channel. AP messages / packets may be broadcast to inform other controllers of scheduling information for the RAN to which the initiator belongs, and may include fields as shown in Tables 13 to 17 above.

[0449] When ADV-POLL and AP broadcast on the same NB / UWB discovery / initialization channel, channel congestion and collisions are expected to occur, leading to performance degradation not only in the discovery / initialization and setup processes but also in the channel usage adjustment process. To prevent such problems, improvements to UWB advertising packets that support concurrent ranging session initialization and channel usage adjustment can be considered. In this regard, an example of improving response messages to advertising messages (e.g., ADV-RESP) is described below.

[0450] The responder becomes aware of the initiator's presence by receiving an ADV-POLL broadcast by the initiator during the discovery (or initialization) and setup process. After the responder receives the ADV-POLL, a two-way handshake process may take place. The responder sends an ADV-RESP in response to the ADV-POLL, and the initiator, upon receiving the ADV-RESP, can send a SOR, allowing the responder to join the ranging session. This two-way handshake process can be used to extend advertising packets beyond discovery (or initialization) and setup to also be used for channel usage coordination. For example, the ranging session may be initialized based on the information contained in the ADV-RESP sent by the responder, or channel usage information may be requested.

[0451] Figure 27(c) shows an example of an ADV-RESP payload (PSDU) packet format (e.g., NB O-QPSK case). The ADV-RESP packet format may include a one-octet ID field (e.g., ID=0x21 (see Table 11)), a two-octet address (ADDR) field, a one-octet request mode field, and a two-octet CRC field. The ADDR field may be set to the responder's address value. If the address information of the device sending the ADV-RESP is included in the header, the ADDR field may be omitted in the PSDU, thereby reducing the ADV-RESP size. Here, unlike existing ADV-RESP formats where one octet between the ADDR field and the CRC field is reserved (RFU), the ADV-RESP format according to this disclosure includes a new request mode field.

[0452] Figure 27(d) shows an example of an ADV-RESP IE format (e.g., UWB case). The UWB header IE packet format may include a 7-bit length field, an 8-bit element ID field, a 1-bit type field, a 2-octet ADDR field, a 1-octet requested mode field, and a 1-octet RFU field. For example, the element ID may be set to a value corresponding to ADV-RESP (e.g., one value between 0x80 and 0xFF, e.g., 0x81). The type field may be set to 0. Here, unlike existing ADV-RESP formats in which the two octets following the ADDR field are reserved (i.e., RFU), the ADV-RESP format according to this disclosure includes a new requested mode field.

[0453] The solicitation mode field included in the aforementioned ADV-RESP may contain information indicating whether the responder is requesting ranging session setup or information for channel usage adjustment. Upon receiving an ADV-RESP containing such a solicitation mode field, the initiator (i.e., advertising device) may send a SOR or a CUI based on the value of the solicitation mode field, followed by a frame exchange sequence.

[0454] For example, the request mode field may be defined as being 2 bits in size. If the request mode field is set to a first value (e.g., 00), it may indicate that a ranging session is requested. If the request mode field is set to a second value (e.g., 01), it may indicate that channel usage coordination information (CUI) is requested. The third (e.g., 10) and fourth (e.g., 11) values ​​of the request mode field may be defined for other uses or reserved.

[0455] Alternatively, the request mode field may be defined as having a size of 1 bit. If the request mode field is set to a first value (e.g., 0), it may indicate that a ranging session is requested. If the request mode field is set to a second value (e.g., 1), it may indicate that channel usage coordination information (CUI) is requested.

[0456] In some embodiments of this disclosure, a message exchange between an initiator and a responder may be defined based on a response message that includes a request mode field.

[0457] Figure 28 is a diagram illustrating an example of message exchange between the initiator and responder in this disclosure.

[0458] Figure 28(a) illustrates a two-way handshake procedure when the value of the request mode field in the ADV-RESP sent by the responder in response to the ADV-POLL sent by the initiator is the first value. When the request mode is the first value, the responder indicates that they are requesting a ranging session setup, and the initiator can send a SOR message. The subsequent operations on the ranging channel may be as described with reference to Figure 23.

[0459] Figure 28(b) illustrates a two-way handshake procedure when the value of the request mode field in the ADV-RESP sent by the responder in response to the ADV-POLL sent by the initiator is a second value. When the request mode is a second value, it indicates that the initiator is requesting channel usage information (CUI), so the initiator can send a CUI message. For example, the CUI message may contain some or all of the information exemplified in Tables 13 to 17 above.

[0460] Here, the responder may belong to the same RAN as the initiator, or to a different RAN from the one the initiator belongs to. For example, the initiator in Figure 28(b) may be initiator 1 of RAN1, and the responder in Figure 28(b) may be initiator 2 of RAN2. The responder (or initiator 2 of RAN2) may request channel usage information from the initiator (e.g., initiator 1 of RAN1) for collision avoidance.

[0461] Figure 28(c) shows an example of an initiator broadcasting a CUI message. For example, an initiator may broadcast a CUI message considering its own status (e.g., resource status), channel status, etc., so that other surrounding devices can obtain its channel usage information. Other devices that obtain the CUI may be initiators of other RANs. For example, a CUI related to RAN1 broadcast by initiator 1 belonging to RAN1 may be obtained by devices belonging to other RANs (or that are starting or operating other RANs) (e.g., initiator 2 belonging to RAN2, and / or initiator 3 belonging to RAN3) and used to configure the RANs of those devices.

[0462] For example, if the value of the request mode field in the ADV-RESP sent by a responder (or another RAN's initiator 2) in response to an ADV-POLL sent by initiator 1 is the second value, initiator 1 can broadcast a CUI. This allows not only the responder who sent the response message, but also other surrounding devices (e.g., initiator 3) to obtain initiator 1's CUI. Specifically, initiator 3 can opportunistically scan the CUI message from initiator 1. In this way, initiator 3 can obtain CUI information related to other initiators (or other RANs) without performing a two-way handshake procedure using ADV-POLL reception and ADV-RESP response, and utilize this when changing the channel of a RAN3 while initiating or operating RAN3. For example, initiator 3 can select / determine the channel related to RAN3 while avoiding (i.e., avoiding overlap) the channel related to initiator 1 (or RAN1).

[0463] For example, initiators 2 and 3 can obtain the same CUI from initiator 1 and use it to select / determine a channel related to their own RAN (or by avoiding channels related to initiator 1 / RAN1). In this case, if initiators 2 and 3 do not know each other's channel information, they may attempt to access the same UWB medium simultaneously. Such collision problems can be avoided or mitigated using backoff timers, random delay timers, etc. For example, a device attempting to access a channel selected based on (or by avoiding) a CUI broadcast by another device can select a backoff / random delay timer based on a predetermined rule and access that channel when the timer expires.

[0464] Figure 29 shows an example of concurrent ranging sessions and the exchange of channel usage adjustment information between devices belonging to different RANs as described in this disclosure.

[0465] In the example shown in Figure 29, assume that initiator 1, responder 1, and responder 2, all belonging to RAN1, are in the process of ranging, and responder 3 is performing UWB scanning. Also assume that initiator 2 is in the process of starting or operating another RAN (e.g., RAN2).

[0466] Initiator 1, belonging to RAN1, is in the middle of a ranging session (on the ranging channel) with Responders 1 and 2, and can periodically broadcast ADV-POLL messages on the discovery (or initialization) channel.

[0467] Responder 3 can perform a scan on the discovery (or initialization) channel to join the ranging session of RAN1. If Responder 3 discovers / receives an ADV-POLL sent by Initiator 1 during the scanning process, Responder 3 can send an ADV-RESP to Initiator 1. Here, the value of the request mode field included in the ADV-RESP sent by Responder 3 may be set to a first value (i.e., a ranging session is requested). If Initiator 1 receives the ADV-RESP from Responder 3 and the request mode field indicates a first value (i.e., a ranging session is requested), Initiator 1 can send a SOR to Responder 3 in response. Responder 3, having received the SOR, can then join the ranging session in other ranging blocks. For example, from the time offset, ranging channel information, etc., included in the SOR, Responder 3 can determine that ranging ground 1 is an active round in ranging block n+1 and can begin joining RAN1 in slot 3 of the active slots 1, 2, and 3 within the active ranging ground.

[0468] Initiator 2, which is attempting to start or is already operating RAN2, can scan discovery (or initialization) channels for channel usage adjustment. Upon discovering / receiving an ADV-POLL sent from Initiator 1 through scanning, Initiator 2 can send an ADV-RESP to Initiator 1. Here, the value of the request mode field included in the ADV-RESP sent by Initiator 2 may be set to a second value (i.e., Channel Usage Information (CUI) is requested). If Initiator 1 receives an ADV-RESP from Initiator 2 and the request mode field indicates a second value (i.e., CUI is requested), Initiator 1 can send a CUI to Initiator 2 in response. Upon receiving the CUI, Initiator 2 can start RAN2 by scheduling / setting the ranging session and ranging channels for RAN2 so as not to overlap with RAN1. For example, Initiator 2 can obtain the RAN1 scheduling information (e.g., ranging duration, number of rounds, and active rounds). Initiator 2 can configure its own channel (or RAN2) so as not to overlap with channels associated with Initiator 1 (or RAN1). In addition, Initiator 2 can periodically broadcast its ADV-POLL on the discovery (or initialization) channel so as not to overlap with Initiator 1.

[0469] Unlike existing UWB systems, where RAN channel information cannot be shared with other devices during discovery (or initialization) and setup, and is only provided through channel usage coordination procedures by NB-AP or UWB-AP, this disclosure allows ranging session requests or channel usage information requests to be executed simultaneously by response messages to advertising messages (e.g., ADV-POLL), and other devices that do not send response messages can also obtain the advertising device's channel usage information. This supports ranging session participation and / or channel usage information sharing more quickly and efficiently, thereby achieving a new effect of reducing collisions by channel avoidance between devices belonging to different RANs.

[0470] Various advertising-based discovery / initialization and setup

[0471] The following describes various advertising options applicable to native discovery / initialization and setup for NBA-MMS-UWB.

[0472] As mentioned above, for discovery / initialization, the initiator can advertise to make themselves known, and the responder can scan to discover them. The responder can then set up a ranging session based on the advertising information obtained. For various use cases of such discovery / initialization and session setup, various options may be considered, such as when advertising that supports device privacy (i.e., private advertising) or when public advertising is required. This may enable discovery / initialization and setup to be supported in-band (i.e., NB channel / UWB channel) (i.e., without information exchange via OOB).

[0473] To this end, it is necessary to define secured / private advertising messages or unsecured / public advertising messages (e.g., advertising pole frames). Various examples of discovery / initialization and setup processes based on such various advertisements are described below.

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

[0475] In the examples shown in Figures 30 and 31, the first device may correspond to the initiator or controller, and the second device may correspond to the responder or controlled party.

[0476] In step S3010, the first device can generate an advertising pole frame that includes a frame identifier field.

[0477] For example, multiple advertising pole frames may be defined in relation to whether or not a public address is used for session initialization. In this case, the frame identifier field of the advertising pole frame may be defined / set to different values ​​for each of the multiple advertising pole frames. For example, the frame identifier field may be defined / set to a first value for a public advertising pole frame. Alternatively, the frame identifier field may be set to a second value for advertising pole frames other than public advertising pole frames (e.g., private advertising pole frames, or (simply) advertising pole frames).

[0478] When multiple advertising pole frames are defined, a public advertising pole frame may contain a public address (e.g., a random address) generated by the first device. Alternatively, advertising pole frames other than public advertising pole frames (e.g., a private advertising pole frame, or simply an advertising pole frame) may contain a private address (e.g., an address generated based on a specific encryption / secret key) generated by the first device.

[0479] As another example, an advertising pole frame may be defined as a single-frame format. In this case, the frame identifier field of the advertising pole frame may be defined / set to a single value (i.e., a value indicating that it is an advertising pole frame).

[0480] Such a single-frame format for advertising pole frames may include security-related information. This security-related information may include information regarding security levels and / or security modes.

[0481] For example, security level information can indicate one of the following: Level 1 (e.g., an unencrypted advertising pole), Level 2 (e.g., an encrypted advertising pole associated with a peer device holding an encryption key), or Level 3 (e.g., an encrypted advertising pole associated with a group of devices holding an encryption key).

[0482] For example, information regarding the security mode can indicate one of two modes: a first mode (e.g., an unencrypted advertising pole) or a second mode (e.g., an encrypted advertising pole).

[0483] The various illustrative (public) advertising pole frames in this disclosure may be included in a UWB PPDU (e.g., a PPDU including the SHR, PHR, and PHY payload as described with reference to Figures 2 and 3). Alternatively, the various illustrative (public) advertising pole frames in this disclosure may be included in an O-QPSK based PPDU in NB (e.g., a PPDU including the preamble, SFD, PHR, and payload as described above). For example, the advertising pole frame / public advertising pole frame may be included in the PHY payload of a UWB / NB PPDU.

[0484] In step S3020, the first device can transmit an advertising pole frame. For example, the advertising pole frame may be transmitted / broadcast by the first device so that it is received by the scanning operation of one or more second devices.

[0485] As a concrete example of the operation of the first device, the broadcasting of advertising packets may begin in accordance with instructions from a higher layer, such as the MAC layer, of the first device. The first device (i.e., the advertiser) can generate secured / private advertising packets or unsecured / public advertising packets depending on security-related information from a higher layer (e.g., security level, security mode, etc.). The first device can broadcast the generated advertising packets at predetermined time intervals. If the higher layer instructs the first device to stop broadcasting, the advertising packet transmission operation may terminate.

[0486] The method illustrated in the example in Figure 30 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 an advertising pole frame including a frame identifier field and to transmit the advertising pole frame to one or more second devices via one or more transceivers 106. Here, the frame identifier field may be set to different values ​​for each of the multiple advertising pole frames, based on the fact that multiple advertising pole frames are defined in relation to whether or not a public address is used for session initialization. For example, the processor 102 can generate various packets / messages such as ADV-POLL and ADV-POLL2, which will be described later, based on the information stored in the memory 104. Furthermore, one or more memories 104 of the first device 100 may store instructions for performing the method illustrated in Figure 30 or the examples described later, when executed by one or more processors 102.

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

[0488] In step S3110, the second device can receive an advertising pole frame containing a frame identifier field from the first device. For example, the second device can discover an advertising pole frame through a scanning process and obtain the information. For example, if multiple advertising pole frames related to the use of a public address are defined, the second device can determine which advertising pole frame it corresponds to based on the value of the frame identifier field and obtain the information composed of that frame format.

[0489] In step S3120, the second device can perform a session initialization process based on the information contained in the received advertising pole frame. For example, the second device may send a (public) advertising response frame to the first device and attempt to receive subsequent frames (e.g., SOR) from the first device.

[0490] Specific explanations related to single or multiple advertising pole frame formats are the same as those explained with reference to Figure 30, and redundant explanations are omitted.

[0491] As a concrete example of the operation of the second device, the second device can initiate a scanning operation in response to a higher-layer instruction. The second device (i.e., the scanner) can periodically scan the discovery / initialization channel to find advertising packets broadcast from the first device (i.e., the advertiser). If it is confirmed that an advertising packet is contained within a PPDU discovered by scanning, a post-processing stage can be performed for processing according to the security level / security mode based on the security-related information contained in the advertising packet (e.g., security level, security mode). In the post-processing stage, the security level / security mode may be used to interpret / parse the security region of the secured / private advertising pole frame. If the scanner has information for interpreting / parsing the security region, it can obtain the necessary information within the security region (e.g., private address) and perform a two-way handshake operation for ranging session setup (e.g., sending an advertising response frame). If necessary information cannot be obtained, the received advertising pole frame cannot be used, and the scanning operation may continue until a scanning abort command is provided by a higher layer. If the discovered / received advertising packet is an unsecured / public advertising pole frame, the scanner may analyze / parse the frame and perform a two-way handshake operation for ranging session setup.

[0492] The method illustrated in Figure 31 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 advertising pole frames containing a frame identifier field from the first device via one or more transceivers 206, and to perform a session initialization process based on the information contained in the advertising pole frames. Here, the frame identifier field may be set to different values ​​for each of the multiple advertising pole frames, based on the fact that multiple advertising pole frames are defined in relation to whether or not a public address is used for session initialization. Messages / packets received via the transceivers 206 may be stored in memory 204. The processor 202 can decode the messages / packets stored in memory 204. The processor 202 can acquire control information contained in the messages / packets and store the acquired control information in memory 204. The processor 202 can remove noise and interference by amplification and filtering, and convert the signal into binary data through the processes of sampling, demodulation, and decoding. For example, a BPSK or O-QPSK demodulator may be used in the decoding process, and processes such as mapping the chip to symbols, convolution, and Reed-Solomon decoding may be performed. The recovered data may be used to extract the original information transmitted from the transmitting end. Such a process may include various error correction and data recovery techniques to verify that the transmitted data has been received accurately. The processor 202 can also decode the data fields of packets received via the transceiver 206. The processor 202 can also process the decoded data.For example, the processor 202 can transmit information about the decoded data field to a higher layer (e.g., the MAC layer), and if the higher layer instructs the PHY layer to generate a signal in response, it can perform subsequent operations. Furthermore, one or more memories 204 of the second device 200 can store instructions for performing the methods illustrated in Figure 31 or described in the examples later, when executed by one or more processors 202.

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

[0494] Example 1

[0495] Advertising poles (ADV_POLL) may be broadcast over discovery / initialization channels. In use cases where privacy must be guaranteed, secure advertising is required to a single device or group of devices that have been verified in advance through authentication or other procedures. Alternatively, in use cases where ranging sessions with an unspecified number of people are required / permitted, a public / unsecured advertising method is needed so that any device can analyze advertising packets such as advertising poles.

[0496] Example 1-1

[0497] To support the various advertising messages described above, such as secured / private or unsecured / public, security level-based advertising packets may be configured, and scanner operations based on these packets may be defined.

[0498] The security level may be defined as follows:

[0499] Level 1: No security

[0500] Level 2: Applications involving association with a single device (peer-to-peer)

[0501] Level 3: Applications of coupling with device groups

[0502] Level 1 may apply when advertising ADV_POLL to an unspecified number of people. In use cases such as access control in public places and payment for public transportation fares, ADV_POLL is required to be easily transmitted and analyzed to an unspecified number of people to effectively assist in setting up a ranging session, rather than supporting privacy. In this case, ADV_POLL does not need to be encrypted, and any scanner / responder can obtain the ADV_POLL and set up a ranging session through a two-way handshake operation.

[0503] Level 2 may apply when ADV_POLL is encrypted and advertised so that it is retrieved by only one device. For example, use cases such as smartphone family accessory device discovery using ranging session setup between a personal smartphone and a smartphone family accessory device verified in a manner such as pre-authentication may be considered. In this case, privacy must be sufficiently guaranteed, so a method is required in which advertising is performed in a secure manner and ranging session setup is performed based on this. In this case, the address included in ADV_POLL (i.e., the advertiser's address) may be in the form of a private MAC address. In addition, ADV_POLL (or a portion of ADV_POLL) may be encrypted in a specific manner, and key provisioning or key exchange algorithms such as PKI (public key infrastructure) may be used to help only the promised advertiser and scanner send and receive ADV_POLL while guaranteeing privacy.

[0504] Level 3 may apply when ADV_POLL is encrypted and advertised so that it is obtained only by devices in a specific group. Use cases may include measuring the location and distance of surrounding devices based on distance measurements of multiple devices, and constructing a device map, using ranging session setup between a personal smartphone and multiple smartphone family accessory devices verified in a manner such as pre-authentication, or between a smartphone and home appliance devices verified in a manner such as pre-authentication. In this case, privacy must be sufficiently guaranteed, so the address included in ADV_POLL (i.e., the advertiser's address) may be configured in the form of a private MAC address so that advertising is performed in a secure manner and ranging session setup is performed based on this. In addition, ADV_POLL (or a part of ADV_POLL) may be encrypted in a specific manner, and key provisioning or key exchange algorithms such as PKI (public key infrastructure) may be used to help only the promised advertiser and scanner send and receive ADV_POLL while guaranteeing privacy.

[0505] Examples 1-2

[0506] To support the various advertising messages mentioned above, such as secured / private or unsecured / public, security mode-based advertising packets may be configured and scanner operations defined accordingly.

[0507] The security mode may be defined as follows:

[0508] Mode 0: No security

[0509] Mode 1: For association with a single device (peer-to-peer) or a group of devices.

[0510] Mode 0 may correspond to cases where ADV_POLL is advertised to an unspecified number of people, similar to Level 1 in Example 1-1. In use cases such as access control in public places and payment of fares for public transportation, ADV_POLL is required to be easily transmitted and interpreted by an unspecified number of people and to effectively assist in ranging session setup, rather than supporting privacy. In this case, ADV_POLL does not need to be encrypted (unencrypted), and any scanner / responder can obtain the ADV_POLL and perform ranging session setup through a two-way handshake operation.

[0511] Mode 1 may correspond to cases where ADV_POLL is encrypted and advertised in such a way as Level 2 and / or Level 3 of Example 1-1, so that it is acquired by only one device / device group. For example, use cases may be considered where a device map is constructed by measuring the location and distance of surrounding devices based on distance measurements of (multiple) devices, using ranging session setup between a personal smartphone and a smartphone family accessory device verified in a manner such as pre-authentication, or between a smartphone and a home appliance device verified in a manner such as pre-authentication. In this case, privacy must be sufficiently guaranteed, so the address included in ADV_POLL (i.e., the advertiser's address) may be configured in a form such as a private MAC address so that advertising is performed in a secure manner and ranging session setup is performed based on this. In addition, ADV_POLL (or a portion of ADV_POLL) may be encrypted in a specific way, and key provisioning or key exchange algorithms such as PKI (public key infrastructure) may be used to help only the promised advertiser and scanner send and receive ADV_POLL while guaranteeing privacy.

[0512] The following describes examples of advertising packet formats related to this disclosure with reference to Figure 32.

[0513] Examples 1-3

[0514] Figure 32(a) shows an example of a security level-based advertising packet format.

[0515] The ID field may be set to a value indicating that the frame is ADV-POLL. That is, a single advertising pole frame format may be defined, and the frame ID may be set to a single value corresponding to the advertising pole frame.

[0516] The protocol version field may be set to a value indicating the version of the UWB technical standard in which the frame is defined.

[0517] The security level field is defined as being 2 bits in size and set to one of four values ​​(e.g., 1, 2, 3, and 4, or 00, 01, 10, and 11), where the first value (e.g., 0) corresponds to no security (i.e., level 1 as described above), the second value (e.g., 1) corresponds to use with a single device (i.e., level 2 as described above), and the third value (e.g., 2) corresponds to use with a group of devices (i.e., level 3 as described above). The fourth value of the security level field (e.g., 3) may be reserved.

[0518] The security level may be included in the advertising packet, as illustrated in Figure 32(a), or it may not be included in the advertising packet and can be specified at a higher layer by the advertiser and scanner, respectively. When the security level is specified at a higher layer, the security level field in the advertising packet may be omitted.

[0519] The RDP (random delay present) field can be used to indicate that a random delay field does not exist if its value is 0, and to indicate that a random delay field exists if its value is 1.

[0520] The random delay field may relate to the response time between advertising packets, such as ADV-POLL, and advertising response packets, such as ADV-RESP, during the two-way handshake process. When the value of the random delay field is 0, the responder can send a response packet immediately after receiving the advertising packet. When the value of the random delay field is not 0, the responder can defer sending the response packet within a range based on that value, using methods such as random delay backoff. For example, in a public advertising scheme, random delay may be applied to avoid response packet collisions in a congested environment with many potential responders. The value of the random delay field may be determined by a higher layer. For example, the unit of the random delay field value may be RSTU (ranging scheduling time unit), and it may be set to a value optimized for the application requirements.

[0521] The secured data field may be omitted if the security level field is 0. If the security level field is 1 or 2, the secured data field may contain information for encryption or encrypted information. The encryption method may be selected depending on the applied algorithm. For example, if a method such as a private MAC address is applied to the secured data, the advertiser generates the MAC address using an IRK (identity resolving key) and a random number (e.g., prand), and the advertiser and a pre-approved scanner can determine the private MAC address using the pre-provided IRK and prand information. Alternatively, if the secured area within the advertising packet is encrypted, the advertiser and scanner may be provided with a key through a PKI system, allowing the scanner to decrypt the secured area. The application to the secured area may vary depending on the application and the encryption algorithm.

[0522] The Advertising Data (ADV Data) field may be included if the security level is 0, and may be omitted if the security level is 1 or 2. The ADV data may contain information that the advertiser announces (e.g., information about the services being supported).

[0523] Examples 1-4

[0524] Figure 32(b) shows an example of a security mode-based advertising packet format.

[0525] The security mode field is defined as being 1 bit in size and is set to one of two values ​​(e.g., 0 and 1, or 00 and 01), where the first value (e.g., 0) corresponds to no security (i.e., mode 0 as described above), and the second value (e.g., 1) corresponds to use in combination with one device / device group (i.e., mode 1 as described above).

[0526] The security mode may be included in the advertising packet, as illustrated in Figure 32(a), or it may not be included in the advertising packet and can be specified at a higher layer by the advertiser and scanner, respectively. When the security mode is specified at a higher layer, the security mode field in the advertising packet may be omitted.

[0527] Furthermore, the descriptions for the ID field, protocol version, RDP, and random delay field are the same as those for the fields in Figure 32(a). The descriptions for the secured data field and ADV data are the same as those for the fields in Figure 32(a), but with security level 1 replaced by security mode 0 and security level 2 or 3 replaced by security mode 1. Therefore, redundant descriptions are omitted.

[0528] Examples 1-5

[0529] Unlike the previously described embodiments 1-3 and 1-4, which assume a single format for advertising packets (e.g., advertising pole frames), this embodiment relates to a method for defining multiple advertising pole frame formats that correspond to different frame ID values ​​depending on the security level / security mode (i.e., whether the advertiser's private address or public address is used in advertising for discovery / session initialization).

[0530] In this embodiment, the distinguished frame ID values ​​are denoted as ADV-POLL, ADV-POLL2, ADV-POLL3, ..., but the actual value of the frame ID field may be any of the distinguished integer values ​​(e.g., 0, 1, 2, ..., 10, 11, 12, ...). That is, the scope of this disclosure is not limited by the frame ID values ​​themselves, but includes the definition and use of any distinguished first, second, third, ... frame ID values.

[0531] For example, for security levels 0, 1, and 2, ID values ​​such as ADV-POLL (i.e., the first value), ADV-POLL2 (i.e., the second value), and ADV-POLL3 (i.e., the third value) may be defined, respectively.

[0532] Alternatively, ID values ​​for ADV-POLL (i.e., the first value) and ADV-POLL2 (i.e., the second value) may be defined for security modes 0 and 1, respectively.

[0533] Figure 33 shows another example of an advertising packet format relating to this disclosure.

[0534] Figure 33(a) shows an example of an unsecured / public advertising packet format. Here, the value of the frame ID field may be set to a first value (for example, a value corresponding to ADV-POLL), and the security level field or security mode field and the secured data field may be omitted compared to the example in Figure 32.

[0535] Figure 33(b) shows an example of a secured / private advertising packet format. Here, the value of the frame ID field may be set to a secondary value (for example, a value corresponding to ADV-POLL2), and the security level field or security mode field and the ADV data field may be omitted compared to the example in Figure 32.

[0536] Figure 34 shows yet another example of an advertising packet format relating to this disclosure.

[0537] If the advertiser address (ADV-ADDR) field is not included in the header of the advertising packet, the ADV-ADDR may be included in the payload.

[0538] Figure 34(a) shows an example of an unsecured / public advertising packet format. Here, the value of the frame ID field may be set to a first value (for example, a value corresponding to ADV-POLL). Also, the advertiser address field may be generated and set to a value corresponding to a public address (or public MAC address).

[0539] Figure 33(b) shows an example of a secured / private advertising packet format. Here, the value of the frame ID field may be set to a secondary value (for example, a value corresponding to ADV-POLL2). Also, the advertiser address field may be generated and set to a value corresponding to a private address (or private MAC address).

[0540] Example 2

[0541] This embodiment describes examples of discovery / initialization and setup operations based on secured / private advertising packets or unsecured / public advertising packets as defined in Example 1.

[0542] Figure 35 shows an example of peripheral device discovery based on secure advertising as described in this disclosure.

[0543] When broadcasting advertising packets to find a personal device and peripheral devices owned by an individual, or when searching for one's friends, it may be necessary to protect personal information, and therefore, secure advertising may be applied. In this case, if an unspecified number of people can receive and analyze the advertising packets, personal device fingerprint information such as MAC addresses and session configuration information may be exposed, and secure advertising may be applied to prevent this.

[0544] The example in Figure 35 illustrates an example of a procedure for finding a smartphone and surrounding devices or nearby friends using secure advertising.

[0545] Referring to Figure 35, a user device (e.g., a smartphone), known private device 1 (e.g., an earbird), and known private device 2 (e.g., a laptop) are shown.

[0546] Smartphones can broadcast secure advertising packets over NB / UWB discovery channels.

[0547] The Earbird can scan NB / UWB discovery channels, receive advertising packets, and analyze them using IRK and prand to establish a ranging session. This may allow the ranging (e.g., distance) and direction between the smartphone and the Earbird to be measured.

[0548] The laptop can scan NB / UWB discovery channels, receive advertising packets, and analyze them using IRK and prand to establish a ranging session. This may allow the ranging (e.g., distance) and direction between the smartphone and the laptop to be measured.

[0549] In other words, as mentioned above, known private devices such as laptops and earbirds scan the NB / UWB discovery channel, but they can find secured advertising packets and analyze the private MAC addresses using information such as IRK and prand.

[0550] This allows a known peripheral device, after discovering an advertising packet, to perform a ranging session setup according to a two-way handshake procedure, measure ranging and AOA (angle of arrival), etc., to determine distance and direction, thereby informing the user of the location of the smartphone and the peripheral device.

[0551] An unknown user device attempts to scan on the NB / UWB channel, but is unable to find a valid address from the advertising packets, and therefore cannot establish a ranging session with the smartphone.

[0552] In the example shown in Figure 35, the advertising packet broadcast by the smartphone may include the following information:

[0553] [Table 18]

[0554] Figure 36 shows an example of access control for multiple devices based on unsecured advertising as described in this disclosure.

[0555] The example in Figure 36 illustrates a procedure for controlling access to a public place (e.g., a hospital, a bus fare payment location, etc.) using unsecured advertising.

[0556] Devices installed in public places (for example, a main control device installed in a hospital) can broadcast unsecured advertising packets containing public MAC addresses over NB / UWB discovery channels.

[0557] Among a large number of unknown user devices, if one user (e.g., Mr. Lee) enters the hospital carrying a smartphone, that customer's smartphone can scan the NB / UWB discovery channel. The customer's smartphone can discover unsecured advertising packets on the NB / UWB discovery channel and establish a ranging session with the hospital's main control device.

[0558] This allows the hospital's main control device to access further information about the customer who owns the smartphone, based on the ranging and AOA measurement results between the hospital's main control device and the customer's smartphone, and thereby determine that the customer (i.e., Mr. Lee) has entered the hospital.

[0559] Therefore, the advertising packets broadcast by the main control device may include the following information:

[0560] [Table 19]

[0561] Figure 37 shows an example of a purchasing process using any device based on unsecured advertising as described herein. The example in Figure 37 is an example of a procedure for mobile payments (e.g., payment for goods in a store) for an unspecified number of customers using unsecured advertising.

[0562] POS (point of sale) devices installed in stores can broadcast unsecured advertising packets over NB / UWB discovery channels.

[0563] One of the unspecified customers may activate a payment app on their smartphone. Using this app, the smartphone may scan for advertising packets, and a ranging session may be set up between the POS device and the smartphone. The ranging is then measured, and if the distance is less than 1 meter, the payment may be processed. That is, when the distance between the customer's device and the POS device becomes less than 1 meter, the payment information for the items recognized by the POS device may be transmitted to the payment app on the customer's smartphone. The customer then confirms the payment information, and once they make a final confirmation of the payment, the payment may proceed.

[0564] Therefore, advertising packets broadcast by a POS device may include the following information:

[0565] [Table 20]

[0566] Tables 18 to 20 illustrate cases where the frame ID of an advertising pole frame is set to ADV-POLL and the security mode field indicates that it is a private or public advertising packet. However, as in Example 1-5, the frame ID field in Table 18 may be set to ADV-POLL (i.e., a value indicating that it is a private advertising packet), and the frame ID fields in Tables 19 and 20 may be set to ADV-POLL2 (i.e., a value indicating that it is a public advertising packet). In the various examples of this disclosure described above, secured / private or unsecured / public advertising schemes associated with security levels / modes may be defined and applied in the native discovery / initialization and setup procedures for NBA-MMS-UWB. In other words, according to this disclosure, privacy-ensuring advertising or public advertising can be appropriately applied to the situation in relation to the advertising process for the advertiser to make itself known for discovery / initialization, the scanning process for the scanner to find the advertiser, and the procedure for establishing a ranging session setup after discovery, so that efficient discovery / initialization and setup can be supported by in-band UWB alone.

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

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

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

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

[0571] [Claims when filing an international application] [Claim 1] A method performed by a first device in an ultra-wideband (UWB) wireless network system, The steps include: generating an advertising pole frame that includes a frame identifier field; The process includes the step of transmitting the advertising pole frame to one or more second devices; A method in which, based on the fact that multiple advertising pole frames are defined in relation to whether or not a public address is used for session initialization, the frame identifier field is set to a different value for each of the multiple advertising pole frames. [Claim 2] The method according to claim 1, wherein the frame identifier field is set to a first value for a public advertising pole frame. [Claim 3] The method according to claim 1, wherein the frame identifier field is set to a second value for advertising pole frames other than public advertising pole frames. [Claim 4] The method according to claim 1, wherein the public advertising pole frame includes a public address generated by the first device. [Claim 5] The method according to claim 1, wherein advertising pole frames other than public advertising pole frames include private addresses generated by the first device. [Claim 6] The method according to claim 1, wherein the frame identifier field is set to a single value based on the definition of a single frame format for the advertising pole frame. [Claim 7] The method according to claim 6, wherein the single frame format includes security-related information. [Claim 8] The aforementioned security-related information includes information regarding the security level, The information regarding the aforementioned security level is, First level for unencrypted advertising poles, A second level of encryption for encrypted advertising poles associated with peer devices that hold the encryption key, or The method according to claim 7, which indicates one of a third level for an encrypted advertising pole associated with a group of devices holding an encryption key. [Claim 9] The aforementioned security-related information includes information regarding the security mode, The information regarding the aforementioned safety mode is, The first mode for unencrypted advertising poles, or The method according to claim 7, which indicates one of a second mode for an encrypted advertising pole. [Claim 10] The first device is the initiator or controller, The method according to claim 1, wherein the second device is a responder or a controlled device. [Claim 11] The method according to claim 1, wherein the ADV-POLL message is transmitted over an NB (narrowband) channel or a UWB channel. [Claim 12] A first device in an ultra-wideband (UWB) wireless network system, One or more transceivers; The system comprises one or more processors connected to the one or more transceivers; The one or more processors described above are: Generate an advertising pole frame that includes a frame identifier field, and The system is configured to transmit the advertising pole frame to one or more second devices via one or more transceivers. A device in which, based on the fact that multiple advertising pole frames are defined in relation to whether or not a public address is used for session initialization, the frame identifier field is set to a different value for each of the multiple advertising pole frames. [Claim 13] A method performed by a second device in an ultra-wideband (UWB) wireless network system, The steps include receiving an advertising pole frame containing a frame identifier field from a first device; The process includes: a step of performing a session initialization process based on the information contained in the advertising pole frame; A method in which, based on the fact that multiple advertising pole frames are defined in relation to whether or not a public address is used for the session initialization, the frame identifier field is set to a different value for each of the multiple advertising pole frames. [Claim 14] A second device in an ultra-wideband (UWB) wireless network system, One or more transceivers; The system comprises one or more processors connected to the one or more transceivers; The one or more processors described above are: An advertising pole frame containing a frame identifier field is received from the first device via one or more transceivers, and The system is configured to perform a session initialization process based on the information contained in the advertising pole frame. A device in which, based on the fact that multiple advertising pole frames are defined in relation to whether or not a public address is used for the session initialization, the frame identifier field is set to a different value for each of the multiple advertising pole frames. [Claim 15] A processing device configured to control devices in an ultra-wideband (UWB) wireless network system, One or more processors; A processing device comprising: one or more computer memories operably connected to the one or more processors and storing instructions for performing the method according to any one of claims 1 to 11, based on that they are executed by the one or more processors; [Claim 16] One or more non-transitory computer-readable media for storing one or more instructions, The one or more instructions are executed by one or more processors and control the device to perform the method according to any one of claims 1 to 11 in an ultra-wideband (UWB) wireless network system, in a computer-readable medium.

Claims

1. A method performed by a first device in an ultra-wideband (UWB) wireless network system, The steps include: generating an advertising pole frame that includes a frame identifier field; The process includes the step of transmitting the advertising pole frame to one or more second devices; A method in which, based on the fact that multiple advertising pole frames are defined in relation to whether or not a public address is used for session initialization, the frame identifier field is set to a different value for each of the multiple advertising pole frames.

2. The method according to claim 1, wherein the frame identifier field is set to a first value for a public advertising pole frame.

3. The method according to claim 1, wherein the frame identifier field is set to a second value for advertising pole frames other than public advertising pole frames.

4. The method according to claim 1, wherein the public advertising pole frame includes a public address generated by the first device.

5. The method according to claim 1, wherein advertising pole frames other than public advertising pole frames include private addresses generated by the first device.

6. The method according to claim 1, wherein the frame identifier field is set to a single value based on the definition of a single frame format for the advertising pole frame.

7. The method according to claim 6, wherein the single frame format includes security-related information.

8. The aforementioned security-related information includes information regarding the security level, The information regarding the aforementioned security level is, First level for unencrypted advertising poles, A second level of encryption for encrypted advertising poles associated with peer devices that hold the encryption key, or The method according to claim 7, which indicates one of a third level for an encrypted advertising pole associated with a group of devices holding an encryption key.

9. The aforementioned security-related information includes information regarding the security mode, The information regarding the aforementioned safety mode is, The first mode for unencrypted advertising poles, or The method according to claim 7, which specifies one of a second mode for an encrypted advertising pole.

10. The first device is the initiator or controller, The method according to claim 1, wherein the second device is a responder or a controlled device.

11. The method according to claim 1, wherein the ADV-POLL message is transmitted over an NB (narrowband) channel or a UWB channel.

12. 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 transceivers; The one or more processors described above are: Generate an advertising pole frame that includes a frame identifier field, and The system is configured to transmit the advertising pole frame to one or more second devices via one or more transceivers. A device in which, based on the fact that multiple advertising pole frames are defined in relation to whether or not a public address is used for session initialization, the frame identifier field is set to a different value for each of the multiple advertising pole frames.

13. A method performed by a second device in an ultra-wideband (UWB) wireless network system, The steps include: receiving an advertising pole frame containing a frame identifier field from a first device; The process includes: a step of performing a session initialization process based on the information contained in the advertising pole frame; A method in which, based on the fact that multiple advertising pole frames are defined in relation to whether or not a public address is used for the session initialization, the frame identifier field is set to a different value for each of the multiple advertising pole frames.

14. 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 transceivers; The one or more processors described above are: An advertising pole frame containing a frame identifier field is received from the first device via one or more transceivers, and The system is configured to perform a session initialization process based on the information contained in the advertising pole frame. A device in which, based on the fact that multiple advertising pole frames are defined in relation to whether or not a public address is used for the session initialization, the frame identifier field is set to a different value for each of the multiple advertising pole frames.

15. A processing device configured to control devices in an ultra-wideband (UWB) wireless network system, One or more processors; A processing device comprising: one or more computer memories operably connected to the one or more processors and storing instructions for performing the method according to any one of claims 1 to 11, based on that they are executed by the one or more processors;

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

Images