Patent Application
20170086132
Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, etc. These wireless networks may be multiple-access networks capable of supporting multiple users by sharing the available network resources. Examples of such multiple-access networks include Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, and Single-Carrier FDMA (SC-FDMA) networks.
A wireless communication network may include a number of eNodeBs that can support communication for a number of user equipments (UEs). A UE may communicate with an eNodeB via the downlink and uplink. The downlink (or forward link) refers to the communication link from the eNodeB to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the eNodeB.
In some instances, discovery of neighbors of neighbors cells may be a challenge due to absence of X2 connections between neighbors, for example, discovery of neighbors of neighbors in self organizing networks (SONs). The discovery of neighbors of neighbors may be useful in many scenarios, e.g., physical cell identity (PCI) selection, neighbor list additions, etc.
The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
The present disclosure presents an example method and apparatus for discovering a cell in a wireless network. For example, in an aspect, the present disclosure presents an example method that may include identifying at a third cell that a first cell is a neighbor of a second cell, wherein the third cell and the second cell are neighbors, and wherein the identifying is based at least on a user equipment (UE) history information information element (IE) of a UE and performing an action at the third cell based at least on information acquired from the identification.
Additionally, the present disclosure presents an example apparatus for discovering a cell in a wireless network that may include means for identifying at a third cell that a first cell is a neighbor of a second cell, wherein the third cell and the second cell are neighbors, and wherein the identifying is based at least on a user equipment (UE) history information information element (IE) of a UE and means for performing an action at the third cell based at least on information acquired from the identification.
In a further aspect, the present disclosure presents an example computer readable medium storing computer executable code for discovering a cell in a wireless network that may include code for identifying at a third cell that a first cell is a neighbor of a second cell, wherein the third cell and the second cell are neighbors, and wherein the identifying is based at least on a user equipment (UE) history information information element (IE) of a UE and code for performing an action at the third cell based at least on information acquired from the identification.
Furthermore, in an aspect, the present disclosure presents an example apparatus for discovering a cell in a wireless network that may include a processor and a memory, the processor and the memory configured to identify at a third cell that a first cell is a neighbor of a second cell, wherein the third cell and the second cell are neighbors, and wherein the identifying is based at least on a user equipment (UE) history information information element (IE) of a UE and perform an action at the third cell based at least on information acquired from the identification.
To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.
In order to facilitate a fuller understanding of the present disclosure, reference is now made to the accompanying drawings, in which like elements are referenced with like numerals. These drawings should not be construed as limiting the present disclosure, but are intended to be illustrative only.
Aspects of the present disclosure generally relate to self-configuration procedures in wireless communications, and more particularly, self-configuring a physical cell identity (PCI) at a cell upon detecting a PCI confusion at a neighbor cell. PCI confusion may occur when two or more neighbors (e.g., target cells) of a source cell have the same PCI and the source cell cannot identify which target cell to use for a UE handover resulting in handover delays and/or failures.
The detailed description set forth below, in connection with the appended drawings, is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.
A small cell or a small cell base station or access point may refer, but is not limited to, a femtocell, picocell, microcell, or any other cell or base station having a relatively small transmit power or relatively small coverage area as compared to a macro cell or macro base station.
The techniques described herein may be used for various wireless communication networks such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other networks. The terms “network” and “system” are often used interchangeably. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA network may implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS). 3GPP LTE and LTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP). UMB and cdma2000 are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2). The techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, certain aspects of the techniques are described below for LTE, and LTE terminology is used in much of the description below.
The base stations 105 may wirelessly communicate with the UEs 115 via one or more base station antennas. Each of the base stations 105 sites may provide communication coverage for a respective geographic coverage area 110. In some aspects, base stations 105 may be referred to as a base transceiver station, a radio base station, an access point, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a NodeB, eNodeB, Home NodeB, a Home eNodeB, or some other suitable terminology. The geographic coverage area 110 for a base station 105 may be divided into sectors making up only a portion of the coverage area (not shown). The wireless communications system 100 may include base stations 105 of different types (e.g., macro, micro, and/or pico base stations). There may be overlapping coverage areas for different technologies.
In an aspect, the wireless communications system 100 is an LTE/LTE-A network communication system. In LTE/LTE-A network communication systems, the terms evolved NodeB (eNodeB) may be generally used to describe the base stations 105. The wireless communications system 100 may be a Heterogeneous LTE/LTE-A network in which different types of eNodeBs provide coverage for various geographical regions. For example, each eNodeB 105 may provide communication coverage for a macro cell, a pico cell, a femtocell, and/or other types of cell. A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 115 with service subscriptions with the network provider. A pico cell would generally cover a relatively smaller geographic area (e.g., buildings) and may allow unrestricted access by UEs 115 with service subscriptions with the network provider. A femtocell would also generally cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs 115 having an association with the femtocell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 for users in the home, and the like). An eNodeB 105 for a macro cell may be referred to as a macro eNodeB. An eNodeB 105 for a pico cell may be referred to as a pico eNodeB. And, an eNodeB 105 for a femtocell may be referred to as a femto eNodeB or a home eNodeB. An eNodeB 105 may support one or multiple (e.g., two, three, four, and the like) cells. The wireless communications system 100 may support use of LTE and WLAN or Wi-Fi by one or more of the UEs 115. A small cell may refer to a micro cell, a pico cell, or a femtocell, for example.
The core network 130 may communicate with the eNodeBs 105 or other base stations 105 via first backhaul links 132 (e.g., S1 interface, etc.). The eNodeBs 105 may also communicate with one another, e.g., directly or indirectly via second backhaul links 134 (e.g., X2 interface, etc.) and/or via the first backhaul links 132 (e.g., through core network 130). The wireless communications system 100 may support synchronous or asynchronous operation. For synchronous operation, the eNodeBs 105 may have similar frame timing, and transmissions from different eNodeBs 105 may be approximately aligned in time. For asynchronous operation, the eNodeBs 105 may have different frame timing, and transmissions from different eNodeBs 105 may not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.
The UEs 115 may be dispersed throughout the wireless communications system 100, and each UE 115 may be stationary or mobile. A UE 115 may also be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. A UE 115 may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a wireless network appliance (e.g., devices for Internet of Things (IoT)), or the like. A UE 115 may be able to communicate with macro eNodeBs, pico eNodeBs, femto eNodeBs, relays, and the like.
The communication links 125 shown in the wireless communications system 100 may include uplink (UL) transmissions from a UE 115 to an eNodeB 105, and/or downlink (DL) transmissions, from an eNodeB 105 to a UE 115. The downlink transmissions may also be called forward link transmissions while the uplink transmissions may also be called reverse link transmissions.
For example, in an aspect, a cell (e.g., cell_3260 of
In an aspect, cell_3260 may include a cell discovery manager 270 for discovering a cell in a wireless network. The cell discovery manager 270 may include a cell identifying component 275 and an action performing component 280. In an additional or optional aspect, cell discovery manager 270 may optionally include a querying component 285 and/or a X2 interface component 290.
The cell identifying component 275 may include hardware, software, or a combination of hardware and software and may be configured or be operable to identify at a third cell that a first cell is a neighbor of a second cell, wherein the third cell and the second cell are neighbors, and wherein the identifying is based at least on a user equipment (UE) history information information element (IE) of a UE.
The action performing component 280 may include hardware, software, or a combination of hardware and software and may be configured or operable to perform an action at the third cell based at least on information acquired from the identification.
The querying component 285 may include hardware, software, or a combination of hardware and software and may be configured or operable to query a PCI, a frequency, a TX power, or any combination thereof, of the first cell, and/or query a PCI, a frequency, a transmitted (TX) power, or any combination thereof, of the first cell from the network entity.
The X2 interface component 290 may include hardware, software, or a combination of hardware and software and may be configured or operable to establish a X2 interface between the third cell and the first cell.
In an aspect, for instance, UE history information IE contains information about cells that a UE (e.g., UE 115) has been served by in active state prior to the target cell. The UE history information IE is passed from one cell (e.g., source cell) to another cell (e.g., target cell) during a handover and contains past cell identifies and the time the UE stayed on each cell. For example, in an aspect, UE 115 may be in active state and may be served by cell_1240, initially handed over to cell_2250, and later handed over to cell_3260. In such an instance, for example, UE history information IE of UE 115 may include information of cell_2250 and cell_1240 (in that order) and the respective times UE 115 stayed on cell_2250 and cell_1240 before being handed over to cell_3260. Moreover, the information of cell_2250 and cell_1240 is in an order with the most recent cell (e.g., cell_2250) at the top of the order.
In an additional or optional aspect, UE history information IE may be sent from one cell (e.g., cell_1240) to another cell (cell_225) over S1 interface. This allows the transfer of UE history information IE between cells even if X2 interface is not present between cells (e.g., X2 interfaces are not present between cell_2250 and cell_1240 and/or cell_2250 and cell_3260). The X2 interfaces may not be present due to various reasons. For example, cell_2250 may not support X2 interface, cell_2250 may belong to another vendor and inter-vendor X2 is not supported (or not working properly).
In an aspect, at block 320, methodology 300 may include performing an action at the third cell based at least on information acquired from the identification. For example, in an aspect cell_3260 and/or cell discovery manager 270 may include a specially programmed processor module, or a processor executing specially programmed code stored in a memory, to perform an action at the third cell (e.g., cell_3260) based at least on information acquired from the identification.
In an aspect, cell_3260 and/or cell discovery manager 270 may change (e.g., modify, update, etc.) PCI, frequency, or transmitted (TX) power of the cell (e.g., cell_3260) based at least on the information acquired (e.g., obtained, received, etc.) from the identification (e.g., the information acquired may include PCI, frequency, or TX power of cell_1240). For example, in an aspect, cell_3260 and/or cell discovery manager 270 may change PCI, frequency, or TX power of the cell (e.g., cell_3260) if cell_3260 determines there is PCI confusion (e.g., same PCI values for neighbors of neighbors) with cell_1240. For instance, if cell_3260 determines that PCI configured at cell_3260 is same as PCI of cell_1240, cell_3260 may perform an action (e.g., action to reconfigure, modify, update or revise) to change PCI of cell_3260. In an additional or optional aspect, cell_3260 and/or cell discovery manager 270 may change a combination (e.g., any combination) of PCI, frequency, or TX power of the cell_3260 based at least on the information acquired from the identification.
In an additional aspect, for example, cell_3260 and/or cell discovery manager 270 may perform an action that may include establishing (e.g., setting up, configuring, etc.) an X2 interface between the third cell (cell_3260) and the first cell (cell_1240). That is, an X2 connection is established with the discovered “neighbor or neighbor.” The establishment of the X2 connection between cell_3260 and cell_1240 allows cell_3260 to gather (e.g., retrieve, find out, etc.) more information (e.g., PCI, frequency, TX power) of cell_1240.
In a further additional aspect, for example, cell_3260 and/or cell discovery manager 270 may query a network entity (e.g., HeMS 230) for more information about discovered “neighbor of neighbor” (e.g., cell_1240). In such an aspect, cell_3260 and/or cell discovery manager 270 may query network entity (e.g., HeMS 230) using identity of cell_1240, e.g., cell identifier or eCGI.
Additionally, in an aspect, cell_3260 and/or cell discovery manager 270 may change PCI, frequency, or TX power of the cell (e.g., cell_3260) based at least on the information received in the UE history information IE. For example, if UE history information IE includes information such as PCI, frequency, TX power, etc., cell_3260 and/or cell discovery manager 270 may change PCI, frequency, TX power of cell_3260 based on the information received in the UE history information IE without the need for retrieving such information from cell_1240 and/or network entity as described above.
Referring to
For example, system 400 can reside at least partially within a cell, for example, cells 260 (
Additionally, logical grouping 402 may include an electrical component 406 to performing an action at the third cell based at least on information acquired from the identification. For example, in an aspect, electrical component 406 may comprise cell discovery manager 270 (
Additionally, system 400 can include a memory 408 that retains instructions for executing functions associated with the electrical components 404 and 406, stores data used or obtained by the electrical components 404 and 406, etc. While shown as being external to memory 408, it is to be understood that one or more of the electrical components 404 and 406 can exist within memory 408. In one example, electrical components 404 and 406 can comprise at least one processor, or each electrical component 404 and 406 can be a corresponding module of at least one processor. Moreover, in an additional or alternative example, electrical components 404 and 406 can be a computer program product including a computer readable medium, where each electrical component 404 and 406 can be corresponding code.
Referring to
Computer device 500 further includes a memory 504, such as for storing data used herein and/or local versions of applications being executed by processor 502. Memory 504 can include any type of memory usable by a computer, such as random access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof.
Further, 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. For example, 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. In an additional aspect, 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.
Additionally, computer device 500 may further include a data store 508, which can be any suitable combination of hardware and/or software, that provides for mass storage of information, databases, and programs employed in connection with aspects described herein. For example, data store 508 may be a data repository for applications not currently being executed by processor 502 and/or any threshold values or finger position values.
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. Further, 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.
The processor 604 is responsible for managing the bus 602 and general processing, including the execution of software stored on the computer-readable medium 606. 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 606 may also be used for storing data that is manipulated by the processor 604 when executing software.
The E-UTRAN includes the evolved NodeB (eNB) 706 and other eNBs 708. The eNB 706 provides user and control plane protocol terminations toward the UE 702. The eNB 706 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), an extended service set (ESS), or some other suitable terminology. The eNB 706 provides an access point to the EPC 760 for a UE 702. Examples of UEs 702 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, or any other similar functioning device. The UE 702 may also be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
The eNB 706 is connected by an S1 interface to the EPC 760. The EPC 760 includes a Mobility Management Entity (MME) 762, other MMEs 764, a Serving Gateway 766, and a Packet Data Network (PDN) Gateway 768. The MME 762 is the control node that processes the signaling between the UE 702 and the EPC 760. Generally, 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).
Referring to
As the UE 834 moves from the illustrated location in cell 804 into cell 806, 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 NodeBs corresponding to the respective cells, at a Mobility Management Entity (MME) 762 (
Further, the modulation and multiple access scheme employed by the access network 800 may vary depending on the particular telecommunications standard being deployed. By way of example, the standard may include Evolution-Data Optimized (EV-DO) or Ultra Mobile Broadband (UMB). EV-DO and UMB are air interface standards promulgated by the 3rd Generation Partnership Project 2 (3GPP2) as part of the CDMA2000 family of standards and employs CDMA to provide broadband Internet access to mobile stations. 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 902.11 (Wi-Fi), IEEE 902.16 (WiMAX), IEEE 902.20, and Flash-OFDM employing OFDMA. UTRA, E-UTRA, UMTS, LTE, LTE Advanced, and GSM are described in documents from the 3GPP organization. CDMA2000 and UMB are described in documents from the 3GPP2 organization. The actual wireless communication standard and the multiple access technology employed will depend on the specific application and the overall design constraints imposed on the system.
In the downlink communication, a transmit processor 920 may receive data from a data source 912 and control signals from a controller/processor 940. The transmit processor 920 provides various signal processing functions for the data and control signals, as well as reference signals (e.g., pilot signals). For example, the transmit processor 920 may provide cyclic redundancy check (CRC) codes for error detection, coding and interleaving to facilitate forward error correction (FEC), mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM), and the like), spreading with orthogonal variable spreading factors (OVSF), and multiplying with scrambling codes to produce a series of symbols. Channel estimates from a channel processor 944 may be used by a controller/processor 940 to determine the coding, modulation, spreading, and/or scrambling schemes for the transmit processor 920. These channel estimates may be derived from a reference signal transmitted by the UE 950 or from feedback from the UE 950. The symbols generated by the transmit processor 920 are provided to a transmit frame processor 930 to create a frame structure. The transmit frame processor 930 creates this frame structure by multiplexing the symbols with information from the controller/processor 940, resulting in a series of frames. The frames are then provided to a transmitter 932, which provides various signal conditioning functions including amplifying, filtering, and modulating the frames onto a carrier for downlink transmission over the wireless medium through antenna 934. The antenna 934 may include one or more antennas, for example, including beam steering bidirectional adaptive antenna arrays or other similar beam technologies.
At the UE 950, a receiver 954 receives the downlink transmission through an antenna 952 and processes the transmission to recover the information modulated onto the carrier. The information recovered by the receiver 954 is provided to a receive frame processor 960, which parses each frame, and provides information from the frames to a channel processor 984 and the data, control, and reference signals to a receive processor 970. The receive processor 970 then performs the inverse of the processing performed by the transmit processor 920 in the NodeB 910. More specifically, the receive processor 970 descrambles and despreads the symbols, and then determines the most likely signal constellation points transmitted by the NodeB 910 based on the modulation scheme. These soft decisions may be based on channel estimates computed by the channel processor 984. The soft decisions are then decoded and deinterleaved to recover the data, control, and reference signals. The CRC codes are then checked to determine whether the frames were successfully decoded. The data carried by the successfully decoded frames will then be provided to a data sink 972, which represents applications running in the UE 950 and/or various user interfaces (e.g., display). Control signals carried by successfully decoded frames will be provided to a controller/processor 990. When frames are unsuccessfully decoded by the receive processor 970, the controller/processor 990 may also use an acknowledgement (ACK) and/or negative acknowledgement (NACK) protocol to support retransmission requests for those frames.
In the uplink, data from a data source 978 and control signals from the controller/processor 990 are provided to a transmit processor 980. The data source 978 may represent applications running in the UE 950 and various user interfaces (e.g., keyboard). Similar to the functionality described in connection with the downlink transmission by the NodeB 910, the transmit processor 980 provides various signal processing functions including CRC codes, coding and interleaving to facilitate FEC, mapping to signal constellations, spreading with OVSFs, and scrambling to produce a series of symbols. Channel estimates, derived by the channel processor 984 from a reference signal transmitted by the NodeB 910 or from feedback contained in the midamble transmitted by the NodeB 910, may be used to select the appropriate coding, modulation, spreading, and/or scrambling schemes. The symbols produced by the transmit processor 980 will be provided to a transmit frame processor 982 to create a frame structure. The transmit frame processor 982 creates this frame structure by multiplexing the symbols with information from the controller/processor 990, resulting in a series of frames. The frames are then provided to a transmitter 956, which provides various signal conditioning functions including amplification, filtering, and modulating the frames onto a carrier for uplink transmission over the wireless medium through the antenna 952.
The uplink transmission is processed at the NodeB 910 in a manner similar to that described in connection with the receiver function at the UE 950. A receiver 935 receives the uplink transmission through the antenna 934 and processes the transmission to recover the information modulated onto the carrier. The information recovered by the receiver 935 is provided to a receive frame processor 936, which parses each frame, and provides information from the frames to the channel processor 944 and the data, control, and reference signals to a receive processor 939. The receive processor 939 performs the inverse of the processing performed by the transmit processor 980 in the UE 950. The data and control signals carried by the successfully decoded frames may then be provided to a data sink 938 and the controller/processor, respectively. If some of the frames were unsuccessfully decoded by the receive processor, the controller/processor 940 may also use an acknowledgement (ACK) and/or negative acknowledgement (NACK) protocol to support retransmission requests for those frames.
The controller/processors 940 and 990 may be used to direct the operation at the NodeB 910 and the UE 950, respectively. For example, the controller/processors 940 and 990 may provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. The computer readable media of memories 942 and 992 may store data and software for the NodeB 910 and the UE 950, respectively. A scheduler/processor 946 at the NodeB 910 may be used to allocate resources to the UEs and schedule downlink and/or uplink transmissions for the UEs.
Several aspects of a telecommunications system have been presented with reference to a W-CDMA system. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures and communication standards.
By way of example, various aspects may be extended to other UMTS systems such as TD-SCDMA, High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), High Speed Packet Access Plus (HSPA+) and TD-CDMA. Various aspects may also be extended to systems employing Long Term Evolution (LTE) (in FDD, TDD, or both modes), LTE-Advanced (LTE-A) (in FDD, TDD, or both modes), CDMA2000, Evolution-Data Optimized (EV-DO), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth, and/or other suitable systems. 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.
In accordance with various aspects of the disclosure, an element, or any portion of an element, or any combination of elements may be implemented with a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. 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. A non-transitory computer-readable medium includes, by way of example, a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip), an optical disk (e.g., compact disk (CD), digital versatile disk (DVD)), a smart card, a flash memory device (e.g., card, stick, key drive), random access memory (RAM), read only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), a register, a removable disk, and any other suitable medium for storing software and/or instructions that may be accessed and read by a computer.
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. By way of example, a computer-program product may include a computer-readable medium in packaging materials. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.
It is to be understood that the specific order or hierarchy of steps in the methods disclosed is an illustration of exemplary processes. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the methods may be rearranged. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented unless specifically recited therein.
The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language of the claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. A phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover: a; b; c; a and b; a and c; b and c; and a, b and c. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed under the provisions of 35 U.S.C. §112, sixth paragraph, unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the element is recited using the phrase “step for.”
