Abstract: Various aspects of the present disclosure enable a plurality of mobile devices (UEs) within a cell to spread out in time their respective transmissions of signaling messages, such as cell update messages, when the network enables or disables enhanced uplink (EUL, sometimes referred to as high-speed uplink packet access or HSUPA) while the UE is in the CELL_FACH state, by changing SIB5 or SIB5bis. In this way, the network load may be reduced, and a network blockage that otherwise might result from large numbers of UEs simultaneously transmitting the cell update message can be avoided. According to one example, a network node may be configured to distribute CELL_UPDATE messages or procedures to UEs when the network node enables or disables EUL in CELL_FACH by changing SIB5 or SIB5bis over time to reduce the network load. According to another example, a UE may be configured for utilizing a random timer or back-off timer to defer cell updates.

Abstract: Techniques for prioritizing non-scheduled data are described. Non-scheduled data to be transmitted on a non-scheduled MAC-d flow having a non-scheduled priority and scheduled data to be transmitted on a scheduled MAC-d flow having a scheduled priority may be identified by a user equipment (UE). The UE may transmit the non-scheduled MAC-d flow and the scheduled MAC-d flow according to a priority condition. In one aspect, the UE may receive a pre-allocation of power associated with a non-empty non-scheduled MAC-d flow. Based on a priority condition that the non-scheduled priority is a highest priority, the UE may apply all of the pre-allocation of power when transmitting the non-scheduled MAC-d flow.

Abstract: The present disclosure presents a method and apparatus for dynamically configuring a cell update message at a user equipment (UE). For example, the method may include determining that a size of the cell update message at the UE is above a threshold value after a “measured results on random access channel (RACH)” information element (IE) is excluded from the cell update message. Furthermore, such an example method may include removing one or more IEs from the cell update message until the size of the cell update message is at or below the threshold value. As such, dynamic configuration of a cell update message at a UE is achieved.

Abstract: Systems and methodologies are described that facilitate supporting mobility for UEs and relay eNBs in split-cell relay configurations. Parameters regarding communicating with one or more UEs can be provided to disparate eNBs from a donor eNB to provide mobility for one or more of the UEs or a serving relay eNB. In addition, a donor eNB can request establishment of one or more radio bearers at a target relay eNB for continuing communications with one or more UEs. Moreover, a donor eNB can provide information regarding one or more core network bearers to a target donor eNB to facilitate establishing the core network bearers at the target donor eNB for communicating with the one or more UEs. Furthermore, uplink buffer contents from a relay eNB can be provided to a target donor eNB so communications from the one or more UEs can be continued by the target donor eNB.

Abstract: Systems and methodologies are described that facilitate supporting mobility for UEs and relay eNBs in split-cell relay configurations. Parameters regarding communicating with one or more UEs can be provided to disparate eNBs from a donor eNB to provide mobility for one or more of the UEs or a serving relay eNB. In addition, a donor eNB can request establishment of one or more radio bearers at a target relay eNB for continuing communications with one or more UEs. Moreover, a donor eNB can provide information regarding one or more core network bearers to a target donor eNB to facilitate establishing the core network bearers at the target donor eNB for communicating with the one or more UEs. Furthermore, uplink buffer contents from a relay eNB can be provided to a target donor eNB so communications from the one or more UEs can be continued by the target donor eNB.

Abstract: The described aspects include a user equipment (UE) apparatus, network component, and corresponding methods of communicating power saving information using common uplink messages. By using a resource update message to communicate power saving information from a UE, the UE need not request and establish resources with the network for requesting a power state that uses less power than a current state. Similarly, in UE mobility, the UE can indicate previous power saving information to a target Node B to cause the target Node B to refrain from assigning resources to the UE.

Abstract: Systems and methodologies are described that facilitate assigning TEIDs, or portions thereof, to UEs or other devices during network attachment and/or dedicated bearer activation using one or more cell relays. Relay eNBs can request bearer establishment from a UE, which can be based on receiving an attach accept from an upstream node during attachment for the UE, receiving a bearer setup request from the upstream node, and/or the like. Once a bearer establishment response is received from the UE, the relay eNBs can store a TEID relating to the bearer. This can be a TEID that is at least partially received in the attach accept or bearer setup message, generated for the UE upon receiving the bearer establishment response, and/or the like. The TEID, or portion thereof, can be utilized for subsequent packet routing to the UE through one or more cell relays.

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

