Narrow-range channel synchronization in wireless communications

Description

1 / 20 Narrow-range band channel synchronization in wireless communications Cross-reference to a related patent application.

[0001] This disclosure is part of a non-provisional patent application claiming the priority benefit of U.S. Provisional Patent Application No. 63 / 598,164, filed November 13, 2023, the contents of which are incorporated herein by reference in their entirety. TECHNICAL FIELD

[0002] This disclosure relates generally to wireless communications and, more particularly, to narrowband (NB) channel synchronization in wireless communications. BACKGROUND

[0003] Unless otherwise indicated herein, the approaches described in this section are not prior art of the claims listed below and are not admitted as prior art by their inclusion in this section.

[0004] In wireless communications, such as ultra-wideband (UWB), according to the Institute of Electrical and Electronics Engineers (IEEE) 802.15.4ab specifications, an initiator is permitted to continue advertisement polling (ADV-POLL) after initiating a range control phase with a device. The initiator may initiate a one-to-many range session with multiple responders participating in the same round. After the initiator confirms receipt of a RESPONSE message from a responder during the control phase, and unless initialization of other devices is required, the initiator must interrupt range initialization and cease transmission of ADV-POLL messages. According to the current IEEE specification, a range initiation (SOR) does not have an explicit channel assignment of an NB range channel to which the initiator / responder must initially switch. Instead, it relies on the channel seed of Petition 870250096331, dated 10 / 22 / 2025, page 9 / 35 2 / 20 NB and block index 0 to derive the NB channel. Furthermore, according to the current specification, it is assumed that the first range block of any responder has a range block index set to zero (RangingBlockIndex = 0) and that message protection is performed only on REPORT messages.

[0005] Currently, for multi-millisecond (MMS) one-to-many (O2M) reaching, responders can join the reaching session at different times / blocks. The current assumption is that, after the session starts, the reaching block index starts from zero. This, however, tends to create certain problems. First, for RangingBlockIndex-based NB reaching control channel switching / hopping, responders joining in different reaching blocks may hop to different channels in the same round because their block index starts at different times. Second, for time-efficient ultra-wideband (UWB) reaching with Reach Integrity Fragments (RIFs) / Physical Layer Security (PHY), for initiator RIFs to the responder(s) to be received by multiple responders, their V value used to generate the initiator's common scrambled timestamp sequence (STS) must be synchronized.However, if different reach sessions start in different blocks, the V value will begin to increase at different times, resulting in different values ​​in the same block / round for different respondents.

[0006] Furthermore, for current one-to-one (O2O) narrowband assisted MMS reach, if the O2O Reply message is not received by the initiator, the initiator, having sent an O2O Search message but not having received an O2O Reply message, does not know whether the O2O Reply message was not sent (e.g., reach start message (SOR) in the initialization phase or the DE message). Petition 870250096331, dated 10 / 22 / 2025, page 10 / 35 3 / 20 The O2O polling during the reach phase is not received by the responder, or the O2O Response message is sent but not received by the initiator. If the responder has received the O2O polling and sent the O2O Response message, it can proceed to generate RIFS from the value V based on block index 0 and the RIFS slot index. However, the initiator would determine this as a reach initialization failure, since the O2O Response message was not received. To retry the initialization without another UWB session key exchange, the block index / slot index would be reset to 0 based on the current requirement. This would result in the same RIF generated by the responder in the last failed attempt, thus compromising reach security. To avoid the problem, the upper layer would be invoked for another UWB session key exchange.The medium access control (MAC) protocol itself should handle this over-the-air error scenario instead of relying on a higher layer to resynchronize / regenerate a completely new key.

[0007] In view of the problems described above, there is a need for a range-bound NB channel synchronization solution in wireless communications. SUMMARY

[0008] The following summary is for illustrative purposes only and is not intended to be limiting in any way. That is, the following summary is provided to introduce concepts, highlights, benefits, and advantages of the novel and non-obvious techniques described herein. Selected implementations are described in more detail below. Therefore, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.

