WO2015116393A1 - Apparatus, method, and system of inter-node communication - Google Patents

Apparatus, method, and system of inter-node communication Download PDF

Info

Publication number
WO2015116393A1
WO2015116393A1 PCT/US2015/011516 US2015011516W WO2015116393A1 WO 2015116393 A1 WO2015116393 A1 WO 2015116393A1 US 2015011516 W US2015011516 W US 2015011516W WO 2015116393 A1 WO2015116393 A1 WO 2015116393A1
Authority
WO
WIPO (PCT)
Prior art keywords
rntp
setting
rwtp
enb
node
Prior art date
Application number
PCT/US2015/011516
Other languages
English (en)
French (fr)
Inventor
Alexei Davydov
Alexander Maltsev
Gregory Morozov
Alexander Sirotkin
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Priority to EP15743522.3A priority Critical patent/EP3100584A4/en
Priority to CN201580003286.1A priority patent/CN105850225B/zh
Publication of WO2015116393A1 publication Critical patent/WO2015116393A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/27—Control channels or signalling for resource management between access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/022—Site diversity; Macro-diversity
    • H04B7/024—Co-operative use of antennas of several sites, e.g. in co-ordinated multipoint or co-operative multiple-input multiple-output [MIMO] systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/0413—MIMO systems
    • H04B7/0456—Selection of precoding matrices or codebooks, e.g. using matrices antenna weighting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/0413—MIMO systems
    • H04B7/0456—Selection of precoding matrices or codebooks, e.g. using matrices antenna weighting
    • H04B7/0478—Special codebook structures directed to feedback optimisation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0613—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission
    • H04B7/0615—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal
    • H04B7/0617—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station using simultaneous transmission of weighted versions of same signal for beam forming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/06—TPC algorithms
    • H04W52/14—Separate analysis of uplink or downlink
    • H04W52/143—Downlink power control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/18—TPC being performed according to specific parameters
    • H04W52/22—TPC being performed according to specific parameters taking into account previous information or commands
    • H04W52/226—TPC being performed according to specific parameters taking into account previous information or commands using past references to control power, e.g. look-up-table
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/18—TPC being performed according to specific parameters
    • H04W52/24—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters
    • H04W52/243—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters taking into account interferences
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/04—TPC
    • H04W52/18—TPC being performed according to specific parameters
    • H04W52/24—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters
    • H04W52/247—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters where the output power of a terminal is based on a path parameter sent by another terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • 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

