Method and device for establishing communication links between mobile communication systems

[0001] This invention was made with Government support under Contract Number N00014-96-C-2063 awarded by the Naval Research Laboratory. The Government has certain rights in this invention.

FIELD OF THE INVENTION

[0002] The present invention relates to the field of communications, and more particularly, to a network of mobile communication systems operating with directional antennas.

BACKGROUND OF THE INVENTION

[0003] Time division multiple access (TDMA) is one example of an access scheme used for establishing communication links between wireless mobile communication systems. Communication links between the wireless mobile communication systems are established within a series of time frames. Each time frame is divided into time slots, with each wireless mobile communication system being assigned at least one time slot.

[0004] An omni-directional antenna is typically used by a wireless mobile communication system so that information transmitted by one mobile communication system is received by all the other mobile communication systems. When the mobile communication systems are operating at a fixed frequency, they must take turns transmitting within their respective time slots to prevent channel interference.

[0005] To improve quality of a communications link between two wireless communication systems, a directional antenna may be used. The directional antenna provides an increased antenna gain in a desired area that is limited in coverage while decreasing the antenna gain towards the remaining area.

[0006] U.S. Pat. No. 5,767,807 to Pritchett discloses phased array antennas being used for establishing communication links within a network of wireless communication systems. The phased array antenna includes parasitic elements for selectively controlling the antenna pattern. The phased array antenna radiates an omni-directional signal when all of the parasitic elements are in a high impedance state, and radiates a directional signal when a selected number of parasitic elements are placed in a lower impedance state in response to switching circuits.

[0007] More particularly, the Pritchett '807 patent discloses the acquisition, by a fixed initiating wireless communication system from a fixed receiving wireless communication system, of a list of the wireless communication systems operating in the network and a corresponding respective time slot list for each wireless communication system. A table is then created based upon the list for scheduling time slots among the wireless communication systems.

[0008] However, there is still a need to efficiently schedule time slots for wireless communication systems operating with directional antennas, particularly when the wireless communication systems are mobile. In such a dynamic network, mobile communication systems are continuously entering into and dropping out of the network.

SUMMARY OF THE INVENTION

[0009] In view of the foregoing background, it is therefore an object of the present invention to schedule time slots in a manner that is responsive to variations in communication link demands for wireless mobile.

[0010] This and other objects, advantages and features in accordance with the present invention are provided by a wireless communication network comprising a plurality of mobile nodes each comprising a transceiver, a directional antenna connected to the transceiver, and a controller connected to the transceiver. The controller preferably schedules a respective semi-permanent time slot for each time frame to establish a communication link with each neighboring mobile node and leaving at least one available time slot in each time frame, and schedules the at least one available time slot to also serve the communication link with a neighboring mobile node based upon link communications demand.

[0011] The controller preferably aims the directional antenna toward each neighboring mobile node during communication therewith. The directional antenna may be a phased array, a dish or horn antennas, for example. The use of directional antennas focuses an RF signal in a desired direction. Consequently, a plurality of communication links may be established within a scheduled semi-permanent time slot, with each communication link including a different pair of neighboring mobile nodes.

[0012] Each time frame may have up to N semi-permanent time slots and at least 2N−1 available time slots. An advantage of limiting the number of semi-permanent time slots simplifies scheduling of the time slots.

[0013] The controller may prioritize the communication links and drop one of the communication links based upon the prioritization for making available a semi-permanent time slot for establishing a communication link with a new neighboring mobile node. In addition, the controller may also prioritize the communication links and schedule the at least one available time slot based upon this prioritization.

[0014] In other words, scheduling of the semi-permanent time slots is done in a distributed fashion. A pair of neighboring mobile nodes in the network is able to agree upon a scheduled semi-permanent time slot without having to communicate with any other mobile nodes. Consequently, there is no single point failure in scheduling semi-permanent time slots throughout the network since any pair of mobile nodes are not relying upon the semi-permanent time slots being assigned between other neighboring nodes.

[0015] The controller may schedule one of the semi-permanent time slots as an available time slot if a number of the communication links is less than N. This advantageously supports communication link demands on an as needed basis for the existing communication links. However, the controller may reschedule the demand assigned time slot back to a semi-permanent time slot if the number of the communication links is again equal to N.

[0016] Each communication link is formed by an initiating mobile node and a receiving mobile node, and the initiating mobile node may transmit a list of available semi-permanent time slots to the receiving mobile node. The receiving mobile node may then transmit selection of one of the semi-permanent time slots to the initiating mobile node. The initiating mobile node may then confirm selection of the selected semi-permanent time slot to the receiving mobile node.

[0017] Each mobile node may further comprise an omni-directional antenna connected to the transceiver for exchanging positional information with other neighboring mobile nodes. In addition, the phased array antenna may simultaneously generate multiple antenna beams, wherein the controller preferably aims the phased array antenna to multiple neighboring mobile nodes within a scheduled semi-permanent time slot.

[0018] Another aspect of the present invention relates to a method for establishing communication links for a plurality of mobile nodes, with each mobile node comprising a transceiver, a phased array antenna connected to the transceiver, and a controller connected to the transceiver. The method preferably comprises for each mobile node scheduling a respective semi-permanent time slot for each time frame to establish a communication link with a neighboring mobile node and leaving at least one available time slot in each time frame.

[0019] The at least one available time slot is preferably scheduled to serve the communication link with a neighboring mobile node based upon link communications demand. The phased array antenna is preferably aimed toward each neighboring mobile node during communication therewith. Each time frame may have up to N semi-permanent time slots and at least 2N−1 available time slots.

[0020] The method may further include having each node prioritize the communication links and drop one of the communication links based upon the prioritization for making available a semi-permanent time slot for establishing a communication link with a new neighboring mobile node. This advantageously allows any mobile node to accommodate variations in communication link demands.

BRIEF DESCRIPTION OF THE DRAWINGS

[0021]FIG. 1 is a diagram illustrating a network of mobile communication systems in accordance with the present invention.

[0022]FIG. 2 is a more detailed block diagram illustrating a pair of wireless mobile communication systems in accordance with the present invention.

[0023]FIG. 3 is a diagram illustrating a frame of time slots in accordance with the present invention.

[0024]FIG. 4 illustrates the scheduling of available time slots to the network diagram illustrated in FIG. 2 in accordance with the present invention.

[0025]FIG. 5 is a top-level state diagram for the scheduling of semi-permanent time slots and available time slots in accordance with the present invention.

[0026]FIG. 6 is a diagram illustrating a semi-permanent time slot scheduling process in accordance with the present invention.

[0027]FIG. 7 is a diagram illustrating a semi-permanent time slot being scheduled for a new communication link in accordance with the present invention.

[0028]FIG. 8 is a diagram illustrating an available time slot scheduling process in accordance with the present invention.

[0029]FIG. 9 is a diagram illustrating an available time slot being added to a communications link in accordance with the present invention.

[0030]FIGS. 10 and 11 are diagrams illustrating a semi-permanent time slot being scheduled for a new communications link based upon multiple simultaneous antenna beams from a phased array antenna in accordance with the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0031] The present invention will now be described more fully hereinafter with reference to the accompanying drawings in which preferred embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout and prime notations are used in alternate embodiments. The dimensions of layers and regions may be exaggerated in the figures for greater clarity.

[0032] Referring initially to FIGS. <b>1</b>-<b>2</b>, a wireless mobile communication network <b>10</b> comprises a plurality of wireless mobile nodes <b>12</b><i>a</i>-<b>12</b><i>h</i>. Each mobile node <b>12</b><i>a</i>-<b>12</b><i>h </i>comprises a transceiver <b>14</b>, a directional antenna <b>16</b> connected to the transceiver, and a controller <b>18</b> connected to the transceiver.

[0033] The controller <b>18</b> includes a semi-permanent time slot unit <b>18</b><i>a </i>for scheduling a respective semi-permanent time slot for each time frame for establishing a communication link with each neighboring mobile node while leaving at least one available time slot in each time frame. An available time slot unit <b>18</b><i>b </i>schedules the at least one available time slot to also serve the communication link with a neighboring mobile node based upon link communications demand. In addition, the controller <b>18</b> includes an antenna aiming unit <b>18</b><i>c </i>for aiming the directional antenna toward each neighboring mobile node during communication therewith.

[0034] The wireless mobile nodes <b>12</b><i>a</i>-<b>12</b><i>h </i>are operating in a mobile environment. These systems may be ground based and/or airborne, whereby they are continuously entering into and dropping out of the network <b>10</b>. The directional antenna <b>16</b> may be a phased array, a dish or horn antennas, for example. Transmission via a directional antenna <b>16</b> enables the RF signal to be focused in a desired direction.

[0035] By selectively controlling the direction of the antenna pattern between a pair of wireless mobile communication systems for establishing a communications link therebetween, additional communication links may be established between other wireless communication systems within the same scheduled semi-permanent time slot. This is illustrated by communication link <b>27</b> operating in time slot 1 between mobile nodes <b>12</b><i>c </i>and <b>12</b><i>e</i>, and communication link <b>29</b> also operating in time slot 1 between mobile nodes <b>12</b><i>a </i>and <b>12</b><i>b</i>, as best illustrated in FIG. 1. This feature of the present invention advantageously allows the resources of the wireless mobile communication network <b>10</b> to be better utilized.

[0036] The controller <b>18</b> limits the number of communication links for each wireless mobile node <b>12</b><i>a</i>-<b>12</b><i>h </i>within each time frame based upon a total number of time slots within the frame. The advantage of limiting the number of communication links to a fraction of the total number of time slots within the time frame significantly simplifies the scheduling of time slots with neighboring nodes.

[0037] The number of communication links for each wireless mobile node <b>12</b><i>a</i>-<b>12</b><i>h </i>within each time frame is less than or equal to N, and the total number of time slots within each frame is greater than or equal to 2N−1. In addition to simplifying the scheduling of time slots, this type of distributed scheduling avoids conflicts.

[0038] Distributed scheduling allows any two pair of wireless mobile nodes, such as <b>12</b><i>a </i>and <b>12</b><i>b</i>, for example, to schedule a semi-permanent time slot without having to communicate with any other wireless mobile node. In other words, there is no centralized master/slave type of coordination with all of the wireless mobile nodes <b>12</b><i>a</i>-<b>12</b><i>h </i>for scheduling the semi-permanent time slots. Since the time slots among the wireless mobile nodes <b>12</b><i>a</i>-<b>12</b><i>h </i>are scheduled in a distributed fashion, there is no single point of failure in the wireless mobile communication network <b>10</b>.

[0039] The controller <b>18</b> may prioritize the communication links and drop one of the communication links based upon the prioritization for making available a semi-permanent time slot for establishing a communication link with a new neighboring mobile node. Prioritization of the communication links will be addressed in greater detail below. In addition, the controller <b>18</b> may also prioritize the communication links and schedule the at least one available time slot based upon this prioritization.

[0040] The controller <b>18</b> may also schedule one of the semi-permanent time slots as an available time slot if a number of the communication links is less than N. This advantageously supports communication link demands on an as needed basis for the existing communication links. However, the controller <b>18</b> may reschedule the demand assigned time slot back to a semi-permanent time slot if the number of the communication links is again equal to N, as will also be discussed in greater detail below.

[0041] Each communication link is formed by an initiating mobile node, such as node <b>12</b><i>a</i>, and a receiving mobile node, such as node <b>12</b><i>b</i>, and the initiating mobile node transmits a list of available semi-permanent time slots to the receiving mobile node. The receiving mobile node <b>12</b><i>b </i>then transmits selection of one of the semi-permanent time slots to the initiating mobile node. The initiating mobile node <b>12</b><i>a </i>then confirms selection of the selected semi-permanent time slot to the receiving mobile node.

[0042] Each mobile node may further comprise an omni-directional antenna <b>20</b> connected to the transceiver <b>14</b> for exchanging positional information with other neighboring mobile nodes. Other information that may be exchanged includes resource requirements and detection of the presence of a potential new neighbor node. In addition, the phased array antenna <b>16</b> may simultaneously generate multiple antenna beams, wherein the controller <b>18</b> aims the phased array antenna to multiple neighboring mobile nodes within a scheduled semi-permanent time slot.

[0043] The method is also directed to a method for establishing communication links for a plurality of mobile nodes <b>12</b><i>a</i>-<b>12</b><i>h</i>, with each mobile node comprising a transceiver <b>14</b>, a phased array antenna <b>16</b> connected to the transceiver, and a controller <b>18</b> connected to the transceiver. The method comprises for each mobile node <b>12</b><i>a</i>-<b>12</b><i>h </i>scheduling a respective semi-permanent time slot for each time frame to establish a communication link with a neighboring mobile node and leaving at least one available time slot in each time frame.

[0044] The at least one available time slot is preferably scheduled to serve the communication link with a neighboring mobile node based upon link communications demand. The phased array antenna <b>16</b> is aimed toward each neighboring mobile node <b>12</b><i>a</i>-<b>12</b><i>h </i>during communication therewith. Each time frame may have up to N semi-permanent time slots and at least 2N−1 available time slots.

[0045] The method further includes having each node prioritize the communication links and drop one of the communication links based upon the prioritization for making available a semi-permanent time slot for establishing a communication link with a new neighboring mobile node. In addition, an available time slot that is currently scheduled to serve a particular communication link may be reassigned to another communication link based on link demand. This advantageously allows any mobile node to accommodate variations in communication link demands.

