Long range scheduling for directional antenna manet networks
Abstract
Method and apparatus for scheduling time division multiple access (TDMA) communications among a plurality of peer nodes arranged to form a wireless ad hoc mobile network. The peer nodes communicate with each other using directional antennas and a TDMA process. The method includes a scheduling process for scheduling at least one transmit time slot during which a first one of the plurality of peer nodes transmits wireless data to a second one of the plurality of peer nodes.

Term
1.9 yearsto projected expiry
Projected expiry 31 July 2028, counted from filing; an application has no term until it is granted.
- Priority
- Filed
- Published
- Today
- Projected expiry
10 claims: 1 independent, 9 dependent
- 1A method for scheduling time division multiple access (TDMA) communications among a plurality of peer nodes using directional antennas in a mobile ad hoc network, comprising:arranging a plurality of peer nodes to form a wireless ad hoc mobile network, said peer nodes communicating with each other using directional antennas and a TDMA process;automatically scheduling at least one transmit time slot during which a first one of said plurality of peer nodes transmits wireless data to a second one of said plurality of peer nodes;wherein said scheduling step includes automatically selecting a candidate time slot for said transmit time slot and determining whether transmissions during said candidate time slot will (1) cause interference with communications of any of said plurality of peer nodes that are located in a defined transmit antenna beam of said first node, or (2) be subject to interference when received at said second node resulting from transmissions from any of said plurality of peer nodes located in a defined receive antenna beam of said second node.
75 paragraphs, as filed
0001The inventive arrangements relate to directional networks that can cover terrestrial and airborne nodes over hundreds of nautical miles, and more particularly to long range TDMA time slot scheduling in peer-to-peer directional networks.
0002Peer-to-peer mobile ad hoc networks (MANET) using directional antennas are known in the art. These MANET networks can use a variety of communications formats including Time Division Multiplexed Access (TDMA) arrangements. Further, they are characterized by independence from fixed infrastructures and by peer-to-peer distributed control mechanisms and protocols. In TDMA type MANET networks, each node can communicate during a specified time period or time slot. In order to coordinate such communications, each node can include a clock which is synchronized with a highly stable time reference. For example, this stable time reference can be derived from a satellite-based GPS signal. It should be noted that TDMA cellular systems often rely on synchronization to base stations to establish system timing and to compensate for propagation delay differences. Such TDMA cellular systems include, but are not limited to, global systems for mobile communications (GSM), Integrated Digital Enhanced Network (iDENs) systems, 802.16 based broadband wireless access network systems, and TDMA satellite communications (SATCOM) systems.
0003Still, each TDMA node can be expected to have a significant total time base uncertainty. Also, propagation delay between nodes can create additional timing uncertainties that change in real time as the mobile nodes move relative to one another. In order to manage these timing uncertainties, prior art systems use a base station infrastructure to create a hub and spoke typology. These base stations are usually, but not necessarily, fixed in location. The mobile nodes operate as "spokes" or "clients" to the basestation hubs and synchronize their transmissions to those base stations.
0004A MANET is an infrastructureless network that uses peer-to-peer control mechanisms and therefore does not have base stations to provide a central timing reference. Therefore, there is a need in a TDMA MANET for a new time synchronization method that can compensate for variable propagation delay and other propagation uncertainty in the absence of a central infrastructure.
0005In a TDMA MANTET, a transmitted RF burst is can be transmitted within a time slot as close to the beginning of the time slot as possible. The time slot length can be selected to exceed the maximum RF burst length by an amount of time referred to as the "guard time." This guard time is used to accommodate any timing uncertainties at either the transmitter or receiver, and the maximum propagation time delay. If the range delay between the transmit node and the receive node exceeds the allocation in the guard time, a maximum length RF burst will spill over into the following time slot at the receiver. This spillover can cause interference if such following time slot is in use for communications as between other nodes.
0006Conventional MANET networks using TDMA generally choose a guard time which is based (at least in part) on the maximum permitted range between nodes. In this regard, networks which are designed to accommodate larger distances between nodes can require larger guard times. These larger guard times are necessary to accommodate potentially longer propagation delays between distant nodes. This approach can provide acceptable results for a limited network range. However, for networks operating over hundreds of nautical miles, the guard time can become relatively lengthy in duration. Such lengthy guard periods restrict the available time for other nodes to communicate with each other, leading to inefficiencies in the overall network. For example, a system which has 88% efficiency with an operating range of 11 nautical miles can have an efficiency of only 16% if the operating range is extended to 440 nautical miles.
0007In order to address this problem, several existing TDMA wireless systems have used range adjusted timing systems. However, such systems have generally only been applied in hub-spoke type networks. The problem becomes more considerably more complex in the case of ad-hoc peer-to-peer networks. Accordingly, a new approach is needed for ad-hoc peer-to-peer communications networks to facilitate TDMA communications which are capable of providing efficient communications over larger geographic areas.
0008The invention concerns a method and apparatus for scheduling time division multiple access (TDMA) communications among a plurality of nodes arranged to form a wireless ad hoc mobile network. The nodes communicate with each other using directional antennas and a TDMA scheduling process. The nodes have knowledge of the range between the transmitting node and other nodes within the radio line of sight of the transmitting node. The method includes a scheduling process for scheduling at least one transmit time slot during which a first one of the plurality of nodes transmits wireless data to a second one of the plurality of nodes. The scheduling process includes automatically selecting a candidate time slot for the transmit time slot. The scheduling process also includes determining whether transmissions during the candidate time slot will (1) cause interference with communications of any of the plurality of nodes that are located in a defined transmit antenna beam of the first node, or (2) be subject to interference when received at the second node as a result of transmissions from any of the plurality of nodes located in a defined receive antenna beam of the second node.
0009A data epoch is defined for the TDMA process. The data epoch includes a recurring time period which defines an overall timing cycle for the TDMA process. Each data epoch is sub-divided in time to form a plurality of mini-slots, each comprising a fractional duration of the data epoch. The scheduling process includes selecting the candidate time slot to have a duration which includes a plurality of M contiguous mini-slots. The scheduling process further includes automatically selecting the candidate time slot to include any contiguous group of M mini-slots contained within the data epoch.
0010The scheduling step further includes automatically selecting a receive time slot for the second node. The receive time slot length corresponds to the transmit time slot, but the arrival time is automatically adjusted in time to compensate for a propagation delay between the first node and the second node, which is directly known a priori or derived from prior knowledge of the range between the nodes. In this regard, the receive time slot can comprise a different contiguous group of mini-slots as compared to the transmit time slot. Significantly, the second node automatically determines the receive time slot exclusive of any centralized controller for the mobile ad hoc network. According to a preferred embodiment, the scheduling process is a distributed process which is cooperatively performed in a process which involves at least at the first node and the second node.
0011The scheduling step further includes automatically selecting an alternative candidate time slot. For example, the alternative candidate time slot will be selected if it is determined that transmissions from the first node to the second node during the initially selected candidate time slot will (1) cause interference with communications of any of the plurality of nodes that are located in the defined transmit antenna beam of the first node, or (2) be subject to interference when received at the second node as a result of transmissions from any of the plurality of nodes located in the defined receive antenna beam of the second node.
0012The method also includes a second scheduling step. The second scheduling step involves scheduling at least a second transmit time slot during which the second one of the plurality of nodes to transmit wireless data to the first one of the plurality of nodes. The second scheduling step also makes use of a distributed scheduling process. The second scheduling step includes automatically selecting a second candidate time slot for the second transmit time slot and determining whether transmissions during the second candidate time slot will (1) cause interference with communications of any of the plurality of nodes that are located within the radio line of sight of the second node, or (2) be subject to interference when received at the first node as a result of transmissions from any of the plurality of nodes located in a defined receive antenna beam of the first node. If the nodes use directional antennas, then this step includes a consideration of the antenna pattern and beam location when the potential to cause interference is evaluated.
0013The inventive arrangements also include an alternative method for scheduling time division multiple access (TDMA) communications among a plurality of nodes using directional antennas in a mobile ad hoc network. The alternative method includes arranging a plurality of nodes to form a wireless ad hoc mobile network. The nodes communicate with each other using directional antennas and a TDMA process. The method includes using a peer-to-peer distributed scheduling process. The distributed scheduling process includes automatically scheduling for each node at least one transmit time slot for transmitting wireless data to a neighboring one of the plurality of nodes. The method also includes automatically scheduling for each node a receive time slot for receiving signals transmitted from a neighboring one of the plurality of nodes during a respective one of the transmit time slots. Significantly, each of the receive time slots corresponds to a time of a respective one of the transmit time slots, but is automatically adjusted delayed in time to compensate for a propagation delay between nodes.
0014The scheduling step further includes automatically selecting at each node a candidate time slot for the transmit time slot and determining whether transmissions during the candidate time slot will (1) cause interference with communications of any of the plurality of nodes that are located in a defined transmit antenna beam of the node, or (2) be subject to interference when received at the neighboring node resulting from transmissions from any of the plurality of nodes located in a defined receive antenna beam of the neighboring node.
0015In the alternative embodiment, a data epoch is defined for the TDMA process. The data epoch includes a recurring time period which defines an overall timing cycle for the TDMA system. Each data epoch is sub-divided in time to form a plurality of mini-slots, each comprising a fractional duration of the data epoch. Significantly, the transmit time slot is selected to have a duration which includes a plurality of M contiguous mini-slots. The scheduling process further includes automatically selecting the transmit time slot to include any contiguous group of M mini-slots contained within the data epoch.
0016According to yet another embodiment, the invention includes a distributed system for scheduling time division multiple access (TDMA) communications among a plurality of nodes using any combination of omni or directional antennas in a mobile ad hoc network. The system includes a plurality of nodes arranged to form a wireless ad hoc mobile network that communicate with each other using directional antennas and a TDMA process. A processor for performing scheduling functions is provided at each node. The processor at each node cooperates with processors at other nodes to cooperatively schedule at least one transmit time slot during which a first one of the plurality of nodes transmits wireless data to a second one of the plurality of nodes. The processor is further configured to automatically select a candidate time slot for the transmit time slot. The processor cooperates with at least one other processor in another node to determine whether transmissions during the candidate time slot will (1) cause interference with communications of any of the plurality of nodes that are located in a defined transmit antenna beam of the first node, or (2) be subject to interference when received at the second node resulting from transmissions from any of the plurality of nodes located in a defined receive antenna beam of the second node.
0017The TDMA process includes a data epoch comprising a recurring time period which defines an overall timing cycle for the TDMA process. Each data epoch is sub-divided in time to form a plurality of mini-slots, each comprising a fractional duration of the data epoch. The processor in each node that is used for scheduling processing is configured for selecting the candidate time slot to have a duration which includes a plurality of M mini-slots. Notably, the processor is configured to automatically select the candidate time slot to include any contiguous group of M mini-slots contained within the data epoch.
0018The processor at each node is also configured to automatically select a receive time slot for the second node corresponding to a time of the transmit time slot, wherein the receive time slot is automatically adjusted in time to compensate for a propagation delay between the first node and the second node. Significantly, the processor used for scheduling at the second node automatically determines the receive time slot exclusive of any centralized controller for the mobile ad hoc network. The receive time slot includes a different contiguous group of mini-slots as compared to the transmit time slot.
0019The TDMA process includes a "neighbor database" at each node that maintains knowledge of the location of or equivalently the relative range and angles between the plurality of nodes within the radio line of sight of the first node. The neighbor database also includes knowledge of the currently scheduled transmit and receive timeslots at the plurality of nodes included in the neighbor database.
0020The TDMA process includes a method for populating the database of node locations of the plurality of nodes. Those skilled in the art will appreciate that there are numerous methods available to populate a database with this information. The methods include broadcast or multicast transmissions between the nodes or downloads from an external source. <ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001">FIG. 1</figref> is a drawing that is useful for understanding timing problems which occur in mobile ad hoc networks.</li><li><figref idref="f0002">FIG. 2</figref> is a timing diagram that is useful for understanding timing problems which occur in mobile ad hoc networks.</li><li><figref idref="f0002">FIG. 3</figref> is a timing diagram that is useful for understanding timing problems which occur in mobile ad hoc networks.</li><li><figref idref="f0003">FIG. 4</figref> is a block diagram of a wireless mobile node that can be used to implement the present invention.</li><li><figref idref="f0004">FIG. 5</figref> is a timing diagram that is useful for understanding a timing relation between data epochs, mini-slots, and time slots.</li><li><figref idref="f0005">FIG. 6</figref> is a drawing that shows a planar geometry of several nodes which is useful for understanding the invention.</li><li><figref idref="f0005">FIG. 7</figref> is a timing diagram that is useful for understanding potential sources of interference in <figref idref="f0005">FIG. 6</figref>.</li><li><figref idref="f0006">FIG. 8</figref> is a drawing that shows the planar geometry of several nodes in <figref idref="f0005">FIG. 6</figref> with different antenna pattern overlays.</li><li><figref idref="f0006">FIG. 9</figref> is a timing diagram that is useful for understanding potential sources of interference in <figref idref="f0006">FIG. 8</figref>.</li><li><figref idref="f0007">FIG. 10</figref> is a flowchart that is useful for understanding an interaction among various nodes in a mobile ad hoc network.</li><li><figref idref="f0008">FIG. 11</figref> is a flowchart that provides additional detail relating to step 1016 in <figref idref="f0007">FIG. 10</figref>.</li><li><figref idref="f0009">FIG. 12</figref> is a flowchart that provides additional detail relating to step 1102 in <figref idref="f0008">FIG. 11</figref>.</li><li><figref idref="f0010">FIG. 13</figref> is a flowchart that provides additional detail relating to step 1106 in <figref idref="f0008">FIG. 11</figref>.</li><li><figref idref="f0011">FIG. 14</figref> is a flowchart that provides additional detail relating to step 1210 in <figref idref="f0009">FIG. 12</figref>.</li><li><figref idref="f0012">FIG. 15</figref> is a flowchart that provides additional detail relating to step 1308 in <figref idref="f0010">FIG. 13</figref>.</li></ul>
0021Conventional approaches to peer-to-peer, ad-hoc TDMA communication networks are based on knowing only the maximum range between nodes. This concept is illustrated in <figref idref="f0001 f0002">FIGS. 1-3</figref>. <figref idref="f0001">FIG. 1</figref> shows a two-dimensional layout of a group of nodes in a prior art TDMA based mobile ad hoc network (MANET). In <figref idref="f0001">FIG. 1</figref>, the transmitting node is node 102. In this example, the system has a guard time that is designed to accommodate maximum range indicated by the radius of the circle 103. Nodes 104 are within this radius. Node 106-1 is outside this radius. Node 106-2 is further outside the radius as compared to node 106-1.
0022Referring now to <figref idref="f0002">Figure 2</figref> there is shown a conventional time slot 200. The time slot has a duration 201, a maximum RF burst time 202, and a guard time 203. The guard time is provided to accommodate range uncertainty as well as other timing uncertainties at the receiver and transmitter. An RF burst 206 is shown within the maximum burst time 202. Referring again to <figref idref="f0001">FIG. 1</figref>, it can be understood that transmissions from node 102 to node 106-1 or 106-2, which are of the maximum RF burst length, will contaminate the following (or later) time slot for node 106-1, 106-2 because these nodes are each located beyond the radius of the maximum range circle 103.
0023An alternative illustration of the foregoing concept is provided in <figref idref="f0002">Figure 3</figref>. The transmit RF burst 206 of maximum length is shown in time slot n. At a node 104 the RF burst 206 arrives within slot n because node 104 is within the maximum guard time protected range. When RF burst 206 is received at a node 106-1 (beyond maximum protected range) the transmission will cause interference for node 106-1 in time slot n+1. At a more distant node 106-2, the transmission will cause interference in time slot node n+2. As will be appreciated by those skilled in the art, transmitted RF bursts 206 that are not of maximum length may or may not contaminate the following time slot(s).
0024In <figref idref="f0001 f0002">FIGS. 1-3</figref>, the length of the guard period 203 can be defined so that it comprises a greater portion of the total time 201 comprising time slot 200. Increasing the length of time of the guard period in this way can allow more distant nodes, such as nodes 106-1, 106-2 to receive the RF burst 206 within the guard period for a time slot n. Thus, if it is known that the network must cover a larger area, a longer guard period can be selected. However, it will be appreciated that increasing the guard period in this way will decrease the time available for the RF burst 206. This has the undesirable effect of reducing efficiency.
0025The invention will now be described more fully hereinafter with reference to accompanying drawing <figref idref="f0003 f0004 f0005 f0006 f0007 f0008 f0009 f0010 f0011 f0012">FIGS. 4-15</figref>, in which illustrative 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.
0026In order to overcome the deficiencies of the prior art, an embodiment of the invention includes a peer-to-peer TDMA type mobile ad hoc network comprised of a plurality of individual nodes. The individual nodes communicate with each other within an ad-hoc network environment. Significantly, information concerning the range between node pairs is estimated and exploited. Consequently, the scalability, latency, and efficiency of the TDMA communication system can be significantly enhanced.
0027The inventive arrangements advantageously include a distributed long range scheduler function as part of each node. The distributed long range scheduler determines specific times when node pairs can communicate so as to avoid interfering with one another. Heuristics produce an efficient distributed schedule for communication between node pairs. This schedule is advantageously based on information which includes both node range and angle (i.e. direction). Accurate time references are provided at each node and nodes exchange position estimates so that each node can maintain an estimate of range to its various neighbors. Further, unlike conventional arrangements which provide a time axis measured in fixed time slots per epoch, the inventive arrangements make use of a plurality of mini-slots. A plurality of mini-slots can be arbitrarily selected to define a time slot which is thereafter used for communications from one node to another node. The time slot is independently evaluated by each node to determine whether its use will cause interference with neighboring nodes. Each node independently adjusts its schedule to account for the link delay. Further, transmit and receive time slots are scheduled separately to allow for more efficient use of available time.
0028Referring now to <figref idref="f0003">FIG. 4</figref>, there is provided a simplified block diagram for a wireless mobile node 404 that is useful for understanding the present invention. The wireless mobile node can be used in a wireless communication network as described herein. The wireless mobile node 404 is comprised of a directional antenna 404, a transceiver 406, and a control unit 408. The wireless mobile node 404 can optionally include an omni-directional antenna 402.
0029The transceiver 406, the omni-directional antenna 402 and the phased array antenna 404 collectively enable wireless communications between the wireless mobile node 404 and a plurality of other nodes having a similar configuration in the . In this regard, it should be appreciated that the omni-directional antenna 402 is configured to send and/or receive signals in any direction. The directional antenna 404 is configured to selectively send and/or receive signals in a desired direction. The directional antenna 404 can include, but is not limited to, a phased array antenna. The omni-directional antenna 402 and directional antenna 404 are coupled to the transceiver 406 so that RF signals can be communicated to and from each of these antennas. In an alternative embodiment, the omni-directional antenna can be omitted and omni-directional communications can be provided by scanning a directional antenna beam through a wide range of azimuth and elevation angles.
0030The transceiver 406 can include conventional RF circuitry (not shown) and a modem (not shown) for receiving and transmitting RF signals. The transceiver 406 is electrically connected to the controller 450 so that received signals demodulated by the transceiver 406 can be communicated to the control unit 408. Similarly, baseband digital data and control signals can be communicated from the control unit 408 to the transceiver 406.
0031The control unit 408 is comprised of processor 410, antenna control unit 412, a clock 414, and node position unit 416. The antenna control unit 412 can control a direction of an antenna beam associated with the directional antenna 404. The antenna control unit 412 can optionally be included as part of the transceiver 406. Clock 414 provides a highly accurate and stable time reference for each node. The accuracy of the clock 414 can be maintained by any suitable means. For example, a GPS timing signal can be used for this purpose. As will be appreciated by those skilled in the art, GPS timing signals can provide a highly accurate time reference. Thus, clock 414 can be synchronized with clocks of other wireless mobile nodes forming part of the network described herein. The clocks are preferably synchronized to within a fractional portion of a mini time-slot (described below in greater detail). According to one embodiment, the time references can advantageously be selected so that a clock 414 associated with each node 404 is synchronized to within 100 nanoseconds of other nodes in the network. Still, the invention is not limited in this regard.
0032The control unit 408 also includes a node position unit. The node position unit is configured to allow the node to identify its position. For example, the node position unit can advantageously include a GPS receiver and GPS processing circuitry suitable for allowing the node 404 to precisely locate its position at any terrestrial or airborne location. If a GPS receiver is used, the GPS timing data can be used as described above to aid in synchronizing the clocks 414 in each of the nodes 404.
0033The control unit 408 also includes a memory device 450. The memory device 450 stores several different types of information. For example, the memory device 450 can includes a neighbor information table 420, epoch schedule 422, a receive (Rx) interference profile 424, a transmit (Tx) interference profile 426, and a neighbor time-slot usage profile 428. The various types of information stored in memory device 450 will be discussed below in greater detail. The various components forming the control unit 408 can communicate with each other by means of a suitable data bus 418.
0034Those skilled in the art will appreciate that the architecture described herein for wireless mobile node 404 is one possible example of a wireless mobile node which can be used with the present invention. However, it should be understood that the invention is not limited in this regard. Instead, any other suitable wireless mobile node architecture can also be used without limitation.
0035An overview of the basic operation of wireless mobile network utilizing a plurality of wireless mobile nodes 404 according to the inventive arrangements will now be provided. According to an embodiment of the invention, individual network nodes 404 use a neighbor discovery process. The neighbor discovery process includes an exchange of position information so that each node has the coordinates of neighboring nodes. This position information allows the range information and relative direction of such neighbor nodes to be calculated. Range information and direction information is used for purposes of performing interference calculations. Interference calculations also include consideration of propagation delays between nodes and required antenna beam pointing directions based on the known node locations.
0036The present invention is unlike conventional MANET systems that utilize conventional TDMA technology. In such conventional TDMA systems, periods of time are divided into epochs, and communication between nodes occurs in time slots which are sub-portions of each epoch. Significantly, each time slot in a conventional system will have a fixed timing position in each epoch. Nodes in the ad hoc network which need to communicate are assigned time slots for such communications. However, this fixed timing creates problems for long range communications.
0037The present invention also divides time into a series of epochs. However, the timing of the time slots used for communications between nodes is not fixed. State differently, it can be said that the timing position of each time slot is not fixed within each epoch. In the present invention, the position of time slots within each epoch can be arbitrarily selected by the nodes in accordance with an algorithm. The algorithm is selected for minimizing potential interference among neighbor nodes.
0038In order to allow for time slots to have timing positions which are arbitrarily defined within an epoch, the present invention introduces the concept of mini-slots, which are some fraction of the duration of a time slot. For example, each mini-time slot can have a duration which is 1/8 of the duration of a time slot. This concept can be better understood with reference to <figref idref="f0004">FIG. 5</figref>. In <figref idref="f0004">FIG. 5</figref>, there is shown a timing diagram 500 for a TDMA type mobile ad hoc network according to the inventive arrangements. The timing diagram shows a series of data epochs 504 which are fixed divisions of time. Each epoch 504 is sub-divided into a plurality of N mini-slots 506. According to an embodiment of the invention, a time slot 508 can be comprised of contiguous groups of M mini-slots. For example, each time slot 508 can be comprised of 8 mini-slots 506 (M=8). Each time slot 508 can have an arbitrarily defined starting position (subject to interference calculations) that corresponds to a starting time of any selected mini-slot.
0039In order to understand how time slot timing, range, direction and propagation information is used to mitigate interference, an example is useful. <figref idref="f0005">FIG. 6</figref> shows a planar geometry of several nodes where node 404<sub>2</sub> (the transmitting node) is attempting to schedule a transmit time slot consisting of five mini-slots (M=5) with node 404<sub>4</sub> (the receiving node). In <figref idref="f0005">FIG. 6</figref>, the transmit beam pattern 602 is shown for node 2. Nodes 404<sub>4</sub>, 404<sub>6</sub>, 404<sub>7</sub> and 404<sub>9</sub> are located within range and in the beam pattern. A time slot scheduler can be used to automatically select a timing position for a transmit time slot that will minimize interference to neighboring nodes.
0040The scheduler process begins by selecting a candidate set of mini-slots which will define the position of the transmit time slot for node 404<sub>2</sub>. <figref idref="f0005">FIG. 7</figref> is a timing diagram 700 which shows the time base at nodes 404<sub>2</sub>, 404<sub>4</sub>, 404<sub>6</sub>, 404<sub>7</sub> and 404<sub>9</sub>. It is assumed that clocks 414 at the nodes 404<sub>1</sub> - 404<sub>9</sub> are synchronized to fractions of a mini-slot.
0041The timing diagram shows that a candidate set of mini-slots MT<sub>2</sub> - MT<sub>6</sub> can be selected at node 404<sub>2</sub> which define a possible timing position for time slot 702. In order to determine whether this timing position will cause interference with neighboring nodes, the timing position of time slot 702 is mapped to the corresponding time intervals at nodes 404<sub>4</sub>, 404<sub>6</sub>, 404<sub>7</sub> and 404<sub>9</sub>. These corresponding time intervals 704, 706, 707, 709 are offset from time slot 702 because of the propagation delay "d" between the nodes. Propagation delay can be determined if the transmitting node 404<sub>2</sub> knows the relative position of neighbor nodes 404<sub>6</sub>, 404<sub>7</sub> and 404<sub>9</sub>. The corresponding time interval for the receiver node 404<sub>4</sub>, is 704. The corresponding time intervals mapped to the location of nodes 404<sub>6</sub>, 404<sub>7</sub> and 404<sub>9</sub> are respectively 706, 707, 709. Time intervals 706, 707, 709 represent the time intervals at nodes 404<sub>6</sub>, 404<sub>7</sub> and 404<sub>9</sub> during which the signal will arrive from node 404<sub>2</sub> if transmitted during time slot 702.
0042It should be understood that during the time intervals 706, 707, 709, a transmitted signal from node 404<sub>2</sub> will cause interference at nodes 404<sub>6</sub>, 404<sub>7</sub> and 404<sub>9</sub> if the antenna beams of these nodes are pointed in the direction of transmitting node 404<sub>2</sub>. For example, it can be observed that transmitting node 404<sub>2</sub> can be within a receive antenna beam 606 of node 404<sub>6</sub> during a transmit time interval. Notably, transmitting node 404<sub>2</sub> can advantageously be provided with position and timing schedule for neighbor nodes to determine the direction in which its neighbor node antennas are pointing during each mini-slot. If transmitting node 404<sub>2</sub> determines that any one of nodes 404<sub>6</sub>, 404<sub>7</sub> and 404<sub>9</sub> are in fact scheduled to receive signals (1) from a direction which coincides with transmitting node 404<sub>2</sub>, and (2) such signals are scheduled to be received during the intervals 706, 707, 709, then it can conclude that the transmissions from node 404<sub>2</sub> during time slot 702 will cause interference. If transmitting node determines that interference will occur, then a different candidate time slot 702 is advantageously selected.
0043If node 404<sub>2</sub> determines that time slot 702 will not cause interference to the receivers of nodes 404<sub>6</sub>, 404<sub>7</sub> and 404<sub>9</sub> then a second analysis can be performed. This second analysis can determine whether any nodes in the antenna beam of receiver node 404<sub>4</sub> will be transmitting in the direction of node 404<sub>4</sub> during the time interval corresponding to time slot 702 (as adjusted for propagation delay). This analysis is shown in <figref idref="f0006">FIGS. 8 and 9. FIG. 8</figref> shows a planar geometry 800 which is similar to the one shown in <figref idref="f0005">FIG. 6</figref>. However, in <figref idref="f0006">FIG. 8</figref>, nodes 404<sub>6</sub>, 404<sub>7</sub> and 404<sub>9</sub> are omitted for greater clarity since they are not part of this analysis. It can be observed in <figref idref="f0006">FIG. 8</figref> that nodes 404<sub>1</sub>, 404<sub>2</sub>, 404<sub>3</sub> and 404<sub>5</sub> are located within the range and in the receiver beam pattern 812 of node 404<sub>4</sub>.
0044<figref idref="f0006">FIG. 9</figref> shows a timing diagram which includes segment of the time base at several nodes 404<sub>1</sub> - 404<sub>5</sub>. It is assumed that clocks 414 at the nodes 404<sub>1</sub> - 404<sub>4</sub> are synchronized to fractions of a mini-slot. In <figref idref="f0006">FIG. 9</figref>, the timing position of time interval 704 is mapped to the corresponding time intervals at nodes 404<sub>1</sub>, 404<sub>3</sub>, and 404<sub>5</sub>. These corresponding time intervals 901, 903, 905 are offset from time slot 704 because of the propagation delay "d" between the nodes. <figref idref="f0006">FIG. 9</figref> shows that node 404<sub>4</sub> will experience interference during time interval 704 if nodes 404<sub>1</sub>, 404<sub>3</sub>, or 404<sub>5</sub> transmit toward node 404<sub>4</sub> during time periods 901, 903, or 905. If node 404<sub>4</sub> has transmission schedules and position information for nodes 404<sub>1</sub>, 404<sub>3</sub>, or 404<sub>5</sub> then it can determine whether time interval 704 is an acceptable receive time for node 404<sub>4</sub>. In the same way, node 404<sub>4</sub> can determine whether time interval 702 is an acceptable transmit time slot for node 404<sub>2</sub>.
0045The flowcharts in <figref idref="f0007 f0008 f0009 f0010 f0011">FIGS. 10-14</figref> will now be used to explain how the concepts discussed above in relation to <figref idref="f0005 f0006">FIGS. 6-9</figref> can be applied in a mobile ad hoc network. <figref idref="f0007">FIG. 10</figref> provides a basic overview of a mobile ad hoc network process 1000. It will be understood that the scheduler process described in relation to <figref idref="f0005 f0006">FIGS. 6-9</figref> requires detailed information regarding the identification, position, and communication schedule of neighbor nodes. Process 1000 is useful for understanding how such information is exchanged. Still, it should be understood that the process 1000 merely discloses one possible process for exchange of such data and the invention is not intended to be so limited. Instead, any other process for exchanging node identification, position, and communication schedule can be used. Further, it should be understood that all of the foregoing information can be exchanged using one or more control channels. For example, one or more mini-slots can be defined as control channels which are reserved for exchange of such information.
0046The process 1000 begins in step 1002 and continues with step 1004. In step 1004, nodes in a network engage in a neighbor discovery process. Neighbor discovery processes in mobile ad hoc networks are generally well known. Accordingly, the details of this process will not be described here. However, it should be understood that the neighbor discovery process involves transmission of "hello" messages to neighboring nodes using a control channel. The "hello" message can be broadcast to neighboring nodes by any suitable means. For example, the "hello" message can be transmitted by using an omni-directional antenna 402 or a scanned beam provided by directional antenna 404.
0047The "hello" message can include node identifier information and a position report for the node which transmits the message. Each node determines its own position using the node position unit 416. Each node also collects identifying information and position information from its neighbors using these "hello" messages.
0048In step 1006, information derived from the neighbor discovery process in step 1004 is used to populate (and/or update) neighbor information tables at each node. For example, node identification and position information can be stored in a neighbor information table 420. Each node further maintains an epoch schedule 422 which provides timing information for the occurrence of each data epoch 504. Timing of mini-slots 506 can also be derived from the epoch schedule 422.
0049The network process 1000 continues with step 1008 in which each node periodically communicates to its neighbors a transmit schedule for that node. In step 1010, each node also periodically broadcasts to its neighbors a receive schedule for that node. In step 1012, each node stores neighbor transmit and receive information in the table in <figref idref="f0003">FIG. 4</figref> identified as the neighbor time slot usage profile 428.
0050The process continues in step 1014 in which each node uses processor 410 to apply topology control rules to the information stored in its neighbor information table 420. The topology control rules can be stored in memory device 450. The topology control rules are used to select one or more neighbor nodes with which communication links should be established. Topology control rules for mobile ad hoc networks are well known in the art and therefore will not be described here in detail. However, it should be understood that such topology control rules can allow a node to determine whether communication links with various neighbor nodes should be established, maintained, or terminated. In step 1016, new communication links are formed with selected neighboring nodes as determined by the topology control rules. This process of forming links with new nodes will be described in more detail in relation to <figref idref="f0008 f0009 f0010 f0011">FIGS. 11-14</figref>. In step 1018, certain communication links are terminated with selected neighbor nodes as determined by topology control rules. In step 1020, a determination is made as to whether the network process should be terminated for any reason. If so, then the process terminates in step 1022. Alternatively, the process continues with step 1004 and repeats.
0051<figref idref="f0008">FIG. 11</figref> shows a series of steps which provide further detail concerning step 1016 in <figref idref="f0007">FIG. 10</figref>. Step 1016 involves one node forming a communication link with a selected neighbor node. Establishing this communication link begins with selection of a suitable time slot when a first node (transmitter node) will transmit data to a second node (receiver node).
0052As shown in <figref idref="f0008">FIG. 11</figref>, step 1016 includes a series of steps which can begin with step 1102. Step 1102 includes using a scheduler process at the transmitter node to generate a list of candidate transmit time slots for transmissions from the transmitter node to the receiver node. The scheduler process can be performed by processor 410 executing a programmed set of instructions. Alternatively, the scheduler process can be implemented as any other combination of hardware and software. Step 1102 is described in greater detail in <figref idref="f0009">FIG. 12</figref>. In general, however, the list of candidate time slots can be generated using an interference analysis similar to that described in relation to <figref idref="f0005">FIGS. 6-7</figref>. In this regard it may be noted that in <figref idref="f0005">FIGS. 6 and 7</figref> the transmitter node was node 404<sub>2</sub> and the receiver node was 404<sub>4</sub>.
0053In step 1104, the list of candidate transmit time slots can be communicated from the transmitter node to the receiver node. Any suitable means can be used for communicating this candidate transmit time slot list from the transmitter node to the receiver node. For example, a dedicated control channel can be used for this purpose. Still, the invention is not limited in this regard.
0054In step 1106, the candidate transmit time slot list is received and used at the receiver node to determine which of the proposed candidate time slots are acceptable. Step 1106 is described in greater detail in <figref idref="f0010">FIG. 13</figref>. In general, however, acceptable candidate time slots can be determined using a process similar to that previously described in relation to <figref idref="f0006">FIGS. 8-9</figref>. Following steps 1106, the receiver node will now be aware that transmitter node wishes to establish a transmit time slot for communications to receiver node. Consequently, the receiver node can initiate another process similar to that described in step 1016 for the purpose of establishing a transmit time slot for communications from the receiver node to the transmitter node. To avoid redundancy, that process will not be described here.
0055Continuing on now with step 1108, a message can be sent from the receiver node to the transmitter node. The message identifies those transmit time slots proposed by the transmitter node which are determined to be acceptable to the receiver node. In step 1110, this message is received at transmitter node. The process continues on to step 1112 in which the receiver node begins listening for transmissions from the transmitter node during the time slot which has been accepted by the transmitter node. In step 1114 data transmissions can begin from the transmitter node to the receiver node using the time slot that has been selected. Thereafter, the process can continue on to step 1018 as previously described.
0056Referring now to <figref idref="f0009">FIG.12</figref>, there is provided a more detailed description of the processes associated with step 1102 in <figref idref="f0008">FIG. 11</figref>. Step 1102 involves using a scheduler process at the transmitter node to generate a list of candidate transmit time slots for transmissions from the transmitter node to the receiver node. As an aid to understanding, step 1102 will be described with reference to <figref idref="f0004">FIG. 5</figref>.
0057The process can begin with step 1202 in which the scheduler process at the transmitter node selects a candidate transmit time slot beginning at mini-slot n and comprised of M mini-slots that are contiguous with each other. For example, in <figref idref="f0004">FIG. 5</figref> a candidate time slot can be time slot 508 which begins at mini-slot 4 and continues through mini-slot 11 (M=8). In step 1204, the scheduler process checks the transmitter node's transmit and receive schedule to determine whether any of the M mini-slots comprising the candidate time slot is already in use at the transmit node (for receiving or transmitting). The transmitter node's transmit and receive schedule can be stored in memory 450. If any of the M mini-slots are currently in use, then the candidate time slot is not acceptable and the process continues to step 1206. In step 1206, the value of n is incremented and the step 1204 is repeated with a different set of M mini-slots. For convenience, the value of n can be incremented by 1. However, the invention is not limited in this regard. For example, the value of n could be incremented by M or any other value.
0058In step 1204, if none of the M mini-slots are currently in use at the transmitter node, then the process continues on to step 1208. In step 1208, the scheduler process determines whether any of the M mini-slots are in use at the receiver node. Information concerning time slot usage at the receive node can be obtained from the neighbor time slot usage profile 428 which is stored in memory device 450. If any of the time slots are currently in use at the receiver node, the process can return to step 1206 where the value of n is incremented to select a different set of M mini-slots. Alternatively, if the M mini-slots are not in use at the receiver node, then the process continues on to step 1210.
0059In step 1210, the scheduler process in the transmitter node determines whether the transmitter node's use of the M mini-slots associated will cause interference to neighboring nodes located in the transmit beam of the transmitter node (when pointed toward the receiver node). This process for mitigating interference is described below in more detail in relation to <figref idref="f0011">FIG. 14</figref>. If the scheduler process determines that use of the M mini-slots by the transmitter node will cause interference to neighboring nodes, then the process returns to step 1206 and an alternative set of mini-slots is selected for evaluation. Conversely, if the scheduler process determines that use of the M mini-slots by the transmitter node will not cause interference to neighboring nodes, then the process continues on to step 1212.
0060In step 1212, the candidate time slot comprised of the M mini-slots is added to a list of candidate time slots which can be used. Thereafter, in step 1214, a determination is made as to whether the candidate transmit time slot list is complete. This determination can be based on any one of several considerations. For example, the list can be deemed complete when a predetermined number of candidate transmit time slots have been identified. Alternatively, the list can be complete when all possible candidate time slots have been considered.
0061Referring now to <figref idref="f0011">FIG. 14</figref>, there is provided a more detailed description of the process associated with step 1210 in <figref idref="f0009">FIG. 12</figref>. It may be recalled from the discussion regarding <figref idref="f0009">FIG. 12</figref>, that step 1210 generally involves a scheduler process at the transmitter node. The scheduler process is used to evaluate potential interference caused by the transmitting node's use of the M mini-slots associated with the candidate time slot. In particular, this scheduler process determines whether the transmissions by the transmitter node during the candidate time slot, using an antenna beam pointing toward the receiver node, will cause interference to other neighboring nodes that are also located in the transmit beam. As an aid in understanding, the process will be described with reference to <figref idref="f0005">FIGS. 6 and 7</figref> in which node 404<sub>2</sub> is considered the transmitter node and node 404<sub>4</sub> is considered to be the receiver node.
0062The process in <figref idref="f0011">FIG. 14</figref> begins with step 1402 in which the transmitter scheduler at the transmitter node determines a direction that it's transmit beam will be pointed for the purpose of communicating with the receiver node. In the context of <figref idref="f0005">FIGS. 6 and 7</figref>, this means that the node 404<sub>2</sub> will determine which direction its antenna beam 602 should point for communications with node 404<sub>4</sub>. Once the direction of the transmitter beam has been determined in step 1402, the scheduler process at the transmitter node (404<sub>2</sub>) will determine in step 1404 whether there are any neighbor nodes that are contained within the transmit beam. If not, then it can be assumed that the transmitter node's use of the M mini-slots will not cause interference to any other nodes and the process will continue on to step 1412.
0063Alternatively, if it is determined in step 1404 that there are neighbor nodes contained within the transmit beam, then the process continues on to step 1406. For example, in <figref idref="f0005">FIG. 6</figref> nodes 404<sub>6</sub>, 404<sub>7</sub>, 404<sub>9</sub> are in the transmit beam 602 (in addition to node 404<sub>4</sub>). In step 1406 the scheduler process determines whether there are any neighbor nodes in the transmit beam that are scheduled to be receiving during the candidate transmit time slot as adjusted for propagation delay. This concept is illustrated in <figref idref="f0005">FIG. 7</figref>. In step 1406, the transmitter scheduler would determine whether any of the nodes 404<sub>6</sub>, 404<sub>7</sub>, 404<sub>9</sub> are scheduled to be receiving during time intervals 706, 707, 709. If not, then it can be assumed that no interference will occur and the scheduler process continues on to step 1412. Otherwise, the scheduler process goes on to step 1408.
0064In step 1408, a determination is made as to whether any of the receive beam of the neighbor nodes is pointing toward the transmitter during the candidate transmit time (adjusted for propagation delay). In the context of <figref idref="f0005">FIG. 7</figref>, this would mean determining whether the antenna beams of any of the nodes 404<sub>6</sub>, 404<sub>7</sub>, 404<sub>9</sub> are pointing toward the transmitter node 404<sub>2</sub>. In <figref idref="f0005">FIG. 6</figref>, it can be observed that antenna beam 606 of node 404<sub>6</sub> is pointing toward the transmitter node 404<sub>2</sub> during time interval 706. In this example, the scheduler process would continue on to step 1410 and determine that the transmitter node's use of the M mini-slots associated with a particular candidate time slot will cause interference to the other nodes located in the transmit beam. The process would then continue on to step 1206 in <figref idref="f0009">FIG. 12</figref>. Alternatively, the scheduler process continues to step 1412 and determine that the transmitter node's use of the M mini-slots will not cause interference. From step 1412, the process continues on to step 1212 where the candidate time slot is added to the candidate time slot list.
0065It may be recalled from <figref idref="f0008">FIG. 11</figref> that once a suitable list of candidate transmit time slots has been compiled in step 1102, this list is communicated to the receiver in step 1104. Thereafter, in step 1106 the scheduling process at the receiver determines which, if any, of the candidate time slots are acceptable. Step 1106 will now be described in further detail with reference to <figref idref="f0010">FIG. 13</figref>. The process can begin in step 1302 when the receiver scheduler receives the list of candidate transmit time slots at the receiver node. The process continues on to step 1304 in which the receiver scheduler selects the first candidate time slot on the list for evaluation.
0066The evaluation process begins in step 1306 with the receiver scheduler process at the receiver node determining whether the M mini-slots corresponding to the candidate transmit time slot are still idle and are therefore available. This step is somewhat redundant because a similar check is performed in step 1208. However, it will be appreciated that the transmit and receive schedule at the receiver node will often contain scheduling information for the receiver mode that is more current than the corresponding information for the receiver node that is stored in at the transmitter node. Accordingly, step 1306 is a useful verification that the M mini-slots are still idle.
0067If the M mini-slots are determined to be no longer idle, then the process continues on to step 1312 where the receiver scheduler process determines whether there are any more candidate transmit time slots on the candidate transmit time slot list. Alternatively, in step 1306, if the M mini-slots associated with a candidate time slot are in fact available, then the process continues on to step 1308.
0068In step 1308, the receiver scheduler process at the receiver node determines whether the receiver node will experience interference from network nodes other than the transmitter node. Step 1308 is described in greater detail in relation to <figref idref="f0012">FIG.15</figref>. However, it should be understood that the receiver scheduler process in step 1308 determines whether the receiver node will experience interference from other neighboring nodes during the M mini-slots corresponding to the candidate transmit time slot (as adjusted in time to compensate for propagation delay). If, in step 1308, the receiver scheduler process determines that no interference will result from neighboring nodes, then the process continues on to step 1108 in <figref idref="f0008">FIG. 11</figref>. In step 1108, a message is sent to the transmitter node indicating that the candidate time slot is acceptable to the receiver node. Alternatively, if the receiver scheduler process determines that the receiver node will experience interference from other neighboring nodes, then the process continues on to step 1312.
0069In step 1312, the receiver scheduler process determines whether there are any other candidate time slots on the candidate time slot list. If so, then the receiver scheduler process continues on to step 1316 where the next candidate time slot is selected. Alternatively, if there are no more candidate time slots on the list, the receiver scheduler process continues on to step 1314 in which the receiver node notifies the transmitter node that none of the candidate time slots are acceptable. The receiver scheduler process then returns to step 1102 in <figref idref="f0008">FIG. 11</figref>, where a new list of candidate time slots is generated at the transmitter node.
0070Referring now to <figref idref="f0012">FIG. 15</figref>, the processes associated with step 1308 will now be described in greater detail. The process in <figref idref="f0012">FIG. 15</figref> begins with step 1502 in which the scheduler process at the receiver node determines a direction that it's receive beam will be pointed for the purpose of receiving communications from the transmitter node. In the context of <figref idref="f0006">FIGS. 8 and 9</figref>, this means that the node 404<sub>4</sub> will determine which direction its receiver antenna beam 812 will need to point towards for communications with node 404<sub>2</sub>. Once the direction of the receiver antenna beam 812 has been determined in step 1502, the scheduler process at the receiver node (404<sub>4</sub>) will determine in step 1504 whether there are any neighbor nodes that are contained within the receiver antenna beam 812.
0071If it is determined in step 1504 that there are no neighbor nodes contained within the receiver antenna beam 812, then the process continues in step 1512. In step 1512, the scheduler process determines that the receiver node 404<sub>4</sub> will not experience interference from other transmitting nodes during the time interval corresponding to the M mini-slots (as adjusted for propagation delay). Accordingly, the process will thereafter continue on to step 1108 in <figref idref="f0008">FIG. 11</figref>.
0072Alternatively, if it is determined in step 1504 that there are neighbor nodes contained within the receiver antenna beam 812, then the process continues on to step 1506. For example, in <figref idref="f0006">FIG. 8</figref> nodes 404<sub>1</sub>, 404<sub>3</sub>, 404<sub>5</sub> are in the receiver antenna beam 812 (in addition to node 404<sub>2</sub>). Accordingly, the process would continue on to step 1506 in the example shown in <figref idref="f0006">FIG. 8</figref>.
0073In step 1506 the scheduler process at the receiver node determines whether transmitted signals from any neighbor nodes in the receiver beam 812 can potentially be received at the receiver node 404<sub>4</sub> during any of the mini-slots corresponding to the time interval 704. This concept is illustrated in <figref idref="f0006">FIG. 9</figref>. Recall that time interval 704 is the period of time during which a transmission from transmitter node 404<sub>2</sub> will actually be received at receiver node 404<sub>4</sub> (assuming that the signal is transmitted from node 404<sub>2</sub> during time slot 702). Similarly, time intervals 901, 903, 905 represent those transmission time intervals for nodes 404<sub>1</sub>, 404<sub>3</sub>, 404<sub>5</sub> that will result in signals actually being received at receiver node 404<sub>4</sub> during time interval 704.
0074In step 1506, if none of the nodes 404<sub>1</sub>, 404<sub>3</sub>, 404<sub>5</sub> are actually scheduled to be transmitting during the time periods 901, 903, 905, then it can be concluded that no interference will be caused at the receiver node 404<sub>4</sub> during time interval 704. In that case, the transmit time slot 702 would be an acceptable time slot during which node 404<sub>2</sub> can transmit to node 404<sub>4</sub>, and the scheduler process continues on to step 1512. Conversely, if any of the nodes 404<sub>1</sub>, 404<sub>3</sub>, 404<sub>5</sub> are actually scheduled to be transmitting during the time periods 901, 903, 905, then such transmissions can potentially cause interference at the receiver node 404<sub>4</sub> during time interval 704. In that case, the transmit time slot 702 may not be an acceptable time slot during which node 404<sub>2</sub> can transmit to node 404<sub>4</sub>. Accordingly, the scheduler process will continue on to step 1508.
0075In step 1508, a determination is made as to whether an antenna beam of any neighbor nodes that is actually pointed toward the receiver 404<sub>4</sub> during a time interval when the receiver is expecting to receive signals from the transmitter node. In the context of <figref idref="f0006">FIG. 9</figref>, this would mean determining whether the antenna beams of any of the nodes 404<sub>1</sub>, 404<sub>3</sub>, 404<sub>5</sub> are pointing toward the receiver node 404<sub>4</sub> during time intervals 901, 903, 905. If so, then the scheduler continues on to step 1510 where it determines that other transmitters will cause interference to the receiver if the transmitter node uses the M mini-slots associated with a candidate transmit time slot such as slot 702. Following step 1510, the scheduler process at the receiver node continues on to step 1312 in <figref idref="f0010">FIG. 13</figref>. In step 1312 the scheduler process checks to see if other candidate time slots are available and continues on as described above.
13 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| EP2124500A1 | Cited by | European Patent Office (EPO) | Search report |
| EP3457645A1 | Cited by | European Patent Office (EPO) | Search report |
| WO2019200363A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| WO2019053094A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US8155093B2 | Cited by | United States of America | Applicant |
| US12058057B2 | Cited by | United States of America | Applicant |
| US11382056B2 | Cited by | United States of America | Applicant |
| EP2124501A1 | Cited by | European Patent Office (EPO) | Search report |
| US8537789B2 | Cited by | United States of America | Applicant |
| WO0128170A2 | Cites | World Intellectual Property Organization (WIPO) | Search report |
| US2002176381A1 | Cites | United States of America | Examiner |
| US2003214914A1 | Cites | United States of America | Search report |
| US2005053099A1 | Cites | United States of America | Examiner |
| US2007140127A1 | Cites | United States of America | Examiner |
| US6016322A | Cites | United States of America | Examiner |
| US6317436B1 | Cites | United States of America | Search report |
| US7006534B1 | Cites | United States of America | Examiner |
16 members in 4 offices; this record represents the family
Priority claims5
| Document | Office | Kind | Date |
|---|---|---|---|
| 832202 | United States of America | – | |
| 83220207 | United States of America | A | |
| 83220207 | United States of America | A | |
| 832202 | – | – | – |
| US20070832202 | – | – | – |
Members16
| Document | Office | Kind | |
|---|---|---|---|
| EP2020786A2This record | European Patent Office (EPO) | A2 | |
| US2009034446A1 | United States of America | A1 | |
| US2009034489A1 | United States of America | A1 | |
| US2009034491A1 | United States of America | A1 | |
| EP2020786A3 | European Patent Office (EPO) | A3 | |
| EP2124500A1 | European Patent Office (EPO) | A1 | |
| EP2124501A1 | European Patent Office (EPO) | A1 | |
| US7855997B2 | United States of America | B2 | |
| EP2124501B1 | European Patent Office (EPO) | B1 | |
| AT506831T | Austria | T | |
| ATE506831T1 | Austria | T1 | |
| DE602009001102D1 | Germany | D1 | |
| US8155093B2 | United States of America | B2 | |
| EP2020786B1 | European Patent Office (EPO) | B1 | |
| EP2124500B1 | European Patent Office (EPO) | B1 | |
| US8537789B2 | United States of America | B2 |
40 legal events, as 4 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Application deemed withdrawn, or ip right lapsed, due to non-payment of renewal feeWithdrawnR119 | R119 | DE | |
| Change of representativeR082 | R082 | DE | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Change of representativeR082 | R082 | DE | |
| Change of representativeR082 | R082 | DE | |
| Amendment of ipc main classPREVIOUS MAIN CLASS: H04W0072080000R079 | R079 | DE | |
| Change of applicant/patenteeR081 | R081 | DE | |
| Change of representativeR082 | R082 | DE | |
| Change of representativeR082 | R082 | DE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Fee paymentPLFP | PLFP | FR | |
| Fee paymentPLFP | PLFP | FR | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Gb: european patent ceased through non-payment of renewal feeCeasedGBPC | GBPC | EP | |
| Fee paymentPLFP | PLFP | FR | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| No opposition filed against granted patent, or epo opposition proceedings concluded without decisionGrantedR097 | R097 | DE | |
| No opposition filedOpposition26N | 26N | EP | |
| No opposition filed within time limitOppositionORIGINAL CODE: 0009261PLBE | PLBE | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: NO OPPOSITION FILED WITHIN TIME LIMITSTAA | STAA | EP | |
| Dpma publication of mentioned ep patent grantGrantedR096 | R096 | DE | |
| Designated contracting statesAK | AK | EP | |
| European patent grantedGrantedFG4D | FG4D | GB | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Amendment of ipc main classPREVIOUS MAIN CLASS: H04W0072120000R079 | R079 | DE | |
| First examination report despatched17Q | 17Q | EP | |
| Designation fees paidAKX | AKX | EP | |
| Designated contracting statesAK | AK | EP | |
| Request for extension of the european patentAX | AX | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Search report despatchedORIGINAL CODE: 0009013PUAL | PUAL | EP | |
| Request for examination filed17P | 17P | EP | |
| Designated contracting statesAK | AK | EP | |
| Request for extension of the european patentAX | AX | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP |
Numbers
- Publication
- 2020786
- Publication, DOCDB
- 2020786
- Publication, EPODOC
- EP2020786
- Application
- 8013751
- Application, DOCDB
- 08013751
- Application, EPODOC
- EP20080013751
Titles3
- German
- Weitreichende Terminplanung für MANET-Netzwerke mit direktionalen Antennen
- English
- Long range scheduling for directional antenna manet networks
- French
- Programmation longue distance pour réseaux manet à antenne directionnelle
Classification
- CPC, 2
- H04W72/541
- H04W84/18
- IPC, 2
- H04L12 56
- H04W72 54
Designated states2
- Contracting states, 1
- Türkiye
- Extension states, 1
- Serbia