[0009] One objective of this publication is to provide schemes, concepts, designs, techniques, methods and apparatus. Petition 870250096331, dated 10 / 22 / 2025, page 11 / 35 4 / 20 pertaining to NB range channel synchronization in wireless communications. It is believed that several schemes proposed here can address or alleviate these problems mentioned above.

[0010] In one aspect, a method may involve an initiator initiating or otherwise conducting a reach session by: (1) transmitting a reach start message (ROS) and a poll message; and (2) receiving a response message from each of one or more responders. The ROS message may provide: (a) explicit NB reach channel information; or (b) a reach block index (RangingBlockIndex) to which a time offset field in the ROS message points.

[0011] In another aspect, a method may involve a responder participating in a reach session by: (1) receiving a reach initiation message (RIN) and a Survey message from an initiator; and (2) transmitting a Response message responsive to the Survey message received. The RIN message may provide: (a) explicit NB reach channel information; or (b) a RangingBlockIndex to which a time offset field in the RIN message points.

[0012] It is important to emphasize that, although the description provided here may be in the context of certain radio access technologies, networks, and network topologies, such as Wi-Fi, the concepts, schemes, and any proposed variations / derivatives can be implemented in, for, and by other types of radio access technologies, networks, and network topologies, such as, for example and without limitation, Bluetooth, ZigBee, 5th Generation (5G) / New Radio (NR), Long Term Evolution (LTE), LTE Advanced, LTE-Advanced Pro, Internet of Things (IoT), Industrial IoT (IoT), and Narrowband IoT (NB-IoT). Thus, the scope of this disclosure is not limited to the examples described herein. Petition 870250096331, dated 10 / 22 / 2025, page 12 / 35 5 / 20 BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The accompanying drawings are included to provide a better understanding of the disclosure and are incorporated into and form a part of this disclosure. The drawings illustrate implementations of the disclosure and, together with the description, serve to explain the principles of the disclosure. It is important to note that the drawings are not necessarily to scale, as some components may appear disproportionate to size in the actual implementation, in order to clearly illustrate the concept of the present disclosure.

[0014] FIG. 1 is a diagram of an example network environment in which various schemes according to the present disclosure can be implemented.

[0015] FIG. 2 is a diagram of an example scenario in which various schemes proposed according to the present disclosure can be implemented.

[0016] FIG. 3 is a diagram of an example scenario in which various schemes proposed according to this disclosure can be implemented.

[0017] FIG. 4 is a diagram of an example scenario in which various schemes proposed according to this disclosure can be implemented.

[0018] FIG. 5 is a block diagram of an example communication system according to various implementations of the present disclosure.

[0019] FIG. 6 is a flowchart of an example process according to various implementations of the present disclosure.

[0020] FIG. 7 is a flowchart of an example process according to various implementations of the present disclosure. DETAILED DESCRIPTION

[0021] Detailed modalities and implementations of the claimed matters are disclosed here. However, it should be understood that the modalities and implementations disclosed are Petition 870250096331, dated 10 / 22 / 2025, p. 13 / 35 6 / 20 are merely illustrative of the claimed materials, which may be incorporated in various forms. This disclosure may, however, be incorporated in many different forms and should not be interpreted as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided so that the description of this disclosure is complete and thorough and fully conveys the scope of this disclosure to those skilled in the art. In the description below, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the embodiments and implementations presented. Overview

[0022] Implementations according to this disclosure refer to various techniques, methods, schemes and / or solutions pertaining to NB-range channel synchronization in wireless communications. According to this disclosure, various possible solutions can be implemented separately or in combination. That is, although these possible solutions may be described separately below, two or more of these possible solutions may be implemented in one combination or another.

[0023] FIG. 1 illustrates an example of a 100 network environment in which various solutions and schemes according to this disclosure can be implemented. FIGS. 1 - 7 illustrate examples of implementation of various proposed schemes in the 100 network environment according to this disclosure. The following description of various proposed schemes is provided with reference to FIGS. 1 - 7.