Definitions

  • Some embodiments described herein generally relate to inter-node communication.
  • a cell may suffer co-channel interference from one or more neighboring cells.
  • the co-channel interference may be a dominant limiting factor for achieving higher network efficiency, for example, for cell edge users.
  • Downlink (DL) Coordinated Multi-Point (CoMP) schemes attempt to address the inter- cell interference, by using coordination schemes on a network side to coordinate between transmitting nodes.
  • the DL CoMP schemes assume an Evolved Node B (eNB) architecture with multiple remote radio heads (RRH), a central processing unit, which is responsible for signal processing and coordination of RRHs, and ideal, e.g., high capacity and low latency, backhaul links to connect between the RRHs and the central processing unit.
  • eNB Evolved Node B
  • RRH remote radio heads
  • ideal e.g., high capacity and low latency
  • backhaul links to connect between the RRHs and the central processing unit.
  • usage of the DL CoMP schemes may be limited to very specific deployments, since ideal or close-to-ideal backhaul links may not be available in many deployments.
  • the frequency-domain ICIC may be used to assign different Transmit (TX) power levels to different subcarriers, and to allocate the subcarriers to User Equipment (UE) based on UE locations with respect to a cell edge.
  • TX Transmit
  • UE User Equipment
  • non-overlapping subcarriers across neighboring cells may be allocated to the cell edge UEs, and overlapping subcarriers may be simultaneously allocated to UEs located at centers of the cells.
  • different power levels may be used to prevent cell edge UEs, which are served by neighboring cells, from being affected by inter-cell interference.
  • the frequency-domain ICIC may be implemented by exchanging a Relative Narrowband TX Power indication (RNTP) signaling messages to provide an indication on DL power restriction per Physical Resource Block (PRB) in a cell.
  • RTP Relative Narrowband TX Power indication
  • the current RNTP signaling is limited to specific deployments, and is not able to support other deployments.
  • FIG. 1 is a schematic illustration of a cellular system, in accordance with some demonstrative embodiments.
  • FIG. 2 is a schematic block diagram illustration of a cellular node, in accordance with some demonstrative embodiments.
  • Fig. 3 is a schematic illustration of a Heterogeneous Network (HetNet) deployment, in accordance with some demonstrative embodiments.
  • HetNet Heterogeneous Network
  • Fig. 4 is a schematic flow-chart illustration of a method of inter-node communication, in accordance with some demonstrative embodiments.
  • Fig. 5 is a schematic flow-chart illustration of a method of inter-node communication, in accordance with some demonstrative embodiments.
  • FIG. 6 is a schematic illustration of a product, in accordance with some demonstrative embodiments.
  • Discussions herein utilizing terms such as, for example, “processing”, “computing”, “calculating”, “determining”, “establishing”, “analyzing”, “checking”, or the like, may refer to operation(s) and/or process(es) of a computer, a computing platform, a computing system, or other electronic computing device, that manipulate and/or transform data represented as physical (e.g., electronic) quantities within the computer's registers and/or memories into other data similarly represented as physical quantities within the computer's registers and/or memories or other information storage medium that may store instructions to perform operations and/or processes.
  • the terms “plurality” and “a plurality”, as used herein, include, for example, “multiple” or “two or more”. For example, "a plurality of items” includes two or more items.
  • references to "one embodiment,” “an embodiment,” “demonstrative embodiment,” “various embodiments,” etc., indicate that the embodiment(s) so described may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrase “in one embodiment” does not necessarily refer to the same embodiment, although it may.
  • Some embodiments may be used in conjunction with various devices and systems, for example, a User Equipment (UE), a Mobile Device (MD), a wireless station (STA), a Personal Computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a Smartphone device, a server computer, a handheld computer, a handheld device, a Personal Digital Assistant (PDA) device, a handheld PDA device, an onboard device, an off-board device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless Access Point (AP), a wireless node, a base station (BS), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wireless network, a wireless area network, a
  • Some embodiments may be used in conjunction with devices and/or networks operating in accordance with existing Long Term Evolution (LTE) specifications (including 3 GPP TS 36.423 (3GPP TS 36.423 V12.0.0 (2013-12); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 application protocol (X2AP) (Release 12)), and/or 3 GPP TS 36.213 (3 GPP TS 36.213 VI 2.0.0 (2013-12); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures (Release 12)))), and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing IEEE 802.16 standards (IEEE-Std 802.16, 2009 Edition, Air Interface for Fixed Broadband Wireless Access Systems; IEEE-Std 802.16e, 2005 Edition, Physical and Medium Access Control Layers
  • Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems, for example, Radio Frequency (RF), Frequency-Division Multiplexing (FDM), Orthogonal FDM (OFDM), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time-Division Multiplexing (TDM), Time -Division Multiple Access (TDM A), Extended TDMA (E-TDMA), General Packet Radio Service (GPRS), extended GPRS, Code-Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA 2000, single- carrier CDMA, multi-carrier CDMA, Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT), Bluetooth®, Global Positioning System (GPS), Wireless Fidelity (Wi-Fi), Wi-Max, ZigBeeTM, Ultra- Wideband (UWB), Global System for Mobile communication (GSM), second generation (2G), 2.5G, 3G, 3.5G, 4G, Fifth Generation (5G), Fifth Generation
  • wireless device includes, for example, a device capable of wireless communication, a communication device capable of wireless communication, a communication station capable of wireless communication, a portable or non-portable device capable of wireless communication, or the like.
  • a wireless device may be or may include a peripheral that is integrated with a computer, or a peripheral that is attached to a computer.
  • the term "wireless device” may optionally include a wireless service.
  • the term "communicating" as used herein with respect to a wireless communication signal includes transmitting the wireless communication signal and/or receiving the wireless communication signal.
  • a wireless communication unit which is capable of communicating a wireless communication signal, may include a wireless transmitter to transmit the wireless communication signal to at least one other wireless communication unit, and/or a wireless communication receiver to receive the wireless communication signal from at least one other wireless communication unit.
  • the verb "communicating” may be used to refer to the action of transmitting or the action of receiving.
  • the phrase “communicating a signal” may refer to the action of transmitting the signal by a first device, and may not necessarily include the action of receiving the signal by a second device.
  • the phrase “communicating a signal” may refer to the action of receiving the signal by a first device, and may not necessarily include the action of transmitting the signal by a second device.
  • UMTS Universal Mobile Telecommunications System
  • GSM Global System for Mobile communications
  • 3G cellular network a 4G cellular network
  • 4G cellular network a 4.5G network
  • 5G cellular network a WiMax cellular network
  • HetNet Heterogeneous Network
  • the HetNet may utilize a deployment of a mix of technologies, frequencies, cell sizes and/or network architectures, e.g., including cellular, mm Wave, and/or the like.
  • the HetNet may include a radio access network having layers of different-sized cells ranging from large macrocells to small cells, for example, picocells and femtocells.
  • Other embodiments may be used in conjunction with any other suitable wireless communication network.
  • antenna may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays.
  • the antenna may implement transmit and receive functionalities using separate transmit and receive antenna elements.
  • the antenna may implement transmit and receive functionalities using common and/or integrated transmit/receive elements.
  • the antenna may include, for example, a phased array antenna, a single element antenna, a dipole antenna, a set of switched beam antennas, and/or the like.
  • cell as used herein, may include a combination of network resources, for example, downlink and optionally uplink resources.
  • cellular system 100 may include a 4 th generation cellular system such as, for example, a long term evolution (LTE) or LTE advance cellular system, a WiMAX cellular system, and the like. In other embodiments, system 100 may include any other cellular system.
  • LTE long term evolution
  • WiMAX WiMAX
  • system 100 may include a plurality of cellular nodes, e.g., including cellular nodes 106 and 108, capable of communicating content, data, information and/or signals corresponding to a plurality of cells, e.g., including cells 102 and 104.
  • node 106 may communicate with a plurality of User Equipment (UE) devices 110 within cell 102 and/or node 108 may communicate with a plurality of UE devices 112 within cell 104.
  • UE User Equipment
  • nodes 106 and/or 108 may include an Evolved Node B (eNB).
  • nodes 106 and/or 108 may be configured to perform radio resource management (RRM), radio bearer control, radio admission control (access control), connection mobility management, resource scheduling between UEs and eNB radios, e.g., Dynamic allocation of resources to UEs in both uplink and downlink, header compression, link encryption of user data streams, packet routing of user data towards a destination, e.g., another eNB or an Evolved Packet Core (EPC), scheduling and/or transmitting paging messages, e.g., incoming calls and/or connection requests, broadcast information coordination, measurement reporting, and/or any other operations.
  • RRM radio resource management
  • radio bearer control radio admission control
  • access control access control
  • connection mobility management e.g., Dynamic allocation of resources to UEs in both uplink and downlink
  • resource scheduling between UEs and eNB radios e.g., Dynamic allocation
  • nodes 106 and/or 108 may include any other functionality and/or may perform the functionality of any other cellular node, e.g., a Node B (NB), a Base Station (BS), and the like.
  • NB Node B
  • BS Base Station
  • nodes 106 and 108 may communicate via one or more backhaul links, e.g., via a backhaul link 105.
  • nodes 106 and 108 may communicate via backhaul link 105 according to an X2 Application Protocol (X2AP) signaling protocol, e.g., as described below. In other embodiments, nodes 106 and 108 may communicate via backhaul link 105 according to any other signaling protocol.
  • X2AP X2 Application Protocol
  • backhaul link 105 may include a wireless link. In other embodiments, backhaul link 105 may include a wired link, a fiber link, or any combination of wired, fiber and/or wireless links.
  • UEs 110 and/or 112 may include, for example, a mobile computer, a MD, a STA, a laptop computer, a notebook computer, a tablet computer, an UltrabookTM computer, a mobile internet device, a handheld computer, a handheld device, a storage device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a mobile phone, a cellular telephone, a PCS device, a mobile or portable GPS device, a DVB device, a relatively
  • cellular node 200 may perform the functionality of node 106 (Fig. 1) and/or node 108 (Fig. 1).
  • cellular node 200 may include an air interface, for example, a cellular transceiver (TRx) 202, configured to communicate with one or more UEs.
  • TRx cellular transceiver
  • cellular TRx 202 may include one or more wireless transmitters, receivers and/or transceivers able to send and/or receive wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data.
  • cellular TRx 202 may include a multiple input multiple output (MIMO) transmitters receivers system (not shown), which may be capable of performing antenna beamforming methods, if desired.
  • cellular TRx 202 may include any other transmitters and/or receivers.
  • cellular TRx 202 may include LTE, WCDMA and/or TD-SCDMA modulators and/or demodulators (not shown) configured to communicate downlink signals over downlink channels, e.g., between node 200 and a UE, and uplink signals over uplink channels, e.g., between a UE and node 200.
  • cellular TRx 202 may include any other modulators and/or demodulators.
  • cellular TRx 202 may include a turbo decoder and/or a turbo encoder (not shown) for encoding and/or decoding data bits into data symbols, if desired.
  • cellular TRx 202 may include OFDM and/or SC- FDMA modulators and/or demodulators (not shown) configured to communicate OFDM signals over the downlink (DL) channels, and/or SC-FDMA signals over the uplink (UL) channels.
  • node 200 may include, or may be associated with, one or more antennas.
  • node 200 may be associated with at least two antennas, e.g., antennas 208 and 210.
  • node 200 may be associated with one antenna or more than two antennas.
  • antennas 208 and/or 210 may include any type of antennas suitable for transmitting and/or receiving wireless communication signals, blocks, frames, transmission streams, packets, messages and/or data.
  • antennas 208 and/or 210 may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays.
  • antennas 208 and/or 210 may include a phased array antenna, a dipole antenna, a single element antenna, a set of switched beam antennas, and/or the like.
  • antennas 208 and/or 210 may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some embodiments, antennas 208 and/or 210 may implement transmit and receive functionalities using common and/or integrated transmit/receive elements.
  • node 200 may include a backhaul interface 230 to communicate between node 200 and one or more other nodes via a backhaul link. For example, backhaul interface 230 may communicate between nodes 106 (Fig. 1) and 108 (Fig. 1), e.g., via backhaul link 105 (Fig. 1).
  • backhaul interface 230 may include an X2AP interface. In other embodiments, backhaul interface 230 may include any other interface.
  • node 200 may include a controller 240 to control one or more functionalities of node 200 and/or to control one or more communications performed by node 200, for example, to control inter-node communications between nodes 106 and 108 (Fig. 1), to control communications between node 200 and one or more UEs, and/or to control communications between node 200 and one or more other network elements, e.g., as described below.
  • a controller 240 to control one or more functionalities of node 200 and/or to control one or more communications performed by node 200, for example, to control inter-node communications between nodes 106 and 108 (Fig. 1), to control communications between node 200 and one or more UEs, and/or to control communications between node 200 and one or more other network elements, e.g., as described below.
  • controller 240 may perform the functionality of a scheduler to schedule communications of a UE, e.g., as described below. For example, controller 240 may schedule communications of one or more UEs 110 (Fig. 1), e.g., if node 200 performs the functionality of node 106 (Fig. 1); or controller 240 may schedule communications of one or more UEs 112 (Fig. 1), e.g., if node 200 performs the functionality of node 108 (Fig. 1).
  • controller 240 may include or may be implemented using suitable circuitry, e.g., controller circuitry, scheduler circuitry, processor circuitry, memory circuitry, and/or any other circuitry, which may be configured to perform at least part of the functionality of controller 240. Additionally or alternatively, one or more functionalities of controller 240 may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below.
  • suitable circuitry e.g., controller circuitry, scheduler circuitry, processor circuitry, memory circuitry, and/or any other circuitry, which may be configured to perform at least part of the functionality of controller 240.
  • one or more functionalities of controller 240 may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below.
  • cellular node 200 may include, for example, one or more of a processor 220, a memory unit 222, and a storage unit 224.
  • processor, 220 memory 222 and/or storage 224 may be implemented as one or more elements separate from transceiver 202, and/or controller 240.
  • processor, 220 memory 222 and/or storage 224 may be implemented as part of transceiver 202, and/or controller 240.
  • Processor 220 includes, for example, a Central Processing Unit (CPU), a Digital Signal Processor (DSP), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, circuitry, a logic unit, an Integrated Circuit (IC), an Application-Specific IC (ASIC), or any other suitable multi-purpose or specific processor or controller.
  • Processor 220 executes instructions, for example, of an Operating System (OS) of node 200 and/or of one or more suitable applications.
  • OS Operating System
  • Memory unit 222 includes, for example, a Random Access Memory (RAM), a Read Only Memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM (SD-RAM), a flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units.
  • Storage unit 224 includes, for example, a hard disk drive, a floppy disk drive, a Compact Disk (CD) drive, a CD- ROM drive, a DVD drive, or other suitable removable or non-removable storage units.
  • Memory unit 222 and/or storage unit 224 may store data processed by node 200.
  • nodes 106 and 108 to communicate inter-node communications, e.g., inter-node signaling messages, which may be configured, for example, to coordinate communications between cells 102 and 104, e.g., as described below.
  • inter-node communications between nodes 106 and 108 may be configured, for example, to mitigate inter-cell interference between cells 102 and 104, e.g., as described below.
  • the inter-node communications between nodes 106 and 108 may be configured, for example, to facilitate improved, efficient, and/or flexible Downlink (DL) Coordinated Multi-Point (CoMP) schemes, e.g., as described below.
  • DL Downlink
  • CoMP Coordinated Multi-Point
  • the inter-node communications between nodes 106 and 108 may be configured, for example, to enable coordination of scheduling and/or precoding settings (also referred to as "beamforming settings") between nodes 106 and 108, e.g., as described below.
  • nodes 106 and 108 may be configured to coordinate the scheduling and/or precoding setting using signaling messages communicated via backhaul link 105 between nodes 106 and 108, e.g., as described below.
  • the ability to communicating the signaling messages via backhaul link 105 between nodes 106 and 108 may enable, for example, utilizing a DL CoMP scheme in deployment scenarios, which may, for example, have non-ideal or sub- optimal backhaul links.
  • nodes 106 and 108 may be configured to communicate via backhaul link 105 one or more signaling messages including one or more precoding restriction settings, for example, in the form of a Codebook Subset Restriction (also referred to as "codebookSubsetRestriction”) parameter, which may be configured to provide an indication of a precoding restriction in a cell.
  • the codebookSubsetRestriction may be configured to provide a precoding restriction per resource block, for example, per Physical Resource Block (PRB) or a wideband resource, e.g., as described below.
  • PRB Physical Resource Block
  • cellular TRx 202 (Fig. 2) of node 106 may communicate with UE 110 in cell 102.
  • controller 240 (Fig. 2) of node 106 may determine a precoding restriction setting, for example, based on downlink communications to the UE 110.
  • backhaul interface 230 (Fig. 2) of node 106 may send to node 108 a signaling message including the precoding restriction setting, e.g., via backhaul link 105, for example, as described below.
  • controller 240 (Fig. 2) of node 108 may schedule communications for one or more UEs 112 of cell 104, for example, based on the precoding restriction setting received from node 106, e.g., via backhaul link 105.
  • controller 240 (Fig. 2) of node 106 may determine the precoding restriction setting, for example, while taking into account a precoding restriction setting recommendation from node 108, e.g., as described below.
  • node 108 may receive Channel State Information from one or more UEs 112 of cell 104, and controller 240 (Fig. 2) of node 108 may determine the precoding restriction setting recommendation based on the CSL
  • the CSI may include, for example, information relating to a Precoding Matrix indicator (PMI), a Channel Quality Indicator (CQI), a Rank Indicator (RI), Precoding Type Indicator (PTI), or any combination thereof.
  • the CSI information may include information of any additional or alternative CSI-related parameter, e.g., corresponding to a channel between a node and a UE.
  • backhaul interface 230 (Fig. 2) of node 108 may send to node 106 a signaling message including the precoding restriction setting recommendation, e.g., via backhaul link 105, for example, as described below.
  • node 106 may send the precoding restriction setting, and/or node 108 may send the precoding restriction setting recommendation in the form of a beamforming restriction setting bitmap, which may be configured to indicate a restricted precoding parameter corresponding to a precoding codebook, e.g., as described below.
  • nodes 106 and 108 may communicate the precoding restriction setting and/or the precoding restriction setting recommendation in the form of a message including a codebookSubsetRestriction Information Element (IE), and a Number of CSI Reference Signals (CSI-RS) Antenna Ports IE, e.g., as described below.
  • IE codebookSubsetRestriction Information Element
  • CSI-RS Number of CSI Reference Signals
  • nodes 106 and 108 may communicate the precoding restriction setting and/or the precoding restriction setting recommendation in the form of the following IEs:
  • the Number Of Channel State Information Reference Signals (CSI-RS) Antenna Ports IE may indicate a codebook to be used for precoding restrictions using the codebookSubsetRestriction .
  • the codebookSubsetRestriction IE may include, for example, a bitmap indicating a restricted precoding parameter corresponding to the codebook.
  • the restricted precoding parameter may include, for example, a PMI, a RI, a PTI, or any other precoding parameter.
  • the bitmap may include, for example, an indication of a restriction on the precoding parameter.
  • the bitmap may indicate a restriction on the PMI.
  • the bitmap may include a plurality of bits corresponding to a plurality of PMI values, e.g., according to the codebook.
  • a bit corresponding to a PMI value may have, for example, a first value, e.g., "0", to indicate that the PMI value is to be restricted, or a second value, e.g., "1", to indicate that the PMI value is not to be restricted.
  • nodes 106 and 108 may communicate the precoding restriction setting and/or the precoding restriction setting recommendation to indicate precoding restrictions per two or more resources.
  • nodes 106 and 108 may communicate the precoding restriction setting and/or the precoding restriction setting recommendation to indicate precoding restrictions per resources of a frequency domain, for example, per PRB, per frequency sub-band, or per any other frequency-domain resource .
  • nodes 106 and 108 may communicate the precoding restriction setting and/or the precoding restriction setting recommendation to indicate precoding restrictions per resources of a time domain, for example, per an Almost Blank Subframe (ABS) pattern, or per any other time-domain resource.
  • nodes 106 and 108 may communicate the precoding restriction setting and/or the precoding restriction setting recommendation in the form of an X2AP message.
  • nodes 106 and 108 may communicate the X2AP message via backhaul link 105.
  • nodes 106 and 108 may communicate the precoding restriction setting and/or the precoding restriction setting recommendation as part of an X2AP Load Information message, e.g., described below. In other embodiments, nodes 106 and 108 may communicate the precoding restriction setting and/or the precoding restriction setting recommendation as part of any other X2AP message and/or as part of any other type of message. [0080] In some demonstrative embodiments, nodes 106 and 108 may communicate a plurality of sets of Relative Narrowband Transmit (Tx) Power (RNTP) parameters, which may be configured to provide RNTP settings corresponding to a plurality of RNTP thresholds, e.g., as described below.
  • Tx Relative Narrowband Transmit
  • RNTP Relative Narrowband Transmit
  • signaling the plurality of sets of RNTP parameters between nodes 106 and 108 may enable nodes 106 and 108 to provide one another with RNTP parameters at an increased level of granularity, which, in turn, may increase an efficiency and/or accuracy of coordination between nodes 106 and 108.
  • controller 240 (Fig. 2) of node 106 may determine a RNTP setting, for example, based on downlink communications to the UE 110.
  • backhaul interface 230 (Fig. 2) of node 106 may send to node 108 a signaling message including the RNTP setting, e.g., via backhaul link 105, for example, as described below.
  • controller 240 (Fig. 2) of node 108 may schedule communications for one or more UEs 112 of cell 104, for example, based on the RNTP setting received from node 106, e.g., via backhaul link 105.
  • controller 240 (Fig. 2) of node 106 may determine the RNTP setting, for example, while taking into account a RNTP setting recommendation from node 108, e.g., as described below.
  • controller 240 (Fig. 2) of node 108 may determine the RNTP setting recommendation based on the CSI from one or more of UEs 112.
  • backhaul interface 230 (Fig. 2) of node 108 may send to node 106 a signaling message including the RNTP setting recommendation, e.g., via backhaul link 105, for example, as described below.
  • the RNTP setting and/or the RNTP setting recommendation may include a plurality of RNTP bitmaps corresponding to a respective plurality of different RNTP thresholds, e.g., as described below.
  • an RNTP bitmap of the plurality of RNTP bitmaps may include a plurality of bits corresponding to a respective plurality of PRBs.
  • a bit corresponding to a PRB may have a value to indicate if a transmit power of the PRB is not to exceed an RNTP threshold corresponding to the RNTP bitmap, e.g., as described below.
  • nodes 106 and 108 may communicate the RNTP setting and/or the RNTP setting recommendation in the form of a message including an RNTP IE, e.g., as described below.
  • nodes 106 and 108 may communicate the RNTP setting and/or the RNTP setting recommendation including at least two RNTP bitmaps corresponding to two RNTP thresholds, e.g., as follows:
  • Threshold (- ⁇ , -l l, -10, -9, defined in TS
  • the element RNTPl Threshold includes a first RNTP threshold
  • the element RNTPl per PRB includes a first RNTP bitmap corresponding to the first RNTP threshold
  • the element RNTP2 Threshold includes a second RNTP threshold
  • the element RNTP2 per PRB includes a second RNTP bitmap corresponding to the second RNTP threshold.
  • an RNTP bitmap corresponding to a RNTP threshold may include a plurality of bits corresponding to a respective plurality of PRBs.
  • an RNTP bit value of the RNTP bitmap may indicate whether a corresponding PRB is limited by a transmit power threshold or not.
  • an RNTP bit corresponding to a PRB may have either a first value, e.g., "0", to indicate that a transmit power corresponding to the PRB is not to exceed the RNTP threshold, or a second value, e.g., "1", to indicate no guarantee regarding the transmit power corresponding to the PRB.
  • an RNTP value, denoted RNTP(n PRB ) of the RNTP bit may have granularity of one PRB, e.g., as follows:
  • E A denotes a maximum intended Energy Per Resource Element (EPRE) of UE-specific Physical Downlink Shared Channel (PDSCH) Resource Elements (REs) in OFDM symbols not containing RS in a physical resource block on an antenna port, denoted p, in a considered future time interval
  • n PRB denotes a physical resource block number
  • RNTP threshold denotes the RNTP threshold, e.g., a value selected from RNTP lhreshold e ⁇ -oo -11 -10 -9 -8 -7 -6 -5 -4 -3 -2 -l,0,+l,+2,+3 ⁇ [dB], wherein:
  • P ⁇ is a base station maximum output power
  • Af , N ⁇ andN ⁇ include parameters, e.g., defined, for example, in 3 GPP TS 36.211 (3GPP TS 36.211 V12.0.0 (2013-12); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation (Release 12)).
  • the RNTP bitmap may be defined according to any other scheme, and/or values.
  • the plurality of RNTP bitmaps may enable communicating between nodes 106 and 108 RNTP information at an increased level of granularity.
  • using the first and second RNTP bitmaps may enable to indicate, for a PRB, whether the transmit power corresponding to the PRB is to be below a first threshold, whether the transmit power corresponding to the PRB is to be between the first and second thresholds, or whether the transmit power corresponding to the PRB is not guaranteed to be below he second threshold.
  • the RNTP setting and/or the RNTP setting recommendation may include more than two RNTP bitmaps corresponding to more than two RNTP thresholds, e.g., three or more RNTP bitmaps corresponding to three or more RNTP thresholds.
  • nodes 106 and 108 may communicate the RNTP setting and/or the RNTP setting recommendation in the form of an X2AP message.
  • nodes 106 and 108 may communicate the X2AP message via backhaul link 105.
  • nodes 106 and 108 may communicate the RNTP setting and/or the RNTP setting recommendation as part of an X2AP Load Information message, e.g., described below. In other embodiments, nodes 106 and 108 may communicate the RNTP setting and/or the RNTP setting recommendation as part of any other X2AP message and/or as part of any other type of message.
  • nodes 106 and 108 may communicate via backhaul link 105 one or more signaling messages to indicate restrictions, e.g., power setting restrictions, in a time domain, e.g., as described below.
  • nodes 106 and 108 may communicate via backhaul link 105 one or more signaling messages including a Relative Wideband Transmit Power (RWTP) setting, e.g., as described below.
  • RWTP Relative Wideband Transmit Power
  • signaling the RWTP setting between nodes 106 and 108 may enable nodes 106 and 108 to provide one another with transmit power restrictions in the time domain, which, in turn, may increase an efficiency and/or accuracy of coordination between nodes 106 and 108, e.g., with respect to resource usage in the time domain.
  • controller 240 (Fig. 2) of node 106 may determine a RWTP setting, for example, based on downlink communications to the UE 110.
  • backhaul interface 230 (Fig. 2) of node 106 may send to node 108 a signaling message including the RWTP setting, e.g., via backhaul link 105, for example, as described below.
  • controller 240 (Fig. 2) of node 108 may schedule communications for one or more UEs 112 of cell 104, for example, based on the RWTP setting received from node 106, e.g., via backhaul link 105.
  • controller 240 (Fig. 2) of node 106 may determine the RWTP setting, for example, while taking into account a RWTP setting recommendation from node 108, e.g., as described below.
  • controller 240 (Fig. 2) of node 108 may determine the RWTP setting recommendation based on the CSI from one or more of UEs 112.
  • backhaul interface 230 (Fig. 2) of node 108 may send to node 106 a signaling message including the RWTP setting recommendation, e.g., via backhaul link 105, for example, as described below.
  • the RWTP setting and/or the RWTP setting recommendation may include at least one RWTP bitmap corresponding to at least one respective different RWTP threshold, e.g., as described below.
  • the RWTP bitmap may include a plurality of bits corresponding to a respective plurality of time domain resource elements, e.g., a plurality of time slots ("slots"), a plurality of sub-frames, and/or any other time domain resources.
  • a bit corresponding to a time domain resource element may have a value to indicate if a transmit power of the time domain resource element is not to exceed the RWTP threshold corresponding to the RWTP bitmap, e.g., as described below.
  • nodes 106 and 108 may communicate the RWTP setting and/or the RWTP setting recommendation in the form of a message including an RWTP IE, e.g., as described below.
  • nodes 106 and 108 may communicate the RWTP setting and/or the RWTP setting recommendation including at least one RWTP bitmaps corresponding to at least one RWTP threshold.
  • nodes 106 and 108 may communicate the RWTP setting and/or the RWTP setting recommendation with respect to a plurality of slots, e.g., as follows:
  • Threshold RATED defined in TS 36.213
  • an RWTP bitmap corresponding to a RWTP threshold may include a plurality of bits corresponding to a respective plurality of time domain resources, e.g., slots.
  • an RWTP bit value of the RWTP bitmap may indicate whether a corresponding slot is limited by a transmit power threshold or not.
  • an RWTP bit corresponding to a slot may have either a first value, e.g., "0", to indicate that a transmit power corresponding to the slot is not to exceed the RWTP threshold, or a second value, e.g., "1", to indicate no guarantee regarding the transmit power corresponding to the slot.
  • an RWTP value, denoted RWTP(n s ), of the RWTP bit may have granularity of one slot, e.g., as follows:
  • E A denotes a maximum intended Energy Per Resource Element (EPRE) of UE- specific PDSCH Resource Elements (REs) in OFDM symbols not containing RS in a slot, denoted S, on the antenna port p, in a considered future time interval
  • RWTP threshold denotes the RWTP threshold, e.g., a value selected from RWTP threshold e ⁇ - ⁇ ,-ll -10,-9,-8 -7,-6,-5 -4 -3,-2 ,-l,0,+l,+2,+3 ⁇ [dB], wherein:
  • the RWTP bitmap may be defined according to any other scheme, and/or values.
  • the RWTP setting may be defined with respect to any other time domain resource.
  • the RWTP setting may be defined per subframe.
  • the RWTP bitmap may include a bit string of length 10, e.g., corresponding to the ten sub frames n s .
  • the number of bits allocated for the RWTP bitmap may be set in accordance with a number of downlink subframes of an UL/DL Time Division Duplexing (TDD) configuration used in a given cell, e.g., if the RWTP setting is not to be applicable to uplink subframes for the TDD configuration.
  • TDD Time Division Duplexing
  • the RWTP setting and/or the RWTP setting recommendation may include a plurality of RWTP bitmaps corresponding to a respective plurality of different RWTP thresholds.
  • the RWTP setting and/or the RWTP setting recommendation may include at least two RWTP bitmaps corresponding to at least two RWTP thresholds, e.g., a first RWTP bitmap corresponding to a first RWTP threshold, and a second RWTP bitmap corresponding to a second RWTP threshold.
  • the plurality of RWTP bitmaps may enable communicating between nodes 106 and 108 RWTP information at an increased level of granularity.
  • using the first and second RWTP bitmaps may enable to indicate, for a time domain resource, e.g., a slot or a subframe, whether the transmit power corresponding to the time domain resource is to be below the first RWTP threshold, whether the transmit power corresponding to the time domain resource is to be between the first and second RWTP thresholds, or whether the transmit power corresponding to the time domain resource is not guaranteed to be below the second RWTP threshold.
  • the RWTP setting may be communicated between nodes 106 and 108 using one or more RNTP parameter sets.
  • one or more RNTP per PRB bitmaps corresponding to one or more respective RNTP thresholds may be signaled by node 106 and/or node 108, for example for each time domain resource, e.g., for each subframe within a frame, to indicate different configurations of power allocation restrictions in the time domain.
  • nodes 106 and 108 may communicate the RWTP setting and/or the RWTP setting recommendation in the form of an X2AP message.
  • nodes 106 and 108 may communicate the X2AP message via backhaul link 105.
  • nodes 106 and 108 may communicate the RWTP setting and/or the RWTP setting recommendation as part of an X2AP message, e.g., described below. In other embodiments, nodes 106 and 108 may communicate the RWTP setting and/or the RWTP setting recommendation as part of any other X2AP message and/or as part of any other type of message.
  • nodes 106 and 108 may communicate one or more restriction settings via an X2AP message.
  • node 106 may send to node 108, e.g., via backhaul link 105, an X2AP message including the precoding restriction setting, the RNTP setting, and/or the RWTP setting; and/or node 108 may send to node 106, e.g., via backhaul link 105, an X2AP message including the precoding restriction setting recommendation, the RNTP setting recommendation, and/or the RWTP setting recommendation.
  • nodes 106 and 108 may communicate the precoding restriction setting and/or recommendation, the RNTP setting and/or recommendation, and/or the RWTP setting and/or recommendation via an X2AP Load Information message, e.g., as follows:
  • a firs node (“the victim node”), e.g., node 108, which may serve one or more UEs ("the victim UEs"), e.g., cell edge UEs, subject to interference from a second node (“the interfering node"), e.g., node 106.
  • the victim node may send one or more recommended restriction settings, e.g., the precoding restriction recommendation, the RNTP setting recommendation, and/or the RWTP setting recommendation to the interfering node, e.g., via backhaul link 105.
  • node 108 may determine the precoding restriction recommendation, the RNTP setting recommendation, and/or the RWTP setting recommendation, based on the CSI from the victim UEs, e.g., as described above.
  • the interfering node may determine one or more restriction settings, e.g., the precoding restriction, the RNTP setting, and/or the RWTP setting, and may send the restriction settings to the victim node, e.g., via backhaul link 105.
  • FIG. 3 schematically illustrates a HetNet deployment including a macro eNB 302 and a plurality of small cell (SC) eNBs 304, in accordance with some demonstrative embodiments.
  • macro eNB 302 may perform the functionality of node 106 (Fig. 1)
  • small cell eNB 304 may perform the functionality of node 108 (Fig. 1).
  • macro eNB 302 may be configured to perform interference avoidance in a spatial domain towards one or more UEs 306, e.g., cell-edge UEs, of a neighboring small cell eNB 304, e.g., based on CSI feedback corresponding to interfering channels.
  • macro eNB 302 may inform small cell eNB 304 of one or more restriction settings, for example, a precoding restriction setting, a RNTP setting, and/or a RWTP setting, e.g., as described above.
  • small cell eNB 304 may perform user scheduling, e.g., to schedule communications of UEs 306, for example, by considering the restriction setting from macro cell 302, e.g., on specific time and/or frequency resources.
  • macro eNB 302 may restrict use of certain PMIs on specific time frequency resources, e.g., PMIs, which may create the high interference to the cell-edge UEs 306 of the neighboring cells.
  • Small cell eNB 304 may schedule the cell-edge UE 306 on the time and/or frequency resources, for example, in accordance with the restriction settings, e.g., to avoid the interference.
  • small cell node 304 may determine recommended precoding restriction, RNTP, and/or RWTP settings, and small cell node 304 may signal recommended precoding restriction, RNTP, and/or RWTP settings to macro eNB 302, as recommendation for interference coordination, e.g., as described above.
  • Macro eNB 302 may respond to small cell eNB 304 with restriction setting decisions on some or all time and/or frequency resources, e.g., as described above.
  • Fig. 4 is a schematic flow-chart illustration of a method of inter-node communication, in accordance with some demonstrative embodiments. In some demonstrative embodiments, one or more operations of the method of Fig. 4 may be performed at a first node, e.g., node 108 (Fig. 1).
  • the method may include receiving CSI from one or more UEs, e.g., with respect to one or more channels ("the interfering channels") suffering interference from a second node.
  • node 108 may receive from UEs 112 (Fig. 1) CSI corresponding to one or more channels, which may suffer interference from node 106 (Fig. 1), e.g., as described above.
  • the method may include determining one or more restriction recommendations, e.g., based on the CSI.
  • controller 240 (Fig. 2) of node 108 (Fig. 1) may determine a precoding restriction recommendation, a R TP setting recommendation, and/or a RWTP setting recommendation, e.g., as described above.
  • the method may include sending to the second node at least one signaling message including the one or more restriction recommendations, e.g., via a backhaul link.
  • node 108 may send to node 106 (Fig. 1), e.g., via backhaul ink 105 (Fig. 1), one or more X2AP messages including the precoding restriction recommendation, the RNTP setting recommendation, and/or the RWTP setting recommendation, e.g., as described above.
  • the method may include receiving from the second node at least one signaling message including one or more restriction settings, e.g., via a backhaul link.
  • node 108 (Fig. 1)
  • the method may include scheduling communications for the UEs based on the one or more restriction settings.
  • controller 240 (Fig. 2) of node 108 (Fig. 1) may schedule communications for UEs 112 (Fig. 1), based on the precoding restriction setting, the RNTP setting, and/or the RWTP setting, e.g., as described above.
  • Fig. 5 is a schematic flow-chart illustration of a method of inter-node communication, in accordance with some demonstrative embodiments.
  • one or more operations of the method of Fig. 5 may be performed at a first node, e.g., node 106 (Fig. 1).
  • the method may include receiving from a second node at least one signaling message including one or more restriction recommendations, e.g., via a backhaul link.
  • node 106 (Fig. 1) may receive from node 108 (Fig. 1), e.g., via backhaul link 105 (Fig. 1), one or more X2AP messages including the precoding restriction recommendation, the R TP setting recommendation, and/or the RWTP setting recommendation, e.g., as described above.
  • the method may include determining one or more restriction settings, e.g., based on the one or more restriction recommendations.
  • controller 240 (Fig. 2) of node 106 (Fig. 1) may determine a precoding restriction setting, a RNTP setting, and/or a RWTP setting, e.g., as described above.
  • controller 240 (Fig. 2) of node 106 (Fig. 1) may determine one or more restriction settings, for example, using status of transmissions to one or more of UEs 112 (Fig. 1), which may also be served by node 106 (Fig. 1), for example, while taking into consideration the one or more restriction recommendations, e.g., as described above.
  • the method may include sending to the second node at least one signaling message including the one or more restriction settings, e.g., via a backhaul link.
  • node 106 (Fig. 1) may send to node 108 (Fig. 1), e.g., via backhaul ink 105 (Fig. 1), one or more X2AP messages including the precoding restriction setting, the RNTP setting, and/or the RWTP setting, e.g., as described above.
  • Fig. 6 schematically illustrates a product of manufacture 600, in accordance with some demonstrative embodiments.
  • Product 600 may include a non- transitory machine-readable storage medium 602 to store logic 604, which may be used, for example, to perform at least part of the functionality of a node, e.g., node 106 (Fig. 1), node 108 (Fig. 1), node 200 (Fig. 2), node 302 (Fig. 3), and/or node 304 (Fig. 3); and/or a controller, e.g., controller 240 (Fig. 2); and/or to perform one or more operations of the methods of Fig 4 and/or Fig. 5.
  • the phrase "non-transitory machine -readable medium" is directed to include all computer-readable media, with the sole exception being a transitory propagating signal.
  • product 600 and/or machine -readable storage medium 602 may include one or more types of computer-readable storage media capable of storing data, including volatile memory, non- volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and the like.
  • machine-readable storage medium 602 may include, RAM, DRAM, Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), Compact Disk ROM (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory (e.g., NOR or NAND flash memory), content addressable memory (CAM), polymer memory, phase-change memory, ferroelectric memory, silicon-oxide -nitride- oxide-silicon (SONOS) memory, a disk, a floppy disk, a hard drive, an optical disk, a magnetic disk, a card, a magnetic card, an optical card, a tape, a cassette, and the like.
  • RAM random access memory
  • DDR-DRAM Double-Data-Rate DRAM
  • SDRAM static RAM
  • ROM read-only memory
  • the computer- readable storage media may include any suitable media involved with downloading or transferring a computer program from a remote computer to a requesting computer carried by data signals embodied in a carrier wave or other propagation medium through a communication link, e.g., a modem, radio or network connection.
  • a communication link e.g., a modem, radio or network connection.
  • logic 604 may include instructions, data, and/or code, which, if executed by a machine, may cause the machine to perform a method, process and/or operations as described herein.
  • the machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware, software, firmware, and the like.
  • logic 604 may include, or may be implemented as, software, a software module, an application, a program, a subroutine, instructions, an instruction set, computing code, words, values, symbols, and the like.
  • the instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like.
  • the instructions may be implemented according to a predefined computer language, manner or syntax, for instructing a processor to perform a certain function.
  • the instructions may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language, such as C, C++, Java, BASIC, Matlab, Pascal, Visual BASIC, assembly language, machine code, and the like.
  • Example 1 includes an Evolved Node B (eNB) comprising a cellular transceiver to communicate with a User Equipment (UE); a backhaul interface to receive a precoding restriction setting from another eNB via a backhaul link; and a controller to schedule communications of the UE based on the precoding restriction setting.
  • eNB Evolved Node B
  • UE User Equipment
  • backhaul interface to receive a precoding restriction setting from another eNB via a backhaul link
  • a controller to schedule communications of the UE based on the precoding restriction setting.
  • Example 2 includes the subject matter of Example 1, and optionally, wherein the backhaul interface is to send to the another eNB a precoding restriction recommendation.
  • Example 3 includes the subject matter of Example 2, and optionally, wherein the cellular transceiver is to receive Channel State Information (CSI) from the UE, the controller to determine the precoding restriction recommendation based on the CSI.
  • CSI Channel State Information
  • Example 4 includes the subject matter of any one of Examples 1-3, and optionally, wherein the precoding restriction setting comprises a bitmap indicating a restricted precoding parameter corresponding to a precoding codebook.
  • Example 5 includes the subject matter of any one of Examples 1-4, and optionally, wherein the precoding restriction setting comprises a CodebookSubsetRestriction Information Element (IE) and a Number Of CSI Reference Signals (CSI-RS) Antenna Ports IE.
  • IE CodebookSubsetRestriction Information Element
  • CSI-RS Number Of CSI Reference Signals
  • Example 6 includes the subject matter of any one of Examples 1-5, and optionally, wherein the backhaul interface comprises an X2 Application Protocol (X2-AP) interface.
  • X2-AP X2 Application Protocol
  • Example 7 includes the subject matter of Example 6, and optionally, wherein the backhaul interface is to receive an X2 load information message including the precoding restriction setting.
  • Example 8 includes the subject matter of any one of Examples 1-7, and optionally, comprising one or more antennas; a memory and a processor.
  • Example 9 includes an Evolved Node B (eNB) comprising a cellular transceiver to communicate with a User Equipment (UE); a backhaul interface to receive a Relative Narrowband Transmit (Tx) Power (RNTP) setting from another eNB via a backhaul link, the RNTP setting comprising a plurality of RNTP bitmaps corresponding to respective plurality of different RNTP thresholds; and a controller to schedule communications of the UE based on the RNTP setting.
  • Example 10 includes the subject matter of Example 9, and optionally, wherein the backhaul interface is to send to the another eNB an RNTP recommendation.
  • Example 11 includes the subject matter of Example 10, and optionally, wherein the cellular transceiver is to receive Channel State Information (CSI) from the UE, the controller to determine the RNTP recommendation based on the CSI.
  • Example 12 includes the subject matter of any one of Examples 9-11, and optionally, wherein an RNTP bitmap of the plurality of RNTP bitmaps comprises a plurality of bits corresponding to a respective plurality of Physical Resource Blocks (PRB), a bit corresponding to a PRB to indicate if a transmit power of the PRB is not to exceed an RNTP threshold corresponding to the RNTP bitmap.
  • PRB Physical Resource Block
  • Example 13 includes the subject matter of any one of Examples 9-12, and optionally, wherein the backhaul interface comprises an X2 Application Protocol (X2-AP) interface.
  • X2-AP X2 Application Protocol
  • Example 14 includes the subject matter of Example 13, and optionally, wherein the backhaul interface is to receive an X2 load information message including the RNTP setting.
  • Example 15 includes the subject matter of any one of Examples 9-14, and optionally, comprising one or more antennas; a memory and a processor.
  • Example 16 includes an Evolved Node B (eNB) comprising a cellular transceiver to communicate with a User Equipment (UE); a backhaul interface to receive a Relative Wideband Transmit (Tx) Power (RWTP) setting from another eNB via a backhaul link, the RWTP setting comprising at least one RWTP bitmap corresponding to at least one respective RWTP threshold; and a controller to schedule communications of the UE based on the RWTP setting.
  • Example 17 includes the subject matter of Example 16, and optionally, wherein the backhaul interface is to send to the another eNB an RWTP recommendation.
  • Example 18 includes the subject matter of Example 17, and optionally, wherein the cellular transceiver is to receive Channel State Information (CSI) from the UE, the controller to determine the RWTP recommendation based on the CSI.
  • Example 19 includes the subject matter of any one of Examples 16-18, and optionally, wherein the RWTP bitmap comprises a plurality of bits corresponding to a respective plurality of time domain resource elements, a bit corresponding to a time domain resource element to indicate if a transmit power of the time domain resource element is not to exceed the RWTP threshold.
  • Example 20 includes the subject matter of any one of Examples 16-19, and optionally, wherein the RWTP setting includes a plurality of RWTP bitmaps corresponding a respective plurality of RWTP thresholds.
  • Example 21 includes the subject matter of any one of Examples 16-20, and optionally, wherein the backhaul interface comprises an X2 Application Protocol (X2-AP) interface.
  • Example 22 includes the subject matter of Example 21, and optionally, wherein the backhaul interface is to receive an X2 load information message including the RWTP setting.
  • Example 23 includes the subject matter of any one of Examples 16-22, and optionally, comprising one or more antennas; a memory and a processor.
  • Example 24 includes an Evolved Node B (eNB) comprising a cellular transceiver to communicate with a User Equipment (UE); a controller to determine a precoding restriction setting based on downlink communications to the UE; and a backhaul interface to send the precoding restriction setting to another eNB via a backhaul link.
  • eNB Evolved Node B
  • UE User Equipment
  • controller to determine a precoding restriction setting based on downlink communications to the UE
  • a backhaul interface to send the precoding restriction setting to another eNB via a backhaul link.
  • Example 25 includes the subject matter of Example 24, and optionally, wherein the backhaul interface is to receive a precoding restriction recommendation from the another eNB, the controller to determine the precoding restriction setting based on the precoding restriction recommendation.
  • Example 26 includes the subject matter of Example 24 or 25, and optionally, wherein the precoding restriction setting comprises a bitmap indicating a restricted precoding parameter corresponding to a precoding codebook.
  • Example 27 includes the subject matter of any one of Examples 24-26, and optionally, wherein the precoding restriction setting comprises a CodebookSubsetRestriction Information Element (IE) and a Number Of CSI Reference Signals (CSI-RS) Antenna Ports IE.
  • IE CodebookSubsetRestriction Information Element
  • CSI-RS Number Of CSI Reference Signals
  • Example 28 includes the subject matter of any one of Examples 24-27, and optionally, wherein the backhaul interface comprises an X2 Application Protocol (X2-AP) interface.
  • X2-AP X2 Application Protocol
  • Example 29 includes the subject matter of Example 28, and optionally, wherein the backhaul interface is to send an X2 load information message including the precoding restriction setting.
  • Example 30 includes the subject matter of any one of Examples 24-29, and optionally, comprising one or more antennas; a memory and a processor.
  • Example 31 includes an Evolved Node B (eNB) comprising a cellular transceiver to communicate with a User Equipment (UE); a controller to determine a Relative Narrowband Transmit (Tx) Power (RNTP) setting based on downlink communications to the UE, the RNTP setting comprising a plurality of RNTP bitmaps corresponding to respective plurality of different RNTP thresholds; and a backhaul interface to send the RNTP setting to another eNB via a backhaul link.
  • eNB Evolved Node B
  • UE User Equipment
  • RNTP Relative Narrowband Transmit
  • RNTP Relative Narrowband Transmit
  • Example 32 includes the subject matter of Example 31, and optionally, wherein the backhaul interface is to receive an RNTP recommendation from the another eNB, the controller to determine the RNTP setting based on the RNTP recommendation.
  • Example 33 includes the subject matter of Example 31 or 32, and optionally, wherein an RNTP bitmap of the plurality of RNTP bitmaps comprises a plurality of bits corresponding to a respective plurality of Physical Resource Blocks (PRB), a bit corresponding to a PRB to indicate if a transmit power of the PRB is not to exceed an RNTP threshold corresponding to the RNTP bitmap.
  • PRB Physical Resource Block
  • Example 34 includes the subject matter of any one of Examples 31-33, and optionally, wherein the backhaul interface comprises an X2 Application Protocol (X2-AP) interface.
  • X2-AP X2 Application Protocol
  • Example 35 includes the subject matter of Example 34, and optionally, wherein the backhaul interface is to send an X2 load information message including the RNTP setting.
  • Example 36 includes the subject matter of any one of Examples 31-35, and optionally, comprising one or more antennas; a memory and a processor.
  • Example 37 includes an Evolved Node B (eNB) comprising a cellular transceiver to communicate with a User Equipment (UE); a controller to determine a Relative Wideband Transmit (Tx) Power (RWTP) setting based on downlink communications to the UE, the RWTP setting comprising at least one RWTP bitmap corresponding to at least one respective RWTP threshold; and a backhaul interface to send the RWTP setting to another eNB via a backhaul link.
  • eNB Evolved Node B
  • UE User Equipment
  • RWTP Relative Wideband Transmit
  • RWTP Relative Wideband Transmit
  • backhaul interface to send the RWTP setting to another eNB via a backhaul link.
  • Example 38 includes the subject matter of Example 37, and optionally, wherein the backhaul interface is to receive an RWTP recommendation from the another eNB, the controller to determine the RWTP setting based on the RWTP recommendation.
  • Example 39 includes the subject matter of Example 37 or 38, and optionally, wherein the RWTP bitmap comprises a plurality of bits corresponding to a respective plurality of time domain resource elements, a bit corresponding to a time domain resource element to indicate if a transmit power of the time domain resource element is not to exceed the RWTP threshold.
  • Example 40 includes the subject matter of any one of Examples 37-39, and optionally, wherein the RWTP setting includes a plurality of RWTP bitmaps corresponding a respective plurality of RWTP thresholds.
  • Example 41 includes the subject matter of any one of Examples 37-40, and optionally, wherein the backhaul interface comprises an X2 Application Protocol (X2-AP) interface.
  • Example 42 includes the subject matter of Example 41, and optionally, wherein the backhaul interface is to send an X2 load information message including the RWTP setting.
  • Example 43 includes the subject matter of any one of Examples 37-42, and optionally, comprising one or more antennas; a memory and a processor.
  • Example 44 includes a method to be performed at an Evolved Node B (eNB), the method comprising communicating with a User Equipment (UE); receiving a precoding restriction setting from another eNB via a backhaul link; and scheduling communications of the UE based on the precoding restriction setting.
  • eNB Evolved Node B
  • UE User Equipment
  • Example 45 includes the subject matter of Example 44, and optionally, comprising sending to the another eNB a precoding restriction recommendation.
  • Example 46 includes the subject matter of Example 45, and optionally, comprising receiving Channel State Information (CSI) from the UE, and determining the precoding restriction recommendation based on the CSI.
  • CSI Channel State Information
  • Example 47 includes the subject matter of any one of Examples 44-46, and optionally, wherein the precoding restriction setting comprises a bitmap indicating a restricted precoding parameter corresponding to a precoding codebook.
  • Example 48 includes the subject matter of any one of Examples 44-47, and optionally, wherein the precoding restriction setting comprises a CodebookSubsetRestriction Information Element (IE) and a Number Of CSI Reference Signals (CSI-RS) Antenna Ports IE.
  • IE CodebookSubsetRestriction Information Element
  • CSI-RS Number Of CSI Reference Signals
  • Example 49 includes the subject matter of any one of Examples 44-48, and optionally, wherein the backhaul link comprises a X2 Application Protocol (X2-AP) link.
  • Example 50 includes the subject matter of Example 49, and optionally, comprising receiving an X2 load information message including the precoding restriction setting.
  • Example 51 includes a method to be performed at an Evolved Node B (eNB), the method comprising communicating with a User Equipment (UE); receiving a Relative Narrowband Transmit (Tx) Power (RNTP) setting from another eNB via a backhaul link, the RNTP setting comprising a plurality of RNTP bitmaps corresponding to respective plurality of different RNTP thresholds; and scheduling communications of the UE based on the RNTP setting.
  • eNB Evolved Node B
  • UE User Equipment
  • RNTP Relative Narrowband Transmit
  • RNTP Relative Narrowband Transmit
  • RNTP Relative Narrowband Transmit
  • RNTP setting comprising a plurality of RNTP bitmaps corresponding to respective plurality of different RNTP thresholds
  • Example 52 includes the subject matter of Example 51, and optionally, comprising sending to the another eNB an RNTP recommendation.
  • Example 53 includes the subject matter of Example 52, and optionally, comprising receiving Channel State Information (CSI) from the UE, and determining the RNTP recommendation based on the CSI.
  • CSI Channel State Information
  • Example 54 includes the subject matter of any one of Examples 51-53, and optionally, wherein an RNTP bitmap of the plurality of RNTP bitmaps comprises a plurality of bits corresponding to a respective plurality of Physical Resource Blocks (PRB), a bit corresponding to a PRB to indicate if a transmit power of the PRB is not to exceed an RNTP threshold corresponding to the RNTP bitmap.
  • PRB Physical Resource Block
  • Example 55 includes the subject matter of any one of Examples 51-54, and optionally, wherein the backhaul link comprises an X2 Application Protocol (X2-AP) link.
  • X2-AP X2 Application Protocol
  • Example 56 includes the subject matter of Example 55, and optionally, comprising receiving an X2 load information message including the RNTP setting.
  • Example 57 includes a method to be performed at an Evolved Node B (eNB), the method comprising communicating with a User Equipment (UE); receiving a Relative Wideband Transmit (Tx) Power (RWTP) setting from another eNB via a backhaul link, the RWTP setting comprising at least one RWTP bitmap corresponding to at least one respective RWTP threshold; and scheduling communications of the UE based on the RWTP setting.
  • eNB Evolved Node B
  • UE User Equipment
  • RWTP Relative Wideband Transmit
  • RWTP Relative Wideband Transmit
  • RWTP Relative Wideband Transmit
  • RWTP setting comprising at least one RWTP bitmap corresponding to at least one respective RWTP threshold
  • scheduling communications of the UE based on the RWTP setting.
  • Example 58 includes the subject matter of Example 57, and optionally, comprising sending to the another eNB an RWTP recommendation.
  • Example 59 includes the subject matter of Example 58, and optionally, comprising receiving Channel State Information (CSI) from the UE, and determining the RWTP recommendation based on the CSI.
  • CSI Channel State Information
  • Example 60 includes the subject matter of any one of Examples 57-59, and optionally, wherein the RWTP bitmap comprises a plurality of bits corresponding to a respective plurality of time domain resource elements, a bit corresponding to a time domain resource element to indicate if a transmit power of the time domain resource element is not to exceed the RWTP threshold.
  • Example 61 includes the subject matter of any one of Examples 57-60, and optionally, wherein the RWTP setting includes a plurality of RWTP bitmaps corresponding a respective plurality of RWTP thresholds.
  • Example 62 includes the subject matter of any one of Examples 57-61, and optionally, wherein the backhaul link comprises an X2 Application Protocol (X2-AP) link.
  • Example 63 includes the subject matter of Example 62, and optionally, comprising receiving an X2 load information message including the RWTP setting.
  • Example 64 includes a method to be performed at an Evolved Node B (eNB), the method comprising communicating with a User Equipment (UE); determining a precoding restriction setting based on downlink communications to the UE; and sending the precoding restriction setting to another eNB via a backhaul link.
  • eNB Evolved Node B
  • UE User Equipment
  • Example 65 includes the subject matter of Example 64, and optionally, comprising receiving a precoding restriction recommendation from the another eNB, and determining the precoding restriction setting based on the precoding restriction recommendation.
  • Example 66 includes the subject matter of Example 64 or 65, and optionally, wherein the precoding restriction setting comprises a bitmap indicating a restricted precoding parameter corresponding to a precoding codebook.
  • Example 67 includes the subject matter of any one of Examples 64-66, and optionally, wherein the precoding restriction setting comprises a CodebookSubsetRestriction Information Element (IE) and a Number Of CSI Reference Signals (CSI-RS) Antenna Ports IE.
  • IE CodebookSubsetRestriction Information Element
  • CSI-RS Number Of CSI Reference Signals
  • Example 68 includes the subject matter of any one of Examples 64-67, and optionally, wherein the backhaul link comprises an X2 Application Protocol (X2-AP) link.
  • X2-AP X2 Application Protocol
  • Example 69 includes the subject matter of Example 64-68, and optionally, comprising sending an X2 load information message including the precoding restriction setting.
  • Example 70 includes a method to be performed at an Evolved Node B (eNB), the method comprising communicating with a User Equipment (UE); determining a Relative Narrowband Transmit (Tx) Power (RNTP) setting based on downlink communications to the UE, the RNTP setting comprising a plurality of RNTP bitmaps corresponding to respective plurality of different RNTP thresholds; and sending the RNTP setting to another eNB via a backhaul link.
  • eNB Evolved Node B
  • Example 71 includes the subject matter of Example 70, and optionally, comprising receiving an RNTP recommendation from the another eNB, and determining the RNTP setting based on the RNTP recommendation.
  • Example 72 includes the subject matter of Example 70 or 71, and optionally, wherein an RNTP bitmap of the plurality of RNTP bitmaps comprises a plurality of bits corresponding to a respective plurality of Physical Resource Blocks (PRB), a bit corresponding to a PRB to indicate if a transmit power of the PRB is not to exceed an RNTP threshold corresponding to the RNTP bitmap.
  • PRB Physical Resource Block
  • Example 73 includes the subject matter of any one of Examples 70-72, and optionally, wherein the backhaul link comprises an X2 Application Protocol (X2-AP) link.
  • Example 74 includes the subject matter of Example 73, and optionally, comprising sending an X2 load information message including the RNTP setting.
  • Example 75 includes a method to be performed at an Evolved Node B (eNB), the method comprising communicating with a User Equipment (UE); determining a Relative Wideband Transmit (Tx) Power (RWTP) setting based on downlink communications to the UE, the RWTP setting comprising at least one RWTP bitmap corresponding to at least one respective RWTP threshold; and sending the RWTP setting to another eNB via a backhaul link.
  • UE User Equipment
  • RWTP Relative Wideband Transmit
  • RWTP Relative Wideband Transmit
  • RWTP Relative Wideband Transmit
  • Example 75 includes a method to be performed at an Evolved Node B (eNB), the method comprising communicating with a User Equipment (UE); determining a Relative Wideband Transmit (Tx) Power (RWTP) setting based on downlink communications to the UE, the RWTP setting comprising at least one RWTP bitmap corresponding to at least one respective RWTP threshold;
  • Example 76 includes the subject matter of Example 75, and optionally, comprising receiving an RWTP recommendation from the another eNB, and determining the RWTP setting based on the RWTP recommendation.
  • Example 77 includes the subject matter of Example 75 or 76, and optionally, wherein the RWTP bitmap comprises a plurality of bits corresponding to a respective plurality of time domain resource elements, a bit corresponding to a time domain resource element to indicate if a transmit power of the time domain resource element is not to exceed the RWTP threshold.
  • Example 78 includes the subject matter of any one of Examples 75-77, and optionally, wherein the RWTP setting includes a plurality of RWTP bitmaps corresponding a respective plurality of RWTP thresholds.
  • Example 79 includes the subject matter of any one of Examples 75-78, and optionally, wherein the backhaul link comprises an X2 Application Protocol (X2-AP) link.
  • X2-AP X2 Application Protocol
  • Example 80 includes the subject matter of Example 79, and optionally, comprising sending an X2 load information message including the RWTP setting.
  • Example 81 includes a product including one or more tangible computer-readable non- transitory storage media comprising computer-executable instructions operable to, when executed by at least one computer processor, enable the at least one computer processor to implement a method at an Evolved Node B (eNB), the method comprising communicating with a User Equipment (UE); receiving a precoding restriction setting from another eNB via a backhaul link; and scheduling communications of the UE based on the precoding restriction setting.
  • eNB Evolved Node B
  • Example 82 includes the subject matter of Example 81, and optionally, wherein the method comprises sending to the another eNB a precoding restriction recommendation.
  • Example 83 includes the subject matter of Example 82, and optionally, wherein the method comprises receiving Channel State Information (CSI) from the UE, and determining the precoding restriction recommendation based on the CSI.
  • CSI Channel State Information
  • Example 84 includes the subject matter of any one of Examples 81-83, and optionally, wherein the precoding restriction setting comprises a bitmap indicating a restricted precoding parameter corresponding to a precoding codebook.
  • Example 85 includes the subject matter of any one of Examples 81-84, and optionally, wherein the precoding restriction setting comprises a CodebookSubsetRestriction Information Element (IE) and a Number Of CSI Reference Signals (CSI-RS) Antenna Ports IE.
  • IE CodebookSubsetRestriction Information Element
  • CSI-RS Number Of CSI Reference Signals
  • Example 86 includes the subject matter of any one of Examples 81-85, and optionally, wherein the backhaul link comprises a X2 Application Protocol (X2-AP) link.
  • X2-AP X2 Application Protocol
  • Example 87 includes the subject matter of Example 86, and optionally, wherein the method comprises receiving an X2 load information message including the precoding restriction setting.
  • Example 88 includes a product including one or more tangible computer-readable non- transitory storage media comprising computer-executable instructions operable to, when executed by at least one computer processor, enable the at least one computer processor to implement a method at an Evolved Node B (eNB), the method comprising communicating with a User Equipment (UE); receiving a Relative Narrowband Transmit (Tx) Power (RNTP) setting from another eNB via a backhaul link, the RNTP setting comprising a plurality of RNTP bitmaps corresponding to respective plurality of different RNTP thresholds; and scheduling communications of the UE based on the RNTP setting.
  • Example 89 includes the subject matter of Example 88, and optionally, wherein the method comprises sending to the another eNB an RNTP recommendation.
  • Example 90 includes the subject matter of Example 89, and optionally, wherein the method comprises receiving Channel State Information (CSI) from the UE, and determining the RNTP recommendation based on the CSI.
  • Example 91 includes the subject matter of any one of Examples 88-90, and optionally, wherein an RNTP bitmap of the plurality of RNTP bitmaps comprises a plurality of bits corresponding to a respective plurality of Physical Resource Blocks (PRB), a bit corresponding to a PRB to indicate if a transmit power of the PRB is not to exceed an RNTP threshold corresponding to the RNTP bitmap.
  • PRB Physical Resource Block
  • Example 92 includes the subject matter of any one of Examples 88-91, and optionally, wherein the backhaul link comprises an X2 Application Protocol (X2-AP) link.
  • Example 93 includes the subject matter of Example 92, and optionally, wherein the method comprises receiving an X2 load information message including the RNTP setting.
  • Example 94 includes a product including one or more tangible computer-readable non- transitory storage media comprising computer-executable instructions operable to, when executed by at least one computer processor, enable the at least one computer processor to implement a method at an Evolved Node B (eNB), the method comprising communicating with a User Equipment (UE); receiving a Relative Wideband Transmit (Tx) Power (RWTP) setting from another eNB via a backhaul link, the RWTP setting comprising at least one RWTP bitmap corresponding to at least one respective RWTP threshold; and scheduling communications of the UE based on the RWTP setting.
  • Example 95 includes the subject matter of Example 94, and optionally, wherein the method comprises sending to the another eNB an RWTP recommendation.
  • Example 96 includes the subject matter of Example 95, and optionally, wherein the method comprises receiving Channel State Information (CSI) from the UE, and determining the RWTP recommendation based on the CSI.
  • Example 97 includes the subject matter of any one of Examples 94-96, and optionally, wherein the RWTP bitmap comprises a plurality of bits corresponding to a respective plurality of time domain resource elements, a bit corresponding to a time domain resource element to indicate if a transmit power of the time domain resource element is not to exceed the RWTP threshold.
  • Example 98 includes the subject matter of any one of Examples 94-97, and optionally, wherein the RWTP setting includes a plurality of RWTP bitmaps corresponding a respective plurality of RWTP thresholds.
  • Example 99 includes the subject matter of any one of Examples 94-98, and optionally, wherein the backhaul link comprises an X2 Application Protocol (X2-AP) link.
  • Example 100 includes the subject matter of Example 99, and optionally, wherein the method comprises receiving an X2 load information message including the RWTP setting.
  • Example 101 includes a product including one or more tangible computer-readable non- transitory storage media comprising computer-executable instructions operable to, when executed by at least one computer processor, enable the at least one computer processor to implement a method at an Evolved Node B (eNB), the method comprising communicating with a User Equipment (UE); determining a precoding restriction setting based on downlink communications to the UE; and sending the precoding restriction setting to another eNB via a backhaul link.
  • eNB Evolved Node B
  • UE User Equipment
  • UE User Equipment
  • Example 102 includes the subject matter of Example 101, and optionally, wherein the method comprises receiving a precoding restriction recommendation from the another eNB, and determining the precoding restriction setting based on the precoding restriction recommendation.
  • Example 103 includes the subject matter of Example 101 or 102, and optionally, wherein the precoding restriction setting comprises a bitmap indicating a restricted precoding parameter corresponding to a precoding codebook.
  • Example 104 includes the subject matter of any one of Examples 101-103, and optionally, wherein the precoding restriction setting comprises a CodebookSubsetRestriction Information Element (IE) and a Number Of CSI Reference Signals (CSI-RS) Antenna Ports IE.
  • IE CodebookSubsetRestriction Information Element
  • CSI-RS Number Of CSI Reference Signals
  • Example 105 includes the subject matter of any one of Examples 101-104, and optionally, wherein the backhaul link comprises an X2 Application Protocol (X2-AP) link.
  • X2-AP X2 Application Protocol
  • Example 106 includes the subject matter of Example 105, and optionally, wherein the method comprises sending an X2 load information message including the precoding restriction setting.
  • Example 107 includes a product including one or more tangible computer-readable non- transitory storage media comprising computer-executable instructions operable to, when executed by at least one computer processor, enable the at least one computer processor to implement a method at an Evolved Node B (eNB), the method comprising communicating with a User Equipment (UE); determining a Relative Narrowband Transmit (Tx) Power (RNTP) setting based on downlink communications to the UE, the RNTP setting comprising a plurality of RNTP bitmaps corresponding to respective plurality of different RNTP thresholds; and sending the RNTP setting to another eNB via a backhaul link.
  • eNB Evolved Node B
  • Example 108 includes the subject matter of Example 107, and optionally, wherein the method comprises receiving an RNTP recommendation from the another eNB, and determining the RNTP setting based on the RNTP recommendation.
  • Example 109 includes the subject matter of Example 107 or 108, and optionally, wherein an RNTP bitmap of the plurality of RNTP bitmaps comprises a plurality of bits corresponding to a respective plurality of Physical Resource Blocks (PRB), a bit corresponding to a PRB to indicate if a transmit power of the PRB is not to exceed an RNTP threshold corresponding to the RNTP bitmap.
  • PRB Physical Resource Block
  • Example 110 includes the subject matter of any one of Examples 107-109, and optionally, wherein the backhaul link comprises an X2 Application Protocol (X2-AP) link.
  • X2-AP X2 Application Protocol
  • Example 111 includes the subject matter of Example 110, and optionally, wherein the method comprises sending an X2 load information message including the RNTP setting.
  • Example 112 includes a product including one or more tangible computer-readable non- transitory storage media comprising computer-executable instructions operable to, when executed by at least one computer processor, enable the at least one computer processor to implement a method at an Evolved Node B (eNB), the method comprising communicating with a User Equipment (UE); determining a Relative Wideband Transmit (Tx) Power (RWTP) setting based on downlink communications to the UE, the RWTP setting comprising at least one RWTP bitmap corresponding to at least one respective RWTP threshold; and sending the RWTP setting to another eNB via a backhaul link.
  • eNB Evolved Node B
  • UE User Equipment
  • RWTP Relative Wideband Transmit
  • RWTP Relative Wideband Transmit
  • RWTP Relative Wideband Transmit
  • Example 113 includes the subject matter of Example 112, and optionally, wherein the method comprises receiving an RWTP recommendation from the another eNB, and determining the RWTP setting based on the RWTP recommendation.
  • Example 114 includes the subject matter of Example 112 or 113, and optionally, wherein the RWTP bitmap comprises a plurality of bits corresponding to a respective plurality of time domain resource elements, a bit corresponding to a time domain resource element to indicate if a transmit power of the time domain resource element is not to exceed the RWTP threshold.
  • Example 115 includes the subject matter of any one of Examples 112-114, and optionally, wherein the RWTP setting includes a plurality of RWTP bitmaps corresponding a respective plurality of RWTP thresholds.
  • Example 116 includes the subject matter of any one of Examples 112-115, and optionally, wherein the backhaul link comprises an X2 Application Protocol (X2-AP) link.
  • X2-AP X2 Application Protocol
  • Example 117 includes the subject matter of Example 116, and optionally, wherein the method comprises sending an X2 load information message including the RWTP setting.
  • Example 118 includes an Evolved Node B (eNB) comprising means for communicating with a User Equipment (UE); means for receiving a precoding restriction setting from another eNB via a backhaul link; and means for scheduling communications of the UE based on the precoding restriction setting.
  • Example 119 includes the subject matter of Example 118, and optionally, comprising means for sending to the another eNB a precoding restriction recommendation.
  • Example 120 includes the subject matter of Example 119, and optionally, comprising means for receiving Channel State Information (CSI) from the UE, and determining the precoding restriction recommendation based on the CSI.
  • Example 121 includes the subject matter of any one of Examples 118-120, and optionally, wherein the precoding restriction setting comprises a bitmap indicating a restricted precoding parameter corresponding to a precoding codebook.
  • Example 122 includes the subject matter of any one of Examples 118-121, and optionally, wherein the precoding restriction setting comprises a CodebookSubsetRestriction Information Element (IE) and a Number Of CSI Reference Signals (CSI-RS) Antenna Ports IE.
  • IE CodebookSubsetRestriction Information Element
  • CSI-RS Number Of CSI Reference Signals
  • Example 123 includes the subject matter of any one of Examples 118-122, and optionally, wherein the backhaul link comprises a X2 Application Protocol (X2-AP) link.
  • X2-AP X2 Application Protocol
  • Example 124 includes the subject matter of Example 123, and optionally, comprising means for receiving an X2 load information message including the precoding restriction setting.
  • Example 125 includes an Evolved Node B (eNB) comprising means for communicating with a User Equipment (UE); means for receiving a Relative Narrowband Transmit (Tx) Power (RNTP) setting from another eNB via a backhaul link, the RNTP setting comprising a plurality of RNTP bitmaps corresponding to respective plurality of different RNTP thresholds; and means for scheduling communications of the UE based on the RNTP setting.
  • Example 126 includes the subject matter of Example 125, and optionally, comprising means for sending to the another eNB an RNTP recommendation.
  • Example 127 includes the subject matter of Example 126, and optionally, comprising means for receiving Channel State Information (CSI) from the UE, and determining the RNTP recommendation based on the CSI.
  • Example 128 includes the subject matter of any one of Examples 125-127, and optionally, wherein an RNTP bitmap of the plurality of RNTP bitmaps comprises a plurality of bits corresponding to a respective plurality of Physical Resource Blocks (PRB), a bit corresponding to a PRB to indicate if a transmit power of the PRB is not to exceed an RNTP threshold corresponding to the RNTP bitmap.
  • PRB Physical Resource Block
  • Example 129 includes the subject matter of any one of Examples 125-128, and optionally, wherein the backhaul link comprises an X2 Application Protocol (X2-AP) link.
  • X2-AP X2 Application Protocol
  • Example 130 includes the subject matter of Example 129, and optionally, comprising means for receiving an X2 load information message including the RNTP setting.
  • Example 131 includes an Evolved Node B (eNB) comprising communicating with a User Equipment (UE); receiving a Relative Wideband Transmit (Tx) Power (RWTP) setting from another eNB via a backhaul link, the RWTP setting comprising at least one RWTP bitmap corresponding to at least one respective RWTP threshold; and scheduling communications of the UE based on the RWTP setting.
  • eNB Evolved Node B
  • UE User Equipment
  • RWTP Relative Wideband Transmit
  • RWTP Relative Wideband Transmit
  • Example 132 includes the subject matter of Example 131, and optionally, comprising means for sending to the another eNB an RWTP recommendation.
  • Example 133 includes the subject matter of Example 132, and optionally, comprising means for receiving Channel State Information (CSI) from the UE, and determining the RWTP recommendation based on the CSI.
  • CSI Channel State Information
  • Example 134 includes the subject matter of any one of Examples 131-133, and optionally, wherein the RWTP bitmap comprises a plurality of bits corresponding to a respective plurality of time domain resource elements, a bit corresponding to a time domain resource element to indicate if a transmit power of the time domain resource element is not to exceed the RWTP threshold.
  • Example 135 includes the subject matter of any one of Examples 131-134, and optionally, wherein the RWTP setting includes a plurality of RWTP bitmaps corresponding a respective plurality of RWTP thresholds.
  • Example 136 includes the subject matter of any one of Examples 131-135, and optionally, wherein the backhaul link comprises an X2 Application Protocol (X2-AP) link.
  • X2-AP X2 Application Protocol
  • Example 137 includes the subject matter of Example 136, and optionally, comprising means for receiving an X2 load information message including the RWTP setting.
  • Example 138 includes an Evolved Node B (eNB) comprising means for communicating with a User Equipment (UE); means for determining a precoding restriction setting based on downlink communications to the UE; and means for sending the precoding restriction setting to another eNB via a backhaul link.
  • eNB Evolved Node B
  • UE User Equipment
  • UE User Equipment
  • Example 139 includes the subject matter of Example 138, and optionally, comprising means for receiving a precoding restriction recommendation from the another eNB, and determining the precoding restriction setting based on the precoding restriction recommendation.
  • Example 140 includes the subject matter of Example 138 or 139, and optionally, wherein the precoding restriction setting comprises a bitmap indicating a restricted precoding parameter corresponding to a precoding codebook.
  • Example 141 includes the subject matter of any one of Examples 138-140, and optionally, wherein the precoding restriction setting comprises a CodebookSubsetRestriction Information Element (IE) and a Number Of CSI Reference Signals (CSI-RS) Antenna Ports IE.
  • IE CodebookSubsetRestriction Information Element
  • CSI-RS Number Of CSI Reference Signals
  • Example 142 includes the subject matter of any one of Examples 138-141, and optionally, wherein the backhaul link comprises an X2 Application Protocol (X2-AP) link.
  • X2-AP X2 Application Protocol
  • Example 143 includes the subject matter of Example 142, and optionally, comprising means for sending an X2 load information message including the precoding restriction setting.
  • Example 144 includes an Evolved Node B (eNB) comprising means for communicating with a User Equipment (UE); means for determining a Relative Narrowband Transmit (Tx) Power (RNTP) setting based on downlink communications to the UE, the RNTP setting comprising a plurality of RNTP bitmaps corresponding to respective plurality of different RNTP thresholds; and means for sending the RNTP setting to another eNB via a backhaul link.
  • eNB Evolved Node B
  • UE User Equipment
  • RNTP Relative Narrowband Transmit
  • RNTP Relative Narrowband Transmit
  • RNTP Relative Narrowband Transmit
  • Example 144 includes an Evolved Node B (eNB) comprising means for communicating with a User Equipment (UE); means for determining a Relative Narrowband Transmit (Tx) Power (RNTP) setting based on downlink communications to the UE, the RNTP setting comprising a plurality of
  • Example 145 includes the subject matter of Example 144, and optionally, comprising means for receiving an RNTP recommendation from the another eNB, and determining the RNTP setting based on the RNTP recommendation.
  • Example 146 includes the subject matter of Example 144 or 145, and optionally, wherein an RNTP bitmap of the plurality of RNTP bitmaps comprises a plurality of bits corresponding to a respective plurality of Physical Resource Blocks (PRB), a bit corresponding to a PRB to indicate if a transmit power of the PRB is not to exceed an RNTP threshold corresponding to the RNTP bitmap.
  • PRB Physical Resource Block
  • Example 147 includes the subject matter of any one of Examples 144-146, and optionally, wherein the backhaul link comprises an X2 Application Protocol (X2-AP) link.
  • Example 148 includes the subject matter of Example 147, and optionally, comprising means for sending an X2 load information message including the RNTP setting.
  • Example 149 includes an Evolved Node B (eNB) comprising means for communicating with a User Equipment (UE); means for determining a Relative Wideband Transmit (Tx) Power (RWTP) setting based on downlink communications to the UE, the RWTP setting comprising at least one RWTP bitmap corresponding to at least one respective RWTP threshold; and means for sending the RWTP setting to another eNB via a backhaul link.
  • eNB Evolved Node B
  • UE User Equipment
  • RWTP Relative Wideband Transmit
  • RWTP Relative Wideband Transmit
  • Example 150 includes the subject matter of Example 149, and optionally, comprising means for receiving an RWTP recommendation from the another eNB, and determining the RWTP setting based on the RWTP recommendation.
  • Example 151 includes the subject matter of Example 149 or 150, and optionally, wherein the RWTP bitmap comprises a plurality of bits corresponding to a respective plurality of time domain resource elements, a bit corresponding to a time domain resource element to indicate if a transmit power of the time domain resource element is not to exceed the RWTP threshold.
  • Example 152 includes the subject matter of any one of Examples 149-151, and optionally, wherein the RWTP setting includes a plurality of RWTP bitmaps corresponding a respective plurality of RWTP thresholds.
  • Example 153 includes the subject matter of any one of Examples 149-152, and optionally, wherein the backhaul link comprises an X2 Application Protocol (X2-AP) link.
  • X2-AP X2 Application Protocol
  • Example 154 includes the subject matter of Example 153, and optionally, comprising means for sending an X2 load information message including the RWTP setting.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/US2015/011516 2014-01-30 2015-01-15 Apparatus, method, and system of inter-node communication WO2015116393A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP15743522.3A EP3100584A4 (en) 2014-01-30 2015-01-15 Apparatus, method, and system of inter-node communication
CN201580003286.1A CN105850225B (zh) 2014-01-30 2015-01-15 节点间通信的装置、方法和系统

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201461933859P 2014-01-30 2014-01-30
US61/933,859 2014-01-30
US14/492,333 US9736834B2 (en) 2014-01-30 2014-09-22 Apparatus, method, and system of inter-node communication
US14/492,333 2014-09-22

Publications (1)

Publication Number Publication Date
WO2015116393A1 true WO2015116393A1 (en) 2015-08-06

Family

ID=53680435

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/011516 WO2015116393A1 (en) 2014-01-30 2015-01-15 Apparatus, method, and system of inter-node communication

Country Status (6)

Country Link
US (1) US9736834B2 (zh)
EP (1) EP3100584A4 (zh)
CN (1) CN105850225B (zh)
HK (1) HK1225895A1 (zh)
TW (1) TWI590698B (zh)
WO (1) WO2015116393A1 (zh)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9888469B2 (en) 2014-03-19 2018-02-06 Nec Corporation Signalling for coordinated multi-point transmission and reception (CoMP)
US10230507B2 (en) * 2014-09-25 2019-03-12 Nec Corporation Signalling in coordinated multi-point transmission and reception (CoMP)
US10224986B2 (en) 2014-09-25 2019-03-05 Nec Corporation Signalling in coordinated multi-point transmission and reception (CoMP)
CN106982109B (zh) * 2016-01-16 2021-02-09 华为技术有限公司 一种无线通信的回程传输方法、控制器、基站、网关
US10594427B2 (en) 2016-05-13 2020-03-17 Intel Corporation Inter evolved NODEB coordinated beamforming
CN111342868B (zh) * 2016-06-22 2021-06-25 上海朗帛通信技术有限公司 一种大尺度mimo的传输方法和装置
EP3306828B1 (en) * 2016-10-07 2019-06-05 Mitsubishi Electric R&D Centre Europe B.V. Method for determining a precoder in a distributed fashion
CN107743078B (zh) * 2016-11-15 2020-01-31 腾讯科技（深圳）有限公司 一种网络数据的监控方法、装置和系统
CN108400804B (zh) * 2017-02-06 2021-07-09 大唐移动通信设备有限公司 一种上行数据传输方法、终端和网络侧设备
US10568082B2 (en) 2017-09-08 2020-02-18 At&T Intellectual Property I, L.P. Reducing higher layer signaling overhead in multiantenna wireless communication systems
CN110535505B (zh) * 2019-03-29 2023-04-07 中兴通讯股份有限公司 控制预编码的方法、装置、终端设备及基站
US20230318881A1 (en) * 2022-04-05 2023-10-05 Qualcomm Incorporated Beam selection using oversampled beamforming codebooks and channel estimates

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009120048A2 (en) 2008-03-28 2009-10-01 Lg Electronics Inc. Method for avoiding inter-cell interference in a multi-cell environment
US20130051240A1 (en) * 2011-02-14 2013-02-28 Qualcomm Incorporated CRS (COMMON REFERENCE SIGNAL) AND CSI-RS (CHANNEL STATE INFORMATION REFERENCE SIGNAL) TRANSMISSION FOR REMOTE RADIO HEADS (RRHs)
US20130344816A1 (en) * 2012-06-26 2013-12-26 Huaning Niu Mobility measurment using csi-rs in additional carrier
EP2680639A1 (en) * 2011-02-24 2014-01-01 Huawei Technologies Co., Ltd. Method and device for managing user equipment

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1841092B1 (en) * 2006-03-28 2012-01-25 Sony Deutschland Gmbh Wireless communication method and system
US8825100B2 (en) * 2008-08-11 2014-09-02 Blackberry Limited Method and system for providing a power boost for a wireless communication link using a subset of subcarrier frequencies of the wireless communication link channel as a reduced bandwidth channel
CN101420734A (zh) * 2008-11-28 2009-04-29 华为技术有限公司 下行干扰协调方法和基站
US9544913B2 (en) 2009-08-24 2017-01-10 Fraunhofer Gesellschaft Zur Forderung Der Angewandten Forschung E.V. Controlling scheduling decisions in a distributed cooperation system
CN102648645B (zh) * 2009-10-26 2015-04-15 意大利电信股份公司 无线通信系统中的基于分数的干扰协调
CN102271337B (zh) * 2010-06-03 2015-09-16 中兴通讯股份有限公司 小区间干扰协调信息的处理方法及装置
WO2012044088A2 (ko) * 2010-09-29 2012-04-05 엘지전자 주식회사 다중 안테나 지원 무선 통신 시스템에서 효율적인 피드백 방법 및 장치
EP2633633B1 (en) * 2010-10-25 2019-06-26 LG Electronics Inc. Method of reducing intercell interference in wireless communication system and apparatus thereof
EP2590336A1 (en) * 2011-11-07 2013-05-08 Panasonic Corporation Precoding matrix set quality measurement and reporting
EP3011784B1 (en) * 2013-06-17 2017-09-13 Telefonaktiebolaget LM Ericsson (publ) Methods and base stations for assisting scheduling of a user equipment in a heterogeneous network
CN104349488A (zh) * 2013-08-09 2015-02-11 阿尔卡特朗讯 多点协作中的信令信息交换装置与方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009120048A2 (en) 2008-03-28 2009-10-01 Lg Electronics Inc. Method for avoiding inter-cell interference in a multi-cell environment
US20130051240A1 (en) * 2011-02-14 2013-02-28 Qualcomm Incorporated CRS (COMMON REFERENCE SIGNAL) AND CSI-RS (CHANNEL STATE INFORMATION REFERENCE SIGNAL) TRANSMISSION FOR REMOTE RADIO HEADS (RRHs)
EP2680639A1 (en) * 2011-02-24 2014-01-01 Huawei Technologies Co., Ltd. Method and device for managing user equipment
US20130344816A1 (en) * 2012-06-26 2013-12-26 Huaning Niu Mobility measurment using csi-rs in additional carrier

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3100584A4

Also Published As

Publication number Publication date
US9736834B2 (en) 2017-08-15
TW201542017A (zh) 2015-11-01
HK1225895A1 (zh) 2017-09-15
TWI590698B (zh) 2017-07-01
CN105850225A (zh) 2016-08-10
CN105850225B (zh) 2021-05-18
EP3100584A1 (en) 2016-12-07
EP3100584A4 (en) 2017-12-20
US20150215934A1 (en) 2015-07-30

Similar Documents

Publication Publication Date Title
US10433254B2 (en) Method, system and apparatus of time-division-duplex (TDD) uplink-downlink (UL-DL) configuration management
US9736834B2 (en) Apparatus, method, and system of inter-node communication
US9673928B2 (en) Method, system and apparatus of time-division-duplex (TDD) uplink-downlink (UL-DL) configuration management
CN109195148B (zh) 用于资源分配和设备对设备发现跳的用户设备和方法
US20220104208A1 (en) Csi reporting method and terminal device
CN109156030B (zh) Pucch资源分配
KR20200044963A (ko) 업링크 제어 채널을 전송하기 위한 방법 및 장치
CN114514723A (zh) 针对版本16类型ii信道状态信息(csi)的csi省略过程
WO2019137299A1 (zh) 通信的方法和通信设备
WO2019024786A1 (zh) 通信方法和网络设备
US20200328786A1 (en) Communication Method, Network Device, and Terminal Device
US20230361975A1 (en) Method of sharing srs resources between srs resource sets of different usages, and corresponding ue
WO2022150484A1 (en) Methods of mapping multiple sd-fd bases per csi-rs port for type ii port selection codebook
US20180352465A1 (en) Information Transmission Apparatus and Method and Communication System
WO2022216545A1 (en) Methods of defining frequency domain starting position for srs partial frequency sounding
CN117998605A (zh) 传输配置确定方法、装置及存储介质
CN117880985A (zh) 信息处理方法、配置方法、装置、终端及网络侧设备
CN117040706A (zh) 一种dci确定方法、设备及装置
CN117917156A (zh) 用于非基于码本的传输的系统和方法
JP2013031210A (ja) 移動通信システム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15743522

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2015743522

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015743522

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE