US20100260109A1

US20100260109A1 - Optimized inter-access point packet routing for ip relay nodes

Info

Publication number: US20100260109A1
Application number: US12/756,287
Authority: US
Inventors: Fatih Ulupinar; Yongsheng Shi; Gavin Bernard Horn; Parag Arun Agashe; Xiaolong Huang
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2009-04-10
Filing date: 2010-04-08
Publication date: 2010-10-14
Also published as: KR20120022915A; TW201130264A; KR101402143B1; EP2417795A1; WO2010118426A3; US20100260129A1; TW201129140A; EP2417736B1; CN102388578B; WO2010118431A1; US9160566B2; TW201130336A; CN102388578A; JP2014132757A; KR20110138278A; US20100260098A1; CN102388648A; EP2417736A2; WO2010118428A1; WO2010118426A2

Abstract

Systems and methodologies are described that facilitate communicating inter-eNB packets among eNBs in a cluster implemented by a donor eNB. A relay eNB can report an address received from a gateway upstream to one or more eNBs. The one or more eNBs can store the address along with one or more parameters for communicating with the relay eNB. In this regard, disparate eNBs can communicate with the relay eNB by specifying the address in an inter-eNB packet, and upstream eNBs can route the inter-eNB packet to the relay eNB based at least in part on locating the address in a routing table. In this regard, the inter-eNB packets need not pass through the gateway to reach the relay eNB.

Description

CLAIM OF PRIORITY UNDER 35 U.S.C. §119

The present application for patent claims priority to Provisional Application No. 61/168,522 entitled “RELAY NODE PROCESSING FOR LONG TERM EVOLUTION SYSTEMS” filed Apr. 10, 2009, and assigned to the assignee hereof and hereby expressly incorporated by reference herein.

BACKGROUND

1. Field
The following description relates generally to wireless communications, and more particularly to routing data packets among multiple access points.
2. Background
Wireless communication systems are widely deployed to provide various types of communication content such as, for example, voice, data, and so on. Typical wireless communication systems may be multiple-access systems capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, . . . ). Examples of such multiple-access systems may include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and the like. Additionally, the systems can conform to specifications such as third generation partnership project (3GPP), 3GPP long term evolution (LTE), ultra mobile broadband (UMB), and/or multi-carrier wireless specifications such as evolution data optimized (EV-DO), one or more revisions thereof, etc.
Generally, wireless multiple-access communication systems may simultaneously support communication for multiple mobile devices. Each mobile device may communicate with one or more access points (e.g., base stations) via transmissions on forward and reverse links. The forward link (or downlink) refers to the communication link from access points to mobile devices, and the reverse link (or uplink) refers to the communication link from mobile devices to access points. Further, communications between mobile devices and access points may be established via single-input single-output (SISO) systems, multiple-input single-output (MISO) systems, multiple-input multiple-output (MIMO) systems, and so forth. Access points, however, can be limited in geographic coverage area as well as resources such that mobile devices near edges of coverage and/or devices in areas of high traffic can experience degraded quality of communications from an access point.
Relay nodes can be provided to expand network capacity and coverage area by facilitating communication between mobile devices and access points. For example, a relay node can establish a backhaul link with a donor access point, which can provide access to a number of relay nodes, and the relay node can establish an access link with one or more mobile devices or additional relay nodes. To mitigate modification to backend core network components, communication interfaces with the backend network components, such as S1-U, can terminate at the donor access point. Thus, the donor access point appears as a normal access point to backend network components. To this end, the donor access point can route packets from the backend network components to the relay nodes for communicating to the mobile devices.

SUMMARY

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
In accordance with one or more aspects and corresponding disclosure thereof, various aspects are described in connection with facilitating routing packets between one or more relay nodes and/or donor access points in an internet protocol (IP) relay configuration. For example, when a relay node receives an IP address related to communicating in a wireless network, the address can be propagated to one or more disparate relay nodes or the donor access point in a related cluster. In this regard, for example, packets can be communicated with the relay node from the one or more disparate relay nodes or the donor access point without requiring communicating the packet to network components further upstream than the donor access point (e.g., to one or more gateway nodes, mobility management entities, and/or the like).
According to related aspects, a method is provided that includes transmitting a plurality of packets to an upstream evolved Node B (eNB) for communicating with a wireless network and specifying an address received from a gateway for communicating with the gateway in a portion of the plurality of packets. The method further includes specifying a disparate address for communicating with a disparate eNB in a disparate portion of the plurality of packets.
Another aspect relates to a wireless communications apparatus. The wireless communications apparatus can include at least one processor configured to communicate a plurality of packets to an upstream eNB for providing to one or more components of a wireless network and indicate an address assigned by a gateway for communicating with the gateway in a portion of the plurality of packets. The at least one processor is further configured to specify a disparate address for communicating with a disparate eNB in a disparate portion of the plurality of packets. The wireless communications apparatus also comprises a memory coupled to the at least one processor.
Yet another aspect relates to an apparatus. The apparatus includes means for communicating with an upstream eNB to access a gateway in a wireless network based at least in part on an address received from the gateway. The apparatus also includes means for indicating a disparate address in one or more inter-eNB packets for communicating to a relay eNB, wherein the means for communicating with the upstream eNB communicates the one or more inter-eNB packets to the upstream eNB.
Still another aspect relates to a computer program product, which can have a computer-readable medium including code for causing at least one computer to communicate a plurality of packets to an upstream eNB for providing to one or more components of a wireless network and code for causing the at least one computer to indicate an address assigned by a gateway for communicating with the gateway in a portion of the plurality of packets. The computer-readable medium can also comprise code for causing the at least one computer to specify a disparate address for communicating with a disparate eNB in a disparate portion of the plurality of packets.
Moreover, an additional aspect relates to an apparatus including a communicating component that transmits one or more packets to an upstream eNB for providing to a gateway in a wireless network based at least in part on an address received from the gateway. The apparatus can further include an address assigning component that specifies a disparate address in one or more inter-eNB packets for communicating to a relay eNB, wherein the communicating component transmits the one or more inter-eNB packets to the upstream eNB.
According to another aspect, a method is provided that includes receiving an address related to a packet obtained from a downstream relay eNB and locating the address in a routing table of addresses related to one or more relay eNBs in a cluster. The method further includes transmitting the packet to a disparate relay eNB in the cluster based at least in part on the locating the address in the routing table.
Another aspect relates to a wireless communications apparatus. The wireless communications apparatus can include at least one processor configured to determine an address related to a packet received from a downstream relay eNB and discern the address is in a routing table comprising one or more address corresponding to one or more relay eNBs in a cluster. The at least one processor is further configured to communicate the packet to a disparate relay eNB in the cluster based at least in part on discerning the address is in the routing table. The wireless communications apparatus also comprises a memory coupled to the at least one processor.
Yet another aspect relates to an apparatus. The apparatus includes means for receiving an address related to a packet obtained from a downstream relay eNB and means for locating the address in a routing table of addresses related to one or more relay eNBs in a cluster. The apparatus also includes means for transmitting the packet to a disparate relay eNB in the cluster based at least in part on locating the address in the routing table.
Still another aspect relates to a computer program product, which can have a computer-readable medium including code for causing at least one computer to determine an address related to a packet received from a downstream relay eNB and code for causing the at least one computer to discern the address is in a routing table comprising one or more address corresponding to one or more relay eNBs in a cluster. The computer-readable medium can also comprise code for causing the at least one computer to communicate the packet to a disparate relay eNB in the cluster based at least in part on discerning the address is in the routing table.
Moreover, an additional aspect relates to an apparatus including a routing parameter receiving component that obtains an address related to a packet obtained from a downstream relay eNB and a routing table component that locates the address in a routing table of addresses related to one or more relay eNBs in a cluster. The apparatus can further include a communicating component that transmits the packet to a disparate relay eNB in the cluster based at least in part on locating the address in the routing table.
To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed and this description is intended to include all such aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an illustration of an example wireless communications system that facilitates providing relays for wireless networks.

FIG. 2 is an illustration of an example communications apparatus for employment within a wireless communications environment.

FIG. 3 is an illustration of an example wireless communications system that communicates a transport address to an upstream evolved Node B (eNB) for receiving inter-eNB packets.

FIG. 4 is an illustration of an example wireless communications system that generates inter-eNB packets for communicating to one or more eNBs.

FIG. 5 is an illustration of an example wireless communications system that tunnels inter-eNB packets over resources requested from a donor eNB.

FIG. 6 is an illustration of an example wireless communications system for attaching a relay eNB to a wireless network.

FIG. 7 is an illustration of an example wireless communications system that establishes tunneling for communicating inter-eNB packets related to handover.

FIG. 8 is an illustration of an example wireless communications system that tunnels inter-eNB packets related to handover.

FIG. 9 is an illustration of an example wireless communications system that utilizes internet protocol (IP) relays to provide access to a wireless network.

FIG. 10 is an illustration of an example methodology for communicating inter-eNB packets to an upstream eNB for providing to a relay eNB.

FIG. 11 is an illustration of an example methodology that transmits received inter-eNB packets to a relay eNB.

FIG. 12 is an illustration of an example methodology that tunnels inter-eNB packets to a relay eNB based on a received tunnel endpoint identifier (TEID).

FIG. 13 is an illustration of an example methodology that facilitates tunneling packets to a relay eNB based on a TEID over a bearer associated with the TEID.

