CELL RELAY MOBILITY PROCEDURES

[0001] The present Application for Patent claims priority to Provisional Application No. 61/108,287 entitled “CELL RELAY BASE STATION FOR LTE” filed Oct. 24, 2008, and assigned to the assignee hereof and hereby expressly incorporated by reference herein.

[0002] 1. Field

[0003] The following description relates generally to wireless communications, and more particularly to wireless network mobility procedures for cell relays and other devices.

[0004] 2. Background

[0005] 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.

[0006] 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.

[0007] Cell relays can be provided to expand network capacity and coverage area by facilitating communication between mobile devices and access points. For example, a cell relay can establish a backhaul link with a donor access point, which can provide access to a number of cell relays, and the cell relay can establish an access link with one or more mobile devices or additional cell relays. To mitigate modification to backend core network components, communication interfaces, 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 cell relays for communicating to the mobile devices.

[0008] 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.

[0009] In accordance with one or more aspects and corresponding disclosure thereof, various aspects are described in connection with facilitating wireless network mobility for cell relays and/or devices communicating therewith. In particular, a cell relay can reselect to one or more disparate cell relays in a cluster provided by a donor node. In this example, the cell relay can perform handover to the one or more disparate cell relays using similar handover procedures as user equipment (UE), and upstream cell relays and/or donor nodes can update routing tables to associate the cell relay with the one or more disparate downstream cell relays. In another example, where the cell relay reselects to one or more disparate cell relays in a disparate cluster provided by a disparate donor node, the cell relay can additionally perform procedures for requesting/receiving a new identifier from the disparate donor node and/or one or more intermediary cell relays in the disparate cluster. Also in this example, however, downstream cell relays connected to the cell relay can request/receive a new identifier from the disparate donor node and/or intermediary cell relays. Similarly, upstream cell relays and donor node can update routing tables with the new identifiers assigned to the cell relay and its downstream cell relays where present.

[0010] According to related aspects, a method is provided that includes communicating with a relay eNB to receive access to a wireless network and establishing a connection with a disparate relay eNB to facilitate reselecting the disparate relay eNB where the disparate relay eNB and relay eNB communicate with a same donor eNB to provide wireless network access. The method further includes transmitting a bearer list update message to the disparate relay eNB comprising an identifier previously assigned by the donor eNB.

[0011] Another aspect relates to a wireless communications apparatus. The wireless communications apparatus can include at least one processor configured to communicate with a relay eNB to receive access to a wireless network and initiate reselection to a disparate relay eNB that communicates with a same donor eNB as the relay eNB. The at least one processor is further configured transmit a bearer list update message to the disparate relay eNB comprising an identifier of the wireless communications apparatus assigned by the donor eNB. The wireless communications apparatus also comprises a memory coupled to the at least one processor.

[0012] Yet another aspect relates to an apparatus. The apparatus includes means for initiating reselection from a relay eNB to a disparate relay eNB that utilizes a same donor eNB to provide access to a wireless network. The apparatus also means for generating a bearer list update message comprising an identifier of the apparatus and transmitting the bearer list update message during reselection.

[0013] 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 with a relay eNB to receive access to a wireless network. The computer-readable medium can also comprise code for causing the at least one computer to establish a connection with a disparate relay eNB to facilitate reselecting the disparate relay eNB where the disparate relay eNB and the relay eNB communicate with a same donor eNB to provide wireless network access and code for causing the at least one computer to transmit a bearer list update message to the disparate relay eNB comprising an identifier previously assigned by the donor eNB.

[0014] Moreover, an additional aspect relates to an apparatus including a reselection initiating component that initializes reselection from a relay eNB to a disparate relay eNB that utilizes a same donor eNB to provide access to a wireless network. The apparatus can further include an update message generating component that creates a bearer list update message comprising an identifier of the apparatus and transmits the bearer list update message during reselection.

[0015] According to another aspect, a method is provided that includes receiving a bearer list update message from a relay eNB during reselection for the relay eNB. The method also includes determining an identifier of the relay eNB from the bearer list update message and associating the identifier of the relay eNB to a bearer identifier of a next downstream relay eNB in a communication path to the relay eNB in a routing table.

[0016] Another aspect relates to a wireless communications apparatus. The wireless communications apparatus can include at least one processor configured to obtain a bearer list update message from a relay eNB during reselection for the relay eNB and discern an identifier of the relay eNB from the bearer list update message. The at least one processor is further configured to store the identifier of the relay eNB with a bearer identifier of a next downstream relay eNB in a communication path to the relay eNB in a routing table. The wireless communications apparatus also comprises a memory coupled to the at least one processor.

[0017] Yet another aspect relates to an apparatus. The apparatus includes means for receiving a bearer list update message from a relay eNB during reselection for the relay eNB and means for determining an identifier of the relay eNB from the bearer list update message. The apparatus also includes means for storing an association between the identifier of the relay eNB and a bearer identifier of a next downstream relay eNB in a communication path to the relay eNB in a routing table.

[0018] 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 receive a bearer list update message from a relay eNB during reselection for the relay eNB and code for causing the at least one computer to determine an identifier of the relay eNB from the bearer list update message. The computer-readable medium can also comprise code for causing the at least one computer to associate the identifier of the relay eNB to a bearer identifier of a next downstream relay eNB in a communication path to the relay eNB in a routing table.

[0019] Moreover, an additional aspect relates to an apparatus including an update message receiving component that obtains a bearer list update message from a relay eNB during reselection for the relay eNB. The apparatus can further include a parameter parsing component that determines an identifier of the relay eNB from the bearer list update message and a routing table component that stores an association between the identifier of the relay eNB and a bearer identifier of a next downstream relay eNB in a communication path to the relay eNB in a routing table.

[0020] In another aspect, a method is provided that includes communicating with a relay eNB to receive access to a wireless network and establishing a connection with a disparate relay eNB to facilitate reselecting the disparate relay eNB where the disparate relay eNB and relay eNB communicate with disparate donor eNBs to provide wireless network access. The method also includes transmitting an identifier request to the disparate relay eNB to facilitate assignment of a unique identifier at the disparate donor eNB.

[0021] Another aspect relates to a wireless communications apparatus. The wireless communications apparatus can include at least one processor configured to receive wireless network access from a relay eNB and initiate reselection to a disparate relay eNB that communicates with a disparate donor eNB than the relay eNB to provide wireless network access. The at least one processor is further configured to transmit an identifier request to the disparate relay eNB to facilitate assigning a unique identifier to the wireless communications apparatus by the disparate donor eNB. The wireless communications apparatus also comprises a memory coupled to the at least one processor.

[0022] Yet another aspect relates to an apparatus. The apparatus includes means for initiating reselection from a relay eNB to a disparate relay eNB that utilizes a disparate donor eNB to provide access to a wireless network than the relay eNB. The apparatus also includes means for transmitting an identifier request to facilitate assignment of a unique identifier at the disparate donor eNB.

[0023] 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 with a relay eNB to receive access to a wireless network. The computer-readable medium can also comprise code for causing the at least one computer to establish a connection with a disparate relay eNB to facilitate reselecting the disparate relay eNB where the disparate relay eNB communicates with a disparate donor eNB to provide wireless network access than the relay eNB and code for causing the at least one computer to transmit an identifier request to the disparate relay eNB to facilitate assignment of a unique identifier at the disparate donor eNB.

[0024] Moreover, an additional aspect relates to an apparatus including a reselection initiating component that initializes a reselection from a relay eNB to a disparate relay eNB that utilizes a disparate donor eNB to provide access to a wireless network than the relay eNB. The apparatus can further include a requesting component that transmits an identifier request to facilitate assignment of a unique identifier at the disparate donor eNB.

[0025] In additional aspects, a method is provided that includes receiving an identifier request from a relay eNB during reselection for the relay eNB. The method also includes obtaining an identifier for the relay eNB and associating the identifier of the relay eNB to a bearer identifier of a next downstream relay eNB in a communication path to the relay eNB in a routing table.

[0026] Another aspect relates to a wireless communications apparatus. The wireless communications apparatus can include at least one processor configured to receive an identifier request from a relay eNB during reselection for the relay eNB. The at least one processor is further configured to obtain an identifier for the relay eNB and associate the identifier of the relay eNB in a routing table along with a bearer identifier of a next downstream relay eNB in a communication path to the relay eNB. The wireless communications apparatus also comprises a memory coupled to the at least one processor.

[0027] Yet another aspect relates to an apparatus. The apparatus includes means for receiving an identifier request from a relay eNB during reselection for the relay eNB and means for obtaining an identifier for the relay eNB. The apparatus also includes means for storing an association between the identifier of the relay eNB and a bearer identifier of a next downstream relay eNB in a communication path to the relay eNB in a routing table.

[0028] 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 receive an identifier request from a relay eNB during reselection for the relay eNB and code for causing the at least one computer to obtain an identifier for the relay eNB. The computer-readable medium can also comprise code for causing the at least one computer to associate the identifier of the relay eNB to a bearer identifier of a next downstream relay eNB in a communication path to the relay eNB in a routing table.

[0029] Moreover, an additional aspect relates to an apparatus including an identifier request receiving component that obtains an identifier request from a relay eNB during reselection for the relay eNB and an identifier receiving component that obtains an identifier for the relay eNB. The apparatus can further include a routing table component that stores an association between the identifier of the relay eNB and a bearer identifier of a next downstream relay eNB in a communication path to the relay eNB in a routing table.

[0030] 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.

[0050] 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.

[0051] 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.

[0052] 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, or some other terminology.

[0053] 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.

[0054] 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.

[0055] 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.

[0056] 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.

[0057] 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.

[0058] 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) as would a UE in regular LTE configurations. In this regard, donor eNB 102 can be a regular LTE eNB requiring no changes at the link layer or related interface (e.g., E-UTRA-Uu) to support the relay eNB 104. In addition, relay eNB 104 can appear to UE 110 as a regular eNB at the link layer, such that no changes are required for UE 110 to connect to relay eNB 104 at the link layer, 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.

[0059] With respect to transport layer communications, transport protocols related to relay eNB 108 or UE 110 communications can terminate at the donor eNB 102, referred to as cell relay functionality, since the relay eNB 104 is like a cell of the donor eNB 102. For example, in a cell relay configuration, donor eNB 102 can receive communications for the relay eNB 104 from the core network 106, terminate the transport protocol, and forward the communications to the relay eNB 104 over a disparate transport layer keeping the application layer substantially intact. It is to be appreciated that the forwarding transport protocol type can be the same as the terminated transport protocol type, but is a different transport layer established with the relay eNB 104.

[0060] Relay eNB 104 can determine a relay eNB or UE related to the communications, and provide the communications to the relay eNB or UE (e.g., based on an identifier thereof within the communications). Similarly, donor eNB 102 can terminate the transport layer protocol for communications received from relay eNB 104, translate the communications to a disparate transport protocol, and transmit the communications over the disparate transport protocol to the core network 106 with the application layer intact for relay eNB 104 as a cell relay. In these examples, where relay eNB 104 is communicating with another relay eNB, the relay eNB 104 can support application protocol routing to ensure communications reach the correct relay eNB.

[0061] Moreover, application layer protocols can terminate at upstream eNBs. Thus, for example, application layer protocols for relay eNB 108 and UE 110 can terminate at relay eNB 104, and similarly for relay eNB 104 can terminate at donor eNB 102. The transport and application layer protocols, for example, can relate to S1-U, S1-MME, and/or X2 interfaces. S1-U interface can be utilized to communicate in a data plane between a node and a serving gateway (not shown) of the core network 106. S1-MME interface can be utilized for control plane communications between a node and a mobility management entity (MME) (not shown) of the core network 106. X2 interface can be utilized for communications between eNBs. In addition, for example, donor eNB 102 can communicate with other relay eNBs to allow communications therebetween over the access network (e.g., relay eNB 104 can communicate with one or more additional relay eNBs connected to donor eNB 102).

[0062] According to an example, relay eNBs, such as relay eNB 108, can reselect various relay eNBs and/or donor eNBs (not shown) to retain connection to core network 106. For example, relay eNB 108 can reselect the various relay eNBs and/or donor eNBs as it travels throughout a core network 106 coverage area to facilitate seamless network access. In one example, relay eNB 108 can reselect intra-cluster, which can refer to reselecting to a disparate relay eNB in the cluster provided by donor eNB 102 (not shown) and/or donor eNB 102 itself. In this example, relay eNB 108 can perform reselection to the disparate relay eNB using a similar procedure as a UE communicating with core network 106 (e.g., UE 110), where core network 106 is a 3GPP LTE or similar evolved 3GPP network. In addition, however, relay eNB 108 can perform additional steps in the reselection to facilitate providing relevant information to one or more downstream or upstream nodes for the reselection.

[0063] For example, donor eNB 102 can assign an identifier (e.g., a tunnel endpoint identifier (TEID), etc.), or a portion thereof, to relay eNB 108 upon relay eNB 108 attaching to core network 106. Donor eNB 102 can additionally store the identifier, or portion thereof, in a routing table along with an identifier (e.g., a cell radio network temporary identifier (C-RNTI), etc.) of a next downstream relay eNB in the communication path to relay eNB 108, which can be relay eNB 104, in this example, to facilitate subsequent packet routing among the various eNBs. Similarly, relay eNB 104 can store the identifier, or portion, with an identifier of a next downstream relay eNB, which can be relay eNB 108 in this example. It is to be appreciated that other intermediary relay eNBs can exist in the communication path between relay eNB 108 and donor eNB 102, and the intermediary relay eNBs can similarly store an association between the identifier of relay eNB 108 assigned by donor eNB 102 and a radio identifier of the next downstream relay eNB.

[0064] In this regard, during intra-cluster reselection, relay eNB 108 can inform the target relay eNB (e.g., the relay eNB to which relay eNB 108 desires to connect) of the reselection by providing a bearer list update message and can include its identifier assigned by donor eNB 102 in the bearer list update message. The target relay eNB (not shown) can update its routing table with an entry associating the received identifier along with a radio identifier of relay eNB 108 and can transmit the bearer list update message to an upstream relay eNB in the communications path to donor eNB 102 or donor eNB 102, where no other relay eNBs are present in the communications path. Where an entry already exists for relay eNB 108 in its routing table, the target relay eNB can update the entry to reflect the appropriate downstream relay eNB radio identifier where it has changed. It is to be appreciated that intermediary relay eNBs can similarly store the identifier for relay eNB 108 with a radio identifier of a next downstream relay eNB from which the bearer list update message is received and forward the message to the next eNB in the communication path. Donor eNB 102, upon receiving the bearer list update message, can similarly update its routing table to modify the current entry for relay eNB 108 to reflect the appropriate next downstream relay eNB where it has changed.

[0065] In addition, where relay eNB 108 performs an inter-cluster reselection, which can refer to a reselection to a relay eNB or donor eNB in a disparate cluster (not shown), additional procedures can be performed as part of the reselection. For example, relay eNB 108 can require a new identifier for the new cluster, as can any downstream relay eNBs (not shown) connected to relay eNB 108 (e.g., directly or through one or more intermediary relay eNBs). Thus, in one example, relay eNB 108 can collect parameters regarding its downstream relay eNBs upon initiating a reselection procedure, and can transmit the parameters to core network 106. Core network 106 can initiate bearer setup procedures, and the target donor eNB (not shown) can assign an identifier, or portion, to the relay eNB 108, as well as the downstream relay eNBs under relay eNB 108.

[0066] The target donor eNB can store the identifier in a routing table along with a next downstream relay eNB in the communication path to relay eNB 108 and can additionally transmit the various identifiers to the next downstream relay eNB. The next downstream relay eNB can store the various identifiers in its routing table along with a next downstream relay eNB identifier in the communication path to relay eNB 108, if present, and so on. Once the identifiers reach relay eNB 108, it can update the identifiers in its routing table to reflect the newly assigned identifiers and can forward the identifiers to the respective next downstream relay eNB in the respective communication paths. The next downstream relay eNBs can perform similar updating procedures.

[0067] In another example, as part of a procedure for inter-cluster reselection, relay eNB 108 can request an identifier from the target donor eNB during reselection without gathering information of the connected downstream relay eNBs. Upon performing reselection, relay eNB 108 can inform the connected downstream relay eNBs, which can similarly perform reselection procedures requesting new identifier from the target donor eNB. In yet another example, as part of a procedure for inter-cluster reselection, relay eNB 108 can release its radio connection with all connected downstream relay eNBs (and UEs if present). In this example, the previously connected downstream relay eNBs and UEs (and/or relay eNB 108) can perform network attachment procedures to re-attach to the network via target donor eNB receiving a new identifier therefrom.

[0068] Turning now to FIG. 2, a wireless communication system 200 is illustrated that facilitates intra-cluster cell relay reselection. System 200 includes a donor eNB 102 that provides one or more relay eNBs, such as relay eNBs 104 and 202, with access to a core network 106. Similarly, relay eNB 104 can provide one or more disparate relay eNBs, such as relay eNB 108, with access to the core network 106 via donor eNB 102, and relay eNB 108 can similarly provide core network 106 access to relay eNBs 204 and 206. 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.

[0069] Donor eNB 102 can additionally provide an access link for relay eNBs 104 and 202, which can also be wired or wireless, LTE or other technologies, as described. Similarly, relay eNBs 104 and 202 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, as described, which can be a wired or wireless LTE or other technology link. Relay eNB 108 can provide similar access links to relay eNBs 204 and 206. Donor eNB 102 can connect to the core network 106 over a disparate backhaul link technology.

[0070] According to an example, relay eNB 108 can initiate intra-cluster reselection to relay eNB 202, which communicates with the same donor eNB 102 as relay eNB 104. This can be based on a higher level of service provided by relay eNB 202, signal to noise ratio (SNR) over a certain threshold, and/or the like. Indeed, the reselection can be similar to and performed in similar cases as UE reselection in core network 106. In this regard, in one example, relay eNB 108 (and/or relay eNBs 104 and 202) can be mobile such that they travel throughout a core network 106 coverage area.

[0071] As described, relay eNB 108 can perform similar reselection procedures as a UE to handover S1 interface to relay eNB 202. In addition, however, relay eNB 108 can perform specific steps to ensure proper packet routing to/from core network 106 through the various donor and relay nodes. In an example, relay eNB 108, upon initiating reselection to relay eNB 202, can transmit a bearer list update message to relay eNB 202 indicating bearer and/or identifier information for relay eNB 108, as well as relay eNBs 204 and 206 (and any relay eNBs under relay eNBs 204 and 206, for example). Relay eNB 202 can update its routing table by adding an entry for an identifier of relay eNB 108 in the bearer list update message (e.g., an identifier previously assigned by donor eNB 102 such as a TEID or portion thereof) along with a bearer identifier for relay eNB 108. Relay eNB 202 can additionally update its routing table adding entries for identifiers of relay eNBs 204 and 206 along with an association to the bearer identifier for relay eNB 108.