Abstract: Systems and methodologies are described that facilitate packet routing among relay nodes in a wireless network. Bearer quality of service (QoS) mapping is provided for internet protocol (IP) relays by utilizing differentiated services (DiffServ) code point (DSCP) values to determine a bearer for communicating related packets. In addition, SDF filtering at a gateway node can be modified to route packets over certain tunnels to provide QoS for the packets.

Abstract: Systems and methodologies are described that facilitate packet routing among relay eNBs in a wireless network. Packet data convergence protocol (PDCP) layer communications from a user equipment (UE) can terminate at a donor evolved Node B (eNB) and vice versa. In this regard, a relay application protocol (RAPP) layer is defined to transport application layer control data among relay eNBs to facilitate appropriate routing. RAPP layer messages can be similar to control messages at other application layers, such as S1-AP, X2, etc., while additionally including a relay UE identifier for routing the messages among relay eNBs. In addition, RAPP layer messages can exclude other parameters normally defined in other application layers to protect security and encryption/decryption details.

Abstract: Systems and methodologies are described that facilitate supporting mobility for UEs and relay eNBs in split-cell relay configurations. Parameters regarding communicating with one or more UEs can be provided to disparate eNBs from a donor eNB to provide mobility for one or more of the UEs or a serving relay eNB. In addition, a donor eNB can request establishment of one or more radio bearers at a target relay eNB for continuing communications with one or more UEs. Moreover, a donor eNB can provide information regarding one or more core network bearers to a target donor eNB to facilitate establishing the core network bearers at the target donor eNB for communicating with the one or more UEs. Furthermore, uplink buffer contents from a relay eNB can be provided to a target donor eNB so communications from the one or more UEs can be continued by the target donor eNB.

Abstract: Systems and methodologies are described that facilitate compressing headers for internet protocol (IP) relay nodes. In particular, a plurality of IP headers in a packet and at least one tunneling protocol header can be compressed to facilitate efficient communications of packets between IP relay nodes and/or a donor access point. In addition, IP relay nodes can be limited in a number of upstream bearers and can provide a greater number of downstream bearers. In this regard, the IP relay nodes can compress headers for upstream packets related to one or more downstream devices utilizing disparate context identifiers for the upstream packets. Thus, the upstream packets can be distinguished from each other while sent over the same upstream bearer.

Abstract: Systems and methodologies are described that facilitate packet routing among relay eNBs in a wireless network. Packet data convergence protocol (PDCP) layer communications from a user equipment (UE) can terminate at a donor evolved Node B (eNB) and vice versa. In this regard, relay eNBs can forward PDCP layer communications over a routing protocol without locally processing the layer. The relay eNBs can, however, retrieve one or more parameters from a header of the PDCP layer for feedback to the donor eNB to assist in flow control, sequence number status transfer, and/or the like. In addition, routing identifier can be utilized to determine relay eNBs for receiving the packets. The routing identifier can additionally include an identifier of a radio bearer of the relay eNB communicating with the UE over which the PDCP layer communications are to be transmitted.

Abstract: Systems and methodologies are described that facilitate mapping multiple evolved packet system (EPS) bearers to a single relay eNB radio bearer. In particular, an upstream eNB can select a radio bearer of a downstream eNB for association to an EPS bearer; the selection can be based on a best effort match or substantially any logic. The upstream eNB can store an association between the radio bearer and EPS bearer for subsequent downstream packet routing. The upstream eNB can also provide an indication of the selected radio bearer to the downstream relay eNB to facilitate upstream packet routing therefrom. The upstream eNB can alternatively select the radio bearer of the downstream eNB for association to the EPS bearer based on a quality of service (QoS) class identifier (QCI) of the EPS bearer.

