Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
  • H04W52/04—Transmission power control [TPC]
  • H04W52/38—TPC being performed in particular situations
  • H04W52/48—TPC being performed in particular situations during retransmission after error or non-acknowledgment
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
  • H04W52/04—Transmission power control [TPC]
  • H04W52/38—TPC being performed in particular situations
  • H04W52/44—TPC being performed in particular situations in connection with interruption of transmission
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W24/00—Supervisory, monitoring or testing arrangements
  • H04W24/02—Arrangements for optimising operational condition
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W24/00—Supervisory, monitoring or testing arrangements
  • H04W24/08—Testing, supervising or monitoring using real traffic
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/0005—Control or signalling for completing the hand-off
  • H04W36/0055—Transmission or use of information for re-establishing the radio link
  • H04W36/0058—Transmission of hand-off measurement information, e.g. measurement reports
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/0005—Control or signalling for completing the hand-off
  • H04W36/0055—Transmission or use of information for re-establishing the radio link
  • H04W36/0064—Transmission or use of information for re-establishing the radio link of control information between different access points
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/0005—Control or signalling for completing the hand-off
  • H04W36/0055—Transmission or use of information for re-establishing the radio link
  • H04W36/0079—Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W36/00—Hand-off or reselection arrangements
  • H04W36/0005—Control or signalling for completing the hand-off
  • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
  • H04W36/0085—Hand-off measurements
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
  • H04W52/02—Power saving arrangements
  • H04W52/0203—Power saving arrangements in the radio access network or backbone network of wireless communication networks
  • H04W52/0206—Power saving arrangements in the radio access network or backbone network of wireless communication networks in access points, e.g. base stations
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W92/00—Interfaces specially adapted for wireless communication networks
  • H04W92/16—Interfaces between hierarchically similar devices
  • H04W92/20—Interfaces between hierarchically similar devices between access points
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
  • H04W52/04—Transmission power control [TPC]
• • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
  • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
  • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
  • Y02D30/00—Reducing energy consumption in communication networks
  • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