[0072] Relay eNB 202 can additionally forward the bearer list update message to donor eNB 102 (or one or more intermediary relay eNBs, where present). Donor eNB 102 can update its routing table by modifying its entry for relay eNB 108, which associates the assigned identifier for relay eNB 108 with a bearer identifier for relay eNB 104, to instead associate the assigned identifier with a bearer identifier for relay eNB 202. Likewise, donor eNB 102 can update its routing table to associate identifiers of relay eNBs 204 and 206 with relay eNB 202 (instead of relay eNB 104). Thus, upon receiving downlink packets from core network 106 comprising an identifier for relay eNB 108 or relay eNBs 204 or 206, donor eNB 102 can consult its routing table to determine to forward the packet to relay eNB 202 based on the associated bearer identifier. Relay eNB 202, upon receiving the packet, can consult its routing table and determine to forward the packet to relay eNB 108, and so on.

[0073] Referring now to FIG. 3, an example wireless communication system 300 that facilitates performing intra-cluster reselection for cell relays is illustrated. System 300 includes a donor eNB 102 that provides relay eNBs 104 and 202 with access to core network 106. Additionally, as described, relay eNB 104 can provide relay eNB 108 with access to the core network 106 through the donor eNB 102. Moreover, for example, there can be multiple relay eNBs 104 between the donor eNB 102 and relay eNB 108. In addition, it is to be appreciated that relay eNB 108 (and relay eNBs 202, 204, and 206) can comprise the components of relay eNB 202 (and/or vice versa) to provide similar functionality, in one example, for reselection. Moreover, donor eNB 102 can be a macrocell access point, femtocell access point, picocell access point, mobile base station, and/or the like. Relay eNBs 104 (and relay eNBs 108, 202, 204, and 206) can similarly be mobile or stationary relay nodes that communicate with donor eNB 102 (and relay eNB 104) over a wireless or wired backhaul, as described.

[0074] Donor eNB 102 comprises an update message receiving component 302 that obtains a bearer list update message from a downstream relay eNB, a parameter parsing component 304 that extracts one or more parameters regarding downstream relay eNBs from the bearer list update message, a routing table component 306 that stores identifiers of relay eNBs (which can be assigned by donor eNB 102) along with bearer identifiers for next downstream relay eNBs in the communication path to the relay eNBs, and a packet routing component 308 that forwards packets received from core network 106 to next downstream relay eNBs based on matching an identifier in the packet to an identifier stored by the routing table component 306.

[0075] Relay eNB 202 comprises an update message receiving component 310 that obtains a bearer list update message from a downstream relay eNB and forwards the message to an upstream eNB, a parameter parsing component 312 that obtains one or more parameters regarding downstream relay eNBs from the bearer list update message, a routing table component 314 that stores identifiers of relay eNBs (which can be assigned by donor eNB 102) along with bearer identifiers for next downstream relay eNBs in the communication path to the relay eNBs, and a packet routing component 316 that forwards packets received from an upstream eNB to next downstream relay eNBs based on matching an identifier in the packet to an identifier stored by the routing table component 314.

[0076] Relay eNB 108 includes a reselection initiating component 318 that can begin a procedure to reselect to a disparate relay eNB, a downstream parameter gathering component 320 that obtains one or more parameters, such as evolved packet system (EPS) bearer identifiers, assigned identifiers, bearer quality of service (QoS) parameters, etc., of downstream relay eNBs, an update message generating component 322 that creates a bearer list update message comprising the downstream relay eNB parameters and/or parameters related to relay eNB 108, and a packet routing component 324 that forwards packets received from an upstream eNB to relay eNBs 204 and 206, which can be based on an identifier in the packets and a routing table (not shown), as described with respect to donor eNB 102 and relay eNB 202.

[0077] According to an example, relay eNB 108 can communicate with donor eNB 102 via relay eNB 104. Thus, donor eNB 102 can have assigned an identifier, such as a TEID or other relay identifier, to relay eNB 108, and routing table component 306 can have stored an association between the assigned identifier and a bearer identifier of the next downstream relay eNB in the communication path to relay eNB 108, which is relay eNB 104. Reselection initiating component 318, as described, can initiate reselection to relay eNB 202 from relay eNB 104. In this regard, reselection initiating component 318 can perform UE type reselection procedures to handover S1 interface to relay eNB 202. In addition, as part of the reselection, downstream parameter gathering component 320 can obtain one or more parameters related to relay eNBs 204 and 206, such as bearer identifiers, QoS parameters, eNB global identifiers (EGI), identifiers assigned by donor eNB 102, etc. Update message generating component 322 can compose a bearer list update message that includes at least a portion of the parameters for relay eNBs 204 and 206 and transmit the bearer list update message to its upstream target eNB, which is relay eNB 202, in this example.

[0078] Update message receiving component 310 can obtain the bearer list update message, and parameter parsing component 312 can extract one or more parameters from the bearer list update message related to downstream relay eNBs. For example, parameter parsing component 312 can determine an identifier for each downstream relay eNB (e.g., relay eNB 108 and/or relay eNBs 202 and 204) assigned by donor eNB 102. Routing table component 314 can store an association between the assigned identifiers and a bearer identifier for relay eNB 108, which indicates the next downstream relay eNB in the communication path to the related relay eNB. Update message receiving component 310 can forward the bearer list update message to donor eNB 102.

[0079] Similarly, update message receiving component 302 can obtain the bearer list update message, and parameter parsing component 304 can extract one or more parameters from the bearer list update message related to the downstream relay eNBs. For example, parameter parsing component 304 can determine an identifier for each downstream relay eNB (e.g., relay eNB 108 and/or relay eNBs 202 and 204) assigned by donor eNB 102. Routing table component 306 can update stored associations for the assigned identifiers to associate to a bearer identifier of relay eNB 202 (e.g., instead of relay eNB 104), which indicates the next downstream relay eNB in the communication path to the related relay eNB. Update message receiving component 302 can additionally transmit an RRC connection reconfiguration message to relay eNB 104 in response to receiving the bearer list update message, and update message receiving component 310 can forward the RRC connection reconfiguration message to relay eNB 108. Reselection initiating component 318 can receive the RRC connection reconfiguration message and can modify a radio bearer. Reselection initiating component 318 can further transmit an RRC connection reconfiguration complete message to relay eNB 104, as described further below. It is to be appreciated other upstream intermediary relay eNBs in the communications path between relay eNB 202 and donor eNB 102 can similarly update routing table entries (where present), since the intermediary relay eNBs can have a stored association for the identifiers generated by donor eNB 102.

[0080] In this regard, routing table components 306 and 314 can have updated associations as a result of the reselection to relay eNB 202. Thus, upon receiving packets from core network 106 with the identifier of relay eNB 108, 204, or 206, packet routing component 308 can determine the identifier in the packet and discern a next downstream relay eNB based on locating a stored association between the identifier in routing table component 306. As described, for relay eNBs 108, 204, and 206, the routing table entry can relate to relay eNB 202, and the packet routing component 308 can accordingly forward the packet. Similarly, upon relay eNB 202 receiving the packet, packet routing component 316 can consult routing table component 314 to determine the next downstream relay eNB, which is relay eNB 108, as described, according to the new entry inserted during reselection. Thus, packet routing component 316 can forward the packet to relay eNB 108. Once relay eNB 108 receives the packet, packet routing component 324 can forward the packet, if applicable, to the appropriate relay eNB using the same associations as it did before reselection (e.g., using a similar routing table, etc.).

[0081] Referring to FIG. 4, an example wireless communication system 400 that facilitates performing intra-cluster cell relay reselection is illustrated. System 400 includes a handover relay eNB 402 that communicates with a source relay eNB 404 for access to donor eNB 408. In addition, system 400 includes a target relay eNB 406 to which handover relay eNB 402 reselects, as depicted. As shown, a UE part of handover relay eNB 402 can perform S1 reselection 410 to target relay eNB 406. This can include, for example, handing over the S1 communication interface and related information to facilitate communicating with target relay eNB 406 using the interface. Source relay eNB 404 can perform a bearer resource release 412 to free communication resource previously utilized by handover relay eNB 402. In addition, source relay eNB 404 can transmit a bearer list update message 414 to donor eNB 408 indicating one or more communication resources donor eNB 408 can release in view the reselection procedure by handover relay eNB 402. Donor eNB 408 can release the resources 416. In one example, the bearer list update message can have a format similar to the following.

BearerListUpdate ::= SEQUENCE {
	rrc-TransactionIdentifier	RRC-TransactionIdentifier,
	criticalExtensions	CHOICE {
	bearerListUpdate-r10	BearerListUpdate-r10-IEs,
	criticalExtensions	SEQUENCE { }
	}
}
BearerListUpdate-r10-IEs ::= SEQUENCE {
	cenb-Identity	ENB-Identity,
	enb-Identity	ENB-Identity,
	enbList ::=  SEQUENCE (SIZE (1 .. noofeNBs)) of SEQUENCE{
	enb-Identity	ENB-Identity,
	ueList ::=  SEQUENCE (SIZE (1 .. noofUEs)) of SEQUENCE{
	enb-UE-S1AP-Identity	ENB-UE-S1AP-Identity,
	bearerList ::= SEQUENCE (SIZE (1 .. noofSAEbearers)) of
SEQUENCE{
	bearerToBeReleasedListItemIEs	BearerListItemIEs
	OPTIONAL,
	bearerToBeAddedListItemIEs	BearerListItemIEs
	OPTIONAL,
	...
	}
	}
	}
}

where the BearerListltemlE can have a format similar to the following.

BearerListItemIEs ::=  SEQUENCE {
	sae-Bearer-Identity	SAE-Bearer-Identity,
	sl-DL-TEID	TEID,
	sae-BearerLevelQoSParametersSAE-BearerLevelQoSParameters
	OPTIONAL,
	...
}

[0082] As described, handover relay eNB 402 can transmit a bearer list update message 418 to target relay eNB 406, which can include parameters regarding handover relay eNB 402 and/or one or more downstream relay eNBs connected directly or indirectly thereto, such as EPS bearer identifiers, QoS parameters, assigned identifiers of the handover relay eNB and/or related downstream relay eNBs, etc. Target relay eNB 406 can perform admission control and routing table update 420. Admission control can refer to allocating resources according to various parameters regarding a related device. In addition, routing table update, as described, can include adding an entry for an assigned identifier of handover relay eNB 402 and/or downstream relay eNBs directly or indirectly connected thereto and a bearer identifier for handover relay eNB 402. Target relay eNB 406 can forward the bearer list update 422 to donor eNB 408. Donor eNB 408 can similarly perform admission control and routing table update 424. Routing table update for donor eNB 408, as described, can include updating entries stored for handover relay eNB 402 and/or the one or more downstream relay eNBs directly or indirectly connected thereto to associate with target relay eNB 406 instead of source relay eNB 404. In one example, donor eNB 102 can locate the entries according to the identifiers received in the bearer list update message (e.g., the identifiers can be those previously assigned by donor eNB 408, as described).

[0083] Donor eNB 408 can subsequently transmit a radio resource control (RRC) connection reconfiguration 426 to target relay eNB 406. For example, if there is no maximum number of data radio bearers limitation for donor eNB 408, it can establish a radio bearer that maps to an EPS bearer of target relay eNB 406 (e.g., received in the bearer list update message). If radio bearers are pre-established, for example, donor eNB 408 can map the EPS bearer to the appropriate radio bearer and send an RRC connection reconfiguration with QoS parameters (e.g., received in the bearer list update message). If radio bearers are not pre-established, the donor eNB 408 can send the RRC connection reconfiguration to the target relay eNB 406 to establish a radio bearer that maps to the EPS bearer. In either case, donor eNB 408 can additionally transmit a bearer list update complete message 428 to target relay eNB 406, and target relay eNB 406 can transmit an RRC reconfiguration complete 430 to donor eNB 408. In one example, the bearer list update complete message can have a format similar to the following.

BearerListUpdateComplete ::= SEQUENCE {
	rrc-TransactionIdentifier	RRC-TransactionIdentifier,
	criticalExtensions	CHOICE {
	bearerListUpdateComplete-r10	BearerListUpdateComplete-r10-IEs,
	criticalExtensions	SEQUENCE { }
	}
}
BearerListUpdateComplete-r10-IEs ::= SEQUENCE {
	cenb-Identity	ENB-Identity,
	enb-Identity	ENB-Identity,
	enbList ::=	SEQUENCE (SIZE (1 .. noofeNBs)) of SEQUENCE{
	enb-Identity	ENB-Identity,
	ueList ::=	SEQUENCE (SIZE (1 .. noofUEs)) of SEQUENCE{
	enb-UE-S1AP-Identity	ENB-UE-S1AP-Identity,
	bearerList ::=	SEQUENCE (SIZE (1 .. noofSAEbearers)) of
SEQUENCE{
	bearerToBeReleasedListItemIEs	BearerListItemIEs
	OPTIONAL,
	bearerToBeAddedListItemIEs	BearerListItemIEs
	OPTIONAL,
	...
	}
	}
	}
}

[0084] In addition, target relay eNB 406 can transmit an RRC connection reconfiguration 432 to handover relay eNB 402 for changing the radio bearer configuration in response to receiving the bearer list update message. Similarly, if there is no maximum number of data radio bearers limitation for target relay eNB 406, it can establish a radio bearer that maps to an EPS bearer of handover relay eNB 402 (e.g., received in the bearer list update message). If radio bearers are pre-established, for example, target relay eNB 406 can map the EPS bearer to the appropriate radio bearer and send an RRC connection reconfiguration with QoS parameters (e.g., received in the bearer list update message). If radio bearers are not pre-established, the target relay eNB 406 can send the RRC connection reconfiguration to the handover relay eNB 402 to establish a radio bearer that maps to the EPS bearer. In either case, In either case, target relay eNB 406 can additionally transmit a bearer list update complete message 434 to handover relay eNB 402, and handover relay eNB 402 can transmit an RRC reconfiguration complete 436 to target eNB 406. Subsequently, donor eNB 408 can forward downlink data 438 to target relay eNB 406 based on the updated routing table, which can transmit the downlink data 440 to handover relay eNB 402 based on its updated routing table.

[0085] Turning now to FIG. 5, a wireless communication system 500 is illustrated that facilitates inter-cluster cell relay reselection. System 500 includes a donor eNB 102 that provides one or more relay eNBs, such as relay eNB 104, with access to a core network 106, and a donor eNB 502 that similarly provides one or more relay eNBs, such as relay eNB 202, with access to core network 106. Similarly, relay eNB 104 can provide one or more disparate relay eNBs, such as relay eNB 108, with access to the core network 106 via donor eNB 102, and relay eNB 108 can similarly provide core network 106 access to relay eNBs 204 and 206. Donor eNBs 102 and 502 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. Thus, donor eNBs 102 and 502 can provide separate clusters for accessing core network 106.

[0086] Donor eNB 102 can additionally provide an access link for relay eNB 104 (and donor eNB 502 for relay eNB 202), which can also be wired or wireless, LTE or other technologies, as described. Similarly, relay eNB 104 can communicate with the donor eNB 102 (and relay eNB 202 to donor eNB 502) using a backhaul link over the access link of the donor eNB. Relay eNB 104 can similarly provide an access link for relay eNB 108, as described, which can be a wired or wireless LTE or other technology link. Relay eNB 108 can provide similar access links to relay eNBs 204 and 206. Donor eNBs 102 and 502 can connect to the core network 106 over a disparate backhaul link technology.

[0087] According to an example, relay eNB 108 can initiate inter-cluster reselection to relay eNB 202, which is in a different cluster than relay eNB 104 (e.g., relay eNB 202 communicates with donor eNB 502 where relay eNB 104 communicates with donor eNB 102). Reselection, as described, can be based on a higher level of service provided by relay eNB 202, signal to noise ratio (SNR) over a certain threshold, and/or the like. Indeed, the reselection can be similar to and performed in similar cases as UE reselection in core network 106. In this regard, in one example, relay eNB 108 (and/or relay eNBs 104, 202, 204, 206) can be mobile such that they travel throughout a core network 106 coverage area.

[0088] As described, relay eNB 108 can perform similar reselection procedures as a UE to handover S1 interface to relay eNB 202. In addition, however, relay eNB 108 can perform specific steps to ensure proper packet routing to/from core network 106 through the various donor and relay nodes in the new cluster. In an example, relay eNB 108, upon initiating reselection to relay eNB 202, can collect one or more parameters regarding downstream relay eNBs, such as relay eNBs 204 and 206, and/or downstream UEs (not shown). The one or more parameters can include, for example a number of relay eNBs, identifiers for the relay eNBs (such as EGIs assigned by core network 106), a number of UEs, UE bearer information, and/or the like. Relay eNB 108 can forward the parameters to relay eNB 202 (e.g., in a handover required message). Relay eNB 202 can forward the parameters to donor eNB 502, which can assign identifiers (e.g., TEID or other relay identifiers) to relay eNB 108 and/or the downstream relay eNBs (relay eNBs 204 and 206 in this example). Donor eNB 502 can store the assigned identifiers along with a bearer identifier for the next downstream relay eNB in the communication path, which is relay eNB 202.

[0089] Donor eNB 502 can transmit the assigned identifiers to relay eNB 202, which can similarly store the identifiers along with an association to the next downstream relay eNB in the communications path, which is relay eNB 108. Relay eNB 202 can transmit the assigned identifiers for downstream relay eNBs that are directly or indirectly connected to relay eNB 108 (e.g., relay eNBs 204 and 206) to relay eNB 108. Relay eNB 108 can store the assigned identifiers along with identifiers for the related next downstream relay eNBs in the communication path to those relay eNBs, and so on. In addition, donor eNB 502 can provide the assigned identifiers to core network 106 (or one or more components thereof, such as a serving gateway (SGW) related to the relay eNBs), such that the core network 106 can include the assigned identifiers in communications for the respective relay eNBs. Also, in this example, bearer setup procedures can be initiated by relay eNB 108 for substantially all downstream relay eNBs and UEs directly or indirectly connected to relay eNB 108.

[0090] In another example, relay eNB 108, along with performing UE type reselection procedures, can request or otherwise acquire identifier assignment from donor eNB 502 and can setup its bearer (and/or bearers of its directly connected UEs) with donor eNB 502. Donor eNB 502 can assign an identifier and store it in a routing table, as described, with a bearer identifier of the next downstream relay eNB, relay eNB 202 in this case. Donor eNB 502 can provide the identifier assignment to relay eNB 202, which can similarly store the assigned identifier along with a bearer identifier of the next downstream relay eNB, relay eNB 108 in this example. Relay eNB 108 can inform its downstream relay eNBs (e.g., relay eNBs 204 and 206) of the reselection, and the downstream relay eNBs can similarly request identifier assignment from donor eNB 502 and establish bearers for itself and directly connected UE.

[0091] In yet another example, as part of reselecting to relay eNB 202 using UE style procedures, relay eNB 108 can send an RRC connection release to its underlying relay eNBs (e.g., relay eNB 204 and 206) and UEs to release established radio bearers. The underlying relay eNBs can similarly send RRC connection release to their underlying relay eNBs and UEs. Subsequently, relay eNB 108 and the relay eNBs and/or UEs previously connected (directly or indirectly) to relay eNB 108 can re-attach to donor eNB 502 to receive identifier assignments and establish routing tables, as described previously.

