Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/70—Admission control; Resource allocation
  • H04L47/78—Architectures of resource allocation
  • H04L47/782—Hierarchical allocation of resources, e.g. involving a hierarchy of local and centralised entities
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L47/00—Traffic control in data switching networks
  • H04L47/10—Flow control; Congestion control
  • H04L47/41—Flow control; Congestion control by acting on aggregated flows or links
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W28/00—Network traffic management; Network resource management
  • H04W28/02—Traffic management, e.g. flow control or congestion control
  • H04W28/0284—Traffic management, e.g. flow control or congestion control detecting congestion or overload during communication
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W28/00—Network traffic management; Network resource management
  • H04W28/02—Traffic management, e.g. flow control or congestion control
  • H04W28/10—Flow control between communication endpoints
  • H04W28/12—Flow control between communication endpoints using signalling between network elements
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/10—Connection setup
  • H04W76/18—Management of setup rejection or failure
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
  • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/10—Connection setup
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
  • H04W88/02—Terminal devices
  • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user

Definitions

• Wireless mobile communication technology uses various standards and protocols to transmit data between a node (e.g., a transmission station) and a wireless device (e.g., a mobile device).
• Some wireless devices communicate using orthogonal frequency-division multiple access (OFDMA) in a downlink (DL) transmission and single carrier frequency division multiple access (SC-FDMA) in an uplink (UL) transmission.
• OFDM orthogonal frequency-division multiplexing
• LTE long term evolution
• IEEE Institute of Electrical and Electronics Engineers
• the node can be a 3GPP radio access network (RAN) LTE systems.
• RAN radio access network
• E-UTRAN Evolved Universal Terrestrial Radio Access Network
• Node Bs also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs
• RNCs Radio Network Controllers
• UE user equipment
• the downlink (DL) transmission can be a
• the communication from the node (e.g., eNodeB) to the wireless device (e.g., UE), and the uplink (UL) transmission can be a communication from the wireless device to the node.
• the node e.g., eNodeB
• the wireless device e.g., UE
• the uplink (UL) transmission can be a communication from the wireless device to the node.
• FIG. 1 illustrates a plurality of machine type communication (MTC) devices communicating radio resource control (RRC) connection request messages to an eNodeB in accordance with an example
• FIG. 2 illustrates a plurality of machine type communication (MTC) devices receiving radio resource control (RRC) connection reject messages from an eNodeB in accordance with an example
• FIG. 3 illustrates one or more machine type communication (MTC) devices communicating signaling information to a selected MTC device in accordance with an example
• FIG. 4 illustrates a selected machine type communication (MTC) device communicating an acknowledgement to one or more MTC devices in accordance with an example
• FIG. 5 illustrates a selected machine type communication (MTC) device communicating a radio resource control (RRC) connection request message to an eNodeB in accordance with an example
• FIG. 6 illustrates a selected machine type communication (MTC) device communicating aggregated signaling information for one or more MTC devices to an eNodeB in accordance with an example
• FIG. 7 illustrates a selected machine type communication (MTC) device communicating an accept or reject message to one or more MTC devices in accordance with an example
• FIG. 8 depicts functionality of an eNodeB operable to facilitate aggregated signaling from a plurality of devices in accordance with an example
• FIG. 9 depicts functionality of an aggregation machine type communication (MTC) device operable to aggregate signaling for a plurality of MTC devices in accordance with an example
• FIG. 10 depicts a flowchart of a machine readable storage medium having instructions embodied thereon for communicating small data from a user equipment (UE) to an eNodeB in accordance with an example;
• UE user equipment
• FIG. 11 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example
• FIG. 12 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example.
• UE wireless device
• MTC Machine Type Communication
• An MTC device can communicate over a network with MTC servers and/or other MTC devices.
• MTC devices can include health monitoring devices, smart meters, sensors, etc.
• MTC devices can communicate (i.e., send or receive) small amounts of data over the network.
• the small amount of data typically ranges from a few bits to kilobits of data.
• small data payloads can range from 1 to 128 bytes in length, but it should be understood that small data payloads can be larger in some instances.
• the small data is transmitted as a short data transfer in a single packet or burst.
• the network can be a wireless wide area network (WWAN) or a wireless local area network (WLAN) based on a selected radio access network (RAN) technology.
• the WWAN can be configured to operate based on a cellular networking standard, such as Third Generation Partnership Project (3GPP). Exemplary releases of the 3GPP standard include the 3 GPP LTE, Release 8 in the fourth quarter of 2008, 3 GPP LTE Advanced Release 10 in the first quarter of 2011, and 3GPP LTE Release 11 in the third quarter of 2012.
• 3GPP Third Generation Partnership Project
• the MTC applications that are executed on the MTC devices can be related to a variety of areas, such as security (e.g., surveillance systems, driver security), tracking and tracing (e.g., asset tracking, navigation, traffic information, road tolling), payment (e.g., vending machines, gaming machines), health (e.g., monitoring vital signs, supporting the elderly or handicapped), remote maintenance/control (e.g., sensors, lighting, vehicle diagnostics), metering (e.g., power, gas, water, heating), and/or consumer devices (e.g., digital cameras).
• security e.g., surveillance systems, driver security
• tracking and tracing e.g., asset tracking, navigation, traffic information, road tolling
• payment e.g., vending machines, gaming machines
• health e.g., monitoring vital signs, supporting the elderly or handicapped
• remote maintenance/control e.g., sensors, lighting, vehicle diagnostics
• metering e.g., power, gas, water, heating
• consumer devices
• UEs which can include MTC devices
• RRC radio resource control
• the eNodeB can receive the RRC connection request messages from the UEs, and in response, the eNodeB can transmit RRC connection reject messages to the UEs.
• the RRC connection reject messages can include a back off timer (or wait timer) and a deprioritization for the UE.
• the eNodeB can use different values for the back off timer depending on the user, such that the eNodeB can distribute the access load over a period of time.
• the back off timer can be randomly distributed to distribute the initiation of access of these UEs over the period of time.
• the eNodeB can prevent the UEs from further congesting the network.
• the UEs can again initiate a connection to the network. For example, the UEs can send another RRC connection request message to the eNodeB in order to attempt establishing a connection with the network.
• one problem with the legacy LTE cellular system with respect to MTC devices is signaling congestion control. Since the number of MTC devices in the network is expected to be high, even the number of MTC devices that wake up after expiry of the back off timer to initiate the connection to the network can still cause further congestion in the network. In current solutions, the number of UEs that connect to the network is relatively less so the back off timer mechanism is an effective solution, but the back off timer would not be an effective solution for the high number of MTC devices that are expected in upcoming years.
• a selected MTC device (also referred to as a phantom device) can aggregate signaling information from a plurality of MTC devices, and the selected MTC device can transmit the aggregated signaling information to the eNodeB.
• each of the MTC devices can transmit signaling information to the selected MTC device.
• the selected MTC device can aggregate the signaling information, and then send the aggregated signaling information to the eNodeB. As a result, individual signaling from each MTC device to the eNodeB is prevented, thereby reducing congestion in the network.
• the eNodeB when a plurality of MTC devices transmit RRC connection request messages to the eNodeB, the eNodeB can transmit RRC connection reject messages to the plurality of MTC devices. However, the eNodeB can select one of the plurality of MTC devices as the phantom device. For example, when the eNodeB sends the RRC connection reject message to the selected MTC device (or phantom device), the eNodeB provides a configuration (e.g., resources) that enables the selected MTC device to form a new cell. The new cell formed by the selected MTC device can also be referred to as a shadow cell.
• a configuration e.g., resources
• the new cell formed by the selected MTC device can have limited capabilities as compared to the cell formed by the eNodeB.
• the eNodeB can redirect the other MTC devices to the selected MTC device. In other words, the eNodeB can redirect the other MTC devices to camp on the new cell formed by the selected MTC device.
• each of the other MTC devices can transmit an RRC connection request message to the selected MTC device (or phantom device).
• This communication between the other MTC devices and the selected MTC device (or phantom device) can be a form of device-to-device (D2D) communication.
• the selected MTC device (or phantom device) can aggregate the RRC connection request messages from the other MTC devices to form aggregated signaling information, and the selected MTC device can transmit the aggregated signaling information to the eNodeB.
• the selected MTC device can concatenate or piggyback the aggregated signaling information with its own signaling information and/or small uplink data being transmitted to the eNodeB.
• the eNodeB can receive the aggregated signaling information from the selected MTC device, and the eNodeB can determine whether to accept or reject the RRC connection request from each of the other MTC devices.
• the eNodeB can transmit accept or reject messages to the selected MTC device, and the selected MTC device can forward the accept or reject messages to the other MTC devices.
• the LTE cellular system can support the increased volume of MTC devices without having to significantly delay UL signaling and small UL data.
• the number of RRC connection requests and RRC connection rejects for each MTC device can be reduced.
• cellular resources can be saved at the eNodeB.
• FIG. 1 illustrates an example of a plurality of user equipments (UEs), such as machine type communication (MTC) devices, in a network.
• the network can include an eNodeB 110 and a number of MTC devices.
• the MTC devices can be replaced with user equipments (UEs).
• the MTC devices can form a cluster of devices that surround the eNodeB 110.
• the MTC devices can have low mobility delay tolerant uplink (UL) data and signaling requirements.
• each of the MTC devices can communicate a radio resource control (RRC) connection request messages to the eNodeB 110.
• RRC radio resource control
• device A 112, device B 114, device C 116 and device D 118 can form the cluster of MTC devices that surround the eNodeB 110.
• device A 112, device B 114, device C 116 and device D 118 can each send an RRC connection request message to the eNodeB 110 in order to connect to the network.
• the RRC connection request message communicated from each of the MTC devices to the eNodeB 110 can be a periodic tracking area update (TAU) message.
• TAU periodic tracking area update
• the MTC device can transmit other control signal messages or data to the eNodeB 110.
• the MTC device can transmit non-access stratum (NAS) messages or upper layer application signaling messages.
• NAS non-access stratum
• the MTC devices can communicate the RRC connection request messages to the eNodeB 110 when the network is congested.
• the network can be congested when the amount of traffic at the eNodeB 110 exceeds a defined threshold.
• FIG. 2 illustrates an example of a plurality of machine type communication (MTC) devices receiving radio resource control (RRC) connection reject messages from an eNodeB 210.
• the eNodeB 210 can communicate the RRC connection reject messages to the plurality of MTC devices in response to receiving an RRC connection request message from each of the MTC devices, as shown in FIG. 1.
• the eNodeB 210 can send the RRC connection reject messages to the plurality of MTC devices when the network is congested.
• the eNodeB 210 can select one of the MTC devices as a phantom device. More specifically, the eNodeB 210 can send an RRC connection reject message to the selected MTC device (or phantom device), and the RRC connection reject message can include a configuration that enables the selected MTC device to form a new cell (also referred to as a shadow cell).
• the configuration in the RCC connection reject message communicated to the selected MTC device can include a selected Evolved Universal Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN) and a selected physical cell identifier (PCI).
• E-UTRA Evolved Universal Terrestrial Radio Access
• E-UTRA Absolute Radio Frequency Channel Number
• PCI selected physical cell identifier
• the selected EARFCN and the selected PCI can enable the selected MTC device to form the new cell (or shadow cell).
• the eNodeB 210 can select the EARFCN and PCI for the selected MTC device (or phantom device) such that the EARFCN and PCI causes a minimum amount of interference to the cellular operating frequencies.
• the new cell (or shadow cell) formed by the selected MTC device has limited capabilities as compared to the cell formed by the eNodeB 210.
• the selected MTC device (or phantom device) that forms the new cell can broadcast a minimum set of information to allow for other MTC devices to connect to the selected MTC device.
• the selected MTC device can broadcast a master information block (MIB), a system information block 1 (SIB1) and a system information block 2 (SIB2), which can allow for the other MTC devices to connect to the selected MTC device.
• MIB master information block
• SIB1 system information block 1
• SIB2 system information block 2
• the selected MTC device (or phantom device) that forms the new cell can only allow for camping by the other MTC devices and sending/receiving data to the other MTC devices.
• the selected MTC device may be unable to perform reselection, handover and other cellular eNodeB capabilities. As such, smaller and less capable devices can also form the new cell.
• the new cell (or shadow cell) can be a lower capability cell, but with enough capability to perform data transfer. In some cases, the new cell can have
• the eNodeB 210 can use various selection criteria when determining which MTC device from the plurality of MTC devices is best suited to act as the phantom device. For example, the eNodeB 210 can select the MTC device based on a type of power source associated with the MTC device. If the MTC device is connected to a dedicated power source, then the MTC device can be more likely to be selected as the phantom device.
• each of the plurality of MTC devices can communicate a capability message to the eNodeB 210 that includes various capabilities or characteristics (e.g., type of power source) associated with the MTC device, and the eNodeB 210 can select a particular MTC device to act as the phantom device and form the new cell (or shadow cell) based on the capability messages received from the plurality of MTC devices.
• the capability message can be communicated from the MTC devices to the eNodeB 210 during an attach procedure.
• the capability message communicated to the eNodeB 210 can indicate whether a particular MTC device is able to form a new cell (or host a new cell).
• the MTC device can use its own algorithm for determining whether or not the MTC device is able to form the new cell. For example, the MTC device can set a flag in the capability message to "true” or "false” depending on whether or not the MTC device is able to form the new cell.
• the MTC device can set the flag to "true” based on current battery conditions of the MTC device and/or based on monetization factors (e.g., the MTC device can set the flag to "true” when a network operator has provided compensation for the MTC device to host the new cell).
• each RRC connection reject message can include a redirection to the new cell formed by the selected MTC device (or phantom device).
• the redirection in each of the RRC connection reject messages can include the EARFCN and the PCI that are associated with the selected MTC device (or phantom device).
• the inclusion of the EARFCN and the PCI can enable the other MTC devices to redirect signaling to the selected MTC device, as opposed to the eNodeB 210.
• each RRC connection reject message can include additional information that enables the selected MTC device to form the new cell.
• the redirection to the new cell causes signaling from the other MTC devices to be redirected or offloaded to the selected MTC device (or phantom device) as opposed to the eNodeB 210.
• the selected MTC device can handle much of the signaling from the other MTC devices, as opposed to the eNodeB 210. As a result, the amount of signaling to the eNodeB 210 is reduced, thereby reducing or alleviating congestion in the network.
• the plurality of MTC devices that each receive an RRC connection reject message from the eNodeB 210 can include device A 212, device B 214, device C 216 and device D 218. Based on capability information received from each of device A 212, device B 214, device C 216 and device D 218, the eNodeB 210 can select device B 214 as the phantom device. Therefore, the RRC connection reject message communicated from the eNodeB 210 to device B 214 (the phantom device) can include a new EARFCN and a PCI that is set to a value of 500.
• the RRC connection reject messages that are communicated from the eNodeB 210 to each of device A 212, device C 216 and device D 218 can include a redirection to device B 214 (the phantom device), wherein the redirection includes the new EARFCN and the PCI that is set to the value of 500. Based on the redirection included in the RRC connection reject messages, device A 212, device C 216 and device D 218 can camp on (or connect to) device B 214 (the phantom device).
• FIG. 3 illustrates an example of one or more machine type communication (MTC) devices communicating signaling to a selected MTC device.
• MTC machine type communication
• an eNodeB 310 can select one MTC device from a plurality of MTC devices to act as a phantom device, and the selected MTC device can form a new cell (or shadow cell) with limited capabilities.
• the other MTC devices i.e., the other MTC devices that are not selected as the phantom device
• signaling from the other MTC devices can be redirected to the selected MTC device, as opposed to being communicated to the eNodeB 310.
• the other MTC devices can each communicate an RRC connection request message to the selected MTC device (or phantom device).
• the other MTC devices can each communicate a tracking area update (TAU) message to the selected MTC device (or phantom device).
• TAU tracking area update
• the other MTC devices can transmit the TAU messages directly to the selected MTC device, rather than transmitting the TAU messages to the eNodeB 310, thereby reducing the amount of signaling at the eNodeB 310.
• the other MTC devices can transmit non-access stratum (NAS) messages or upper layer application signaling messages to the selected MTC device.
• NAS non-access stratum
• device B 314 can be selected as the phantom device, and device B 314 can form the new cell with limited capabilities.
• Device A 312, device C 316 and device D 318 can be redirected by the eNodeB 310 to communicate directly with device B 314, as opposed to communicating with the eNodeB 310.
• Device A 312, device C 316 and device D 318 can each transmit a tracking area update (TAU) message to the device B 314 (or phantom device).
• TAU tracking area update
• FIG. 4 illustrates an example of a selected machine type communication (MTC) device communicating an acknowledgement to one or more MTC devices.
• MTC machine type communication
• the selected MTC device (or phantom device) can receive signaling directly from the one or more MTC devices.
• the one or more MTC devices can send signaling to the selected MTC device, as opposed to sending the signaling to an eNodeB 410.
• the selected MTC device (or phantom device) can receive a tracking area update (TAU) message from each of the one or more MTC devices.
• TAU tracking area update
• MTC device (or phantom device) can transmit an acknowledgement (ACK) to each of the one or more MTC devices.
• ACK acknowledgement
• the ACK is not a confirmation of the TAU, but rather a confirmation that the transmission of the TAU message was successful.
• device B 414 can be selected as the phantom device, and device B 314 can form the new cell with limited capabilities.
• Device A 412, device C 416 and device D 418 can each transmit a tracking area update (TAU) message to the device B 414 (or phantom device).
• TAU tracking area update
• device B 414 (or phantom device) can transmit an acknowledgement (ACK) to each of device A 412, device C 416 and device D 418.
• ACK acknowledgement
• the selected MTC device can aggregate or concatenate or piggyback the signaling from the one or more MTC devices along with the selected MTC device's own signaling.
• the selected MTC device can aggregate or concatenate or piggyback periodic TAU messages received from the one or more MTC devices along with the selected MTC device's own periodic TAU message.
• FIG. 5 illustrates an example of a selected machine type communication (MTC) device communicating a radio resource control (RRC) connection request message to an eNodeB 510.
• the selected MTC device (or phantom device) can indicate a defined number of MTC devices in the RRC connection request message, wherein the defined number indicates the number of MTC devices for which the selected MTC device is transmitting aggregated or concatenated or piggybacked signaling information.
• one or more MTC devices can send signaling to the selected MTC device, the selected MTC device can aggregate or concatenate or piggyback the signaling from the one or more MTC devices, and then the selected MTC device can indicate the number of MTC devices for which the selected MTC device is transmitting aggregated or concatenated or piggybacked signaling information.
• the eNodeB 510 can receive the RRC connection request message from the selected MTC device (or phantom device) which indicates the number of MTC devices for which the selected MTC device is transmitted aggregated signaling information.
• the eNodeB 510 can perform an RRC connection setup with the selected MTC device, in which the eNodeB 510 assigns an increased priority level for the signaling requests received from the selected MTC device.
• the eNodeB 510 can allocate resources for receiving the aggregated signaling information from the selected MTC device.
• device B 514 can be selected as the phantom device, and device B 514 can form the new cell with limited capabilities.
• Device A 512, device C 516 and device D 518 can each transmit a tracking area update (TAU) message to the device B 514 (or phantom device).
• Device B 514 (or phantom device) can transmit an RRC connection request message to the eNodeB 510, wherein the RRC connection request message can indicate the number of MTC devices for which the TAU is to be updated. In other words, the RRC connection request message can indicate the number of MTC devices for which device B 514 (the phantom device) is sending piggy backed TAU messages.
• the RRC connection request message can indicate three MTC devices, which corresponds to device A 512, device C 516 and device D 518.
• the eNodeB 510 can initiate an RRC connection setup procedure with device B 514 (or phantom device) to perform the TAU.
• the eNodeB 510 can assign an increased priority level for the TAU messages received from device B 514, and the eNodeB 510 can allocate resources for receiving the periodic TAU messages.
• FIG. 6 illustrates an example of a selected machine type communication (MTC) device communicating aggregated signaling information for one or more MTC devices to an eNodeB 610.
• MTC machine type communication
• the selected MTC device (or phantom device) can receive signaling information from one or more MTC devices, and the selected MTC device can aggregate the signaling information along with the selected MTC device's own signaling.
• the eNodeB 610 can allocate resources to the selected MTC device, and using the resources, the selected MTC device can transmit the aggregated signaling information to the eNodeB 610.
• the aggregated signaling information can include periodic tracking area update (TAU) messages for the one or more MTC devices, as well as the selected MTC device's own periodic TAU message.
• TAU tracking area update
• the eNodeB 610 can receive the aggregated signaling information from the selected MTC device.
• the eNodeB 610 can determine that it is receiving aggregated signaling information since the signaling information is coming from the selected MTC device (or phantom device). Since the eNodeB 610 knows that it is receiving aggregated signaling information and that signaling received from the selected MTC device (or phantom device) is assigned the higher priority level, the eNodeB 610 is less likely to reject the aggregated signaling information.
• the eNodeB 610 can send to the selected MTC device (or phantom device) either an accept message or a reject message for each of the one or more MTC devices.
• the eNodeB 610 can send an accept message to indicate that the MTC device is permitted to connect to the eNodeB 610, or the eNodeB 610 can send a reject message to indicate that the MTC device is not permitted to connect to the eNodeB 610.
• the eNodeB 610 can transmit an accept message for all of the MTC devices that are requesting to connect to the eNodeB 610.
• the eNodeB 610 can transmit an accept message for some MTC devices, while transmitting a reject message to other MTC devices.
• device B 614 can be selected as the phantom device, and device B 614 can form the new cell with limited capabilities.
• Device A 612, device C 616 and device D 618 can each transmit a tracking area update (TAU) message to the device B 614 (or phantom device).
• TAU tracking area update
• Device B 614 can aggregate the TAU messages received from device A 612, device C 616 and device D 618, respectively, and transmit the aggregated TAU messages to the eNodeB 610. In other words, device B 614 can piggy back the TAU messages received from device A 612, device C 616 and device D 618 onto device B's own periodic TAU message.
• the eNodeB 610 can send to device B 614 an accept message or a reject message for each of device A 612, device C 616 and device D 618, respectively.
• the eNodeB 610 can transmit to device B 614 an accept message for device A 612 and reject messages for device C 616 and device D 618.
• FIG. 7 illustrates an example of a selected machine type communication (MTC) device communicating an accept or reject message to one or more MTC devices.
• MTC machine type communication
• the selected MTC device (or phantom device) can receive, from an eNodeB 710, an accept message or reject message for each of the one or more MTC devices. Therefore, the selected MTC device can forward an accept message or reject message to each of the one or more MTC devices.
• the selected MTC device can instruct each of the one or more MTC devices to detach from the selected MTC device (or phantom device).
• the one or more MTC devices can now connect to the eNodeB 710 and do not necessarily have to maintain a connection with the selected MTC device (or phantom device).
• device B 714 can be selected as the phantom device, and device B 714 can form the new cell with limited capabilities.
• Device A 712, device C 716 and device D 718 can each transmit a tracking area update (TAU) message to the device B 714 (or phantom device).
• Device B 714 can transmit aggregated TAU messages to the eNodeB 710, and the eNodeB 710 can respond with an accept or reject message for each of device A 712, device C 716 and device D 718, respectively.
• Device B 714 (or phantom device) can forward the accept or reject message to each of device A 712, device C 716 and device D 718, respectively.
• each of device A 712, device C 716 and device D 718 can detach from device B 714 (or phantom device).
• the one or more MTC devices can automatically attempt to perform TAU with the selected MTC device (or phantom device).
• the one or more MTC devices can automatically send the periodic TAU messages to the selected MTC device (or phantom device), and the selected MTC device can aggregate the TAU messages and send aggregated TAU messages to the eNodeB (as described earlier). If the one or more MTC devices are unsuccessful in sending the periodic TAU messages to the selected MTC device (or phantom device), or if the selected MTC device is no longer configured as the phantom device, then the one or more MTC devices can send the periodic TAU messages directly to the eNodeB.
• the period of time for which the selected MTC device continues to function as the phantom device is configured by the network.
• the network can configure the selected MTC device to function as the phantom device for several hours.
• the network can configure the selected MTC device to function as the phantom device for a certain period of time every day.
• the eNodeB can select a particular MTC device to function as a phantom device and form a new cell (or shadow cell). Other MTC devices can be redirected to the selected MTC device. For example, when the other MTC devices wish to send uplink data (e.g., sensor data, temperature data) to the eNodeB 710, the other MTC devices can send the data to the selected MTC device. The selected MTC device can aggregate the data, and then send the aggregated data to the eNodeB 710. Therefore, in addition to aggregating signaling information (as described earlier), the selected MTC device can also aggregate uplink data from the other MTC devices.
• uplink data e.g., sensor data, temperature data
• the selected MTC device can aggregate the data, and then send the aggregated data to the eNodeB 710. Therefore, in addition to aggregating signaling information (as described earlier), the selected MTC device can also aggregate uplink data from the other MTC devices.
• the selected MTC device can act as a relay between the other MTC devices and the eNodeB 710.
• signaling overhead can be reduced and/or more efficiently managed at the eNodeB 710.
• a group of MTC devices can send a short messaging service (SMS) to the selected MTC device (or phantom device).
• SMS short messaging service
• the selected MTC device can aggregate the SMS messages received from the group of MTC devices, and then send an aggregated SMS message to the eNodeB.
• a group of MTC device can be configured to send a burst of data (e.g., 100 packets) every 24 hours. Rather than communicating the data directly to the eNodeB, the MTC devices can communicate the data to the selected MTC device (or phantom device), and the selected MTC device can aggregate the data and send the aggregated data to the eNodeB.
• the formation of the cell and redirection to the cell can be achieved via radio resource control (RRC) reconfiguration messages.
• RRC radio resource control
• an eNodeB can send an RRC reconfiguration message to a selected MTC device, wherein the RRC reconfiguration message includes a configuration that causes the selected MTC device to form the cell.
• the cell formed by the selected MTC device can include a selected subset of MTC devices.
• the selected MTC device can form a reduced capacity cell, in which the selected MTC device is only configured to transmit a master information block (MIB), a system information block 1 (SIB1) and a SIB2.
• the eNodeB can transmit an RRC reconfiguration message to the selected subset of devices, wherein the RRC reconfiguration message includes a redirection to the cell formed by the selected MTC device.
• the eNodeB can utilize RRC reconfiguration messages.
• a series of actions can be performed at an eNodeB and one or more MTC devices in order to reduce signaling congestion at the eNodeB.
• a plurality of co-located MTC devices can simultaneously initiate periodic TAU control signaling to the eNodeB when the network is congested.
• the eNodeB can select one of the MTC devices as a phantom device, and the other MTC devices are redirected to the phantom device.
• the other MTC devices can camp on the phantom device and send their periodic TAU messages to the phantom device.
• the phantom device can send ACKs for the periodic TAU messages that have been received.
• the phantom device can concatenate or piggyback the periodic TAU messages of the other MTC devices along with the phantom device's own periodic TAU message.
• the phantom device can send an RRC connection request to the eNodeB that indicates a number of MTC devices for which the phantom device is sending piggy backed TAU messages, and the eNodeB provides resources to the phantom device for sending the periodic TAU messages.
• the phantom device can send the piggy backed TAU messages to the eNodeB, and the eNodeB can send a TAU accept message or a TAU reject message for each of the MTC devices.
• the phantom device can send the received TAU accept/reject messages to the MTC devices, as well as an instruction for the MTC devices to detach from the phantom device.
• the MTC devices can initially attempt to perform TAU using the phantom device.
• Another example provides functionality 800 of an eNodeB operable to facilitate aggregated signaling from a plurality of devices, as shown in the flow chart in FIG 8.
• the functionality can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included on at least one computer readable medium or one non-transitory machine readable storage medium.
• the eNodeB can comprise one or more processors and memory configured to: receive, at the eNodeB, a connection request message from each of the plurality of devices, as in block 810.
• the eNodeB can comprise one or more processors and memory configured to: select, at the eNodeB, a device from the plurality of devices using a set of selection criteria, as in block 820.
• the eNodeB can comprise one or more processors and memory configured to: send, to the selected device, a connection reject message that includes a configuration that causes the selected device to form a cell comprising a selected subset of devices of the plurality of devices, as in block 830.
• the eNodeB can comprise one or more processors and memory configured to: send, to the selected subset of devices, a connection reject message that includes a redirection to the cell formed by the selected device, wherein each of the devices in the selected subset are configured to transmit a connection request message to the selected device based on the redirection to the cell, as in block 840.
• Another example provides functionality 900 of an aggregation machine type communication (MTC) device operable to aggregate signaling for a plurality of MTC devices, as shown in the flow chart in FIG. 9.
• the functionality can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included on at least one computer readable medium or one non-transitory machine readable storage medium.
• the aggregation MTC device can comprise one or more processors and memory configured to: send, to an eNodeB, a connection request message, as in block 910.
• the aggregation MTC device can comprise one or more processors and memory configured to: receive, from the eNodeB, a connection reject message that includes a configuration that instructs the aggregation MTC device to form a cell, wherein the eNodeB is configured to select the aggregation MTC device to form the cell based on a set of selection criteria, as in block 920.
• the aggregation MTC device can comprise one or more processors and memory configured to: receive, at the aggregation MTC device, a connection request message from one or more MTC devices in the cell, wherein the eNodeB is configured to redirect control signaling from the one or more MTC devices in the cell to the aggregation MTC device, as in block 930.
• the aggregation MTC device can comprise one or more processors and memory configured to: transmit, from the aggregation MTC device, an aggregated connection request message that includes the connection request message received from the one or more MTC devices in the cell, as in block 940.
• Another example provides at least one machine readable storage medium having instructions 1000 embodied thereon for communicating small data from a user equipment (UE) to an eNodeB, as shown in the flow chart in FIG. 10.
• the instructions can be executed on a machine, where the instructions are included on at least one computer readable medium or one non-transitory machine readable storage medium.
• the instructions when executed perform: receiving, using one or more processors of the UE, a radio resource control (RRC) reconfiguration message from the eNodeB, wherein the RRC reconfiguration message includes a redirection to a selected aggregation UE that is hosting a cell, wherein the eNodeB chooses the selected aggregation UE to host the cell based on a capability of the selected aggregation UE, as in block 1010.
• RRC radio resource control
• the instructions when executed perform: transmitting, using the one or more processors of the UE, data to the selected aggregation UE based on the redirection included in the RRC reconfiguration message received from the eNodeB, wherein the selected aggregation UE is configured to forward the data to the eNodeB, as in block 1020.
• FIG. 11 provides an example illustration of a user equipment (UE) device 1100, such as a wireless device, a mobile station (MS), a machine type communication (MTC) device, a mobile wireless device, a mobile communication device, a tablet, a handset, or other type of wireless device.
• the UE device 1100 can include one or more antennas configured to communicate with a node or transmission station, such as a base station (BS), an evolved Node B (eNB), a baseband unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE), a remote radio unit (RRU), a central processing module (CPM), or other type of wireless wide area network (WWAN) access point.
• BS base station
• eNB evolved Node B
• BBU baseband unit
• RRH remote radio head
• RRE remote radio equipment
• RS relay station
• RE radio equipment
• RRU remote radio unit
• CCM central processing module
• the UE device 1100 can be configured to communicate using at least one wireless communication standard including 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi.
• the UE device 1100 can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards.
• the UE device 1100 can communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a WWAN.
• WLAN wireless local area network
• WPAN wireless personal area network
• WWAN wireless wide area network
• the UE device 1100 may include application circuitry 1102, baseband circuitry 1104, Radio Frequency (RF) circuitry 1106, front-end module (FEM) circuitry 1108 and one or more antennas 1110, coupled together at least as shown.
• application circuitry 1102 baseband circuitry 1104, Radio Frequency (RF) circuitry 1106, front-end module (FEM) circuitry 1108 and one or more antennas 1110, coupled together at least as shown.
• RF Radio Frequency
• FEM front-end module
• the application circuitry 1102 may include one or more application processors.
• the application circuitry 1102 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
• the processor(s) may include any combination of general -purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
• the processors may be coupled with and/or may include a storage medium 1112 and may be configured to execute instructions stored in the storage medium 1112 to enable various applications and/or operating systems to run on the system.
• the baseband circuitry 1104 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
• the baseband circuitry 1104 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 1106 and to generate baseband signals for a transmit signal path of the RF circuitry 1106.
• Baseband processing circuity 1104 may interface with the application circuitry 1102 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1106.
• the baseband circuitry 1104 may include a second generation (2G) baseband processor 1104a, third generation (3G) baseband processor 1104b, fourth generation (4G) baseband processor 1104c, and/or other baseband processor(s) 1104d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6Q etc.).
• the baseband circuitry 1104 e.g., one or more of baseband processors 1104a-d
• the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
• modulation/demodulation circuitry of the baseband circuitry 1104 may include Fast-Fourier Transform (FFT), precoding, and/or constellation
• encoding/decoding circuitry of the baseband circuitry 1104 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality
• LDPC Low Density Parity Check
• the baseband circuitry 1104 may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol
• EUTRAN evolved universal terrestrial radio access network
• PHY physical
• MAC media access control
• RLC radio link control
• a central processing unit (CPU) 1104e of the baseband circuitry 1104 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers.
• the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 1104f.
• the audio DSP(s) 104f may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
• Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
• some or all of the constituent components of the baseband circuitry 1104 and the application circuitry 1102 may be implemented together such as, for example, on a system on a chip (SOC).
• SOC system on a chip
• the baseband circuitry 1104 may provide for
• the baseband circuitry 1104 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
• EUTRAN evolved universal terrestrial radio access network
• WMAN wireless metropolitan area networks
• WLAN wireless local area network
• WPAN wireless personal area network
• multi-mode baseband circuitry Embodiments in which the baseband circuitry 1104 is configured to support radio communications of more than one wireless protocol.
• the RF circuitry 1106 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
• the RF circuitry 1106 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
• RF circuitry 1106 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1108 and provide baseband signals to the baseband circuitry 1104.
• RF circuitry 1106 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1104 and provide RF output signals to the FEM circuitry 1108 for transmission.
• the RF circuitry 1106 may include a receive signal path and a transmit signal path.
• the receive signal path of the RF circuitry 1106 may include mixer circuitry 1106a, amplifier circuitry 1106b and filter circuitry 1106c.
• the transmit signal path of the RF circuitry 1106 may include filter circuitry 1106c and mixer circuitry 1106a.
• RF circuitry 1106 may also include synthesizer circuitry 1106d for synthesizing a frequency for use by the mixer circuitry 1106a of the receive signal path and the transmit signal path.
• the mixer circuitry 1106a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 1108 based on the synthesized frequency provided by synthesizer circuitry 1106d.
• the amplifier circuitry 1106b may be configured to amplify the down-converted signals and the filter circuitry 1106c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
• LPF low-pass filter
• BPF band-pass filter
• Output baseband signals may be provided to the baseband circuitry 1104 for further processing.
• the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
• mixer circuitry 1106a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
• the mixer circuitry 1106a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1106d to generate RF output signals for the FEM circuitry 1108.
• the baseband signals may be provided by the baseband circuitry 1104 and may be filtered by filter circuitry 1106c.
• the filter circuitry 1106c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.
• LPF low-pass filter
• the mixer circuitry 1106a of the receive signal path and the mixer circuitry 1106a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and/or up-conversion respectively.
• the mixer circuitry 1106a of the receive signal path and the mixer circuitry 1106a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
• the mixer circuitry 1106a of the receive signal path and the mixer circuitry 1106a may be arranged for direct down-conversion and/or direct up-conversion, respectively.
• the mixer circuitry 1106a of the receive signal path and the mixer circuitry 1106a of the transmit signal path may be configured for super-heterodyne operation.
• the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
• the output baseband signals and the input baseband signals may be digital baseband signals.
• the RF circuitry 1106 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1104 may include a digital baseband interface to communicate with the RF circuitry 1106.
• ADC analog-to-digital converter
• DAC digital-to-analog converter
• a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
• the synthesizer circuitry 1106d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
• synthesizer circuitry 1106d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
• the synthesizer circuitry 1106d may be configured to synthesize an output frequency for use by the mixer circuitry 1106a of the RF circuitry 1106 based on a frequency input and a divider control input.
• the synthesizer circuitry 1106d may be a fractional N/N+l synthesizer.
• frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
• VCO voltage controlled oscillator
• Divider control input may be provided by either the baseband circuitry 1104 or the applications processor 1102 depending on the desired output frequency.
• a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 1102.
• Synthesizer circuitry 1106d of the RF circuitry 1106 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
• the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA).
• the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio.
• the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
• the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
• Nd is the number of delay elements in the delay line.
• synthesizer circuitry 1106d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
• the output frequency may be a LO frequency (fLO).
• the RF circuitry 1106 may include an IQ/polar converter.
• FEM circuitry 1108 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1110, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1106 for further processing.
• FEM circuitry 1108 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1106 for transmission by one or more of the one or more antennas 1110.
• the FEM circuitry 1108 may include a TX/RX switch to switch between transmit mode and receive mode operation.
• the FEM circuitry may include a receive signal path and a transmit signal path.
• the receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1106).
• LNA low-noise amplifier
• the transmit signal path of the FEM circuitry 1108 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1106), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1110.
• PA power amplifier
• FIG. 12 provides an example illustration of the wireless device, such as a user equipment (UE), a mobile station (MS), a mobile wireless device, a mobile
• the wireless device can include one or more antennas configured to communicate with a node, macro node, low power node (LPN), or, transmission station, such as a base station (BS), an evolved Node B (eNB), a baseband processing unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE), or other type of wireless wide area network (WWAN) access point.
• the wireless device can be configured to communicate using at least one wireless communication standard such as, but not limited to, 3 GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi.
• the wireless device can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards.
• the wireless device can communicate in a wireless local area network
• the wireless device can also comprise a wireless modem.
• the wireless modem can comprise, for example, a wireless radio transceiver and baseband circuitry (e.g., a baseband processor).
• the wireless modem can, in one example, modulate signals that the wireless device transmits via the one or more antennas and demodulate signals that the wireless device receives via the one or more antennas.
• FIG. 12 also provides an illustration of a microphone and one or more speakers that can be used for audio input and output from the wireless device.
• the display screen can be a liquid crystal display (LCD) screen, or other type of display screen such as an organic light emitting diode (OLED) display.
• the display screen can be configured as a touch screen.
• the touch screen can use capacitive, resistive, or another type of touch screen technology.
• An application processor and a graphics processor can be coupled to internal memory to provide processing and display capabilities.
• a non-volatile memory port can also be used to provide data input/output options to a user.
• the non-volatile memory port can also be used to expand the memory capabilities of the wireless device.
• a keyboard can be integrated with the wireless device or wirelessly connected to the wireless device to provide additional user input.
• a virtual keyboard can also be provided using the touch screen.
• Example 1 includes an apparatus of an eNodeB operable to facilitate aggregated signaling from a plurality of devices, the apparatus comprising one or more processors and memory configured to: receive, at the eNodeB, a connection request message from each of the plurality of devices; select, at the eNodeB, a device from the plurality of devices using a set of selection criteria; send, to the selected device, a connection reject message that includes a configuration that causes the selected device to form a cell comprising a selected subset of devices of the plurality of devices; and send, to the selected subset of devices, a connection reject message that includes a redirection to the cell formed by the selected device, wherein each of the devices in the selected subset are configured to transmit a connection request message to the selected device based on the redirection to the cell.
• Example 2 includes the apparatus of Example 1, further configured to: receive, from the selected device, an aggregated connection request message that includes the connection request message for each of the devices in the selected subset; and transmit, to the selected device, an accept message or a reject message for each of the devices in the selected subset, wherein the selected device is configured to forward the accept message or the reject message to each of the devices in the selected subset.
• Example 3 includes the apparatus of any of Examples 1-2, further configured to: receive, from the selected device, a connection request message that indicates a number of devices in the selected subset for which the selected device is to transmit connection request messages to the eNodeB; and send, to the selected device, a connection setup message that includes an allocation of resources for the transmission of the aggregated connection request message for the selected subset of devices.
• Example 4 includes the apparatus of any of Examples 1-3, wherein the aggregated connection request message received at the eNodeB from the selected device is prioritized over other connection request messages received at the eNodeB from other devices in a network.
• Example 5 includes the apparatus of any of Examples 1-4, further configured to select the device from the plurality of devices based on a capability message that is received from the device, wherein the capability message indicates a type of power source associated with the device.
• Example 6 includes the apparatus of any of Examples 1-5, further configured to select the device from the plurality of devices based on a capability message that is received from the device, wherein the capability message indicates that the device is able to form the cell.
• Example 7 includes the apparatus of any of Examples 1-6, further configured to receive, at the eNodeB, data from the selected subset of devices via the selected device, wherein the selected subset of devices are configured to transmit the data to the selected device based on the redirection to the cell formed by the selected device, wherein the selected device is configured to forward aggregated data to the eNodeB.
• Example 8 includes the apparatus of any of Examples 1-7, wherein the configuration in the connection reject message communicated to the selected device includes at least one of: a selected Evolved Universal Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN), a selected physical cell identifier (PCI) for the selected device and additional information for forming the cell.
• E-UTRA Evolved Universal Terrestrial Radio Access
• E-UTRA Absolute Radio Frequency Channel Number
• PCI physical cell identifier
• Example 9 includes the apparatus of any of Examples 1-8, wherein the connection reject message communicated to the selected subset of devices includes the redirection to a selected Evolved Universal Terrestrial Radio Access (E-UTRA) Absolute Radio
• E-UTRA Evolved Universal Terrestrial Radio Access
• connection reject message includes system information associated with the redirection.
• Example 10 includes the apparatus of any of Examples 1-9, wherein the accept message or the reject message transmitted to the selected device for each of the devices in the selected subset includes an instruction for the selected subset of devices to detach from the selected device.
• Example 11 includes the apparatus of any of Examples 1-10, wherein the connection request message received from each of the plurality of devices is one of: a tracking area update (TAU) message, a non-access stratum (NAS) message, or an upper layer application signaling message.
• TAU tracking area update
• NAS non-access stratum
• Example 12 includes the apparatus of any of Examples 1-11, wherein the connection request message and the connection reject message are radio resource control (RRC) messages.
• RRC radio resource control
• Example 13 includes the apparatus of any of Examples 1 -12, wherein the eNodeB is operable to configure the defined device to form the cell during network congestion.
• Example 14 includes the apparatus of any of Examples 1 -13, wherein the selected device is a machine type communication (MTC) device.
• MTC machine type communication
• Example 15 includes an apparatus of an aggregation machine type communication (MTC) device operable to aggregate signaling for a plurality of MTC devices, the apparatus comprising one or more processors and memory configured to: send, to an eNodeB, a connection request message; receive, from the eNodeB, a connection reject message that includes a configuration that instructs the aggregation MTC device to form a cell, wherein the eNodeB is configured to select the aggregation MTC device to form the cell based on a set of selection criteria; receive, at the aggregation MTC device, a connection request message from one or more MTC devices in the cell, wherein the eNodeB is configured to redirect control signaling from the one or more MTC devices in the cell to the aggregation MTC device; and transmit, from the aggregation MTC device, an aggregated connection request message that includes the connection request message received from the one or more MTC devices in the cell.
• MTC machine type communication
• Example 16 includes the apparatus of Example 15, further configured to: receive, from the eNodeB, an accept message or a reject message for each of the one or more MTC devices; and forward the accept message or the reject message to each of the one or more MTC devices.
• Example 17 includes the apparatus of any of Examples 15-16, further configured to transmit, from the aggregation MTC device, an acknowledgement (ACK) to the one or more MTC devices in response to the connection request message received from the one or more MTC devices.
• ACK acknowledgement
• Example 18 includes the apparatus of any of Examples 15-17, further configured to: transmit, to the eNodeB, a connection request message that indicates a number of MTC devices for which the aggregation MTC device is to transmit connection request messages to the eNodeB; and receive, from the eNodeB, a connection setup message that includes an allocation of resources for the transmission of the aggregated connection request message from the aggregation MTC device to the eNodeB.
• Example 19 includes the apparatus of any of Examples 15-18, further configured to receive additional connection request messages directly from the one or more MTC devices, wherein the one or more MTC devices are configured to bypass the eNodeB and communicate additional connection request messages directly to the aggregation MTC device.
• Example 20 includes the apparatus of any of Examples 15-19, further configured to communicate a capability message to the eNodeB that indicates a type of power source associated with the aggregation MTC device, wherein the eNodeB is configured to select the aggregation MTC device to form the cell based, in part, on the capability message received from the aggregation MTC device.
• Example 21 includes the apparatus of any of Examples 15-20, wherein the configuration in the connection reject message received from the eNodeB includes a selected Evolved Universal Terrestrial Radio Access (E-UTRA) Absolute Radio
• E-UTRA Evolved Universal Terrestrial Radio Access
• Frequency Channel Number (EARFCN) and a selected physical cell identifier (PCI) for the aggregation MTC device.
• Example 22 includes the apparatus of any of Examples 15-21, wherein the aggregated connection request message includes a connection request message that is associated with the aggregation MTC device.
• Example 23 includes the apparatus of any of Examples 15-22, wherein the connection request message received from each of the one or more MTC devices is a tracking area update (TAU) message.
• TAU tracking area update
• Example 24 includes the apparatus of any of Examples 15-23, further configured to: receive data from the one or more MTC devices, wherein the one or more MTC devices are configured to transmit data for the eNodeB to the aggregation MTC device based on a redirection to the cell formed by the aggregation MTC device; and forward the data from the aggregation MTC device to the eNodeB.
• Example 25 includes the apparatus of any of Examples 15-24, wherein the aggregation MTC device forms a reduced capacity cell and the aggregation MTC device is configured to only transmit a master information block (MIB), a system information block 1 (SIB1) and a SIB2.
• MIB master information block
• SIB1 system information block 1
• SIB2 system information block 1
• Example 26 includes at least one machine readable storage medium having instructions embodied thereon for communicating small data from a user equipment (UE) to an eNodeB, the instructions when executed perform the following: receiving, using one or more processors of the UE, a radio resource control (RRC) reconfiguration message from the eNodeB, wherein the RRC reconfiguration message includes a redirection to a selected aggregation UE that is hosting a cell, wherein the eNodeB chooses the selected aggregation UE to host the cell based on a capability of the selected aggregation UE and the eNodeB instructs the selected aggregation UE to host the cell based on an RRC reconfiguration message communicated from the eNodeB to the selected aggregation UE; and transmitting, using the one or more processors of the UE, small data to the selected aggregation UE via a device-to-device (D2D) connection between the UE and the selected aggregation UE
• Example 27 includes the at least one machine readable storage medium of Example 26, wherein the redirection received from the eNodeB includes a selected Evolved Universal Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN) and a selected physical cell identifier (PCI) that are associated with the selected aggregation UE.
• E-UTRA Evolved Universal Terrestrial Radio Access
• E-UTRA Absolute Radio Frequency Channel Number
• PCI physical cell identifier
• Example 28 includes the at least one machine readable storage medium of any of Examples 26-27, wherein the UE and the selected aggregation UE are machine type communication (MTC) devices.
• MTC machine type communication
• Example 29 includes the at least one machine readable storage medium of any of Examples 26-28, wherein the UE includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, a baseband processor, an internal memory, a non- volatile memory port, and combinations thereof.
• Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, compact disc-read-only memory (CD-ROMs), hard drives, non-transitory computer readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques.
• a non-transitory computer readable storage medium can be a computer readable storage medium that does not include signal.
• the computing device may include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device.
• the volatile and non-volatile memory and/or storage elements may be a random-access memory (RAM), erasable
• the node and wireless device may also include a transceiver module (i.e., transceiver), a counter module (i.e., counter), a processing module (i.e., processor), and/or a clock module (i.e., clock) or timer module (i.e., timer).
• a transceiver module i.e., transceiver
• a counter module i.e., counter
• a processing module i.e., processor
• a clock module i.e., clock
• timer module i.e., timer
• One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like.
• API application programming interface
• Such programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system.
• the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted
• circuitry may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality.
• ASIC Application Specific Integrated Circuit
• the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
• circuitry may include logic, at least partially operable in hardware.
• modules may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
• VLSI very-large-scale integration
• a module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
• Modules may also be implemented in software for execution by various types of processors.
• An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module may not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
• a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices.
• operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.
• the modules may be passive or active, including agents operable to perform desired functions.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Mobile Radio Communication Systems (AREA)

Priority Applications (2)

Applications Claiming Priority (1)

Publications (1)

Family

ID=55066812

Family Applications (1)

Country Status (2)

Cited By (1)

Citations (5)

• 2015
  • 2015-12-09 WO PCT/US2015/064820 patent/WO2017099766A1/en active Application Filing
• 2016
  • 2016-11-02 TW TW105135565A patent/TWI713339B/zh active

Patent Citations (5)

Non-Patent Citations (2)

Also Published As

Similar Documents

Legal Events