WO2023096950A1 - Système et procédé de superposition de sensibilisation spatiale sur des préambules de message récurrents de réseau ad hoc mobile (manet) - Google Patents

Système et procédé de superposition de sensibilisation spatiale sur des préambules de message récurrents de réseau ad hoc mobile (manet) Download PDF

Info

Publication number
WO2023096950A1
WO2023096950A1 PCT/US2022/050828 US2022050828W WO2023096950A1 WO 2023096950 A1 WO2023096950 A1 WO 2023096950A1 US 2022050828 W US2022050828 W US 2022050828W WO 2023096950 A1 WO2023096950 A1 WO 2023096950A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
communications
nulling
frequency
preamble
Prior art date
Application number
PCT/US2022/050828
Other languages
English (en)
Inventor
Stephen M. CLARK
Tj T. KWON
William B. SORSBY
Brian L. AANDERUD
Eric J. LOREN
Original Assignee
Rockwell Collins, Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US17/534,061 external-priority patent/US11665658B1/en
Priority claimed from US17/541,703 external-priority patent/US20220094634A1/en
Priority claimed from US17/957,881 external-priority patent/US20230379033A1/en
Application filed by Rockwell Collins, Inc filed Critical Rockwell Collins, Inc
Publication of WO2023096950A1 publication Critical patent/WO2023096950A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/0035—Synchronisation arrangements detecting errors in frequency or phase