[0046] Scheduling of the semi-permanent time slots and the available time slots will now be discussed in greater detail. Details on steering the directional antennas <b>16</b> toward a receiving mobile node <b>12</b><i>a</i>-<b>12</b><i>h </i>will be omitted since this feature of the present invention is readily understood by one skilled in the art.

[0047] For purposes of discussion, it will be assumed that the directional antenna <b>16</b> is a phased array antenna. As readily understood by one skilled in the art, a phased array antenna <b>16</b> includes a plurality of antenna elements and respective phase shifters that can be adjusted for producing a steerable antenna beam in a desired direction. The phased array antenna <b>16</b> steers or scans the antenna pattern without physically moving the antenna.

[0048] Also for purposes of discussion, a number of assumptions about the wireless mobile communication network <b>10</b> are made. First, there is a single frequency band that is a high data rate channel that is shared by all the wireless mobile nodes <b>12</b><i>a</i>-<b>12</b><i>h</i>. This type of transmission channel is time shared between all the wireless mobile nodes <b>12</b><i>a</i>-<b>12</b><i>h </i>for both transmit and receive. All transmission slots are scheduled in advance.

[0049] An assumption is also made that a separate low data rate overhead channel is provided. This overhead channel can be used for node discovery, net entry, and exchange of various other data link control overhead information including resource requests. This overhead channel is provided via an omni-directional antenna <b>20</b>. Good global timing reference is also known at all nodes. The terms wireless mobile nodes and wireless mobile communications systems <b>12</b><i>a</i>-<b>12</b><i>h </i>are interchangeable throughout the following discussion.

[0050] The wireless mobile communication network <b>10</b> also includes the capability for locating and tracking mobile nodes so that the phased array antennas <b>16</b> can be pointed accurately when a scheduled time slot is available. As noted above, a detailed discussion on the pointing/tracking will not be provided herein.

[0051] An assumption is also made that the phased array antennas <b>16</b> have zero beamwidth. This assumption will be relaxed later. Consequently, we can assume that a transmission by a given mobile node will be received only by the neighbor mobile node to which it is attempting to transmit. This allows a less restrictive set of constraints on the scheduling of time slots. Each communications link will be labeled with a number which represents a scheduled time slot for transmitting and receiving data therein.

[0052] The constraints are as follows. No node may have more than one communications link labeled with the same time slot number. A given time slot assignment will apply to a half duplex link between two mobile nodes, and be used alternately by the two nodes for transmit and receive. These two constraints imply that a time slot assigned by a mobile node to one of its neighboring nodes is constrained by the previous time slot assigned by that node to other links.

[0053] The scheduling of time slots for the phased array antenna <b>16</b> is illustrated in FIG. 1, which shows a network <b>10</b> with link connectivity based upon scheduled time slots. The time slots are scheduled so that the wireless mobile nodes <b>12</b><i>a</i>-<b>12</b><i>h </i>know when to point their respective phased array antenna <b>16</b> toward a neighboring wireless mobile node.

[0054] The communication links are assumed to be bidirectional and are used in a half duplex fashion where each time slot number represents a time slot and a transmission opportunity in each direction occurring in that time slot. The term N_framewill be used to denote the maximum link index or the maximum number of time slots within a frame. In the case of this example, N_frame=6.

[0055]FIG. 3 illustrates a representative frame of time slots. In the simplest formulation, each epoch or frame has n slots and the value of n is set to N_frame. In the figure we also show how a time slot is used for the link connecting to nodes labeled as nodes A and B. Each time slot is divided into two mini-slots <b>22</b><i>a</i>, <b>22</b><i>b</i>. The first mini-slot <b>22</b><i>a </i>(e.g., half of the time slot) is used for transmissions from node A to B. Then the direction of the link is reversed and the second mini-slot <b>22</b><i>b </i>is used for transmissions from node B to A.

[0056] During the transmission periods, multiple packets can be transmitted. As indicated, each mini-slot <b>22</b><i>a</i>, <b>22</b><i>b </i>also contains a guard time <b>24</b><i>a</i>, <b>24</b><i>b </i>selected according to the following considerations. The maximum range between any pair of nodes determines the maximum propagation delay that must be accommodated. A maximum range of 100 miles corresponds to about 0.5 ms of propagation delay. A guard time is allocated for each mini-slot <b>22</b><i>a</i>, <b>22</b><i>b </i>to accommodate uncertainty of propagation delay and unequal propagation delays between all pairs of nodes.

[0057] At a maximum range of 100 miles, a guard time of 0.5 ms is needed. The guard time allocation for a maximum range of 100 miles implies the need to make the mini-slots <b>22</b><i>a</i>, <b>22</b><i>b </i>on the order of 2 to 4 ms to minimize the channel efficiency loss. As an example, if we assume a 50 Mb/s data rate on the communication links and a maximum range of 100 miles, then a 4 ms mini-slot implies 200,000 bits/mini-slot (250 mini-slots per second). Then the mini-slot would contain a 25,000 bit guard time and 175,000 bits of mission data.

[0058] The controller <b>18</b> may also bias each established link to assign priority when the available time slots are scheduled. As will be discussed in greater detail below, semi-permanent (SP) time slots and available or demand assigned (DA) time slots are provided within each frame. A stated objective is to increase reuse of time slots among several nodes at the same time. While the mobile network <b>10</b> in FIG. 1 is limited in the total number of nodes and communication links, there are a number of cases of parallel usage of time slots. For example, time slots 1 and 2 are simultaneously each used on 3 different communication links, and time slot 6 is used on only one link. All the other time slots are assigned to two communication links. We can define a reuse factor which indicates the average level of reuse as a ratio of the total number of time slot assignments in the network (N_frame) to the number of assigned time slots (Num_Slots_Assigned): <maths id="MATH-US-00001" num="1"><math overflow="scroll"><mtable><mtr><mtd><mrow><mi>R</mi><mo>=</mo><mfrac><mrow><mi>Num_Slots</mi><mo></mo><mi>_Assigned</mi></mrow><msub><mi>N</mi><mi>frame</mi></msub></mfrac></mrow></mtd><mtd><mrow><mo>(</mo><mn>1</mn><mo>)</mo></mrow></mtd></mtr></mtable></math><img file="US20030193908A1-20031016-M00001.TIF" id="EMI-M00001" he="19.93005" wi="216.027" img-format="tif" img-content="mf" /><attachments><attachment idref="MATHEMATICA-00001" attachment-type="nb" file="US20030193908A1-20031016-M00001.NB" /></attachments></maths>

[0059] For the example network <b>10</b> in FIG. 1, the reuse approach provides a reuse factor of R=14/6=2.333, indicating that on the average there are slightly more than two simultaneous users of each time slot in the network schedule. It is obvious that the reuse factor calculated for any specific scheduling algorithm will be highly dependent on the network size and topology. A full comparative evaluation should consider a variety of network sizes and topologies.

[0060] A lower bound on the value of N_framefor any graph can be determined by noting that each node requires at least as many time slots as the node has neighbors, i.e, the node requires a number of time slots at least equal to its degree. Then N_framemust be at least as great as the maximum node degree over the entire graph. Thus, denoting the degree of node i by d_ithe lower bound on N_frameis

<i>N</i>_frame≧max_i<i>{d</i>_i}  (2)

[0061] For the example network <b>10</b> illustrated in FIG. 2 the reuse portion is assigned the scheduling with N_frameequal to the minimum number of time slots that must be used according to equation (2). Note that several nodes, namely all nodes but node 1, are assigned less than the full set of time slot. Thus, an enhanced scheduling algorithm may be able to assign additional slots to some of the links without introducing conflicts in scheduling.

[0062] The following discussion focuses primarily on the scheduling of time slots for generating the link schedules. Other parts of the overall phased array network problem that ultimately must be addressed include: 1) node and neighbor discovery, 2) net entry, 3) overhead channel format and protocol including protocol exchanges for scheduling updates, and 4) tracking and location of neighbor nodes (may include assistance of phased array antenna <b>16</b>), and 5) a routing algorithm for a dynamic network topology.

[0063] The approach for scheduling time slots according to the present invention is based upon the following principles. First, a specified number of time slots are allocated as semi-permanent (SP) time slots scheduled for a given link. The rest of the available time slots (DA) may be allocated on a demand-assigned basis to those nodes/links that need them most. This allows flexibility in shifting the schedule on an as needed basis. Secondly, as discussed above, a limit on the maximum number of semi-permanently assigned time slots is established. This limit is a parameter that is selected based upon a specific network. This limit is also the upper limit on the number of allowable neighbor nodes, with a single SP time slot per node.

[0064] Third, as also discussed above, a limit on the maximum number of time slots per frame is established. This limit is a parameter that is also selected based upon a specific network. This limit is important for establishing a limit on latency since it determines the maximum revisit time for a link transmit opportunity.

[0065] Fourth, the relationship between the number of total time slots per frame, N_frame, and the limit on the maximum number of semi-permanently assigned time slots per frame is chosen so that the scheduling of the semi-permanently assigned time slots is greatly simplified and scheduling conflicts may be significantly avoided even with distributed scheduling.

[0066] By limiting the maximum number of semi-permanently assigned time slots per node to a certain fraction to the total number of time slots per frame, the process of distributively assigning semi-permanently assigned time slots is greatly simplified. The upper limit on the number of the semi-permanently assigned time slots (and, therefore, the maximum number of allowable neighbor nodes) will be denoted by N. We will consider values of N_framesuch that:

<i>N</i>_frame≧2<i>N−</i>1  (3)

[0067] Assume that all nodes <b>12</b><i>a</i>-<b>12</b><i>h </i>in the network <b>10</b> are connected by directional links, where each node has a single beam phased array antenna <b>16</b> with beam sharing by time hopping and pointing to its neighbor nodes. Further, assume that the number of neighbors is equal to N, and the limit on the allowable number of semi-permanent time slots (with one SP time slot allocated per neighbor) is fixed.

[0068] If the fixed value of N_framesatisfies equation (3), then all nodes can select a different semi-permanent time slot for each of these links by mutual agreement with the neighbor for that link without regard to what links other nodes are selecting more than one-hop away. This allows each node to select its semi-permanent time slot for the link to a neighbor node in a very direct fashion by communicating only with that neighbor node. This process can be followed for up to N neighbor nodes.

[0069] The key is recognizing that as the value of N_frameincreases for a fixed value of N, there are fewer constraints on the ability of a node to select a time slot that does not conflict with a neighbor's choice of a time slot. A node selecting a time slot for a new link must select a time slot that it is not currently being used and that the neighbor is not currently using.

[0070] If a node currently has m neighbors with a single time slot assigned to each of these links to the neighbors and is adding a link to a new neighbor node, then the neighbor node can be using at most (N−1) time slots. Thus, if N_frameis greater than (m+N−1), then there will be at least one more time slot available that the node can assign to the new link. The worst case in this assignment process is when the node already has (N−1) neighbors and is assigning the time slot for the N^thneighbor node. In this case N_framemust satisfy equation (3) for an additional time slot to be guaranteed to be available for assignment to the link to the N^thneighbor.

[0071] Some additional observations will be made about how this property can be exploited in the disclosed time slot scheduling approach. First, a node need only coordinate the selection of the semi-permanent time slot to be assigned for a directional link to a neighbor with that neighbor. The node requesting the link might, for example, send to the neighbor the list of suggested time slots for the link. This is based upon those time slots not being used for SP assignments. There could be some ordering of this list based upon other factors to be discussed below, but this is not necessary. The neighbor node can then select from this list the time slot it prefers and return a reply with this selection. This allows us to define a straightforward, fully distributed algorithm for scheduling the semi-permanent time slots.

[0072] If a node has less than N neighbors, then more than one of its N allowed semi-permanent time slots could be assigned on individual links. However, in this case there is no guarantee that all N assignments can be made via neighbor-to-neighbor node coordination without some conflicts. For example, if N=6 and a node had only 3 neighbors but each of these neighbors each had 6 neighbors, then the node would be able to assign only one time slot to each of the links with its 3 neighbors. In order to simplify our algorithm, we will not allow scheduling of more than one SP time slot per link. However, all unused time slots may be allocated as available time slots.

[0073] For certain networks with very large numbers of nodes where the number of potential neighbors will be much larger than the limit N, there will also be a topology control problem to deal with. The node will be faced with choosing, from among the potential neighbors, those neighbors that create the optimum network topology. This topology control problem also is related to the concept of optimizing an energy efficient network. In the case where the number of potential neighbors is much larger than the limit N, a topology control function can be used to select the neighbor node to connect to.

[0074] If we assign to N_framethe minimum value allowed by (3), then each node will be allowed to have a maximum of N semi-permanent time slots and a total of (2N−1) time slot assignments. The demand assigned time slots will be assigned on a basis to best accommodate the traffic load.

[0075] As with the semi-permanent time slots, the node need only coordinate the selection of the available time slots to be assigned for a directional link to a neighbor with that neighbor. This means that a neighbor will send a request to the neighbor for the time slot assignment over the directional link, and receive either a grant of the assignment or a denial of the request over the same link.

[0076] A node requesting the allocation of an available time slot DA from a neighbor node will do so based upon a perceived need for additional capacity on that link. This may be prompted by a high link utilization (queue buildup) based on short and long term measurements. The request will contain the number of slots requested and a metric, which indicates the priority to be attached to the request. The metric might indicate the queue length as a measure of the need for the time slot allocation.

