US 6,904,275 B2Grant
Prioritized-routing for an ad-hoc, peer-to-peer, mobile radio access system
Issue Date:2005-06-07
•10 Claims
•5 Drawing Sheets
Abstract
An ad-hoc, peer-to-peer radio access system having a series of remote terminals, where each remote terminal is capable of forming a link, or hop, of the routing of a call made by one of the series of terminals. The status of the battery of each terminal which may potentially form part of the routing path of a call is reported to other terminals, whereby the routing path for a call will be decided also based on the status of the battery-charge of each terminal along the routing path.
Metadata
Assignee
- MeshNetworks, Inc.
Inventor
- Peter Stanforth
Application Information
Application Number:US 09/859,305
Filing Date:2001-05-18
Priority Date:2000-11-13
Art Unit:2682
Patent Drawings (5 sheets)
Description
Cross-Reference to Related Applications
[0001] This application is a continuation of patent application Ser. No. 09/815164 filed Mar. 22, 2001.
[0002] Priority of provision application Ser. No. 60/248,182, on Nov. 13, 2000 is herewith claimed.
Background of the Invention
[0003] The present invention is directed to a method of routing radio telephone calls of an ad-hoc, peer-to-peer radio system, and, in particular, to such an ad-hoc, peer-to-peer radio system disclosed in copending application Ser. No. 09/705,588, filed on Nov. 3, 2001, entitled “Methods and Apparatus for Coordinating Channel Access to Shared Parallel Data Channels”, which application is incorporated by reference herein in its entirety. The network system having coordinating channel access to shared parallel data channels via a separate reservation channel of copending application Ser. No. 09/705,588 is directed to a network system, such as radio network, where each node, or radio terminal, of the network is capable of serving as a node or hop of a routing path of a call from another, or to another radio terminal. In that system, communication between nodes or radio terminals is achieved using Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) protocol with the addition of multiple parallel data channels serviced by one reservation channel. By dedicating a separate reservation channel for the multiple parallel data channels, collision-free access by all of the competing nodes or terminals of the service group of the network is greatly reduced. Communications between terminals or nodes is set up by information exchanged on the separate reservation channel, which information includes all of the call set-up information such as data channel desired to be used for transferring voice, video or data, the desired power level of at least initial transmission, messaging such as Request-to-Send (RTS), Clear-to-Send (CTS), Not-Clear-to-Send (NCLS), Acknowledgment (ACK) for indicating reception of the transmitted call, Non-Acknowledgment (NACK) for indicating improper reception of the call, etc. In this system, in order to further ensure fast, adequate and collision-free transmission and reception, besides a primary modem typically provided with the transceiver of each node or terminal, a secondary modem is also provided which is dedicated to the reservation channel when the primary modem of the transceiver is occupied, such as when sending out data on a data channel. This system also provides for collision free transmission and reception between nodes or terminals by transmitting the reservation and data channels in time slots of time frames, with the information as to which time slot is to be used being included in the messaging transmitted by the reservation channel. Such a format not only provides collision-free transmission, but also allows for Quality-of-Service (QoS) for different types of Class-of-Service (CoS), Thus, not only may voice and video be transmitted, besides data, but voice and data transmission may be prioritized, so that when competing calls vie for a data channel, the delay-dependent voice or video transmissions will take precedence. This prioritization is accomplished by assigning prioritized calls for transmission in earlier time slots of a time frame.
[0004] The network system disclosed in U.S. application Ser. No. 09/705,588 ensures that every node or terminal of a service set of terminals has the most information regarding all of other terminals of that service set, so that the choice of data channel to be used, any required delay is transmitting the call, information on power level, and the like, are checked and updated by each terminal by a practically continuous monitoring of the reservation channel.
[0005] As explained above, the system disclosed in U.S. application Ser. No. 09/705,588 utilizes protocol that provides collision-free channel access, which also emphasizes improving geographic reuse of the frequency spectrum.
[0006] In U.S. Pat. No. 5,943,322—Mayer, et al., which patent is incorporated by reference herein, there is disclosed a radio system is for use, in one embodiment, in battlefield conditions. The ad-hoc, peer-to-peer radio system of this patent does not have, nor require, a base station, as conventional cellular systems, personal communications system (PCS), and the like, require; instead, each radio terminal forming part of the ad-hoc, peer-to-peer radio system may alternatively serve as a base station, in addition to being an ordinary link terminal of the radio system, whereby, if one such terminal serving as a base station should for some reason become inoperative, another terminal may take over and serve as the base station.
[0007] The ad-hoc, peer-to-peer radio system of U.S. Pat. No. 5,943,322 is based on a transport-mechanism using a time division duplex (TDD) technique in a code division multiple access (CDMA) system. Time Division Duplex (TDD) is a way of maximizing the bits/hz/km2. Such a system not only may be used for providing commercial voice, but is also quite suited to both transmission and reception of data and video services. Time Division Duplex (TDD) systems are typically used for packet data systems as they make much more efficient use of the available bandwidth, in order to deliver a much higher effective data rate to the end user. TDD is typically used in fixed wired solutions or point-to-point wireless systems because it has its own spectrum limitations. TDD systems, however, have not been deployed for voice systems.
[0008] In the above-identified provisional application Ser. No. 60/248,182, there is disclosed an ad-hoc, peer-to-peer radio system for use as a stand-alone system that is also connected to a cellular network and/or landline. The ad-hoc mobile radio networking system thereof is capable of receiving and transmitting voice, data and video calls through any number of different types of telecommunication networks, such as the PSTN, the Internet, and the like, besides the cellular and next-generation cellular networks.
[0009] In any ad-hoc, peer-to-peer radio system, a critical consideration is the status and life of the battery of each terminal forming a part of the system. With the arrival of laptop computers, portable digital assistants (PDAs) and high-tech cellular phones, consumers are beginning to request mobile data services in addition to traditional voice services. Such devices are in use much more than traditional cellular phones, and, therefore, deplete their limited-life batteries more quickly. The ad-hoc, peer-to-peer system disclosed in the above-mentioned priority, provisional application Ser. No. 60/248,182, depletes batteries even more quickly, since each terminal can also serve as a router and relay for other terminals of the system, in order to extend the range or provide alternate routes to destinations. The ability to limit the use of the battery, therefore, is a very important element and consideration of that system.
[0010] In commonly-owned U.S. provisional application Ser. No. 60/246,833, and commonly-owned pending U.S. application Ser. No. 09/847,170, filed on May 3,2001 entitled “Time Division Protocol for an Ad-Hoc, Peer-to-Peer Radio Network Having Coordinating Channel Access to Shared Parallel Data Channels with Separate Reservation Channel”, which applications are incorporated by reference herein, there are disclosed a protocol method and algorithm for ad-hoc network system that is based on least-energy routing of calls from and between network radio terminals. In simple terms, the major component of the routing decision is to choose the route to the destination that uses the least amount of energy over the complete route. The major reason for this is that least-energy routing minimizes the radiated RF energy, in order to reduce interference between terminals. A consequence of this is that it creates the most efficient use of the power supply of the terminals.
[0011] There are, also, other components of most conventional routing algorithms for ad-hoc, peer-to-peer radio systems that are generally related to the Quality of Service (QOS). The two major attributes of QoS are: The potential for delay, or latency, and the potential for bit errors (BER) during transmission. However, no present or prior system or algorithm has taken into consideration the impact of the battery life of the terminals, which, as stated above, should be a major and primary consideration for any network that consists of hand-held terminals, and especially for an ad-hoc, peer-to-peer radio system where batteries are used so much more as compared to conventional radio systems such as the cellular network, PCS's, and the like. Since hand-held terminals only have limited battery life in terms of trade off of size and weight, users do all that is possible in order to conserve their batteries, so that there will be sufficient life in them when they wish to use the device. As stated above, ad-hoc networks discharge a battery even more, even when the terminal owner is not using the terminal, since each terminal may also serve as a base station or a router or a link in the routing decision for connecting a call.
[0012] The present invention, therefore, is directed to the provision of the consideration of the status of the battery-charge of each terminal forming a part or link of an ad-hoc, peer-to-peer radio system, whereby the routing algorithm and method by which a call from a terminal-source is connected to the terminal-destination or to an exterior, independent radio system and/or PSTN interconnected with the ad-hoc, peer-to-peer radio system in which the present invention is deployed, also takes into consideration the status of the battery of each terminal by which the routing of the outgoing call is to be connected.
Summary of the Invention
[0013] It is, therefore, the primary objective of the present invention to provide an additional criterion to the routing decision of an ad-hoc, peer-to-peer radio system, which additional criterion includes information about the status of the battery-charge of each battery which may possibly serve as a link for call-routing of call over the radio system.
[0014] It is another objective of the present invention to provide such a system where the battery of each radio terminal forming a part of the ad-hoc, peer-to-peer radio system continually calculates and transmits to other, like terminals the status of its battery-charge, whereby each terminal is capable of taking into consideration the status of each battery of each terminal of the radio system when selecting the best route for connecting a call.
[0015] It is yet another objective of the present invention to provide such a system where the battery-status information calculated and transmitted to other terminals is used in conjunction with least-energy routing of a radio telephone call in order to choose the route to the destination that uses the least amount of energy over the complete route, whereby least-energy routing minimizes the radiated RF energy, in order to reduce interference between terminals, and in order to provide the most efficient use of the battery power supply of the terminals.
[0016] According to the present invention, routing algorithms are extended to include information about the battery state of each terminal, such that if a choice of routes is available, one of which includes a low battery terminal, an alternate route will be selected. Multiple levels of battery determination may be used, the number of which may change depending upon different radio protocols and topologies. For example, a terminal that is in a charging cradle, or hooked up to an external power supply, will identify itself as having infinite battery life. A terminal with a fully charged battery will identify itself as having excellent battery life. A terminal with a low battery life will identify itself as having poor battery life, which will indicate that it should only be used for routing emergency data, or in the case of no other available option. Once the battery drops below some configurable threshold, the terminal will identify itself as having no battery life. This will allow the terminal to reserve some battery life for it's own use.
Brief Description of the Drawings
[0017] The invention will be more readily understood with reference to the accompanying drawings, where:
[0018] FIGS. 1A and 1B are schematics showing a basic, ad-hoc, peer-to-peer radio system with which the method and algorithm of the present invention may be used;
[0019] FIG. 2 is a schematic showing an example of least-energy routing with which the system of the present invention is to be used;
[0020] FIG. 3 is a schematic showing the exchange of routing tables of between end-users of an ad-hoc, peer-to-peer radio system with which the battery-status routing method and algorithm of the present invention is used;
[0021] FIGS. 4A and 4B are flow charts showing the subroutine conducted by each terminal of the ad-hoc, peer-to-peer radio system for initiating the checking of the status of its battery, either when it is in its idle state or when it in its stable, alert state;
[0022] FIG. 5 is a flow chart showing the subroutine by which the status of battery of the terminal is determined for subsequent reporting to other similar terminals in order to serve as a basis for calculating the best route of connection of a radio telephone call;
[0023] FIG. 6 is a flow chart showing the subroutine performed at the terminal-source that is initiating an outgoing radio telephone call, in order to actuate the subroutine for determining the best routing of its outgoing call; and
[0024] FIG. 7 is a flow chart showing the routing table messaging subroutine for establishing the outgoing radio telephone call which may be based not only on least energy routing, but also on the status of the battery of each terminal-link potentially forming a part of the route for connecting the outgoing radio telephone call.
Detailed Description of the Invention
[0025] Referring now to the drawings in greater detail, and to FIGS. 1-3 for now, an ad-hoc, peer-to-peer radio system is shown. The ad-hoc radio system consists of a series of radios or terminals 10, which may communicate directly with each one to another, as shown in FIG. 1A , or to other terminals 10 via link-routing where other, intermediate terminals are used, as shown in FIG. 1B. For simplicity, only three such terminals 10 have been shown in FIG. 1B , it being understood that the ad-hoc, peer-to-peer radio system will employ a multitude of such terminals, whereby the routing of a call from one terminal to another will employ a number of other, intermediate terminals. Such an ad-hoc, peer-to-peer radio system is disclosed in the above-mentioned commonly-owned applications Ser. Nos. 60/246,833 and 09/847,170, and in priority application Ser. No. 60/248,182. The present invention applies to all types of ad-hoc, peer-to-peer radio systems, but has particular relevance to type disclosed in the above-mentioned copending U.S. application Ser. No. 09/705,588.
[0026] In the ad-hoc, peer-to-peer radio system disclosed in above-mentioned patent applications, routing of a radio call from a source-terminal to a destination-terminal is achieved by a method and algorithm that calculates the routing path based on least energy; that is, the major component of the routing decision is to choose the route to the destination that uses the least amount of energy over the complete route. The major reason for this is that least-energy routing minimizes the radiated RF energy, in order to reduce interference between terminals. As a result of this, it creates the most efficient use of the power supply of the terminals.
[0027] FIG. 2 shows an extreme example of what happens without using least energy routing. The radio source uses a direct route to the destination. This route requires high power, which results in a large number of other radios being interfered with. Therefore, according to least energy routing disclosed in the above-mentioned, commonly-owned U.S. applications Ser. No. 60/246,833 and 09/847,170. The source radio will choose an alternative routing path with a greater number of radio-hops through intermediate terminals, which will result in reduced interference in the other radio terminals.
[0028] There are, also, other components of most conventional routing algorithms for ad-hoc, peer-to-peer radio systems that are generally related to the Quality of Service (QOS). The two major attributes of QoS are: The potential for delay, or latency, and the potential for bit errors (BER) during transmission.
[0029] As seen in FIG. 3,the routing of calls is achieved by each terminal storing a routing table if that terminal is to be part a link, or hop, of the routing path. This routing table includes all of the information required by the source-terminal in order to determine and calculate the least-energy path of routing of the call from source-terminal to the destination-terminal. Adjacent or proximate terminals 10 exchange routing tables, as seen in FIG. 3 , whereby when a call is to be set up from a source-terminal, each terminal 10 already knows the routing table of its most immediate or adjacent neighbor-terminal, whereby a call may be routed to another destination-terminal, or to a router or gateway 20, for subsequent transmittal of the call to another similar cell of terminals, to a cellular switched network, or to the PSTN, and the like.
[0030] In accordance with the present invention, additional information is added to each routing table of each terminal 10, which additional information contains information about the status of the charge of the battery of that terminal, whereby when routing tables are exchanged, the battery status of each terminal is also taken into consideration when determining or calculating the best and most efficient routing path to take for completing a call from a source-terminal to a destination-terminal.
[0031] According to the preferred embodiment of the invention, each battery of each terminal 10 may assume one of four status-conditions of 2 bits, or more than four status-conditions may be employed:
[0032]
When a terminal 10 is in a charging cradle, or hooked up to an external power supply, it will identify itself as having infinite battery life—code 11. A terminal with a fully charged battery will identify itself as having excellent battery life—code 10. A terminal with a low battery life will identify itself as having poor battery life—code 01, which will indicate that it should only be used for routing emergency data, or in the case of no other available option. Once the battery drops below some configurable threshold, the terminal will identify itself as having no battery life—code 00. This will allow the terminal to reserve some battery life for it's own use.
| 00 | critical |
| 01 | poor |
| 10 | full |
| 11 | infinite. |
When a terminal 10 is in a charging cradle, or hooked up to an external power supply, it will identify itself as having infinite battery life—code 11. A terminal with a fully charged battery will identify itself as having excellent battery life—code 10. A terminal with a low battery life will identify itself as having poor battery life—code 01, which will indicate that it should only be used for routing emergency data, or in the case of no other available option. Once the battery drops below some configurable threshold, the terminal will identify itself as having no battery life—code 00. This will allow the terminal to reserve some battery life for it's own use.
[0033] “Battery Conservation Algorithms”
[0034] The components of the system of the present invention described above are independent of the link layer of the ad-hoc transport of that system disclosed in the above-identified commonly-owned patent applications. The present invention adds the capability to the routing layer and call-control layers of the ad-hoc network system, in order to permit the function of battery-conservation to be accomplished.
[0035] The basic reasoning behind the algorithm of the present invention is to add a component to the routing decision that includes consideration for the state of the battery. In order for this to work, the routing algorithms are extended to include information about the battery state of the terminal, such that if a choice of routes is available, one of which includes a low battery terminal, the alternate route will be selected.
[0036] Referring now to FIGS. 4-7 , there are shown the flow charts for the method of adding battery-status information to the routing tables of the terminals 10. Each terminal periodically wakes up in order to check its own battery status (FIG. 4A 0 Blocks 30, 32), after which it will update, if necessary, it routing table (FIG. 5). If the status remains unchanged, then the status of the battery of that terminal will remain unchanged, or stable, as shown in FIG. 4B (block 36), and no change will be made to that terminal's routing table. Again, periodically, the terminal will self-test its battery life (block 38). The battery status is checked using the subroutine “Evaluation” (blocks 34 and 40 in FIGS. 4A and 4B , respectfully).
[0037] Referring to FIG. 5 , the “Evaluation” subroutine 42 is shown. This subroutine determines whether or not its terminal's routing table needs updating based on the “check-battery status” subroutine of FIGS. 4A and 4B (block 44 of FIG. 5). One the most-recent status has been determined (block 46), it is determined which of the four status-conditions exists: Infinite—block 48(code 11), high—block 50 (code 10), low—block 52 (code 01), or critical—block 54 (code 00). If the status determined in block 46 is the same as that of the previous results from the “check battery status” subroutine, then the program goes to block 56, indicating that the terminal's battery is stable, indicating that no change of status from the previous determination has occurred, whereby no change is made to the terminal's routing table. However, if there has been a change from the previous status, then the program will update the terminal's routing table to the appropriate code-value. The update need not necessarily be a downgrade; if, since the last status-check of the battery the battery had been recharged, then a status-upgrade to the routing table will ensue. The updated routing table will be transmitted to each adjacent terminal of the ad-hoc, peer-peer-radio system, preferably as part of the configuration data time-frame messaging transmitted and received on the control channel, as disclosed in commonly-owned U.S. application Ser. Nos. 60/246,833 and 09/847,170, which are incorporated by reference herein. Radio terminals of the ad-hoc, peer-to-peer system thereof routinely exchange routing tables with their neighbors, either after some configurable time delay, which is typically several seconds, or when they note a change in the environment or view of the neighbors. The battery condition of the terminal then becomes a new and critical factor or parameter of the routing update message, which, according to the present invention, is incorporated into the updated routing table messaging.
[0038] Referring to FIGS. 6 and 7 , there is shown the flow charts for a source terminal 60 determining (block 62) the optimal route 64 for the type of call it is sending. In FIG. 7 , the routing table messaging subroutine includes calculated values for the Code Rate (block 66), the Symbol Rate (block 68), the Power Level (70), and the RTS (Request to Send) message to another node-terminal or gateway (block 70), after which is waits for the CTS (Clear to Send) message (block 72) from the other terminal or gateway.
[0039] “Terminal Battery Determination Algorithm”
[0040] The following are algorithms for performing the battery-status check and update of a terminal's battery, and its consideration in the routing decision made by a source-terminal.
[0041]
| /*This algorithm is used by a hand-held terminal to define the battery | ||
| status and will report to other terminals in the routing data exchange: | ||
| */ | ||
| IF power_source = external | ||
| THEN | Battery := infinite | |
| ELSE IF battery_level = full | ||
| THEN Battery := excellent | ||
| ELSE IF battery_level >= config_param_battery | ||
| THEN Battery := poor | ||
| ELSE Battery := critical | ||
| /* config_param_battery is a system parameter that is provisioned | ||
| over the air or the terminal interface that defines the threshold for | ||
| eliminating the terminal from the routing options. | ||
| This should range from 25% to 50% of the available battery power. | ||
| */ | ||
[0042] Terminals exchange routing table information on a regular basis via the time-frame messaging on the control channel of the ad-hoc, peer-to-peer radio system. These messages include information on the terminals that the initiating device can see and the parameters that it understands about those terminals. The critical components are the quality of the link between the initiating device and all those terminals, the data rates that it could maintain on those links, and the congestion level of the terminal. To this information is added the present invention's indication of the battery level of the initiating terminal.
[0043] The routing update message includes a new field battery_condition:
battery_condition (2 bits)
[0044]
| 02 | critical |
| 03 | poor |
| 11 | full |
| 11 | infinite |
[0045] As previously mentioned, there are several schemes that can be employed by the source of a message to determine the optimal route to the destination. The following algorithm is based on a minimum energy routing algorithm.
[0046]
| source-routing (message_ptr,msg-length,destination, msg-type) |
| /* source based routing including link adaptation algorithm |
| */ |
| opt_route(destination, msg_type) |
| /* determine optimal route to destination this will return the best available |
| route based on Class Of Service (COS) from msg_type and other network |
| parameters including link quality and battery life. The returned informa- |
| tion will be used to calculate the data rate and power level |
| */ |
| calc_symbol_rate (sym_rate) |
| calc_code_rate (code_rate) |
| calc_pwr_level (pwr_level) |
| send_msg(RTS,msg_length,destination,sym_rate,code_rate,pwr_level) |
| /* send RTS to first router and await CTS to send the data packet |
[0047] The Symbol Rate is a standard calculation of the number of RF chips to be used to define a symbol or bit of data in the transmission.
[0048] The Code Rate is conventional, and is a function of the direct sequence spread spectrum, and, specifically, the spreading code PN to be used for the transmission.
[0049] Power Level is defined in 1 dB steps between −27 and +28 dBm, where 28 dBm is approximately equivalent to the maximum power allowed under FCC Rules for the ISN band; for other RF spectrums, the range may vary.
opt_route (destination, msg_type)
[0050] RTS refers to Request-To-Send message; CTS refers to Clear-To-Send message; msg refers to the message sent from each terminal. The “code” is one of the four 2-digit codes of the battery status described above.
/*This algorithm determines the best route to the destination based on the COS in the message type.
The following example illustrates the decision process:
- [0051] Route1 term1→term4
- [0052] Low latency, worst battery level=excellent, BER=high
- [0053] Route 2 term1→term2→term4
- [0054] High latency, worst battery level=good, BER=low
- [0055] Route 3 term1→term2→term3→term4
- [0056] High latency, worst battery level=poor, BER=low
- [0057] Route 4 term1→term5→term6→term4
- [0058] Low latency, worst battery level=poor, BER=low
[0059] BER is Bit-Error-Rate; latency is delay.
[0060] In the case of a voice call that has a COS that can tolerate a high BER but not high latency, it would choose route 1 over route 4 because of the battery and because it cannot tolerate high latency.
[0061] In the case of a data call that has a COS that can tolerate high latency but not high BER, it will choose route 2 over route 3 or 4 because of the battery.
[0062] In a second embodiment, instead of utilizing four battery levels in the algorithm of the invention, there are seven battery levels used and reported.
Battery—A value from 0-7 designating the following battery conditions:
[0063]
| 0. | IAP; |
| 1. | Wireless Router; |
| 2. | Subscriber Device with non-battery power; |
| 3. | Subscriber Device with nearly full battery (>80%); |
| 4. | Subscriber Device with battery level (>50%); |
| 5. | Subscriber Device with battery level low (>20%); |
| 6. | Subscriber Device (or Wireless Router) with minimal battery (>0%); |
| 7. | Subscriber Device: Don't Use Ever. This prevention should be |
| capable of being chosen by the network manager remotely. | |
[0064] The following is an example of the routing table messaging used in the present invention incorporating seven such battery status indications.
[0065]
| 1 Ad-Hoc Routing Header | |||
|---|---|---|---|
| Mod ID (8 bits) | Msg ID (8 bits) | Version (8 bits) | TOS (8 bits) |
| Lateral (1 bits) | Sequence Num (8) | Carrier ID (16 bits) | |
| TTL (hops) (7 bits) | |||
| Source Address (48 bits) | |||
| Destination Address (48 bits) | |||
| Payload (X bits) | |||
[0066] This is the standard header for all AHRL inter-node messages. The Payload field may be an IP message to be transmitted, or any other AHRL message going over-the-air. Each field is describes as:
- [0067] Mod ID: the module generating the message
- [0068] Msg ID: the unique message type identified assigned and known on a module-by-module basis.
- [0069] Version: The software version being used by the generating terminal: 4 bits for major rev, and 4 bits for minor rev.
- [0070] TOS: the standard internet TOS field which effects QoS. Inter AHR messages shall set the TOS based on a lookup table of values TBD which is based on the payload being sent.
- [0071] LAT/TTL: The TTL (time to live) field is the estimated hop count based on the number of hops indicated in the routing table. One is subtracted from this count at each relaying node. If the TTL reaches zero, then the message is destroyed. The Lateral bit is used to indicate that this message has been laterally forwarded, and the hop count is not decremented.
- [0072] Carrier ID: This value is used to distinguish one Arachnet system from another.
- [0073] Source Address: The 48-bit hardware address of the originating terminal of the message.
- [0074] Destination Address: The 48-bit hardware address of the destination terminal.
- [0075] Payload: Any block of data that is to be transmitted over-the-air.
[0076]
| 2. Routing Advertisement Message (RA) | ||
|---|---|---|
| 2.1 Routing Advertisement Header | ||
| Node Addr (48-bits) | ||
| Seq. Num (8-bits) | Num Entries (8-bits) | |
| Metrics (32-bits) | ||
- [0077] Note Addr—The 48-bit address of the sender of the Routing Advertisement.
- [0078] Seq Num—A sequence number which is incremented each time a node sends a Routing Advertisement.
- [0079] Num Entries—The number of entries in the Routing Advertisement.
- [0080] Metrics—The metrics associated with a sending node. See section 3.
[0081]
| 2.2 Routing Advertisement Entry | |
|---|---|
| Node Address (48-bits) | |
| Next Hop Address (48-bits) | |
| Metrics (32-bits) | |
| Repeat up to MAX_RA_NODES . . . | |
[0082] This is the Routing Advertisement message, which is defined in the Routing module spect. It is contained within the RT to TC IMM.
- [0083] Node Address—The 48-bit address of the destination being reported by the sender of the Routing Advertisement.
- [0084] Next Hop Address—The 48-bit address of the node that is being used as the next hop from the sender of the Routing Advertisement towards the destination being reported.
- [0085] Metrics—The metrics associated with the destination being reported. See section 3.
[0086]
| 3 Routing Metrics | |||||
|---|---|---|---|---|---|
| Energy (16-bits) | |||||
| Hops-3 | Congestion-3 | Mobility-1 | Ra Heard-1 | Battery-3 | pad-5 |
[0087] The metrics sent in the routing advertisement are used to determine a Link Resistance value that becomes the cost associated with the route to the destination. The metrics are associated with the best path that the sender has currently chose to reach that destination. The following are description of each metric:
- [0088] Energy—A value that is calculated with the formula:
Cost=10 dB+(Power Level)+10* log10 (Max Data Rate/DataRate)
Example 1
Power Level=−10 dbm, Data Rate=8 Mbps
Cost=10+(−10)+10* log10 (8/8)=10+(−10)+0
Cost=10+(−10)+10* log10 (8/8)=10+(−10)+0
Example 2
Power level=+30 dbm, Data Rate=500 kbps.
Cost=10+(+30)+10* log10 (8/0.5)=40+10*1.2=52
The range for this value is 0-52.
Cost=10+(+30)+10* log10 (8/0.5)=40+10*1.2=52
The range for this value is 0-52.
- [0089] Hops—The number of hops to the sender of the RA to the destination.
- [0090] Congestion—The average quantized level of congestion from the sender of the RA to the destination (range 0-7).
- [0091] Mobility—A bit designating whether or not the destination node is currently moving.
- [0092] Ra Heard—A bit desighating whether or not the sender of the RA has recently received an RA from the destination being reported.
- [0093] Battery—A value from 0-7 designating the following battery conditions:
[0094]
| 0. | IAP |
| 1. | Wireless Router |
| 2. | Subscriber Device with non-battery power |
| 3. | Subscriber Device with nearly full battery (>80%) |
| 4. | Subscriber Device with battery level (>50%) |
| 5. | Subscriber Device with battery level low (>20%) |
| 6. | Subscriber Device (or Wireless Router) with minimal battery (>0%) |
| 7. | Subscriber Device: Don't Use Ever. This prevention should be |
| capable of being chosen by the network manager remotely | |
[0095] There are 5 additional bits remaining for future metrics expansion. Also, there are additional bits in the energy field that may be used.
[0096] While a specific embodiment of the invention has been shown and described, it is to be understood that numerous changes and modifications may be made therein without departing from the scope and spirit of the invention.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
1. A wireless ad-hoc, peer-to-peer network comprising:
a plurality of radio terminals, each being adapted to transmit and receive data, each said radio terminal comprising a battery and a controller adapted to generate a routing table for use by other terminals in determining the routing path of said data, said controller being adapted to check the status of said battery in order to include said battery-status in said routing table;
a plurality of wireless routers, each including a controller and being connected to an associated external power supply, such that said controller is adapted to generate a routing table including information indicating that its wireless router is connected to an external power supply; and
a plurality of intelligent access points (IAP), each including a controller and being connected to an associated external power supply, such that said controller is adapted to generate a routing table including information indicating that its IAP is connected to an external power supply;
wherein said radio terminals, wireless routers and IAPs base routing of said data on said external power supply information of said wireless routers and said IAPs and said battery-status information of said radio terminals.
2. The network according to claim 1, wherein said controller of a radio terminal is adapted to check for a plurality of status indicators; said plurality of status indicators comprising at least four said status indicators of: infinite, full, poor and critical; said infinite status indicator indicating a terminal whose power source is external, said full status indicator indicating an approximately fully charged battery, said poor status indicator indicating a substantially discharged battery, and said critical status indicator indicating a battery charge below a predetermined critical value.
3. The network according to claim 2, wherein said controller of a radio terminal is adapted to check for at least all four of said status indicators.
4. The network according to claim 1, wherein said controller of a radio terminal is adapted to determine and report in said routing table information on least-energy routing so that the least amount of energy over a selected route is chosen for routing said data, whereby the minimizing of radiated RF energy is achieved in order to reduce interference between terminals.
5. The network according to claim 1, wherein said controller of a radio terminal is adapted to update the battery status indicator of said respective routing table thereof based on the most recent status report determined by checking the status of the respective said battery.
6. The network according to claim 1, wherein said controller of a radio terminal is further adapted to generate said routing table, said routing table comprising time-frame based messaging, said time-frame based messaging having said battery-status indicator as a section thereof.
7. The network according to claim 6, wherein time-frame based messaging is based on time division duplex (TDD) technique in a code division multiple access (CDMA) system.
8. The network according to claim 6, wherein said routing table of each said terminal also comprises information on least-energy routing so that the least amount of energy over a selected route is chosen for routing said data, whereby the minimizing of radiated RF energy is achieved in order to reduce interference between terminals, said time-frame based messaging also having a section for reporting least-energy routing of said data.
9. The network according to claim 1, wherein said controller of a radio terminal is further adapted to generate information on the class of service (COS) being transmitted, and being adapted to report at least two of the following types of COS information: voice type information, data type information, and video type information, whereby routing of said data is based also on the said type of COS information being transmitted.
10. A method of routing data in a wireless ad-hoc, peer-to-peer network the network comprising a plurality of radio terminals, a plurality of wireless routers, and a plurality of intelligent access points (IAPs), each said radio terminal, wireless router and IAP being adapted to transmit and receive data, each said radio terminal comprising a battery, and each said wireless router and said IAP being connected to an associated external power supply, the method comprising:
controlling each said radio terminal to generate a routing table for use by other terminals in determining the routing path of said data, said routing table including battery-status information of said battery of said radio terminal;
controlling each said wireless router to generate a routing table including information indicating that it is connected to an external power supply;
controlling each said IAP to generate a routing table including information indicating that it is connected to an external power supply; and
controlling said radio terminals, said wireless routers and said IAPs to base routing of said data on said external power supply information of said wireless routers and said IAPs and said battery-status information of said radio terminals.
Patent Citations (127)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4494192(A) | 1985-01-01 | Lew et al. | Applicant |
| US4617656(A) | 1986-10-01 | Kobayashi et al. | Applicant |
| US4736371(A) | 1988-04-01 | Tejima et al. | Applicant |
| US4742357(A) | 1988-05-01 | Rackley | Applicant |
| US4747130(A) | 1988-05-01 | Ho | Applicant |
| US4910521(A) | 1990-03-01 | Mellon | Applicant |
| US5034961(A) | 1991-07-01 | Adams | Applicant |
| US5068916(A) | 1991-11-01 | Harrison et al. | Applicant |
| US5231634(A) | 1993-07-01 | Giles et al. | Applicant |
| US5233604(A) | 1993-08-01 | Ahmadi et al. | Applicant |
| US5241542(A) | 1993-08-01 | Natarajan et al. | Applicant |
| US5317566(A) | 1994-05-01 | Joshi | Applicant |
| US5392450(A) | 1995-02-01 | Nossen | Applicant |
| US5412654(A) | 1995-05-01 | Perkins | Applicant |
| US5424747(A) | 1995-06-01 | Chazelas | Applicant |
| US5502722(A) | 1996-03-01 | Fulghum | Applicant |
| US5517491(A) | 1996-05-01 | Nanni et al. | Applicant |
| US5533026(A) | 1996-07-01 | Ahmadi et al. | Applicant |
| US5555425(A) | 1996-09-01 | Zeller et al. | Applicant |
| US5555540(A) | 1996-09-01 | Radke | Applicant |
| US5572528(A) | 1996-11-01 | Shuen | Applicant |
| US5615212(A) | 1997-03-01 | Ruszczyk et al. | Applicant |
| US5618045(A) | 1997-04-01 | Kagan et al. | Applicant |
| US5621732(A) | 1997-04-01 | Osawa | Applicant |
| US5623495(A) | 1997-04-01 | Eng et al. | Applicant |
| US5627976(A) | 1997-05-01 | McFarland et al. | Applicant |
| US5631897(A) | 1997-05-01 | Pacheco et al. | Applicant |
| US5644576(A) | 1997-07-01 | Bauchot et al. | Applicant |
| US5652751(A) | 1997-07-01 | Sharony | Applicant |
| US5680392(A) | 1997-10-01 | Semaan | Applicant |
| US5684794(A) | 1997-11-01 | Lopez et al. | Applicant |
| US5687194(A) | 1997-11-01 | Paneth et al. | Applicant |
| US5696903(A) | 1997-12-01 | Mahany | Applicant |
| US5701294(A) | 1997-12-01 | Ward et al. | Applicant |
| US5706428(A) | 1998-01-01 | Boer et al. | Applicant |
| US5717689(A) | 1998-02-01 | Ayanoglu | Applicant |
| US5745483(A) | 1998-04-01 | Nakagawa et al. | Applicant |
| US5748624(A) | 1998-05-01 | Kondo | Applicant |
| US5774876(A) | 1998-06-01 | Wooley et al. | Applicant |
| US5781540(A) | 1998-07-01 | Malcolm et al. | Applicant |
| US5787076(A) | 1998-07-01 | Anderson et al. | Applicant |
| US5787080(A) | 1998-07-01 | Hulyalkar et al. | Applicant |
| US5794154(A) | 1998-08-01 | Bar-On et al. | Applicant |
| US5796732(A) | 1998-08-01 | Mazzola et al. | Applicant |
| US5796741(A) | 1998-08-01 | Saito et al. | Applicant |
| US5805593(A) | 1998-09-01 | Busche | Applicant |
| US5805842(A) | 1998-09-01 | Nagaraj et al. | Applicant |
| US5805977(A) | 1998-09-01 | Hill et al. | Applicant |
| US5809518(A) | 1998-09-01 | Lee | Applicant |
| US5822309(A) | 1998-10-01 | Ayanoglu et al. | Applicant |
| US5844905(A) | 1998-12-01 | McKay et al. | Applicant |
| US5845097(A) | 1998-12-01 | Kang et al. | Applicant |
| US5857084(A) | 1999-01-01 | Klein | Applicant |
| US5870350(A) | 1999-02-01 | Bertin et al. | Applicant |
| US5877724(A) | 1999-03-01 | Davis | Applicant |
| US5881095(A) | 1999-03-01 | Cadd | Applicant |
| US5881372(A) | 1999-03-01 | Kruys | Applicant |
| US5886992(A) | 1999-03-01 | Raatikainen et al. | Applicant |
| US5896561(A) | 1999-04-01 | Schrader et al. | Applicant |
| US5903559(A) | 1999-05-01 | Acharya et al. | Applicant |
| US5909651(A) | 1999-06-01 | Chander et al. | Applicant |
| US5936953(A) | 1999-08-01 | Simmons | Applicant |
| US5943322(A) | 1999-08-01 | Mayor et al. | Applicant |
| US5987011(A) | 1999-11-01 | Toh | Applicant |
| US5987033(A) | 1999-11-01 | Boer et al. | Applicant |
| US5991279(A) | 1999-11-01 | Haugli et al. | Applicant |
| US6016311(A) | 2000-01-01 | Gilbert et al. | Applicant |
| US6028853(A) | 2000-02-01 | Haartsen | Applicant |
| US6029074(A) | 2000-02-01 | Irvin | Applicant |
| US6029217(A) | 2000-02-01 | Arimilli et al. | Applicant |
| US6034542(A) | 2000-03-01 | Ridgeway | Applicant |
| US6044062(A) | 2000-03-01 | Brownrigg et al. | Applicant |
| US6047330(A) | 2000-04-01 | Stracke, Jr. | Applicant |
| US6052594(A) | 2000-04-01 | Chuang et al. | Applicant |
| US6052752(A) | 2000-04-01 | Kwon | Applicant |
| US6058106(A) | 2000-05-01 | Cudak et al. | Applicant |
| US6064626(A) | 2000-05-01 | Stevens | Applicant |
| US6067291(A) | 2000-05-01 | Kamerman et al. | Applicant |
| US6067297(A) | 2000-05-01 | Beach | Applicant |
| US6078566(A) | 2000-06-01 | Kikinis | Applicant |
| US6088337(A) | 2000-07-01 | Eastmond et al. | Applicant |
| US6097704(A) | 2000-08-01 | Jackson et al. | Applicant |
| US6104712(A) | 2000-08-01 | Robert et al. | Applicant |
| US6108316(A) | 2000-08-01 | Agrawal et al. | Applicant |
| US6108738(A) | 2000-08-01 | Chambers et al. | Applicant |
| US6115580(A) | 2000-09-01 | Chuprun et al. | Applicant |
| US6122690(A) | 2000-09-01 | Nannetti et al. | Applicant |
| US6130881(A) | 2000-10-01 | Stiller et al. | Applicant |
| US6132306(A) | 2000-10-01 | Trompower | Applicant |
| US6163699(A) | 2000-12-01 | Naor et al. | Applicant |
| US6178337(B1) | 2001-01-01 | Spartz et al. | Applicant |
| US6192053(B1) | 2001-02-01 | Angelico et al. | Applicant |
| US6192230(B1) | 2001-02-01 | van Bokhorst et al. | Applicant |
| US6208870(B1) | 2001-03-01 | Lorello et al. | Applicant |
| US6222463(B1) | 2001-04-01 | Rai | Applicant |
| US6223240(B1) | 2001-04-01 | Odenwald et al. | Applicant |
| US6240294(B1) | 2001-05-01 | Hamilton et al. | Applicant |
| US6246875(B1) | 2001-06-01 | Seazholtz et al. | Applicant |
| US6249516(B1) | 2001-06-01 | Brownrigg et al. | Applicant |
| US6275707(B1) | 2001-08-01 | Reed et al. | Applicant |
| US6285892(B1) | 2001-09-01 | Hulyalkar | Applicant |
| US6304556(B1) | 2001-10-01 | Haas | Applicant |
| US6327300(B1) | 2001-12-01 | Souissi et al. | Applicant |
| US6349091(B1) | 2002-02-01 | Li | Applicant |
| US6349210(B1) | 2002-02-01 | Li | Applicant |
| US6359872(B1) | 2002-03-01 | Mahany et al. | Applicant |
| US6377805(B1) | 2002-04-01 | Anvekar et al. | Examiner |
| US6522900(B1) | 2003-02-01 | Cho | Examiner |
| US2001/0053699(A1) | 2001-12-01 | McCrady et al. | Applicant |
| US2003/0045295(A1) | 2003-03-01 | Stanforth | Examiner |
| CA2132180 | 1996-03-01 | Applicant | |
| EP513841(A2) | 1992-11-01 | Applicant | |
| EP627827(A2) | 1994-12-01 | Applicant | |
| EP924890(A2) | 1999-06-01 | Applicant | |
| FR2683326 | 1993-07-01 | Applicant | |
| WO9608884 | 1996-03-01 | Applicant | |
| WO9724005 | 1997-07-01 | Applicant | |
| WO9839936 | 1998-09-01 | Applicant | |
| WO9912302 | 1999-03-01 | Applicant | |
| WO34932 | 2000-06-01 | Applicant | |
| WO110154 | 2001-02-01 | Applicant | |
| WO133770 | 2001-05-01 | Applicant | |
| WO135567 | 2001-05-01 | Applicant | |
| WO137481 | 2001-05-01 | Applicant | |
| WO137482 | 2001-05-01 | Applicant | |
| WO137483 | 2001-05-01 | Applicant | |
| WO235253 | 2002-05-01 | Applicant |
Non-Patent Literature (23)
- Wong et al., “Soft Handoffs in CDMA Mobile Systems”, Dec. 1997, IEEE Personal Communications.Applicant
- Wong et al., “A Pattern Recognition System for Handoff Algorithms”, Jul. 2000, IEEE Journal on Selected Areas in Communications, vol. 18, No. 7.Applicant
- Andras G. Valko, “Cellular IP: A New Approach to Internet Host Mobility”, Jan. 1999, ACM Computer Communication Review.Applicant
- Richard North, Dale Bryan and Dennis Baker, “Wireless Networked Radios: Comparison of Military, Commercial, and R&D Protocols”, Feb. 28-Mar. 3, 1999, 2nd Annual UCSD Conference on Wireless Communications, San Diego CA.Applicant
- Benjamin B. Peterson, Chris Kmiecik, Richard Hartnett, Patrick M. Thompson, Jose Mendoza and Hung Nguyen, “Spread Spectrum Indoor Geolocation”, Aug. 1998, Navigation: Journal of the Institute of Navigation, vol. 45, No. 2, summer 1998.Applicant
- “A Review of Current Routing Protocols for Ad-Hoc Mobile Wireless Networks”, Royer, et al., Univ of Calif.Applicant
- “The Dynamics Source Routing Protocol for Mobile AD Hoc Networks”, IETF MANET Working Group;Josh Broch, et al., Dec. 1998.Applicant
- “Ad hoc On-Demand Distance Vector Routing draft-ietf-manet-aodv-08.txt”, Mobile Ad Hoc Networking Working Group, Charles E. Perkins, et al., Mar. 2, 2001.Applicant
- “Optimized Link State Routing Protocol”, IETF MANET Working Gr Group , Philippe Jacquet, et al, Sep. 2, 2001.Applicant
- “The Dynamic Source Routing for Mobile Ad Hoc Networks”, IETF MANET Working Group, David B. Johnson, et al., Mar. 2, 2001.Applicant
- “Topology Control of Multihop Wireless Networks using Transmit Power Adjustment”, by Ram Ramanathan and Regina Rosales-Hain; BBN Technologies (Division of GTE), Cambridge, Mass. 1997.Applicant
- “Reversing the Collision-Avoidance Handshake in Wireless Networks” by J.J. Garcia-Luna-Aceves and Asimmakis Tzamaloukas; Baskin School of Engineering, University of California, Santa Cruz, 1997.Applicant
- “Self-Organizing, Self-Healing Wireless Networks”, by Chip Elliot and Bob Helle; BBN Technologies, Cambridge, Mass: IEEE, 2000.Applicant
- “A Performance Comparison of Multi-Hop Wireless Ad Hoc Netwrk Routing Protocols”, by Josh Brock, et al., Carnegie Mellon University, Pttsburgh, Pa., Proceedings of the Fourth Annual ACM/IEEE International Conference on Mobile Computing and Networking; 1998.Applicant
- “USAP:A Unifying Dynamic Distributed Multichannel TDMA Slot Assignment Protocol”, by C. David Young,Rockwell International, Richardson,Texas.Applicant
- “Net Throughput with IEEE 802.11 Wireless LANs”, by Ad Kamerman and Guido Aben, Lucent Tech., Nieuwegein,The Netherlands.Applicant
- “Transmission-Efficient Routing in Wireless Networks Using Link-State Information”, by J.J. Garcia-Lunas-Aceves, Baskin School of Engineering, University of California, Santa Cruz; 1997.Applicant
- “The Core-Assisted Mesh Protocol”, by J.J. Garcia-Lunas-Aceves and Ewerton L. Madruga, Baskin School of Engineering, University of California, Santa Cruz; 1997.Applicant
- “Optimization of an Adaptive Link Control Protocol for Multimedia Packet Radio Networks”, by J.R.McChesney, et al.; ITT Industries Aerospace Comm. Div.; Ft.Wayne,IN ;1997.Applicant
- “Hierarchically-Organized, Multihop Mobile Wireless Networks for Quality-of-Service Support”, by Ram Ramanathan and Martha Steenstrup; BBN Systems and Tech., Cambridge, Mass. 1995.Applicant
- “Dynamic Multipoint Virtual Circuits for Multimedia Traffic in Multihop Mobile Wireless Networks”, by Martha E. Steenstrup; BBN Tech., Cambridge, Mass. 1995.Applicant
- “Collision-Avoidance Transmission Scheduling for Ad-Hoc Networks”, by Zhenyu Tang and J.J. Garcia-Luna-Aceves, University of California Santa Cruz, Calif., 1997.Applicant
- “QoS Networking with Adaptive Link Control and Tactical Multi-Channel Software Radios”, by George Vardakas, et al., Communications Systems Div. of Raytheon Systems Co., San Diego, Calif.; 1997.Applicant