[0024] Referring to part (A) of FIG. 1, network environment 100 may include at least one first STA (STA 110) and one second STA (STA 120). Both STA 110 and STA 120 may be an initiator / controller STA (hereinafter referred to alternately as Initiator), and both STA 110 and STA Petition 870250096331, dated 10 / 22 / 2025, p. 14 / 35 7 / 20 120 can be one of the responder / controller STAs (hereinafter referred to alternately as Responder). Although there may be additional STAs involved in the 100 network environment under one or more of the schemes proposed herein, for simplicity, only two STAs (STA 110 and STA 120) are shown in FIG. 1 with the understanding that additional STAs may be involved (e.g., additional non-AP STAs participating in reach sessions under the proposed schemes). Each of STA 110 and STA 120 can be configured to implement various schemes proposed in accordance with this disclosure, as described below. For example, one of STA 110 and STA 120 can function as an initiator and the other of STA 110 and STA 120 can function as a responder in an NB reach session under the proposed schemes.It is worth noting that, although the various proposed schemes can be described individually or separately below, in real-world implementations, some or all of the proposed schemes may be used or implemented together. Of course, each of the proposed schemes can be used or implemented individually or separately.

[0025] Part (B) of FIG. 1 shows an example of the message content fields of a range start message (SOR). Referring to part (B) of FIG. 1, an SOR message may include a time offset field, an NB channel seed field, an NB channel selection field, a UWB PHY configuration field, a UWB MAC configuration field, an NB PHY configuration field, and an NB MAC configuration field.

[0026] FIG. 2 illustrates an example scenario 200 in which several proposed schemes according to the present disclosure can be implemented. Scenario 200 can belong to a one-to-many reach session initialization with responders participating in the same round. FIG. 3 illustrates an example scenario 300 in which several proposed schemes of Petition 870250096331, dated 10 / 22 / 2025, page 15 / 35 8 / 20 according to this disclosure can be implemented. Scenario 300 may belong to a standard one-to-many reach scenario. FIG. 4 illustrates an example scenario 400 in which several schemes proposed according to this disclosure can be implemented. Scenario 400 may belong to a time-efficient one-to-many reach scenario.

[0027] In a proposed scheme according to the present disclosure, a SOR message, whether for a one-to-many reach session or a one-to-one reach session, may provide the NB reach channel explicitly or a RangingBlockIndex to which the Time Offset field points. Explicit NB reach channel information and / or RangingBlockIndex may facilitate a responder finding the responder's first block hop NB reach channel after initialization, and the hop NB reach channel may be common to other responders currently in their second or third block in an ongoing one-to-many reach session. Furthermore, RangingBlockIndex information in the SOR may facilitate multiple responders synchronizing their V value used to generate the common RIFs transmitted by the initiator, if RIFs are enabled.Responders joining in different blocks can use different RangingBlockIndex information in their respective SOR messages to initialize their V value with the same value in the same range block. Additionally, RangingBlockIndex information in the SOR for one-to-one range can facilitate synchronization of the initiator and responder's V value if there is a previous initialization failure causing the reuse of the same V value. For example, in the previous initialization attempt, an O2O Response message might not be received by the initiator, even though the Response message, range sequence fragments (RSFs) / RIFs, may have been transmitted by the responder. After a restart without a key exchange... Petition 870250096331, dated 10 / 22 / 2025, page 16 / 35 In the 9 / 20 UWB session, the same V value is reused by the responder to generate the RIF again.

[0028] In another proposed scheme according to this disclosure, if the SOR message explicitly provides the NB range channel for the block to which the Time Offset field points, the responder can verify that the initial NB channel is the same as the selected channel generated based on the channel seed and RangingBlockIndex provided by the initial Survey message. This can be equivalent to the SOR message providing the RangingBlockIndex of the responder's first block (pointed to by the Time Offset field). The responder can initialize the V value for the RIFs based on the RangingBlockIndex provided by the Survey message. Advantageously, this can help responders joining in different blocks synchronize with the same counter value for common RIFs sent by the initiator in a one-to-many range with time efficiency.Additionally, this can help the responder and initiator in a one-to-one range to start from an unused V value if there is a previous initialization failure causing their counters to malfunction. Throughout the rest of the document, we refer to the V value as the STS counter. Illustrative implementations