[0077] The node receiving the request may also receive requests from other neighbor nodes, which may contend for allocation of the same time slot. In order to simplify the protocol, a node must complete processing one thread of an available time slot DA allocation before considering the next allocation. These allocations may not persist for a long period of time because they are constantly subject to preemption to become reallocated as semi-permanent time slots as a result of topology changes or subject to reallocation due to shifting traffic demand.

[0078] Neighbor and link discovery will now be discussed. The distributed link scheduling algorithm requires support from an omni-directional overhead channel for certain protocol exchanges that must occur with a potential neighbor node prior to the establishment of the directional link with that node. Such messages include the REQ_SPTS which requests the allocation of a semi-permanent time slot on the directional link to that node.

[0079] In addition to supporting protocol message exchanges which directly support the protocol defined herein, the omni-directional overhead channel must support the function of neighbor and link discovery. This is usually done through periodic omni transmissions by each node via an omni-directional antenna <b>20</b> that alerts any other node that move within range that the two nodes can be neighbor nodes. Several ad hoc routing protocols (including OLSR) have defined such a supporting protocol. These previously defined protocols could be adapted to support this distributed link scheduling algorithm. The primary function that must be performed by such a protocol is to discover new potential neighbor nodes and to report these to the topology control function.

[0080] One approach for node and link discovery includes each node periodically transmitting beacon messages over the control channel to notify neighbor nodes of its presence and its position. In addition, link state messages are transmitted periodically to notify neighbor nodes of the identity of its beacon neighbors (BN list) and its PA neighbor nodes (PAN list) and the time slots assigned to these nodes.

[0081] The link discovery portion of the algorithm continually compares the bidirectional beacon neighbors (BBN) list with the PAN list to see if there are any nodes on the BBN list that are not on the PAN list. Any such neighbor node becomes a candidate for link testing to determine if a PA link is possible. According to this approach, after an exchange of control messages the directional link is tested to determine if reliable communication is possible. If communication is reliable, the new neighbor node is added to the PAN list.

[0082] This validates communication in the testing time slot, but not necessarily in the time slot that may be assigned to the link on a semi-permanent basis. One approach is to do it this way or another approach is to wait until an SP time slot is assigned and test it in this time slot.

[0083] The topology control function can be a very straightforward function if it does not have to do topology optimization. The purpose of this function is to take the list of nodes in the PAN list, the information about the reliability of these links, and the information about the network topology, and use this information to determine which nodes on the PAN list should become PA neighbors. This is the function that should optimize the network topology if there are constraints such as the number of PA neighbors that do not allow all nodes in the PAN list to become PA neighbors.

[0084] With the proposed constraints of a fixed value for N_frameand a fixed value for N (the maximum number of semi-permanent time slots per node), the potential exists for having some concern about network topology utilization. This would certainly be the case if these values were selected to be very small numbers. For example, if N=3 were selected with N_frame=5, it may be difficult to expect a well connected network topology when we could have no more than 3 neighbors for any node, unless an intelligent topology control function carefully utilized the topology prior to adding new PA neighbor nodes. This may be particularly so for a large network.

[0085] Thus, the topology control function should create a neighbor priority (NP) list, which is the PAN list ordered in order of desirability as potential PA neighbors. This list will direct the priority order in which potential PA neighbors are scheduled time slots. However, our initial problem is that of a small network with perhaps 15 nodes. In this case, we could specify N to have a value in the range of 5 to 8 and still have low latency. There is very little likelihood that there will be any topology utilization issues since allowing for 5 to 8 neighbor nodes will allow almost all possible neighbors to be PA neighbors.

[0086] A second purpose of the topology control function is to generate the topology change event that causes the link scheduler process to change state and perform the reallocation process for the SP time slots.

[0087] A top-level scheduling algorithm structure will now be discussed. The scheduling process was formulated with the objective of minimizing the complexity of the process while taking advantage of the overall approach outlined above. Key to controlling this scheduling process is maintaining an accurate data structure at each node reflecting the state of time slot schedules for future time slots assigned to the link with each neighbor node.

[0088] Two data structures are proposed: a slot assignment DB and a link message DB. The possible states of links in the data structure for a given time slot in the epoch are listed in TABLE 1. The table describes each possible state and gives the notation for that state. TABLE 2 shows an example slot assignment DA and the contents indicating the timeslots for N_frame=9(N=5), the state assignments for each state, and example assigned neighbor IDs for each time slot.

[0089] In this example, 4 neighbors have been assigned SP time slots so one additional neighbor may be connected with these constraints. There is one free time slot which may be allocated as a DB time slot or offered with the DB time slots to be allocated as an SP time slot if a new neighbor node is possible. The use of the link message DB will be discussed later in the detailed protocol explanation. The example also indicates the use of sub-slots, e.g., 2 sub-slots per slot.

[0090] This is a concept to be used with the DA allocations to allow finer granularity. The meaning in this case would be that an allocation of time slot k, sub-slot 1 would be an allocation to a link of time slot k on the odd numbered frames. Conversely, sub-slot 2 would indicate an allocation of the time slot on the even numbered frames. <tables id="TABLE-US-00001" num="1"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="133PT" align="left" /><colspec colname="2" colwidth="56PT" align="left" /><thead><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="2" align="center">TABLE 1</entry></row><row>&lt;entry /&gt;&lt;entry /&gt;</row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row><row>&lt;entry /&gt;<entry>Time Slot State in DB</entry><entry>Notation</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;<entry>Free</entry><entry>Free</entry></row><row>&lt;entry /&gt;<entry>SP Allocated Time Slot</entry><entry>SP_Alloc</entry></row><row>&lt;entry /&gt;<entry>DA Allocated Time Slot (May</entry><entry>DA_Alloc</entry></row><row>&lt;entry /&gt;<entry>Be Preempted by SP Allocation</entry></row><row>&lt;entry /&gt;<entry>Process or by DA</entry></row><row>&lt;entry /&gt;<entry>Reallocation)</entry></row><row>&lt;entry /&gt;<entry>SP Allocation Request Message</entry><entry>SP_Req</entry></row><row>&lt;entry /&gt;<entry>Sent</entry></row><row>&lt;entry /&gt;<entry>SP Allocation Reply Message</entry><entry>SP_Reply</entry></row><row>&lt;entry /&gt;<entry>Sent</entry></row><row>&lt;entry /&gt;<entry>DA Allocation Request Message</entry><entry>DA_Req</entry></row><row>&lt;entry /&gt;<entry>Sent (May Be Preempted by SP</entry></row><row>&lt;entry /&gt;<entry>Allocation Process or by DA</entry></row><row>&lt;entry /&gt;<entry>Reallocation)</entry></row><row>&lt;entry /&gt;<entry>DA Allocation Reply Message</entry><entry>DA_Reply</entry></row><row>&lt;entry /&gt;<entry>Sent (May Be Preempted by SP</entry></row><row>&lt;entry /&gt;<entry>Allocation Process or by DA</entry></row><row>&lt;entry /&gt;<entry>Reallocation)</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0091]<tables id="TABLE-US-00002" num="2"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="5"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="35PT" align="center" /><colspec colname="2" colwidth="56PT" align="center" /><colspec colname="3" colwidth="42PT" align="left" /><colspec colname="4" colwidth="70PT" align="center" /><thead><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="4" align="center">TABLE 2</entry></row><row>&lt;entry /&gt;&lt;entry /&gt;</row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="4" align="center" rowsep="1" /></row><row>&lt;entry /&gt;&lt;entry /&gt;&lt;entry /&gt;&lt;entry /&gt;<entry>Assigned</entry></row><row>&lt;entry /&gt;<entry>Time Slot</entry><entry>Subslot</entry><entry>State</entry><entry>Neighbor ID</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="4" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;</row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="5"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="35PT" align="char" char="." /><colspec colname="2" colwidth="56PT" align="center" /><colspec colname="3" colwidth="42PT" align="left" /><colspec colname="4" colwidth="70PT" align="center" /><tbody valign="top"><row>&lt;entry /&gt;<entry>1</entry><entry>—</entry><entry>Free</entry><entry>—</entry></row><row>&lt;entry /&gt;<entry>2</entry><entry>—</entry><entry>SP_Alloc</entry><entry>3</entry></row><row>&lt;entry /&gt;<entry>3</entry>&lt;entry /&gt;<entry>SP_Req</entry><entry>4</entry></row><row>&lt;entry /&gt;<entry>4</entry><entry>1</entry><entry>DA_Alloc</entry><entry>3</entry></row><row>&lt;entry /&gt;<entry>4</entry><entry>2</entry><entry>DA_Alloc</entry><entry>4</entry></row><row>&lt;entry /&gt;<entry>5</entry><entry>1</entry><entry>DA_Alloc</entry><entry>5</entry></row><row>&lt;entry /&gt;<entry>5</entry><entry>2</entry><entry>DA_Alloc</entry><entry>3</entry></row><row>&lt;entry /&gt;<entry>6</entry><entry>—</entry><entry>SP_Alloc</entry><entry>5</entry></row><row>&lt;entry /&gt;<entry>7</entry><entry>1,2</entry><entry>DA_Alloc</entry><entry>8</entry></row><row>&lt;entry /&gt;<entry>8</entry><entry>2</entry><entry>DA_Alloc</entry><entry>4</entry></row><row>&lt;entry /&gt;<entry>9</entry><entry>—</entry><entry>SP_Alloc</entry><entry>8</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0092] The top-level state diagram for the link scheduling protocol is shown in FIG. 5. The diagram shows two independent processes <b>30</b> and <b>32</b> that are responsible for maintaining and modifying the time slot allocation database. On the left side is the state diagram for the process for maintaining and assigning semi-permanent (SP) time slots, i.e., process <b>30</b>. This process has priority over the assignments made by the process <b>32</b> on the right, which has responsibility for assigning the available (DA) time slots. Within process path <b>31</b>, the time slots that can be seized are as follows: free, DA allocated, and in process of being DA allocated. Similarly, within process path <b>33</b>, the time slots that can be seized are as follows: free, DA allocated and also need to be reallocated.

[0093] This database must be controlled as a locked database such that for any given time slot assignment state, only one of the two scheduling processes may modify that state at a given point in time. Once one of the processes begins to modify the state of a particular time slot assignment, the state is locked and the other process may not modify it until it is released.

[0094] At any time each time slot in the DB is in one of seven states as indicated in TABLE 1. Available time slots are said to be in the free state, i.e., they are not assigned to a link to one of its neighbor nodes either because a scheduling conflict has prevented assignment or because the time slot has recently become free and has not yet been scheduled.

[0095] As indicated, a time slot in the free state may be scheduled either as an SP time slot or a DA time slot. A time slot that has been allocated as SP assigned may be modified only by the process that maintains SP time slots. The time slot may be deallocated by this process if network topology changes or if a more desirable topology is possible. Until such a time slot is returned to the free state, the process for maintaining and assigning the DA time slots cannot modify its state.

[0096] In addition, any time slot with a DB state indicating that it is in the process of being SP assigned cannot be allocated by the DA assignment process. This includes states indicating that SP request and reply messages have been sent. However, if the state of a time slot is DA allocated, then it may be reallocated by the DA assignment process. This might be done if the loading on the network indicated that a reallocation of the DA time slot is needed.

[0097] In contrast, the process allocating SP time slots has priority. In addition to assigning free slots, it may seize and reassign all time slots that have been DA assigned or are in the process of being DA assigned. This is done to provide a straightforward process of ensuring at least a single SP time slot assigned to each neighbor node during a frame of N_frametime slots. SP allocated time slots are returned to the free state only if the link is lost or if the topology control function determines that a particular link should no longer be in the list of the top N links to be established with neighbor nodes.

[0098]FIG. 5 illustrates how this process works at the top level. The SP slot assignment process has greater flexibility in allocating time slots. It can seize more time slots for allocation than the DA process, and it can seize time slots that either have been DA allocated or are in the process of being DA allocated. The SP process may receive various events for processing including topology change events from the topology control function and protocol messages.

[0099] Such events might include loss of link to a neighbor, discovery of a new neighbor, reception of an SP allocation request message from a neighbor node, and the discovery that a topology change should occur to either add a link to a neighbor, break a link, or do both. The topology change event notification will carry data that will describe the topology change that needs to occur.

[0100] If the event described a loss of a link, then the only action that must be taken is to change the appropriate time slot state in the slot assignment DB to “free.” If a link is to be added the process is more complex. In this case, the SP slot assignment process initiates protocol message exchanges with the new neighbor node and modifies the slot assignment DB. This ultimately results in the agreement between the two nodes on a time slot assignment for the SP slot assigned to this link. Only a single SP time slot is to be assigned to each link with a neighbor to simplify the protocol. Additional details of this protocol are described below.

[0101] The process of assigning DA time slots follows a similar procedure. The DA slot assignment process must calculate the DA time slot needs and compare them with the allocated time slots to determine if a new time slot reallocation is needed. If a reassignment of DA slots is initiated, it will also lead to a series of protocol message exchanges with neighbor nodes to agree on the reassigned time slots. The DA slot assignment process may reassign only time slots that are in the free state or not SP assigned. More about the protocol details and the process for determining when DA time slot reassignment is needed will be discussed below.