[0092] Referring now to FIG. 6, an example wireless communication system 600 that facilitates performing inter-cluster reselection for cell relays by assigning identifiers to various downstream relay eNBs at the target donor eNB is illustrated. System 600 includes a donor eNB 102 that provides relay eNB 104 with access to core network 106, and a donor eNB 502 that provides relay eNB 202 with access to core network 106. Additionally, as described, relay eNB 104 can provide relay eNB 108 with access to the core network 106 through the donor eNB 102. Moreover, for example, there can be multiple relay eNBs 104 between the donor eNB 102 and relay eNB 108. In addition, it is to be appreciated that relay eNB 108 (and relay eNBs 202, 204, and 206) can comprise the components of relay eNB 202 (and/or vice versa), in one example, to provide reselection functionality. Moreover, donor eNBs 102 and 502 can be macrocell access points, femtocell access points, picocell access points, mobile base stations, and/or the like. Relay eNBs 104 (and relay eNBs 108, 202, 204, and 206) can similarly be mobile or stationary relay nodes that communicate with donor eNBs 102 and 502 over a wireless or wired backhaul, as described.

[0093] Donor eNB 502 comprises an update message receiving component 602 that obtains a handover required or other message from a downstream relay eNB, an identifier assigning component 604 that generates an identifier for one or more relay eNBs indicated in the received message, a routing table component 306 that stores assigned identifiers of relay eNBs along with bearer identifiers for next downstream relay eNBs in the communication path to the relay eNBs, and a packet routing component 308 that forwards packets received from core network 106 to next downstream relay eNBs based on matching an identifier in the packet to an identifier stored by the routing table component 306.

[0094] Relay eNB 202 comprises an update message receiving component 310 that obtains a handover required or other message from a downstream relay eNB and forwards the message to an upstream eNB, an identifier receiving component 606 that obtains an identifier for one or more downstream relay eNBs from an upstream relay eNB, a routing table component 314 that stores identifiers of the one or more relay eNBs (which can be assigned by donor eNB 502) along with bearer identifiers for next downstream relay eNBs in the communication path to the one or more relay eNBs, and a packet routing component 316 that forwards packets received from an upstream eNB to next downstream relay eNBs based on matching an identifier in the packet to an identifier stored by the routing table component 314.

[0095] Relay eNB 108 includes a reselection initiating component 318 that can begin a procedure to reselect to a disparate relay eNB, a downstream parameter gathering component 608 that obtains one or more parameters of downstream relay eNBs and/or UEs, an update message generating component 610 that creates a handover required or other message comprising the downstream relay eNB/UE parameters and/or parameters related to relay eNB 108, an identifier receiving component 612 that obtains one or more identifiers for downstream relay eNBs from donor eNB 502, a routing table component 614 that stores the identifiers of the downstream relay eNBs along with bearer identifiers for next downstream relay eNBs in the communication path to the downstream relay eNBs, and a packet routing component 324 that forwards packets received from an upstream eNB to relay eNBs 204 and 206 based on locating an identifier receive in the packets in the routing table component 614.

[0096] According to an example, relay eNB 108 can communicate with relay eNB 104 to receive access to core network 106 via donor eNB 102. As described, thus, relay eNB 108 can operate in a cluster provided by donor eNB 102 and can utilize a donor eNB 102 assigned identifier in transmitting and receiving communications in the cluster. Reselection initiating component 318, as described, can initiate reselection to relay eNB 202 from relay eNB 104. In this regard, reselection initiating component 318 can perform UE type reselection procedures to handover S1 interface to relay eNB 202. Before initiating reselection, downstream parameter gathering component 608 can obtain one or more parameters related to relay eNBs 204 and 206 or other devices, such as a number of downstream relay eNBs directly or indirectly connected to relay eNB 108, EGI of the relay eNBs, a number of UEs (not shown) directly or indirectly connected to relay eNB 108, bearer information for the UEs, and/or the like. Reselection initiating component 318 can perform at least a portion of a reselection procedure, and update message generating component 610 can create a handover required or similar message comprising the one or more parameters and transmit the message to relay eNB 202.

[0097] Update message receiving component 310 can obtain the message and forward the message to donor eNB 502. Update message receiving component 602 can similarly obtain the message and signal the core network 106 to initiate bearer setup procedure (e.g., for the UEs). Identifier assigning component 604 can determine the relay eNBs in the handover required or other message and can assign identifiers, such as TEID or other relay identifiers as described, to the relay eNBs. This can include assigning an identifier to relay eNB 108. Routing table component 306 can store associations between the assigned identifiers and a bearer identifier for the next downstream relay eNB in the communication path to the relay eNBs, which is relay eNB 202 in this example. Identifier assigning component 604 can transmit the assigned identifiers to relay eNB 202 (e.g., along with the respective received EGI).

[0098] Identifier receiving component 606 can obtain the assigned identifiers, and routing table component 314 can similarly store the assigned identifiers along with associations to a bearer identifier of the next downstream relay eNB, which is relay eNB 108, in this example. Identifier receiving component 606 can forward the identifiers (and EGI, for example) to relay eNB 108. Identifier receiving component 612 can similarly receive the assigned identifiers. Routing table component 614 can update entries related to downstream relay eNBs based on the received assigned identifiers. For example, routing table component 614 can locate entries based on a corresponding received EGI and update the identifier with that corresponding to the EGI in the received identifiers. Identifier receiving component 612 can transmit the identifiers to related next downstream relay eNBs for similar routing table updating, for example. In addition, identifier assigning component 604 can provide the assigned identifiers to core network 106 (e.g., with EGI) allowing core network 106 to appropriately utilize the updated identifiers for the relay eNBs.

[0099] Thus, routing table components 306, 314, and 614 can have updated associations as a result of the reselection to relay eNB 202. In this regard, upon receiving packets from core network 106 with the identifier of relay eNB 108, 204, or 206, packet routing component 308 can determine the identifier in the packet and discern a next downstream relay eNB based on locating a stored association between the identifier in routing table component 306. As described, for relay eNBs 108, 204, and 206, the routing table entry can relate to relay eNB 202, and the packet routing component 308 can accordingly forward the packet. Similarly, upon relay eNB 202 receiving the packet, packet routing component 316 can consult routing table component 314 to determine the next downstream relay eNB, which is relay eNB 108, as described, according to the new entry received in reselection. Thus, packet routing component 316 can forward the packet to relay eNB 108. Once relay eNB 108 receives the packet, packet routing component 324 can forward the packet, if applicable, to the appropriate relay eNB according to its routing table component 614 updated with the new assigned identifiers for the respective downstream relay eNBs.

[0100] Referring now to FIG. 7, an example wireless communication system 700 that facilitates performing inter-cluster reselection for cell relays by requesting identifier assignment and notifying downstream of the reselection is illustrated. System 700 includes a donor eNB 102 that provides relay eNB 104 with access to core network 106, and a donor eNB 502 that provides relay eNB 202 with access to core network 106. Additionally, as described, relay eNB 104 can provide relay eNB 108 with access to the core network 106 through the donor eNB 102. Moreover, for example, there can be multiple relay eNBs 104 between the donor eNB 102 and relay eNB 108. In addition, it is to be appreciated that relay eNB 108 (and relay eNBs 202, 204, and 206) can comprise the components of relay eNB 202 (and/or vice versa), in one example, to provide reselection functionality. Moreover, donor eNBs 102 and 502 can be macrocell access points, femtocell access points, picocell access points, mobile base stations, and/or the like. Relay eNBs 104 (and relay eNBs 108, 202, 204, and 206) can similarly be mobile or stationary relay nodes that communicate with donor eNBs 102 and 502 over a wireless or wired backhaul, as described.

[0101] Donor eNB 502 comprises an identifier request receiving component 702 that obtains a request for an identifier from a downstream relay eNB (e.g. performing reselection), an identifier assigning component 604 that generates an identifier for one or more relay eNBs indicated in the received message, a routing table component 306 that stores assigned identifiers of relay eNBs along with bearer identifiers for next downstream relay eNBs in the communication path to the relay eNBs, and a packet routing component 308 that forwards packets received from core network 106 to next downstream relay eNBs based on matching an identifier in the packet to an identifier stored by the routing table component 306.

[0102] Relay eNB 202 comprises an identifier request receiving component 704 that obtains a request for an identifier from a downstream relay eNB and forwards the request to an upstream eNB, an identifier receiving component 606 that obtains an identifier for one or more downstream relay eNBs from an upstream relay eNB, a routing table component 314 that stores identifiers of the one or more relay eNBs (which can be assigned by donor eNB 502) along with bearer identifiers for next downstream relay eNBs in the communication path to the one or more relay eNBs, and a packet routing component 316 that forwards packets received from an upstream eNB to next downstream relay eNBs based on matching an identifier in the packet to an identifier stored by the routing table component 314.

[0103] Relay eNB 108 includes a reselection initiating component 318 that can begin a procedure to reselect to a disparate relay eNB, an identifier requesting component 706 that generates and transmits a request for an identifier to a relay eNB when reselecting to the relay eNB, an identifier receiving component 612 that obtains one or more identifiers for downstream relay eNBs from donor eNB 502, a bearer requesting component 708 that transmits a request to establish bearers for directly connected UEs to a donor eNB in a new cluster, a reselection notifying component 710 that provides downstream relay eNBs with a notification of reselection by relay eNB 108, a routing table component 614 that stores the identifiers of the downstream relay eNBs along with bearer identifiers for next downstream relay eNBs in the communication path to the downstream relay eNBs, and a packet routing component 324 that forwards packets received from an upstream eNB to relay eNBs 204 and 206 based on locating an identifier receive in the packets in the routing table component 614.