Abstract: Systems and methodologies are described that facilitate attaching cell relays to a wireless network. During the attachment procedure, a relay eNB can request assignment of an identifier, or a portion thereof, from a donor eNB for subsequent packet routing to the relay eNB. This can occur through one or more intermediary relay eNBs, where present. Donor eNB can assign an identifier or portion thereof (or confirm/deny an explicit identifier request from the relay eNB) and can forward establishment information downstream to the relay eNB. Donor eNB and intermediary relay eNBs, where present, can store the identifier for subsequent use in routing packets to the relay eNB. The identifier can be a terminal endpoint identifier (TEID) utilized in a tunneling protocol, a relay identifier utilized in a relay protocol, and/or the like.

Abstract: Systems and methodologies are described that facilitate compressing packet headers for cell relay communications. Since cell relays can support a number of evolved packet system (EPS) bearers over a given dedicated radio bearer (DRB), robust header compression (RoHC) can be multiplexed for communications to/from a given cell relay. Thus, an upstream node compressing one or more packet headers can indicate a RoHC context, which can be represented by a RoHC context identifier in a RoHC header. A receiving entity can decompress the headers based on determining the RoHC context. Alternatively, the RoHC context can be associated with an identifier of a related UE bearer such as a tunnel endpoint identifier (TEID), a relay identifier, and/or the like, that is received in a tunneling protocol header to facilitate packet routing.

Abstract: Systems and methodologies are described that facilitate packet routing among relay eNBs in a wireless network. A donor eNB can create at least a portion of a tunnel endpoint identifier (TEID) for a relay eNB communicating with a UE or other device. In addition, the relay eNB communicating with the UE can create a portion of the TEID. Upon receiving packets with a TEID, the donor eNB can route the packets to downstream eNBs based on the portion of the TEID that it created. Other downstream eNBs can continue to route packets to next hop eNBs based on the portion of the TEID created by the donor eNB or the downstream eNBs themselves. The relay eNB communicating with the UE can route packets to the UE based on the portion of the TEID it created and/or the portion created by the donor eNB.

Abstract: Systems and methodologies are described that facilitate assigning TEIDs, or portions thereof, to UEs or other devices during network attachment and/or dedicated bearer activation using one or more cell relays. Relay eNBs can request bearer establishment from a UE, which can be based on receiving an attach accept from an upstream node during attachment for the UE, receiving a bearer setup request from the upstream node, and/or the like. Once a bearer establishment response is received from the UE, the relay eNBs can store a TEID relating to the bearer. This can be a TEID that is at least partially received in the attach accept or bearer setup message, generated for the UE upon receiving the bearer establishment response, and/or the like. The TEID, or portion thereof, can be utilized for subsequent packet routing to the UE through one or more cell relays.

Abstract: Systems and methodologies are described that facilitate performing intra-cluster and inter-cluster reselection for relay eNBs. In intra-cluster reselection, a relay eNB can reselect a disparate relay eNB and indicate its identifier in a bearer list update message. The disparate relay eNB and upstream eNBs (including the donor eNB) can update routing tables based at least in part on the identifier. In addition, the relay eNB can provide identifiers of downstream relay eNBs to facilitate updating routing tables for those identifiers as well. In an inter-cluster reselection, relay eNBs can release connection to downstream relay eNBs and re-attach to a wireless network to receive an identifier from a new donor eNB in the new cluster. Alternatively, the relay eNB can request an identifier from the donor eNB during reselection, notify downstream relay eNBs of the reselection, and/or request identifiers for one or more downstream relay eNBs.

Abstract: Systems and methodologies are described that facilitate providing a relay protocol to facilitate communicating upper layer protocol data among relay and donor nodes. In particular, a donor node can create a relay protocol packet upon receiving data for a relay node from a core network. Donor node can indicate an assigned relay identifier in the relay protocol packet header to facilitate routing the packet among related downstream relay nodes to arrive at the appropriate relay node, which can process the upper layer protocol data. In addition, a relay node can formulate a relay protocol packet for communication to a donor node through zero or more intermediary upstream relay nodes. Similarly, the relay node can insert the assigned relay identifier in the header to allow the donor node to associate response or related packets from the core network with the relay node.