[0102] Allocating semi-permanent time slots to directional links will now be discussed. In the description of the approach for allocating N semi-permanent time slots assume that N is fixed and intelligently chosen with respect to the network size and environment. Also assume that N_frame=2N−1. N_framecould also be set at any value higher than this to provide additional on-demand time slots if that is deemed to be useful for the particular network and traffic environment.

[0103] Several important functions are provided by the topology control function. The neighbor priority (NP) list is generated by the topology control function and is used to indicate the preferred PA neighbor nodes for the assignment of time slots.

[0104] If the length of the NP list is N or smaller, then the topology control function will generate topology change events to the SP slot assignment process to make it attempt to get time slot assignments to all of these neighbor nodes. If the length of the NP list is greater than N, then it will generate topology change events to the SP slot assignment process to obtain time slot assignments to each of the N highest priority nodes on the NP list.

[0105] The NP list is constantly changing due to network dynamics. When PA links go down, the node is removed from the NP list and the time slot(s) for that link are then subject to reallocation. This is initiated by the topology control function which sends the SP slot assignment process a link delete event. Thus, the SP time slot and any DA time slots allocated to that link become available for reallocation to another node on the PA list.

[0106] The first choice when slots become available is to allocate the slot(s) to additional PA neighbor nodes if that is possible given the current state of the NP list. If no additional neighbor nodes can be added, then the slot(s) can be reallocated on a DA basis.

[0107]FIG. 6 shows a state diagram of the SP slot assignment process. In order to manage the protocol message processing, a link scheduling message DB is created as shown in TABLE 3. This maintains the state needed from prior protocol exchanges to be used when the next SP message arrives for processing. The idle process does event management in that it checks received events prior to allowing a state change to one of the other states.

[0108] These operations include checking received messages to determine if they are consistent with the current state of the DB. If a message is inconsistent with the DB, it is discarded. Certain timeouts may indicate that DB state needs to be reset. This process performs this function. <tables id="TABLE-US-00003" num="3"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="7"><colspec colname="1" colwidth="28PT" align="center" /><colspec colname="2" colwidth="42PT" align="left" /><colspec colname="3" colwidth="35PT" align="center" /><colspec colname="4" colwidth="28PT" align="center" /><colspec colname="5" colwidth="28PT" align="center" /><colspec colname="6" colwidth="28PT" align="center" /><colspec colname="7" colwidth="28PT" align="center" /><thead><row><entry namest="1" nameend="7" align="center">TABLE 3</entry></row><row>&lt;entry /&gt;</row><row><entry namest="1" nameend="7" align="center" rowsep="1" /></row><row>&lt;entry /&gt;&lt;entry /&gt;&lt;entry /&gt;<entry>Time</entry><entry>Selected</entry>&lt;entry /&gt;&lt;entry /&gt;</row><row>&lt;entry /&gt;<entry>Link</entry>&lt;entry /&gt;<entry>Slot</entry><entry>Time</entry><entry>Selected</entry><entry>Num_—</entry></row><row><entry>Nbr_ID</entry><entry>State</entry><entry>Time out</entry><entry>List</entry><entry>Slot</entry><entry>Subslot</entry><entry>tries</entry></row><row><entry namest="1" nameend="7" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>1</entry><entry>SP_Alloc</entry><entry>—</entry><entry>—</entry><entry>2</entry><entry>1</entry><entry>—</entry></row><row><entry>1</entry><entry>SP_Alloc</entry><entry>—</entry><entry>—</entry><entry>2</entry><entry>2</entry><entry>—</entry></row><row><entry>1</entry><entry>DA_Alloc</entry><entry>—</entry><entry>—</entry><entry>5</entry><entry>1</entry><entry>—</entry></row><row><entry>2</entry><entry>SP_Alloc</entry><entry>—</entry><entry>—</entry><entry>4</entry><entry>1</entry><entry>—</entry></row><row><entry>2</entry><entry>SP_Alloc</entry><entry>—</entry><entry>—</entry><entry>4</entry><entry>2</entry><entry>—</entry></row><row><entry>2</entry><entry>DA_Alloc</entry><entry>—</entry><entry>—</entry><entry>5</entry><entry>2</entry><entry>—</entry></row><row><entry>3</entry><entry>SP_Req</entry><entry>T2</entry><entry>Ls</entry><entry>—</entry>&lt;entry /&gt;<entry>1</entry></row><row><entry>4</entry><entry>SP_Alloc</entry><entry>—</entry><entry>—</entry><entry>6</entry><entry>1</entry><entry>—</entry></row><row><entry>4</entry><entry>SP_Alloc</entry><entry>—</entry><entry>—</entry><entry>6</entry><entry>2</entry><entry>—</entry></row><row><entry namest="1" nameend="7" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0109] There are four basic message types required in the SP time slot assignment protocol as listed below in Table 4. The use of these are self-explanatory and consistent with the prior discussion. <tables id="TABLE-US-00004" num="4"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="OFFSET" colwidth="21PT" align="left" /><colspec colname="1" colwidth="63PT" align="left" /><colspec colname="2" colwidth="133PT" align="left" /><thead><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="2" align="center">TABLE 4</entry></row><row>&lt;entry /&gt;&lt;entry /&gt;</row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row><row>&lt;entry /&gt;<entry>Message Type</entry><entry>Message Function</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;<entry>REQ_SPTS</entry><entry>Request New SP Slot Allocation</entry></row><row>&lt;entry /&gt;<entry>REPLY_SPTS</entry><entry>Reply to Received REQ_SPTS</entry></row><row>&lt;entry /&gt;<entry>CONFIRM</entry><entry>Response to Received REPLY_SPTS</entry></row><row>&lt;entry /&gt;<entry>DELETE_TS</entry><entry>Message Indicating Deleted Time</entry></row><row>&lt;entry /&gt;&lt;entry /&gt;<entry>Slot Allocation</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0110] An example of SP time slot assignment is shown in FIG. 7. Nodes 1 and 2 both have 3 neighbors with the SP time slots allocations shown for each link. Therefore, they can add an additional link between themselves. The link scheduling protocol will find an acceptable time slot for the SP allocation. The corresponding protocol message exchange is shown in TABLE 5.

[0111] Node 1 initiates the exchange by sending a REQ_SPTS(L=(4,5,6,7)) with a list of at least N candidate time slots. This list may include all free and DA time slots. Node 1 is using slots 1, 2 and 3 for SP allocations to its neighbors so its list L contains the other time slots 4, 5, 6 and 7. When the request message is sent, the appropriate changes are made to the time slot and link scheduling message data structures. Node 2 is using time slots 4, 5 and 6 as SP allocations for its links to its 3 neighbors so it selects time slot 7 as the only one that will work for the new link. It sends this choice in the reply message.

[0112] When a reply message is sent, the appropriate changes are also made to the time slot and link scheduling message data structures. Finally, when a confirm is sent or received, the state of the appropriate time slots are changed to “SP allocated to link (1,2).”

[0113] Note also that if nodes 1 and 2 had already selected 4 neighbor nodes, it would still be possible for them to find common time slots with which to establish a link between them if they used the same time slots with at least two of their neighbors. <tables id="TABLE-US-00005" num="5"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="91PT" align="left" /><colspec colname="2" colwidth="28PT" align="center" /><colspec colname="3" colwidth="98PT" align="left" /><thead><row><entry namest="1" nameend="3" align="center">TABLE 5</entry></row><row>&lt;entry /&gt;</row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row><row><entry>Node 1</entry>&lt;entry /&gt;<entry>Node 2</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>Receives Link Add Event</entry>&lt;entry /&gt;&lt;entry /&gt;</row><row><entry>From Its Topology</entry></row><row><entry>Control For A Link From</entry></row><row><entry>Node 1 to Node 2</entry></row><row><entry>Send</entry><entry>→</entry><entry>Msg Lost</entry></row><row><entry>REQ_SPTS(L= (4,5,6,7) )</entry></row><row><entry>Timeout and retry</entry><entry>→</entry><entry>Rcvd</entry></row><row><entry>Resend</entry></row><row><entry>REQ_SPTS(L= (4,5,6,7) )</entry><entry>←</entry><entry>REQ_SPTS(L= (4,5,6,7) )</entry></row><row><entry>Rcvd REPLY_SPTS(Slot 7)</entry>&lt;entry /&gt;<entry>Send REPLY_SPTS(Slot</entry></row><row>&lt;entry /&gt;&lt;entry /&gt;<entry>7)</entry></row><row><entry>Send CONFIRM(Slot 7)</entry><entry>→</entry><entry>Rcvd CONFIRM(Slot 7)</entry></row><row><entry>Slot 7 Allocated to Link</entry>&lt;entry /&gt;<entry>Slot 7 Allocated to</entry></row><row><entry>(1,2)</entry>&lt;entry /&gt;<entry>Link (1,2)</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0114] Some initial pseudocode describing the processes required in FIG. 6 has been developed. There are various events that may occur which must be processed by the SP slot assignment process <b>34</b>. Event management is done in the idle process as shown in TABLE 6. Four categories of events are shown: received message, check timeouts, link addition notification from topology control, and link failure or link deletion.

[0115] Received messages are first checked versus the link scheduling message DB to insure that the message is consistent with the current state of the DB. For example, if we sent a request to a neighbor, the next message expected is a reply. To simplify this distributed protocol, only one thread of SP protocol message exchanges is allowed at a time. This is enforced in the procedure by checking the DB to see if other SP message exchanges are ongoing prior to initiating a link add transition or prior to processing a REQ_SPTS message.

[0116] If a link addition cannot be initiated because another SP protocol thread is currently in process, the link addition will be postponed by backing off and rescheduling for a later time when the other process is expected to be completed. Allowing multiple attempts is done to handle potential conflict between several nodes attempting to add links simultaneously. This is not meant to deal with the problem of an unreliable RF link. This latter issue should be addressed by using a link protocol on the overhead channel that uses ARQ and retransmission to recover lost/errored messages.

[0117] Thus, the distributed scheduling protocol can assume that messages will not get lost. This allows simplification of the protocol. When topology control selects a neighbor node from the NP list to connect to as a new neighbor, it issues a topology change (link addition) event which (after consistency checks in the idle process) causes a transition to the link add state in the SP slot assignment process. <tables id="TABLE-US-00006" num="6"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 6</entry></row><row>&lt;entry /&gt;</row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Procedure for Idle State (SP Event Management)</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;</row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>Case Event Type</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Received Message:</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>If received message is not consistent with the</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="56PT" align="left" /><colspec colname="1" colwidth="161PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>state of the Link Scheduling Message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="84PT" align="left" /><colspec colname="1" colwidth="133PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>DB for that Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Discard Message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Elseif message type = REQ_SPTS</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="84PT" align="left" /><colspec colname="1" colwidth="133PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>If no pending SP message activity in the</entry></row><row>&lt;entry /&gt;<entry>Link</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="98PT" align="left" /><colspec colname="1" colwidth="119PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Scheduling Message DB for link</entry></row><row>&lt;entry /&gt;<entry>additions</entry></row><row>&lt;entry /&gt;<entry>other than receiving a previous</entry></row><row>&lt;entry /&gt;<entry>REQ_SPTS</entry></row><row>&lt;entry /&gt;<entry>message from Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Transition to Process REQ_SPTS</entry></row><row>&lt;entry /&gt;<entry>state to</entry></row><row>&lt;entry /&gt;<entry>process message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="84PT" align="left" /><colspec colname="1" colwidth="133PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Else</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="112PT" align="left" /><colspec colname="1" colwidth="105PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Reject new link and send negative</entry></row><row>&lt;entry /&gt;<entry>REPLY_SPTS message to</entry></row><row>&lt;entry /&gt;<entry>Nbr_ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="84PT" align="left" /><colspec colname="1" colwidth="133PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>End</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Elseif message type = REPLY_SPTS</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="70PT" align="left" /><colspec colname="1" colwidth="147PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Transition to Process REPLY_SPTS state to</entry></row><row>&lt;entry /&gt;<entry>process message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Elseif message type = CONFIRM</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="70PT" align="left" /><colspec colname="1" colwidth="147PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Transition to Process CONFIRM state to</entry></row><row>&lt;entry /&gt;<entry>process message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Elseif message type = DELETE_TS</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="70PT" align="left" /><colspec colname="1" colwidth="147PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Transition to Process DELETE_TS state to</entry></row><row>&lt;entry /&gt;<entry>process message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>End</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Check Timeouts:</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Check all timeouts</entry></row><row>&lt;entry /&gt;<entry>If Timeout expired for a link in the SP_Req state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="56PT" align="left" /><colspec colname="1" colwidth="161PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Transition to Link Add State</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>If Timeout expired for a link in the SP_Reply</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="56PT" align="left" /><colspec colname="1" colwidth="161PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>state</entry></row><row>&lt;entry /&gt;<entry>Reset Slot Assignment DB for time slot Ns and</entry></row><row>&lt;entry /&gt;<entry>in the Link Message state in</entry></row><row>&lt;entry /&gt;<entry>Link Scheduling Message DB for index Nbr_ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>End</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Link Addition Notification from Topology Control:</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>If no pending SP message activity in the Link</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="56PT" align="left" /><colspec colname="1" colwidth="161PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Scheduling Message DB</entry></row><row>&lt;entry /&gt;<entry>Transition to Link Add state to add Nbr_ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Else</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="56PT" align="left" /><colspec colname="1" colwidth="161PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Backoff and reschedule Link Addition</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>End</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Link Failure or Link Deletion:</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Transition to Link Delete state to delete link to</entry></row><row>&lt;entry /&gt;<entry>Nbr_ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>End</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>End</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0118] Psuedocode for the link add process is shown in TABLE 7. This starts a process which requires coordination of the SP time slot assignment and protocol message exchanges between only the two neighbor nodes. The node requesting the link sends a REQ_SPTS message to the candidate neighbor node with the list of acceptable time slots for the link.