FIG. 14 is an illustration of an example methodology that provides a TEID and bearer identifier for tunneling inter-eNB packets.

FIG. 15 is an illustration of a wireless communication system in accordance with various aspects set forth herein.

FIG. 16 is an illustration of an example wireless network environment that can be employed in conjunction with the various systems and methods described herein.

FIG. 17 is an illustration of an example system that communicates inter-eNB packets to an upstream eNB for providing to a relay eNB.

FIG. 18 is an illustration of an example system that transmits received inter-eNB packets to a relay eNB.

DETAILED DESCRIPTION

Various aspects are now described with reference to the drawings. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. It may be evident, however, that such aspect(s) may be practiced without these specific details.
As used in this application, the terms “component,” “module,” “system” and the like are intended to include a computer-related entity, such as but not limited to hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets, such as data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal.
Furthermore, various aspects are described herein in connection with a terminal, which can be a wired terminal or a wireless terminal A terminal can also be called a system, device, subscriber unit, subscriber station, mobile station, mobile, mobile device, remote station, remote terminal, access terminal, user terminal, terminal, communication device, user agent, user device, or user equipment (UE). A wireless terminal may be a cellular telephone, a satellite phone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device having wireless connection capability, a computing device, or other processing devices connected to a wireless modem. Moreover, various aspects are described herein in connection with a base station. A base station may be utilized for communicating with wireless terminal(s) and may also be referred to as an access point, a Node B, evolved Node B (eNB), or some other terminology.
Moreover, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise, or clear from the context, the phrase “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, the phrase “X employs A or B” is satisfied by any of the following instances: X employs A; X employs B; or X employs both A and B. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from the context to be directed to a singular form.
The techniques described herein may be used for various wireless communication systems such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other systems. The terms “system” and “network” are often used interchangeably. A CDMA system may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband-CDMA (W-CDMA) and other variants of CDMA. Further, cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA system may implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). 3GPP Long Term Evolution (LTE) is a release of UMTS that uses E-UTRA, which employs OFDMA on the downlink and SC-FDMA on the uplink. UTRA, E-UTRA, UMTS, LTE and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP). Additionally, cdma2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). Further, such wireless communication systems may additionally include peer-to-peer (e.g., mobile-to-mobile) ad hoc network systems often using unpaired unlicensed spectrums, 802.xx wireless LAN, BLUETOOTH and any other short- or long-range, wireless communication techniques.
Various aspects or features will be presented in terms of systems that may include a number of devices, components, modules, and the like. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules etc. discussed in connection with the figures. A combination of these approaches may also be used.
Referring to FIG. 1, a wireless communication system 100 is illustrated that facilitates providing relay functionality in wireless networks. System 100 includes a donor eNB 102 that provides one or more relay eNBs, such as relay eNB 104, with access to a core network 106. Similarly, relay eNB 104 can provide one or more disparate relay eNBs, such as relay eNB 108, or UEs, such as UE 110, with access to the core network 106 via donor eNB 102. Donor eNB 102, which can also be referred to as a cluster eNB, can communicate with the core network 106 over a wired or wireless backhaul link, which can be an LTE or other technology backhaul link. In one example, the core network 106 can be a 3GPP LTE or similar technology network.
Donor eNB 102 can additionally provide an access link for relay eNB 104, which can also be wired or wireless, LTE or other technologies, and the relay eNB 104 can communicate with the donor eNB 102 using a backhaul link over the access link of the donor eNB 102. Relay eNB 104 can similarly provide an access link for relay eNB 108 and/or UE 110, which can be a wired or wireless LTE or other technology link. In one example, donor eNB 102 can provide an LTE access link, to which relay eNB 104 can connect using an LTE backhaul, and relay eNB 104 can provide an LTE access link to relay eNB 108 and/or UE 110. Donor eNB 102 can connect to the core network 106 over a disparate backhaul link technology. Relay eNB 108 and/or UE 110 can connect to the relay eNB 104 using the LTE access link to receive access to core network 106, as described. A donor eNB and connected relay eNBs can be collectively referred to herein as a cluster.
According to an example, relay eNB 104 can connect to a donor eNB 102 at the link layer (e.g., media access control (MAC) layer), transport layer, application layer, and/or the like, as would a UE in conventional LTE configurations. In this regard, donor eNB 102 can act as a conventional LTE eNB requiring no changes at the link layer, transport layer, application layer, etc, or related interface (e.g., user-to-user (Uu), such as E-UTRA-Uu, user-to-network (Un), such as EUTRA-Un, etc.), to support the relay eNB 104. In addition, relay eNB 104 can appear to UE 110 as a conventional eNB in LTE configurations at the link layer, transport layer, application layer, and/or the like, such that no changes are required for UE 110 to connect to relay eNB 104 at the link layer, transport layer, application layer, etc., for example. In addition, relay eNB 104 can configure procedures for resource partitioning between access and backhaul link, interference management, idle mode cell selection for a cluster, and/or the like. It is to be appreciated that relay eNB 104 can connect to additional donor eNBs, in one example.
Thus, for example, relay eNB 104 can establish a connection with donor eNB 102 to receive access to one or more components in core network 106 (such as a mobility management entity (MME), serving gateway (SGW), packet data network (PDN) gateway (PGW), etc.). In an example, relay eNB 104 can obtain an internet protocol (IP) address from a PGW/SGW in the core network 106 (e.g., via donor eNB 102) for communicating therewith. In addition, UE 110 can establish a connection with relay eNB 104 to receive access to one or more similar components in core network 106. In this regard, for example, UE 110 can communicate IP packets to relay eNB 104 for providing to core network 106. Relay eNB 104 can obtain the IP packets, associate an additional IP header with the packets related to relay eNB 104, and provide the packets to donor eNB 102. Thus, donor eNB 102 can route the packets to a component of core network 106 related to relay eNB 104 (e.g., by adding another header and transmitting to core network 106).
Components of core network 106, for example, can route the packets within the core network 106 according to the various IP headers. Moreover, for example, core network 106 can construct packets for providing to UE 110 to include IP headers related to routing the packet to UE 110 through relay eNB 104. In an example, core network 106 can include an IP header related to UE 110 with the packet, as well as an IP header related to relay eNB 104, and one related to donor eNB 102. Core network 106 can forward the packet with the headers to donor eNB 102. Donor eNB 102 can obtain the packet, remove the IP header related to donor eNB 102, and forward the packet to relay eNB 104 based on the next IP header. Relay eNB 104 can similarly remove the header related to relay eNB 104, in one example, and relay eNB 104 can forward the packet to UE 110 based on the remaining IP header or another header. Though one relay eNB 104 is shown between UE 110 and donor eNB 102, it is to be appreciated that additional relay eNBs can exist, and IP headers can be added to uplink and downlink packets, as described, for each relay eNB to facilitate packet routing.
In this configuration, relay eNB 104 can communicate inter-eNB packets (e.g., handover parameters or commands, interference management messages, and/or similar eNB-to-eNB messages) to donor eNB 102 and/or other relay eNBs in the cluster through core network 106. In another example, as described herein, donor eNB 102 and/or relay eNBs in the cluster can receive IP address information for disparate eNBs in the cluster to facilitate routing inter-eNB packets without utilizing components of core network 106. For example, upon attachment to core network 106, or otherwise receiving an IP address, relay eNB 104 can communicate a received IP address to donor eNB 102. Donor eNB 102 can store the IP address to facilitate subsequent packet routing to relay eNB 104 (e.g., where requested by one or more disparate relay eNBs in the cluster). Similarly, relay eNB 108 can communicate an assigned IP address to relay eNB 104, which can store the IP address and forward to donor eNB 102. Donor eNB 102 can store this IP address as well as one or more parameters regarding the next downstream relay eNB to relay eNB 104 (e.g., relay eNB 104, in this example). Furthermore, in an example, donor eNB 102 can propagate the received IP address to substantially all relay eNBs in its cluster to facilitate inter-eNB packet routing in more complex IP relay deployments.
Turning to FIG. 2, illustrated is a communications apparatus 200 for employment within a wireless communications environment. The communications apparatus 200 can be a base station or a portion thereof, a mobile device or a portion thereof, or substantially any communications apparatus that receives and transmits data over a wireless communications environment. The communications apparatus 200 can include an address receiving component 202 that obtains an address for communicating in a core network, an address providing component 204 that transmits the address to one or more relay eNBs or donor eNBs in a cluster related to communications apparatus 200, a target address specifying component 206 that indicates an address of a target relay eNB or donor eNB to receive an inter-eNB packet from communications apparatus 200, and a communicating component 208 that transmits the packet to an upstream relay eNB or donor eNB for providing to the target relay eNB or donor eNB.
According to an example, communications apparatus 200 can communicate with a core network (not shown) via one or more upstream relay eNBs (not shown) and/or a donor eNB (not shown). Upon attaching to the core network, and/or otherwise receiving an address therefrom, address receiving component 202 can obtain an address from a component of the core network for communicating therewith. For example, address receiving component 202 can obtain the address from the component via the one or more upstream relay eNBs and/or donor eNB. In addition, address providing component 204 can communicate the assigned address to the one or more upstream relay eNBs and/or donor eNB to facilitate communicating inter-eNB messages, such as handover commands and parameters, interference management information, and/or the like, with communications apparatus 200.
In addition, for example, communications apparatus 200 can communicate an inter-eNB packet with a target eNB (e.g., one or more relay eNBs or the donor eNB) in the cluster. In this example, target address specifying component 206 can specify an address of the one or more relay eNBs or the donor eNB in a header of the inter-eNB packet (e.g., rather than an address of a gateway node in the core network). Communicating component 208 can transmit the inter-eNB packet upstream for providing to the target eNB. As described in further detail herein, an upstream eNB receiving the inter-eNB packet can determine whether the inter-eNB packet is intended for the upstream eNB based at least in part on the address and/or can route the inter-eNB packet to the intended eNB based at least in part on the address. Thus, in the foregoing example, core network components, such as gateway nodes, are not required to communicate inter-eNB packets in IP relay configurations.
Turning to FIG. 3, a wireless communication system 300 is illustrated that facilitates supporting IP relay communications in a wireless network. System 300 includes a donor eNB 102 that provides one or more relay eNBs, such as relay eNB 104, with access to a core network 106. Similarly, relay eNB 104 can provide one or more disparate relay eNBs or UEs, such as UE 110, with access to the core network 106 via donor eNB 102, as described. Moreover, donor eNB 102 can be a macrocell access point, femtocell access point, picocell access point, mobile base station, and/or the like. Relay eNB 104 can similarly be a mobile or stationary relay node that communicates with donor eNB 102 over a wireless or wired backhaul, as described. In addition, for example, one or more intermediary relay eNBs can be present between donor eNB 102 and relay eNB 104 and can comprise components thereof to facilitate similar functionality.
Donor eNB 102 can include a communicating component 302 that transmits data to and/or receives data from a relay eNB over an access link and/or a core network over a backhaul link to provide access to the relay eNB. Donor eNB 102 also includes a routing parameter receiving component 304 that receives information regarding routing packets to a relay eNB and a routing table component 306 that stores the information for subsequent routing of packets to the relay eNB. Relay eNB 104 includes a communicating component 308 that transmits data to and/or receives data from a UE or other relay eNBs over an access link and/or a donor eNB or one or more upstream relay eNBs over a backhaul link. Relay eNB 104 also includes an address receiving component 310 that obtains an address from a core network (e.g., via one or more disparate eNBs) for communicating therewith and an address providing component 312 that communicates the address to one or more disparate eNBs to facilitate receiving inter-eNB messages therefrom.
According to an example, relay eNB 104 can request attachment to core network 106 via donor eNB 102. In this example, communicating component 308 can transmit the request to donor eNB 102, and communicating component 302 can receive and forward the request based at least in part on one or more parameters in the request or a header thereof. Core network 106 can assign an address, such as an IP address, to relay eNB 104 for communicating with core network 106 and/or one or more components thereof. Indeed, communicating component 308 can specify the IP address in communications intended for core network 106 and can forward the communications to donor eNB 102. Address receiving component 310 can obtain the address from core network 106 and can utilize the address in subsequent communications therewith. In addition, address providing component 312 can transmit the address to donor eNB 102 (e.g., in a message transmitted by communicating component 308).
Routing parameter receiving component 304 can obtain the address from relay eNB 104 (e.g., in a message received at communicating component 302), and routing table component 306 can store the address for subsequent use in communicating inter-eNB packets directly to relay eNB 104 without utilizing core network 106 and/or one or more upstream components thereof. In this regard, as described in further detail herein, communicating component 302 can receive an inter-eNB packet from disparate eNBs, and routing table component 306 can determine whether an address related to the inter-eNB packet is stored by the routing table component 306. If so, communicating component 302 can forward the inter-eNB packet to a relay eNB corresponding to the address based at least in part on additional information in the routing table component 306 related to the address (e.g., a related radio bearer for communicating with the relay eNB, a next downstream relay eNB in a communications path to the relay eNB, resources assigned to the relay eNB for receiving communications from donor eNB 102, and/or the like). In another example, an intermediary relay eNB (not shown) between relay eNB 104 and donor eNB 102 can similarly receive the address from relay eNB 104 and store the address using a routing table component. In addition, the intermediary relay eNB can forward the address information to donor eNB 102 for storing, as described above.
Referring to FIG. 4, a wireless communication system 400 is illustrated that facilitates supporting IP relay communications in a wireless network. System 400 includes a donor eNB 102 that provides one or more relay eNBs, such as relay eNB 104 and/or relay eNB 402, with access to a core network 106. Similarly, relay eNB 104 and/or relay eNB 402 can provide one or more disparate relay eNBs or UEs, such as UE 110, with access to the core network 106 via donor eNB 102, as described. Moreover, donor eNB 102 can be a macrocell access point, femtocell access point, picocell access point, mobile base station, and/or the like. Relay eNB 104 and relay eNB 402 can similarly be mobile or stationary relay nodes that communicate with donor eNB 102 over a wireless or wired backhaul, as described. In addition, for example, one or more intermediary relay eNBs can be present between donor eNB 102 and relay eNB 104 (and/or relay eNB 402) and can comprise components thereof to facilitate similar functionality.
Donor eNB 102 can include a communicating component 302 that transmits data to and/or receives data from a relay eNB over an access link and/or a core network over a backhaul link to provide access to the relay eNB. Donor eNB 102 also includes an address determining component 404 that discerns an address from an inter-eNB packet received from one or more relay eNBs and a routing table component 306 that determines a relay eNB related to the address. Relay eNB 104 includes a communicating component 308 that transmits data to and/or receives data from a UE or other relay eNBs over an access link and/or a donor eNB or one or more upstream relay eNBs over a backhaul link. Relay eNB 104 also includes an inter-eNB packet generating component 406 that creates an inter-eNB packet for communicating to an eNB in the cluster related to relay eNB 104 and an address assigning component 408 that associates an address of a relay eNB for which the inter-eNB packet is intended with the inter-eNB packet.
According to an example, as described, donor eNB 102 can store addresses received from one or more relay eNBs in its cluster, such as relay eNB 104 and/or relay eNB 402 using routing table component 306. Thus, for example, inter-eNB packet generating component 406 can create a packet for communicating to relay eNB 402. As described, the packet can relate to one or more inter-eNB messages, such as handover preparation messages or other commands, interference management/resource blanking messages, and/or the like. Address assigning component 408 can insert an address of relay eNB 402 in a header of the packet. The address can be received by relay eNB 104 from UE 110 (e.g., in a measurement report), for example, or one or more disparate network components, and the inter-eNB packet generating component 406 can be created based on receiving the address. Communicating component 308 can transmit the packet to donor eNB 102.
Communicating component 302 can receive the packet, and address determining component 404 can retrieve an address from a header of the packet related to a destination eNB. For example, address determining component 404 can discern whether the address is the address assigned to donor eNB 102. If so, donor eNB 102 can process the packet. In another example, address determining component 404 can query routing table component 306 to determine whether the address is stored in routing table component 306. If so, for example, communicating component 302 can transmit the packet according to an entry in the routing table component 306 for the address, which can specify a next downstream relay eNB in a communications path to the relay eNB corresponding to the address, a radio bearer and/or resources for communicating with the relay eNB corresponding to the address, and/or the like, as described. In one example, if the address is not stored in routing table component 306, donor eNB 102 can forward the packet to core network 106 for processing and/or routing.
In addition, it is to be appreciated that one or more intermediary relay eNBs (not shown) can exist between relay eNB 104 (and/or relay eNB 402) and donor eNB 102. In this example, as described, the intermediary relay eNBs can similarly include address determining components and routing table components for discerning and storing addresses of other relay eNBs in the cluster. Thus, for example, where the intermediary relay eNB receives a packet from relay eNB 104, it can determine an address in the packet header and consult its routing table component to determine whether the address relates to a relay eNB in the cluster. If so, the intermediary relay eNB can forward the packet to another upstream relay eNB (e.g., if the target relay eNB indicated the packet header is not served by the intermediary relay eNB), which can include adding another header related to the upstream relay eNB. If the target relay eNB is served by the intermediary relay eNB, it can forward the packet to the target relay eNB. In a further example, in this regard, the intermediary relay eNB, can store a routing table related to relay eNBs it serves and a disparate routing table related to the other relay eNBs in the cluster. Based on which routing table component comprises the address, the intermediary relay eNB can forward the packet accordingly.
For example, UE 110 can send a measurement report to relay eNB 104 related to handing over communications to a disparate eNB. Communicating component 308 can receive the measurement report, and inter-eNB packet generating component 406 can create a handover preparation message for relay eNB 402 based at least in part on the measurement report (e.g., where relay eNB 402 has a desirable signal-to-noise ratio (SNR) as compared to relay eNB 104, etc.). Address assigning component 408 can, thus, insert an address (e.g., an IP address) of relay eNB 402 in a header of the handover preparation message, where the address can be received from the measurement report. Communicating component 308 can transmit the handover preparation message to donor eNB 102.
Communicating component 302 can obtain the measurement report, and address determining component 404 can receive the address from the header of the message. Where address determining component 404 discerns that the address is that of donor eNB 102, donor eNB 102 can process the handover preparation message. Otherwise, for example, routing table component 306 can attempt to locate the address in a list of stored addresses. If routing table component 306 locates the address, communicating component 302 can forward the handover preparation message based at least in part on information stored with the address. In this example, routing table component 306 can identify the address as that of relay eNB 402, and communicating component 302 can forward the handover preparation message thereto for processing.
In FIG. 5, an example wireless communication system 500 that facilitates efficiently communicating handover messages between IP relays without utilizing gateway nodes, MMEs, or other core network components further upstream than a donor eNB is illustrated. System 500 includes a donor eNB 102 that provides one or more relay eNBs, such as source relay eNB 502 and/or target relay eNB 504, with access to a core network 106. Similarly, source relay eNB 502 and/or target relay eNB 504 can provide one or more disparate relay eNBs or UEs, such as UE 110, with access to the core network 106 via donor eNB 102, as described. Moreover, donor eNB 102 can be a macrocell access point, femtocell access point, picocell access point, mobile base station, and/or the like. Source relay eNB 502 and target relay eNB 504 can similarly be mobile or stationary relay nodes that communicate with donor eNB 102 over a wireless or wired backhaul, as described. In addition, for example, one or more intermediary relay eNBs can be present between donor eNB 102 and source relay eNB 502 (and/or target relay eNB 504) and can comprise components thereof to facilitate similar functionality.
Source relay eNB 502 includes a communicating component 506 that transmits data to and/or receives data from a UE or other relay eNBs over an access link and/or a donor eNB or one or more upstream relay eNBs over a backhaul link and a bearer modification requesting component 508 that generates a UE requested bearer resource modification procedure to setup uplink resources with an upstream eNB for forwarding downlink data to a target relay eNB. Source relay eNB 502 additionally includes a handover requesting component 510 that generates a request to handover communications of a UE to a target relay eNB, a tunnel endpoint identifier (TEID) receiving component 512 that obtains a TEID or other identifier to utilize for communicating packets to the target relay eNB, and a tunneling component 514 that applies a tunneling header to communications for the target relay eNB.
Donor eNB 102 can include a communicating component 302 that transmits data to and/or receives data from a relay eNB over an access link and/or a core network over a backhaul link to provide access to the relay eNB. Donor eNB 102 also includes a bearer establishing component 516 that initializes one or more bearers with a relay eNB for communicating therewith, a routing table component 306 that stores addresses related to one or more relay eNBs in the cluster of donor eNB 102, and a bearer mapping component 518 that communicates packets to the one or more relay eNBs in the cluster over a bearer based at least in part on an identifier specified in the packets.
Target relay eNB 504 includes a communicating component 520 that transmits data to and/or receives data from a UE or other relay eNBs over an access link and/or a donor eNB or one or more upstream relay eNBs over a backhaul link and a TEID assigning component 522 that generates a TEID for communicating packets to target relay eNB 504. Target relay eNB 504 also includes a handover acknowledging component 524 that generates a handover acknowledgement based on receiving a handover request from a source relay eNB and a routing reporting component 526 that informs a donor eNB regarding mapping between the generated TEID and a bearer established with the donor eNB.
According to an example, UE 110 can provide a measurement report to source relay eNB 502, and source relay eNB 502 can initiate a handover procedure to handover communications of UE 110 to target relay eNB 504 based at least in part on the measurement report. In this example, bearer modification requesting component 508 can initiate a bearer resource modification procedure to setup uplink resources with donor eNB 102 for communicating with target relay eNB 504 without routing through a core network (not shown). Bearer establishing component 516 can obtain the request and establish a bearer with source relay eNB 502 for forwarding parameters and/or messages as part of the handover procedure.
For example, handover requesting component 510 can generate a request to handover UE 110 communications, specifying an address of target relay eNB 504 (e.g., based on the measurement report, as described), and communicating component 506 can transmit the handover request to donor eNB 102. Communicating component 302 can receive the handover request, and routing table component 306 can determine a relay eNB to receive the handover request based at least in part on an address in a header in the handover request, as described. Communicating component 302 can transmit the handover request to target relay eNB 504 based at least in part on locating the address in routing table component 306 (e.g., where routing table component 306 previously received the address from target relay eNB 504). Communicating component 520 can receive the handover request and determine that the handover request relates to target relay eNB 504 (e.g., based on the address).
In addition, for example, TEID assigning component 522 can generate a TEID for a bearer established between target relay eNB 504 and donor eNB 102 for receiving handover data from source relay eNB 502. In addition, handover acknowledging component 524 can create a handover request acknowledgement, which can include the TEID, for transmitting upstream and can insert an address of source relay eNB 502 in the handover request acknowledgement. For example, target relay eNB 104 can acquire the address or source relay eNB from the handover request. Communicating component 520 can transmit the handover request acknowledgement to donor eNB 102, which can similarly determine that the handover request acknowledgement is intended for source relay eNB 502 (e.g., based at least in part on locating the address in routing table component 306). Thus, communicating component 302 can forward the handover request acknowledgement to source relay eNB 502, as described.
Communicating component 506, for example, can receive the handover request acknowledgement, and TEID receiving component 512 can extract a TEID therefrom (e.g., and/or from one or more related messages) for tunneling handover messages and/or related data to target relay eNB 504. In addition, for example, routing reporting component 526 can generate a routing report for transmitting to the donor eNB 102 that associates the TEID with a bearer between target relay eNB 504 and donor eNB 102. Communicating component 520 can transmit the routing report, and communicating component 302 can receive the message. In addition, for example, bearer mapping component 518 can establish an association between the TEID and the bearer with target relay eNB 504, as received in the routing report.
Thus, for example, source relay eNB 502 can subsequently transmit forwarded data to target relay eNB 504 via donor eNB 102. In this example, tunneling component 514 can attach a tunneling protocol header, such as a general packet radio service (GPRS) tunneling protocol (GTP) header, including the TEID, to the forwarded data. Communicating component 506 can transmit the forwarded data to donor eNB 102 over the radio bearer established by bearer establishing component 516, as described above. Communicating component 302 can receive the forwarded data, and routing table component 306 can determine that the forwarded data corresponds to target relay eNB 504. Furthermore, bearer mapping component 518 can determine a bearer with target relay eNB 504 corresponding to the TEID in the GTP header, which can be based on the routing report, as described previously. Thus, for example, communicating component 302 can transmit the forwarded data to target relay eNB over the bearer based on the TEID.
It is to be appreciated, in one example, that target relay eNB 504 can establish a dedicated radio bearer (DRB) with donor eNB 102 for receiving the forwarded data (e.g., where the DRB is mapped to the TEID by bearer mapping component 518 upon receiving the routing report). In this example, target relay eNB 504 can keep the bearer with donor eNB 102 and/or remove the bearer upon completion of the handover procedure. Moreover, as described, though the example depicted relates to relay eNBs directly connected to donor eNB 102, it is to be appreciated that the relay eNBs in a cluster can similarly include routing table components to assure that inter-eNB messages are routed among the relay eNBs in the cluster without utilizing core network components upstream to donor eNB 102.
Referring to FIG. 6, an example wireless communication system 600 is illustrated that facilitates attaching a relay eNB to a core network. System 600 includes a relay eNB 2 602 that communicates with a relay eNB 1 604 to receive access to a wireless network. Relay eNB 1 604 can communicate with donor eNB 102 for providing wireless network access. Donor eNB 102 communicates with one or more core network components, such as one or more gateway nodes, MMEs, and/or the like. As depicted, donor eNB 102 can communicate with ReNB 1 PGW/SGW 606 and/or ReNB 2 PGW/SGW 608 (e.g., via ReNB 1 PGW/SGW 606 or otherwise). In addition, donor eNB 102 can communicate with a relay eNB 1 MME 610 and/or relay eNB 2 MME 612 (e.g., via one or more of the PGW/SGWs) to authorize one or more devices with the core network. In addition, donor eNB 102 can facilitate communications with an operation, administration, and maintenance (OAM) node 614 to obtain an eNB ID for one or more relay eNBs.
According to an example, relay eNB 2 602 can request attachment to the wireless network. Thus, relay eNB 2 602 can initial perform a random access procedure with relay eNB 1 604 to acquire communications resources therefrom, and relay eNB 2 602 can attach to the network 616 using the resources to communicate with additional nodes in the wireless network. For example, ReNB 2 MME 612 can authenticate relay eNB 2 602 and/or ReNB 2 PGW/SGW 608 can assign an IP address to relay eNB 2 602. Furthermore, relay eNB 2 602 can obtain an eNB ID 618 from an OAM 614 via one or more additional network nodes. Upon receiving the eNB ID, relay eNB 2 602 can transmit an S1 setup request 620 to relay eNB 1 604 to establish an S1 protocol for communicating control data therewith.
Relay eNB 1 604 can communicate a transport address acquire 622 to relay eNB 2 602 to retrieve a transport address therefrom to facilitate routing inter-eNB packets, as described. Relay eNB 2 602 can thus transmit a transport address report 624 to relay eNB 1 604 that includes an address (e.g., an IP address) assigned by relay eNB 2 PGW/SGW 608. Relay eNB 1 604, as described, can store the address in a routing table for subsequently communicating packets with relay eNB 2 602 without utilizing relay eNB 2 PGW/SGW 608. Relay eNB 1 604 can forward the transport address report 626 to donor eNB 102, which can similarly store the address in a routing table, as described.
Relay eNB 1 604 can then encapsulate the setup request in a GTP or similar tunnel 628 (e.g., by utilizing a tunneling header in association with the request), and can transmit the setup request 630 to donor eNB 102. Donor eNB 102 can forward the setup request 632 to relay eNB 1 PGW/SGW 606, which can forward the setup request 634 to relay eNB 2 PGW/SGW 608 in the tunnel 628. Relay eNB 2 PGW/SGW 608 can remove the tunneling from the setup request, and can transmit the S1 setup request 636 to relay eNB 2 MME 612. Relay eNB 2 MME 612 can transmit an S1 setup response 638 to relay eNB 2 PGW/SGW 608 related to the S1 setup request. Relay eNB 2 PGW/SGW 608 can encapsulate the setup response in a tunnel 640, as described, and can communicate the setup response 642 to relay eNB 1 PGW/SGW 606, which can forward the setup response 644 to donor eNB 102, which can forward the setup response 646 to relay eNB 1 604 in the tunnel 640. Relay eNB 1 604 can remove the tunneling header and process the setup response, for example.
Now referring to FIGS. 7-8, example wireless communication systems are shown that facilitate handing over UE communications among relay eNBs utilizing efficient routing of inter-eNB packets. In FIG. 7, a wireless communication system 700 is depicted that facilitates establishing bearers for communicating inter-eNB packets as part of a handover procedure. System 700 includes a UE 110 that communicates with a source relay eNB 702 to receive access to a core network. A target relay eNB 704 is also show to which source relay eNB 702 can handover UE 110 communications. In addition, system 700 includes a donor eNB 102 that provide source relay eNB 702 and target relay eNB 704 with access to core network components, such as source relay eNB PGW/SGW 706 and target relay eNB PGW/SGW 708.
According to an example, UE 110 can transmit measurement reports 710 to source relay eNB 702 as part of a handover procedure. The measurement reports 710, for example, can include measurements of one or more communication metrics of neighboring access points (including target relay eNB 704). Source relay eNB 702 can request bearer resource modification 712 with source relay eNB PGW/SGW 706 to establish uplink communication resources with donor eNB 102 for transmitting downlink packets for handover. Source relay eNB 702 can initialize a handover decision 714 to handover UE 110 communications to target relay eNB 704 based at least in part on the measurement report. In this regard, source relay eNB 702 can transmit a handover request 716 to donor eNB 102, which can forward the handover request 718 (or send a new handover request) to target relay eNB 704.
Target relay eNB 704 can perform admission control 720 or other quality of service (QoS) procedure to determine resource allocation based on bandwidth, latency, and/or the like, for example. Target relay eNB 704 can additionally request bearer resource modification 722 with target relay eNB PGW/SGW 708 to establish downlink resources with donor eNB 102 for receiving downlink packets during handover. Target relay eNB 704 can transmit a handover request acknowledgement 724 to donor eNB 102. In addition, target relay eNB 704 can also associate a TEID with the downlink resources for associating to the target relay eNB 704, and can transmit a routing report 726 to donor eNB 102 that specifies the association between the TEID and the downlink resources. Donor eNB 102 can transmit a routing report complete 728 to target relay eNB 704 to acknowledge the routing report. Donor eNB 102 can also transmit the handover request acknowledgement to source relay eNB 702, which can include the TEID. Thus, source relay eNB 702 can provide a downlink resource allocation 732 to UE 110, and can transmit a handover command 734 to UE 110 over the downlink resource allocation.
Turning to FIG. 8, a wireless communication system 800 is illustrated that can be similar to wireless communication 700 of FIG. 7 and can represent messages passed following those of FIG. 7. Source relay eNB 702 can transmit a sequence number (SN) status transfer 802 to donor eNB 102, which can include one or more parameters related to a SN of a last packet sent to UE 110 by source relay eNB 702. For example, source relay eNB 702 can include the transport address of target relay eNB 704 (which can be previously received as in FIG. 6) in the SN status transfer 802. In this example, donor eNB 102 can forward the SN status transfer 804 to target relay eNB 704 based at least in part on the transport address. For example, donor eNB 102 can obtain the transport address and locate it in a routing table, as described.
Source relay eNB 702 can similarly specify the transport address in data for forwarding 806 to target relay eNB 704 through donor eNB 102, as described. In this example, donor eNB 102 can receive the data for forwarding 806, determine that the target relay eNB 704 is to receive the data (e.g., based on the transport address), and forward the data to target relay eNB 704 by tunneling the data according to a TEID associated with downlink resources. In another example, source relay eNB 702 can associate a tunneling header with the data for forwarding 806, and can specify the received TEID, as described, in the tunneling header. In this example, donor eNB 102 can tunnel the data for forwarding 806 to the target relay eNB 704. Target relay eNB 704 can buffer the packets from source relay eNB 808. Subsequently, UE 110 can perform synchronization 810 with target relay eNB 704, and target relay eNB 704 can provide an uplink allocation and timing advance (TA) 812 to the UE 110. UE 110 can confirm handover 814. It is to be appreciated that target relay eNB 704 can begin to transmit buffered packets to UE 110 and/or donor eNB 102 to continue UE 110 communications with the core network.
Now turning to FIG. 9, an example wireless communication network 900 that provides IP relay functionality is depicted. Network 900 includes a UE 110 that communicates with a relay eNB 104, as described, to receive access to a wireless network. Relay eNB 104 can communicate with a donor eNB 102 to provide access to a wireless network, and as described, donor eNB 102 can communicate with an MME 902 and/or SGW 904 that relate to the relay eNB 104. SGW 904 can connect to or be coupled with a PGW 906, which provides network access to SGW 904 and/or additional SGWs. PGW 906 can communicate with a PCRF 908 to authenticate/authorize relay eNB 104 to use the network, which can utilize an IMS 910 to provide addressing to the relay eNB 104.
According to an example, SGW 904 and PGW 906 can also communicate with SGW 916 and PGW 918, which can be related to UE 110. For example, SGW 916 and/or PGW 918 can assign an IP address to UE 110 and can communicate therewith via SGW 904 and PGW 906, donor eNB 102, and relay eNB 104. As described above, communications between UE 110 and SGW 916 and/or PGW 918 can be tunneled through the nodes. SGW 904 and PGW 906 can similarly tunnel communications between UE 110 and MME 914. PGW 918 can similarly communicate with a PCRF 908 to authenticate/authorize UE 110, which can communicate with an IMS 910. In addition, PGW 918 can communicate directly with the IMS 910 and/or internet 912.
In an example, UE 110 can communicate with the relay eNB 104 over one or more radio protocol interfaces, such as an E-UTRA-Uu interface, as described, and the relay eNB 104 can communicate with the donor eNB 102 using one or more radio protocol interfaces, such as an E-UTRA-Un or other interface. As described, relay eNB 104 can add an UDP/IP and/or GTP header related to SGW 904 and/or PGW 906 to packets received from UE 110 and can forward the packets to donor eNB 102. Donor eNB 102 communicates with the MME 902 using an S1-MME interface and the SGW 904 and PGW 906 over an S1-U interface, as depicted. For example, donor eNB 102 can similarly add an UDP/IP and/or GTP header to the packets and forward to MME 902 or SGW 904.
SGW 904 and/or PGW 906 can utilize the UDP/IP and/or GTP headers to route the packets within the core network. For example, as described, SGW 904 and/or PGW 906 can receive the packets and remove the outer UDP/IP and/or GTP header, which relates to the SGW 904 and/or PGW 906. SGW 904 and/or PGW 906 can process the next UDP/IP and/or GTP header to determine a next node to receive the packets, which can be SGW 916 and/or PGW 918, which relate to UE 110. Similarly, SGW 916 and/or PGW 918 can obtain downlink packets related to UE and can include an UDP/IP header and/or GTP header related to communicating the packets to relay eNB 104 for providing to UE 110. SGW 916 and/or PGW 918 can forward the packets to SGW 904 and/or PGW 906, which relate to relay eNB 104. SGW 904 and/or PGW 906 can further include an additional UDP/IP and/or GTP header in the packets related to donor eNB 102.
Moreover, SGW 904 and/or PGW 906 can select a GTP tunnel over which to communicate the packets to donor eNB 102. This can be based on information in the UDP/IP and/or GTP headers received from SGW 916 and/or PGW 918, as described, and/or the like. SGW 904 and/or PGW 906 can communicate the packets to donor eNB 102 over the tunnel (e.g., by including one or more parameters in the GTP header included by SGW 904 and/or PGW 906). Donor eNB 102 can remove the outer GTP and/or UDP/IP header included by SGW 904 and/or PGW 906 and can determine a next node to receive the packets. Donor eNB 102 can thus transmit the packets to relay eNB 104 over a radio bearer related to the GTP tunnel Relay eNB 104 can similarly determine a next node to receive the packets and/or a bearer over which to transmit the packets based at least in part on one or more parameters in the next UDP/IP or GTP header, the radio bearer over which the packets are received, etc. Relay eNB 104 can remove the UDP/IP and GTP headers and can transmit the packets to UE 110.
Referring to FIGS. 10-14, methodologies relating to routing packets using IP relays are illustrated. While, for purposes of simplicity of explanation, the methodologies are shown and described as a series of acts, it is to be understood and appreciated that the methodologies are not limited by the order of acts, as some acts may, in accordance with one or more aspects, occur in different orders and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all illustrated acts may be required to implement a methodology in accordance with one or more aspects.
Turning to FIG. 10, an example methodology 1000 that facilitates efficiently communicating inter-eNB packets among relay eNBs is illustrated. At 1002, a plurality of packets can be transmitted to an upstream eNB for communicating with a wireless network. For example, the packets can include inter-eNB packets as well as packets intended for a network component to which a connection has been established. At 1004, an address received from a gateway for communicating therewith can be specified in a portion of the packets. Thus, the upstream eNB, for example, can communicate the portion of the packets further upstream to the gateway (e.g., through one or more additional network components). At 1006, a disparate address for communicating with a disparate eNB can be specified in a disparate portion of the packets. As described, the disparate portion of the packets can relate to inter-eNB packets, and the upstream eNB can communicate the inter-eNB packets to the disparate eNB, in one example, without utilizing the gateway.
Referring to FIG. 11, an example methodology 1100 is depicted that facilitates communicating inter-eNB packets to one or more relay eNBs in a cluster. At 1102, an address related to a packet obtained from a downstream relay eNB can be received. For example, the address can be extracted from a header of the packet. At 1104, the address can be located in a routing table of addresses related to relay eNBs in a cluster. In this example, as described, addresses can be received from the relay eNBs (e.g., during relay eNB attachment) and stored in the routing table along with one or more parameters for communicating with the relay eNBs. At 1106, the packet can be transmitted to a disparate relay eNB in the cluster based at least in part on locating the address in the routing table. In this regard, efficient inter-eNB packet routing is provided allowing eNBs to specify addresses of relay eNBs in a cluster to which to route inter-eNB packets, and the inter-eNB packets are accordingly routed without requiring communications with a gateway.
Turning to FIG. 12, an example methodology 1200 for tunneling packets to a relay eNB based on a received TEID is illustrated. At 1202, a UE requested bearer resource modification procedure can be initiated. In one example, the UE requested bearer resource modification procedure can be performed with a donor eNB to request uplink resources for communicating inter-eNB packets to a relay eNB. A request can be sent to a relay eNB for communicating therewith at 1204. As described, for example, the request can be sent to the relay eNB through the donor eNB. At 1206, a request acknowledgement can be received from the relay eNB including a TEID. In an example, the request acknowledgement can be received through the donor eNB. At 1208, packets can be tunneled to the relay eNB by including a tunneling protocol header with the TEID. Thus, for example, the donor eNB can forward packets to the relay eNB based on the TEID.
Referring to FIG. 13, an example methodology 1300 is shown that facilitates communicating packets between eNBs in a cluster. At 1302, uplink resources can be allocated to a relay eNB. This can be in response to a UE requested bearer resource modification, as described, previously. At 1304, a TEID and an associated bearer identifier can be received from a disparate relay eNB in a routing report. As described, the relay eNB can receive a request for communications from a disparate eNB and can designate a bearer to receive communications from the disparate eNB. Thus, at 1306, communications received in the uplink resources that specify the TEID can be forwarded over a bearer corresponding to the bearer identifier.
Turning to FIG. 14, an example methodology 1400 that acknowledges a request for communicating inter-eNB packets with an eNB is illustrated. At 1402, a request can be received from an eNB for communicating therewith. As described, the request can be received from a disparate upstream eNB, such as a donor eNB. At 1404, a TEID and associated bearer identifier can be transmitted to a donor eNB in a routing report. In this regard, the donor eNB can associate the TEID with the bearer identifier for transmitting packets received with the TEID over a corresponding bearer, as described. At 1406, the TEID can be transmitted to the eNB in a request acknowledgement. The request acknowledgement can be transmitted to the eNB via the donor eNB. Thus, the eNB can specify the TEID in a tunneling protocol when transmitting inter-eNB packets, as described.
It will be appreciated that, in accordance with one or more aspects described herein, inferences can be made regarding determining whether an address of a relay eNB is stored in a routing table, communicating a UE requested bearer resource modification, determining a bearer associated with a bearer identifier, and/or other aspects described herein. As used herein, the term to “infer” or “inference” refers generally to the process of reasoning about or inferring states of the system, environment, and/or user from a set of observations as captured via events and/or data. Inference can be employed to identify a specific context or action, or can generate a probability distribution over states, for example. The inference can be probabilistic—that is, the computation of a probability distribution over states of interest based on a consideration of data and events. Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data. Such inference results in the construction of new events or actions from a set of observed events and/or stored event data, whether or not the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources.
Referring now to FIG. 15, a wireless communication system 1500 is illustrated in accordance with various embodiments presented herein. System 1500 comprises a base station 1502 that can include multiple antenna groups. For example, one antenna group can include antennas 1504 and 1506, another group can comprise antennas 1508 and 1510, and an additional group can include antennas 1512 and 1514. Two antennas are illustrated for each antenna group; however, more or fewer antennas can be utilized for each group. Base station 1502 can additionally include a transmitter chain and a receiver chain, each of which can in turn comprise a plurality of components associated with signal transmission and reception (e.g., processors, modulators, multiplexers, demodulators, demultiplexers, antennas, etc.), as will be appreciated by one skilled in the art.
Base station 1502 can communicate with one or more mobile devices such as mobile device 1516 and mobile device 1522; however, it is to be appreciated that base station 1502 can communicate with substantially any number of mobile devices similar to mobile devices 1516 and 1522. Mobile devices 1516 and 1522 can be, for example, cellular phones, smart phones, laptops, handheld communication devices, handheld computing devices, satellite radios, global positioning systems, PDAs, and/or any other suitable device for communicating over wireless communication system 1500. As depicted, mobile device 1516 is in communication with antennas 1512 and 1514, where antennas 1512 and 1514 transmit information to mobile device 1516 over a forward link 1518 and receive information from mobile device 1516 over a reverse link 1520. Moreover, mobile device 1522 is in communication with antennas 1504 and 1506, where antennas 1504 and 1506 transmit information to mobile device 1522 over a forward link 1524 and receive information from mobile device 1522 over a reverse link 1526. In a frequency division duplex (FDD) system, forward link 1518 can utilize a different frequency band than that used by reverse link 1520, and forward link 1524 can employ a different frequency band than that employed by reverse link 1526, for example. Further, in a time division duplex (TDD) system, forward link 1518 and reverse link 1520 can utilize a common frequency band and forward link 1524 and reverse link 1526 can utilize a common frequency band.
Each group of antennas and/or the area in which they are designated to communicate can be referred to as a sector of base station 1502. For example, antenna groups can be designed to communicate to mobile devices in a sector of the areas covered by base station 1502. In communication over forward links 1518 and 1524, the transmitting antennas of base station 1502 can utilize beamforming to improve signal-to-noise ratio of forward links 1518 and 1524 for mobile devices 1516 and 1522. Also, while base station 1502 utilizes beamforming to transmit to mobile devices 1516 and 1522 scattered randomly through an associated coverage, mobile devices in neighboring cells can be subject to less interference as compared to a base station transmitting through a single antenna to all its mobile devices. Moreover, mobile devices 1516 and 1522 can communicate directly with one another using a peer-to-peer or ad hoc technology (not shown).
According to an example, system 1500 can be a multiple-input multiple-output (MIMO) communication system. Further, system 1500 can utilize substantially any type of duplexing technique to divide communication channels (e.g., forward link, reverse link, . . . ) such as FDD, FDM, TDD, TDM, CDM, and the like. In addition, communication channels can be orthogonalized to allow simultaneous communication with multiple devices over the channels; in one example, OFDM can be utilized in this regard. Thus, the channels can be divided into portions of frequency over a period of time. In addition, frames can be defined as the portions of frequency over a collection of time periods; thus, for example, a frame can comprise a number of OFDM symbols. The base station 1502 can communicate to the mobile devices 1516 and 1522 over the channels, which can be create for various types of data. For example, channels can be created for communicating various types of general communication data, control data (e.g., quality information for other channels, acknowledgement indicators for data received over channels, interference information, reference signals, etc.), and/or the like.
FIG. 16 shows an example wireless communication system 1600. The wireless communication system 1600 depicts one base station 1610 and one mobile device 1650 for sake of brevity. However, it is to be appreciated that system 1600 can include more than one base station and/or more than one mobile device, wherein additional base stations and/or mobile devices can be substantially similar or different from example base station 1610 and mobile device 1650 described below. In addition, it is to be appreciated that base station 1610 and/or mobile device 1650 can employ the systems (FIGS. 1-9 and 15) and/or methods (FIGS. 10-14) described herein to facilitate wireless communication therebetween.
At base station 1610, traffic data for a number of data streams is provided from a data source 1612 to a transmit (TX) data processor 1614. According to an example, each data stream can be transmitted over a respective antenna. TX data processor 1614 formats, codes, and interleaves the traffic data stream based on a particular coding scheme selected for that data stream to provide coded data.
The coded data for each data stream can be multiplexed with pilot data using orthogonal frequency division multiplexing (OFDM) techniques. Additionally or alternatively, the pilot symbols can be frequency division multiplexed (FDM), time division multiplexed (TDM), or code division multiplexed (CDM). The pilot data is typically a known data pattern that is processed in a known manner and can be used at mobile device 1650 to estimate channel response. The multiplexed pilot and coded data for each data stream can be modulated (e.g., symbol mapped) based on a particular modulation scheme (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM), etc.) selected for that data stream to provide modulation symbols. The data rate, coding, and modulation for each data stream can be determined by instructions performed or provided by processor 1630.
The modulation symbols for the data streams can be provided to a TX MIMO processor 1620, which can further process the modulation symbols (e.g., for OFDM). TX MIMO processor 1620 then provides N_Tmodulation symbol streams to N_Ttransmitters (TMTR) 1622 a through 1622 t. In various aspects, TX MIMO processor 1620 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.
Each transmitter 1622 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. Further, N_Tmodulated signals from transmitters 1622 a through 1622 t are transmitted from N_Tantennas 1624 a through 1624 t, respectively.
At mobile device 1650, the transmitted modulated signals are received by N_Rantennas 1652 a through 1652 r and the received signal from each antenna 1652 is provided to a respective receiver (RCVR) 1654 a through 1654 r. Each receiver 1654 conditions (e.g., filters, amplifies, and downconverts) a respective signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding “received” symbol stream.
An RX data processor 1660 can receive and process the N_Rreceived symbol streams from N_Rreceivers 1654 based on a particular receiver processing technique to provide N_T“detected” symbol streams. RX data processor 1660 can demodulate, deinterleave, and decode each detected symbol stream to recover the traffic data for the data stream. The processing by RX data processor 1660 is complementary to that performed by TX MIMO processor 1620 and TX data processor 1614 at base station 1610.
A processor 1670 can periodically determine which precoding matrix to utilize as discussed above. Further, processor 1670 can formulate a reverse link message comprising a matrix index portion and a rank value portion.
The reverse link message can comprise various types of information regarding the communication link and/or the received data stream. The reverse link message can be processed by a TX data processor 1638, which also receives traffic data for a number of data streams from a data source 1636, modulated by a modulator 1680, conditioned by transmitters 1654 a through 1654 r, and transmitted back to base station 1610.
At base station 1610, the modulated signals from mobile device 1650 are received by antennas 1624, conditioned by receivers 1622, demodulated by a demodulator 1640, and processed by a RX data processor 1642 to extract the reverse link message transmitted by mobile device 1650. Further, processor 1630 can process the extracted message to determine which precoding matrix to use for determining the beamforming weights.
Processors 1630 and 1670 can direct (e.g., control, coordinate, manage, etc.) operation at base station 1610 and mobile device 1650, respectively. Respective processors 1630 and 1670 can be associated with memory 1632 and 1672 that store program codes and data. Processors 1630 and 1670 can also perform computations to derive frequency and impulse response estimates for the uplink and downlink, respectively.
With reference to FIG. 17, illustrated is a system 1700 that facilitates communicating inter-eNB packets to one or more eNBs in a cluster. For example, system 1700 can reside at least partially within a base station, mobile device, etc. It is to be appreciated that system 1700 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (e.g., firmware). System 1700 includes a logical grouping 1702 of electrical components that can act in conjunction. For instance, logical grouping 1702 can include an electrical component for communicating with an upstream eNB to access a gateway in a wireless network based at least in part on an address received from the gateway 1704. For example, as described, the upstream eNB can be a donor eNB that provides access to the gateway and/or one or more core network components. Additionally, logical grouping 1702 can include an electrical component for indicating a disparate address in one or more inter-eNB packets for communicating to the relay eNB 1706.
In one example, the disparate address can be received in one or more messages related to communicating inter-eNB packets with the relay eNB, as described. Thus, electrical component 1706 can specify the disparate address to attempt to avoid utilizing the gateway to communicate the inter-eNB packets. Moreover, logical grouping 1702 can include an electrical component for receiving the address from the gateway during an attachment procedure with the upstream eNB 1708. In addition, logical grouping 1702 can include an electrical component for transmitting the address to the upstream eNB during an attachment procedure 1710. In this regard, the upstream eNB can store a routing table with addresses of eNBs in the cluster to facilitate communicating inter-eNB packets thereto. Similarly, logical grouping 1702 can include an electrical component for storing the disparate address in a routing table with one or more parameters related to communicating with the relay eNB 1712. In this example, electrical component 1712 can also receive the disparate address from the relay eNB or upstream eNB (e.g., during an attachment procedure). Additionally, system 1700 can include a memory 1714 that retains instructions for executing functions associated with electrical components 1704, 1706, 1708, 1710, and 1712. While shown as being external to memory 1714, it is to be understood that one or more of electrical components 1704, 1706, 1708, 1710, and 1712 can exist within memory 1714.
With reference to FIG. 18, illustrated is a system 1800 that facilitates forwarding inter-eNB packets among eNBs in a cluster. For example, system 1800 can reside at least partially within a base station, mobile device, etc. It is to be appreciated that system 1800 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (e.g., firmware). System 1800 includes a logical grouping 1802 of electrical components that can act in conjunction. For instance, logical grouping 1802 can include an electrical component for receiving an address related to a packet obtained from a downstream relay eNB 1804. As described, the address can be received from a header of the packet.
Additionally, logical grouping 1802 can include an electrical component for locating the address in a routing table of addresses related to one or more relay eNBs in a cluster 1806. For example, electrical component 1806 can have also stored the address upon receipt from the one or more relay eNBs (e.g., in an attachment procedure or upon otherwise obtaining an address from the one or more relay eNBs). Moreover, logical grouping 1802 can include an electrical component for transmitting the packet to a disparate relay eNB in the cluster based at least in part on locating the address in the routing table 1808. As described, electrical component 1806 can store one or more parameters regarding communicating with the disparate relay eNB along with the address in the routing table. Electrical component 1808 can communicate with the disparate relay eNB according to the one or more parameters, as described. Additionally, system 1800 can include a memory 1810 that retains instructions for executing functions associated with electrical components 1804, 1806, and 1808. While shown as being external to memory 1810, it is to be understood that one or more of electrical components 1804, 1806, and 1808 can exist within memory 1810.
The various illustrative logics, logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but, in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Additionally, at least one processor may comprise one or more modules operable to perform one or more of the steps and/or actions described above.
Further, the steps and/or actions of a method or algorithm described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium may be coupled to the processor, such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. Further, in some aspects, the processor and the storage medium may reside in an ASIC. Additionally, the ASIC may reside in a user terminal In the alternative, the processor and the storage medium may reside as discrete components in a user terminal. Additionally, in some aspects, the steps and/or actions of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a machine readable medium and/or computer readable medium, which may be incorporated into a computer program product.
In one or more aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions, procedures, etc. may be stored or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection may be termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs usually reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
While the foregoing disclosure discusses illustrative aspects and/or embodiments, it should be noted that various changes and modifications could be made herein without departing from the scope of the described aspects and/or embodiments as defined by the appended claims. Furthermore, although elements of the described aspects and/or embodiments may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Additionally, all or a portion of any aspect and/or embodiment may be utilized with all or a portion of any other aspect and/or embodiment, unless stated otherwise. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim. Furthermore, although elements of the described aspects and/or aspects may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Additionally, all or a portion of any aspect and/or embodiment may be utilized with all or a portion of any other aspect and/or embodiment, unless stated otherwise.