[0029] FIG. 5 illustrates an example system 500 having at least one example device 510 and one example device 520 according to an implementation of the present disclosure. Each of the devices 510 and 520 can perform various functions to implement schemes, techniques, processes, and methods described herein relating to range-bound channel synchronization in wireless communications, including the various schemes described above with respect to various proposed designs, concepts, schemes, systems, and methods described above, as well as processes described below. For example, device 510 can be implemented in STA 110 and device 520 can be implemented Petition 870250096331, dated 10 / 22 / 2025, p. 17 / 35 10 / 20 on STA 120, or vice versa.

[0030] Each of the 510 and 520 devices can be part of an electronic device, such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. When implemented in a STA, each of the 510 and 520 devices can be implemented in a smartphone, a smartwatch, a personal digital assistant, a digital camera, or a computing device such as a tablet, laptop, or notebook. Each of the 510 and 520 devices can also be part of a machine-type device, which can be an IoT device, such as a stationary or fixed device, a household appliance, a wired communication device, or a computing device. For example, each of the 510 and 520 devices can be implemented in a smart thermostat, a smart refrigerator, a smart lock, a wireless speaker, or a home control center.When deployed in or as a network appliance, the 510 appliance and / or the 520 appliance can be deployed in a network node, such as an AP in a WLAN.

[0031] In some implementations, each of the 510 and 520 devices may be implemented in the form of one or more integrated circuit (IC) chips, such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, one or more reduced instruction set computing (RISC) processors, or one or more complex instruction set computing (CISC) processors. In the various schemes described above, each of the 510 and 520 devices may be implemented in or as a controller / initiator or a controlled / responder. Each of the 510 and 520 devices may include at least some of the components shown in FIG. 5, such as a 512 processor and a 522 processor, respectively, for example. Each of the 510 and 520 devices may additionally include one or more other Petition 870250096331, dated 10 / 22 / 2025, page 18 / 35 11 / 20 components not relevant to the proposed scheme of this disclosure (for example, internal power supply, display device and / or user interface device) and, therefore, such components of devices 510 and 520 are not shown in FIG. 5 nor described below in the interest of simplicity and brevity.

[0032] In one aspect, each of the 512 and 522 processors can be implemented in the form of one or more single-core processors, one or more multi-core processors, one or more RISC processors, or one or more CISC processors. That is, although a singular term “a processor” is used herein to refer to the 512 and 522 processors, each of the 512 and 522 processors may include multiple processors in some implementations and a single processor in other implementations according to the present disclosure.In another aspect, each of the 512 and 522 processors can be implemented in hardware (and optionally firmware) form with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and / or one or more varactors that are configured and arranged to achieve specific purposes in accordance with this disclosure. In other words, in at least some implementations, each of the 512 and 522 processors is a special-purpose machine specifically designed, organized and configured to perform specific tasks, including those pertaining to NB-range channel synchronization in wireless communications, according to various implementations of this disclosure.

[0033] In some implementations, the 510 device may also include a 516 transceiver coupled to the 512 processor. The 516 transceiver may include a transmitter capable of wireless transmission and a receiver capable of receiving data wirelessly. Petition 870250096331, dated 10 / 22 / 2025, page 19 / 35 12 / 20 wireless. In some implementations, the 520 device may also include a 526 transceiver coupled to the 522 processor. The 526 transceiver may include a transmitter capable of wirelessly transmitting and a receiver capable of wirelessly receiving data. It is worth noting that, although the 516 transceiver and the 526 transceiver are illustrated as being external and separate from the 512 and 522 processors, respectively, in some implementations, the 516 transceiver may be an integral part of the 512 processor as a system-on-a-chip (SoC) and / or the 526 transceiver may be an integral part of the 522 processor as a SoC.

[0034] In some implementations, the 510 device may additionally include a 514 memory coupled to the 512 processor and capable of being accessed by the 512 processor and storing data therein. In some implementations, the 520 device may additionally include a 524 memory coupled to the 522 processor and capable of being accessed by the 522 processor and storing data therein. Each of the 514 and 524 memories may include a type of random access memory (RAM), such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM), and / or zero-capacitor RAM (Z-RAM). Alternatively, or additionally, each of the 514 and 524 memories may include a type of read-only memory (ROM), such as mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), and / or electrically erasable programmable ROM (EEPROM).Alternatively, or additionally, each of the 514 and 524 memories may include a type of non-volatile random access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.