[0119] The list of candidate time slots must contain at least N time slots including at least one semi-permanent time slot SP. The list can also include possibly all of the N−1 available DA time slots. The available or on-demand time slots may be currently temporarily allocated for on-demand traffic. This list will be priority-ordered to indicate the time slot preference that causes the least perturbation in the current available time slot assignments. In otherwords, the notation being used is that a time slot is not an SP time slot unless already allocated to a communication link. Any of the 2N−1 time slots may be an SP time slot. Thus, the list of N time slots sent are all either free time slots or an available DA time slot. These may be N−1 SP time slots but they are already allocated and are not on the list.

[0120] The REQ_SPTS message can be sent up to MAX_TRIES times to allow for unreliable links and conflicts with other assignments potentially occurring simultaneously. The timeout in the link scheduling message DB triggers the retries if there is no REPLY_SPTS message from the neighbor node in response to the REQ_SPTS message. Once the REQ_SPTS message is sent the process returns to the idle state where other events can be processed. <tables id="TABLE-US-00007" num="7"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 7</entry></row><row>&lt;entry /&gt;</row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Procedure for Link Addition to Node Nbr_ID</entry></row><row><entry>(Generate REQ_SPTS Message)</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;</row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>If Num_tries = MAX_TRIES (No more tries)</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Reset state of Link Scheduling Message DB for index</entry></row><row>&lt;entry /&gt;<entry>Nbr_ID (Link State = Free and no timeout for retry)</entry></row><row>&lt;entry /&gt;<entry>Return to Idle state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>Else</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>If initial try to node Nbr_ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Set Num_tries = 1 in Link Scheduling Message DB</entry></row><row>&lt;entry /&gt;<entry>for index Nbr_ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Else</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Set Num_tries = Num_tries +1 in Link Scheduling</entry></row><row>&lt;entry /&gt;<entry>Message DB for index Nbr_ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>End</entry></row><row>&lt;entry /&gt;<entry>Construct list Ls of time slots to offer to Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Append list Ls to REQ_SPTS message and send to Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Setup timeout and Link Message state in Link Scheduling</entry></row><row>&lt;entry /&gt;<entry>Message DB for index</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Nbr_ID and in Slot Assignment DB</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Return to Idle state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>End</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0121] The neighbor receiving a REQ_SPTS message will have its SP slot assignment process transition to the process REQ_SPTS state. The procedure for processing this message is shown in TABLE 8. This procedure takes the offered list of time slots, Ls, and selects its preferred time slot, Ns.

[0122] If the number of links to neighbor nodes, Num_links, is less than the limit N, the procedure selects the time slot it prefers from this list. Then a REPLY_SPTS reply message with this selection is sent. If the link cannot be accepted or if there is another ongoing SP slot assignment in process, a negative REPLY_SPTS reply message is sent.

[0123] The selected time slot will be selected from one of its N available time slots or one of its free time slots. An available time slot is either a “free” time slot or an available DA time slot. There will be at least N of these if we can add another link. Each node always manages its time slots so that there are N time slots available to assign as semi-permanent time slots (one to each of N neighbor nodes if that many neighbor nodes are available). If it accepts the link, then it will have at most N−1 other neighbor nodes with one semi-permanent time slot allocated per node. The procedure also makes the appropriate modifications to the state in the link scheduling message DB and the slot assignment DB. <tables id="TABLE-US-00008" num="8"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 8</entry></row><row>&lt;entry /&gt;</row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Procedure for Processing REQ_SPTS Message (from Nbr_ID)</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;</row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>If Num_links&lt;N</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Examine list Ls of the available time slots received</entry></row><row>&lt;entry /&gt;<entry>from potential neighbor node</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Nbr_ID, compare with the current allocations in</entry></row><row>&lt;entry /&gt;<entry>the Slot Assignment DB, and select the best</entry></row><row>&lt;entry /&gt;<entry>assignment = Ns</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Make appropriate modification to the Slot Assignment DB</entry></row><row>&lt;entry /&gt;<entry>(mark it as SP_Reply) for time slot Ns</entry></row><row>&lt;entry /&gt;<entry>If time slot Ns was DA allocated</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Send DELETE_TS to the neighbor node allocated the</entry></row><row>&lt;entry /&gt;<entry>DA time slot</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>End</entry></row><row>&lt;entry /&gt;<entry>Append time slot choice, Ns, to REPLY_SPTS message and</entry></row><row>&lt;entry /&gt;<entry>send to Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Setup timeout and Link Message state (to SP_Reply with</entry></row><row>&lt;entry /&gt;<entry>time slot Ns) in Link</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Scheduling Message DB for index Nbr_ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Return to Idle state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>Else</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Reject new link and send negative REPLY_SPTS message to</entry></row><row>&lt;entry /&gt;<entry>Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Return to Idle state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>End</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0124] A received REPLY_SPTS message is processed as shown in TABLE 9. The choice of time slot, Ns, received from the neighbor node is extracted from the message. We will also require the node to confirm this reply with either a positive or negative CONFIRM message that indicates that it will agree to use the allocated time slot. This three-way handshake eliminates uncertainty in the outcome of the scheduling process.

[0125] If the REPLY_SPTS message is a positive reply, then the choice of time slot, Ns, is examined to see if it is still an allowable assignment for a new SP time slot for the new link. If it is allowable, then the appropriate modifications to the state in the slot assignment and link scheduling message databases are made. Then a positive CONFIRM message is returned.

[0126] If the received REPLY_SPTS message was negative, then the slot assignment and link scheduling message databases are reset for this Nbr_ID. Otherwise, if the choice of Ns is no longer allowable, then the link scheduling message database is reset for this Nbr_ID. Then a negative CONFIRM message is sent to the neighbor node rejecting the link. <tables id="TABLE-US-00009" num="9"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 9</entry></row><row>&lt;entry /&gt;</row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Procedure for Processing REPLY_SPTS Message from Nbr_ID</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;</row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>Extract time slot choice Ns from the REPLY_SPTS message from</entry></row><row><entry>Nbr_ID</entry></row><row><entry>If (positive REPLY_SPTS message) and (choice of Ns is still</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>allowable from Slot Assignment DB)</entry></row><row>&lt;entry /&gt;<entry>Make appropriate modification to the Slot Assignment DB</entry></row><row>&lt;entry /&gt;<entry> (mark it as SP_Reply)</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>for time slot Ns and in the Link Message state in</entry></row><row>&lt;entry /&gt;<entry>Link Scheduling Message DB</entry></row><row>&lt;entry /&gt;<entry>for index Nbr_ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>If time slot Ns was DA allocated</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Send DELETE_TS to the neighbor node allocated the</entry></row><row>&lt;entry /&gt;<entry>DA time slot</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>End</entry></row><row>&lt;entry /&gt;<entry>Create CONFIRM message for Ns and send to Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Increment Num_links</entry></row><row>&lt;entry /&gt;<entry>Return to Idle state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>Elseif negative REPLY_SPTS message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Reset Slot Assignment DB for time slot Ns and in the</entry></row><row>&lt;entry /&gt;<entry>Link Message state in</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Link Scheduling Message DB for index Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Return to Idle state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>Else</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Reset Link Message state in Link Scheduling Message DB</entry></row><row>&lt;entry /&gt;<entry>for index Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Send negative CONFIRM message to Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Return to Idle state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>End</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0127] Table 10 shows the procedure for processing CONFIRM messages. If the CONFIRM is positive, the link is considered to be added to the set of neighbors. The number of links for the node, Num_links, is incremented. The assigned time slot, Ns, is marked SP_Alloc in the slot assignment DB, and the link message state in the link scheduling message DB is reset for index Nbr_ID. If the message was a negative CONFIRM, then the slot assignment and link scheduling message databases are reset for this Nbr_ID. <tables id="TABLE-US-00010" num="10"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 10</entry></row><row>&lt;entry /&gt;</row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Procedure for Processing CONFIRM Message from Nbr_ID</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;</row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>If positive CONFIRM message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Make appropriate modification to the Slot Assignment DB</entry></row><row>&lt;entry /&gt;<entry> (mark it as SP_Alloc)</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>for time slot Ns</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Reset Link Message state in Link Scheduling Message DB</entry></row><row>&lt;entry /&gt;<entry>for index Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Increment Num_links</entry></row><row>&lt;entry /&gt;<entry>Return to Idle state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Else</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Reset the Slot Assignment DB (mark it as Free) for time</entry></row><row>&lt;entry /&gt;<entry>slot Ns</entry></row><row>&lt;entry /&gt;<entry>Reset Link Message state in Link Scheduling Message DB</entry></row><row>&lt;entry /&gt;<entry>for index Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Return to Idle state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>End</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0128] An allocated time slot may need to be deallocated for one of several reasons. If during the course of normal operation a link goes down or becomes unreliable, then the topology control function gets involved to address the unreliable link problem. Ultimately, it may generate a topology change (e.g., link deletion) event directing the SP slot assignment process to delete all slots assigned to the link.

[0129] The steps involved in this procedure are shown in TABLE 11. The link is de-allocated by sending a DELETE_TS message from the node requesting the de-allocation of all the time slots which are shared with the other node. In addition, the appropriate entries in the link scheduling message DB and the slot assignment DB are reset. <tables id="TABLE-US-00011" num="11"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 11</entry></row><row>&lt;entry /&gt;</row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Procedure for Link Deletion to Node Nbr_ID (Generate</entry></row><row><entry>DELETE_TS Message)</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;</row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Extract list of all SP and DA time slots, Ls, from the Slot</entry></row><row>&lt;entry /&gt;<entry>Assignment DB assigned to the</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>link to Nbr_ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Construct message, DELETE_TS, with the list, Ls, and send to</entry></row><row>&lt;entry /&gt;<entry>Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Reset Link Scheduling Message DB for index Nbr_ID and Slot</entry></row><row>&lt;entry /&gt;<entry>Assignment DB for all time slots in Ls</entry></row><row>&lt;entry /&gt;<entry>Decrement Num_links</entry></row><row>&lt;entry /&gt;<entry>Return to Idle state</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0130] Table 12 shows the procedure for processing a received DELETE_TS message. The list of deallocated time slots, Ls, is extracted from the message. Then the appropriate state in the slot assignment DB and in the link scheduling message DB is reset. <tables id="TABLE-US-00012" num="12"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 12</entry></row><row>&lt;entry /&gt;</row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Procedure for Processing DELETE_TS Message from Nbr_ID</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;</row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Extract list of time slots, Ls, from the DELETE_TS message</entry></row><row>&lt;entry /&gt;<entry>from Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Reset the Slot Assignment DB (mark it as Free) for all time</entry></row><row>&lt;entry /&gt;<entry>slots in list Ls</entry></row><row>&lt;entry /&gt;<entry>Reset Link Message state in Link Scheduling Message DB for</entry></row><row>&lt;entry /&gt;<entry>all time slots in list Ls for index Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Decrement Num_links</entry></row><row>&lt;entry /&gt;<entry>Return to Idle state</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0131] In summary, the objective for the function allocating the semi-permanent time slots is to connect to as many neighbor nodes as possible up to N. If N neighbor nodes are obtained, then each is allocated a single semi-permanent time slot. Once a new link is established by this protocol, both nodes will commence operation in the newly allocated SP time slot.

[0132] This operation will test the new link to determine if reliable communication can be maintained using the allocated time slot. This insures that there is no unusual interference that occurs in this particular time slot. If the link is tested as unreliable, then the topology control function will be notified so that the time slot can be deallocated and used for other purposes.

[0133] Allocation of available (on-demand) time slots will now be discussed. The available time slots are to be allocated in a manner that is responsive to the fluctuating demands of network traffic. Again, assume that N is fixed and intelligently chosen with respect to the network size and environment. Also assume that N_frame=2N−1.

[0134] To allow fine granularity in the allocation of available capacity, time slots will be divided into m_ssub-time slots. Assume for the rest of the following discussion that m_s=2. This will be accomplished by defining a sub-time slot to be a specific time slot allocation that repeats every m_s^th(or second) frame.

[0135] A request for available time slots from one node to a neighbor node is allowed only if at least one semi-permanent time slot is allocated for the link between these two nodes. After a link is allocated at least one semi-permanent time slot, then a node may request a periodic allocation of a single time slot every m_s^th(or second) frame. The messages used for scheduling the available time slots can be sent over the PA link for scheduling time slots several frames in advance of when they are needed since the link has an allocation of at least one semi-permanent time slot per frame.

[0136] A key requirement for efficient allocation of available time slots is the measurement of the traffic requirements on each link. Two measures will be needed. First, the measured average traffic sent over link (i, k) (in units of the number of time slots per frame) will be denoted by T_ikse. This measure will include all traffic sent over one or more semi-permanent time slots per frame as well as any available time slots.

[0137] In addition, we also need to maintain a current measure of the queue state, Q_ik, for link (i, k). Larger values of Q_ikindicate the need for an immediate allocation of one or more available time slots. Occasional bursts of demand may produce increases in Q_ik, which should then trigger a request for additional time slots of on-demand capacity until the queue size decreases.

[0138] The total number of time slots (quantized to ½ of a time slot with m_s=2) allocated on link (i, k) will be denoted by <maths id="MATH-US-00002" num="2"><math overflow="scroll"><mrow><msubsup><mi>N</mi><mi>ik</mi><mi>tot</mi></msubsup><mo>.</mo></mrow></math><img file="US20030193908A1-20031016-M00002.TIF" id="EMI-M00002" he="11.02815" wi="216.027" img-format="tif" img-content="mf" /><attachments><attachment idref="MATHEMATICA-00002" attachment-type="nb" file="US20030193908A1-20031016-M00002.NB" /></attachments></maths>

[0139] The time slot demand is defined as follows: <maths id="MATH-US-00003" num="3"><math overflow="scroll"><mtable><mtr><mtd><mrow><mrow><msubsup><mi>T</mi><mi>ik</mi><mi>dem</mi></msubsup><mo>=</mo><mrow><mi>f</mi><mo></mo><mrow><mo>(</mo><mrow><msubsup><mi>T</mi><mi>ik</mi><mi>se</mi></msubsup><mo>,</mo><msub><mi>Q</mi><mi>ik</mi></msub></mrow><mo>)</mo></mrow></mrow></mrow><mo>,</mo></mrow></mtd><mtd><mrow><mo>(</mo><mn>4</mn><mo>)</mo></mrow></mtd></mtr></mtable></math><img file="US20030193908A1-20031016-M00003.TIF" id="EMI-M00003" he="11.99205" wi="216.027" img-format="tif" img-content="mf" /><attachments><attachment idref="MATHEMATICA-00003" attachment-type="nb" file="US20030193908A1-20031016-M00003.NB" /></attachments></maths>

[0140] which is a function of the measured traffic plus the estimated additional capacity needed that is indicated by the queue size. Then the number of time slots needed on this link, <maths id="MATH-US-00004" num="4"><math overflow="scroll"><mrow><msubsup><mi>T</mi><mi>ik</mi><mi>need</mi></msubsup><mo>,</mo></mrow></math><img file="US20030193908A1-20031016-M00004.TIF" id="EMI-M00004" he="11.02815" wi="216.027" img-format="tif" img-content="mf" /><attachments><attachment idref="MATHEMATICA-00004" attachment-type="nb" file="US20030193908A1-20031016-M00004.NB" /></attachments></maths>

[0141] is as follows: <maths id="MATH-US-00005" num="5"><math overflow="scroll"><mtable><mtr><mtd><mrow><msubsup><mi>T</mi><mi>ik</mi><mi>need</mi></msubsup><mo>=</mo><mrow><mi>max</mi><mo></mo><mrow><mo>(</mo><mrow><msubsup><mi>T</mi><mi>ik</mi><mi>dem</mi></msubsup><mo>,</mo><msubsup><mi>T</mi><mi>ki</mi><mi>dem</mi></msubsup></mrow><mo>)</mo></mrow></mrow></mrow></mtd><mtd><mrow><mo>(</mo><mn>5</mn><mo>)</mo></mrow></mtd></mtr></mtable></math><img file="US20030193908A1-20031016-M00005.TIF" id="EMI-M00005" he="11.99205" wi="216.027" img-format="tif" img-content="mf" /><attachments><attachment idref="MATHEMATICA-00005" attachment-type="nb" file="US20030193908A1-20031016-M00005.NB" /></attachments></maths>

[0142] The metric assigned to this link is as follows: <maths id="MATH-US-00006" num="6"><math overflow="scroll"><mtable><mtr><mtd><mrow><mrow><msubsup><mi>M</mi><mi>ik</mi><mi>DA</mi></msubsup><mo>=</mo><mrow><msubsup><mi>T</mi><mi>ik</mi><mi>need</mi></msubsup><mo>-</mo><msubsup><mi>N</mi><mi>ik</mi><mi>tot</mi></msubsup><mo>+</mo><mi>B</mi></mrow></mrow><mo>,</mo></mrow></mtd><mtd><mrow><mo>(</mo><mn>6</mn><mo>)</mo></mrow></mtd></mtr></mtable></math><img file="US20030193908A1-20031016-M00006.TIF" id="EMI-M00006" he="11.99205" wi="216.027" img-format="tif" img-content="mf" /><attachments><attachment idref="MATHEMATICA-00006" attachment-type="nb" file="US20030193908A1-20031016-M00006.NB" /></attachments></maths>

[0143] which is a measure of the estimated number of additional time slots that should be allocated to this link through the DA slot allocation mechanism. B is a bias term that might be nominally set at about ¼ to ½ of a time slot to allocated enough excess capacity to each link to avoid significant queuing. While we are illustrating the approach using the metric defined in (4), a variety of other forms of metric could also be used as the basis for allocating the DA time slots.

[0144]FIG. 8 shows a state diagram of the DA slot assignment process <b>36</b>. The state diagram and the protocol exchanges are similar to those of the SP slot assignment process. In order to simplify the protocol message processing, only a single thread of DA time slot allocation can be in process at any time. The idle process does event management in that it checks received events prior to allowing a state change to one of the other states.

[0145] These operations include the following. Check received messages to determine if they are consistent with the current state of the DB. If a message is inconsistent with the DB, it is discarded. Certain timeouts may indicate that DB state needs to be reset. This process performs this function. It also determines if the DA slot assignment is optimal given the traffic load needs of the node. It may cause a transition to the add DA slot state if it determines if a new DA time slot must be added to a particular link.

[0146] There are four basic message types required in the DA time slot assignment protocol as listed below in TABLE 13. These are very similar to those used in the SP slot allocation. The use of these is self-explanatory and consistent with the prior discussion of the SP slot allocation process. <tables id="TABLE-US-00013" num="13"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="70PT" align="left" /><colspec colname="2" colwidth="133PT" align="left" /><thead><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="2" align="center">TABLE 13</entry></row><row>&lt;entry /&gt;&lt;entry /&gt;</row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row><row>&lt;entry /&gt;<entry>Message</entry>&lt;entry /&gt;</row><row>&lt;entry /&gt;<entry>Type</entry><entry>Message Function</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;<entry>REQ_DATS</entry><entry>Request New DA Slot Assignment</entry></row><row>&lt;entry /&gt;<entry>REPLY_DATS</entry><entry>Reply to Received REQ_DATS</entry></row><row>&lt;entry /&gt;<entry>CONFIRM</entry><entry>Response to Received REPLY_DATS</entry></row><row>&lt;entry /&gt;<entry>DELETE_TS</entry><entry>Message Indicating Deleted Time Slot</entry></row><row>&lt;entry /&gt;&lt;entry /&gt;<entry>Allocation</entry></row><row>&lt;entry /&gt;<entry>LINK_METRIC</entry><entry>Message Broadcast to Neighbor Nodes</entry></row><row>&lt;entry /&gt;&lt;entry /&gt;<entry>with Link Metric for Each Link to a</entry></row><row>&lt;entry /&gt;&lt;entry /&gt;<entry>Neighbor Node</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0147] An example of DA time slot assignment is shown in FIG. 9. Node 1 wants to add an additional DA time slot allocation for its link (1,2). The corresponding protocol message exchange is shown in TABLE 5. Node 1 initiates the exchange by sending a REQ_DATS (L=(4.2, 5,6)) indicating that it can support allocations of all of slots 5 and 6 and sub-slot 4.2. This list may include all free and DA time slots, the later of which are less needed.

[0148] When the request message is sent, the appropriate changes are made to the time slot and link scheduling message data structures. Node 2 is using time slots 1, 3 and 6 as SP allocations for its links to its 3 neighbors and sub-slots 2.1 and 3.2 as DA allocations. It can select either sub-slot 4.2 or both sub-slots of slot 5. It chooses and sends this choice in the reply message.

[0149] When a reply message is sent the appropriate changes are also made to the time slot and link scheduling message data structures. Finally, when a confirm is sent or received, the state of the appropriate time slots are changed to “sub-slot 4.2 DA allocated to link (1,2).” <tables id="TABLE-US-00014" num="14"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="98PT" align="left" /><colspec colname="2" colwidth="21PT" align="center" /><colspec colname="3" colwidth="98PT" align="left" /><thead><row><entry namest="1" nameend="3" align="center">TABLE 14</entry></row><row>&lt;entry /&gt;</row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row><row><entry>Node 1</entry>&lt;entry /&gt;<entry>Node 2</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>Determines That The</entry>&lt;entry /&gt;&lt;entry /&gt;</row><row><entry>Link From Node 1 to</entry></row><row><entry>Node 2 Requires An</entry></row><row><entry>Additional DA Time Slot</entry></row><row><entry>Send</entry><entry>→</entry><entry>Msg Lost</entry></row><row><entry>REQ_DATS (L= (4.2, 5, 6) )</entry></row><row><entry>Timeout and retry</entry><entry>→</entry><entry>Rcvd</entry></row><row><entry>Resend</entry></row><row><entry>REQ_DATS (L= (4.2, 5, 6) )</entry><entry>←</entry><entry>REQ_DATS (L= (4.2, 5, 6) )</entry></row><row><entry>Rcvd REPLY_DATS(Slot</entry>&lt;entry /&gt;<entry>Send REPLY_DATS(Slot</entry></row><row><entry>4.2)</entry>&lt;entry /&gt;<entry>4.2)</entry></row><row><entry>Send CONFIRM (Slot 4.2)</entry><entry>→</entry><entry>Rcvd CONFIRM (Slot</entry></row><row>&lt;entry /&gt;&lt;entry /&gt;<entry>4.2)</entry></row><row><entry>Slot 4.2 DA Allocated</entry>&lt;entry /&gt;<entry>Slot 4.2 DA Allocated</entry></row><row><entry>to Link (1,2)</entry>&lt;entry /&gt;<entry>to Link (1,2)</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0150] The following approach is used at each network node to allocate the (N−1) available time slots for directional links to neighbor nodes. Using these measures each node will continuously maintain the link metric, <maths id="MATH-US-00007" num="7"><math overflow="scroll"><mrow><msubsup><mi>M</mi><mi>ik</mi><mi>DA</mi></msubsup><mo>,</mo></mrow></math><img file="US20030193908A1-20031016-M00007.TIF" id="EMI-M00007" he="11.02815" wi="216.027" img-format="tif" img-content="mf" /><attachments><attachment idref="MATHEMATICA-00007" attachment-type="nb" file="US20030193908A1-20031016-M00007.NB" /></attachments></maths>

[0151] for each of its links allocated a semi-permanent time slot. Each node will use this link metric to indicate the need for additional transmission time slots to each neighbor node. The largest values of <maths id="MATH-US-00008" num="8"><math overflow="scroll"><msubsup><mi>M</mi><mi>ik</mi><mi>DA</mi></msubsup></math><img file="US20030193908A1-20031016-M00008.TIF" id="EMI-M00008" he="11.02815" wi="216.027" img-format="tif" img-content="mf" /><attachments><attachment idref="MATHEMATICA-00008" attachment-type="nb" file="US20030193908A1-20031016-M00008.NB" /></attachments></maths>

[0152] indicate the links with the greatest need for additional on-demand time slot allocation. A positive value of <maths id="MATH-US-00009" num="9"><math overflow="scroll"><msubsup><mi>M</mi><mi>ik</mi><mi>DA</mi></msubsup></math><img file="US20030193908A1-20031016-M00009.TIF" id="EMI-M00009" he="11.02815" wi="216.027" img-format="tif" img-content="mf" /><attachments><attachment idref="MATHEMATICA-00009" attachment-type="nb" file="US20030193908A1-20031016-M00009.NB" /></attachments></maths>

[0153] indicates the number of additional time slots required, and a negative value of indicates the number of time slots that can be surrendered for reallocation.

[0154] As the metrics, <maths id="MATH-US-00010" num="10"><math overflow="scroll"><mrow><msubsup><mi>M</mi><mi>ik</mi><mi>DA</mi></msubsup><mo>,</mo></mrow></math><img file="US20030193908A1-20031016-M00010.TIF" id="EMI-M00010" he="11.02815" wi="216.027" img-format="tif" img-content="mf" /><attachments><attachment idref="MATHEMATICA-00010" attachment-type="nb" file="US20030193908A1-20031016-M00010.NB" /></attachments></maths>

[0155] are maintained, if the largest link metric indicates a need for an additional sub-slot allocation and if there are sub-slots available either as free slots or as excess DA allocation to other links (again indicated by a small metric), then the process transitions to the add DA slot state and the process of finding a DA sub-slot allocation is initiated.

[0156] As with the semi-permanent time slots, the node need only coordinate the selection of the DA time slot to be assigned for a directional link to a neighbor with that neighbor. This means that a neighbor will send a request to the neighbor for the time slot assignment over the directional link, and receive either a grant of the assignment or a denial of the request over the same link.

[0157] Some initial pseudocode describing the processes required in FIG. 8 has been developed. There are various events that may occur which must be processed by the DA slot assignment process. Event management is done in the idle process as shown in TABLE 6.

[0158] Four categories of events are shown: 1) received message, 2) check timeouts, 3) recalculation of link metrics, and 4) DA time slot needs and DA time slot deletion. Received messages are first checked versus the link scheduling message DB to insure that the message is consistent with the current state of the DB. For example, if we sent a request to a neighbor, the next message expected is a reply.

[0159] To simplify this distributed protocol, only one thread of DA protocol message exchanges is allowed at a time. This is enforced in the procedure by checking the DB to see if other DA message exchanges are ongoing prior to initiating an add DA slot transition or prior to processing a REQ_DATS message. If an addition slot cannot be initiated because another DA protocol thread is currently in process, the addition slot will not be done.

[0160] It can be naturally rescheduled on the next opportunity for recalculation of link metrics and DA time slot needs. Link metrics will be recalculated periodically according to a preset schedule. A link which has a link metric greater than a certain threshold, Max_metric_threshold, is a candidate for obtaining a new DA sub-lot.

[0161] The link with the maximum metric that exceeds this threshold will be selected as the next link to which a new DA sub-slot is allocated. When a new DA sub-slot needs to be allocated and if it satisfies the above conditions, then a transition to the add DA slot state occurs in the DA slot assignment process. <tables id="TABLE-US-00015" num="15"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 15</entry></row><row>&lt;entry /&gt;</row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Procedure for Idle State (DA Event Management)</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;</row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>Case Event Type</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Received Message:</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>If received message is not consistent with the</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>state of the Link Scheduling Message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>DB for that Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Discard Message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Elseif message type = REQ_DATS</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>If no pending DA message activity in the Link</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="56PT" align="left" /><colspec colname="1" colwidth="161PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Scheduling Message DB for link additions</entry></row><row>&lt;entry /&gt;<entry>other than receiving a previous REQ_DATS</entry></row><row>&lt;entry /&gt;<entry>message from Nbr_ID Transition to Process</entry></row><row>&lt;entry /&gt;<entry>REQ_DATS state to process message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Else</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="56PT" align="left" /><colspec colname="1" colwidth="161PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Reject new link and send negative</entry></row><row>&lt;entry /&gt;<entry>REPLY_DATS message to Nbr_ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>End</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Elseif message type = REPLY_DATS</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Transition to Process REPLY_DATS state to</entry></row><row>&lt;entry /&gt;<entry>process message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Elseif message type = CONFIRM</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Transition to Process CONFIRM state to</entry></row><row>&lt;entry /&gt;<entry>process message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Elseif message type = DELETE_TS</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Transition to Process DELETE_TS state to</entry></row><row>&lt;entry /&gt;<entry>process message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>End</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Check Timeouts:</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Check all timeouts</entry></row><row>&lt;entry /&gt;<entry>If Timeout expired for a link in the DA_Req state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Transition to Add DA Slot state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>If Timeout expired for a link in the DA_Reply</entry></row><row>&lt;entry /&gt;<entry>state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Reset Slot Assignment DB for time slot Ns and</entry></row><row>&lt;entry /&gt;<entry>in the Link Message state in</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="56PT" align="left" /><colspec colname="1" colwidth="161PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Link Scheduling Message DB for index Nbr_ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>End</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Recalculate Link Metrics and DA Time Slot Needs:</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Recalculate link metrics</entry></row><row>&lt;entry /&gt;<entry>Send new link metrics to all neighbor nodes in a</entry></row><row>&lt;entry /&gt;<entry>LINK_METRIC message</entry></row><row>&lt;entry /&gt;<entry>Sort link metrics and select Largest_link_metric</entry></row><row>&lt;entry /&gt;<entry>If (no pending DA message activity in the Link</entry></row><row>&lt;entry /&gt;<entry> Scheduling Message DB) and</entry></row><row>&lt;entry /&gt;<entry> (Largest_link_metric &gt; Max_metric_threshold)</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Transition to Add DA Slot state to add new DA</entry></row><row>&lt;entry /&gt;<entry>slot assignment to Nbr_ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>End</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>DA Time Slot Delete:</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Transition to DA TS Delete state to delete Time</entry></row><row>&lt;entry /&gt;<entry>Slot to Nbr_ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>End</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0162] Psuedocode for the additional DA slot process is shown in TABLE 16. This starts a process which requires coordination of the time slot assignment and protocol message exchanges between only the two neighbor nodes. The node requesting the link sends a REQ_DATS message to the candidate neighbor node with the list of acceptable time slots for the link.

[0163] The list of candidate time slots must contain all free sub-slots and all DA sub-slots with a metric below a certain threshold, Min_metric_threshold. The DA time slots may be currently temporarily allocated for other DA traffic. This list will be priority-ordered to indicate the sub-slot preference that causes the least perturbation in the current on-demand time slot assignments. The priority ordering will be first the free time slots followed by the sub-slots with the smallest metrics progressing up to the largest metric less than the Min_metric_threshold.

[0164] In order to simplify this distributed protocol, only one thread of DA protocol message exchanges is allowed at a time. This is enforced in the idle procedure. The REQ_DATS message is only sent once, but it could be unsuccessful if the neighbor node is currently processing another DA protocol exchange. In this case, the node will eventually receive a negative REPLY_DATS message. The attempt to add the DA slot may be made again in this case if this link has the largest metric the next time the link metrics are evaluated. Once the REQ_DATS message is sent the process returns to the idle state where other events can be processed. <tables id="TABLE-US-00016" num="16"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 16</entry></row><row>&lt;entry /&gt;</row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Procedure for Addition of a New DA Subslot to the Link to</entry></row><row><entry>Node Nbr_ID (Generate REQ_DATS Message)</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;</row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Construct list Ls of time slots (subslots) to offer to</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>Nbr_ID from Free time slots and</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>DA subslots with excess capacity (Link_metric &lt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>Min_metric_threshold)</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Append list Ls to REQ_SPTS message and send to Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Setup timeout and Link Message state in Link Scheduling</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>Message DB for index</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Nbr_ID and in Slot Assignment DB</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0165] The neighbor receiving a REQ_DATS message will have its DA slot assignment process transition to the REQ_SPTS state. The procedure for processing this message is shown in TABLE 17. This procedure takes the offered list of sub-slots, Ls, and selects its preferred sub-slot, Ns. The sub-slot accepted is the first sub-slot on the list, ls, that is either marked free in the slot assignment DB or is DA allocated with a link metric less than Min_metric_threshold. Then a REPLY_DATS reply message with this selection is sent. If the link cannot be accepted or if there is another ongoing DA slot assignment in process, a negative REPLY_DATS reply message is sent. The procedure also makes the appropriate modifications to the state in the link scheduling message DB and the slot assignment DB. <tables id="TABLE-US-00017" num="17"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 17</entry></row><row>&lt;entry /&gt;</row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Procedure for Processing REQ_DATS Message (from Nbr_ID)</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;</row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Examine prioritized list Ls of the available subslots</entry></row><row>&lt;entry /&gt;<entry>received from Nbr_ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>and compare with the current allocations in</entry></row><row>&lt;entry /&gt;<entry>the Slot Assignment DB</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Select the best assignment = Ns as the subslot on the</entry></row><row>&lt;entry /&gt;<entry>list that is either marked Free in</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>the Slot Assignment DB or is DA allocated with</entry></row><row>&lt;entry /&gt;<entry>Link_metric &lt;</entry></row><row>&lt;entry /&gt;<entry>Min_metric_threshold</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>If no subslot satisfies conditions for acceptance</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Reject new link and send negative REPLY_DATS message to</entry></row><row>&lt;entry /&gt;<entry>Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Return to Idle state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>Else</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Make appropriate modification to the Slot Assignment DB</entry></row><row>&lt;entry /&gt;<entry> (mark it as DA_Reply)</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>for time slot Ns</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>If time slot Ns was DA allocated</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Send DELETE_TS to the neighbor node allocated the</entry></row><row>&lt;entry /&gt;<entry>DA time slot</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>End</entry></row><row>&lt;entry /&gt;<entry>Append time slot choice, Ns, to REPLY_DATS message and</entry></row><row>&lt;entry /&gt;<entry>send to Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Setup timeout and Link Message state (to DA_Reply with</entry></row><row>&lt;entry /&gt;<entry>time slot Ns) in Link</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Scheduling Message DB for index Nbr_ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Return to Idle state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>End</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0166] A received REPLY_DATS message is processed as shown in TABLE 18. The choice of sub-slot, Ns, received from the neighbor node is extracted from the message. We require the node to confirm this reply with either a positive or negative CONFIRM message that indicates that it will agree to use the allocated time slot. As indicated in the SP allocation process, this three-way handshake eliminates uncertainty in the outcome of the scheduling process.

[0167] If the REPLY_DATS message is a positive reply, then the choice of sub-slot, Ns, is examined to see if it is still an allowable assignment for a new DA sub-slot for the new link. If it is allowable, then the appropriate modifications to the state in the slot assignment and link scheduling message databases are made. Then a positive CONFIRM message is returned.

[0168] If the received REPLY_SPTS message was negative, then the slot assignment and link scheduling message databases are reset for this Nbr_ID. Otherwise, if the choice of Ns is no longer allowable, then the link scheduling message database is reset for this Nbr_ID. Then a negative CONFIRM message is sent to the neighbor node rejecting the link. <tables id="TABLE-US-00018" num="18"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 18</entry></row><row>&lt;entry /&gt;</row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Procedure for Processing REPLY_DATS Message from Nbr_ID</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;</row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Extract time slot choice Ns from the REPLY_DATS message from</entry></row><row>&lt;entry /&gt;<entry>Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>If (positive REPLY_DATS message) and (choice of Ns is still</entry></row><row>&lt;entry /&gt;<entry>allowable from Slot</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Assignment DB)</entry></row><row>&lt;entry /&gt;<entry>Make appropriate modification to the Slot Assignment DB</entry></row><row>&lt;entry /&gt;<entry> (mark it as DA_Reply)</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>for time slot Ns and in the Link Message state in</entry></row><row>&lt;entry /&gt;<entry>Link Scheduling Message DB</entry></row><row>&lt;entry /&gt;<entry>for index Nbr_ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>If time slot Ns was DA allocated</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Send DELETE_TS to the neighbor node allocated the</entry></row><row>&lt;entry /&gt;<entry>DA time slot</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>End</entry></row><row>&lt;entry /&gt;<entry>Create CONFIRM message for Ns and send to Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Return to Idle state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Elseif negative REPLY_DATS message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Reset Slot Assignment DB for time slot Ns and in the</entry></row><row>&lt;entry /&gt;<entry>Link Message state in</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Link Scheduling Message DB for index Nbr_ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Return to Idle state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Else</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Reset Link Message state in Link Scheduling Message DB</entry></row><row>&lt;entry /&gt;<entry>for index Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Send negative CONFIRM message to Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Return to Idle state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>End</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0169] TABLE 19 shows the procedure for processing CONFIRM messages. If the CONFIRM is positive, the selected sub-slot to be added to the allocation to the link to Nbr_ID. The assigned time slot, Ns, is marked DA_Alloc in the slot assignment DB, and the link message state in the link scheduling message DB is reset for index Nbr_ID. If the message was a negative CONFIRM, then the slot assignment and link scheduling message databases are reset for this sub-slot. <tables id="TABLE-US-00019" num="19"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 19</entry></row><row>&lt;entry /&gt;</row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Procedure for Processing CONFIRM Message from Nbr_ID</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;</row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>If positive CONFIRM message</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Make appropriate modification to the Slot Assignment DB</entry></row><row>&lt;entry /&gt;<entry> (mark it as DA_Alloc)</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>for time slot Ns</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Reset Link Message state in Link Scheduling Message DB</entry></row><row>&lt;entry /&gt;<entry>for index Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Return to Idle state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Else</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Reset the Slot Assignment DB (mark it as Free) for time</entry></row><row>&lt;entry /&gt;<entry>slot Ns</entry></row><row>&lt;entry /&gt;<entry>Reset Link Message state in Link Scheduling Message DB</entry></row><row>&lt;entry /&gt;<entry>for index Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Return to Idle state</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>End</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0170] An allocated time slot may need to be deallocated for one of several reasons. If during the course of normal operation a link goes down or becomes unreliable, then the topology control function gets involved to address the unreliable link problem. Ultimately, it may generate a topology change (e.g., a link deletion) event directing the SP slot assignment process to delete all slots assigned to the link.

[0171] The steps involved in this procedure are shown in TABLE 11. The link is de-allocated by sending a DELETE_TS message from the node requesting the de-allocation of all the time slots which are shared with the other node with. In addition, the appropriate entries in the link scheduling message DB and the slot assignment DB are reset. <tables id="TABLE-US-00020" num="20"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 20</entry></row><row>&lt;entry /&gt;</row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Procedure for DA TS Delete to Node Nbr_ID (Generate</entry></row><row><entry>DELETE_TS Message)</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;</row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>Construct message, DELETE_TS, containing the DA subslot, Ns,</entry></row><row><entry>that is to be deleted</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>and send to Nbr_ID</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>Reset Link Scheduling Message DB for index Nbr_ID and Slot</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Assignment DB for subslot Ns</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>Return to Idle state</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0172] Table 21 shows the procedure for processing a received DELETE_TS message. The subslot, Ls, to be deallocated is extracted from the message. Then the appropriate state in the slot assignment DB and in the link scheduling message DB is reset. <tables id="TABLE-US-00021" num="21"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry namest="1" nameend="1" align="center">TABLE 21</entry></row><row>&lt;entry /&gt;</row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Procedure for Processing DELETE_TS Message from Nbr_ID</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;</row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row>&lt;entry /&gt;<entry>Extract DA subslot, Ns, from the DELETE_TS message from</entry></row><row>&lt;entry /&gt;<entry>Nbr_ID</entry></row><row>&lt;entry /&gt;<entry>Reset the Slot Assignment DB (mark it as Free) for subslot</entry></row><row>&lt;entry /&gt;<entry>Ns</entry></row><row>&lt;entry /&gt;<entry>Reset Link Message state in Link Scheduling Message DB for</entry></row><row>&lt;entry /&gt;<entry>subslot Ns</entry></row><row>&lt;entry /&gt;<entry>Return to Idle state</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0173] The link scheduling algorithm is also applicable to multiple simultaneous beams generated by the phased array antenna <b>16</b>. Assume the extension to a system with nodes each employing multiple antenna beams with separate receivers such as a multiple beam phased array (or other types of multiple, directional antennas). Furthermore, assume that all nodes do not all have to have the same number of beams, i.e., node k has B_kbeams. This is equivalent to B_kparallel links possible at any time slot.