[0104] According to an example, relay eNB 108 can communicate with relay eNB 104 to receive access to core network 106 via donor eNB 102. As described, thus, relay eNB 108 can operate in a cluster provided by donor eNB 102 and can utilize a donor eNB 102 assigned identifier in transmitting and receiving communications in the cluster. Reselection initiating component 318, as described, can initiate reselection to relay eNB 202 from relay eNB 104. In this regard, reselection initiating component 318 can perform UE type reselection procedures to handover S1 interface to relay eNB 202. In addition, as part of the reselection, identifier requesting component 706 can generate a request for an identifier from donor eNB 502 and can transmit the request upstream to relay eNB 202.

[0105] Identifier request receiving component 704 can obtain the request and forward the request to donor eNB 502. Identifier request receiving component 702 can similarly obtain the request. Identifier assigning component 604 can generate an identifier, such as TEID or other relay identifier as described, for relay eNB 108. Routing table component 306 can store an association between the assigned identifier for relay eNB 108 and a bearer identifier for the next downstream relay eNB in the communication path to relay eNB 108, which is relay eNB 202 in this example. Identifier assigning component 604 can transmit the assigned identifier to relay eNB 202, in one example.

[0106] Identifier receiving component 606 can obtain the assigned identifier, and routing table component 314 can similarly store the assigned identifier for relay eNB 108 along with an association to a bearer identifier of the next downstream relay eNB, which is relay eNB 108, in this example. Identifier receiving component 606 can forward the identifier to relay eNB 108. Identifier receiving component 612 can similarly receive the assigned identifier or notification of assignment. Moreover, bearer requesting component 708 can request bearer establishment in the new cluster for underlying UEs directly communicating with relay eNB 108. Relay eNB 202 can forward the request to donor eNB 502, which can communicate with core network 106 to establish the bearers. In addition, reselection notifying component 710 can transmit a notification of reselection to its downstream relay eNBs, relay eNBs 204 and 206 in this example. It is to be appreciated that reselection notifying component 710 can determine the downstream relay eNBs based at least in part on entries corresponding to the downstream relay eNBs in routing table component 614, in one example. For example, this can cause relay eNBs 204 and 206 to perform similar procedures as relay eNB 108 to facilitate reselection, such as requesting identifiers from donor eNB 502, requesting bearer establishment in the new cluster for their directly connected UEs, and notifying their downstream relay eNBs of the reselection.

[0107] In this example, identifier assigning component 604 can similarly assign an identifier to relay eNB 204 and/or 206 upon receiving the request, and routing table component 306 can store an association of the identifier to a bearer identifier of relay eNB 202, as described. Moreover, identifier receiving component 606 can similarly obtain the identifier, and routing table 314 can similarly store an association to relay eNB 108. In addition, identifier receiving component 606 can forward the identifier to relay eNB 108. Identifier receiving component 612 can obtain the identifier, and routing table component 614 can update its stored entry for relay eNB 204 and/or 206 to reflect the new identifier. Thus, routing table components 306, 314, and 614 can have updated associations as a result of the reselection to relay eNB 202.

[0108] In this regard, upon receiving packets from core network 106 with the identifier of relay eNB 108, 204, or 206, packet routing component 308 can determine the identifier in the packet and discern a next downstream relay eNB based on locating a stored association between the identifier in routing table component 306. As described, for relay eNBs 108, 204, and 206, the routing table entry can relate to relay eNB 202, and the packet routing component 308 can accordingly forward the packet. Similarly, upon relay eNB 202 receiving the packet, packet routing component 316 can consult routing table component 314 to determine the next downstream relay eNB, which is relay eNB 108, as described, according to the new entry received in reselection. Thus, packet routing component 316 can forward the packet to relay eNB 108. Once relay eNB 108 receives the packet, packet routing component 324 can forward the packet, if applicable, to the appropriate relay eNB according to its routing table component 614 updated with the new assigned identifiers for the respective downstream relay eNBs.

[0109] Referring now to FIG. 8, an example wireless communication system 800 that facilitates performing inter-cluster reselection for cell relays by requesting re-attachment to the network at downstream relay eNBs as part of reselection is illustrated. System 800 includes a donor eNB 102 that provides relay eNB 104 with access to core network 106, and a donor eNB 502 that provides relay eNB 202 with access to core network 106. Additionally, as described, relay eNB 104 can provide relay eNB 108 with access to the core network 106 through the donor eNB 102. Moreover, for example, there can be multiple relay eNBs 104 between the donor eNB 102 and relay eNB 108. In addition, it is to be appreciated that relay eNB 108 (and relay eNBs 202, 204, and 206) can comprise the components of relay eNB 202 (and/or vice versa), in one example, to provide reselection functionality. Moreover, donor eNBs 102 and 502 can be macrocell access points, femtocell access points, picocell access points, mobile base stations, and/or the like. Relay eNBs 104 (and relay eNBs 108, 202, 204, and 206) can similarly be mobile or stationary relay nodes that communicate with donor eNBs 102 and 502 over a wireless or wired backhaul, as described.

[0110] Donor eNB 502 comprises an attachment request receiving component 802 that obtains a network attachment request from a downstream relay eNB, an identifier assigning component 604 that generates an identifier for one or more relay eNBs from which a network attachment request is received, a routing table component 306 that stores assigned identifiers of relay eNBs along with bearer identifiers for next downstream relay eNBs in the communication path to the relay eNBs, and a packet routing component 308 that forwards packets received from core network 106 to next downstream relay eNBs based on matching an identifier in the packet to an identifier stored by the routing table component 306.

[0111] Relay eNB 202 comprises an attachment request receiving component 804 that obtains a network attachment request from a downstream relay eNB and forwards the request to an upstream eNB, an identifier receiving component 606 that obtains an identifier for one or more downstream relay eNBs from an upstream relay eNB, a routing table component 314 that stores identifiers of the one or more relay eNBs (which can be assigned by donor eNB 502) along with bearer identifiers for next downstream relay eNBs in the communication path to the one or more relay eNBs, and a packet routing component 316 that forwards packets received from an upstream eNB to next downstream relay eNBs based on matching an identifier in the packet to an identifier stored by the routing table component 314.

[0112] Relay eNB 108 includes a reselection initiating component 318 that can begin a procedure to reselect to a disparate relay eNB, a connection releasing component 806 that transmits a connection release message to its underlying relay eNBs and UEs to release resources and/or bearers established for the relay eNBs and UEs, an attachment requesting component 808 that transmits a request to attach to a wireless network under a target donor eNB during reselection, an identifier receiving component 612 that obtains one or more identifiers for downstream relay eNBs from the target donor eNB, a routing table component 614 that stores the identifiers of the downstream relay eNBs along with bearer identifiers for next downstream relay eNBs in the communication path to the downstream relay eNBs, and a packet routing component 324 that forwards packets received from an upstream eNB to relay eNBs 204 and 206 based on locating an identifier receive in the packets in the routing table component 614.

[0113] According to an example, relay eNB 108 can communicate with relay eNB 104 to receive access to core network 106 via donor eNB 102. As described, thus, relay eNB 108 can operate in a cluster provided by donor eNB 102 and can utilize a donor eNB 102 assigned identifier in transmitting and receiving communications in the cluster. Reselection initiating component 318, as described, can initiate reselection to relay eNB 202 from relay eNB 104. In this regard, reselection initiating component 318 can perform UE type reselection procedures to handover S1 interface to relay eNB 202. Additionally, as part of reselection, connection releasing component 806 can transmit an RRC connection release (or similar connection release) message to its downstream relay eNBs (e.g., relay eNBs 204 and 206) and UEs (not shown) to release resources and/or bearers associated with the relay eNBs and UEs. This can cause the downstream relay eNBs (e.g., relay eNBs 204 and 206) to similarly release resources for their underlying relay eNBs and UEs.

[0114] Attachment requesting component 808 can transmit a network attachment request to donor eNB 502 to re-attach to the core network 106. Attachment request receiving component 804 can receive the request and forward it to donor eNB 502. In addition, attachment request receiving component 802 can obtain the attachment request. Similarly to an initial attachment procedure, identifier assigning component 604 can generate a donor eNB 502 unique identifier for relay eNB 108 to facilitate routing packets thereto. Routing table component 306 can store an association between the identifier and a bearer identifier for the next downstream relay eNB, relay eNB 202 in this example. Identifier assigning component 604 can transmit the identifier to relay eNB 202. Similarly, identifier receiving component 606 can obtain the identifier, and routing table component 314 can store the identifier along with a bearer identifier for the next downstream relay eNB in the communication path, which is relay eNB 108 in this example.

[0115] Moreover, as described, downstream relay eNBs to relay eNB 108 (e.g., relay eNBs 204 and 206) can similarly re-attach to core network 106. The downstream relay eNBs can additionally receive an identifier from donor eNB 502 that is similarly stored in routing table components 306 and 314. Also, identifier receiving component 606 can transmit the identifier to relay eNB 108. Identifier receiving component 612 can similarly receive the identifier, and routing table 614 can store an association of the identifier to the appropriate next downstream relay eNB, and so on. Additionally, downstream UEs can also re-attach to core network 106 to establish bearers and communication resources previously released. Thus, routing table components 306, 314, and 614 can have updated associations as a result of the reselection to relay eNB 202.