[0035] Each of the 510 and 520 devices can be a communication entity capable of communicating using various proposed schemes according to this disclosure. For illustrative purposes only and without limitation, a description of the capabilities Petition 870250096331, dated 10 / 22 / 2025, p. 20 / 35 The 13 / 20 configuration of device 510 or device 520, such as STA 110 and STA 120 respectively, is provided below in the context of example processes 600 and 700. It is worth noting that while a detailed description of the capabilities, functionalities, and / or technical characteristics of either device 510 or 520 is provided below, the same can be applied to the other device 510 and 520, although a detailed description of them is not provided for the sake of brevity. It is also important to emphasize that while the example implementations described below are provided in the context of WLAN, they can be implemented in other types of networks. Illustrative Processes

[0036] FIG. 6 illustrates an example process 600 according to an implementation of the present disclosure. Process 600 may represent an aspect of the implementation of several proposed designs, concepts, schemes, systems, and methods described above. More specifically, process 600 may represent an aspect of the proposed concepts and schemes relating to range-bound NB channel synchronization in wireless communications. Process 600 may include one or more operations, actions, or functions, as illustrated by one or more blocks / sub-blocks. Although illustrated as discrete blocks, several blocks of process 600 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Furthermore, the blocks / sub-blocks of process 600 may be executed in the order shown in FIG. 6 or, alternatively, in a different order. Additionally, one or more blocks / sub-blocks of process 600 may be executed repeatedly or iteratively.Process 600 can be implemented by or on device 510 and device 520, as well as any variations thereof. For illustrative purposes only and without limiting the scope, process 600 is described below in the context of device 510 and implemented on or as one. Petition 870250096331, dated 10 / 22 / 2025, page 21 / 35 14 / 20 range controller / responder (e.g., a wireless communication device) and device 520 implemented in or as an initiator / range controller of a wireless network in network environment 100, or vice versa, in accordance with one or more IEEE 802.15.4 standards. Process 600 may start in block 610.

[0037] In 610, process 600 may include processor 512 of device 510 initiating, via transceiver 516, a range session performing operations represented by 612 and 614.

[0038] On 612, process 600 may involve processor 512 transmitting, via transceiver 516, a SOR message and a Poll message. The SOR message may provide: (a) explicit NB range channel information; or (b) a RangingBlockIndex to which a time offset field in the SOR message points. Process 600 may proceed from 612 to 614.

[0039] In 614, process 600 may involve processor 512 receiving, via transceiver 516, a Response message from each or more responders.

[0040] In some implementations, each of the explicit NB reach channel information and reach block index can facilitate each of the one or more responders to find a hop NB reach channel from a first block of the respective responder after initialization.

[0041] In some implementations, the hop-on NB reach channel may be common to at least one other responder of the one or more responders currently in a subsequent block in an ongoing one-to-many reach session.

[0042] In some implementations, the RangingBlockIndex information in the SOR message can facilitate multiple responders from one or more responders synchronizing an STS counter of common RIFs transmitted by the initiator.

[0043] In some implementations, the information Petition 870250096331, dated 10 / 22 / 2025, page 22 / 35 15 / 20 RangingBlockIndex in the SOR message for one-to-one ranging can facilitate the synchronization of the initiator and an STS counter of one or more responders in an event where there is a previous initialization failure, causing the STS counters to be reused after the reboot.

[0044] In some implementations, explicit NB reach channel information may indicate an NB reach channel for a block to which the time offset field points, so that each responder of one or more responders is able to verify whether an initial NB channel is the same as a selected channel generated based on a channel seed and another reach block index provided by the Survey message.

[0045] Alternatively, or additionally, explicit NB reach channel information may indicate a reach block index for a block to which the time offset field points, so that each responder of one or more responders is able to initialize a respective STS counter for RIFs based on the reach block index.

