U.S. patent number 9,473,221 [Application Number 14/878,943] was granted by the patent office on 2016-10-18 for subnetworks and multiple networks.
This patent grant is currently assigned to Facebook, Inc.. The grantee listed for this patent is Facebook, Inc.. Invention is credited to Sanjai Kohli.
United States Patent |
9,473,221 |
Kohli |
October 18, 2016 |
Subnetworks and multiple networks
Abstract
A Next Generation Data Network is described. It leverages the
"cloud" for data management, frequency data computation and
analytics. Nodes in the network are arranged into subnets with at
least one node per subnet connected to a physical high-speed
computer communication link. The wireless network using packet
switched beams, the beams are formed and switched electronically.
It utilizes advanced signal processing to compensate for low
transmit signal power and multipath reflections that can be
frequency or flat fades.
Inventors: |
Kohli; Sanjai (Manhattan Beach,
CA) |
Applicant: |
Name |
City |
State |
Country |
Type |
Facebook, Inc. |
Menlo Park |
CA |
US |
|
|
Assignee: |
Facebook, Inc. (Menlo Park,
CA)
|
Family
ID: |
51569065 |
Appl.
No.: |
14/878,943 |
Filed: |
October 8, 2015 |
Prior Publication Data
|
|
|
|
Document
Identifier |
Publication Date |
|
US 20160028610 A1 |
Jan 28, 2016 |
|
Related U.S. Patent Documents
|
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
Issue Date |
|
|
14214957 |
Mar 16, 2014 |
9215644 |
|
|
|
61789188 |
Mar 15, 2013 |
|
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
H04W
52/42 (20130101); H04W 72/0473 (20130101); H04L
45/02 (20130101); H04B 7/0617 (20130101); H04W
40/14 (20130101); H04W 56/00 (20130101); H04W
24/04 (20130101); H04W 40/34 (20130101); H04W
72/085 (20130101); H04B 7/0408 (20130101); H04W
40/16 (20130101); H04L 45/22 (20130101); H04W
28/18 (20130101); H04W 16/28 (20130101); H04L
45/46 (20130101); H04W 24/02 (20130101); H04W
40/12 (20130101); H04W 24/10 (20130101); H04W
40/02 (20130101); H04B 15/00 (20130101); H04W
72/0453 (20130101); H04W 72/1263 (20130101); Y02D
70/122 (20180101); Y02D 70/00 (20180101); Y02D
30/70 (20200801); Y02D 70/22 (20180101); H04W
72/00 (20130101); Y02D 70/34 (20180101); H04W
84/22 (20130101); H04L 1/1867 (20130101); Y02D
70/164 (20180101) |
Current International
Class: |
H04B
7/04 (20060101); H04B 15/00 (20060101); H04W
24/04 (20090101); H04W 40/12 (20090101); H04W
40/02 (20090101); H04W 40/14 (20090101); H04L
12/707 (20130101); H04B 7/06 (20060101); H04W
40/16 (20090101); H04W 40/34 (20090101); H04W
72/04 (20090101); H04W 28/18 (20090101); H04W
56/00 (20090101); H04L 12/751 (20130101); H04L
12/715 (20130101); H04W 72/12 (20090101); H04W
24/02 (20090101); H04W 52/42 (20090101); H04W
72/08 (20090101); H04W 16/28 (20090101); H04W
24/10 (20090101); H04L 1/18 (20060101); H04W
72/00 (20090101); H04W 84/22 (20090101) |
References Cited
[Referenced By]
U.S. Patent Documents
Other References
Notice of Allowance mailed Sep. 29, 2015, for U.S. Appl. No.
14/214,957 of Kohli, S., filed Mar. 16, 2014. cited by applicant
.
Notice of Allowance mailed Oct. 21, 2015, for U.S. Appl. No.
14/214,956 by Kohli, S., filed Mar. 16, 2014. cited by applicant
.
U.S. Appl. No. 14/214,956 by Kohli, S., filed Mar. 16, 2014. cited
by applicant .
U.S. Appl. No. 14/214,957 by Kohli, S., filed Mar. 16, 2014. cited
by applicant .
U.S. Appl. No. 14/878,960 by Kohli, S., filed Oct. 8, 2015. cited
by applicant .
U.S. Appl. No. 14/878,974 by Kohli, S., filed Oct. 8, 2015. cited
by applicant .
U.S. Appl. No. 14/878,982 by Kohli, S., filed Oct. 8, 2015. cited
by applicant .
Corrected Notice of Allowability mailed Jan. 15, 2016, for U.S.
Appl. No. 14/214,956 by Kohli, S., filed Mar. 16, 2014. cited by
applicant .
Notice of Allowance mailed Nov. 3, 2015, for U.S. Appl. No.
14/214,957 of Kohli, S.,filed Mar. 16, 2014. cited by
applicant.
|
Primary Examiner: Elliott, IV; Benjamin H
Parent Case Text
CROSS-REFERENCE TO RELATED APPLICATION(S)
The present application is a continuation of U.S. patent Ser. No.
14/214,957, filed on Mar. 16, 2014, entitled "Distribution Node and
Client Node for Next Generation Data Network," which is related to
and claims priority under 35 U.S.C. 119(e) to U.S. provisional
patent application, Ser. No. 61/789,188, entitled "Next Generation
Data Network," filed on Mar. 15, 2013. The contents of these
applications are hereby incorporated by reference in their
entirety.
Claims
I claim:
1. A method, comprising: receiving information from nodes in a
wireless communication network of a network type that includes
multiple destination nodes and multiple client nodes, each of the
nodes configured to at least wirelessly transmit and at least
wirelessly receive data packets to form the wireless communication
network, wherein at least two of the destination nodes in the
wireless communication network are connected to a physical
high-speed computer communication link, wherein the information
describes channel conditions between the nodes; computing routes
for exchanging data packets between nodes in the wireless
communication network; transmitting the routes for storage in
routing tables at the nodes, wherein the nodes are organized into
two or more subnets, each subset associated with a node that is
communicably coupled to the physical high-speed; computer
communication link; and using a time of travel delay between nodes
as a security key for a data packet.
2. The method of claim 1, wherein the subnets include a core with
at least one destination node and a node that is connected to the
physical high-speed computer communication link and additional
nodes at an edge of the subnet, the method further comprising:
instructing the nodes that are at the edge of the subnet to
transmit in a manner that avoids interference with transmissions
from nodes in the core of the subnet.
3. The method of claim 2, further comprising: instructing the nodes
at the edge of the subnet to transmit data packets at times
selected to minimize interference with transmissions from the nodes
in the core of the subnet.
4. The method of claim 2, further comprising: creating multiple
virtual networks using the nodes in the wireless communication
network and instructing the nodes that are connected to the
physical high-speed computer communication link to assign data
bandwidth according to a specified level of service for each
virtual network.
5. The method of claim 4, further comprising: coordinating packet
sequencing between networks using beamforming and polarization.
6. The method of claim 1, wherein the nodes in each subnet are
categorized by their distance in hops away from the node that is
connected to the physical high-speed computer communication link,
the method further comprising: instructing nodes to decrease a rate
of data transmission with an increasing number of hops away from
the node that is connected to the physical high-speed computer
communication link.
7. The method of claim 1, further comprising: instructing a
transmitting node regarding a power level to use when transmitting
a data packet to another node in the network.
8. The method of claim 1, further comprising: instructing a
transmitting node regarding beamforming parameters to use when
transmitting a data packet to another node in the network.
9. The method of claim 1, further comprising: ranking different
routes between nodes by probabilities and instructing a node to use
a route with a highest probability.
10. The method of claim 1, further comprising: instructing a
transmitting node to use a route with a least number of nodes
between the transmitting node and a destination node.
11. The method of claim 1, further comprising: adjusting one or
more of beamforming coefficients, transmit power, modulation,
coding and symbol rate for the nodes in the wireless communication
network to increase network capacity.
12. A method, comprising: receiving information from nodes in a
wireless communication network of a network type that includes
multiple destination nodes and multiple client nodes, each of the
nodes configured to at least wirelessly transmit and at least
wirelessly receive data packets to form the wireless communication
network, wherein at least two of the destination nodes in the
wireless communication network are connected to a physical
high-speed computer communication link, wherein the information
describes channel conditions between the nodes; computing routes
for exchanging data packets between nodes in the wireless
communication network; transmitting the routes for storage in
routing tables at the nodes, wherein the nodes are organized into
two or more subnets, each subset associated with a node that is
communicably coupled to the physical high-speed, computer
communication link; and instructing a node in the wireless
communication network to adjust its receive beamforming direction
away from a direction in which interference may occur if another
node is transmitting at the same time as the node is receiving.
13. A method, comprising: receiving information from nodes in a
wireless communication network of a network type that includes
multiple destination nodes and multiple client nodes, each of the
nodes configured to at least wirelessly transmit and at least
wirelessly receive data packets to form the wireless communication
network, wherein at least two of the destination nodes in the
wireless communication network are connected to a physical
high-speed computer communication link, wherein the information
describes channel conditions between the nodes; computing routes
for exchanging data packets between nodes in the wireless
communication network; transmitting the routes for storage in
routing tables at the nodes, wherein the nodes are organized into
two or more subnets, each subset associated with a node that is
communicably coupled to the physical high-speed, computer
communication link; and instructing a node to transmit a data
packet by changing a transmit beamforming direction to a
non-line-of-sight path if the data packet is not successfully
received by a receiving node.
14. The method of claim 1, further comprising: instructing a node
to send portions of a data packet via different routes to a
destination node if the data packet is not successfully received by
a receiving node.
15. A multi-hop, wireless communication network, comprising:
multiple destination nodes and multiple client nodes, at least some
of the nodes configured to at least wirelessly transmit and at
least wirelessly receive data packets to form the wireless network,
wherein at least two of the destination nodes in the wireless
communication network are communicatively linked to a physical
high-speed computer communication link; a control computer
configured to receive information from nodes in the wireless
communication network describing channel conditions between the
nodes; compute routes over which data packets are to be exchanged
between nodes in the network; transmit the routes to the nodes for
storage in routing tables; and use a time of travel delay between
nodes as a security key for a data packet; wherein the nodes are
organized into two or more subnets, each subnet associated with a
node that is connected to the physical, high-speed computer
communication link.
16. The multi-hop, wireless communication network of claim 15
wherein the nodes in the wireless communication network are
categorized by their distance in hops away from the node that is
connected to the physical high-speed computer communication link;
and wherein the control computer is configured to instruct the
nodes to decrease a rate of data transmission from a node with an
increasing numbers of hops from the node that is connected to the
high-speed computer communication link.
17. The multi-hop, wireless communication of claim 15, wherein the
wireless communication network includes a core with at least one
destination node and the node that is connected to the physical
high-speed computer communication link, wherein the wireless
communication network also includes additional nodes at an edge of
the network, and wherein the control computer is further configured
to synchronize the nodes at the edge of the wireless communication
network so that they do not cause interference with the nodes in
the core of the network.
18. The multi-hop, wireless communication network of claim 17,
wherein the control computer is configured to instruct the nodes at
the edge of the wireless communication network to transmit data
packets at times selected to minimize interference with
transmissions from the nodes in the core of the network.
19. The multi-hop, wireless communication network of claim 15,
wherein nodes in the wireless communication network are coarsely
synchronized using GPS signals and finely synchronized using
signals transmitted between the nodes of the subnet.
Description
TECHNICAL FIELD
The present disclosure relates generally to wireless communication.
In particular, the present disclosure relates to methods and
systems for controlling a multi-hop mesh wireless data network.
BACKGROUND
Data networks have traditionally been wired, either copper or
fiber. Wireless spectrum has typically been used for subscriber
links, not Data Infrastructure. The advent of micro cells, pica
cells, nano cells, and hotspots has made the provisioning of wired
Data prohibitively expensive. This is a result of inflexibility of
wired networks; cable has to be run to add new points of presence.
In many cases, this requires that streets be torn up.
Wireless Data networks can be much more flexible, and hence more
economically viable. However, existing wireless Data network
architectures limit this flexibility in several ways. One common
form of wireless Data networks uses point-to-point radio links,
typically operating in the microwave or millimeter wave bands.
Another common form of wireless Data networks use a cellular
architecture. These networks are based on frequency reuse.
Typically a cellular reuse scheme where the total available
frequency spectrum is divided into sub bands. "colors", which are
reused in disjoint geographical areas, "cells". For example, reuse
factors of 4, 7, and 12 are popular. Other systems reuse time,
polarization, or code. The disadvantage of all of these fixed,
"cellular", reuse schemes are that they are inefficient, resources
are wasted. For example, in a 7 to 1 frequency cellular reuse
system, only 1/7-th of the total available frequency spectrum is
available in a single cell, even if none of the adjacent cells are
being used. Another disadvantage of these frequency reuse schemes
is that it is difficult to add more cells in an area of high
demand.
SUMMARY
This invention is a wireless Data network that reuses the same
frequency band in all cells. For example, if the frequency band is
divided into three frequency channels, all three of these channels
are available to every node in the network. Frequency channels are
dynamically assigned by the Cloud to maximize network capacity
taking into account potential interference from both other links in
the network and from other sources. This is distinct from previous
systems which try to maximize C/(N+1), ratio of carrier power to
combined noise plus interference power. Further, the system
dynamically adjusts route and frequency channel assignments,
transmit power, modulation, coding, and symbol rate to maximize
network capacity and probability of packet delivery, rather than
trying to maximize the capacity of any one link.
The Next Generation Network is a time domain duplex (TDD) system
(it can also be Frequency domain duplex, however the TDD is the
more complex case, hence explained in detail). All sectors of each
node transmit or receive at the same time. They are synchronized by
a master controller. This allows the use of a single frequency
across all sectors and mitigates adjacent channel interference. It
is a multipoint system where there is no limit to how many nodes a
node can communicate with, Each sector on each node has a 2D or 3D
beamforming capability. This permits the unit to form a high gain
beam that is pointed at the destination node and packet sent. The
receiving node does the same it forms a high gain narrow beam
pointed at the transmitting node. Beam coefficients are grossly
computed in the cloud and fine-tuned between the units.
The network uses two forms of route adjustment. A mesh network
topology is used to allow traffic to be routed between two nodes
via at least two geographically independent paths. This provides
load balancing, so that when one path becomes congested or
degraded, traffic can be routed around it. It also mitigates the
effects of external interference. The second form of route
adjustment is "micro-routes". Rather than just pointing the receive
antenna at the transmitter, or pointing the transmit antenna at the
receiver, this invention takes advantage of multipath to use
indirect (non-line-of-sight) paths in addition to the direct
(line-of-sight) path. The ability to use these paths provides
several advantages. One is interference avoidance. Any interference
that was arranging along the main beam will be mitigated by
pointing away from it. Another is obstacle avoidance. The micro
route can be used to mitigate obstacles, such as trees, signs,
trucks, or similar that blocks the direct line-of-sign path.
Further, by pre-computing these reflected routes they can be
applied in real time.
Frequency channel assignments, transmit power, modulation, coding,
and symbol rate for each link, both direct path and micro route,
are dynamically optimized in the Cloud to maximize network
capacity. Each node transmits probe packets to each of its neighbor
nodes that can be n layers deep using a synchronous scheme. During
a time interval know to its neighbors, the node transmits probe
packets in various directions with a known pattern. The neighbor
nodes listen for each of these transmissions in various directions,
and record the received channel measurements. These measurements
are periodically uploaded to the Cloud and processed. The
processing identifies the viable micro routes and determines the
range of link parameters available for each. This processing takes
into account the received signal strength of the probe packets in
each receive direction for each transmit direction, It also takes
account of the reverse measurements, those made by the other node
with its receive direction pointed in the previous transmit
direction and with first nodes transmit direction pointed in the
direction of the previous receive direction. Data is processed over
time to identify static routes, those that are available over long
periods of time, and periodic routes, those that are repeatedly
available at certain times of day.
The received signal strength data collected by each unit is sent to
the Cloud server for processing. This data consists of transmit
angles, which in one embodiment of the invention are represented by
beamforming parameters, and receive angles, which in the same
embodiment of the invention are represented by beamforming
parameters, and received signal transmit power.
A data processing function in the Cloud processes the data to
identify micro-routes, reflected paths and interference levels
between units. In an alternate embodiment of the invention, the
processing is performed in each unit. In another alternate
embodiment, the processing is performed in selected units. For each
micro-route, the Cloud processor determines a set of signal
parameters to be used for that route. These parameters are the
transmit power level, beam pointing/forming coefficients plus
modulation and coding. In one embodiment of this invention,
transmit constellation pre-distortion parameters are included in
the signal parameter set.
The RF mapping function is performed every 60 seconds. In alternate
embodiments of this invention, it is performed at different rates.
In one alternate embodiment, it is performed whenever capacity
utilization is low. The RF mapping data is collected incrementally,
distributed over time in different sections of the network. In
another embodiment of the invention, the two units at the end
points of a micro-route negotiate evaluations of beam pointing
perturbations to optimize performance over time.
Meteorological data (weather forecasts) of rain and wind storms is
used to identify phenomena, which might impact RF link performance.
When a link degrades due to rain, the meteorological data is used
to predict the motion of the rain microcell, These predictions are
used to route traffic around the rain microcell to accommodate the
reduced link capacity.
In high wind conditions, or when the structural mount is flexible,
the beams are widened to maintain lock when the antennas are moved
by the wind. To compensate for the widened, lower gain beams, the
Cloud also reduces the data rate on these links. Wind direction is
used by the Cloud to anticipate the need for beam widening.
Coarse beam parameters are computed on the server. These are
geometric in nature and downloaded to the unit. Further the server
can also compute perturbations on these parameters that the unit
can try and then categorize by performance.
The Next Generation Network mitigates external interference is
several ways:
1. By changing frequency channel
2. By using a reroute (route diversity) to avoid an interfered
link
3. 13u using a micro-route to "look away" from the interference
4. By using a spatial interference canceller
5. By using a spatial interference canceller and a micro-route if
the interference is along the original path or if additional
interference suppression is required
6. By using adaptive modulation and coding
7. By using adaptive modulation and coding with any of the other
techniques
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 shows a topology of the next generation data network, in
accordance with one embodiment of the present invention.
FIG. 2 shows the deployment of the distribution nodes (DNs), client
nodes (CNs), and a cloud controller (CC) in the next generation
data network, in accordance with one embodiment of the present
invention.
FIG. 3 shows the four sectors of a distribution node, in accordance
with one embodiment of the present invention.
FIG. 4 shows the next generation data network split into subnets
each associated with a subset of fiber connected nodes, in
accordance with one embodiment of the present invention.
FIG. 5 shows a transmit/receive exception pair characterized by the
RF map function as an undesirable path in the next generation data
network, in accordance with one embodiment of the present
invention.
FIG. 6 shows a micro route around a physical or interference
blockage in the next generation data network, in accordance with
one embodiment of the present invention.
FIG. 7 shows a re-route around a physical or interference blockage
in the next generation data network, in accordance with one
embodiment of the present invention.
FIG. 8 shows interference suppression using a micro route in the
next generation data network, in accordance with one embodiment of
the present invention.
FIG. 9 shows the beamforming characteristics of a spatial
interference canceller used in the next generation data network, in
accordance with one embodiment of the present invention.
FIG. 10 shows packet switched beams transmitted by a distribution
node of the next generation data network, in accordance with one
embodiment of the present invention.
FIG. 11 shows the block diagram of the four sectors of a
distribution node of the next generation data network, in
accordance with one embodiment of the present invention.
FIG. 12 shows using beamforming to maximize the coverage region of
the side lobes for communication in the next generation data
network, in accordance with one embodiment of the present
invention.
FIG. 13 shows the elements of the antenna arrays of a sector of a
distribution node or a client node in the next generation data
network, in accordance with one embodiment of the present
invention.
FIG. 14 shows the block diagram of a sector of a distribution node
of the next generation data network, in accordance with one
embodiment of the present invention.
FIG. 15 shows a bus interconnection between the sectors and fiber
1/0 in a distribution node of the next generation data network, in
accordance with one embodiment of the present invention.
FIG. 16 shows characterization of the RF environment for reflection
using RF maps in the next generation data network, in accordance
with one embodiment of the present invention.
FIG. 17 shows data collection of transmit angels, receive angles,
and received power from the transmitter and receivers of a next
generation data network for generating RF maps, in accordance with
one embodiment of the present invention.
FIG. 18 shows prediction of rain microcell to reroute traffic
around the rain microcell in the next generation data network, in
accordance with one embodiment of the present invention.
FIG. 19 shows beam widening to maintain lock on a particular link
of the next generation data network, in accordance with one
embodiment of the present invention.
DETAILED DESCRIPTION
The Next Generation Data Networks topology is shown in FIG. 1. The
network 100 (FIG. 2) consists of Distribution Nodes (DNs), Client
Nodes (CNs), and a Cloud Controller (CC), The Distribution Nodes
(FIG. 3) may connect to a fiber point of presence to get or send
data from the "cloud", The distribution nodes can talk with other
distribution nodes and client nodes, The DN has one to four sectors
302, 304, 306, 308. The Client Nodes have one or two sectors. The
Cloud Controller manages routing and network performance analysis.
A network may have multiple fiber connected nodes that can be used
for redundancy and/or to distribute traffic entry/exit points,
These networks can be further split into subnets 402, 404 each
associated with a subset of fiber connected nodes (FIG. 4). These
subnets are time synchronized to minimize interference and edge
effects between the subnets. Frequency channels may also be managed
between these subnets to minimize interference between the
subnets.
The Cloud Controller computes all of the routes from each
Distribution Node to each of the Client Nodes and generates routing
tables for each Distribution Node to/from each of its Client Nodes.
These routing tables are downloaded into the nodes. The tables tell
each node how to route a packet to its destination. Each node has
its own MAC address. The cloud has a bird's eye view of the network
as it collects statistics on each link to characterize it. These
statistics are (but not restricted to) packet loss, obstructions
and signal attenuation, structure rigidity, available of single or
multiple micro routes. Using this data it computes predicted
probability of packet delivery for each MAC address serviced by
that DN. Another option is for the CC function to download all
routes to the fiber connected DNs, and to each DN--incremental
routes to destination MAC addresses and micro routes relevant to
that DN. An example of the schedule is:
Macro Routing (Once/10 Sec)
Cloud computes all possible routes between fiber nodes and MAC
addresses;
Uplink & downlink;
Cloud Ranks these routes;
Routes are weighted with link quality, speed, time of day, and
traffic congestion;
For each MAC address we have primary and several alternate routes
that are pre-computed with a cost function;
Cloud refreshes ranking--no faster than once every 10 seconds;
Refresh triggered by a substantial change in link quality;
Refresh includes transmit parameters of links;
Route probe commands;
The cloud keeps alternate routes alive with pings and pre-scheduled
slots.
Micro Routing (Once/Hr.)
Cloud refreshes micro routes & ranking every hour based on RF
map updates & Route Probes.
Exception Pairs (Once/Hr.)
Exception transmit receive pairs for SFNs are recomputed every
hour.
The other functions performed by the cloud controller is creation
of RF Maps, management and command of data collection by nodes,
analyses of link performance data collected by the nodes,
determination of transmit power levels for the nodes and clients
that are dependent on the destination of the packet. The cloud
controller also performs management of the single frequency
network, virtual networks, sub nets, and coexistence with other
networks. The cloud controller may also manage interference at the
node level or have the fiber connected node and the node itself
manage these functions depending on timeliness of a response from
the cloud controller in response to changing conditions.
When a fiber connected node receives a packet, either from the
fiber for a Distribution node, or from a client for any node, it
finds the destination MAC address in its routing table, and appends
the routing header specified in the table to that packet. The
packet is then transmitted to the next node in the header. The
header entry tells the node which sector and beam number in that
sector to use. Prior to transmission the sending node strips the
header entry it just used from the packet to expose the next entry
which will be used by the receiving node.
To implement load balancing, the Cloud Controller includes two, or
more, entries in the routing table for a given destination node.
Each entry has an assigned probability. The sum of the
probabilities for a given destination is always one. Thus if there
is only one entry, the assigned probability value is 1. If there
are more than two entries for a given destination, the sending node
generates a random value between 0 and I. If the value is less than
the probability assigned to the first entry, that entry is used. If
not, the value is compared to the sum of the probabilities assigned
to the first two entries. If the value is less than this sum, the
second entry is used. If there are more than two entries, this
procedure is repeated until the packet is sent. Further, the rules
or cost function used for routing can consist of (but not
restricted to) No exception routing pairs (SFN)
For SFN operation we create transmit and receive exception pairs
(FIG. 5) derived by the RF Maps function. That is, if a transmitter
is sending a packet to a client/DN with a specific beam type (main
or micro route), that may interfere with other units. We ensure if
these units are receiving at that time that their main beams are
not pointed in the interference direction. This can be achieved in
two ways one is leave the receive slot empty or option 2 (the
preferred option) is to order the packets so that the receiver and
transmitter have their beams occupied in different directions.
Exception pair may also be created to prevent overlapped
transmission beams of two adjacent sectors of the DN from
interfering with one another. Only terminal traffic on low
reliability links
On low reliability links where the net data throughput is low we
may want to restrict traffic over those links to traffic where the
destination MAC addresses are only reachable by going over those
links. Further, we leverage the fact that traffic density on a link
decreases exponentially on average as we move away from the fiber
connected node. This gives us excess unused capacity on most links
that are I or more hops away from the fiber connected node. Lower
Modulation/higher error coding on low reliability links
We can further enhance the performance of these links by slowing
down the payload rate to ensure timely packet delivery by reducing
the modulation complexity (qam16 to qpsk for example) for example
and/or increase the error coding (Rate 3/4 to rate 1/2 code for
example). Lower modulation on sparse data traffic links
On links with sparse data that is a lot of unused capacity we can
reduce the modulation and increase the error coding to achieve a
higher reliability of packet delivery. Double packet routes of
trunk data over lossy links
High priority packets and "trunk" data (that is data that needs to
be forwarded on) can be sent over multiple routes simultaneously.
Further large packets can be broken down into smaller packets as
that may preserve the integrity of the packets that are being
received from different directions. maximization of probability of
packet delivery
The above mentioned technique may be used in addition to algorithm
choosing links for the route that maximize the probability of
packet delivery, The fiber connected node and the cloud routing
& processing function are compiling statistics on each link
that are being used to predict future performance of each link. A
Minimization of hops
If the probability of packet delivery is the same on two routes,
and there is no congestion, the route with the lower number of hops
will be chosen.
The Next Generation Data Network 100 implements two forms of route
adjustment. The network topology allows packets to be routed
between two nodes via at least two spatially independent paths 702,
704. This provides load balancing, so that when one path becomes
congested or degraded, traffic can be routed around it. It also
mitigates the effects of external interference. The second form of
route adjustment is "micro-routes" 602. Rather than pointing the
receive antenna at the transmitter, or pointing the transmit
antenna at the receiver, this invention takes advantage of
multipath to use indirect (non-line-of-sight) paths. The ability to
use these paths provides several advantages. One is interference
avoidance. Any interference that was aligned with the main beam is
mitigated by pointing away from it. Another is obstacle avoidance.
The micro-route 602 can be used to mitigate obstacles, such as
trees, signs, trucks, or similar objects that block the direct
line-of-sight path.
Frequency channel assignments, beam forming coefficients, transmit
power, modulation, coding, and symbol rate for each link, both
direct path and micro-rout; are dynamically optimized by the Cloud
Controller to maximize network capacity. The two nodes have the
option of further optimizing the cloud computed beam parameters to
include multipath effects, unit misalignment, calibration &
temperature dependent errors, etc.
Each node transmits probe packets to each of its four neighbor
nodes using a synchronous scheme. During a time interval know to
its neighbors, the node transmits probe packets in various
directions with a known pattern. The neighbor nodes listen for each
of these transmissions in various directions, and record the
received channel measurements. These measurements are periodically
uploaded to the Cloud Processor and processed. The processing
identifies the viable micro-routes and determines the range of link
parameters available for each. This processing takes into account
the received signal strength of the probe packets in each receive
direction for each transmit direction. It also takes account of the
reverse measurements, those made by the first node with its receive
direction pointed in the previous transmit direction and with
second nodes transmit direction pointed in the direction of the
previous receive direction. Data is processed over time to identify
static routes, those that are available over long periods of time,
and periodic routes, those that are repeatedly available at certain
times of day.
To mitigate the impact of lossy links, retransmissions are used.
The receiving node is capable of receiving fragments of a packet
over time on the same link or distributed over other links and
reassembling them. When lossy links are detected, the sending node
fragments the packet and sends copies of fragments using different
routes to achieve route diversity and increase the probability of
packet delivery. The node can tradeoff the losses between all of
the entries in the routing table for a given destination node,
including the direct-route and a micro-route. If the losses on the
micro-route are lower it may choose to use the micro-route for
packet delivery.
For a link that is unresponsive, due to a physical blockage or
radio interference, on the path, the transmit node tries to
establish communication on a "micro-route". It may try multiple
micro-routes. If that fails it returns the packet (or packet
number) to the last unit (DN.sub.n-1 unit) that sent it.
For rerouting, FIGS. 6 and 7, the node has a list of alternate
routes 702, 704 for each destination node pre-computed by the Cloud
Controller. The node modifies the routing header using one of these
and retransmits the packet. It is entirely possible that the packet
(or packet identifier) may retrace several steps before it gets on
a new route.
Further, this unit deletes routes that contain the failed route
from its list. This is also done at the fiber connected node and
all other nodes in the network. Only the cloud computation can
reestablish this route. The deletion can be done based on
persistence or on just one occurrence of failure.
All communication failures, link SNR etc. are communicated back to
the fiber node and the cloud.
Each sector of the node is equipped with an FFT, which runs over
the entire spectrum creating a power spectral density map or a
"spectrum analyzer". This data is used by the Cloud Controller to
select the frequency of the link. The transmit and receive
frequencies can be different and are determined by the interference
at the receiver rather than at the transmitter. Further each sector
of the node can operate on a different frequency.
For each fiber point or broadband point of presence (a high
bandwidth link for taking and bringing data from carrier/internet)
and each destination MAC address on the network, the Cloud
pre-computes the possible routes with a cost function. The net of
the cost function is characterized in data rate, delay, and
reliability of packet delivery. It also takes into account the
availability of multiple routes between two units using micro
routes.
Once a unit determines it cannot communicate on its primary path it
utilizes pre-stored micro routes or an alternate path computed by
the Cloud. If these fail it sends the packet back to the
DN.sub.n-1. DN.sub.n-1 has a list of pre-computed routes for a
destination mac address. DN.sub.n-1 replaces the packet routing
header with one of the pre-computed routes 704 that does not
utilize a "failed" route 702.
The fiber connected node and the server are informed of the failed
route or the use of micro-routes and any other route anomalies.
They are also given information on links that are operational on
signal level, signal headroom, fading margin etc.
The Cloud computes all routes from the Distribution Node to the
destination node. These are downloaded into the fiber connected
unit. In an alternate embodiment of the invention, they are
downloaded into an auxiliary units attached to the fiber connected
unit. When the fiber connected unit receives a packet for a MAC
address it adds the routing header on it, and sends it to the
appropriate adjacent unit. The routing header tells a unit as to
which sector to transmit the packet, and the beam "number" on that
sector. The unit strips the parameters from the route header
exposing the next one for the receiving unit. The fiber connected
unit will round robin through equal cost or near equal cost routes
for load balance on the network.
If a communications failure occurs, the node first retransmits the
packet. If that fails, it tries a micro-route or an alternate route
computed by the Cloud. If these fail, it returns the packet to the
last unit (DN.sub.n-1 unit) that sent it. The DN.sub.n-1 unit has a
list of alternate routes for each destination node, pre-computed by
the Cloud Controller and downloaded to that unit. It modifies the
routing header using one of these and retransmits the packet. This
process is repeated until the packet is either returned to the
Distribution Node, or it is delivered. If it is returned to the
Distribution Node, that node resends it on a different path.
When a failure occurs, the sending unit may delete the failed
primary path, the alternate paths, and/or the micro-route from its
routing table, and propagates this information to the other nodes
in the network, including the fiber connected node. The sending
unit may also restrict the use of the primary path, certain
alternate paths, and/or the micro-route between the updating of the
routing table by the Cloud. The fiber connected node reports this
information to the Cloud. Only the Cloud processing can reestablish
this route. In an alternate embodiment, instead of deleting a
micro-route based on a single failure, a failure counter is
maintained for each micro-route, and only when a predefined
threshold is exceeded, is the micro-route deleted.
The means of detecting a static reflector are to collect reflection
data at different times of day or days of week or month or year. If
the reflected path appears in all of them accounting for the
variance of beam pointing errors, it is deemed to be a static
reflector. Dynamic reflectors that have a known periodicity may
also be used but as a function of that periodicity.
By using a micro-route, rather than the direct path, the Next
Generation Network changes the arrival angle of the signal at the
receiver. This allows the network to maximize the signal to
interference ratio at the receiver. For example, typical side-lobe
to main-lobe gain is -13 dB, and a typical micro-route loss is 3
dB. In this case, the improvement in C/I is 10 dB. (FIG. 8)
Micro Route+Modulation
In this case we use the microroute and reduce the modulation &
effective data rate on the link. For example if we increased the
margin by 6 dB from modulation-data rate then our effective margin
over the interferer is 16 dB.
Micro Route+Interference Cancellation
We use a spatial interference canceller (FIG. 9). The canceller
does an "inverse beam former" or creates a null in a direction. We
have shown that these nulls maybe as deep at 28 dB over and above
antenna isolation. In this case we have an effective margin of 38
dB over the interference.
Micro Route+Interference Cancel+Modulation
In this case if we had a 6 dB advantage from modulation-data rate
our effective margin is now 44 dB.
Single Frequency Networks
We enable the complete network to be run on a single frequency
channel rather than alternating frequencies. This enables the most
efficient usage of the frequency spectrum. We achieve this via RF
Maps. Using the RF Maps we
1. Compute Power levels for the unit to transmit a packet (knowing
its destination). Computed power levels reflect the real world
power that is required to close the link at a desired
reliability/availability level. It is important not to transmit at
max power where we can use lower power to minimize self
interference in the network.
2. Beam pointing coefficients coordinated with the packet
transmission sequence across exception pair links. This eliminates
the "exception pairs" generated by the RF Maps function
3. Synchronization and synchronization offsets for irregular
deployments. In a regular or symmetric deployment alternate nodes
transmit and receive. In an irregular deployment there may be
multiple DNs on a path corresponding to one link on another path
that need to be synchronized.
4. Managing C/I (Carrier to Interference ratio) at nodes via
transmit power, modulation, packet sequence and beam pointing
coefficients. The C/I is managed so that the packet can be
delivered with a reliability level that has been guaranteed to the
user.
5. Use 3D RF maps to compute off axis self interference
combinations
a. Auto measure sidelobe performance;
b. Utilize the self interference cross correlation matrix to
eliminate transmit receive combinations (beam weights);
c. Achieved via packet scheduling.
Virtual Networks
Multiple virtual networks can be created over the same hardware
links. These networks can each be assigned data bandwidth at the
fiber node(s). The reason is that the fiber node determines total
throughput of the network. Further, we can overbook each network if
required using statistics that are available historically and that
we have collected on the nature of the burstiness of the data. This
will allow us to allocate bandwidth dependent on the guaranteed
level of service for each virtual Network.
Network Coexistence
Multiple Operators may plan to use our equipment in the same area,
and maybe on the same poles. Using communication between our cloud
controllers we can manage the frequency, the synchronization of
transmit and receive slots to minimize interference and maximize
throughput. Further we can also coordinate packet sequencing
between these networks to maximize antenna isolation both from
beamforming and polarization. The SFN is key to making these
networks operate as it increases the degrees of freedom that we
have to operate both in frequency and/or polarization.
Network and SubNet Synchronization & Security
The network uses two levels of synchronization. Coarse synch using
GPS to a nominal of 100 nanoseconds and a fine synch that using
signaling between units. Sub nets are synchronized in the cloud and
their transmit, receive, and beam pointing along the edges of
subnets is coordinated and synchronized. Further subnet
coordination also utilizes the sparse data or low data densities of
the links at the periphery of each subnet to maximize data traffic
in the core of each subnet. The core is defined as the fiber DN and
the first hop DNs. Security leverages on the delays between units
and time of travel between units. Using this as a key we "open" the
packets only at the destination. Further due to the assignment of
different routes along which the packet may travel, assigned at the
fiber attached node the key is randomized. Further error bounds are
placed to account for retransmits that maybe encountered along the
way. Alternatively we can add "incremental" keys in each DN to
account for retransmits.
Distribution Node (FIG. 3)
Describes nodes in a millimeter wave multi-hop network that provide
high data rates (of the order of multiple Gigabits per second),
flexible deployment (not requiring manual aiming of antennas) and
robustness to multipath fading. FIG. 3 shows a node with 4 faces or
sectors 302, 304, 306, 308. All sectors transmit and receive at the
same time. Each sector has a packet switched beam. That is the
beamforming coefficients are applied to enable the sector to point
the beam at the client or receiver of the packet to be transmitted.
Further, the beam 1002 is then switched to point (FIG. 10) in the
direction 1004 of where the next packet needs to be sent. Each
sector has a table of MAC or IP addresses and beamforming
coefficients that the sector is authorized to communicate with.
There may be multiple sets of beamforming coefficients for the main
beam or a range assigned to each coefficient. Micro route
beamforming coefficients are also included in this table. All 4
sectors are synchronized, one sector is the master and the other 3
sectors are the slaves (FIG. 11). All sectors transmit OFDM
signals. However, the system can work with single carrier
signals
The nodes can perform adaptive transmit and receive beamforming,
and provide omnidirectional coverage as well as high antenna
directivity, That is, each node can communicate with neighbors in
any direction of its choosing in a 360 degree field of view, while
being able to synthesize a highly directive beam in the direction
of the node that it is communicating with at a given time. Link
robustness is achieved by providing diversity against fading, which
can occur due to multipath reflections from surfaces such as the
ground, building walls, or vehicles. The throughput available at
each node is increased by allowing for multiple simultaneous links
with different neighbors.
The reason for multi-hop/mesh is that it permits us to "look"
around corners/buildings and extend the distance we cover. By
having multiple routes to the destination we also increase the
effective availability/reliability of the network.
There are two node types, distribution nodes (DNs) and a client
node (CNs). A distribution node has up to four sectors, each
covering 6 degrees.times.90 degrees (we can change this coverage
for 2D beamforming cases), The fundamental beam is approximately 6
degrees.times.3 degrees and is beam formed to sweep over the
complete angle. Each sector has a beam that can be pointed +/-45
degree. Further, we can reduce the coverage area but utilize the
sidelobes to communicate with the close in clients who maybe on the
extremities. For example (FIG. 12), we can reduce the actual
antenna coverage to 6 degrees.times.45 degrees, and use the
beamforming to maximize the coverage region (that is maximize the
side lobes rather than main lobe). That is clients in the 22.5
degrees on either side of the coverage region are communicated to
by the sidelobes. These links can be closed at a lower transmit
EIPR as the clients are closer in and/or at a lower data rate. This
enhances the link for the "trunk" connections. These nodes are
reconfigurable for other angular coverage, which can include beam
forming in elevation in addition to azimuth.
In an alternate embodiment, a two dimensional (2D) sweep is used.
This 2D beam forming has an n.times.m degree beam that can be
steered vertically in elevation and horizontally in azimuth. This
embodiment is used for building top to building top as buildings
are at different heights. It is also used to illuminate the side of
a building from the street or top of another building.
The antenna array has 32 elements, each 6 degree by 90 degree (FIG.
13). In alternate embodiments, it may have 16, 12 or any other
number of elements. There are two such arrays per sector. On
transmit, both arrays are used with an Alamouti code that permits
mitigating multipath effects and increases the transmit power via
combining. On receive, both arrays are used with MRC combining.
A block diagram of the sector is shown in FIG. 14. It consists of
the antenna arrays, which feed into the beamforming chips. These
chips can be n element chips for simplicity we describe a 32
element beamformer. These beamformer chips use the coefficients for
a packet on transmit or receive. We assume a single
transmit/receive chip for each antenna array. We can have a
separate transmit and receive chip with a switch or separate arrays
for transmit and receive. These chips can output/input the combined
RE signal at baseband or an IF frequency. This signal is
modulated/demodulated by the communication processor which filters,
combines signals from the two antennas for receive or generates two
signals on transmit. It also has a QAM/QPSK mod/demod function with
error coding. Other functions are shown in the FIG. 14 as an
example. The MAC function is part of this processor it can be in
the baseband chip or a separate FPGA. Further Mac filtering takes
place that is the routing header is looked at to determine where it
goes and is sent to the appropriate sector directly or via the
primary sector. We can use the 100 bus as the interconnect bus or
multiple 10 buses or some other digital bus between the sectors.
Connection to fiber 1/0 is shown in FIG. 15.
The multipath propagation characteristics for a highly directive mm
wave link are quite sparse. Spatial diversity is provided by using
multiple transmit and/or receive arrays offset in the horizontal
and vertical directions. The horizontal offset provides diversity
against wall reflections, while the vertical offset provides
diversity against ground reflections. The amount of offset is
chosen based on typical link ranges and typical distances from
scattering surfaces. Thus, each receive antenna array would
generate a single mm wave signal. For diversity combining of
signals from multiple receive arrays, these signals can be further
combined by adjusting gain and phase (e.g., based on a maximal
ratio combining strategy), or one of the signals can be selected
(e.g., based on amplitude or power). This can then be sent to the
single channel chipset.
Each node has a centralized controller that routes packets to and
from the appropriate faces. Isolation between the radio frequency
(RF) circuits for different faces is sufficient that all faces can
simultaneously transmit, or simultaneously receive. By designing
higher layer protocols appropriately, the need for a face to
transmit while another face is receiving can be avoided, thus
greatly simplifying the isolation requirements.
An additional means of increasing data rate and interference
rejection could be to use polarization coding and reverse polarize
the two antennas in the sector. We could take this approach for
doubling the effective throughput 1:0 from the unit.
In one embodiment, output from the unit is GigE, SynchE; power into
the unit is 48V DC, 110 VAC, 240 VAC; and interconnects between the
sectors is via a multiple gigabit Ethernet ports or a single 100
port.
Other Functions and Components in the System
1. 3D RF Maps
We need to characterize the RF environment for reflections (FIG.
16), interference (FIG. 5), and link losses. Characterization is
done using probe packets. While we discuss a two dimensional case,
the maps are generalized for three directions. With vertical
scanning (or elevation scanning on the beam) we can characterize
the reflectors, interference and side lobes in three dimensions.
For simplicity of understanding we discuss a two dimensional
case.
To do this we start with a transmit beam on unit A 1702 and receive
on all "surrounding" units 1704, 1706, 1708. The number or depth of
surrounding units is based on the propagation losses. Data
collection is performed as follows (see FIG. 17).
Unit A1 1702 transmits at angle i. All units 1704, 1706, 1708
receive at angle j. And then at j+1, j+2, . . . n;
Unit A1 1702 then transmits at angle i+1, units receive at j, j+1,
. . . n;
Unit A1 transmits at angle m, all units receive at j, j+1, . . .
n;
Unit A2 transmits in the same sequence as A1 (above), all units
receive the A2 signal at j, j+1, . . . n;
Unit Ak 1710 transmits at angle m, all units receive the Ak signal
at j, j+1, . . . n.
The data collected on transmit receive are transmitted to the
server in the cloud. The data consists of transmit angle or
beamforming parameters and receive angle or beamforming parameters,
received signal transmit power, multipath parameters if any.
Note transmit and receive signals are shown as "geometric" for
simplicity of explanation; however these beams may be "amoeba
shaped". For example, amoeba shaped beams may be constructed from a
combination of geometric beams from the multiple antenna elements
(e.g., 32) of the antenna array. The amoeba shaped beams may be
used to increase the probability of packet reception or to increase
the date rate via independent paths. In one embodiment, amoeba
shaped beams may be created between two nodes independent of the
Cloud.
The data analytics function in the server or super unit or possibly
in each unit, sorts through the data to compute reflected paths and
interference between units. For each of these a signal power level
is associated, a modulation parametric set is associated which may
include distortion of the QAM constellation etc.
This data collection exercise can be performed on a periodic basis
or ad hoc. The data collected can be incremental, that is we do not
have to collect all data in one contiguous set but can be
distributed over time. Further we will re-explore the reflected
paths periodically, further the two units using the reflected path
may further optimize beam parameters between them to optimize
communication.
Whenever there is no traffic or periodically the units are set to
scan one transmitting and one or several receiving. We correlate
the transmit power and "angle" with what receivers see again,
received power and angle. The angles can be in azimuth and
elevation.
To make a single frequency network we use the RF Maps to pin point
interference between cells. As both "cells" have beam forming we
create "packet exclusions," that is if a packet is being sent to a
client then the interfered node will not look (receive/transmit) in
that direction while this operation is in progress. RF Roads are
angular Transmit--receive combinations. Discover RF roads between
units using the scanning beams; RF Roads have data speed,
reliability, and exclusion zones; For desirable roads--permanent
reflectors are sourced by collecting data repeatedly over time.
Weather & Environment Tool
Using Met data we are aware or rain & wind storms 1802 that may
degrade the performance of our links. When we see a link degrade
due to rain we can predict the motion of the rain microcell via met
data (wind direction & speed). This prediction is used to route
traffic around the rain microcell and link capacities in the rain
micro cell will be reduced (FIG. 18).
For wind we collect data on degradation of the beam--that is we may
have to widen a beam to maintain lock on a particular link. We can
use this data that we have collected historically, to predict
effects in a wind storm which will require that we predict and
widen the beam 1902, 1904 (FIG. 19), and reduce the data rate to
maintain the link budget. Further we can use wind direction in the
storm to predict specifics of beam parameters and how they are
affected. (Beam may only need to be widened for particular wind
directions).
3. Beam Parameter Computation
Coarse beam parameters are computed on the server. These are
geometric in nature and downloaded to the unit. Further the server
can also compute perturbations on these parameters that the unit
can try and then categorize by performance. Initial beams maybe
computed using the known GPS locations of the two end of the link
and approximate direction of the sector face. By using multiple
measurements to various destinations that the sector can
communicate with, the Cloud Controller can compute the "nominal"
direction of the sector (that is at 0,0).
When a new unit is added to the network its geographic location is
entered into the provisioning system. The appropriate DNs and their
appropriate sectors (using GPS data) will look for the new unit.
The new unit is in receive & scan mode unit it acquires the
invitation to join the network from a DN. AES keys maybe exchanged
before it is permitted to enter the network. Further, it will
receive the definition of transmit slots, etc., from the DNs.
The perturbations can be for enhanced performance for multipath
(reflectors have been characterized in RF Maps) or for interference
cancellation, or both. The interference cancellation nulls can be
pre-computed based on beam directions and cancellation nulls in
other directions. Perturbations for antenna imperfections are also
taken into account and calibrated in the Cloud Controller. This is
similar to the process to calibrate misalignment or the mounting
angle of the sector.
Transmit or receive beamforming can be performed based on any of a
number of well-known mechanisms, including beamforming at radio
frequency (RF) or intermediate frequency (IF) by controlling the
relative gains and/or phases of each element, or beamforming in
complex baseband by controlling the complex gains of the baseband
signal to/from each element for transmit/receive beamforming.
The beamforming and diversity functionalities can be modularized
and implemented in a number of ways. As one example, sophisticated
integrated circuits developed for short range (e.g., indoor)
applications can be leveraged for the longer range outdoor
applications considered in this disclosure. As FIG. 14 show, a
single channel chipset that handles up/down conversion, baseband
processing, and link layer/medium access protocols, can be used for
each face. Alternatively, Beamforming chipsets customized for the
outdoor application can be layered on top of single channel RF
up/downconvertor chips. In order to control line losses, it is
advantageous to place a beamforming integrated circuit (IC) close
to the antenna array that it is controlling. For transmission, a
transmit beamforming IC would take the mm wave signal from the
single channel chipset. replicate the signal for each transmit
element, provide power amplification, and modulate the gain and
phase to beamform in the appropriate direction. The amount of power
amplification would be set so as to adhere to regulatory guidelines
on radiated power, while overcoming line and coupling losses from
the single channel chipset to the antenna elements. For reception,
a receive beamforming IC would provide low noise amplification as
close to the antenna elements as possible (so as to improve the
overall noise figure), while adjusting the gain and/or phase of the
received signal at each element before summing these signals to
implement receive beamforming.
4. Routing Tool
For each fiber point or broadband point of presence (a high
bandwidth link for taking and bringing data from carrier/internet)
and each destination MAC address on our network, we pre-compute the
possible routes with a cost function. The net of the cost function
is characterized in data rate, delay, and reliability of packet
delivery. It also takes into account the availability of multiple
routes between two units using micro routes.
Further, for rerouting/routing failures, once a unit determines it
cannot communicate on its primary path it utilizes pre-stored micro
routes or an alternate path from the routing table. if these fail
it sends the packet back to the DN.sub.n-1. DN.sub.n-1 has a list
of pre-computed routes for a destination mac address. DN.sub.n-1
replaces the packet routing header with one of the pre-computed
routes that does not utilize a "failed" route.
The fiber connected node and the server are informed of the failed
route or the use of microroutes and any other route anomalies. They
are also given information on links that are operational on signal
level, signal headroom, fading margin etc.
Routing is computed based on RF parameters/statistics of each link
and traffic on the link, to maximize probability of packet delivery
at its destination. The routing tool can also order increased time
coding of packets for error recovery, usually applied to high
priority/critical packets and also for lossy links, For
destinations that can only be reached via excessively lossy links
the routing tool may order two or more copies of the packet to be
sent on distinct routes, where the receiving client has the
responsibility to reconstruct the original packet from error
corrected fragments of the original packet. Further for excessively
lossy links the routing tool may order a large packet be broken
down into smaller sub packets.
Routing header may include:
Route number, sector number, beam number, power to transmit at,
modulation and error correction parameters, number of bits;
Route number+1, sector number, . . .
. . .
Ethernet port address;
Data;
. . .
Data.
5. Micro Route;
Micro-route is a reflected route, pre-computed in the cloud using
"RF Maps" The parameters (beam angle, modulation, coding, tx power,
. . . ) for these routes are downloaded to the unit and then
fine-tuned by the unit. Micro routes utilize "static reflectors"
who properties are known as a time of day or are static over all
time.
The means of detecting a static reflector are to collect reflection
data at different times of day or days of week of month or year. If
the reflected path appears in all of them accounting for the
variance of beam pointing errors, it is deemed to be a static
reflector. Dynamic reflectors that have a known periodicity may
also be used but as a function of that periodicity,
Micro route information also includes beam parameters, data rate,
modulation, error correction and other parameters to let the units
know how to close the link at a required reliability level.
Multiple micro routes between two units can be downloaded and
prioritized.
The other usage for micro routes is for interference management. By
changing the angle of arrival of the signal it can present a side
lobe of the antenna gain pattern to the interference. Micro routes
are periodically tested along with all other routes by the Cloud
Controller.
* * * * *