• FIGS. 4A-4D illustrate messages in various scenarios for handover failure events.
• an eNodeB may track performance measurements of handovers when the eNodeB is providing the target cell of a handover. Based on the performance measurements, the eNodeB may determine whether the configuration of the cell is a cause of handover failures from one or more other cells. The eNodeB may adjust transmission properties in order to improve handover reliability. The adjustments by a target eNodeB may be supplemental to optimization by a source cell or source eNodeBs. The eNodeB may provide an opportunity for source cells or eNodeBs to adjust parameters before adjusting transmission properties.
• multiple UEs such as UE 12 may be in communication coverage with one or more eNodeBs, including eNodeB 14, eNodeB 20, or eNodeB 28.
• the eNodeB 14 (or a cell supported or provided by eNodeB 14) may handover the UE 12 to the eNodeB 20 (or to a cell supported or provided by the eNodeB 20).
• the eNodeB 14 may be referred to as a source eNodeB, while the eNodeB 20 may be referred to as a target eNodeB for such a handover.
• the X2 interface component 32 may also send or receive a HANDOVER
• the HANDOVER REPORT message may include a type of detected handover problem or condition, ECGI of the source and target cells in the handover, an ECGI of the re-establishment cell, and a handover cause that was signaled by the source during handover preparation.
• the detected handover problem or condition may include one of: a too-late handover, a too-early handover, and a handover to wrong cell.
• the type of handover problem may be determined, for example, as described in 3 GPP TS 36.300 v.9.7.0 ⁇ 22.4.2.
• the handover event detecting component 33 may be configured to detect handover events where the eNodeB 20 is a target eNodeB or a wrong eNodeB/cell.
• the handover event detecting component 33 may include hardware, firmware, and/or a processor executing software configured to detect handover events.
• the handover event detecting component 33 may include a processor configured to analyze messages received from the UE 12 and from other eNodeBs over the X2 interface component 32.
• the handover event detecting component 33 may detect incoming too-late handovers, incoming too-early handovers, incoming wrong-cell handovers, and incomplete handovers in addition to outgoing handover events.
• the handover event detecting component 33 may detect when the target eNodeB
• the eNodeB 20 may determine that eNodeB 20 is a target of an incoming too-early handover when X2 interface component 32 sends a HANDOVER REPORT message to eNodeB 14, on receiving an RLF INDICATION message, to indicate that a too-early handover occurred.
• the handover event detecting component 33 may record an incoming too-early handover event for the target eNodeB 20.
• the eNodeB 14 may receive the HANDOVER REPORT message and determine that an outgoing too-early handover occurred.
• the performance measurement component 34 may be configured to determine a performance measurement for at least one handover failure event at a target eNodeB 20.
• the performance measurement component 34 may be implemented by hardware, firmware, and/or a processor executing software configured to determine performance measurements for at least one handover failure event.
• the performance measurement component 34 may be configured to measure failure events detected by the X2 interface component 32.
• the performance measurement component 34 may be configured to measure a number and timing of: too-early handover messages sent, wrong cell handover messages sent, too-late handovers detected, and incomplete handover events.
• the performance measurements may be tracked for each related cell separately.
• the performance measurement component 34 may also be configured to measure a number and timing of: successful incoming handover events and total incoming handover failure events.
• the performance analyzer 36 may be configured to determine whether the target eNodeB 20 is providing an undesired coverage area based on the performance measurement.
• the performance analyzer 36 may be implemented by hardware, firmware, and/or a processor executing software configured to analyze one or more performance measurements.
• An undesired coverage area may be a coverage area of the target eNodeB 20 within a cell of another eNodeB.
• an undesired coverage area may refer to a cell's coverage area that may be leaking, extending, or otherwise extending into an area or region covered by another cell or cells.
• the performance analyzer 36 may determine that the target eNodeB 20 is providing an undesired coverage area when a performance measurement for incoming failed handovers exceeds a threshold value.
• the threshold value may be configured as a number of handover failures or a percentage of a handovers resulting in failures.
• the performance analyzer 36 may be configured to use a combination of both incoming handover performance measurements and outgoing handover performance measurements. For example, the performance analyzer 36 may compare a number of incoming too-late handovers to a number of outgoing too-late handovers. In another example, the performance analyzer 36 may use a metric based on the summation of number of incoming too-late handovers and number of outgoing too- late handovers.
• the performance analyzer 36 may be further configured to provide an opportunity for another eNodeB to change configuration before adjusting the transmit power of the target eNodeB 20.
• a source eNodeB 14 may resolve the problem through configuration changes by performing one or more of the following: 1) adapting the transmit power of the source eNodeB; 2) adapting resource block allocation including those to users experiencing high path loss to the cells provided by the eNodeB; 3) adapting resource block allocation including those to users experiencing high interference from cells provided by other eNodeBs; and/or 4) using MRO to adjust handover parameters such as time-to-trigger, hysteresis, offsets, filtering coefficients.
• the transmit controller 38 may be configured to adjust the transmit power of all cells provided by the eNodeB 20 in response to determining that any of the cells is providing an undesired coverage area.
• the transmit controller 38 may either increase or decrease the transmit power (e.g., the power applied for transmitting signals over a wireless medium) based on the performance measurements. For example, the transmit controller 38 may increase the transmit power of a cell when a high rate of incoming too-late handovers is detected in order to provide a larger overlapping coverage area. As another example, the transmit controller 38 may decrease the transmit power of a cell when a high rate of incoming too-early handovers is detected in order to allow handovers to other possible cells.
• the method 60 may include detecting a handover failure event for an incoming handover.
• the handover event detecting component 33 (FIG. 1) may detect a handover failure event for an incoming handover.
• the detection by the handover event detecting component 33 may further involve sending an indication that a handover occurred too-early using the X2 interface component 32.
• the detection by the handover event detecting component 33 may further involve sending an indication that a handover to the eNodeB was a handover to a wrong cell using the X2 interface component 32.
• the detection by the handover event detecting component 33 may further involve detecting the at least one handover failure event by determining that the target eNodeB (e.g. the eNodeB 20 in FIG. 1) was prepared for a handover and the handover was not completed. In yet another aspect, the detection by handover event detecting component 33 may further involve sending a radio link failure indication to a source eNodeB (e.g. the eNodeB 14 in FIG. 1) using the X2 interface component 32 when the radio link failure indication is due to a too-late handover to the cell.
• a source eNodeB e.g. the eNodeB 14 in FIG.
• the method 60 may optionally include determining, at a target eNodeB, a performance measurement of the at least one handover failure event.
• the performance measurement component 34 (FIG. 1) may determine the performance measurement of the at least one handover failure event.
• the performance measurement may include a statistic or statistical information based on one or more detected handover failure events.
• the performance measurement may be a number, a rate, or a percentage associated with a particular type of handover failure event.
• Performance measurements may be determined separately for each related eNodeB.
• the target eNodeB may determine a rate of incoming too-late handovers from each eNodeB (e.g. eNodeB 14 and eNodeB 28) that has handed a UE over to the target eNodeB 20.
• the method 60 may include determining that the cell provides an undesired coverage area based on the at least one handover failure event.
• the performance analyzer 36 (FIG. 1) may determine that the cell provides the undesired coverage area based on the handover failure event performance measurement.
• the performance analyzer 36 may also determine that the cell provides an undesired coverage area based on whether the performance measurement exceeds a threshold for the performance measurement.
• the method 60 may include adjusting the transmit power of the cell such that the undesired coverage area is altered.
• the transmit controller 38 (FIG. 1) may adjust the transmit power of the cell such that the undesired coverage area is altered.
• the transmit controller 38 may increase or decrease the transmit power of the cell to alter the coverage area.
• FIG. 3A illustrates an example of a scenario of a handover being too-late.
• the eNB_A e.g. eNodeB 14 (FIG. 1)
• a cell associated with the eNB_A, having a coverage area 70 may handover the UE 12 to eNB B (e.g. eNodeB 20), or a cell associated with eNB_B having a coverage area 72.
• the eNB_B may be the target eNodeB.
• the UE 12 may not receive a handover command before it leaves the coverage area 70 of eNB_A.
• the eNB B may receive the RLF INDICATION message from eNB A and determine that the handover was too-early because the UE 12 came recently from eNB A and performed re-establishment at eNB A.
• the eNB B may send a HANDOVER REPORT message to eNB A indicating a too-early handover.
• the eNB B may detect a too-early handover failure event where the eNB B was the target of the too-early handover.
• the too-early handover may be due, in part, to the eNB B providing an undesired coverage area.
• the coverage area 82 of eNB B may leak into the coverage area 80 of eNB A.
• the radio link between the UE 12 and the source eNodeB 14 may deteriorate such that the handover command is not sent by the source eNodeB 14 due to delay in determining the need for a handover.
• the target eNodeB 20 may not receive the handover command.
• the synchronization/RACH procedure 106 may fails or too many packets may be lost before a connection with the target eNodeB 20 is established.
• the UE 12, upon detecting a radio link failure may reestablish a connection with the eNodeB 20 and indicate an RLF in the connection reestablishment message 108.
• the eNodeB 20 may determine that an incoming too late handover occurred by analyzing the reestablishment message. Accordingly, the eNodeB 20 may detect an incoming too-late handover failure event 110. The eNodeB 20 may then send an RLF indication 112 to the eNodeB 14 indicating the incoming too-late handover failure event 110. The eNodeB 14 may detect an outgoing too-late handover failure event 114.
• FIG. 4B illustrates a message diagram for a too-early handover scenario.
• some messages such as acknowledgement messages may be omitted.
• the HO preparation message 102, HO command message 104, and synchronization/RACH procedure 106 may be similar to FIG. 4A.
• the handover may fail before the UE 12 completes the handover to the eNodeB 20.
• the UE 12 may be unable to synchronize or complete the synchronization/RACH procedure 106 with the eNodeB 20.
• the UE 12 may successfully handover to the eNodeB 20.
• the synchronization/RACH procedure 106 may be completed and the target eNodeB 20 may send a context release message 130 to the source eNodeB 14. However, the radio link between the UE 12 and the eNodeB 20 may fail shortly after the successful handover.
• the UE 12 upon detecting a radio link failure, may reestablish a connection with the eNodeB 14 and indicate an RLF in the connection reestablishment message 120.
• the eNodeB 14 may send an RLF indication to the eNodeB 20.
• the eNodeB 20 may determine that a too-early handover occurred and detect an incoming too-early handover event 124 because the RLF indication is received from the source eNodeB 14.
• the eNodeB 20 may send a HANDOVER REPORT message 126 indicating a too-early handover.
• the eNodeB 14 may detect an outgoing too-early handover event 128 based on the HANDOVER REPORT
• FIG. 4C illustrates a message diagram for a wrong-cell handover scenario.
• some messages such as acknowledgement messages may be omitted.
• the HO preparation message 102, HO command message 104, and synchronization/RACH procedure 106 may be similar to FIG. 4A.
• the handover may fail before the UE 12 completes the handover to the eNodeB 20.
• the UE 12 may be unable to synchronize or complete the synchronization/RACH procedure 106 with the eNodeB 20.
• the UE 12 may successfully handover to the eNodeB 20.
• FIG. 4D illustrates a message diagram for an incomplete handover scenario.
• logical grouping 402 can include an electrical component 408 for determining that the target eNodeB is providing an undesired coverage area.
• the electrical component 408 may comprise performance analyzer 36 (FIG. 1).
• logical grouping 402 can include an electrical component 410 for adjusting the transmit power of the eNodeB.
• the electrical component 410 may comprise transmit controller 38 (FIG. 1).
• one or more of eNodeBs 14, 20 (FIG. 1) including mobility optimization component 30 (FIG. 1) may be represented by a specially programmed or configured computer device 500.
• computer device 500 may include mobility optimization component 30 (FIG. 1), such as in specially programmed computer readable instructions or code, firmware, hardware, or some combination thereof.
• Computer device 500 includes a processor 502 for carrying out processing functions associated with one or more of components and functions described herein.
• Processor 502 can include a single or multiple set of processors or multi-core processors.
• processor 502 can be implemented as an integrated processing system and/or a distributed processing system.
• computer device 500 includes a communications component 506 that provides for establishing and maintaining communications with one or more parties utilizing hardware, software, and services as described herein.
• Communications component 506 may carry communications between components on computer device 500, as well as between computer device 500 and external devices, such as devices located across a communications network and/or devices serially or locally connected to computer device 500.
• communications component 506 may include one or more buses, and may further include transmit chain components and receive chain components associated with a transmitter and receiver, respectively, or a transceiver, operable for interfacing with external devices.
• communications component 506 may be configured to receive one or more pages from one or more subscriber networks. In a further aspect, such a page may correspond to the second subscription and may be received via the first technology type communication services.
• Computer device 500 may additionally include a user interface component 510 operable to receive inputs from a user of computer device 500 and further operable to generate outputs for presentation to the user.
• User interface component 510 may include one or more input devices, including but not limited to a keyboard, a number pad, a mouse, a touch-sensitive display, a navigation key, a function key, a microphone, a voice recognition component, any other mechanism capable of receiving an input from a user, or any combination thereof.
• user interface component 510 may include one or more output devices, including but not limited to a display, a speaker, a haptic feedback mechanism, a printer, any other mechanism capable of presenting an output to a user, or any combination thereof.
• FIG. 7 is a block diagram illustrating an example of a hardware implementation for an apparatus 600, for example, including mobility optimization component 30 of FIG. 1 and employing a processing system 614 for carrying out aspects of the present disclosure, such as method for optimizing coverage area of an eNodeB based on failure events for handover to the eNodeB.
• the processing system 614 may be implemented with bus architecture, represented generally by a bus 602.
• the bus 602 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 614 and the overall design constraints.
• the bus 602 links together various circuits including one or more processors, represented generally by the processor 604, computer-readable media, represented generally by the computer-readable medium 606, and one or more components described herein, such as, but not limited to, mobility optimization component 30 (FIG. 1).
• the bus 602 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.
• a bus interface 608 provides an interface between the bus 602 and a transceiver 610.
• the transceiver 610 provides a means for communicating with various other apparatus over a transmission medium.
• a user interface 612 e.g., keypad, display, speaker, microphone, joystick
• the processor 604 is responsible for managing the bus 602 and general processing, including the execution of software stored on the computer-readable medium 607.
• the software when executed by the processor 604, causes the processing system 614 to perform the various functions described infra for any particular apparatus.
• the computer-readable medium 607 may also be used for storing data that is manipulated by the processor 604 when executing software, mobility optimization component 30 as described above may be implemented in whole or in part by processor 604, or by computer-readable medium 606, or by any combination of processor 604 and computer-readable medium 606.
• the LTE network architecture 700 may be referred to as an Evolved Packet System (EPS) 700.
• EPS 700 may include one or more user equipment (UE) 702, an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 704, an Evolved Packet Core (EPC) 780, a Home Subscriber Server (HSS) 720, and an Operator's IP Services 722.
• UE user equipment
• E-UTRAN Evolved UMTS Terrestrial Radio Access Network
• EPC Evolved Packet Core
• HSS Home Subscriber Server
• Operator's IP Services 722 The EPS can interconnect with other access networks, but for simplicity those entities/interfaces are not shown.
• the EPS provides packet-switched services, however, as those skilled in the art will readily appreciate, the various concepts presented throughout this disclosure may be extended to networks providing circuit- switched services.
• the eNB 706 and 708 may each be an example of an eNodeB 20 (FIG. 1) including a mobility optimization component 30 for enabling concurrent transmission and radar detection using self-interference cancellation.
• the eNB 706 provides user and control plane protocol terminations toward the UE 702.
• the eNB 708 may be connected to the other eNBs 708 via an X2 interface (i.e., backhaul).
• the eNB 706 may also be referred to by those skilled in the art as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), a small cell, an extended service set (ESS), or some other suitable terminology.
• BSS basic service set
• ESS extended service set
• the eNB 706 is connected by an SI interface to the EPC 780.
• the EPC 780 includes a Mobility Management Entity (MME) 762, other MMEs 764, a Serving Gateway 766, and a Packet Data Network (PDN) Gateway 768.
• MME 762 is the control node that processes the signaling between the UE 702 and the EPC 780.
• the MME 762 provides bearer and connection management. All user IP packets are transferred through the Serving Gateway 766, which itself is connected to the PDN Gateway 768.
• the PDN Gateway 768 provides UE IP address allocation as well as other functions.
• the PDN Gateway 768 is connected to the Operator's IP Services 722.
• the Operator's IP Services 722 includes the Internet, the Intranet, an IP Multimedia Subsystem (IMS), and a PS Streaming Service (PSS).
• IMS IP Multimedia Subsystem
• PSS PS Streaming Service
• an access network 800 in a E-UTRAN architecture may include one or more base stations or eNodeBs 14, 20, 28 (FIG. 1) having the mobility optimization component 30.
• the multiple access wireless communication system includes multiple cellular regions (cells), including cells 802, 804, and 806, each of which may include one or more sectors and which may be provided by, for example, an eNodeB 14, 20, 28 of FIG. 1.
• the multiple sectors can be formed by groups of antennas with each antenna responsible for communication with UEs in a portion of the cell. For example, in cell 802, antenna groups 812, 814, and 816 may each correspond to a different sector. In cell 804, antenna groups 819, 820, and 822 each correspond to a different sector.
• UEs 830 and 832 may be in communication with eNodeB 842
• UEs 834 and 836 may be in communication with eNodeB 844
• UEs 839 and 840 can be in communication with eNodeB 846.
• each eNodeB 842, 844, 846 is configured to provide an access point for all the UEs 830, 832, 834, 836, 838, 840 in the respective cells 802, 804, and 806.
• each eNodeB 842, 844, 846 and UEs 830, 832, 834, 836, 838, 840 may be UE 12 of FIG. 1 and may perform the methods outlined herein.
• a serving cell change (SCC) or handover may occur in which communication with the UE 834 transitions from the cell 804, which may be referred to as the source cell, to cell 806, which may be referred to as the target cell.
• Management of the handover procedure may take place at the UE 834, at the Node Bs corresponding to the respective cells, at EPC 780 (FIG. 7), or at another suitable node in the wireless network.
• the UE 834 may monitor various parameters of the source cell 804 as well as various parameters of neighboring cells such as cells 806 and 802.
• the standard may alternately be Universal Terrestrial Radio Access (UTRA) employing Wideband-CDMA (W-CDMA) and other variants of CDMA, such as TD-SCDMA; Global System for Mobile Communications (GSM) employing TDMA; and Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM employing OFDMA.
• UTRA, E-UTRA, UMTS, LTE, LTE Advanced, and GSM are described in documents from the 3 GPP organization.
• CDMA2000 and UMB are described in documents from the 3GPP2 organization.
• FIG. 10 is a block diagram conceptually illustrating an exemplary eNodeB 910 and an exemplary UE 950 configured in accordance with an aspect of the present disclosure.
• the base station/eNodeB 910 and the UE 950 may be the eNodeB 20 having mobility optimization component 30 and the UE 12 in FIG. 1, respectively.
• the base station 910 may be equipped with antennas 934a-t
• the UE 950 may be equipped with antennas 952a-r, wherein t and r are integers greater than or equal to one.
• a base station transmit processor 920 may receive data from a base station data source 912 and control information from a base station controller/processor 940.
• the control information may be carried on the PBCH, PCFICH, PHICH, PDCCH, etc.
• the data may be carried on the PDSCH, etc.
• the base station transmit processor 920 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively.
• the base station transmit processor 920 may also generate reference symbols, e.g., for the PSS, SSS, and cell-specific reference signal (RS).
• RS cell-specific reference signal
• the mobility optimization component 30 may control a transmit power for the transmitted reference symbols including the cell-specific RS, which may be monitored for handover measurements.
• a base station transmit (TX) multiple-input multiple-output (MIMO) processor 930 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the base station modulators/demodulators (MODs/DEMODs) 932a-t. Each base station modulator/demodulator 1432 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream.
• TX transmit
• MIMO multiple-input multiple-output
• Each base station modulator/demodulator 1432 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream.
• a UE reception processor 958 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 950 to a UE data sink 960, and provide decoded control information to a UE controller/processor 980.
• a UE transmit processor 964 may receive and process data (e.g., for the PUSCH) from a UE data source 962 and control information (e.g., for the PUCCH) from the UE controller/processor 980.
• the UE transmit processor 964 may also generate reference symbols for a reference signal.
• the symbols from the UE transmit processor 964 may be precoded by a UE TX MIMO processor 966 if applicable, further processed by the UE modulator/demodulators 954a-r (e.g., for SC-FDM, etc.), and transmitted to the base station 910.
• the base station controller/processor 940 and the UE controller/processor 980 may direct the operation at the base station 910 and the UE 950, respectively.
• the base station controller/processor 940 and/or other processors and modules at the base station 910 may perform or direct, e.g., the execution of various processes for the techniques described herein.
• the UE controller/processor 980 and/or other processors and modules at the UE 950 may also perform or direct, e.g., the execution of the functional blocks illustrated in FIG. 2 and/or other processes for the techniques described herein.
• the base station memory 942 and the UE memory 982 may store data and program codes for the base station 910 and the UE 950, respectively.
• a scheduler 944 may schedule UEs 950 for data transmission on the downlink and/or uplink.
• the mobility optimization component 30 may include or be implemented by the modulators/demodulators 932, receive processor 938, controller/processor 940, memory 942, transmit processor 920, and/or modulators/demodulators 932.
• LTE-A LTE-Advanced
• EV- DO Evolution-Data Optimized
• UMB Ultra Mobile Broadband
• Wi-Fi Wi-Fi
• WiMAX WiMAX
• IEEE 802.20 Ultra-Wideband
• Bluetooth Bluetooth
• the actual telecommunication standard, network architecture, and/or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.
• Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
• the software may reside on a computer-readable medium.
• the computer-readable medium may be a non-transitory computer-readable medium.
• the computer-readable medium may also include, by way of example, a carrier wave, a transmission line, and any other suitable medium for transmitting software and/or instructions that may be accessed and read by a computer.
• the computer- readable medium may be resident in the processing system, external to the processing system, or distributed across multiple entities including the processing system.
• the computer-readable medium may be embodied in a computer-program product.
• a computer-program product may include a computer-readable medium in packaging materials.
• DSP digital signal processor
• ASIC application specific integrated circuit
• FPGA field programmable gate array
• 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.
• a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
• An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium.
• the storage medium may be integral to the processor.
• the processor and the storage medium may reside in an ASIC.
• the ASIC may reside in a user terminal.
• the processor and the storage medium may reside as discrete components in a user terminal.
• 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 means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium.
• Disk and disc 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 reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer- readable media.

Landscapes

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

Priority Applications (4)

Applications Claiming Priority (4)

Publications (1)

Family

ID=52998282

Family Applications (1)

Country Status (6)

Cited By (1)

Families Citing this family (12)

Citations (5)

Family Cites Families (14)

• 2014
  • 2014-12-31 US US14/587,855 patent/US9906993B2/en active Active
• 2015
  • 2015-04-15 WO PCT/US2015/026001 patent/WO2015175140A1/en not_active Ceased
  • 2015-04-15 EP EP15718125.6A patent/EP3143799A1/en not_active Withdrawn
  • 2015-04-15 JP JP2016567038A patent/JP2017519415A/ja active Pending
  • 2015-04-15 KR KR1020167034973A patent/KR20170008792A/ko not_active Withdrawn
  • 2015-04-15 CN CN201580025148.3A patent/CN106465205A/zh active Pending

Patent Citations (5)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events