[0046] FIG. 7 illustrates an example process 700 according to an implementation of the present disclosure. Process 700 may represent an aspect of the implementation of several proposed designs, concepts, schemes, systems, and methods described above. More specifically, process 700 may represent an aspect of the proposed concepts and schemes relating to range-bound NB channel synchronization in wireless communications. Process 700 may include one or more operations, actions, or functions, as illustrated by one or more blocks / sub-blocks. Although illustrated as discrete blocks, several blocks of process 700 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Furthermore, the blocks / sub-blocks of process 700 may be executed in the order shown in FIG. 7. Petition 870250096331, dated 10 / 22 / 2025, page 23 / 35 16 / 20 or, alternatively, in a different order. Furthermore, one or more blocks / sub-blocks of process 700 may be executed repeatedly or iteratively. Process 700 may be implemented by or on device 510 and device 520, as well as any variations thereof. For illustrative purposes only and without limiting the scope, process 700 is described below in the context of device 510 and implemented on or as a range controller / responder (e.g., a wireless communication device) and device 520 implemented on or as an initiator / range controller of a wireless network in the 100 network environment, or vice versa, in accordance with one or more IEEE 802.15.4 standards. Process 700 may start on block 710.

[0047] In 710, process 700 may include processor 522 of device 520 participating, via transceiver 526, in a range session performing operations represented by 712 and 714.

[0048] On 712, process 600 may involve processor 522 receiving, via transceiver 526, a SOR message and a Search message from an initiator. The SOR message may provide: (a) explicit NB range channel information; or (b) a RangingBlockIndex to which a time offset field in the SOR message points. Process 700 may proceed from 712 to 714.

[0049] In 714, process 700 may involve processor 522 transmitting, via transceiver 526, a Response message responsive to the received Search message.

[0050] In some implementations, each of the explicit NB reach channel information and reach block index can make it easier for the responder to find a hop NB reach channel from a responder's first block after initialization.

[0051] In some implementations, the hop-on NB reach channel may be common to at least one other responder. Petition 870250096331, dated 10 / 22 / 2025, page 24 / 35 17 / 20 currently in a subsequent block in an ongoing one-to-many outreach session.

[0052] In some implementations, the RangingBlockIndex information in the SOR message can facilitate multiple responders, including the 520 device, synchronizing an STS counter of common RIFs transmitted by the initiator.

[0053] In some implementations, the RangingBlockIndex information in the SOR message for one-to-one ranging can facilitate synchronization of the initiator and a responder STS counter in an event where there is a previous initialization failure, causing the STS counters to be reused after the restart.

[0054] In some implementations, in response to explicit NB reach channel information, indicating an NB reach channel for a block to which the time offset field points, process 700 may additionally involve processor 522 checking whether an initial NB channel is the same as a selected channel generated based on a channel seed and another reach block index provided by the Search message.

[0055] Alternatively, or additionally, in response to explicit NB reach channel information indicating a reach block index for a block to which the time offset field points, process 700 may additionally involve processor 522 initializing an STS counter for RIFs based on the reach block index. Additional notes

[0056] The material described here sometimes illustrates different components contained within or connected to other components. It is important to understand that such represented architectures are merely examples and that, in fact, many other architectures can be implemented to achieve the same functionality. In a conceptual sense, any arrangement of components for Petition 870250096331, dated 10 / 22 / 2025, page 25 / 35 18 / 20 Achieving the same functionality is effectively associated in such a way that the desired functionality is achieved. Therefore, any two components combined here to achieve a specific functionality can be seen as associated with each other, so that the desired functionality is achieved, regardless of the architectures or intermediate components. Similarly, any two components thus associated can also be seen as being operationally connected or operationally coupled to each other to achieve the desired functionality, and any two components capable of being thus associated can also be seen as being operationally coupleable to each other to achieve the desired functionality.Specific examples of operably coupled components include, but are not limited to, physically coupled and / or physically interactive components and / or wireless interactive components and / or logically interactive components.