Claims

1. A method, comprising:

transmitting a plurality of packets to an upstream evolved Node B (eNB) for communicating with a wireless network;

specifying an address received from a gateway for communicating with the gateway in a portion of the plurality of packets; and

specifying a disparate address for communicating with a disparate eNB in a disparate portion of the plurality of packets.

2. The method of claim 1, wherein the transmitting the plurality of packets to the upstream eNB includes transmitting the plurality of packets to a donor eNB, and the specifying the disparate address for communicating with the disparate eNB includes specifying the disparate address for communicating with a relay eNB in a cluster provided by the donor eNB.

3. The method of claim 1, wherein the disparate portion of the plurality of packets are inter-eNB packets.

4. The method of claim 3, wherein the inter-eNB packets include one or more packets related to handing over communications of a user equipment (UE).

5. The method of claim 1, further comprising receiving the address from the gateway through the upstream eNB during an attachment procedure with the upstream eNB.

6. The method of claim 5, further comprising transmitting the address to the upstream eNB during the attachment procedure.

7. The method of claim 1, further comprising receiving the disparate address from the disparate eNB or the upstream eNB.

8. The method of claim 7, further comprising storing the disparate address in a routing table with one or more parameters regarding communicating with the disparate eNB.

9. The method of claim 1, further comprising receiving a tunnel endpoint identifier (TEID) from the disparate eNB.