[0174] We are extending the previous discussion (which assumed a single steered beam) to allow the B_kbeams to be time-shared among a set of neighbor nodes larger than B_k. Even though the nodes may each have different numbers of beams, all nodes must use a common time slot format and frame with a number of time slots per frame for each beam equal to N_frame.

[0175] Consider an upper limit at any node k on the number of semi-permanently (SP) assigned time slots on any one of its B_kbeams (and therefore the maximum number of allowable neighbor nodes per beam) to be denoted by N_beam. The value of N_beamis dependent only on the number of time slots per frame and not the number of beams. As in (3) we will specify that N_beammust satisfy the following equation:

<i>N</i>_frame≧2<i>·N</i>_beam−1  (7)

[0176] Assume that all nodes in a network are connected by directional links, where node k has B_kbeams with beam sharing by time hopping and pointing to its neighbor nodes. Further, assume the number of neighbors allowed per beam is equal to N_beam, the fixed limit on the allowable number of semi-permanent time slots allowed per beam (with one SP time slot allocated per neighbor).

[0177] If the fixed value of N_beamfor each beam at each neighbor node satisfies (7), then all nodes can select a different semi-permanent time slot for each of these links and each of its beams by mutual agreement with the neighbor for that link without regard to what colors other nodes are selecting more than one hop away. This allows each node to select its N_beamsemi-permanent time slots for each beam in a very direct fashion by communicating only with its neighbor node. By following this strategy, each node is able to support at least

<i>N</i>_k<i>=B</i>_k<i>·N</i>_beam  (8)

[0178] neighbors and each allocated a single SP time slot with no more than N_beamsuch time slots allocated per beam.

[0179] Verification that N_beamneighbors per beam can be supported as long as (7) is satisfied follows directly from the verification of the observation for the single beam case. Then if all B_kbeams have their SP time slots scheduled in the same fashion, it is obvious that the number of neighbor nodes that can be supported is the product of the number of beams and the number of neighbors per beam resulting in (8).

[0180] An example of SP time slot assignment between two nodes with an unequal number of beams per node is shown in FIG. 10. In this example node 1 has 2 beams and node 2 has 3 beams. While the two nodes have different numbers of beams, both nodes must use the same frame structure. In this example N_frame=5 time slots per frame. From (7) and (8), this allows node 1 to have a maximum of 6 neighbors and node 2 to have a maximum of 9 neighbors.

[0181] Initially both nodes have one less than the maximum number of neighbors they are allowed under the constraints of (7) and (8). The SP beam/time slots allocations are shown for each link. These nodes can add an additional link between themselves while still satisfying the constraints of (7) and (8). The link scheduling protocol will find an acceptable beam/time slot for the SP allocation for each node, and it operates in essentially the same way it did with the single beam case.

[0182] The corresponding protocol message exchange is shown in TABLE 22. Node 1 initiates the exchange by sending a REQ_SPTS(L=(1, 2, 3)) with a list of at least N_beamcandidate time slots. Note the 3 beam IDs are denoted by a, b and c, and the slot number is denoted by the subscript on the beam ID. Node 1 had to identify that it had used all 3 allowable SP time slots on beam a, but it had allocated only 2 of the 3 allowable SP time slots on its beam b.

[0183] Thus, it sent a list of the 3 SP time slots (available on beam b) to node 2. This list may include all free and DA time slots on this beam. When the request message is sent, the appropriate changes are made to the time slot and link scheduling message data structures. Node 2 has previously allocated SP all available SP time slots on beams a and b for its links to its 8 neighbors.

[0184] Thus, beam c is the only beam that can accept a new SP allocation. When it receives the REQ_SPTS(L=(1, 2, 3)) from node 1, it selects beam/time slot c₃as the only one that will work for the new link (having previously allocated c₁and c₂as SP time slots). It sends this choice in the reply message. When a reply message is sent the appropriate changes are also made to the beam/time slot and link scheduling message data structures. Finally, when a confirm is sent or received, the state of the appropriate time slots are changed to “SP allocated to link (1,2).” <tables id="TABLE-US-00022" num="22"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="91PT" align="left" /><colspec colname="2" colwidth="28PT" align="center" /><colspec colname="3" colwidth="84PT" align="left" /><thead><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="3" align="center">TABLE 22</entry></row><row>&lt;entry /&gt;&lt;entry /&gt;</row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="3" align="center" rowsep="1" /></row><row>&lt;entry /&gt;<entry>Node 1</entry>&lt;entry /&gt;<entry>Node 2</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;<entry>Receives Link Add Event</entry>&lt;entry /&gt;&lt;entry /&gt;</row><row>&lt;entry /&gt;<entry>From Its Topology</entry></row><row>&lt;entry /&gt;<entry>Control For A Link From</entry></row><row>&lt;entry /&gt;<entry>Node 1 to Node 2</entry></row><row>&lt;entry /&gt;<entry>Send REQ_SPTS (L= (1, 2,</entry><entry>→</entry><entry>Rcvd Send</entry></row><row>&lt;entry /&gt;<entry>3) )</entry>&lt;entry /&gt;<entry>REQ_SPTS (L= (1, 2, 3) )</entry></row><row>&lt;entry /&gt;<entry>Rcvd REPLY_SPTS (Slot 3)</entry><entry>←</entry><entry>Send REPLY_SPTS (Slot</entry></row><row>&lt;entry /&gt;&lt;entry /&gt;&lt;entry /&gt;<entry>3)</entry></row><row>&lt;entry /&gt;<entry>Send CONFIRM (Slot 3)</entry><entry>→</entry><entry>Rcvd CONFIRM (Slot 3)</entry></row><row>&lt;entry /&gt;<entry>Beam / Slot b₃</entry>&lt;entry /&gt;<entry>Beam / Slot c₃</entry></row><row>&lt;entry /&gt;<entry>Allocated to Link (1,2)</entry>&lt;entry /&gt;<entry>Allocated to Link</entry></row><row>&lt;entry /&gt;&lt;entry /&gt;&lt;entry /&gt;<entry>(1,2)</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0185] The changes that are required to implement the multiple beam scheduling algorithm/protocol are straightforward and are as follows. Add the beam ID as a variable in the state of the time slot DB and the link scheduling message DB. Use (7) and (8) as the criteria for determining if it is possible to schedule a new SP time slot. We specify a value for the parameters N_frameand N_beamfor the network.

[0186] To offer a new SP time slot to a potential neighbor, the algorithm must first find a beam for which the number of neighbors is less than N_beam. This beam can then be used to add the new neighbor. The REQ_SPTS message that the node sends to its neighbor will specify N_beamavailable time slots for that beam that are not currently SP allocated.

[0187] Having received an REQ_SPTS message the node must find one of its beams for which the number of neighbors is less than N_beam. This beam can then be used to add the new neighbor. Comparing the list of N_beamtime slots in the received REQ_SPTS message with the N_beamtime slots not currently allocated in the selected beam, at least one time slot can be found that is common to both lists. That time slot can be selected as the time slot to send in the REPLY_SPTS message. Once the originating node receives the REPLY_SPTS message, both nodes will have selected their beam and the common time slot allocation.

[0188] This example implicitly assumed that a single frequency band is used for each of the beams. In this case, a node could have several beams simultaneously communicating over the same band without interference. This interference-free operation may be difficult to support in practice. A similar formulation of the problem could be done with each beam operating in a different frequency band, i.e., beams a, b, and c in FIG. 10 each use a different frequency band. In terms of the scheduling algorithm, we would apply the same constraints on the allocation of SP time slots. However, in actually allocating the time slot/beam combinations we would need to find an allocation such that the two nodes are using the same beam (equivalent to using the same band) as well as the same time slot. This equivalent to making each beam/time slot combination different from the scheduling perspective. Thus, the number of available time slots is the number of beams multiplied by the frame size. In this case the constraint on assigning SP time slots to potential neighbors is given by

<i>B·N</i>_frame≧2<i>·N−</i>1,  (9)

[0189] where B denotes the number of beams. This constraint on the number of neighbors is slightly more restrictive than that of (7) and (8) because of the requirement that nodes which share an SP time slot must also use the same beam/frequency channel as well as the same time slot. For the example N_frame=5 and B=3, then the constraint of (9) allows 8 neighbors for each node whereas the constraints of (7) and (8) will allow 9 neighbors for each node.

[0190] The example problem in FIG. 10 has 2 nodes each with 3 beams with each beam operating in a different frequency band, i.e., beams a, b, and c each use a different frequency band. Assume also that the frame size is 5. Both nodes have already committed 7 SP time slots to neighbor nodes and thus, from (9), they can each add an additional neighbor with an SP time slot allowing them to establish a link between them. The committed SP time slots are indicated in the figure, and the message exchanges required to establish the SP time slot assignment and the new link are indicated in Table 23. The message exchange is initiated by node 1 by sending a REQ_SPTS (L=(a₄, a₅, b₃, b₄, b₅, c₃, c₄, c₅)) message to node 2 which must include the 8 beam/time slot combinations it has not previously allocated as SP time slots. In this example, node 2 had already allocated 7 beam/time slot combinations that were not used by node 1 (which were in the list of 8 beam/time slot combinations received in the REQ_SPTS message). Thus, by (9) there must be at least one remaining beam/time slot combination that it can select for allocation (c₅). This is the SP beam/time slot combination allocated to the link between nodes 1 and 2 as show in both FIG. 11 and Table 23. <tables id="TABLE-US-00023" num="23"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="91PT" align="left" /><colspec colname="2" colwidth="28PT" align="center" /><colspec colname="3" colwidth="84PT" align="left" /><thead><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="3" align="center">TABLE 23</entry></row><row>&lt;entry /&gt;&lt;entry /&gt;</row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="3" align="center" rowsep="1" /></row><row>&lt;entry /&gt;<entry>Node 1</entry>&lt;entry /&gt;<entry>Node 2</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row>&lt;entry /&gt;<entry>Receives Link Add Event</entry>&lt;entry /&gt;&lt;entry /&gt;</row><row>&lt;entry /&gt;<entry>From Its Topology</entry></row><row>&lt;entry /&gt;<entry>Control For A Link From</entry></row><row>&lt;entry /&gt;<entry>Node 1 to Node 2</entry></row><row>&lt;entry /&gt;<entry>Send REQ_SPTS(L= (a₄,</entry><entry>→</entry><entry>Rcvd Send</entry></row><row>&lt;entry /&gt;<entry>a₅, b₃, b₄, b₅, c₃, c₄,</entry>&lt;entry /&gt;<entry>REQ_SPTS(L= (a₄, a₅,</entry></row><row>&lt;entry /&gt;<entry>c₅) )</entry>&lt;entry /&gt;<entry>b₃, b₄, b₅, c₃, c₄,</entry></row><row>&lt;entry /&gt;&lt;entry /&gt;&lt;entry /&gt;<entry>c₅) )</entry></row><row>&lt;entry /&gt;<entry>Rcvd REPLY_SPTS</entry><entry>←</entry><entry>Send REPLY_SPTS</entry></row><row>&lt;entry /&gt;<entry>(Beam/Slot c₅)</entry>&lt;entry /&gt;<entry>(Beam/Slot c₅)</entry></row><row>&lt;entry /&gt;<entry>Send CONFIRM (Beam/Slot</entry><entry>→</entry><entry>Rcvd CONFIRM</entry></row><row>&lt;entry /&gt;<entry>c₅)</entry>&lt;entry /&gt;<entry>(Beam/Slot c₅)</entry></row><row>&lt;entry /&gt;<entry>Beam / Slot c₅</entry>&lt;entry /&gt;<entry>Beam / Slot c₅</entry></row><row>&lt;entry /&gt;<entry>Allocated to Link (1,2)</entry>&lt;entry /&gt;<entry>Allocated to Link</entry></row><row>&lt;entry /&gt;&lt;entry /&gt;&lt;entry /&gt;<entry>(1,2)</entry></row><row>&lt;entry /&gt;<entry namest="OFFSET" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0191] The present invention thus provides a fully distributed link scheduling algorithm and protocol for phased array networks. The description of the algorithm/protocol details assumed the case of a single directional beam per node, which is time-shared and pointed toward neighbor nodes during the allocated time slot for that access. However, the approach can be used for an arbitrary number of steered beams per node.

[0192] Many modifications and other embodiments of the invention will come to the mind of one skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the invention is not to be limited to the specific embodiments disclosed, and that modifications and embodiments are intended to be included within the scope of the appended claims.