[0057] Furthermore, with regard to the use of substantially any plural and / or singular terms herein, those skilled in the art may translate from plural to singular and / or from singular to plural, as appropriate to the context and / or application. The various singular / plural permutations may be expressly presented herein for the sake of clarity.

[0058] Furthermore, it will be understood by those skilled in the art that, in general, the terms used herein, and especially in the appended claims, for example, bodies of the appended claims, are generally conceived as open terms, for example, the term including should be interpreted as including, but not limited to, the term having should be interpreted as having at least, the term includes should be interpreted as includes, but not limited to, etc. It will further be understood by those skilled in the art that, if a Petition 870250096331, dated 10 / 22 / 2025, page 26 / 35 19 / 20 If a specific number of introductory claim recitations is intended, such intention will be explicitly stated in the claim, and in the absence of such recitation, such intention will not be present. For example, as an aid to understanding, the following attached claims may contain the use of the introductory phrases at least one and one or more to introduce recitations of claims.However, the use of such phrases should not be interpreted as implying that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any specific claim containing such introduced claim recitation to implementations containing only one of these recitations, even when the same claim includes the introductory phrases "a or more" or "at least one" and indefinite articles such as "a" or "an," for example, "a" and / or "an" should be interpreted as meaning "at least one" or "one or more"; the same applies to the use of definite articles used to introduce claim recitations.Furthermore, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted as meaning at least the number recited, for example, the mere recitation of two recitations, without other modifiers, means at least two recitations, or two or more recitations. Additionally, in cases where a convention analogous to “at least one of A, B, and C, etc.” is used, in general, such a construction is intended in the sense that a person skilled in the art would understand the convention, for example, “a system having at least one of A, B, and C” would include, but not be limited to, systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. In cases where a convention analogous to “at least one of A, B, or C, etc.” It is generally used, such a construction is intended in the sense that a person skilled in the art would understand the convention, for example. Petition 870250096331, dated 10 / 22 / 2025, p. 27 / 35 20 / 20 example, “a system having at least one of A, B or C would include, but not be limited to, systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together and / or A, B and C together, etc. It will be further understood by those skilled in the art that virtually any disjunctive word and / or phrase that presents two or more alternative terms, whether in the descriptive report, claims or drawings, should be understood as contemplating the possibilities of including one of the terms, any of the terms or both terms.

[0059] From the foregoing, it will be appreciated that various implementations of the present disclosure have been described herein for illustrative purposes, and that various modifications may be made without departing from the scope and spirit of the present disclosure. Consequently, the various implementations disclosed herein are not intended to be limiting, with the true scope and spirit being indicated by the following claims. Petition 870250096331, dated 10 / 22 / 2025, p. 28 / 35

Claims

1 / 5 CLAIMS 1. A method, characterized in that it comprises: initiating, by an initiator, a reach session by: transmitting a reach start message (RSM) and a search message; and receiving a Response message from each of one or more responders, wherein the RSM message provides: explicit narrowband reach channel information; or a reach block index (RangingBlockIndex) to which a time offset field in the RSM message points.

2. A method according to claim 1, characterized in that each of the explicit NB reach channel information and reach block index facilitates each of the one or more responders to find a hop NB reach channel from a first block of the respective responder after initialization.

3. Method, according to claim 2, characterized in that the hop-on NB reach channel is common to at least one other responder of the one or more responders currently in a subsequent block in an ongoing one-to-many reach session.

4. A method according to claim 1, characterized in that the RangingBlockIndex information in the SOR message facilitates multiple responders from one or more responders synchronizing a scrambled timestamp sequence counter (STS) of common range integrity fragments (RIFs) transmitted by the initiator.

5. Method, according to claim 1, characterized in that the RangingBlockIndex information in the SOR message for one-to-one ranging facilitates the synchronization of the initiator and a scrambled timestamp sequence counter (STS) of one or more responders in an event where there is a previous initialization failure, causing the STS counters to be reused after the restart.

6. Method, according to claim 1, characterized in that the explicit NB reach channel information indicates an NB reach channel for a block to which the time offset field points, such that each responder of one or more responders is able to verify whether an initial NB channel is the same as a selected channel generated based on a channel seed and another reach block index provided by the Survey message.