10. The method of claim 9, wherein the specifying the disparate address includes specifying the TEID in a tunneling protocol header associated with each of the disparate portion of the plurality of packets.

11. A wireless communications apparatus, comprising:

at least one processor configured to:

communicate a plurality of packets to an upstream evolved Node B (eNB) for providing to one or more components of a wireless network;

indicate an address assigned by a gateway for communicating with the gateway in a portion of the plurality of packets; and

specify a disparate address for communicating with a disparate eNB in a disparate portion of the plurality of packets; and

a memory coupled to the at least one processor.

12. The wireless communications apparatus of claim 11, wherein the upstream eNB is a donor eNB, and the disparate eNB is a relay eNB in a cluster including the donor eNB, the relay eNB, and the wireless communications apparatus.

13. The wireless communications apparatus of claim 11, wherein the disparate portion of the plurality of packets includes one or more inter-eNB packets.

14. The wireless communications apparatus of claim 11, wherein the at least one processor is further configured to receive the address from the gateway during an attachment procedure with the upstream eNB.

15. The wireless communications apparatus of claim 14, wherein the at least one processor is further configured to transmit the address to the upstream eNB during the attachment procedure.

16. The wireless communications apparatus of claim 11, wherein the at least one processor is further configured to:

receive the disparate address from the disparate eNB or the upstream eNB; and

store the disparate address in a routing table with one or more parameters regarding communicating with the disparate eNB.

17. The wireless communications apparatus of claim 11, wherein the at least one processor is further configured to receive a tunnel endpoint identifier (TEID) from the disparate eNB, and the disparate address is the TEID.

18. An apparatus, comprising:

means for communicating with an upstream evolved Node B (eNB) to access a gateway in a wireless network based at least in part on an address received from the gateway; and

means for indicating a disparate address in one or more inter-eNB packets for communicating to a relay eNB, wherein the means for communicating with the upstream eNB communicates the one or more inter-eNB packets to the upstream eNB.

19. The apparatus of claim 18, further comprising means for receiving the address from the gateway during an attachment procedure with the upstream eNB.

20. The apparatus of claim 19, further comprising means for transmitting the address to the upstream eNB during the attachment procedure.

21. The apparatus of claim 18, further comprising means for storing the disparate address in a routing table with one or more parameters related to communicating with the relay eNB.

22. A computer program product, comprising:

a computer-readable medium comprising:

code for causing at least one computer to communicate a plurality of packets to an upstream evolved Node B (eNB) for providing to one or more components of a wireless network;

code for causing the at least one computer to indicate an address assigned by a gateway for communicating with the gateway in a portion of the plurality of packets; and

code for causing the at least one computer to specify a disparate address for communicating with a disparate eNB in a disparate portion of the plurality of packets.

23. The computer program product of claim 22, wherein the upstream eNB is a donor eNB, and the disparate eNB is a relay eNB in a cluster including the donor eNB and the relay eNB.

24. The computer program product of claim 22, wherein the disparate portion of the plurality of packets includes one or more inter-eNB packets.

25. The computer program product of claim 22, wherein the computer-readable medium further comprises code for causing the at least one computer to receive the address from the gateway during an attachment procedure with the upstream eNB.

26. The computer program product of claim 25, wherein the computer-readable medium further comprises code for causing the at least one computer to transmit the address to the upstream eNB during the attachment procedure.

27. The computer program product of claim 22, wherein the computer-readable medium further comprises:

code for causing the at least one computer to receive the disparate address from the disparate eNB or the upstream eNB; and

code for causing the at least one computer to store the disparate address in a routing table with one or more parameters regarding communicating with the disparate eNB.

28. The computer program product of claim 22, wherein the computer-readable medium further comprises code for causing the at least one computer to receive a tunnel endpoint identifier (TEID) from the disparate eNB, and the disparate address is the TEID.

29. An apparatus, comprising:

a communicating component that transmits one or more packets to an upstream evolved Node B (eNB) for providing to a gateway in a wireless network based at least in part on an address received from the gateway; and

