Source: http://www.google.com/patents/US8126470?ie=ISO-8859-1&dq=inventor:%22Arthur+R.+Hair%22
Timestamp: 2014-03-14 11:07:20
Document Index: 246683872

Matched Legal Cases: ['Application No. 200780024815', 'Application No. 200780024974', 'Application No. 2009', 'Application No. 2009', 'Application No. 2008', 'Application No. 2008', 'Application No. 2009117689']

Patent US8126470 - Topology and route discovery and management for relay networks - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsVarious example embodiments are disclosed relating to route discovery and management in relay networks. In an example embodiment, a first message may be received at a first network station in a wireless network. It may be determined whether the received first message includes an identifier of a second...http://www.google.com/patents/US8126470?utm_source=gb-gplus-sharePatent US8126470 - Topology and route discovery and management for relay networksAdvanced Patent SearchPublication numberUS8126470 B2Publication typeGrantApplication numberUS 11/480,767Publication dateFeb 28, 2012Filing dateJul 3, 2006Priority dateJul 3, 2006Also published asCN101485144A, CN101485144B, CN101485150A, CN101485150B, EP2041918A2, EP2041918A4, US20080291847, WO2008004066A2, WO2008004066A3Publication number11480767, 480767, US 8126470 B2, US 8126470B2, US-B2-8126470, US8126470 B2, US8126470B2InventorsHaihong ZhengOriginal AssigneeNokia CorporationExport CitationBiBTeX, EndNote, RefManPatent Citations (32), Non-Patent Citations (32), Referenced by (4), Classifications (20), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetTopology and route discovery and management for relay networksUS 8126470 B2Abstract Various example embodiments are disclosed relating to route discovery and management in relay networks. In an example embodiment, a first message may be received at a first network station in a wireless network. It may be determined whether the received first message includes an identifier of a second network station indicating an attachment of a network node to the second network station. The received first message may be modified to include an identifier of the first network station indicating an attachment of the network node to the first network station if it is determined that the received message does not include the identifier of the second network station. The received first message may be forwarded to a third network station. Various techniques may also be provided for updating and managing a network topology, e.g., for discovering, updating, and selecting communication paths for network traffic.
receiving a first message at a first relay station in a wireless network;
determining whether the received first message includes a relay station identifier of a second relay station indicating an attachment of a network node to the second relay station;
modifying the received first message to include a relay station identifier of the first relay station indicating an attachment of the network node to the first relay station based on determining that the received first message does not include the identifier of the second relay station; and
forwarding the received first message upstream toward a base station.
2. The method of claim 1 wherein the network node comprises a mobile station.
3. The method of claim 1 wherein the first message includes an attachment request.
4. The method of claim 1 wherein the first message includes a ranging request message.
5. The method of claim 1 wherein the first message includes an IEEE 802.16 ranging request (RNG-REQ) message.
the first message includes a type/length/value (TLV) field;
the determining includes determining whether the TLV field included in the first message includes the relay station identifier of the second relay station indicating the attachment of the network node to the second relay station;
the modifying the received first message comprises modifying the TLV field to include the identifier of the first relay station indicating the attachment of the network node to the first relay station based on determining that the TLV field does not include the identifier of the second relay station.
7. The method of claim 1 wherein the base station receives the forwarded first message and determines one or more communication paths between the base station and the network node that includes the network node based on the forwarded first message.
8. The method of claim 1 wherein one or more relay stations receive the forwarded first message and determine one or more communication paths between the base station and the network node that includes the network node based on the forwarded first message.
9. The method of claim 1 wherein the base station receives the forwarded first message and determines a network topology based on the forwarded first message.
10. The method of claim 1 wherein one or more relay stations receive the forwarded first message and determine a network topology based on the forwarded first message.
11. The method of claim 1, wherein the network node receives service from the identified first relay station via the indicated attachment.
12. The method of claim 1, wherein the received first message includes only the identifier of the first relay station or the identifier of the second relay station.
determining whether the received first message indicates that a network node is attaching to the first relay station;
forwarding the received first message to a second relay station; and
sending a second message upstream to the second relay station, the second message including an indication that the network node is directly attached to the first relay station based on the first network station determining that the received first message indicates that the network node is attaching to the first network station.
14. The method of claim 13 wherein the first message includes a ranging request message.
15. The method of claim 13 wherein the second message includes a topology update request message.
16. The method of claim 13 wherein a base station receives the second message and determines a network topology based on the second message.
17. The method of claim 13 wherein one or more relay stations receive the second message and determine a network topology based on the second message.
18. The method of claim 13 wherein a base station receives the second message and determines one or more communication paths between the base station and the network node that includes the network node based on the second message.
19. The method of claim 13 wherein one or more relay stations receive the second message and determine one or more communication paths between a base station and the network node that includes the network node based on the second message.
20. The method of claim 13 and further comprising receiving a third message indicating that a base station received the second message.
21. The method of claim 20 wherein the third message includes a topology update response message.
22. The method of claim 13, wherein the network node receives service from the first relay station via the indicated attachment between the first network node and the first relay station.
23. The method of claim 13, wherein the received first message includes only the indication of attachment to the first relay station.
BACKGROUND The rapid diffusion of Wireless Local Area Network (WLAN) access and the increasing demand for WLAN coverage is driving the installation of a very large number of Access Points (AP). The most common WLAN technology is described in the Institute of Electrical and Electronics Engineers IEEE 802.11 family of industry specifications, such as specifications for IEEE 802.11b, IEEE 802.11g and IEEE 802.11a. Other wireless technologies are being developed, such as IEEE 802.16 or WiMAX technology. A number of different 802.11 task groups are involved in developing specifications relating to improvements to the existing 802.11 technology. For example, a draft specification from the IEEE 802.11e Task Group has proposed a set of QoS parameters to be used for traffic between an Access Point and a station. See, e.g., Tim Godfrey, �Inside 802.11e: Making QoS A Reality Over WLAN Connections,� CommsDesign, Dec. 19, 2003. Similarly in Ultra Wideband (UWB) environment, the WiMedia Alliance has published a draft standard, �Distributed Medium Access Control (MAC) for Wireless Networks,� Release 1.0, Dec. 8, 2005.
As another example, a wireless relay network may include a multi-hop system in which end nodes such as mobile stations or subscriber stations (MS/SSs) may be coupled to a base station (BS) or Access Point (AP) via one or more relay stations (RSs). Thus, traffic between MS/SSs and the BS/AP may pass and be processed by the relay stations. The 802.16 Mobile Multi-hop Relay (MMR), referenced in IEEE 802.16 WG, is an example of a set of specifications relating to the relay concept. The MMR specifications include a focus on defining a network system that uses relay stations (RSs) to extend network coverage and/or enhance system throughput. These are a few examples of wireless network specifications, and there are many other technologies and standards being developed.
In a wireless network system without relay stations, a MS/SS may attach to a base station (BS) directly, and therefore, the BS may be aware of the route (i.e., only the one-hop route) to each of the attached MS/SS. However, when a relay station (RS) is introduced between a MS/SS and a BS, the BS may not be able to easily determine a routing path, or communication path between the MS/SS and BS. However, in scenarios such as, for example, centralized scheduling wherein a BS may schedule the resources for traffic transmissions over every segment on a communication path between a MS/SS and the BS, it may be desirable for the BS to be able to obtain or determine information regarding a complete communication path between the MS/SS and the BS. Moreover, it may be desirable for such an obtained or determined communication path to be easily managed and/or updated.
SUMMARY Various embodiments are disclosed relating to wireless networks, and also relating to topology and route discovery and management in a relay network.
According to an embodiment, a method may include receiving a first message at a first network station in a wireless network. According to an example embodiment, the first message may, for example, include a ranging request message. The method may further include determining whether the received first message includes an identifier of a second network station indicating an attachment of a network node to the second network station. The method may further include modifying the received first message to include an identifier of the first network station indicating an attachment of the network node to the first network station if it is determined that the received message does not include the identifier of the second network station. According to an example embodiment, the received first message may be modified, for example, to include a type/length/value (TLV) field that includes the identifier of the first network station indicating the attachment of the network node to the first network station if it is determined that the received first message does not include an identifier of a second network station. The received first message may be forwarded to a third network station.
According to another embodiment, a method may include receiving a first message at a first network station in a wireless network. According to an example embodiment, the first message may include a ranging request message. The method may further include determining whether the received first message indicates that a network node is attaching to the first network station. The received first message may be forwarded to a second network station. Further, a second message may be sent to the second network station, the second message including an indication that the network node is directly attached to the first network station if it is determined that the received first message indicates that the network node is attaching to the first network station. According to an example embodiment, the second message may include a topology update request message. According to an example embodiment, one or more relay stations may receive the second message and determine the topology and/or a communication path between the base station and the network node that includes the network node based on the second message.
According to another embodiment, a method may include determining that a network node is detaching from a first network station in a wireless network. The method may further include sending a request to a second network station, the request including an indication that the network node is detaching from the first network station.
According to an example embodiment, the request may include a topology update request message. According to an example embodiment, a base station may receive the request and determine a network topology based on the request.
According to another embodiment, a method may include generating a message, at a first network station in a wireless network, the message including one or more identifiers of one or more other network stations indicating that the first network station is attaching to the one or more other network stations. The method may further include sending the message to the one or more other network stations.
According to an example embodiment, the message may include a ranging request message. According to an example embodiment, a base station may receive the message and determine a network topology based on the message.
According to another embodiment, a method may include updating path information associated with a current communication path to indicate an updated communication path between a base station and a network node in a wireless network. The method may further include sending a message indicating the updated communication path to each network node included in one or more of the current communication path or the updated communication path.
According to an example embodiment, each one of the network nodes that receives the message may update local data associated with network communication paths in a storage device associated with the each one of the network nodes based on the received message. According to an example embodiment, the sending the message may include determining a multicast group including each network node included in one or more of the current communication path or the updated communication path, determining a multicast address associated with the multicast group, and sending the message based on the multicast address.
According to another embodiment, a method may include determining that a network node in a wireless network is requesting a connection to a network station included in a first communication path between the network node and a base station. The method may further include determining one or more other communication paths between the network node and the base station. The method may further include selecting one or more selected paths from the first communication path and the one or more other communication paths based on network parameters. According to an example embodiment, the selecting may include selecting one or more selected paths from the first communication path and the one or more other communication paths based on network parameters, wherein the one or more selected paths include an uplink path and a downlink path. The method may further include sending a message indicating one of the selected communication paths to each network station that is included in the one of the selected communication paths.
According to an example embodiment, the sending of the message may include determining a multicast group including each network node included in the one of the selected communication paths, determining a multicast address associated with the multicast group, and sending the message based on the multicast address.
BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a block diagram illustrating a wireless network according to an example embodiment.
FIGS. 4 a-4 b are block diagrams illustrating wireless relay networks according to example embodiments.
FIGS. 5 a-5 b are block diagrams illustrating wireless relay networks according to example embodiments.
FIG. 7 is a flow chart illustrating operation of a wireless node according to an example embodiment.
FIG. 8 is a flow chart illustrating operation of a wireless node according to an example embodiment.
FIG. 9 is a flow chart illustrating operation of a wireless node according to an example embodiment.
FIG. 10 is a flow chart illustrating operation of a wireless node according to an example embodiment.
FIG. 12 is a block diagram illustrating an apparatus that may be provided in a wireless node according to an example embodiment.
DETAILED DESCRIPTION Referring to the Figures in which like numerals indicate like elements, FIG. 1 is a block diagram illustrating a wireless network 102 according to an example embodiment. Wireless network 102 may include a number of wireless nodes or stations, such as an access point (AP) 104 or base station and one or more mobile stations or subscriber stations, such as stations 108 and 110. While only one AP and two mobile stations are shown in wireless network 102, any number of APs and stations may be provided. Each station in network 102 (e.g., stations 108, 110) may be in wireless communication with the AP 104, and may even be in direct communication with each other. Although not shown, AP 104 may be coupled to a fixed network, such as a Local Area Network (LAN), Wide Area Network (WAN), the Internet, etc., and may also be coupled to other wireless networks.
FIG. 3 b is a diagram of a multi-hop environment according to an example embodiment. A group of wireless nodes 332, 334, which may be mobile stations or subscriber stations (MS/SS) may each be coupled via a wireless link to a wireless node 330. As an example, the wireless nodes 332, 334 may include mobile telephones, wireless digital assistants (PDAs), or other types of wireless access devices, or mobile stations. The term �node� or �wireless node� or �network node� or �network station� may refer, for example, to a wireless station, e.g., a subscriber station or mobile station, an access point or base station, a relay station or other intermediate wireless node, or other wireless computing device, as examples. Wireless node 330 may include, for example, a relay station or other node. Wireless node 330 and other wireless nodes 322, 324 may each be coupled to a wireless node 320 via a wireless link. Wireless node 320 and other wireless nodes 308, 310 may each may be coupled to a wireless node 304 via a wireless link. Wireless node 304 may be, for example, a base station (BS), access point (AP) or other wireless node. Wireless node 304 may be coupled to a fixed network, such as network 306, for example. Frames or data flowing from nodes 332, 334 to 330, 322 324, and 330 to 320, and 308, 310, 320 to node 304 may be referred to as flowing in the uplink (UL) or upstream direction, whereas frames flowing from node 304 to nodes 308, 310, and to node 320 and then to nodes 330, 322, 324, 332, and 334 may be referred to as flowing in the downlink (DL) or downstream direction, for example.
FIGS. 4 a-4 b are block diagrams illustrating wireless relay networks according to example embodiments. According to an example embodiment, an example relay network may include n levels of RSs. As an example, a two-level-relay-station architecture is illustrated in FIG. 4 a. Thus, as shown in the example, MS/SS 408, MS/SS 410, and RS1 420 are coupled to, or directly attached to a base station BS 404.
Similarly, as shown in the example, MS/SS 422, MS/SS 424, and RS2 430 are coupled to, or directly attached to the RS1 420. Further, as shown in the example, MS/SS 432 and MS/SS 434 are coupled to, or directly attached to the relay station RS2 430. The term �attach� may, for example, refer to connecting to a network system or network node over a link, for example, a node may attach to a network system or another node by directly coupling with the other node. The term �attachment� may thus, for example, refer to a connection to a network system or network node over a link, for example, via a direct coupling between network nodes. Generally, a node may attach or connect to a system in order to obtain service from the system via another node.
For the generic example as shown, a wireless node indicated as RS0 may include a base station. According to an example embodiment, one or more relay stations, for example, RSi 440, RSi+1 450 may receive data units and forward the data units to the next level of the wireless relay network.
FIGS. 5 a-5 b are block diagrams illustrating wireless relay networks according to example embodiments. As shown in FIG. 5 a, a Mobile Multi-hop Relay base station (MMR-BS) 504 may have a relay station, for example, RS1 506, directly coupled, or directly attached to MMR-BS 504. Further, as shown, a relay station, for example, RS2 508 may be directly attached to RS1 506. Other intermediate network nodes may be included in a communication path between a relay station RSn−1 510 and RS2 508. Additionally, a relay station RSn 512 may be attached to RSn−1 510. Multi-hop subscriber stations, for example, MS/SS 514, 516 may be attached to RSn 512. Thus, as shown in FIG. 5 a, there may exist communication paths, for example, between MMR-BS 504 and MS/SS 514 and between MMR-BS 504 and MS/SS 516. For example, a communication path between MMR-BS 504 and MS/SS 514 may include MMR-BS 504, RS1 506, RS2 508, RSn−1 510, RSn 512, and all network nodes in a communication path between RS2 508 and RSn−1 510. As another example, a communication path between MMR-BS 504 and MS/SS 516 may include MMR-BS 504, RS1 506, RS2 508, RSn−1 510, RSn 512, and all network nodes in a communication path between RS2 508 and RSn−1 510. The MS/SS 514, 516 may also include mobile stations.
As shown in FIG. 5 b, a relay station, for example, RS3 534 may be directly attached to multiple network nodes, for example, relay stations RS1 530, RS2 532, which may both be directly attached to a base station, for example, MMR-BS 504. Thus, for the example shown in FIG. 5 b, there may exist two or more communication paths between MMR-BS 504 and RS3 534: for example, a communication path that includes MMR-BS 504, RS1 530, and RS3 534, and a communication path that includes MMR-BS 504, RS2 532, and RS3 534. For example, one of the communication paths may include an uplink (UL) communication path between MMR-BS 504 and RS3 534 and another may include a downlink (DL) communication path between MMR-BS 504 and RS3 534.
The various example embodiments described herein may be applicable to a wide variety of networks and technologies, such as WLAN networks (e.g., IEEE 802.11 type networks), IEEE 802.16 WiMAX networks, 802.16 Mobile Multi-hop Relay (MMR) networks, as referenced in IEEE 802.16 WG, WiMedia networks, Ultra Wide Band networks, cellular networks, radio networks, or other wireless networks. In another example embodiment, the various examples and embodiments may be applied, for example, to a mesh wireless network, where a plurality of mesh points (e.g., Access Points) may be coupled together via wired or wireless links. The various example embodiments described herein may be applied to wireless networks, both in an infrastructure mode where an AP or base station may communicate with a station (e.g., communication occurs through APs), as well as an ad-hoc mode in which wireless stations may communicate directly via a peer-to-peer network, for example.
A wireless relay network may be an example of a multi-hop system in which end nodes, for example, mobile stations or subscriber stations (MS/SS), may be connected to a base station via one or more relay stations, such as RS1 320 and RS2 330, for example. Traffic between the mobile stations or subscriber stations and the base station may pass through, and be processed by, the relay stations RS1 320 and RS2 330, for example. As an example, a relay station may be used to extend the network coverage and/or enhance the system throughput. For example, the traffic sent from a relay station may be scheduled by the relay station itself or scheduled by the base station instead. In some cases, a relay station may receive and decode a frame from a base station, and then forward the frame to the respective mobile station or subscriber station.
The term �wireless node� or �network station� or �node,� or the like, may include, for example, a wireless station, such as a mobile station or subscriber station, an access point (AP) or base station, a relay station, a wireless personal digital assistant (PDA), a cell phone, an 802.11 WLAN phone, a WiMedia device, a WiMAX device, a wireless mesh point, or any other wireless device. These are merely a few examples of the wireless devices and technologies that may be used to implement the various example embodiments described herein, and this disclosure is not limited thereto.
In a wireless network system without relay stations, a MS/SS may attach to a base station (BS) directly, and therefore, the BS is aware of the route (i.e., only the one-hop route) to each of the attached MS/SS. However, when a relay station (RS) is introduced between a MS/SS and a BS, an initial attachment request, e.g., a Ranging Request (RNG-REQ) in accordance with IEEE 802.16, may be sent from the MS/SS to the BS through one or more RSs. If there are two or more RSs on the path between a MS/SS and a BS, e.g., as discussed regarding MMR-BS 504, RS1 506, . . . , RSn 512, MS/SS 514 with regard to FIG. 5 a, then upon receiving the initial attachment request, the BS, e.g., MMR-BS 504 may be able to determine the last RS, e.g., RS1 506, on the path from the MS/SS 514 to the MMR-BS 504 as shown in FIG. 5 a, but not all the other RSs on the path. Thus the BS, e.g., MMR-BS 504 may not be able to obtain the topology as well as the routing path between the MS/SS, e.g., MS/SS 514 and the BS, e.g., MMR-BS 504.
However, in scenarios such as, e.g., centralized scheduling wherein a BS may schedule the resources for traffic transmissions over every segment on the path between a MS/SS and the BS, the BS may need to determine an exact path between a MS/SS and the BS. If the BS is able to determine the exact path, then as a result of determining a route between the MS/SS and the BS, the BS may determine information relating to the number of hops, the radio condition, etc., on each path. Such information may be used, for example, for the BS to determine scheduling algorithms during regular traffic sessions or during handover.
According to an example embodiment, when a RS, e.g., RS1 506 as shown in FIG. 5 a, attaches directly to a BS, e.g., MMR-BS 504, the BS may record the path to the RS as a direct link. For example, the BS may store information associated with the path as network topology information, for example, in a storage device associated with the BS.
The term �network topology� may refer, for example, to a pattern of links connecting pairs of nodes of a network. Thus, a given node may have one or more links to other nodes, and the links may appear in a variety of different shapes. For example, a simple connection may include a one-way link between two devices. More generally, the term �network topology� or �topology� may be used to describe a configuration of a computer network. Thus, for example, each of FIGS. 1-5 b may be understood to represent various network topologies.
When a RS, e.g., RS2 508 in FIG. 5 a, acting as a MS/SS attaches to the system, e.g., via RS1 506, e.g., by a direct coupling with RS1 506, RS2 508 may send an attachment request, for example, via a ranging request message. Upon receiving the attachment request, RS1 506, e.g., may stamp its signature, e.g., a RS identifier associated with RS1 506, to the attachment request and may forward the modified attachment request to the BS, e.g., the MMR-BS 504. Upon receiving the attachment request from RS2 508 with the signature of RS1 506, the BS, e.g., MMR-BS 504, may determine that RS2 508 is attached to the system via RS1 506. Since MMR-BS 504 may have already determined the route between MMR-BS 504 and RS1 506, e.g., as a result of the RS1 506 attachment process, MMR-BS 504 may determine the topology and/or a path between MMR-BS 504 and RS2 508. The BS, e.g., MMR-BS 504 may then update its network topology information, e.g., to indicate a communication path between MMR-BS 504 and RS2 508 that includes RS1 506.
According to an example embodiment, this technique may be extended as other network nodes attach to network nodes in the current network topology. Thus, when a RS, e.g., RSn 512 in FIG. 5 a 2, acting as a MS/SS, attaches to the system, e.g., via RSn−1 510, RSn 512 may send an attachment request, for example, via a ranging request message. Upon receiving the attachment request, RSn−1 510 may stamp its signature to the attachment request and forward the modified attachment request to the BS, e.g., MMR-BS 504. Any other RSs beyond RSn−1 in the relevant communication path may simply forward the modified attachment request to the next hop. Upon receiving the modified attachment request from RSn 512 with the signature of RSn−1 510 (e.g., an RS-ID associated with RSn−1 510), the BS, MMR-BS 504 may determine that RSn 512 is attached to the system via RSn−1 510. Since MMR-BS 504 may have already determined the route between the MMR-BS 504 and RSn−1 510, e.g., as a result of the RSn−1 512 attachment process, MMR-BS 504 may determine the topology and/or a path between MMR-BS 504 and RSn 512. MMR-BS 504 may then update the network topology information to indicate a communication path between MMR-BS 504 and RSn 512.
When a MS/SS, e.g., MS/SS 514 attaches to the system via RSn 512, the MS/SS 514 may send an attachment request, for example, via a ranging request message. Upon receiving the attachment request, RSn 512 may stamp its signature (e.g., an RS-ID associated with RSn 512) to the attachment request and forward the modified attachment request to the BS, e.g., MMR-BS 504. Any other RSs beyond RSn 512 (e.g., RSn−1 510, RS2 508, RS1 506) may simply forward the modified attachment request to the next hop. Upon receiving the modified attachment request from the MS/SS 514 with the signature of RSn 512, the BS, e.g., MMR-BS 504 may determine that the MS/SS 514 is attached to the system via RSn 512. Since the MMR-BS 504 may have already determined the route, e.g., communication path, between the MMR-BS 504 and RSn 512, e.g., as a result of the RSn 512 attachment process, the MMR-BS 504 may determine the topology and/or a route or communication path between the MMR-BS 504 and MS/SS 514. MMR-BS 504 may then update the network topology information to indicate the communication path between MMR-BS 504 and MS/SS 514.
According to an example embodiment, a signature or stamp of a RS may include, for example, a RS-ID or other form of identity that may uniquely identify the RS. According to an example embodiment, the attachment request may include a ranging request (RNG-REQ) message. According to an example embodiment, the signature or stamp of the RS may be added to a received RNG-REQ message, e.g., by adding to the RNG-REQ message a TLV field including an RS-ID before forwarding the modified RNG-REQ message to the next hop toward the MMR-BS 504.
The techniques described herein may be used in accordance with an IEEE 802.16 system, wherein the attachment request may include, for example, a ranging request (RNG-REQ) message as specified by IEEE 802.16, with enhancements including the RS signature. However, it is understood that the techniques described herein may apply to any type of network system, including network systems other than IEEE 802.16 network systems.
A ranging request (RNG-REQ) message, for example as specified by IEEE 802.16, may be transmitted by a MS/SS at initialization and periodically, for example, to determine network delay and to request power and/or a downlink burst profile change. The RNG-REQ message may be sent, for example, in initial ranging and data grant intervals.
An example format of an example ranging request message is shown in Table 1 below.
Example RNG-REQ message format
RNG-REQ( ) {
Management Message Type = 4
As shown, a RNG-REQ message may include type/length/value (TLV) fields. According to an example embodiment, a TLV field may include an RS-ID TLV field, which may include an identifier associated with a RS. It is understood that a format of a RNG-REQ message may differ from the format shown in Table 1 without diverging from the scope of the present discussion.
A type/length/value (TLV) scheme, for example as specified by IEEE 802.16 generally, may include a formatting scheme that adds a tag to each transmitted parameter that includes the parameter type (and implicitly the encoding rules) and the length of the encoded parameter.
However, according to an example embodiment, the identification of the RS discussed previously may be encoded as a TLV field included in a RNG-REQ message that is being transmitted to a base station.
A ranging response (RNG-RSP) message, for example as specified by IEEE 802.16 generally, may be transmitted by a BS in response to a received RNG-REQ message. In addition, it may be transmitted asynchronously to send corrections based on measurements that have been made on other received data or medium access control (MAC) messages. As a result, an MS/SS may be prepared to receive a RNG-RSP message at any time, not just following a RNG-REQ transmission.
An example format of an example ranging response message is shown in Table 2 below.
Example RNG-RSP message format
RNG-RSP( ) {
Management Message Type = 5
As shown, the RNG-RSP message may also include TLV fields. An example RNG-RSP message may include, for example, timing adjust information, power adjust information, a basic connection identifier (CID) for initial ranging, a subscriber station (SS) medium access control (MAC) address for initial ranging, frequency adjust information, etc.
Thus, for example, when a MS/SS or RS conducts initial ranging, it may send an initial ranging request (RNG-REQ) message. According to an example embodiment, when a RS receives a RNG-REQ without an attached-RS-ID TLV field, the RS may stamp its signature, for example, by including its associated RS-ID in an attached-RS-ID TLV field and inserting the attached-RS-ID TLV field into the RNG-REQ message. It may then forward the modified RNG-REQ message to the next hop.
When a RS receives a RNG-REQ message with an attached-RS-ID TLV field, it may simply forward the RNG-REQ message to the next hop. When a MMR-BS receives a RNG-REQ message without an attached-RS-ID TLV field from a MS/SS or RS (RSi), the MMR-BS may determine that the MS/SS or RSi sending the RNG-REQ message is directly attaching to the MMR-BS itself and is only one hop away. The MMR-BS may then update its network topology information to indicate that the attaching MS/SS or RS (RSi) is directly attached to the MMR-BS. Thus, a communication between the MMR-BS and the attaching MS/SS or RS (RSi) may be established and information relating to the communication path may be included as part of updating the network topology information.
According to an example embodiment, when a MMR-BS receives a RNG-REQ message with an attached-RS-ID field from a MS/SS or RS (RSi), the MMR-BS may retrieve the RS-ID included in the attached-RS-ID TLV field and determine that the MS/SS or RS (RSi) sending the RNG-REQ message is attaching to the system by directly coupling with the RS (RSk) identified by the RS-ID. Since the MMR-BS may have already determined a communication path between RSk and itself using the same mechanism as discussed previously, the MMR-BS may determine the topology and/or a route or communication path between the MS/SS or RSi and the MMR-BS, for example, by combining the already-determined MMR-BS-to-RSk path with the single hop path between RSk and the MS/SS or RSi. The MMR-BS may thus update its network topology information in accordance with the updated communication path.
According to an example embodiment, operations of updating network topology information may also be performed locally by each RSi along the route or communication path as the RNG-REQ message is received and forwarded by the respective RSi at each hop of the route or communication path from the attaching MS/SS or RSi to the MMR-BS. Thus, according to an example embodiment, each RSi may also maintain network topology information associated with traffic flowing through the respective RSi.
According to an example embodiment, TLV fields may only be included in RNG-REQ message of adequate UL bandwidth. Thus, for example, according to MMR specifications, when a MS/SS or RS (RSi) transmits an initial ranging request (RNG-REQ) message, the BS may provide for extra UL bandwidth allocation of size at least sufficient for the RS (RSj) to which the MS/SS or RSi is directly attaching to insert an attached-RS-ID TLV field into the RNG-REQ message.
According to an example embodiment, an attached-RS-ID may be added to the RNG-REQ message by the first RS (RSj) to which a MS/SS or a RS (RSi) directly attaches when the MS/SS or the RS (RSi) is attempting to perform initial entry, re-entry, association or handover to the network via a RS (RSj).
FIG. 6 is a flow chart illustrating operation of a wireless node according to an example embodiment. At 610, a first message may be received at a first network station in a wireless network. According to an example embodiment, the first message may, for example, include a ranging request message (610). For example, as discussed previously, RSn−1 510 may receive a RNG-REQ message that may have been sent from RSn 512 of FIG. 5 a. At 620, it may be determined whether the received first message includes an identifier of a second network station indicating an attachment of a network node to the second network station. For example, RSn−1 510 may determine whether a RNG-REQ message that has been received by RSn−1 510 includes, for example, a RS-ID, for example, in the format of a TLV field included in the RNG-REQ message. For example, the received first message may include any other type of message that may include any type of identifier of the second network station, and is not limited to RNG-REQ messages, nor is it limited to IEEE 802.16 type messages. For example, RSn−1 510 may determine whether a RNG-REQ message that has been received by RSn−1 510 includes, for example, a RS-ID, for example, a RS-ID associated with RSn 512.
At 630, the received first message may be modified to include an identifier of the first network station indicating an attachment of the network node to the first network station if it is determined that the received message does not include the identifier of the second network station. For example, if RSn−1 510 determines that a received RNG-REQ message does not include a RS-ID, then the RNG-REQ message may be modified to include a RS-ID, for example, an identifier associated with RSn−1 510. Thus the modified RNG-REQ message may serve to indicate, for example, that RSn 512 is attaching to RSn−1 510.
According to an example embodiment, the received first message may be modified, for example, to include a type/length/value (TLV) field that includes the identifier of the first network station indicating the attachment of the network node to the first network station if it is determined that the received first message does not include an identifier of a second network station (632). At 640, the received first message may be forwarded to a third network station. This, for example, RSn−1 510 may forward the received first message. If RSn−1 510 has not modified the received first message, then RSn−1 510 may forward the first message in the same status as it was received by RSn−1 510. However, if RSn−1 510 has modified the received first message, then RSn−1 510 may forward the first message in its modified form.
As discussed previously, the received first message may then be received and forwarded, for example, by all other RSs on a communication path from RSn−1 510 to MMR-BS 504 (e.g., RS2 508, RS1 506). As discussed previously, MMR-BS 504 may receive the received first message and may update the network topology information based on the received first message. According to an example embodiment, all RSi along the communication path may update local network topology information based on the received first message as the received first message is received and forwarded by each respective RSi along the communication path or route.
Alternatively, according to another example embodiment, upon receiving a RNG-REQ message from a new MS/SS or RS (RSi), an RS, e.g., RSj may forward the RNG-REQ message to the next hop, and may send a topology update request (Topology-Update-REQ) message to an MMR-BS to inform the MMR-BS that a new MS/SS or RS (RSi) is attaching to the system via RSj. The MMR-BS may update the network topology information or structure based on such information, as well as on the information it receives before receiving the Topology-Update-REQ message.
According to an example embodiment, the Topology-Update-REQ message may be formatted, for example, in accordance with the example format as shown in Table 3 below. The MMR-BS may then, for example, send a Topology-Update-RSP message to RSj. According to an example embodiment, the Topology-Update-RSP message may be formatted, for example, in accordance with the example format as shown in Table 4 below.
Thus, according to an example embodiment, when a relay station, e.g., RS1 506 attaches directly to a MMR-BS, e.g., MMR-BS 504, the MMR-BS 504 may record the path to RS1 506 as a direct link. When another relay station, e.g., RS2 508 acting as a MS/SS attaches to the system via RS1 506, e.g., by sending a RNG-REQ message, RS1 506 may send a topology update request (Topology-Update-REQ) message to the MMR-BS 504 to inform the MMR-BS 504 that RS2 508 attaches to the system via RS1 506. Since the MMR-BS 504 may have already determined the topology between MMR-BS 504 and RS1 506 during a RS1 506 initial ranging process, the MMR-BS 504 may determine a topology between RS2 508 and itself.
Continuing in this manner, according to an example embodiment, when a MS/SS or RS attaches to the system, e.g., via a direct coupling with RSn, the MS/SS or RS may send its initial RNG-REQ message. Upon receiving the RNG-REQ message, RSn may send a Topology-Update-REQ message to the MMR-BS to inform the MMR-BS that the MS/SS or RS attaches to the system via RSn (e.g., via a direct coupling with RSn). Since the MMR-BS may have already determined the topology between the MMR-BS and RSn during a RSn initial ranging process, the MMR-BS may determine the topology between the MS/SS or RS and itself.
FIG. 7 is a flow chart illustrating operation of a wireless node according to an example embodiment. At 710, a first message may be received at a first network station in a wireless network. According to an example embodiment, the first message may include, for example, a ranging request message (712). At 720, it may be determined whether the received first message indicates that a network node is attaching to the first network station. At 730, the received first message may be forwarded to a second network station.
At 740, a second message may be sent to the second network station, the second message including an indication that the network node is directly attached to the first network station if it is determined that the received first message indicates that the network node is attaching to the first network station. According to an example embodiment, the second message, for example, may include a topology update request message (742).
According to an example embodiment, one or more relay stations may receive the second message and determine the topology and/or a communication path between the base station and the network node that includes the network node based on the second message (750).
Similarly, according to an example embodiment, when a directly attached MS/SS or RS (RSi) detaches, for example, terminates an attachment, from a RS (RSj), for example, due to events such as mobility, the RS (RSj) may send a topology update request (Topology-Update-REQ) message to the MMR-BS to inform the MMR-BS that the MS/SS or RS (RSi) is detaching from the system via RSj. Thus, the RS (RSj) may send a Topology-Update-REQ message to the MMR-BS to inform the MMR-BS of the topology change in accordance with the example format as shown in Table 3. Upon receiving the message, the MMR-BS may update the network topology accordingly.
Example Topology-Update-REQ message format
Topology-Update-REQ( ) {
16 bits TLV Encoded Information
An example Topology-Update-REQ message may include an MS/SS or RS ID TLV field and/or an Update Type (attach or detach) TLV field.
Upon receiving a Topology-Update-REQ message from a RS, the MMR-BS may update the network topology accordingly and may reply, for example, with a topology update response (Topology-Update-RSP) message, for example, in accordance with the example format shown in Table 4.
Example Topology-Update-RSP message format
Topology-Update-RSP( ) {
16 bits Confirmation Code
FIG. 8 is a flow chart illustrating operation of a wireless node according to an example embodiment. At 810, it may be determined that a network node is detaching from a first network station in a wireless network. At 820, a request may be sent to a second network station, the request including an indication that the network node is detaching from the first network station. According to an example embodiment, the request may include a topology update request message (822).
According to an example embodiment, a base station may receive the request and determine a network topology based on the request (830).
Based on the network topology information obtained from the topology discovery techniques as discussed herein, a MMR-BS, for example, may determine a centralized calculation of a route or communication path between the MMR-BS and any communicating MS/SSs for both an uplink and a downlink direction. Whenever the network topology is updated, for example, due to events such as mobility, the MMR-BS may recalculate the routes or communication paths and may generate new communication paths and/or delete invalid communication paths.
According to an example embodiment, a new RS, acting as a MS/SS, for example, a RS newly attaching to the system, may send an initial RNG-REQ message to all the RSs and/or BS to which it is attaching. For example, RS3 534 may attach to the system shown in FIG. 5 b via a direct coupling with RS1 530 and a direct coupling with RS2 532. The RSs to which the new RS attaches may stamp their own signature to the corresponding RNG-REQ message that they receive from the new RS and they may then forward the respective modified RNG-REQ message to the next hop.
When MMR-BS, e.g., MMR-BS 504 of FIG. 5 b receives multiple initial RNG-REQ messages from a RS, e.g., RS3 534, but with different RS signatures, the MMR-BS 504 may determine that the RS3 534 attaches to the system via more than one RS, and thus that multiple paths exist between the RS3 534 and the MMR-BS 504.
According to an example embodiment, when a new path is determined after an initial topology discovery or topology update, a MMR-BS may, for example, send the complete path information to all the RSs on one particular path. According to an example embodiment, the MMR-BS may first establish a multicast group and may invite all the RSs on a path to join the multicast group. The MMR-BS may assign a new multicast address for the multicast group. The MMR-BS may then use the multicast address to send all the management messages that are needed by the RSs that are included on the path. For example, the MMR-BS 504 of FIG. 5 a may determine a multicast group including RS1 506, RS2 508, . . . RSn−1 510, RSn 512 along a communication path between MMR-BS 504 and MS/SS 516.
The MMR-BS may then, for example, send to the multicast group a path advertisement indication or a path advertisement request (Path-Advertisement-REQ) message that may include the complete path information (e.g., indicators associated with the MMR-BS 504, RS1 506, RS2 508, . . . RSn 512, MS/SS 516) and a path identifier. Thus, for example, the path advertisement indication or a path advertisement request may be sent as a multicast message addressed to a multicast group address that includes the addresses (e.g., MAC addresses) of all the RSs in the path between the MS/SS and the MMR-BS as multicast group members. When a RS receives the multicast message, for example, every RS in the path (who is a member of the multicast group) may then route the multicast message to the other RSs on the path based on a defined multicast tree, for example. All members of the multicast group may, for example, share a group authentication key.
After receiving the Path-Advertisement-REQ message, the RSs in the multicast group may store the path information, for example, in a local storage device, and may reply, for example, via a path advertisement response (Path-Advertisement-RSP) message, for example, in accordance with an example format as shown below in Table 6.
According to an example embodiment, the MMR-BS may send the path advertisement indication or a path advertisement request message via a unicast message to each RS included in the particular path. Thus, for example, the path advertisement indication or path advertisement request message may be sent as a unicast message sent to each of the one or more relay stations on the path between the MS/SS and the MMR-BS. With this unicast scheme, however, overhead may increase as the number of RSs on a path increases since a separate message is sent to each RS.
According to an example embodiment, the MMR-BS may send the path advertisement indication or a path advertisement request message via a unicast message to the last RS included in the particular path. Thus, for example, the path advertisement indication or path advertisement request message may be sent as a Z-unicast message addressed to the RS directly attached to the MS/SS. In this example, the message may be sent by the MMR-BS to the RS that is most directly attached to the MS, allowing the message to be received and read by each RS along the path. This may provide a more efficient technique by transmitting one message that is used or read by all RSs along the path. When the message reaches each RS on the path, each RS may retrieve parameters from the message, for example, parameters associated with the communication path.
Thus, according to an example embodiment, an MMR-BS may send a Path-Advertisement-REQ message when it intends to advertise the complete path information to all the RSs included in a communication path. An MMR-BS may, for example, generate Path-Advertisement-REQ messages in accordance with the example format as shown in Table 5.
Example Path-Advertisement-REQ message format
Path-Advertisement-REQ( ) {
The Path-Advertisement-REQ message may include, for example, TLV fields indicating a path identifier (Path-ID) and/or Path-Information. The Path-Information may, for example, include identifiers associated with each network node included in the communication path to be advertised.
Upon receiving a Path-Advertisement-REQ message from the MMR-BS, a RS may reply via a path advertisement response (Path-Advertisement-RSP) message, for example, in accordance with the example format as shown in Table 6.
Example Path-Advertisement-RSP message format
Path-Advertisement-RSP( ) {
An MMR-BS may send a path cancellation request (Path-Cancellation-REQ) message when it intends to cancel a path and to inform the RSs on path of the cancellation decision as well. According to an example embodiment, if a MMR-BS makes a decision to cancel an existing path, it may send to an associated multicast group a path cancellation request (Path-Cancellation-REQ) message which may include, for example, a path identifier (Path-ID) TLV field. An example of a format for a Path-Cancellation-REQ message is shown in Table 7 below.
Example Path-Cancellation-REQ message format
Path-Cancellation-REQ( ) {
A Path-Cancellation-REQ message may include, for example, one or more path identifier (Path-ID) TLV fields.
The RSs that receive the Path-Cancellation-REQ message may then remove the associated record for the path specified by the Path-ID and may, for example, reply via a path cancellation response (Path-Cancellation-RSP message). Thus, upon receiving a Path-Cancellation-REQ message from the MMR-BS, a RS may remove its stored indication of the identified path, for example, a record for the identified path, and may reply, for example, via a Path-Cancellation-RSP message, for example, in accordance with the example format as shown in Table 8.
Example Path-Cancellation-RSP message format
Path-Cancellation-RSP( ) {
According to an example embodiment, a MMR-BS may maintain information indicating all the possible paths between a MS/SS and the MMR-BS. Thus, when a new connection is established for an MS/SS, the MMR-BS may select one or more communication paths to carry the traffic for the new connection.
According to an example embodiment, when multiple routes or communication paths exist between a MMR-BS and a MS/SS, the MMR-BS may select a particular path, e.g., based on network parameters or metrics that may include but are not limited to link condition, load condition, overall delay, etc.
According to an example embodiment, to inform all the RSs on the selected paths of the traffic information, the MMR-BS may send a path selection indication or path selection request (Path-Selection-REQ) message to a multicast group to which all the RSs on the selected path belong (e.g., a Path-Selection-REQ message in accordance with an example format as shown below in Table 9). The Path-Selection-REQ message may include, for example, a connection identifier (CID) of the connection, a path identifier (path-id), and optionally a service flow indicator (SFID) and/or a quality of service (QoS) requirement associated with the service flow.
According to an example embodiment, as used in the context of IEEE 802.16 systems, a connection identifier, (CID) may identify a connection to equivalent peers in the medium access control (MAC) layer of a BS and SS. The CID may map to a service flow indicator (SFID), which may define the QoS parameters of the service flow associated with that connection.
According to an example embodiment, when a RS on the path receives the Path-Selection-REQ message, it may record the information, which may be used by the RS to route traffic based on a path that may be specified, for example, in accordance with an example path advertisement technique. If the SFID and the QoS requirement are also present, the RS may also record such information that may be used for scheduling. Each RS that receives the Path-Selection-REQ message may then reply, for example, via a path selection confirmation or path selection response (Path-Selection-RSP) message, e.g., a Path-Selection-RSP message in accordance with an example format as shown below in Table 10, to the MMR-BS.
According to an example embodiment, the MMR-BS may select one or more paths for a particular connection. According to an example embodiment, the MMR-BS may select asymmetric paths for uplink and downlink traffic.
After selecting one or more paths to carry the traffic for a new connection, a MMR-BS may send a Path-Selection-REQ message, for example, in accordance with the example format as shown below in Table 9, to a multicast group to which all the RSs on the selected path belong.
Example Path-Selection-REQ message format
Path-Selection-REQ( ) {
A Path-Selection-REQ message may, for example, include one or more path identifier (Path-ID) and/or connection identifier (CID) TLV fields. Further, a Path-Selection-REQ message may, for example, include one or more service flow parameter TLV fields.
Upon receiving a Path-Selection-REQ message from the MMR-BS, a RS may retrieve and record the relevant information and may reply, for example, via a path selection response (Path-Selection-RSP) message, for example, in accordance with the example format as shown in Table 10.
Example Path-Selection-RSP message format
Path-Selection-RSP( ) {
According to an example embodiment, if a single new RS, e.g., RS3 534 of FIG. 5 b attempts to attach to an MMR system via multiple paths (e.g., via one or more paths), the new RS may generate a RNG-REQ message or RNG-REQ messages that includes the RS-ID(s) associated with any network stations to which the new RS wishes to attach. Thus, there is no need for any intermediate node between the new RS and the base station to modify the RNG-REQ message.
For example, if RS3 534 of FIG. 5 b attempts to attach to the system of FIG. 5 b, e.g., by directly coupling with RS1 530 and RS2 532, the new RS, e.g., RS3 534 may itself generate a RNG-REQ message or RNG-REQ messages that include the RS-ID(s) associated with any network stations to which the new RS wishes to attach. For example, the RS3 534 may generate RNG-REQ messages that include the RS-IDs of RS1 530 and RS2 532 if RS3 534 wishes to attach to both RS1 530 and RS2 532 and then send the RNG-REQ message(s).
According to an example embodiment, the RS3 534 may send RNG-REQ messages that do not include the RS-IDs of RS1 530 and RS2 532, but may instead, e.g., send a second message, e.g. a topology update message associated with each of RS1 530 and RS2 532, to indicate to MMR-BS 504 that RS3 534 is attaching to both RS1 530 and RS2 532.
If multiple communication paths are available between the MMR-BS 504 and a MS/SS and/or any intermediate RSs, the MMR-BS 504 may select an appropriate communication path (or appropriate communication paths) for communicating with any of the MS/SS and/or any intermediate RSs, e.g., based on the selection techniques discussed previously.
As another example, if RSn 512 of FIG. 5 a wishes to attach to RSn−1 512, the RSn 512 may generate a RNG-REQ message that includes a RS-ID of RSn−1 512 and then send the RNG-REQ message.
According to an example embodiment, the RSn 512 may send a RNG-REQ message that does not include the RS-ID of RSn−1 512, but may instead, e.g., send a second message, e.g. a topology update message associated with RSn−1 512, to indicate to MMR-BS 504 that RSn 512 is attaching to RSn−1 512.
FIG. 9 is a flow chart illustrating operation of a wireless node according to an example embodiment. At 910, a message may be generated, at a first network station in a wireless network, the message including one or more identifiers of one or more other network stations indicating that the first network station is attaching to the one or more other network stations. For example, as discussed previously, RSn 512 of FIG. 5 a may wish to attach, e.g., to RSn−1 520, and may thus send, e.g., a ranging request message including a RS-ID associated with RSn−1 520, or RSn 512 may send, e.g., a topology update request message including a RS-ID associated with RSn−1 520.
For example, as discussed previously, RS3 534 of FIG. 5 b may wish to attach to at least RS1 530 and RS2 532, and thus RS3 534 may, e.g., send a ranging request message including RS-IDs associated with both of RS1 530 and RS2 532. Alternatively, RS3 534 of FIG. 5 b may send a ranging request message to each of RS1 530 and RS2 532, each ranging request message including an RS-ID associated with a respective one of RS1 530 and RS2 532.
For example, as discussed previously, if RS3 534 of FIG. 5 b attempts to attach to the system of FIG. 5 b, e.g., by directly coupling with RS1 530 and RS2 532, then RS3 534 may itself generate a RNG-REQ message or RNG-REQ messages that include the RS-ID(s) associated with any network stations to which the new RS wishes to attach. For example, the RS3 534 may generate RNG-REQ messages that include the RS-IDs of RS1 530 and RS2 532 if RS3 534 wishes to attach to both RS1 530 and RS2 532 and then send the RNG-REQ message(s).
According to an example embodiment, the RS3 534 may instead, e.g., send, e.g. a topology update message associated with each of RS1 530 and RS2 532, to indicate to MMR-BS 504 that RS3 534 is attaching to both RS1 530 and RS2 532.
At 920, the message may be sent to the one or more other network stations. According to an example embodiment, the message may include a ranging request message (922).
According to an example embodiment, a base station may receive the message and determine a network topology based on the message (930).
FIG. 10 is a flow chart illustrating operation of a wireless node according to an example embodiment. At 1010, path information associated with a current communication path may be updated to indicate an updated communication path between a base station and a network node in a wireless network. At 1020, a message indicating the updated communication path may be sent to each network node included in one or more of the current communication path or the updated communication path.
According to an example embodiment, each one of the network nodes that receives the message may update local data associated with network communication paths in a storage device associated with the each one of the network nodes based on the received message (1022). According to an example embodiment, the sending the message may include determining a multicast group including each network node included in one or more of the current communication path or the updated communication path, determining a multicast address associated with the multicast group, and sending the message based on the multicast address (1024).
FIG. 11 is a flow chart illustrating operation of a wireless node according to an example embodiment. At 1110, it may be determined that a network node in a wireless network is requesting a connection to a network station included in a first communication path between the network node and a base station. For example, it may be determined that RS3 534 of FIG. 5 b may request a connection to RS1 530, which may be included in a communication path between RS3 534 and MMR-BS 504.
At 1120, one or more other communication paths between the network node and the base station may be determined. For example, a communication path including MMR-BS 504, RS2 532, and RS3 534 may be determined. At 1130, one or more selected paths may be selected from the first communication path and the one or more other communication paths based on network parameters. For example, a path including RS1 530 may be selected, or a path including RS2 532 may be selected based on network parameters or metrics. For example, such network parameters or metrics may include but are not limited to link condition, load condition, overall delay, etc.
According to an example embodiment, the selecting may include selecting one or more selected paths from the first communication path and the one or more other communication paths based on network parameters, wherein the one or more selected paths include an uplink path and a downlink path (1132). For example, a path including RS1 530 may be selected for an uplink flow, and a path including RS2 532 may be selected for a downlink flow based on network parameters.
At 1140, a message indicating one of the selected communication paths may be sent to each network station that is included in the one of the selected communication paths. According to an example embodiment, the sending of the message may include determining a multicast group including each network node included in the one of the selected communication paths, determining a multicast address associated with the multicast group, and sending the message based on the multicast address.
FIG. 12 is a block diagram illustrating an apparatus 1200 that may be provided in a wireless node according to an example embodiment. The wireless node (e.g. station or AP) may include, for example, a wireless transceiver 1202 to transmit and receive signals, a controller 1204 to control operation of the station and execute instructions or software, and a memory 1206 to store data and/or instructions.
Controller 1204 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more the tasks or methods described above in FIGS. 1-11.
In addition, a storage medium may be provided that includes stored instructions, when executed by a controller or processor that may result in the controller 1204, or other controller or processor, performing one or more of the functions or tasks described above.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS7646752Dec 31, 2003Jan 12, 2010Nortel Networks LimitedMulti-hop wireless backhaul network and methodUS7889713Oct 13, 2006Feb 15, 2011Nokia CorporationTransmission of management messages for relay networksUS20020080736Dec 5, 2001Jun 27, 2002Nec CorporationData transmission method and apparatus in relay transmission type radio networkUS20020191573May 31, 2002Dec 19, 2002Whitehill Eric A.Embedded routing algorithms under the internet protocol routing layer of a software architecture protocol stack in a mobile Ad-Hoc networkUS20030091014Jun 4, 2002May 15, 2003Meier Robert C.Radio frequency local area networkUS20040025018Jan 23, 2003Feb 5, 2004Haas Zygmunt J.Secure end-to-end communication in mobile ad hoc networksUS20040109493Aug 20, 2003Jun 10, 2004Luca BlessentCode channel allocations in a wireless communications systemUS20040170147Mar 10, 2004Sep 2, 2004Mitsubishi Denki Kabushiki KaishaMethod and apparatus for assigning codesUS20050058151Jun 30, 2004Mar 17, 2005Chihsiang YehMethod of interference management for interference/collision avoidance and spatial reuse enhancementUS20050117539Nov 29, 2004Jun 2, 2005Samsung Electronics Co., Ltd.System and method for ranging for a fast handover in a mobile communication systemUS20050232183May 2, 2005Oct 20, 2005Sartori Philippe JMethod and apparatus for relay facilitated communicationsUS20050286547Dec 3, 2004Dec 29, 2005Baum Kevin LMethod and apparatus for accessing a wireless multi-carrier communication systemUS20060107166Sep 27, 2005May 18, 2006Sanjiv NandaEnhanced block acknowledgementUS20060176973Nov 18, 2005Aug 10, 2006Siavash AlamoutiVertical adaptive antenna array for a discrete multitone spread spectrum communications systemUS20070097915Oct 30, 2006May 3, 2007Aris PapasakellariouMethods for Dimensioning the Control Channel for Transmission Efficiency in Communication SystemsUS20070097945 *Jul 7, 2006May 3, 2007Wang Guo QMethods and systems for a wireless routing architecture and protocolUS20070110016Nov 9, 2006May 17, 2007AlcatelWireless access control method, relay station and base stationUS20080002610Oct 13, 2006Jan 3, 2008Nokia CorporationTransmission of management messages for relay networksUS20080039014Jul 16, 2007Feb 14, 2008Institute For Information IndustryWireless communication system, apparatus, and method for transmitting information to describe network topologyUS20080056193Sep 1, 2006Mar 6, 2008Nextwave Broadband Inc.Pre-allocated random access identifiersUS20080117854Oct 12, 2007May 22, 2008Nokia CorporationBandwidth allocation for relay networksEP1524800A2Aug 31, 2004Apr 20, 2005Samsung Electronics Co., Ltd.A method for processing broadcast data in a mobile ad-hoc networkEP1912390A1Jul 31, 2007Apr 16, 2008Fujitsu LimitedWireless communication systemsJP2001237875A Title not availableJPH04341031A Title not availableJPH11177622A Title not availableWO2000055640A1Mar 2, 2000Sep 21, 2000Coactive Networks IncDynamic wait acknowledge for network protocolWO2006023771A2Aug 18, 2005Mar 2, 2006Kevin L BaumMethod and apparatus for transparent relayingWO2006096728A2Mar 7, 2006Sep 14, 2006Texas Instruments IncSystem and method for rangingWO2008004062A2Jun 28, 2007Jan 10, 2008Nokia CorpTransmission of success and failure indications (ack_bitmap) in relay networksWO2008004066A2Jun 29, 2007Jan 10, 2008Nokia CorpTopology and route discovery and management for relay networksWO2008047203A2Oct 15, 2007Apr 24, 2008Nokia CorpBandwidth allocation for relay networks using cdma codes* Cited by examinerNon-Patent CitationsReference1"6.3.2.3.5 Ranging Request (RNG-REQ) message", Air Interface for Fixed Broadband Wireless Access Systems, IEEE Std 802.16-2004 (Oct. 1, 2004), p. 49.2"Air Interface for Fixed Broadband Wireless Access Systems", IEEE Standard 802.16-2004, (Oct. 1, 2004), pp. 42-44.3English Translation of Office Action for Israeli Application Serial No. 195928, mailed Feb. 24, 2010, 2 pages.4Final Office Action for U.S. Appl. No. 11/549,387, mailed on Aug. 5, 2010, 7 pages.5Final Office Action for U.S. Appl. No. 11/871,649, mailed Jun. 7, 2011, 17 pages.6Johnson, D. B., "Dynamic Source Routing in Ad Hoc Wireless Networks", Carnegie Mellon University, (1995), pp. 1-18.7Marks, R et al., "IEEE Standard 802.16: A Technical Overview of the WirelessMAN Air Interface for Broadband Wireless Access", Retrieved from: www.ieee802.org/16/docs/02/C80216-02-05.pdf,(Jun. 4, 2002),98/107.8Marks, R et al., "IEEE Standard 802.16: A Technical Overview of the WirelessMAN Air Interface for Broadband Wireless Access", Retrieved from: www.ieee802.org/16/docs/02/C80216-02�05.pdf,(Jun. 4, 2002),98/107.9Non-Final Office Action for U.S. Appl. No. 11/871,649, mailed on Oct. 19, 2010, 24 pages.10Non-Final Office Action Response for U.S. Appl. No. 11/871,649, filed Mar. 30, 2011, 22 pages.11Notice of Allowance for Korean Patent Application Serial No. 2008-7031888, mailed on Aug. 10, 2011, 3 pages.12Notice of Allowance for U.S. Appl. No. 11/549,387, mailed Oct. 19, 2010, 14 pages.13Office Action for Chinese Application No. 200780024815.1 (with English Translation), mailed Apr. 26, 2011, 19 pages.14Office Action for Chinese Application No. 200780024974.1 (with English Translation), mailed Apr. 20, 2011, 9 pages.15Office Action for Indonesian Application No. WO0200804069 (with English Translation), mailed Apr. 27, 2011, 4 pages.16Office Action for Indonesian Application No. WO0200804127 (with English Translation), mailed Feb. 17, 2011, 6 pages.17Office Action for JP Application No. 2009-517470 (with English Translation), mailed Jun. 13, 2011, 16 pages.18Office Action for JP Application No. 2009-517471 (with English Translation), mailed Jun. 13, 2011, 9 pages.19Office Action for Korean Application No. 2008-7031882 (with English Translation), mailed on Dec. 24, 2010, 4 pages.20Office Action for KR Application No. 2008-7031888 (with English Translation), mailed Apr. 20, 2011, 4 pages.21Office Action for Russian Patent Application No. 2009117689 (with English Translation), mailed on Aug. 13, 2010,12 pages.22Pabst, R. "Realy-Based Deployment Concepts for Wireless and Mobile Broadband Radio", IEEE Communications Magazine, (Sep. 2004),pp. 80-88.23Pabst, R. "Realy�Based Deployment Concepts for Wireless and Mobile Broadband Radio", IEEE Communications Magazine, (Sep. 2004),pp. 80-88.24Saifullah, Y. et al., "Clarification on CDMA Codes TLV", IEEE 802.16 Broadband Wireless Access Working Group, (Jul. 13, 2007),16j-07/402r3, pp. 3.25Saifullah, Y. et al., "Resource Request for Bandwidth", IEEE 802.16 Broadband Wireless Access Working Group, (Jan. 18, 2007),16j-07/039r3, pp. 9.26Saifullah, Y. et al., "Resource Request for Bandwidth", IEEE 802.16 Presentation Submission Template (Rev 8.3), (Nov. 15, 2006),16j-06/189 ,pp. 5.27Shen, et al, "Recommendations on IEEE 802.16j", IEEE 802.16j-06/004r1, Rev. 8.3, May 8, 2006, 15 pages.28Wiemann, et al, "A Novel Multi-Hop ARQ Concept", Vehicular Technology Conference, vol. 5, Jun. 1, 2005, 5 pages.29Wiemann, H et al., "A Novel Multi-Hop ARQ Concept", Vehicular Technology Conference, VTC 2005-Spring. 2005 IEEE 6th, 3097-3101 (Jun. 2005).30Zheng, H et al., "HARQ with Relays", IEEE C802.16j-06/197r1, Retrieved from: www.ieee802.org/16/relay/index.html, whole document,(Nov. 7, 2006).31Zheng, H et al., "Transmission Scheme of MAC Management Message towards a RS Group in multi-hop relay System", IEEE 0802.16j-07-033, Retrieved from: www.ieee802.org/16/relay/index.html,(Jan. 8, 2007),section 1-2,4.32Zheng, H et al., "Transmission Scheme of MAC Management Message towards a RS Group in multi-hop relay System", IEEE 0802.16j-07�033, Retrieved from: www.ieee802.org/16/relay/index.html,(Jan. 8, 2007),section 1-2,4.Referenced byCiting PatentFiling datePublication dateApplicantTitleUS8498233 *Apr 22, 2008Jul 30, 2013Thomson LicensingMethod and apparatus for multicast tree management in multi-hop relay communication systemUS20100202322 *Dec 12, 2007Aug 12, 2010Sean CaiMethod for Terminating Connection to Wireless Relay StationUS20110051651 *Apr 22, 2008Mar 3, 2011Thomson LicensingMethod and apparatus for multicast tree management in multi-hop relay communication systemUS20120051231 *Aug 31, 2010Mar 1, 2012Cisco Technology, Inc.Enhancing mtrace to detect failure in multicast diverse paths* Cited by examinerClassifications U.S. Classification455/446, 370/315, 455/11.1, 370/432, 370/390, 370/328International ClassificationH04W40/22, H04W84/22, H04W16/26, H04W60/04Cooperative ClassificationH04W60/04, H04W40/24, H04B7/2606, H04W84/22, H04L45/26, H04W16/26, H04W40/22, H04W84/047European ClassificationH04W60/04, H04L45/26Legal EventsDateCodeEventDescriptionOct 4, 2006ASAssignmentOwner name: NOKIA CORPORATION, FINLANDFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ZHENG, HAIHONG;REEL/FRAME:018364/0550Effective date: 20060817RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google