[0116] In this regard, upon receiving packets from core network 106 with the identifier of relay eNB 108, 204, or 206, packet routing component 308 can determine the identifier in the packet and discern a next downstream relay eNB based on locating a stored association between the identifier in routing table component 306. As described, for relay eNBs 108, 204, and 206, the routing table entry can relate to relay eNB 202, and the packet routing component 308 can accordingly forward the packet. Similarly, upon relay eNB 202 receiving the packet, packet routing component 316 can consult routing table component 314 to determine the next downstream relay eNB, which is relay eNB 108, as described, according to the new entry received in reselection. Thus, packet routing component 316 can forward the packet to relay eNB 108. Once relay eNB 108 receives the packet, packet routing component 324 can forward the packet, if applicable, to the appropriate relay eNB according to its routing table component 614 updated with the new assigned identifiers for the respective downstream relay eNBs.

[0117] Now turning to FIG. 9, an example wireless communication network 900 that provides cell 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 using a relay protocol 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 UE 110 to use the network, which can utilize an IMS 910 to provide addressing to the UE 110 and/or relay eNB 104.

[0118] According to an example, MME 902 and/or SGW 904 and PGW 906 can be related to donor eNB 102 serving substantially all relay eNBs in the cluster. Donor eNB 102 can also communicate with an SGW 916 and PGW 918 that relate to the UE 110, such that the PGW 918 can assign UE 110 a network address to facilitate tunneling communications thereto through the relay eNB 104, donor eNB 102, and SGW 916. Moreover, for example, SGW 916 can communicate with an MME 914 to facilitate control plane communications to and from the UE 110. It is to be appreciated that MME 902 and MME 914 can be the same MME, in one example. 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.

[0119] In an example, UE 110 can communicate with the relay eNB 104 over an E-UTRA-Uu interface, as described, and the relay eNB 104 can communicate with the donor eNB 102 using an E-UTRA-Uu interface or other interface using the relay protocol, as described herein. 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. In one example, as described, communications received from relay eNB 104 for MME 902 or SGW 904/PGW 906 can be over a relay protocol and can have an IP address of MME 902 or SGW 904/PGW 906 in the relay protocol header. Donor eNB 102 can appropriately route the packet according to the IP address and/or payload type of the relay protocol. In another example, packets from relay eNB 104 can comprised a previously assigned TEID or portion thereof. In addition, the transport layers used over the S1-MME and S1-U interfaces are terminated at the donor eNB 102, as described. In this regard, upon receiving communications for the relay eNB 104 from the MME 902 or SGW 904, donor eNB 102 can, for example, decouple the application layer from the transport layer by defining a new relay protocol packet, or other protocol layer packet, and transmitting the application layer communication to the relay eNB 104 in the new protocol packet (over the E-UTRA-Uu interface, in one example). Donor eNB 102 can transmit the packet to relay eNB 104 (and/or one or more disparate relay eNBs as described) based on a TEID in the packet or relay identifier in the header.

[0120] Upon transmitting control plane communications from the relay eNB 104 to the MME 902, donor eNB 102 can indicate an identifier of the relay eNB 104 (e.g., in an S1-AP message), and MME 902 can transmit the identifier in responding communications to the donor eNB 102. When transmitting data plane communications from relay eNB 104 to SGW 904, donor eNB 102 can insert an identifier for the relay eNB 104 (or UE 110 or one or more related bearers) in the TEID of a GTP-U header to identify the relay eNB 104 (or UE 110 or one or more related bearers). This can be an identifier generated for relay eNB 104 by donor eNB 102 such that donor eNB 102 can determine the relay eNB 104, or one or more downstream relay eNBs is to receive the translated packet, as described above. For example, this can be based at least in part on locating at least a portion of the identifier in a routing table at donor eNB 102. In addition, headers can be compressed, in one example, as described. As shown, MME 902 can communicate with SGW 904, and MME 914 to SGW 916, using an S11 interface. PGWs 906 and 918 can communicate with PCRF 908 over a Gx interface. Furthermore, PCRF 908 can communicate with IMS 910 using an Rx interface, and PGW 918 can communicate with IMS 910 and/or the internet 912 using an SGi interface.

[0121] Referring to FIGS. 10-13, methodologies relating to reselecting relay eNBs in cell relay configured wireless networks 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.

[0122] Turning to FIG. 10, an example methodology 1000 that facilitates performing one or more steps in an intra-cluster reselection is illustrated. At 1002, a relay eNB can be communicated with to receive access to a wireless network. As described, the relay eNB can provide such access through a donor eNB (and/or one or more intermediary relay eNBs). At 1004, a connection with a disparate relay eNB can be established to facilitate reselecting the disparate relay eNB. In this example, the disparate relay eNB can provide wireless network access through the same donor eNB (and thus be in the same cluster) as the relay eNB. In this regard, upstream relay eNBs can modify internal routing tables for routing packets through the disparate relay eNB instead of the relay eNB. To facilitate such updating, at 1006, a bearer list update message can be transmitted to the disparate relay eNB comprising an identifier assigned by a donor eNB. In addition, as described, the bearer list update message can also comprise identifiers of one or more downstream relay eNBs such that an upstream relay eNB can update or add routing table entries to forward packets according to the identifiers in the bearer list update message, as described previously.

[0123] Referring to FIG. 11, an example methodology 1100 is shown that facilitates updating routing tables upon intra-cluster reselection by a downstream relay eNB. At 1102, a bearer list update message can be received from a relay eNB during reselection for the relay eNB. As described, the bearer list update message can include an identifier of the relay eNB and/or identifiers of downstream relay eNBs of the relay eNB. At 1104, an identifier of the relay eNB can be determined from the bearer list update message. At 1106, the identifier of the relay eNB can be associated to a bearer identifier of a next downstream relay eNB. As described, if an entry exists for the relay eNB, it can be updated; if no entry exists, an entry can be added. In addition, where other identifiers of downstream relay eNBs of the relay eNB are present in the bearer list update message, associations for those identifiers can be similarly updated or added.

[0124] Referring to FIG. 12, an example methodology 1200 is shown that facilitates performing one or more steps in an inter-cluster reselection. At 1202, a relay eNB can be communicated with to receive access to a wireless network. As described, the relay eNB can provide such access through a donor eNB (and/or one or more intermediary relay eNBs). At 1204, a connection with a disparate relay eNB can be established to facilitate reselecting the disparate relay eNB. In this example, the disparate relay eNB can provide wireless network access through a disparate donor eNB (and thus be in a different cluster) as the relay eNB. In this regard, an identifier can be assigned by the disparate donor eNB to facilitate routing within the new cluster. At 1206, an identifier request can be transmitted to the disparate relay eNB to facilitate assignment of an identifier by a donor eNB of the disparate relay eNB. In one example, this can be an explicit request, a request triggered by a network attachment procedure, and/or the like. In addition, the identifier request, in one example, can comprise identifiers for downstream relay eNBs to facilitate assigning identifiers to those nodes as well.

[0125] Referring to FIG. 13, an example methodology 1300 is shown that facilitates updating routing tables upon inter-cluster reselection by a downstream relay eNB. At 1302, an identifier request can be received from a relay eNB during reselection for the relay eNB. As described, the identifier request can be an explicit request, a request triggered by a network attachment procedure, a request for assigning multiple identifiers (e.g., of downstream relay eNBs to the relay eNB), and/or the like. At 1304, an identifier can be obtained for the relay eNB. For example, the identifier can be received from an upstream relay eNB, generated for the relay eNB, and/or the like. At 1306, the identifier of the relay eNB can be associated to a bearer identifier of a next downstream relay eNB. As described, the association can be stored in a routing table. Moreover, as described, identifiers can be obtained for downstream relay eNBs to the relay eNB, for example, and similarly associated to the next downstream relay eNB in the routing table, for example.

[0126] It will be appreciated that, in accordance with one or more aspects described herein, inferences can be made regarding generating identifiers for downstream relay eNBs, updating routing tables according to the identifiers, 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.

[0127] Referring now to FIG. 14, a wireless communication system 1400 is illustrated in accordance with various embodiments presented herein. System 1400 comprises a base station 1402 that can include multiple antenna groups. For example, one antenna group can include antennas 1404 and 1406, another group can comprise antennas 1408 and 1410, and an additional group can include antennas 1412 and 1414. Two antennas are illustrated for each antenna group; however, more or fewer antennas can be utilized for each group. Base station 1402 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.

[0128] Base station 1402 can communicate with one or more mobile devices such as mobile device 1416 and mobile device 1422; however, it is to be appreciated that base station 1402 can communicate with substantially any number of mobile devices similar to mobile devices 1416 and 1422. Mobile devices 1416 and 1422 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 1400. As depicted, mobile device 1416 is in communication with antennas 1412 and 1414, where antennas 1412 and 1414 transmit information to mobile device 1416 over a forward link 1418 and receive information from mobile device 1416 over a reverse link 1420. Moreover, mobile device 1422 is in communication with antennas 1404 and 1406, where antennas 1404 and 1406 transmit information to mobile device 1422 over a forward link 1424 and receive information from mobile device 1422 over a reverse link 1426. In a frequency division duplex (FDD) system, forward link 1418 can utilize a different frequency band than that used by reverse link 1420, and forward link 1424 can employ a different frequency band than that employed by reverse link 1426, for example. Further, in a time division duplex (TDD) system, forward link 1418 and reverse link 1420 can utilize a common frequency band and forward link 1424 and reverse link 1426 can utilize a common frequency band.

[0129] 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 1402. For example, antenna groups can be designed to communicate to mobile devices in a sector of the areas covered by base station 1402. In communication over forward links 1418 and 1424, the transmitting antennas of base station 1402 can utilize beamforming to improve signal-to-noise ratio of forward links 1418 and 1424 for mobile devices 1416 and 1422. Also, while base station 1402 utilizes beamforming to transmit to mobile devices 1416 and 1422 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 1416 and 1422 can communicate directly with one another using a peer-to-peer or ad hoc technology (not shown).