7. A method according to claim 1, characterized in that explicit NB reach channel information indicates a reach block index for a block to which the time offset field points, such that each responder of one or more responders is able to initialize a respective scrambled timestamp sequence counter (STS) for reach integrity fragments (RIFs) based on the reach block index.

8. Method, characterized in that it comprises: participation, by a responder, in a reach session by: receiving a reach initiation message (ROS) and a Survey message from an initiator; and transmitting a Response message responsive to the Survey message received, wherein the ROS message provides: explicit narrowband (NB) reach channel information; or a reach block index (RangingBlockIndex) to which a time offset field in the ROS message points.

9. Method, according to claim 8, characterized in that each of the explicit reach channel information and reach block index facilitates the responder to find a bounce NB reach channel from a responder's first block after initialization.

10. Method, according to claim 9, characterized in that the hop-on NB reach channel is common to at least one other responder currently in a subsequent block in an ongoing one-to-many reach session.

11. A method according to claim 8, characterized in that the RangingBlockIndex information in the SOR message facilitates multiple responders, including the responder, from synchronizing a scrambled timestamp (STS) sequence counter of common range integrity fragments (RIFs) transmitted by the initiator.

12. Method, according to claim 8, characterized in that the RangingBlockIndex information in the SOR message for one-to-one ranging facilitates the synchronization of the initiator and a scrambled timestamp sequence (STS) counter of the responder in an event where there is a previous initialization failure, causing the STS counters to be reused after the restart.

13. Method according to claim 8, characterized in that, responsive to explicit NB reach channel information indicating an NB reach channel for a block to which the time offset field points, it further comprises: verifying whether an initial NB channel is the same as a selected channel generated based on a channel seed and another reach block index provided by the Search message.

14. Method according to claim 8, characterized in that, responsive to explicit NB reach channel information indicating a reach block index for a block to which the time offset field points, Petition 870250090100, dated 10 / 03 / 2025, p. 23 / 26 4 / 5, further comprises: initializing a scrambled timestamp sequence (STS) counter for reach integrity fragments (RIFs) based on the reach block index.

15. Device deployable in a responder, characterized in that it comprises: a transceiver configured to communicate wirelessly; and a processor coupled to the transceiver and configured to perform operations comprising: participating, through the transceiver, in a range session by: receiving a Range Start Message (SOR) and a Survey Message from an initiator; and transmitting a Response Message responsive to the received Survey Message, wherein the SOR Message provides: explicit narrowband (NB) range channel information; or a Range Block Index (RangingBlockIndex) to which a time offset field in the SOR Message points.

16. Device according to claim 15, characterized in that each of the explicit NB range channel information and range block index facilitates the responder in finding a hop NB range channel from a responder's first block after initialization.

17. Device according to claim 16, characterized in that the hopping NB reach channel is common to at least one other responder currently in a subsequent block in an ongoing one-to-many reach session.

18. Device according to claim 15, characterized in that the RangingBlockIndex information Petition 870250090100, dated 10 / 03 / 2025, page 24 / 26 5 / 5 in the SOR message facilitates multiple responders, including the responder, synchronizing a scrambled timestamp sequence counter (STS) of common range integrity fragments (RIFs) transmitted by the initiator.

19. Device according to claim 15, characterized in that the RangingBlockIndex information in the SOR message for one-to-one ranging facilitates the synchronization of the initiator and a scrambled timestamp sequence (STS) counter of the responder in an event where there is a previous initialization failure, causing the STS counters to be reused after the reboot.

20. Apparatus according to claim 15, characterized in that, responsive to explicit NB reach channel information indicating an NB reach channel for a block to which the time offset field points, the processor is additionally configured to perform operations comprising: verifying whether an initial NB channel is the same as a selected channel generated based on a channel seed and a reach block index provided by the Search message; or initializing a scrambled timestamp sequence (STS) counter for reach integrity fragments (RIFs) based on the reach block index provided by the SOR message. Petition 870250090100, dated 10 / 03 / 2025, pp. 25 / 26

Images