Definitions

  • Mobile Ad-hoc NETworks (MANET; e g., “mesh networks”) are known in the art as quickly deployable, self-configuring wireless networks with no pre-defined network topology.
  • MANET Mobile Ad-hoc NETworks
  • Each communications node within a MANET is presumed to be able to move freely. Additionally, each communications node within a MANET may be required to forward (relay) data packet traffic.
  • Data packet routing and delivery within a MANET may depend on a number of factors including, but not limited to, the number of communications nodes within the network, communications node proximity and mobility, power requirements, network bandwidth, user traffic requirements, timing requirements, and the like.
  • topology learning is the key task of routing mechanisms especially for proactive routing. Topology learning is non-trivial and requires significant over-the-air control packet exchanges due to the frequent topology changes caused by node mobility and channel condition changes. It is very hard to construct accurate topology of a large MANET.
  • Existing routing protocols utilize small hello packet exchanges to identify neighbor nodes. Hello messaging with neighbor list is a commonly used mechanism to learn the 1 st and the 2 nd hop neighbors.
  • Local topology learned by hello messaging is delivered via packet flooding or hop-by-hop propagation throughout the connected network. By combining local topology information, each and every communication node may identify efficient routes to all connected communication nodes. Whether by hello messaging or packet flooding, however, topology learning and neighbor discovery are major sources of MANET overhead.
  • fast-moving platforms e.g., communications nodes moving relative to each other
  • a frequency Doppler shift e.g., offset
  • the communication receiver must implement algorithms that estimate and correct for this doppler shift before performing demodulation. If the receiver does not perform the necessary compensation, the system will operate with a reduced receiver sensitivity and loss of performance - when experiencing large relative velocity between nodes.
  • a receiving (Rx) node of a mobile ad hoc communications network (MANET) or like multi-node network receives a preamble and/or header portion (e.g., a full header or partial portion thereof) of a resource allocation message sent by a transmitting (Tx) node of the network, where the Tx node is in motion according to a particular velocity vector (e.g., having a velocity and a direction) relative to a common reference frame known to both nodes (e.g., known to all nodes of the network), and the motion of the Tx node relative to the Rx node is associated with a Doppler frequency shift.
  • a particular velocity vector e.g., having a velocity and a direction
  • the Rx node determines a receiver-side Doppler nulling direction (e.g., to offset the Doppler shift) by adjusting a receiving frequency of the resource allocation message through a set of nulling frequencies each corresponding to a Doppler nulling direction (e.g., where each nulling frequency offsets a relative Doppler shift in the given nulling direction). Based on the frequency adjustment, the Rx node determines a relative velocity and/or relative direction of the Tx node (relative to the Rx node).
  • a receiver-side Doppler nulling direction e.g., to offset the Doppler shift
  • the network is a cell-based network
  • the Rx node is a participating member of a cell of the network
  • the Tx node is an administrator of the cell.
  • the Tx node is a tactical base station (TBS) of the network.
  • TBS tactical base station
  • the Rx node is a one-hop neighbor of the Tx node.
  • the Rx node may create a replica message based on the received preamble and/or header portion, e.g., if the resource allocation message is overly noisy or improperly demodulated.
  • the replica message may be correlated against the original resource allocation message, and the replica message used by the Rx node as a basis for adjusting the receiving frequency through the set of nulling frequencies.
  • the Rx node is a participating member of a cell
  • the Tx node is an administrator or TBS of a different cell of the network.
  • the Rx node is in transition from the current cell to the cell administered by the Tx node.
  • the common reference frame, as well as the relative motion between the Tx and Rx nodes, is three-dimensional.
  • the Rx node determines the receiver-side nulling direction by adjusting the receiving frequency through a set of step frequencies. For example, each step frequency may correspond to an incremental arc section (e.g., 10, 15, 20 degrees).
  • the Rx node is also in motion according to a receiver- side velocity vector (e.g., having a velocity and a direction). For example, based on receiver-side adjustments to the receiving frequency (e.g., and transmitter-side adjustments to the transmitting frequency by the Tx node), the Rx node determines a relative velocity vector (velocity, direction), e.g., the difference in velocity vectors between the Tx and Rx nodes.
  • a relative velocity vector velocity, direction
  • the Tx node is associated with a transmitter-side Doppler nulling direction
  • the Rx node determines the receiver-side Doppler nulling direction by adjusting the receiving frequency to a nulling frequency corresponding to a nulling direction opposite the transmitter-side Doppler nulling direction.
  • the Rx node is time synchronized with the Tx node.
  • the resource allocation message (or preamble or header portion thereof) is associated with a time of transmission (TOT) by the Tx node, the TOT known to the Rx node.
  • the Rx node determines a time of arrival (TOA) of the resource allocation message/preamble/header portion at the Rx node, and can determine, based on the TOT and TOA, a distance between the Tx and Rx nodes.
  • TOA time of arrival
  • a transmitting (Tx) node of a MANET or like multi-node network is also disclosed.
  • the Tx node is in motion according to a velocity vector (having a velocity and a direction) relative to a common reference frame known to each node of the network.
  • the Tx node is an administrator or otherwise associated with a cell (e.g., of a cell-based network) and transmits (e.g., at predetermined intervals) to participating nodes of the cell resource allocation messages having a preamble and a header.
  • the Tx node determines a transmitter- side Doppler nulling direction (e.g., to offset Doppler frequency shift associated with the relative motion of the Tx node) by adjusting a transmitting frequency of the preamble or header (or of the resource allocation message) through a nulling frequency corresponding to a particular Doppler nulling direction (e.g., for offsetting Doppler shift due to relative motion in that direction).
  • a transmitter- side Doppler nulling direction e.g., to offset Doppler frequency shift associated with the relative motion of the Tx node
  • the Tx node determines the transmitter-side Doppler nulling frequency by adjusting the transmitting frequency through a set of step frequencies, where each step frequency is associated with an incremental arc section (e.g., 10, 15, 20 degrees).
  • the Tx node is a tactical base station (TBS) configured for administration of the network cell.
  • TBS tactical base station
  • a method includes receiving, via a receiving (Rx) node of a MANET or like multi-node network, a preamble and/or header portion of a resource allocation message sent by a Tx node of the network, the Tx node in motion according to a velocity vector having a velocity and a direction.
  • Rx receiving
  • the Tx node in motion according to a velocity vector having a velocity and a direction.
  • the method includes determining, via the Rx node, a receiver-side nulling direction (e.g., for offsetting a Doppler frequency shift associated with the motion of the Tx node relative to the Rx node) by adjusting a receiving frequency of the message, preamble, and/or header portion through a nulling frequency corresponding to a Doppler nulling direction (e.g., for offsetting Doppler shift due to relative motion in said direction).
  • the method includes, based on the adjustment of the receiving frequency/determination of the Rx-side nulling frequency, determining a relative velocity vector of the Tx node relative to the Rx node (e.g., a relative velocity, a relative direction).
  • the method includes creating, via the Rx node, a replica message (e.g., a replica header portion and/or replica data payload) based on a noisy or incorrectly demodulated resource allocation message, and performing receiver-side frequency adjustment based on a correlation of the replica message and the resource allocation message.
  • a replica message e.g., a replica header portion and/or replica data payload
  • the method includes adjusting, via the Rx node, the receiving frequency through a set of step frequencies, each step frequency corresponding to an incremental arc section or Doppler nulling direction.
  • the Tx and Rx nodes are time synchronized, and the preamble, header portion, and/or message is associated with a time of transmission (TOT) by the Tx node that is also known to the Rx node, and the method includes determining, via the Rx node, a time of arrival (TOA) of the preamble, header portion, and/or message at the Rx node. The method includes determining, based on the TOT and TOA, an estimate of the distance between the Tx and Rx nodes.
  • TOT time of transmission
  • TOA time of arrival
  • the network is a cell-based network wherein the Rx node is a participating member of a cell within the network, and the Tx node is a tactical base station (TBS) configured for cell administration (e.g., either of the cell of which the Rx node is a participating member, or another cell).
  • TBS tactical base station
  • FIG. 1 is a diagrammatic illustration of a transmitting (Tx) and receiving (Rx) node of multi-node communications network, and the components of each node, according to example embodiments of the inventive concepts disclosed herein;
  • FIGS. 2A and 2B are plots of net Doppler frequency shift as a function of Doppler nulling angle for a mobile Tx node and stationary Rx nodes of the network of FIG. 1 at various angles;
  • FIG. 3 is a diagrammatic illustration of the multi-node communications network of FIG. 1 wherein both the Tx and Rx nodes are mobile;
  • FIGS. 4A and 4B are plots of net Doppler frequency shift as a function of Doppler nulling angle for a mobile Tx and Rx nodes of the network of FIG. 3 at various angles, headings, and/or velocities;
  • FIG. 5 is a diagrammatic illustration of Doppler null scanning operations of the Tx and Rx nodes of the multi-node communications network of FIGS. 1 and 3;
  • FIG. 6 is a diagrammatic illustration of a cell-based multi-node communications network according to example embodiments of the inventive concepts disclosed herein;
  • FIGS. 7A and 7B are diagrammatic illustrations of an operating theater implementation of the multi-node communications network of FIG. 6;
  • FIGS. 8A and 8B are diagrammatic illustrations of Doppler null overlay- operations of the multi-node communications networks of FIGS. 1 , 3, and 6 according to example embodiments of the inventive concepts disclosed herein;
  • FIG. 9 is a flow diagram illustrating a method for mobile ad hoc networking operations according to example embodiments of the inventive concepts disclosed herein.
  • a letter following a reference numeral is intended to reference an embodiment of the feature or element that may be similar, but not necessarily identical, to a previously described element or feature bearing the same reference numeral (e.g., 1 , 1 a, 1 b). Such shorthand notations are used for purposes of convenience only and should not be construed to limit the disclosure in any way unless expressly stated to the contrary.
  • “or” refers to an inclusive or and not to an exclusive or. For example, a condition A or B is satisfied by any one of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present).
  • any reference to “one embodiment” or “some embodiments” means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment disclosed herein.
  • the appearances of the phrase “in some embodiments” in various places in the specification are not necessarily all referring to the same embodiment, and embodiments may include one or more of the features expressly described or inherently present herein, or any combination or sub-combination of two or more such features, along with any other features which may not necessarily be expressly described or inherently present in the instant disclosure.
  • the multi-node communications network 100 may include multiple communications nodes, e.g., a transmitting (Tx) node 102 and a receiving (Rx) node 104.
  • Tx transmitting
  • Rx receiving
  • the multi-node communications network 100 may include any multi-node communications network known in the art.
  • the multi-node communications network 100 may include a mobile ad-hoc network (MANET) in which the Tx and Rx nodes 102, 104 (as well as every other communications node within the multi-node communications network) is able to move freely and independently.
  • the Tx and Rx nodes 102, 104 may include any communications node known in the art which may be communicatively coupled.
  • the Tx and Rx nodes 102, 104 may include any communications node known in the art for transmitting/transceiving data packets.
  • the Tx and Rx nodes 102, 104 may include, but are not limited to, radios, mobile phones, smart phones, tablets, smart watches, laptops, and the like.
  • the Rx node 104 of the multi-node communications network 100 may each include, but are not limited to, a respective controller 106 (e.g., control processor), memory 108, communication interface 110, and antenna elements 112.
  • controller 106 e.g., control processor
  • memory 108 e.g., memory 108
  • communication interface 110 e.g., communication interface
  • all attributes, capabilities, etc. of the Rx node 104 described below may similarly apply to the Tx node 102, and to any other communication node of the multi-node communication network 100.
  • the controller 106 provides processing functionality for at least the Rx node 104 and can include any number of processors, micro-controllers, circuitry, field programmable gate array (FPGA) or other processing systems, and resident or external memory for storing data, executable code, and other information accessed or generated by the Rx node 104.
  • the controller 106 may execute one or more software programs embodied in a non-transitory computer readable medium (e.g., memory 108) that implement techniques described herein.
  • the controller 106 is not limited by the materials from which it is formed or the processing mechanisms employed therein and, as such, can be implemented via semiconductor(s) and/or transistors (e.g., using electronic integrated circuit (IC) components), and so forth.
  • the memory 108 can be an example of tangible, computer- readable storage medium that provides storage functionality to store various data and/or program code associated with operation of the Rx node 104 and/or controller 106, such as software programs and/or code segments, or other data to instruct the controller 106, and possibly other components of the Rx node 104, to perform the functionality described herein.
  • the memory 108 can store data, such as a program of instructions for operating the Rx node 104, including its components (e.g., controller 106, communication interface 110, antenna elements 112, etc.), and so forth.
  • memory 108 can be integral with the controller 106, can comprise stand-alone memory, or can be a combination of both.
  • Some examples of the memory- 108 can include removable and non-removable memory components, such as random-access memory (RAM), read-only memory (ROM), flash memory (e.g., a secure digital (SD) memory card, a mini-SD memory card, and/or a micro ⁇ SD memory card), solid-state drive (SSD) memory, magnetic memory, optical memory, universal serial bus (USB) memory devices, hard disk memory, external memory, and so forth.
  • RAM random-access memory
  • ROM read-only memory
  • flash memory e.g., a secure digital (SD) memory card, a mini-SD memory card, and/or a micro ⁇ SD memory card
  • SSD solid-state drive
  • magnetic memory magnetic memory
  • optical memory optical memory
  • USB universal serial bus
  • the communication interface 110 can be operatively configured to communicate with components of the Rx node 104.
  • the communication interface 110 can be configured to retrieve data from the controller 106 or other devices (e.g., the Tx node 102 and/or other nodes), transmit data for storage in the memory 108, retrieve data from storage in the memory, and so forth.
  • the communication interface 110 can also be communicatively coupled with the controller 106 to facilitate data transfer between components of the Rx node 104 and the controller 106.
  • the communication interface 110 is described as a component of the Rx node 104, one or more components of the communication interface 110 can be implemented as external components communicatively coupled to the Rx node 104 via a wired and/or wireless connection.
  • the Rx node 104 can also include and/or connect to one or more input/output (I/O) devices.
  • the communication interface 110 includes or is coupled to a transmitter, receiver, transceiver, physical connection interface, or any combination thereof.
  • the communication interface 110 of the Rx node 104 may be configured to communicatively couple to additional communication interfaces 110 of additional communications nodes (e.g., the Tx node 102) of the multi- node communications network 100 using any wireless communication techniques known in the art including, but not limited to, GSM, GPRS, CDMA, EV-DO, EDGE, WiMAX, 3G, 4G, 4G LTE, 5G, WiFi protocols, RF, LoRa, and the like.
  • the antenna elements 112 may include directional or omnidirectional antenna elements capable of being steered or otherwise directed (e.g. , via the communications interface 110) for spatial scanning in a full 360-degree arc (114) relative to the Rx node 104.
  • one or both of the Tx node 102 and Rx node 104 may be moving in an arbitrary direction at an arbitrary speed, and similarly may be moving relative to each other.
  • the Tx node 102 may be moving relative to the Rx node 104 according to a velocity vector 116, at a relative velocity and a relative angular direction (an angle ⁇ relative to an arbitrary direction 118 (e.g., due east); ⁇ may be the angular direction of the Rx node relative to due east.
  • any signal transmitted by the Tx node 102 and received by the Rx node 104 may be associated with a Doppler frequency shift proportional to the relative radial velocity between the Tx and Rx nodes.
  • the relative radial velocity may be defined by the motion of the Tx node 102 or of the Tx and Rx nodes 104 (e.g., if both are in motion), in two or three dimensions.
  • the Tx node 102 may correct for its own Doppler frequency shift (e.g., due to its own motion according to the velocity vector 116) by implementing a Doppler nulling protocol, e.g., in an earth-centered earth-fixed (ECEF) reference frame (or in some other reference frame as needed). For example, the Tx node 102 may adjust its transmit frequency to counter the Doppler frequency offset such that there is no net frequency offset (e.g., “Doppler null”) for a given Doppler nulling direction 120 (at an angle ⁇ relative to the arbitrary direction 118, e.g., 100 degrees from due east).
  • Doppler nulling protocol e.g., in an earth-centered earth-fixed (ECEF) reference frame (or in some other reference frame as needed.
  • Doppler nulling protocol e.g., in an earth-centered earth-fixed (ECEF) reference frame (or in some other reference frame as needed.
  • the Tx node 102 may adjust its transmit frequency to counter the Dopp
  • the communications interface 110 of the Tx node 102 may be informed by the platform (e.g., the controller 106) of its own velocity vector and orientation (e.g., ⁇ , ) and may adjust its transmitting frequency to remove the Doppler frequency shift at each Doppler nulling direction 120 and angle ⁇ .
  • the platform e.g., the controller 106
  • the Doppler shift as seen by the Rx node due to the motion of the Tx node 102 may be
  • the Tx node 102 may adjust its transmitting frequency ( ⁇ f T ) to correct for this Doppler shift, based on its speed and velocity direction ⁇ such that the transmitter frequency adjustment ⁇ f T is proportional to the velocity projection onto the Doppler null direction and is such that the net frequency shift ⁇ f net seen by the Rx node 104 is the sum of these two terms, thus it is assumed that the velocity vector and velocity direction ⁇ will change slowly relative to periodic measurements of ⁇ f net , such that from the perspective of the Rx node 104 ⁇ , , and ⁇ may be regarded as constants.
  • the transmitter frequency adjustment ⁇ f T may compensate exactly for the net Doppler shift ⁇ f net . It may further be assumed that the Rx node 104 is configured to resolve any adjustments to the frequency of the inbound transmitted signal.
  • the sinusoidal plot may maintain an amplitude consistent with Tx speed or 5 ppm) regardless of velocity direction or position.
  • the stationary Rx node 104 may determine a speed of the Tx node 102 (e.g., a heading of the Tx node (e.g., ⁇ ), and a direction of the Tx node relative to the Rx node (e.g., ⁇ ). For example, although ambiguities of position direction may exist (e.g., 0 vs. 180 degrees as shown by FIG. 2A; ⁇ 90 degrees as shown by FIG. 2B), it is assumed the Rx node 104 is configured to resolve any such ambiguities, e.g., the Rx node knows whether the Tx node 102 is west or east of it.
  • a speed of the Tx node 102 e.g., a heading of the Tx node (e.g., ⁇ )
  • a direction of the Tx node relative to the Rx node e.g., ⁇
  • ambiguities of position direction may exist (e.g., 0 vs. 180 degrees as shown by
  • the multi-node communications network 300 may be implemented and may function similarly to the multi-node communications network 100 of FIG. 1 , except that the Rx node 302 of the multi-node communications network 300 may also be in motion (e.g., characterized by a receiver velocity and a velocity direction ⁇ .
  • the Rx node 302 may adjust its receiver frequency to compensate for its motion as well as the motion of the Tx node 102.
  • the true Doppler shift as seen by the Rx node 302 may be
  • both the Tx node 102 and the Rx node 302 may adjust their respective transmitting and receiving frequencies ( ⁇ f T , ⁇ f R ), each according to their own speed and velocity direction ( ⁇ , ⁇ ).
  • the Rx node 302 may adjust its receiving frequency either within, or prior to, the frequency resolution algorithm resolving the adjusted transmitting frequency (e.g., ⁇ f T ) of the received signal, thus
  • the net frequency shift seen by the Rx node 302 may be the sum of all terms:
  • FIGS. 4A and 4B the net frequency shift for moving Tx and Rx nodes 102, 302 is plotted (400) for various relative receiver angles ⁇ or velocity directions ⁇ , ⁇ .
  • amplitude of net frequency shift (e.g., in ppm) is consistent with relative velocity between the Tx node 102 and
  • Rx node 304
  • the velocity and velocity direction of the Tx node 102 may be known to the Rx node 302, resolving any dual point ambiguities with respect to the receiver angle ⁇ .
  • the Tx node 102 may scan (500) through a full 360 degrees of two-dimensional (2D) space in successive steps or intervals 502 (e.g., 36 cycles of 10 degrees each, 24 cycles of 15°, 18 cycles of 20°) to determine a shift or adjustment to the transmitter frequency (e.g., a step frequency) capable of correcting the net Doppler shift for each interval direction.
  • a shift or adjustment to the transmitter frequency e.g., a step frequency
  • less intuitive or more obfuscated scan approaches may be utilized.
  • both the Tx node 102 and Rx node 104 may implement directional discovery of each other (as well as other nodes of the multi-node communications network 100) by scanning the full 360 degrees (or a subset thereof).
  • the Tx node 102 and Rx node 104 may be time-synchronized to apply Doppler correction respectively for their own motions relative to a common inertial reference frame. As a transmit angle advances, a receive angle retreats by a same amount as the transmit angle advance. This can be understood by first considering the Tx node 102 when the Tx node applies full Doppler correction in its own direction of travel.
  • the Rx node 104 directly in line with the path of travel of the Tx node 102. If the Rx node 104 at the same time similarly applies Doppler correction for the Rx node’s 104 motion in line with the Tx node 102, then at least a near-zero Doppler path (e.g., a near-zero Doppler path or a zero Doppler path) will exist from the Tx node 102 to the Rx node 104.
  • a near-zero Doppler path e.g., a near-zero Doppler path or a zero Doppler path
  • the Doppler correction can be swept through a plurality of (e.g., some or all) angles so that a zero Doppler path 504 or near-zero Doppler path will exist from the Tx node 102 to the Rx node 104 including the angle resulting in the near-zero Doppler path or the zero Doppler path, the zero Doppler path having zero net frequency offset.
  • an angle resulting in a near-zero Doppler path may be within 5 degrees of the angle resulting in the zero Doppler path.
  • a zero-Doppler path 504 will be available between the Tx node 102 and the Rx node 104 when the two are synchronized to apply Doppler correction for a swept angle ⁇ relative to the inertial reference frame of choice.
  • neither the Tx node 102 nor the Rx node 104 need know a direction to the other node in advance.
  • the Rx node may determine an angle of arrival (AOA) of the transmitted signal, and thus the relative direction/receiver angle ⁇ may be known to the Rx node (e.g., and shared with the Tx node).
  • AOA angle of arrival
  • the Tx node 102 and Rx node 104 may share a time of transmission (TOT) and a time of arrival (TOA; e.g., a time the signal is received by the Rx node) of the transmitted signal, and thereby determine a distance 506 between the Tx and Rx nodes based on the transmission delay.
  • distance estimates between the Tx and Rx nodes 102, 104 may include an error component proportional to relative bias error between the two nodes.
  • any clock error between the two nodes may produce an error component in the distance estimate (e.g., 1 light-microsecond (300 m ⁇ 984 ft) for every 1 ⁇ s/1000 ns of clock error).
  • the 2D scanning approach may be expanded into 3D space.
  • the 2D scan for a given step direction may correspond to a conical coverage area 508, e.g., a 10-degree, 15-degree, 20-degree cone, and thereby to a 3D fractional coverage area.
  • Doppler null scanning for a full spherical region may be achieved by adding additional scanning cycles corresponding to the areas uncovered by the 2D scan.
  • the mobile ad hoc network 600 may be implemented similarly to the multi-node communications networks 100, 300 of FIGS. 1 and 3, except that the MANET 600 may be organized as a cell-based network of tactical base station (TBS) nodes 602 and user equipment (UE) nodes 604 organized into cells 606, or subsets of the MANET 600.
  • TBS tactical base station
  • UE user equipment
  • each TBS node 602 and UE node 604 may be implemented and may function similarly to the Tx and/or Rx nodes 102, 104, 302 of FIGS. 1 and 3, except that each cell 606 within the MANET 600 may correspond to a subset of the MANET administered by a TBS node 602.
  • each cell 606 may correspond to a geographical region or a coverage area of the TBS node 602.
  • the MANET 600 may correspond to an operating theater, within which each cell 606 may include a set of participating UE nodes 604 in operation within that cell.
  • each cell 606 may include a set of participating UE nodes 604 in operation within that cell.
  • a TBS node 602 may control all network communications and allocate communications resources to all participating UE nodes 604
  • participating UE nodes 604 may include ground-based, water- based, or airborne vehicles and individual manpacks operating either within, or remotely from, a vehicle.
  • each TBS node 602 may be a ground-based, water-based, or airborne node (e.g., an unmanned aircraft system (UAS)) in control of all network communications within the cell 606 and configured to allocate communications resources to ail participating UE nodes 604 currently assigned to that TBS node.
  • UAS unmanned aircraft system
  • resource allocations may be transmitted by each TBS node 602 to its assigned participating UE nodes 604 at regular intervals, e.g., each second.
  • each TBS node 602 and participating UE node 604 may be stationary or mobile.
  • the participating UE node 604a assigned to the TBS node 602a and the cell 606a may be in motion toward the cell 606b administered by the TBS 602b.
  • the participating UE node 604a may be handed off by the TBS node 602a to the control of the TBS node 602b, e.g., while operating within the cell 606b.
  • the participating UE node 604a may maintain communications with both TBS nodes 602a-b while preparing for the transition to the cell 606b and TBS node 602b.
  • the participating UE node 604b, in motion away from the cell 606b may operate within the coverage areas of both TBS nodes 602a ⁇ b but may remain under the administration of the TBS node 602a and within the cell 606a.
  • the multi-node communications network 700 may be implemented and may function similarly to the multi-node communications networks 100, 300, 600 except that the multi-node communications network 700 may be implemented in an operating theater.
  • the multi-node communications network 700 may include cells 606a, 606b respectively administered by airborne TBS nodes 702a, 702b.
  • the cells 606a, 606b may include participating UE nodes embodied in ground-based vehicles 704a-704c and roaming users 706a-706f (e.g., manpacks).
  • the roaming users 706a, 706b may maintain communications links with the ground- based vehicle 704a in addition to the airborne TBS 702a
  • the roaming users 706c, 706d may maintain communications links with the ground-based vehicle 704b
  • the roaming user 706e may maintain communications links with the ground-based vehicle 704c (in the latter two cases, in addition to the airborne TBS 702b).
  • the roaming user 704f may be a participating UE node of the cell 606a assigned to the airborne TBS 702a, but in motion toward the cell 606b administered by the airborne TBS 702b and thereby in communication with both airborne TBS nodes.
  • the airborne TBS 702a, 702b may be capable of long-haul communications links 708 beyond the normal operating range defining the cells 606a, 606b.
  • each airborne TBS 702a, 702b may receive regular resource allocation messages from the other airborne TBS.
  • the ground-based vehicle 704c and roaming user 706f may be within the long-haul range 708 of the airborne TBS 702a and may receive regular resource allocation messages therefrom.
  • FIG. 8A a resource allocation message 800 sent by the TBS 602a ⁇ 602b of FIG. 6 and the airborne TBS 702a-702b of FIG. 7 is shown.
  • the resource allocation message 800 may include, in addition to a data payload 802, an acquisition preamble 804 and packet header 806.
  • (sine 2 ) function e.g., .
  • Tx nodes (102, FIG. 1 ) and Rx nodes (104, FIG. 1 ; 302, FIG. 3) may perform frequency adjustments to correct for Doppler shift (e.g., Doppler corrections; Doppler null overlay 810) over acquisition preambles 804 and/or packet headers 806 transmitted by the Tx nodes and received by the Rx nodes.
  • Doppler shift e.g., Doppler corrections; Doppler null overlay 810
  • 7A-B may be capable of travel and detection by receiving UE nodes (ground-based vehicles 704, roaming users 706) throughout the long-haul range (708, FIG. 7B) of the transmitting TBS node, whereas payload user data 802 may be reliably detectible only within the cells (606a, 606b; FIG. 7B) corresponding to the normal coverage range of the transmitting TBS node.
  • acquisition preambles 804 and/or preamble headers 806 may be received and/or detected, in whole or in part, up to three hops away.
  • transmitting Tx and TBS nodes 102, 702 may perform Doppler null overlay 810 over the complete acquisition preamble 804 and packet header 806, while receiving nodes 104, 302, 704, 706 (e.g., N-hop neighbors within the long-haul range 708 of the transmitting TBS node 702) may perform spatial aware correlations 812 (e.g., adjusting the receiving frequency of the preamble and/or header to correct for Doppler shift based on the motion of the receiving node) on the acquisition preamble and that portion 806a of the packet header deducible a priori by the receiving node, e.g., based on protocols observed by the receiving node or throughout the multi-node communications network 100, 300, 600, 700 (e.g., including legacy systems).
  • Doppler null overlay 810 over the complete acquisition preamble 804 and packet header 806, while receiving nodes 104, 302, 704, 706 (e.g., N-hop neighbors within the long-haul range 708
  • a priori header portion 806a may include node addresses and/or the encoding mode used to modulate the payload.
  • the deduction of the header portion 806a may be performed by a priori knowledge of which nodes will transmit at a given time, as well as which mode the transmitting nodes will typically use based on to recent previous transmissions. For example, if the TBS node 702a shown by FIGS.
  • the TBS node 102, 702 (referring back to FIG. 8A) to include the header portion 806a within the correlation window 812 shown by FIG. 8A.
  • one-hop neighbors of the transmitting Tx node 102/TBS node 702 may receive the full resource allocation message (800, FIG. 8A) but in a noisy and/or incorrectly demodulated form 814.
  • one-hop neighbors may include Rx nodes 104/302, ground-based vehicles 704, and/or roaming users 706 at the outer limits of the cell 606a-606b administered by the Tx node 102/transmitting TBS node 702.
  • the resource allocation message 814 may include an intact acquisition preamble 804, but one or more of the packet header/header portion 806a and data payload 802a may be incorrectly modulated due to noise.
  • the receiving one-hop neighbor may form a replica resource allocation message 816 based on the incorrectly modulated resource allocation message 814, performing receiver-side passive spatial awareness correlation 818 over the replica resource allocation message.
  • the replica resource allocation message may include a replica packet header 806b and/or replica data payload 802b.
  • the receiving one-hop neighbor may construct a replica packet header 806b, a replica data payload 802b, or other portions of a replica resource allocation message 816 via error correction coding of the incorrectly modulated data 814, e.g., via encoding of the received bits to generate redundant parity bits which may be processed by the receiving node to correct erroneously modulated bits.
  • the error-corrected portions of the incorrectly modulated resource allocation message 814 may be remodulated by the receiving node, producing “corrected” bits for remodulation into the replica packet header 806b or replica data payload 802b.
  • the replica resource allocation message 816 may thus serve as a reference for the receiver-side passive spatial awareness correlation 818 against the original incorrectly modulated resource allocation message 814.
  • the method 900 may be implemented by the receiver nodes 104, 302, 704, 706 and may include the following steps.
  • the receiving (Rx) node receives at least a preamble or a header portion (e.g., a full header or a portion thereof) of a resource allocation message transmitted by a transmitting (Tx) node within the multi-node communications network of which the receiving node is a participating node, the Tx node in motion according to a velocity and a direction associated with a Doppler shift.
  • a preamble or a header portion e.g., a full header or a portion thereof
  • the network may be a cell-based network and the Tx node may be a tactical base station (TBS) configured for administration of a cell of which the receiving node is a participating member (e.g., participating user equipment (UE) such as a vehicle-based node or manpack) or for administration of another cell of the network (e.g., a cell of which the receiving node is not a participating member).
  • TBS tactical base station
  • the receiving node determines a receiver-side Doppler nulling direction capable of correcting for Doppler shift associated with the transmitted resource allocation message and with relative motion of the transmitting Tx node and the receiver node by adjusting a receiving frequency of the resource allocation message through at least one nulling direction.
  • the receiving node may also be in motion and correcting for Doppler shift due to its own velocity and direction.
  • the receiving node may scan through a range of directions relative to a 2D or 3D inertial reference frame, performing Doppler nulling by adjusting the receiver frequency at one or more interval directions within the range.
  • the receiving node determines, based on the receiver-side Doppler nulling and transmitter-side Doppler nulling to correct for Doppler shift due to the motion of the Tx node, one or more of: the relative velocity of the Tx node; the velocity direction of the Tx node; and a direction of the Tx node relative to the receiving node, e.g., based on a determined angle of arrival (AOA) of the received transmission.
  • AOA angle of arrival
  • the receiving node may determine a time of arrival (TOA) of the preamble, header portion, and/or resource allocation message.
  • TOA time of arrival
  • the receiving node may determine, based on the determined TOA and a time of transmission (TOT) of the preamble/header portion/resource allocation message by the Tx node, a distance between the receiving node and the Tx node.
  • TOT time of transmission
  • embodiments of the methods disclosed herein may include one or more of the steps described herein. Further, such steps may be carried out in any desired order and two or more of the steps may be carried out simultaneously with one another. Two or more of the steps disclosed herein may be combined in a single step, and in some embodiments, one or more of the steps may be carried out as two or more sub-steps. Further, other steps or sub-steps may be carried in addition to, or as substitutes to one or more of the steps disclosed herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un nœud de communication d'un réseau mobile ad hoc (MANET) ou d'un réseau similaire à plusieurs nœuds peut recevoir une partie de préambule et/ou d'en-tête associée à un message d'allocation de ressources (par exemple, par opposition au message complet) transmis par un autre nœud de réseau en mouvement par rapport au nœud récepteur. Le nœud de réception détermine une direction d'annulation Doppler côté récepteur (par exemple, pour compenser le décalage Doppler associé au mouvement du nœud d'émission par rapport au nœud de réception) en ajustant une fréquence de réception du préambule et/ou de la partie d'en-tête à travers une ou plusieurs fréquences d'annulation, chaque fréquence d'annulation étant associée à une direction d'annulation pour compenser le décalage Doppler dû au mouvement relatif dans cette direction. Sur la base de la détermination d'une fréquence d'annulation Doppler côté récepteur, le nœud de réception peut déterminer une vitesse et une direction du mouvement relatif entre les nœuds de réception et d'émission.
PCT/US2022/050828 2021-11-23 2022-11-23 Système et procédé de superposition de sensibilisation spatiale sur des préambules de message récurrents de réseau ad hoc mobile (manet) WO2023096950A1 (fr)

Applications Claiming Priority (10)

Application Number Priority Date Filing Date Title
US17/534,061 2021-11-23
US17/534,061 US11665658B1 (en) 2021-04-16 2021-11-23 System and method for application of doppler corrections for time synchronized transmitter and receiver
US17/541,703 2021-12-03
US17/541,703 US20220094634A1 (en) 2019-11-27 2021-12-03 System and method for spatial awareness network routing
US202263344445P 2022-05-20 2022-05-20
US63/344,445 2022-05-20
US17/857,920 2022-07-05
US17/857,920 US20220342027A1 (en) 2021-04-16 2022-07-05 System and method for application of doppler corrections for time synchronized transmitter and receiver in motion
US17/957,881 2022-09-30
US17/957,881 US20230379033A1 (en) 2021-04-16 2022-09-30 System and method for spatial awareness overlay onto mobile ad hoc network (manet) frequent message preambles

Publications (1)

Publication Number Publication Date
WO2023096950A1 true WO2023096950A1 (fr) 2023-06-01

Family

ID=84602350

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2022/050828 WO2023096950A1 (fr) 2021-11-23 2022-11-23 Système et procédé de superposition de sensibilisation spatiale sur des préambules de message récurrents de réseau ad hoc mobile (manet)

Country Status (1)

Country Link
WO (1) WO2023096950A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998034125A1 (fr) * 1997-02-03 1998-08-06 Nokia Telecommunications Oy Radiogoniometre doppler et procede de localisation a l'aide d'un radiogoniometre doppler
JP2006345427A (ja) * 2005-06-10 2006-12-21 Matsushita Electric Ind Co Ltd 移動体の無線伝送方法、無線伝送装置及び無線伝送システム
US20130287080A1 (en) * 2010-10-29 2013-10-31 Lilee Systems, Ltd System and method of frequency offset compensation for radio system with fast doppler shift
US20200120458A1 (en) * 2017-07-01 2020-04-16 Intel Corporation Methods and devices for vehicular radio communications

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998034125A1 (fr) * 1997-02-03 1998-08-06 Nokia Telecommunications Oy Radiogoniometre doppler et procede de localisation a l'aide d'un radiogoniometre doppler
JP2006345427A (ja) * 2005-06-10 2006-12-21 Matsushita Electric Ind Co Ltd 移動体の無線伝送方法、無線伝送装置及び無線伝送システム
US20130287080A1 (en) * 2010-10-29 2013-10-31 Lilee Systems, Ltd System and method of frequency offset compensation for radio system with fast doppler shift
US20200120458A1 (en) * 2017-07-01 2020-04-16 Intel Corporation Methods and devices for vehicular radio communications

Similar Documents

Publication Publication Date Title
US20230393229A1 (en) System and method for application of doppler corrections for time synchronized stationary transmitter and receiver in motion
CN114223223B (zh) 基于多波束用户设备的定位场景中用于定位参考信号（prs）资源的位置辅助信息的分层报告
CN110794398B (zh) 无线通信***中通过镜面反射的车辆微波成像方法和设备
JP2023528133A (ja) 低レイテンシまたはオンデマンド測位のための精度の希釈に支援された報告
KR20230044185A (ko) 밀리미터파 시스템에서 바이스태틱 무선 인터페이스 기반 무선 주파수 감지를 위한 싱글 사이드 빔 관리
KR20230049086A (ko) 사용자 장비 전력 절약들을 위한 포지셔닝 기준 신호들의 서브세트 표시
KR20240067886A (ko) 공동 포지셔닝 세션들에 대한 불연속 수신 (drx) 기반 앵커 사용자 장비 (ue) 선택
TW202241184A (zh) 用於定位的錨使用者設備選擇
JP2023545997A (ja) アンテナ情報を使用することによる到着角度および離脱角度システム最適化
US20230379007A1 (en) Situational awareness (sa) in radio silence (spatial awareness)
US20230379033A1 (en) System and method for spatial awareness overlay onto mobile ad hoc network (manet) frequent message preambles
US20220342027A1 (en) System and method for application of doppler corrections for time synchronized transmitter and receiver in motion
WO2023096950A1 (fr) Système et procédé de superposition de sensibilisation spatiale sur des préambules de message récurrents de réseau ad hoc mobile (manet)
TW202331294A (zh) 用於空間覺知疊加至行動特殊網路頻繁訊息前文之系統及方法
US20230333193A1 (en) Dns spatial discoveries with on-going traffic
US20230288521A1 (en) Directional enhancements for mobile ad hoc networks (manet) via doppler null scanning (dns)
US20230280437A1 (en) Reliable efficient flooding with doppler nulling (spatial awareness)
US20230379008A1 (en) Doppler-nulling for directional networks (spatial awareness)
WO2023225339A1 (fr) Découvertes spatiales dns avec trafic en cours
WO2023096945A1 (fr) Système et procédé de compensation doppler entre des nœuds émetteur et récepteur
CN113132894B (zh) 定位方法及装置、wlan设备、计算设备及存储介质
CN109788466B (zh) 基于先验信息的三维立体无线自组网的邻居发现方法
US20230305093A1 (en) Adaptive doppler-nulling digitization for high-resolution
US20230288518A1 (en) Robust addressing schema for spatial awareness via doppler null scanning (dns)
WO2023123505A1 (fr) Configuration de motif de faisceau pour gestion de faisceau de dispositif de communication aérien

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22830052

Country of ref document: EP

Kind code of ref document: A1