an address assigning component that specifies a disparate address in one or more inter-eNB packets for communicating to a relay eNB, wherein the communicating component transmits the one or more inter-eNB packets to the upstream eNB.

30. The apparatus of claim 29, further comprising an address receiving component that obtains the address from the gateway during an attachment procedure with the upstream eNB.

31. The apparatus of claim 30, further comprising an address providing component that transmits the address to the upstream eNB during the attachment procedure.

32. The apparatus of claim 29, further comprising a routing table component that stores the disparate address in a routing table with one or more parameters related to communicating with the relay eNB.

33. A method, comprising:

receiving an address related to a packet obtained from a downstream relay evolved Node B (eNB);

locating the address in a routing table of addresses related to one or more relay eNBs in a cluster; and

transmitting the packet to a disparate relay eNB in the cluster based at least in part on the locating the address in the routing table of addresses.

34. The method of claim 33, further comprising:

receiving the address from the disparate relay eNB during an attachment procedure with the disparate relay eNB; and

storing the address in the routing table of addresses along with one or more parameters related to communicating with the disparate relay eNB.

35. The method of claim 33, further comprising:

receiving a disparate packet from the downstream relay eNB including a disparate address related to a gateway; and

transmitting the disparate packet to the gateway based at least in part on the disparate address.