[0130] According to an example, system 1400 can be a multiple-input multiple-output (MIMO) communication system. Further, system 1400 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 1402 can communicate to the mobile devices 1416 and 1422 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.

[0131] FIG. 15 shows an example wireless communication system 1500. The wireless communication system 1500 depicts one base station 1510 and one mobile device 1550 for sake of brevity. However, it is to be appreciated that system 1500 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 1510 and mobile device 1550 described below. In addition, it is to be appreciated that base station 1510 and/or mobile device 1550 can employ the systems (FIGS. 1-9 and 14) and/or methods (FIGS. 10-13) described herein to facilitate wireless communication therebetween.

[0132] At base station 1510, traffic data for a number of data streams is provided from a data source 1512 to a transmit (TX) data processor 1514. According to an example, each data stream can be transmitted over a respective antenna. TX data processor 1514 formats, codes, and interleaves the traffic data stream based on a particular coding scheme selected for that data stream to provide coded data.

[0133] 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 1550 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 1530.

[0134] The modulation symbols for the data streams can be provided to a TX MIMO processor 1520, which can further process the modulation symbols (e.g., for OFDM). TX MIMO processor 1520 then provides N_T modulation symbol streams to N_T transmitters (TMTR) 1522a through 1522t. In various aspects, TX MIMO processor 1520 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

[0135] Each transmitter 1522 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_T modulated signals from transmitters 1522a through 1522t are transmitted from N_T antennas 1524a through 1524t, respectively.

[0136] At mobile device 1550, the transmitted modulated signals are received by N_R antennas 1552a through 1552r and the received signal from each antenna 1552 is provided to a respective receiver (RCVR) 1554a through 1554r. Each receiver 1554 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.

[0137] An RX data processor 1560 can receive and process the N_R received symbol streams from N_R receivers 1554 based on a particular receiver processing technique to provide N_T “detected” symbol streams. RX data processor 1560 can demodulate, deinterleave, and decode each detected symbol stream to recover the traffic data for the data stream. The processing by RX data processor 1560 is complementary to that performed by TX MIMO processor 1520 and TX data processor 1514 at base station 1510.

[0138] A processor 1570 can periodically determine which precoding matrix to utilize as discussed above. Further, processor 1570 can formulate a reverse link message comprising a matrix index portion and a rank value portion.

[0139] 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 1538, which also receives traffic data for a number of data streams from a data source 1536, modulated by a modulator 1580, conditioned by transmitters 1554a through 1554r, and transmitted back to base station 1510.

[0140] At base station 1510, the modulated signals from mobile device 1550 are received by antennas 1524, conditioned by receivers 1522, demodulated by a demodulator 1540, and processed by a RX data processor 1542 to extract the reverse link message transmitted by mobile device 1550. Further, processor 1530 can process the extracted message to determine which precoding matrix to use for determining the beamforming weights.

[0141] Processors 1530 and 1570 can direct (e.g., control, coordinate, manage, etc.) operation at base station 1510 and mobile device 1550, respectively. Respective processors 1530 and 1570 can be associated with memory 1532 and 1572 that store program codes and data. Processors 1530 and 1570 can also perform computations to derive frequency and impulse response estimates for the uplink and downlink, respectively.

[0142] It is to be understood that the aspects described herein can be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the processing units can be implemented within one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof.

[0143] When the aspects are implemented in software, firmware, middleware or microcode, program code or code segments, they can be stored in a machine-readable medium, such as a storage component. A code segment can represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment can be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. can be passed, forwarded, or transmitted using any suitable means including memory sharing, message passing, token passing, network transmission, etc.

[0144] For a software implementation, the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The software codes can be stored in memory units and executed by processors. The memory unit can be implemented within the processor or external to the processor, in which case it can be communicatively coupled to the processor via various means as is known in the art.

[0145] With reference to FIG. 16, illustrated is a system 1600 that facilitates performing an intra-cluster reselection to a disparate relay eNB. For example, system 1600 can reside at least partially within a base station, mobile device, etc. It is to be appreciated that system 1600 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 1600 includes a logical grouping 1602 of electrical components that can act in conjunction. For instance, logical grouping 1602 can include an electrical component for initiating reselection from a relay eNB to a disparate relay eNB that utilizes a same donor eNB to provide access to a wireless network 1604. For example, as described, electrical component 1604 can at least initiate reselection for a UE portion (e.g., to handover an S1 interface connection to the disparate relay eNB).

[0146] Additionally, logical grouping 1602 can include an electrical component for generating a bearer list update message comprising an identifier of the system 1600 and transmitting the bearer list update message during reselection 1606. Thus, the identifier can be transmitted to upstream relay eNBs to facilitate routing table updating so packets can be forwarded to the disparate relay eNB following reselection. Moreover, logical grouping 1602 can include an electrical component for determining one or more identifiers relating to one or more downstream relay eNBs 1608. In this regard, electrical component 1606 can also transmit the identifiers of the downstream relay eNBs in the bearer list update message to facilitate routing table updating for those identifiers as well. Additionally, system 1600 can include a memory 1610 that retains instructions for executing functions associated with electrical components 1604, 1606, and 1608. While shown as being external to memory 1610, it is to be understood that one or more of electrical components 1604, 1606, and 1608 can exist within memory 1610.

[0147] With reference to FIG. 17, illustrated is a system 1700 that facilitates receiving identifiers of relay eNBs performing reselection and updating routing tables to reflect a new communications path to the relay eNBs. 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 receiving a bearer list update message from a relay eNB during reselection for the relay eNB 1704. As described, the bearer list update message can comprise an identifier of the relay eNB and/or one or more disparate relay eNBs downstream to the relay eNB.

[0148] Additionally, logical grouping 1702 can include an electrical component for determining an identifier of the relay eNB from the bearer list update message 1706. Moreover, logical grouping 1702 can include an electrical component for storing an association between the identifier of the relay eNB and a bearer identifier of a next downstream relay eNB in a communication path to the relay eNB in a routing table 1708. As described, storing the association can include adding a new association or updating a previous association. Additionally, system 1700 can include a memory 1710 that retains instructions for executing functions associated with electrical components 1704, 1706, and 1708. While shown as being external to memory 1710, it is to be understood that one or more of electrical components 1704, 1706, and 1708 can exist within memory 1710.

[0149] With reference to FIG. 18, illustrated is a system 1800 that facilitates performing an inter-cluster reselection to a disparate relay eNB. 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 initiating reselection from a relay eNB to a disparate relay eNB that utilize disparate donor eNBs to provide access to a wireless network 1804. For example, as described, electrical component 1804 can at least initiate reselection for a UE portion (e.g., to handover an S1 interface connection to the disparate relay eNB).

[0150] Additionally, logical grouping 1802 can include an electrical component for transmitting an identifier request to facilitate assignment of a unique identifier at the disparate donor eNB 1806. As described, the request can be part of a network attachment procedure performed to re-attach to the wireless network through disparate donor eNB (and through disparate relay eNB, for example). In this example, logical grouping 1802 can include an electrical component for transmitting a connection release message to one or more downstream relay eNBs 1808. This can additionally cause the downstream relay eNBs to similarly re-attach to the network and receive new identifiers from the disparate donor eNB. In another example, the identifier request can relate to an explicit request for an identifier. In this example, logical grouping 1802 can include an electrical component for notifying one or more downstream relay eNBs of the initiating reselection 1810. This can cause the downstream relay eNBs to similarly request an identifier, as described, and notify its downstream relay eNBs of reselection.

[0151] Furthermore, logical grouping 1802 can include an electrical component for receiving a unique identifier from the disparate relay eNB relating to at least one of the one or more downstream relay eNBs 1812. As described, this can be received once system 1800 has reselected to the disparate relay eNB. In this regard, logical grouping 1802 can include an electrical component for updating a routing table to associate the unique identifier with a next downstream relay eNB in a communication path to the at least one of the one or more downstream relay eNBs 1814. Additionally, system 1800 can include a memory 1816 that retains instructions for executing functions associated with electrical components 1804, 1806, 1808, 1810, 1812, and 1814. While shown as being external to memory 1816, it is to be understood that one or more of electrical components 1804, 1806, 1808, 1810, 1812, and 1814 can exist within memory 1816.

[0152] With reference to FIG. 19, illustrated is a system 1900 that facilitates receiving identifier requests for relay eNBs performing reselection and updating routing tables to reflect a next downstream relay eNB for the relay eNBs. For example, system 1900 can reside at least partially within a base station, mobile device, etc. It is to be appreciated that system 1900 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 1900 includes a logical grouping 1902 of electrical components that can act in conjunction. For instance, logical grouping 1902 can include an electrical component for receiving an identifier request from a relay eNB during reselection for the relay eNB 1904. As described, the identifier request can be part of a network attachment request, an explicit request for an identifier, a request for identifiers for downstream relay eNBs, and/or the like.

[0153] Additionally, logical grouping 1902 can include an electrical component for obtaining an identifier for the relay eNB 1906. As described, this can include receiving the identifier, generating the identifier, and/or the like. Moreover, logical grouping 1902 can include an electrical component for storing an association between the identifier of the relay eNB and a bearer identifier of a next downstream relay eNB in a communication path to the relay eNB in a routing table 1908. Thus, identifiers can be assigned to relay eNBs reselecting to relay eNBs in a new cluster within which system 1900 operates. Additionally, system 1900 can include a memory 1910 that retains instructions for executing functions associated with electrical components 1904, 1906, and 1908. While shown as being external to memory 1910, it is to be understood that one or more of electrical components 1904, 1906, and 1908 can exist within memory 1910.

[0154] 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.

[0155] 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.

[0156] 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 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.

[0157] 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.