36. The method of claim 33, wherein the transmitting the packet to the disparate relay eNB includes transmitting an inter-eNB packet to the disparate relay eNB.

37. The method of claim 33, further comprising receiving a tunnel endpoint identifier (TEID) from the disparate relay eNB and an association of the TEID to a bearer with the disparate relay eNB.

38. The method of claim 37, further comprising receiving a disparate packet from the downstream relay eNB including a tunneling protocol header comprising the TEID.

39. The method of claim 38, further comprising forwarding the disparate packet to the disparate relay eNB over the bearer based at least in part on the TEID in the tunneling protocol header.

40. A wireless communications apparatus, comprising:

at least one processor configured to:

determine an address related to a packet received from a downstream relay evolved Node B (eNB);

discern the address is in a routing table comprising one or more address corresponding to one or more relay eNBs in a cluster; and

communicate the packet to a disparate relay eNB in the cluster based at least in part on discerning the address is in the routing table; and

a memory coupled to the at least one processor.

41. The wireless communications apparatus of claim 40, wherein the at least one processor is further configured to:

obtain the address from the disparate relay eNB during an attachment procedure with the disparate relay eNB; and

store the address in the routing table with one or more parameters related to communicating with the disparate relay eNB.

42. The wireless communications apparatus of claim 40, wherein the at least one processor is further configured to:

obtain a disparate packet from the downstream relay eNB including a disparate address related to a gateway; and

transmit the disparate packet to the gateway based at least in part on the disparate address.

43. The wireless communications apparatus of claim 42, wherein the packet is an inter-eNB packet.

44. The wireless communications apparatus of claim 40, wherein the at least one processor is further configured to receive a tunnel endpoint identifier (TEID) and an associated bearer identifier from the disparate relay eNB.

45. The wireless communications apparatus of claim 44, wherein the at least one processor is further configured to forward a disparate packet received from the downstream relay eNB to the disparate relay eNB over a bearer corresponding to the associated bearer identifier based at least in part on locating the TEID in the disparate packet.

46. An apparatus, comprising:

means for receiving an address related to a packet obtained from a downstream relay evolved Node B (eNB);

means for locating the address in a routing table of addresses related to one or more relay eNBs in a cluster; and

means for transmitting the packet to a disparate relay eNB in the cluster based at least in part on locating the address in the routing table of addresses.

47. The apparatus of claim 46, wherein the means for receiving the address receives the address during an attachment procedure with the disparate relay eNB, and the means for locating the address in the routing table of addresses stores the address in the routing table of addresses with one or more parameters related to communicating with the disparate relay eNB.

48. The apparatus of claim 46, wherein the means for transmitting the packet receives a disparate packet from the downstream relay eNB including a disparate address related to a gateway, and the means for transmitting the packet transmits the disparate packet to the gateway based at least in part on the disparate address.

49. A computer program product, comprising:

a computer-readable medium comprising:

code for causing at least one computer to determine an address related to a packet received from a downstream relay evolved Node B (eNB);

code for causing the at least one computer to discern the address is in a routing table comprising one or more address corresponding to one or more relay eNBs in a cluster; and

code for causing the at least one computer to communicate the packet to a disparate relay eNB in the cluster based at least in part on discerning the address is in the routing table.

50. The computer program product of claim 49, wherein the computer-readable medium further comprises:

code for causing the at least one computer to obtain the address from the disparate relay eNB during an attachment procedure with the disparate relay eNB; and

code for causing the at least one computer to store the address in the routing table with one or more parameters related to communicating with the disparate relay eNB.

51. The computer program product of claim 49, wherein the computer-readable medium further comprises:

code for causing the at least one computer to obtain a disparate packet from the downstream relay eNB including a disparate address related to a gateway; and

code for causing the at least one computer to transmit the disparate packet to the gateway based at least in part on the disparate address.

52. The computer program product of claim 51, wherein the packet is an inter-eNB packet.

53. The computer program product of claim 49, wherein the computer-readable medium further comprises code for causing the at least one computer to receive a tunnel endpoint identifier (TEID) and an associated bearer identifier from the disparate relay eNB.

54. The computer program product of claim 53, wherein the computer-readable medium further comprises code for causing the at least one computer to forward a disparate packet received from the downstream relay eNB to the disparate relay eNB over a bearer corresponding to the associated bearer identifier based at least in part on locating the TEID in the disparate packet.

55. An apparatus, comprising:

a routing parameter receiving component that obtains an address related to a packet obtained from a downstream relay evolved Node B (eNB);

a routing table component that locates the address in a routing table of addresses related to one or more relay eNBs in a cluster; and

a communicating component that transmits the packet to a disparate relay eNB in the cluster based at least in part on locating the address in the routing table of addresses.

56. The apparatus of claim 55, wherein the routing parameter receiving component obtains the address during an attachment procedure with the disparate relay eNB, and the routing table component stores the address in the routing table of addresses with one or more parameters related to communicating with the disparate relay eNB.

57. The apparatus of claim 55, wherein the communicating component receives a disparate packet from the downstream relay eNB including a disparate address related to a gateway and transmits the disparate packet to the gateway based at least in part on the disparate address.